reno

sphinx 1.6.1 interprets error log messages as errors

Bug #1691224 reported by Doug Hellmann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
reno
Fix Released
Undecided
Unassigned

Bug Description

Reno sends log messages to the ERROR level under some cases, and Sphinx now interprets those as errors to cause the build to stop when strict mode is enabled.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote :

Related patch https://review.openstack.org/465135

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to reno (master)

Reviewed: https://review.openstack.org/465138
Committed: https://git.openstack.org/cgit/openstack/reno/commit/?id=65a69398b8c7b8452303ad360d51c489b022ab00
Submitter: Jenkins
Branch: master

commit 65a69398b8c7b8452303ad360d51c489b022ab00
Author: Doug Hellmann <email address hidden>
Date: Tue May 16 14:13:03 2017 -0400

    lower the log level for an error message

    Sphinx 1.6.1 now interprets error and warning log messages as reasons to
    abort the build when strict mode is enabled. Change the log level for
    some calls that weren't really errors to begin with.

    Change-Id: I688ee8b57e839ba6146633365be9ba8f92e3c7df
    Closes-Bug: #1691224
    Signed-off-by: Doug Hellmann <email address hidden>

Changed in reno:
status: New → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/reno 2.3.0

This issue was fixed in the openstack/reno 2.3.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.