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

Issue 729562 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Feb 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocked on:
issue 729894


Participants' hotlists:
PGO-bugs


Sign in to add a comment

PGO build failures

Project Member Reported by sebmarchand@chromium.org, Jun 5 2017

Issue description

The PGO bots have been quite flaky recently, there's different cause for failure:
- During instrumentation or optimization step: fatal error LNK1181: cannot open input file 'libEGL.dll.lib' [1]: This is probably due to an invalid dependency?
- During the 'merge PGC files step': PGOMGR : fatal error PG0166: Missing or invalid stream 'value/''_ltcg_' in 'C:\b\build\slave\chromium-win-x64-pgo-builder\build\src\out\Release_x64\chrome_child.pgd'. [2] -> No idea what could cause this.
- During optimization step: No profile data was merged into './chrome_child.pgd', profile-guided optimizations disabled : Because all the profiling benchmarks failed.

[1] https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.fyi%2FChromium_Win_x64_PGO_Builder%2F19994%2F%2B%2Frecipes%2Fsteps%2FCompile%3A_Instrumentation_phase.%2F0%2Fstdout
[2] https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.fyi%2FChromium_Win_PGO_Builder%2F8979%2F%2B%2Frecipes%2Fsteps%2FMerge_the_pgc_files_for_chrome_child.%2F0%2Fstdout
[3] https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.fyi%2FChromium_Win_PGO_Builder%2F8967%2F%2B%2Frecipes%2Fsteps%2FCompile%3A_Optimization_phase.%2F0%2Fstdout

 
Owner: sebmarchand@chromium.org
Status: Assigned (was: Untriaged)
Blockedon: 729894
Update on this:
- libEGL.dll.lib issue: Haven't seen this for a while, the problem might have been fixed in Chrome?
- 'merge PGC files step': Should be fixed now (with https://chromium-review.googlesource.com/c/528354/)
- The issue with Telemetry not running any benchmark, it looks like a timeout issue, https://codereview.chromium.org/2932063003/ should fix this.
Project Member

Comment 4 by bugdroid1@chromium.org, Jun 9 2017

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

commit 81faa4757dd1858df5de62a3cc52eecc3d41c519
Author: catapult-deps-roller@chromium.org <catapult-deps-roller@chromium.org>
Date: Fri Jun 09 17:31:01 2017

Roll src/third_party/catapult/ 93941b45f..1ffc3ed05 (1 commit)

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/93941b45f0e4..1ffc3ed05267

$ git log 93941b45f..1ffc3ed05 --date=short --no-merges --format='%ad %ae %s'
2017-06-09 sebmarchand Augment the browser startup timeout when using the PGO profiler.

Created with:
  roll-dep src/third_party/catapult
BUG= 729562 


Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls


CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=sullivan@chromium.org

Change-Id: I1ea00a37fbcecae567bd13e04cd648030455298c
Reviewed-on: https://chromium-review.googlesource.com/528939
Reviewed-by: <catapult-deps-roller@chromium.org>
Commit-Queue: <catapult-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#478320}
[modify] https://crrev.com/81faa4757dd1858df5de62a3cc52eecc3d41c519/DEPS

Issue 734519 has been merged into this issue.
This failure is observed on recipes for build 60.0.3112.65 on official desktop builder.

Build URL:
==========
https://uberchromegw.corp.google.com/i/official.desktop/builders/win-recipes/builds/167

Thanks.!
Just to update, Win 32 PGO build # 62.0.3188.2 failed with same error log.

Build URL:
==========
https://uberchromegw.corp.google.com/i/official.desktop/builders/win-pgo/builds/1489
Lowering the priority of the PGO bugs as we've switched the official build to Clang. I'll close these bugs once we decide that we won't support the VS build anymore.
Status: WontFix (was: Assigned)
WontFix'ing this issue as the switch to Clang make it obsolete.

Sign in to add a comment