New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 665088 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Hard to understand the output from patch failure

Project Member Reported by primiano@chromium.org, Nov 14 2016

Issue description

I was trying to understand why all the bots failed here in
https://codereview.chromium.org/2494063002/#ps40001
which is only moving docs around.

patch_failure failed, it seems a conflict. Good.
Now I want to understand what did conflict and why. Here's the problem:
I don't see any useful information in the stdout of the failing step.

For instance 
https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Ftryserver.chromium.linux%2Flinux_chromium_clobber_rel_ng%2F270370%2F%2B%2Frecipes%2Fsteps%2FPatch_failure%2F0%2Fstdout

Form what I see this thing is telling me that:
- The command being executed was: cmd: ['python', '-u', '/tmp/tmpcaGumx.py']
- That thing returned exit code 1.

Could this thing be a be a bit less cryptical and more verbose?
As it is, this doesn't give me any clue about what's going on.
 
Components: -Infra Infra>Client>Chrome
+ new cross-over team - this is a clear UX issue.
Cc: iannucci@chromium.org
Components: -Infra>Client>Chrome Infra>SDK Infra>Platform
Status: Available (was: Untriaged)
I think this is really about how we do patches on our bots. Not sure who knows this the best.
Status: Fixed (was: Available)
The way bots apply patches has changed wildly, it is now handled in bot_update and much clearer.

Sign in to add a comment