On 04/22/2016 01:25 PM, Amrith Kumar wrote:
The links being referenced in this email for the UNSTABLE outcomes appear to be
missing. Also, I notice that a whole bunch of stable jobs failed around the
same time. Would someone on stable-maint please confirm whether there was
something environmental going on at the time before teams start digging into
these failures.
Yes, UNSTABLE means a problem that Jenkins encountered. It could not
upload logs to logs.openstack.org and therefore marked the jobs as UNSTABLE.
Joshua Hesketh took care of repairing the file system, everything should
be fine again.
If you had a normal job falling due to UNSTABLE jobs, please issue a
"recheck". For periodic jobs like yours, let's wait for tomorrow for the
next run,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
