New issue
Advanced search Search tips

Issue 814462 link

Starred by 1 user
Status: Fixed
Owner:
bpastene@chromium.org
Closed: Feb 2018
Cc:
chrome-trooper-bugs@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

"update_scripts" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Feb 21 2018 
"update_scripts" is flaky.

This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is not infrastructure-related (e.g. flaky test), please add Sheriff-Chromium label and change issue status to Untriaged. When done, please remove the issue from Trooper Bug Queue by removing the Infra-Troopers label.

We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyGQsSBUZsYWtlIg51cGRhdGVfc2NyaXB0cww.

The chromium-try-flakes app is able to file bugs for individual tests when the test launcher is uploading results to the Test Results Server. If recent flakes above are caused by failing tests and you would like to have them filed as invidual bugs, please read more at https://goo.gl/QJKXV4.

This flaky test/step was previously tracked in  issue 811026 .

Comment 1 by sergeybe...@chromium.org, Feb 21 2018

Owner: sergeybe...@chromium.org
Status: Assigned (was: Untriaged)
I don't see a useful pattern:

https://ci.chromium.org/buildbot/tryserver.chromium.win/win10_chromium_x64_rel_ng/87032 - the step timed out after 1h.

https://ci.chromium.org/buildbot/tryserver.chromium.win/win-msvc-rel/57710 and
https://ci.chromium.org/buildbot/tryserver.chromium.win/win-msvc-rel/57621 - something got corrupted somewhere in git:

From https://chromium.googlesource.com/chromium/tools/build
 = [up to date]            infra/config          -> origin/infra/config
 = [up to date]            master                -> origin/master
 = [up to date]            recipe-package-canary -> origin/recipe-package-canary
error: bad signature
fatal: index file corrupt
error: Could not fetch origin
Auto packing the repository in background for optimum performance.
See "git help gc" for manual housekeeping.
error: bad signature
fatal: index file corrupt
error: failed to run repack

The last 2 builds ran on different bots, so it's likely not a borked machine.

Comment 2 by sergeybe...@chromium.org, Feb 21 2018 

Apparently, there are many ways to fail:

https://ci.chromium.org/buildbot/tryserver.chromium.win/win7_chromium_rel_ng/106011

_____ slave.DEPS at refs/remotes/origin/master
----------------------------------------
Error: Command 'git remote --verbose update' returned non-zero exit status 1 in C:\b\slave.DEPS
Fetching origin

fatal: unable to access 'https://chrome-internal.googlesource.com/chrome/tools/build/slave.DEPS/': Could not resolve host: chrome-internal.googlesource.com
error: Could not fetch origin

Comment 3 by sergeybe...@chromium.org, Feb 22 2018

Labels: -Pri-1 Pri-3
I'm putting this on a back burner for now. This seems to be a not-very-actionable alert that doesn't cause too much trouble anyway.

Comment 4 by sergeybe...@chromium.org, Feb 23 2018

Owner: ----
Status: Available (was: Assigned)
Making it available for the next trooper. Sorry, didn't have time to look at it during my shift.

Comment 5 by bpastene@chromium.org, Feb 24 2018

Owner: bpastene@chromium.org
Status: Fixed (was: Available)
vm627-m4 had a broken checkout. clobbered it

other failure we're flaky network/DNS requests for gob
►

Sign in to add a comment