New issue
Advanced search Search tips

Issue 892200 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Oct 8
Cc:
dpranke@chromium.org
jbudorick@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Compile takes 4 minutes to fail

Project Member Reported by martiniss@chromium.org, Oct 4 
https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8933595629039467392/+/steps/compile/0/stdout#L45884_3 is a link to the logs.

It looks like the build fails then, but according to the logdog timestamps, it takes over 4 minutes for the compile to actually fail, which seems strange to me. Ideally we'd fail as soon as we see the actual failure.

Is this a bug? Known behavior?

Not sure what the best component for this is.

Comment 1 by dpranke@chromium.org, Oct 6 

Ninja tries to make as much progress during a build as it can before exiting, and so when there's a bunch of jobs running, even when one fails, it'll wait for all of the other currently executing jobs finish before exiting. You're seeing this, in that the last command that completes is a link and likely took a while to complete.

[ though  I think it only took ~50 seconds to fail (from 259.7s to 305s), not 240. ]

I.e., this looks like it's working as intended.

Comment 2 by jbudorick@chromium.org, Oct 8

Status: WontFix (was: Unconfirmed)
Yeah, I agree that this seems WAI.
►

Sign in to add a comment