New issue
Advanced search Search tips

Issue 814645 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

"postprocess_for_goma" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Feb 22 2018

Issue description

"postprocess_for_goma" 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 14 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRwb3N0cHJvY2Vzc19mb3JfZ29tYQw.

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 793833 .
 
Owner: sergeybe...@chromium.org
Status: Assigned (was: Untriaged)
https://logs.chromium.org/v/?s=chromium%2Fbb%2Ftryserver.chromium.linux%2Ffuchsia_arm64%2F62963%2F%2B%2Frecipes%2Fsteps%2Fpostprocess_for_goma%2F0%2Fsteps%2Fupload_log%2F0%2Fstdout

reason: failed to resolve package "infra/python/wheels/infra_libs-py2" at version "version:1.2.0"

Something is misconfigured?
And indeed:

$ cipd describe infra/python/wheels/infra_libs-py2 -version version:1.3.0
Package:       infra/python/wheels/infra_libs-py2
Instance ID:   2332667c66a20cb0b7af3a5987d25ea6b77d920e
Registered by: user:katthomas@google.com
Registered at: 2018-02-13 10:45:16.33152 -0800 PST
Refs:          none
Tags:
  git_revision:ef7582ab2bd1c43cd1c3792f1b5364ec76ba298e
  version:1.3.0

$ cipd describe infra/python/wheels/infra_libs-py2 -version version:1.2.0
Error: package "infra/python/wheels/infra_libs-py2" doesn't have instance with version "version:1.2.0".

This is odd... Why would the old package disappear?
It seems the dockerbuild was broken in infra.git and didn't upload 1.2.0 version to CIPD. It was fixed in https://crrev.com/c/916735 together with bumping the infra_libs version.
Project Member

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

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build/+/51f68eaea1b25e0a8bb5a29f70bc3ea0521560c6

commit 51f68eaea1b25e0a8bb5a29f70bc3ea0521560c6
Author: Sergey Berezin <sergeyberezin@google.com>
Date: Fri Feb 23 00:58:29 2018

upload_goma_logs: Fix infra_libs version

BUG= 814645 
TBR=yyanagisawa@chromium.org

Change-Id: I2c35c5df7bd8fd245a9b84ac71b5b74086a0cd19
Reviewed-on: https://chromium-review.googlesource.com/933373
Reviewed-by: Sergey Berezin <sergeyberezin@chromium.org>
Commit-Queue: Sergey Berezin <sergeyberezin@chromium.org>

[modify] https://crrev.com/51f68eaea1b25e0a8bb5a29f70bc3ea0521560c6/scripts/slave/upload_goma_logs.py.vpython

Status: Fixed (was: Assigned)
Re: #2
FYI, there were two upload_goma_logs.py breakage behind.

One was a cl that uploads counterz from upload_goma_logs.py could not find the counterz file, due to goma client timing issue (https://chromium-review.googlesource.com/c/chromium/tools/build/+/897219)

The other was submission of the cl that enforce use of vpython from runit.py (https://bugs.chromium.org/p/chromium/issues/detail?id=814607).  As you noticed, libraries listed in .vpython did not match what is is now.

Sign in to add a comment