Closed Bug 956624 Opened 6 years ago Closed 6 years ago

Try valgrind jobs coalesce when they shouldn't

Categories

(Release Engineering :: General, defect, P2)

x86
All
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nthomas, Assigned: nthomas)

Details

Attachments

(1 file)

http://hg.mozilla.org/try/pushloghtml?fromchange=387e2dbf898b&tochange=2be0fc2f13a8 has pushes at 17:35:25 (daf17073da76) and 17:35:57 (2be0fc2f13a8) today. The poller came along at 17:36:53 and added them to the scheduler db with separate sourcestamps, buildsets buildrequests etc.

When the jobs ran they got combined into a single job with both changes
http://buildbot-master87.srv.releng.scl3.mozilla.com:8101/builders/Linux%20x86-64%20try%20valgrind/builds/173

This may only happen for changes with the same author, or it might just require two pushes in less than 60 seconds (but should have heard already in this case), or valgrind isn't being treated right.
Looks like a valgrind specific issue, the builder never gets added to the nomergeBuilders list.
Assignee: nobody → nthomas
Priority: -- → P2
Summary: Try compilation jobs will coalesce if multiple pushes in less than polling interval (60s) → Try valgrind jobs coalesce when they shouldn't
... so that http://hg.mozilla.org/build/buildbotcustom/file/default/misc.py#l999 can do its thing. Also double checked that nothing else needs this on try.
Attachment #8356016 - Flags: review?(catlee)
Attachment #8356016 - Flags: review?(catlee) → review+
Comment on attachment 8356016 [details] [diff] [review]
[buildbotcustom] Add valgrind name to list of builders

https://hg.mozilla.org/build/buildbotcustom/rev/b7cf19f1b3cc

This should get deployed tomorrow morning.
Attachment #8356016 - Flags: checked-in+
In production (not CCed).
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.