maas-builds team mailing list archive

[Raphaël Badin <raphael.badin@xxxxxxxxxxxxx>]

> test_power_up_node (maastest.main.ConfiguredTestMAAS) ... ok
> test_enlist_node (maastest.main.ConfiguredTestMAAS) ... ok
> test_wait_node_down (maastest.main.ConfiguredTestMAAS) ... ok
> test_commission_node (maastest.main.ConfiguredTestMAAS) ... ok
>
> ----------------------------------------------------------------------
> Ran 4 tests in 333.599s
>
> OK
> 2014-01-21 18:37:59,116 INFO Test log saved to /var/log/maas-test/maas-test.2014-01-21_23:37:59.log.
> 2014-01-21 18:37:59,749 INFO Test results uploaded to Launchpad.
> 2014-01-21 18:37:59,750 INFO Visit https://bugs.launchpad.net/maas/+filebug/0fd84e12-82f5-11e3-8fef-d485646cd9a4 to file a bug and complete the maas-test reporting process.
> 2014-01-21 18:38:04,948 INFO Destroying virtual machine 6fdb19a4-82f3-11e3-8c0a-20aa4be0dc05...
> 2014-01-21 18:38:07,235 INFO Done destroying virtual machine 6fdb19a4-82f3-11e3-8c0a-20aa4be0dc05.
> + RET=0
> + exit 0
> Archiving artifacts
> ERROR: No artifacts found that match the file pattern "results/*stderr,results/*stdout,results/*log,results/log,results/*.crash". Configuration error?
> ERROR: 'results/*stderr' doesn't match anything: even 'results' doesn't exist
> Build step 'Archive the artifacts' changed build result to FAILURE
> Email was triggered for: Failure
> Sending email for trigger: Failure


As you can see from the lines above, this is not a real failure but a 
simple problem when "archiving artifacts".

This should fix the problem: 
https://code.launchpad.net/~rvb/maas/ci-no-artifacts/+merge/202616