New issue
Advanced search Search tips

Issue 779095 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

[WPT import] Check Blink trybot failure reason?

Project Member Reported by raphael....@intel.com, Oct 27 2017

Issue description

Not exactly a bug, but rather something I'd like to discuss.

https://build.chromium.org/p/chromium.infra.cron/builders/wpt-importer/builds/3962 was working fine, but the Mac build was broken when the mac*_blink_rel trybots were processing the import, which meant they didn't run the layout tests and the rebaselines were made only against Linux and Windows. Obviously, the final patch didn't work because it caused mac_chromium_rel_ng to go red.

I wonder if we can and whether it makes sense to either cause the import to fail or retrigger the trybots when they fail for a reason that's not "layout tests not passing".
 
My thoughts: For that particular case, that would have made the import faster. But failing the import (because the CQ bot fails) and then restarting a new import job should also work -- so this added logic might not be worth the added cost in complexity.
Is that currently doable though?

`git-cl try-results -- issue 740976  --gerrit -p 1 --json -' returns a JSON with the same value in the "failure_reason" field for both build failures and layout test failures, so it's not clear if we can use git-cl to determine how a build has failed.
Yes let's get rid of that string concatenation then! The simpler, the merrier :)
> Yes let's get rid of that string concatenation then! The simpler, the merrier :)

That was supposed to have been sent to  issue 755753 , right?
Oops, yes. Sorry, working on a shuttle bus is harder than I imagined. :(
Project Member

Comment 6 by sheriffbot@chromium.org, Oct 30

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Type-Task Type-Feature
Status: Available (was: Untriaged)
Looks like this is still a possible feature, but low-priority.

Sign in to add a comment