Opened 5 years ago

Last modified 5 years ago

#2832 new defect

failures_only stopped working in 0.8.9

Reported by: mchandras Owned by:
Priority: major Milestone: 0.8.x
Version: 0.8.9 Keywords:
Cc:

Description

Hi,

Ever since I updated my master to 0.8.9, the failures_only=true parameter in waterfall and feeds has no effect. In waterfall, all the builds are listed (whether they have failed or not) and in feeds, I end up with a blank page and rss/atom readers say that the URL is invalid. Removing the ?failures_only=True results to proper rss/atom feeds with all the builders.

Let me know if you need more information.

Change History (6)

comment:1 Changed 5 years ago by dustin

  • Milestone changed from undecided to 0.8.x
  • Type changed from undecided to defect

The only possibly-related change I can see is [c0fa34187978f1e15504105289ab5e007fcb7f86]. If you revert that, does it start working?

comment:2 Changed 5 years ago by dustin

  • Milestone changed from 0.8.x to 0.8.x (unmaintained)

Milestone renamed

comment:3 Changed 5 years ago by mchandras

Unfortunately it does not seem to solve the problem.

comment:4 Changed 5 years ago by dustin

I have no idea what could have caused the change, then. You're welcome to go digging, noting that all of waterfall.py has been removed already in master.

comment:5 Changed 5 years ago by mchandras

Seems like I was a bit wrong. With failures_only=true in waterfall, I get builders that have failed *and* have warnings. Previously, in 0.8.8, I am fairly sure, I was only getting the failed builders. This is a change in behavior. I will keep digging anyway.

comment:6 Changed 5 years ago by dustin

  • Milestone changed from 0.8.x (unmaintained) to 0.8.x

Milestone renamed

Note: See TracTickets for help on using tickets.