Tony Breeds <tony at bakeyournoodle.com> writes: > On Mon, Dec 10, 2018 at 04:49:47AM +0000, zuul at openstack.org wrote: >> Build failed. >> >> - publish-openstack-releasenotes-python3 http://logs.openstack.org/31/31314e5e707bfe4933e1046dd0a18f1daa8cca6c/tag/publish-openstack-releasenotes-python3/bc14e14/ : POST_FAILURE in 2m 31s > > Looking at the logs I think this failed in create-afs-token[1]. If I > Understand correctly this means the releasenotes weren't published but > they will upon the next successful publish run. > > Yours Tony. > > [1] http://logs.openstack.org/31/31314e5e707bfe4933e1046dd0a18f1daa8cca6c/tag/publish-openstack-releasenotes-python3/bc14e14/job-output.txt.gz#_2018-12-10_04_49_23_454869 > _______________________________________________ > Release-job-failures mailing list > Release-job-failures at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures Yes, that job should run again as part of the post pipeline when another patch is merged in the openstack/freezer repository. The published docs should reflect the newly tagged version. -- Doug