Issue metadata
Sign in to add a comment
|
compile confirm no-op failing on chromium/Mac |
||||||||||||||||||||||
Issue descriptioncompile confirm no-op failing on chromium/Mac Builders failed on: - Mac: https://build.chromium.org/p/chromium/builders/Mac This failure is happening pretty frequently right now. Looking at older bugs where this was happening ( Issue 667151 , Issue 695889), it looks like the usual way to fix this is by rebooting the bot.
,
Mar 3 2017
Please don't assign directly to trooper. See go/bug-a-trooper
,
Mar 3 2017
Ah, sorry about that.
,
Mar 3 2017
I should have said above -- often troopers don't monitor their personal queues when trooping. So one reason it's important to follow the protocol is so your bug gets seen. Restarting the bot.
,
Mar 3 2017
,
Mar 3 2017
Last build succeeded!
,
Mar 3 2017
This explanation doesn't sound right to me. It looks like the first variant of this bug dates back to bug 602169 , which was WontFixed, though I'm not sure why. I'm going to follow up on that. Second, shouldn't this builder be auto-rebooting?
,
Mar 3 2017
I think this builder (and all of the ones on p/chromium) are auto-rebooting. So we probably didn't need to do anything here (that or the two things aren't really causally connected).
,
Mar 4 2017
This has started failing again with the same "compile confirm no-op" issue - reopening this bug for further investigation.
,
Mar 4 2017
,
Mar 4 2017
,
Mar 4 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by sclit...@chromium.org
, Mar 3 2017Status: Assigned (was: Available)