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

Issue 843132 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

crosvm unit tests fail on amd64-generic-tot-asan-informational with "undefined symbol: __asan_option_detect_stack_use_after_return"

Project Member Reported by derat@chromium.org, May 15 2018

Issue description

The crosvm unit tests are failing repeatedly in the UnitTest stage of amd64-generic-tot-asan-informational. See e.g.

http://cros-goldeneye/chromeos/healthmonitoring/buildDetails?id=2572280
http://cros-goldeneye/chromeos/healthmonitoring/buildDetails?buildbucketId=8946471934661024800

=== Start output for job crosvm-0.0.1-r128 (1m43.8s) ===
crosvm-0.0.1-r128: >>> Emerging (1 of 1) chromeos-base/crosvm-0.0.1-r128::chromiumos for /build/amd64-generic/
crosvm-0.0.1-r128:  * bitflags-1.0.1.crate SHA256 SHA512 WHIRLPOOL size ;-) ...             [ ok ]
crosvm-0.0.1-r128:  * byteorder-1.1.0.crate SHA256 SHA512 WHIRLPOOL size ;-) ...            [ ok ]
crosvm-0.0.1-r128:  * cfg-if-0.1.2.crate SHA256 SHA512 WHIRLPOOL size ;-) ...               [ ok ]
crosvm-0.0.1-r128:  * fuchsia-zircon-0.3.3.crate SHA256 SHA512 WHIRLPOOL size ;-) ...       [ ok ]
...
crosvm-0.0.1-r128: test virtio::vhost::net::tests::create_net ... ok
crosvm-0.0.1-r128: test virtio::vhost::net::tests::features ... ok
crosvm-0.0.1-r128: test virtio::vhost::net::tests::keep_fds ... ok
crosvm-0.0.1-r128: test virtio::vhost::vsock::tests::ack_features ... ok
crosvm-0.0.1-r128: test virtio::vhost::vsock::tests::features ... ok
crosvm-0.0.1-r128: test virtio::vhost::vsock::tests::read_config ... ok
crosvm-0.0.1-r128: 
crosvm-0.0.1-r128: test result: ok. 14 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
crosvm-0.0.1-r128: 
crosvm-0.0.1-r128:      Running `/build/amd64-generic/tmp/portage/chromeos-base/crosvm-0.0.1-r128/work/x86_64-cros-linux-gnu/debug/deps/gpu_buffer-f79b211d1e3cb3ff --test-threads=1`
crosvm-0.0.1-r128: /build/amd64-generic/tmp/portage/chromeos-base/crosvm-0.0.1-r128/work/x86_64-cros-linux-gnu/debug/deps/gpu_buffer-f79b211d1e3cb3ff: symbol lookup error: /build/amd64-generic/usr/lib64/libgbm.so.1: undefined symbol: __asan_option_detect_stack_use_after_return
crosvm-0.0.1-r128: error: test failed, to rerun pass '--lib'
crosvm-0.0.1-r128:  * ERROR: chromeos-base/crosvm-0.0.1-r128::chromiumos failed (test phase):
crosvm-0.0.1-r128:  *   cargo test failed
crosvm-0.0.1-r128:  * 
crosvm-0.0.1-r128:  * Call stack:
crosvm-0.0.1-r128:  *     ebuild.sh, line 133:  Called src_test
crosvm-0.0.1-r128:  *   environment, line 4003:  Called die
crosvm-0.0.1-r128:  * The specific snippet of code:
crosvm-0.0.1-r128:  *           cargo test --all --exclude kvm --exclude kvm_sys --exclude net_util -v --exclude qcow --exclude aarch64 --target="${CHOST}" -- --test-threads=1 || die "cargo test failed";
 

Comment 1 by derat@chromium.org, May 16 2018

Cc: mtyin@chromium.org dgreid@chromium.org seanpaul@chromium.org za...@chromium.org
Owner: dgreid@chromium.org
This is continuing to fail. See e.g. http://cros-goldeneye/chromeos/healthmonitoring/buildDetails?buildbucketId=8946386930884402416.

Comment 2 by za...@chromium.org, May 16 2018

We have a potential fix: https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/1060522 but it got kicked out the CQ last night. I'm trying to push it again right now.

Comment 3 by derat@chromium.org, May 16 2018

Owner: za...@chromium.org
Status: Started (was: Assigned)
Thanks!

Comment 4 by za...@chromium.org, May 17 2018

Status: Fixed (was: Started)
The fix landed. Re-open if you are still having issues.

Sign in to add a comment