mac_chromium_archive_rel_ng trybot fails sizes check |
|||||||
Issue descriptionThe trybot fails sizes step: https://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_archive_rel_ng/builds/36 /System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python /b/build/slave/mac_chromium_archive_rel_ng/build/src/infra/scripts/legacy/scripts/slave/chromium/sizes.py --json /tmp/tmpbp10qZ error: unable to open executable '/b/build/slave/mac_chromium_archive_rel_ng/build/src/out/Release/Chromium Framework.framework.dSYM/Contents/Resources/DWARF/Chromium Framework' I guess it needs to build some other target(s) in order to produce that build artifact? The clobber bot running sizes happily passes: https://build.chromium.org/p/chromium/builders/Mac/builds/15536 We use this trybot to avoid rolling in static initializers for WebRTC, so it would be nice to get it fixed. It's not critical though, since Linux coverage is probably sufficient.
,
May 17 2016
The distinction appears to be that the mac_chromium_archive_rel_ng bot is passing "fastbuild=1 dcheck_always_on=1" in the generate_build_files step, whereas the Mac builder just passes "mac_strip_release=1". My guess would be that fixing that will resolve the problem. In particular, the set of compile targets and the set of test targets that each build (from the "get compile targets for scripts" and "read test spec" steps) are identical. Of course, I don't really understand the compile process myself. If that doesn't fix it, I have no idea what would. Since it appears that pawel added this bot, adding him to the bug.
,
May 18 2016
Could this problem simply be caused by the fact that the VM was out of disk? See bug 611004.
,
May 18 2016
,
May 18 2016
Seems likely. Marking blocked on that bug.
,
Jan 18 2017
Stale, dropping priority.
,
Apr 13 2018
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
,
May 4 2018
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by pgervais@chromium.org
, May 17 2016Owner: ----
Status: Untriaged (was: Assigned)