RyanVM just noticed that my project branch is missing b2g tests. I need those enabled ASAP. Thanks!
5 years ago
Component: Buildduty → Platform Support
QA Contact: bugspam.Callek → coop
Component: Platform Support → General Automation
QA Contact: coop → catlee
If someone wants to stab themselves in the face, far be it from me to not hand them the fork. Last time I did this to someone, this was what it took, can't see where anything's changed in the last year to require any more.
Assignee: nobody → philringnalda
Status: NEW → ASSIGNED
Attachment #8483929 - Flags: review?(catlee)
Comment on attachment 8483929 [details] [diff] [review] jammin Review of attachment 8483929 [details] [diff] [review]: ----------------------------------------------------------------- what could possibly go wrong?
Attachment #8483929 - Flags: review?(catlee) → review+
Comment on attachment 8483929 [details] [diff] [review] jammin https://hg.mozilla.org/build/buildbot-configs/rev/d947a55a5e19
Attachment #8483929 - Flags: checked-in+
Is there anything that needs to be done now? Some kind of reconfig process?
Exactly that. You'll see a comment from someone in releng along the lines of "In production," tomorrow if someone says wcpgw? and reconfigs on a Friday, or early next week if they decide not to break things on a Friday, and then builds that start after that will trigger tests.
I missed a bet by not adding a snotty "or, someone will reconfig toward the end of their day, it'll break stuff, and by the time things get straightened out they'll forget all about commenting in bugs, and sometime later when I figure out from context that a reconfig must have happened, I'll comment and close the bug." In production, and the build I retriggered ran tests.
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.