[lustre-devel] [testing] Maloo not scheduling tests

quentin.bouget at cea.fr quentin.bouget at cea.fr
Wed Oct 16 08:32:53 PDT 2019

On 16/10/2019 17:23, Andreas Dilger wrote:
> On Oct 16, 2019, at 19:21, quentin.bouget at cea.fr 
> <mailto:quentin.bouget at cea.fr> wrote:
>> Hello,
>> It seems like Maloo is not scheduling tests for this patch 
>> <https://review.whamcloud.com/#/c/36292/> since I added some test 
>> parameters yesterday:
>>     Test-Parameters: fortestonly testlist=sanity clientarch=ppc64
>> Are there problems on Maloo, or am I doing something wrong?
> The "fortestonly" keyword is for patches that are not intended for 
> landing (e.g. work-in-progress patches for early review), so only a 
> limited number of tests are run.
Yes, I understand this. The idea was to check that the current version 
of the patch does fail on a big-endian client. But it does not seem like 
any tests are being scheduled.

EDIT: I just checked gerrit, there must have been a temporary failure, a 
retest was requested by M. Omstead.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20191016/bcf44174/attachment.html>

More information about the lustre-devel mailing list