Issue metadata
Sign in to add a comment
|
Compile failure on precise64 for official (57.0.2987.56) desktop builder |
||||||||||||||||||||
Issue descriptionLink to Builder: ================ https://uberchromegw.corp.google.com/i/official.desktop/builders/precise64/builds/1517 Link to Log File: ================= https://uberchromegw.corp.google.com/i/official.desktop/builders/precise64/builds/1517/steps/compile/logs/stdio Error from the Log: =================== FAILED: v8_simple_wasm_function_sigs_section_fuzzer ../../third_party/llvm-build/Release+Asserts/bin/clang++ -pie -Wl,--fatal-warnings -fPIC -Wl,-z,noexecstack -Wl,-z,now -Wl,-z,relro -Wl,-z,defs -Wl,--no-as-needed -lpthread -Wl,--as-needed -fuse-ld=gold -B../../third_party/binutils/Linux_x64/Release/bin -Wl,--threads -Wl,--thread-count=4 -Wl,--icf=all -flto -fwhole-program-vtables -Wl,-plugin-opt,O1 -Wl,-plugin-opt,-function-sections -m64 -pthread --sysroot=../../build/linux/debian_wheezy_amd64-sysroot -L/b/build/slave/precise64/build/src/build/linux/debian_wheezy_amd64-sysroot/lib/x86_64-linux-gnu -Wl,-rpath-link=/b/build/slave/precise64/build/src/build/linux/debian_wheezy_amd64-sysroot/lib/x86_64-linux-gnu -L/b/build/slave/precise64/build/src/build/linux/debian_wheezy_amd64-sysroot/usr/lib/x86_64-linux-gnu -Wl,-rpath-link=/b/build/slave/precise64/build/src/build/linux/debian_wheezy_amd64-sysroot/usr/lib/x86_64-linux-gnu -L/b/build/slave/precise64/build/src/build/linux/debian_wheezy_amd64-sysroot/usr/lib/gcc/x86_64-linux-gnu/4.6 -Wl,-rpath-link=/b/build/slave/precise64/build/src/build/linux/debian_wheezy_amd64-sysroot/usr/lib/gcc/x86_64-linux-gnu/4.6 -L/b/build/slave/precise64/build/src/build/linux/debian_wheezy_amd64-sysroot/usr/lib -Wl,-rpath-link=/b/build/slave/precise64/build/src/build/linux/debian_wheezy_amd64-sysroot/usr/lib -fsanitize=cfi-vcall -Wl,-rpath-link=. -Wl,--disable-new-dtags -Werror -Wl,-O1 -Wl,--gc-sections -o "./v8_simple_wasm_function_sigs_section_fuzzer" -Wl,--start-group @"./v8_simple_wasm_function_sigs_section_fuzzer.rsp" -Wl,--end-group -ldl -lrt clang: error: unable to execute command: Segmentation fault clang: error: linker command failed due to signal (use -v to see invocation) [46681/46703] LINK ./v8_parser_shell [46682/46703] LINK ./v8_simple_wasm_fuzzer [46683/46703] LINK ./v8_hello_world [46684/46703] LINK ./webkit_unit_tests tcmalloc: large alloc 1073741824 bytes == 0x1b5a2e000 @ tcmalloc: large alloc 2147483648 bytes == 0x34fe5c000 @ tcmalloc: large alloc 1610612736 bytes == 0x6ca974000 @ [46685/46703] LINK ./views_examples_with_content_exe tcmalloc: large alloc 1073741824 bytes == 0x1b0e84000 @ tcmalloc: large alloc 1610612736 bytes == 0x7084d6000 @ [46686/46703] LINK ./interactive_ui_tests tcmalloc: large alloc 1073741824 bytes == 0x1b349c000 @ tcmalloc: large alloc 2147483648 bytes == 0x34d008000 @ tcmalloc: large alloc 2013265920 bytes == 0x98868c000 @ tcmalloc: large alloc 1610612736 bytes == 0xa9968c000 @ tcmalloc: large alloc 3221225472 bytes == 0xaf968c000 @ [46687/46703] LINK ./browser_tests tcmalloc: large alloc 1073741824 bytes == 0x1c0ea6000 @ tcmalloc: large alloc 2147483648 bytes == 0x355daa000 @ tcmalloc: large alloc 2013265920 bytes == 0xa5dbe6000 @ tcmalloc: large alloc 1610612736 bytes == 0xb7fc6a000 @ tcmalloc: large alloc 3221225472 bytes == 0xbdfc6a000 @ ninja: build stopped: subcommand failed. /b/build/scripts/slave/gsutil cp file:///tmp/tmp6LDpVT gs://chrome-goma-log/2017/02/16/lin64-2-m0/ninja_log.lin64-2-m0.chrome-bot.20170215-203046.41036.gz Copying file:///tmp/tmp6LDpVT [Content-Type=application/octet-stream]... Uploading ...g.lin64-2-m0.chrome-bot.20170215-203046.41036.gz: 0 B/1.18 MiB Uploading ...g.lin64-2-m0.chrome-bot.20170215-203046.41036.gz: 72 KiB/1.18 MiB Uploading ...g.lin64-2-m0.chrome-bot.20170215-203046.41036.gz: 144 KiB/1.18 MiB Uploading ...g.lin64-2-m0.chrome-bot.20170215-203046.41036.gz: 216 KiB/1.18 MiB Uploading ...g.lin64-2-m0.chrome-bot.20170215-203046.41036.gz: 288 KiB/1.18 MiB Uploading ...g.lin64-2-m0.chrome-bot.20170215-203046.41036.gz: 360 KiB/1.18 MiB Uploading ...g.lin64-2-m0.chrome-bot.20170215-203046.41036.gz: 432 KiB/1.18 MiB Uploading ...g.lin64-2-m0.chrome-bot.20170215-203046.41036.gz: 504 KiB/1.18 MiB Uploading ...g.lin64-2-m0.chrome-bot.20170215-203046.41036.gz: 576 KiB/1.18 MiB Uploading ...g.lin64-2-m0.chrome-bot.20170215-203046.41036.gz: 648 KiB/1.18 MiB Uploading ...g.lin64-2-m0.chrome-bot.20170215-203046.41036.gz: 720 KiB/1.18 MiB Uploading ...g.lin64-2-m0.chrome-bot.20170215-203046.41036.gz: 792 KiB/1.18 MiB Uploading ...g.lin64-2-m0.chrome-bot.20170215-203046.41036.gz: 928 KiB/1.18 MiB Uploading ...g.lin64-2-m0.chrome-bot.20170215-203046.41036.gz: 1.04 MiB/1.18 MiB Uploading ...g.lin64-2-m0.chrome-bot.20170215-203046.41036.gz: 1.17 MiB/1.18 MiB Uploading ...g.lin64-2-m0.chrome-bot.20170215-203046.41036.gz: 1.18 MiB/1.18 MiB Copied log file to gs://chrome-goma-log/2017/02/16/lin64-2-m0/ninja_log.lin64-2-m0.chrome-bot.20170215-203046.41036.gz Visualization at http://chromium-build-stats.appspot.com/ninja_log/2017/02/16/lin64-2-m0/ninja_log.lin64-2-m0.chrome-bot.20170215-203046.41036.gz program finished with exit code 1 CL: https://chromium.googlesource.com/chromium/src/+log/57.0.2987.54..57.0.2987.56?pretty=fuller&n=10000 Unable to identify a possible culprit from the CL @sebmarchand: Assigning to you, kindly help us to triage this issue. Thanks.!
,
Feb 16 2017
Assigning to today sheriff jaydasika@ for further triage.
,
Feb 16 2017
The compile failure isn't happening anymore. It is failing some tests but that's being tracked in crbug.com/682505 already.
,
Feb 16 2017
Passed builds are M58. this is official M57 build so reopening the issue for traiging. please correct me if i am wrong. Thank you.
,
Feb 16 2017
Looked at the blamelist and can't figure out where the segmentation fault is coming from. Assigning it to v8 continuous delivery sheriff for better triage.
,
Feb 16 2017
machenbach@ is in different timezone. today 6.00 PM beta build will fail. could someone please take a look?. Thank you.
,
Feb 16 2017
,
Feb 17 2017
I have a bit trouble finding out when this builder is building what. Is this the first attempt to build M57 as beta or were there successful ones before that?
,
Feb 17 2017
Note that this is an internal compiler error (segfault in clang). This should have been looked at by a trooper.
,
Feb 17 2017
The last good 57 build I could find on this builder is: https://uberchromegw.corp.google.com/i/official.desktop/builders/precise64/builds/1514 It builds: https://chrome-internal.googlesource.com/chrome/tools/buildspec/+/c0a52364fadfbbf9b64d05095b5ec6a52fb58076 This had V8 version: https://chromium.googlesource.com/v8/v8/+/de19c70764b07973337a585d6ec45f4bba52bb75 From the first failing we get a V8 range of: https://chromium.googlesource.com/v8/v8/+log/de19c70764..971cd518c1b102a Both changes look absolutely innocent.
,
Feb 17 2017
,
Feb 17 2017
A more important question: Why are these bots building the All target? That's not what we deliver and includes a lot of unnecessary test targets. In one of those the linker crashes now: v8_simple_wasm_function_sigs_section_fuzzer. This is a V8 smoke test target. I could warm up a simplified version of https://codereview.chromium.org/2619743002/ to exclude those targets. But on that CL and the referenced bug we agreed on the callers to decide which targets to build.
,
Feb 17 2017
Correct me if I'm wrong, but it looks like the latest M57 build passed: https://uberchromegw.corp.google.com/i/official.desktop/builders/precise64/builds/1522 I contains V8 version: https://chromium.googlesource.com/v8/v8/+log/f92b614457ae4e The only change that did something with impact since the failing build was: https://chromium.googlesource.com/v8/v8/+/85a9cf4c17200e90b5 Either it fixed the issue or the problem was unrelated. Assigning back to reporter to decide for further actions. I suggest the official bots should build a specific target that only includes what's necessary - to not be hit by such things.
,
Feb 17 2017
Latest official M57 Linux build compiled successfully - https://uberchromegw.corp.google.com/i/official.desktop/builders/precise64/builds/1522. Hence removing "RBB" label. +dimu@, ptal comment #13. Thank you.
,
Feb 23 2017
Latest M57 builds are passed or compiled successfully. Unassigning myself and leaving the issue untriaged.
,
Feb 23 2017
(Linker crashes or wrong build targets aren't trooper issues, removing the label).
,
Feb 27 2017
Closing as per #13, #14, and #15 |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ranjitkan@chromium.org
, Feb 16 2017