Opened 4 years ago

Last modified 2 years ago

#3121 new defect

Master deactivation iterates over all builds

Reported by: dustin Owned by:
Priority: major Milestone: 0.9.+
Version: 0.8.10 Keywords: database, simple


When a master is deactivated, it performs a query for all builds on that master, and marks them as RETRY. However, that query is not optimized down to the DB level, so in practice we select *all* builds, ever, into a Python list and then filter that in Python. That's very inefficient!

The fix is to trace the 'masterid' and 'results' parameters through the data API endpoint and into the DB API.

Change History (2)

Note: See TracTickets for help on using tickets.