We've had far too many cases where nightlies get run on slow build machines when we're under load, and it can take many many many hours to finish. I think it's better to wait for a fast machine to become ready.
I agree, and it may be worth extending this to all compile jobs too. Wait for X mins for a fast machine before using a slow one ?
maybe we can also prioritize nightly builds over all non-release builds?
Assignee: nobody → catlee
Priority: -- → P3
I can't find the bug for using *only* fast slaves for releases. Is that filed or could we use this bug for it too?
Armen, search for usage of nextSlave in buildbot-configs/mozilla2/release_master.py to see how we already do this for releases.
Thanks Nick, I now see how this works. As I understand it, it is also beneficial to *only* run release builds on fast slaves.
Created attachment 485388 [details] [diff] [review] Use only fast slaves for nightly builds I don't think we're ready to switch this on for regular builds yet. Also in the cases where there are no fast slaves (e.g. osx 10.6), we fall back to using slow slaves.
Attachment #485388 - Flags: review?(nrthomas) → review+
Comment on attachment 485388 [details] [diff] [review] Use only fast slaves for nightly builds Looks good! Should we consider using this for mobile as well? Not sure if it matters for android (vms and hardware took the same time to compile last I looked), but it might be worthwhile for maemo and the desktop builds.
Attachment #485388 - Flags: review?(jhford) → review+
Comment on attachment 485388 [details] [diff] [review] Use only fast slaves for nightly builds changeset: 1036:1038ecb9fe0a
Attachment #485388 - Flags: checked-in+
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Flags: needs-reconfig? → needs-reconfig+
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.