Merge lp:~julian-edwards/launchpad/build-queue-sizes-bug-609904 into lp:launchpad
Status: | Merged |
---|---|
Approved by: | Māris Fogels |
Approved revision: | no longer in the source branch. |
Merged at revision: | 11289 |
Proposed branch: | lp:~julian-edwards/launchpad/build-queue-sizes-bug-609904 |
Merge into: | lp:launchpad |
Diff against target: |
75 lines (+28/-5) 2 files modified
lib/lp/buildmaster/doc/builder.txt (+21/-1) lib/lp/buildmaster/model/builder.py (+7/-4) |
To merge this branch: | bzr merge lp:~julian-edwards/launchpad/build-queue-sizes-bug-609904 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Māris Fogels (community) | code | Approve | |
Review via email: mp+31647@code.launchpad.net |
Description of the change
= Summary =
Put pending builds that have virtualized=False in the virtual build queues on
/builders
== Proposed fix ==
IBuilderSet.
BuildQueue.
query will potentially return three groups instead of the expected two, and
because of the bad code in the following "for" loop it will overwrite the
dictionary entry for "nonvirt" depending on which group it sees first in the
results iteration.
== Implementation details ==
Simple fix in the query to coalesce the result so that if it's NULL we turn it
into a True. Also made the inline "if" more explicit.
== Tests ==
bin/test -cvvt builder.txt
== Demo and Q/A ==
Easy to check on edge, there's about 160 pending translations builds
erroneously showing up in the distro builders queue right now!
= Launchpad lint =
Checking for conflicts and issues in changed files.
Hi Julian,
I have a bit of difficulty reviewing this without domain-specific knowledge, so I'll trust you that the code is ok. But I did have a question about the tests.
You see, I'm a bit confused by the doc/ directory and the files within. When I am reading a documentation file I don't care what the 'virtualized' flag does, I just care that it exists. I also don't want to read the gritty details of how it behaves correctly when a certain bug is present (which is what the new doctest code is for). The implementation details and bugfix test should be off in a unit test somewhere.
So, is the doctest the right place to exercise the bugfix? What is the purpose of doc/builder.txt?
I'm marking this as 'Needs Information' for now.
Maris