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

Issue 671917 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Failed shell on Win64 for official.desktop builder for build# 57.0.2944.0

Project Member Reported by ranjitkan@chromium.org, Dec 7 2016

Issue description

Link to Build:
==============
https://uberchromegw.corp.google.com/i/official.desktop/builders/win64/builds/1313

Link to Log:
============
https://uberchromegw.corp.google.com/i/official.desktop/builders/win64/builds/1313/steps/shell/logs/stdio

Error Log:
==========
Traceback (most recent call last):
  File "build_internal\scripts\slave-internal\official_upload.py", line 443, in <module>
    sys.exit(main())
  File "build_internal\scripts\slave-internal\official_upload.py", line 435, in main
    options.allow_missing)
  File "build_internal\scripts\slave-internal\official_upload.py", line 268, in CollectFiles
    allow_missing)
  File "C:\b\build\slave\win64\build\build_internal\scripts\slave-internal\official_utils.py", line 26, in CreateCleanArchive
    allow_missing=missing)
  File "C:\b\build\scripts\common\archive_utils.py", line 325, in CreateArchive
    raise_error=not allow_missing)
  File "C:\b\build\scripts\common\chromium_utils.py", line 681, in MakeZip
    CopyFileToDir(src_path, archive_dir, basename, link_ok=True)
  File "C:\b\build\scripts\common\chromium_utils.py", line 587, in CopyFileToDir
    raise PathNotFound('Unable to find file %s' % src_path)
common.chromium_utils.PathNotFound: Unable to find file C:\b\build\slave\win64\build\src\out\Release_x64\gcp_portmon.dll

@sebmarchand: Request you to please take a look into it.
 
Cc: dimu@chromium.org sebmarchand@chromium.org mmoss@chromium.org
Owner: pastarmovj@chromium.org
This is because gcp_portmon has been added to FILES.cfg (in https://chromium.googlesource.com/chromium/src/+/b91e752ebb2677f75c22a32e668059ec99cfd7ac), but it doesn't get build when doing an official build because it's not in the dependency tree of the 'chrome_official_builder_no_unittests' GN target (https://cs.chromium.org/chromium/src/BUILD.gn?l=112)
Just to update, same failure observed on build 57.0.2945.0

Link to Build:
==============
https://uberchromegw.corp.google.com/i/official.desktop/builders/win64/builds/1316

Link to Log:
============
https://uberchromegw.corp.google.com/i/official.desktop/builders/win64/builds/1316/steps/shell/logs/stdio

Thanks.!
Status: Started (was: Assigned)
I will fix this today. Thanks for letting me know.
Project Member

Comment 4 by bugdroid1@chromium.org, Dec 8 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ae3050e85ea1680090ff2aee26d6f0beef4b8770

commit ae3050e85ea1680090ff2aee26d6f0beef4b8770
Author: pastarmovj <pastarmovj@chromium.org>
Date: Thu Dec 08 15:13:00 2016

Add cloud print to the chrome_official_builder_no_unittests group.

BUG= 671917 
TEST=The official.desktop builder doesn't fail anymore.

Review-Url: https://codereview.chromium.org/2558973004
Cr-Commit-Position: refs/heads/master@{#437245}

[modify] https://crrev.com/ae3050e85ea1680090ff2aee26d6f0beef4b8770/BUILD.gn

Status: Fixed (was: Started)
I added cloud_print to the set of deps for the official build. I hope this should have fixed it.
Status: Verified (was: Fixed)
Latest build (1317) is compiled successfully.closing the issue.

https://uberchromegw.corp.google.com/i/official.desktop/builders/win64/builds/1317

Thank you.

Status: Assigned (was: Verified)
Failed shell on win64 for official.desktop on latest build (1318). reopening the issue.

Link to Build:
==============
https://uberchromegw.corp.google.com/i/official.desktop/builders/win64/builds/1318

Link to Log:
============
https://uberchromegw.corp.google.com/i/official.desktop/builders/win64/builds/1318/steps/shell/logs/stdio


Cc: flackr@chromium.org treib@chromium.org cda...@chromium.org kuan@chromium.org
Summary: [Flaky] Failed shell on Win64 for official.desktop builder for build# 57.0.2944.0 (was: Failed shell on Win64 for official.desktop builder for build# 57.0.2944.0)
Looks like alternative builds are failing. Making it as Flaky and adding the sheriffs.
Thanks

Comment 9 by mmoss@chromium.org, Dec 8 2016

Summary: Failed shell on Win64 for official.desktop builder for build# 57.0.2944.0 (was: [Flaky] Failed shell on Win64 for official.desktop builder for build# 57.0.2944.0)
It's not flaky, it's just that it's only failing on M57.

And that most recent failure should be expected, since the fix just landed a few hours ago, and on trunk, whereas build 1318 was for a branch (2944) from a couple days ago. If the fix is needed on that branch, it will have to be merged, otherwise the next nightly build (2946 branch) should have it.
Is there anything you need me to do or just wait until we don't build the affected versions anymore?
Status: Verified (was: Assigned)
Latest M57 57.0.2946.0 Win 64 build compiled successfully.

Build URL:
==========
https://uberchromegw.corp.google.com/i/official.desktop/builders/win64/builds/1321

Marking it as Verified.

Thanks.!

Sign in to add a comment