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

Issue 884152 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jan 9
Cc:
Components:
EstimatedDays: ----
NextAction: 2019-01-09
OS: ----
Pri: 2
Type: Bug-Regression

Blocked on:
issue 863607
issue 886624



Sign in to add a comment

Compile failure on V8's mac gpu fyi bot

Project Member Reported by machenb...@chromium.org, Sep 14

Issue description

Only fails on a particular bot build169-m9, e.g.:
https://ci.chromium.org/p/v8/builders/luci.v8.ci/Mac%20V8%20FYI%20Release%20%28Intel%29/2491


Runs of the same builder on other bots are green.


FAILED: v8_context_snapshot_generator 
export DEVELOPER_DIR=/b/s/w/ir/cache/builder/src/build/mac_files/Xcode.app;  TOOL_VERSION=1534407336 ../../build/toolchain/mac/linker_driver.py ../../third_party/llvm-build/Release+Asserts/bin/clang++  -stdlib=libc++ -arch x86_64 -segprot PROTECTED_MEMORY rw r -Werror -isysroot ../../build/mac_files/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk -mmacosx-version-min=10.9.0 -Wl,-ObjC -L../../build/mac_files/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/lib -o "./v8_context_snapshot_generator" -Wl,-filelist,"./v8_context_snapshot_generator.rsp"  -framework Cocoa -framework Foundation -framework IOKit -framework Security -framework SystemConfiguration -framework CoreFoundation -framework ApplicationServices -framework AppKit -lbsm -framework CFNetwork -framework CoreServices -lresolv -framework CoreGraphics -framework CoreText -framework IOSurface -framework Carbon -framework Accelerate -framework QuartzCore -framework AudioUnit -framework CoreVideo -framework AudioToolbox -framework CoreAudio -framework OpenGL -framework Quartz -framework AVFoundation -framework CoreMedia -framework VideoToolbox -framework DiskArbitration -framework IOBluetooth -lsandbox
Undefined symbols for architecture x86_64:
  "blink::WorkerGlobalScope::EvaluateClassicScript(blink::KURL const&, WTF::String, std::__1::unique_ptr<WTF::Vector<char, 0u, WTF::PartitionAllocator>, std::__1::default_delete<WTF::Vector<char, 0u, WTF::PartitionAllocator> > >)", referenced from:
      vtable for blink::ThreadPoolWorkerGlobalScope in libworkers.a(thread_pool.o)
      vtable for blink::DedicatedWorkerGlobalScope in libworkers.a(dedicated_worker_global_scope.o)


One issue I see is that all the V8 builders have 10.12 installed, while the Chromium builders are on 10.13.
 
I'm trying to drop the bot's builder cache to rule out some corrupt out directory.
Components: Infra
Labels: -Pri-1 Infra-Troopers Pri-2
I tried dropping the cache by removing:
/b/s/c/named/builder_64d636c54ff443a464f82e58b2551478d01a96c1fe31369b967862d55912abe7_v2 on build169-m9. But I don't really know what I'm doing.

Putting this into trooper queue to verify if that's the right way to drop a builder cache on a bot. The builder cache still shows up in the bot's UI:
https://chromium-swarm.appspot.com/bot?id=build169-m9&sort_stats=total%3Adesc
/b/s/c/named/builder_64d636c54ff443a464f82e58b2551478d01a96c1fe31369b967862d55912abe7_v2 is a symlink, you want to delete the destination, not the symlink itself.
Components: -Infra
Labels: -Infra-Troopers
Thanks, will try that in case the bot fails again. So far all runs of the builder were on other bots and stayed green.
Status: Available (was: Untriaged)
Owner: serg...@chromium.org
Status: Assigned (was: Available)
This is most likely caused by https://crbug.com/882635. I'll take the bot off the pool for now.
Project Member

Comment 7 by bugdroid1@chromium.org, Sep 17

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/config/+/aab2657fb2352342b61c0380ef1d346e0cfd7da5

commit aab2657fb2352342b61c0380ef1d346e0cfd7da5
Author: Sergiy Byelozyorov <sergiyb@google.com>
Date: Mon Sep 17 05:52:09 2018

But in the revision you refer to it's a different bot.

Note that this failed again https://ci.chromium.org/p/v8/builders/luci.v8.ci/Mac%20V8%20FYI%20Release%20(Intel)/2523 - but probably before you took it off the pool.
Project Member

Comment 9 by bugdroid1@chromium.org, Sep 18

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/config/+/0c483efa67f28c3a1b776f96e35f64e05563b094

commit 0c483efa67f28c3a1b776f96e35f64e05563b094
Author: Sergiy Byelozyorov <sergiyb@google.com>
Date: Tue Sep 18 11:15:01 2018

As discussed, the CL above removed the wrong bot from the pool.

This time I'm going to remove the right builder cache from the bot for real...
Owner: machenb...@chromium.org
Cc: serg...@chromium.org
So this was after I purged the builder cache:
https://ci.chromium.org/p/v8/builders/luci.v8.ci/Mac%20V8%20FYI%20Release%20%28Intel%29/2515

Looks like a full rebuild running into the same problem. Something seems different on that particular bot. Lets maybe take it out of the pool and reimage it? Sergiy, any opinion?
SGTM. Should we upgrade it to Mac OS 10.13.6 at the same time? If the bot works well, we can then ask others to be reimaged as well.
Sure, and I assume it should not have xcode installed, right?
No. XCode is not required anymore. It's  deployed via CIPD during the task execution.
Project Member

Comment 16 by bugdroid1@chromium.org, Sep 19

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/config/+/731a34751ed7c0e7d53ce68735dc569104507fe4

commit 731a34751ed7c0e7d53ce68735dc569104507fe4
Author: Michael Achenbach <machenbach@chromium.org>
Date: Wed Sep 19 11:04:57 2018

Blockedon: 886624
Blockedon: 863607
The bot is ready with 10.13 and without xcode. But I'll wait adding it until  issue 863607  is resolved as it otherwise might interfere with V8 stand-alone builders.
Have this been resolved? If so, then perhaps we can return build169-m9 back to the pool?
Project Member

Comment 20 by bugdroid1@chromium.org, Dec 12

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/config/+/ebb0f7f5240e139b0ad4efec539a27cb7aadcd5e

commit ebb0f7f5240e139b0ad4efec539a27cb7aadcd5e
Author: Michael Achenbach <machenbach@google.com>
Date: Wed Dec 12 07:50:33 2018

NextAction: 2019-01-09
Lets check in a few weeks if no new errors occurred and then close this.
The NextAction date has arrived: 2019-01-09
Status: Fixed (was: Assigned)
No new errors in the last weeks.

Sign in to add a comment