Hi Bob, Thanks for looking into this. Cheers, --Morgan On Wed, Dec 9, 2015 at 3:39 AM, Bob Ball <bob.ball at citrix.com> wrote: > Sorry – just got to this mail. > > > > Just to be clear, this was a transient failure on the 7th December, which > is now fixed. > > > > The most recent recheck was successful and > http://zuul.openstack.xenproject.org/scoreboard/?project=openstack%2Fnova&user=jenkins%2CXenProject-CI&timeframe=48&start=&end=&page_size=100 > shows the XenProject CI to be healthy over the last 48 hours. > > > > Thanks, > > > > Bob > > > > *From:* Morgan Fainberg [mailto:morgan.fainberg at gmail.com] > *Sent:* 08 December 2015 23:57 > *To:* openstack-ci at xenproject.org; OpenStack Infra > *Subject:* Thirdparty CI: XenProject CI Failures result in 404 (no logs) > > > > As seen in changeset https://review.openstack.org/#/c/253792/ the 3rd > party CI for XenProject CI check is resulting in HTTP 404 instead of useful > logs. As this is a voting job, the lack of these logs make it hard to > determine if the failure is related to the changeset or unrelated. The > example failure is here: > http://logs.openstack.xenproject.org/92/253792/7/check/dsvm-tempest-xen/1aa770f > from the most recent failed run. > > I would like to ask that this is looked into so that we can continue to > benefit from the XenProject CI reporting on patch-sets. > > Thanks! > > --Morgan > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20151209/06186ff3/attachment.html>