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

Issue 862825 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 814480
Owner:
Closed: Jul 12
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

eve : platform_ToolchainOptions failed. Test Libgcc_s Users 1 failures

Project Member Reported by bleung@chromium.org, Jul 11

Issue description

https://luci-milo.appspot.com/buildbot/chromeos/eve-paladin/3632




07/11 15:11:31.521 DEBUG|              test:0410| Test failed due to Test Libgcc_s Users 1 failures. Exception log follows the after_iteration_hooks.
07/11 15:11:31.521 DEBUG|              test:0415| Starting after_iteration_hooks for platform_ToolchainOptions
07/11 15:11:31.522 DEBUG|      base_sysinfo:0124| Loggable saves logs to /usr/local/autotest/results/default/platform_ToolchainOptions/sysinfo/iteration.1/interrupts.after
07/11 15:11:31.522 DEBUG|      base_sysinfo:0124| Loggable saves logs to /usr/local/autotest/results/default/platform_ToolchainOptions/sysinfo/iteration.1/meminfo.after
07/11 15:11:31.522 DEBUG|      base_sysinfo:0124| Loggable saves logs to /usr/local/autotest/results/default/platform_ToolchainOptions/sysinfo/iteration.1/slabinfo.after
07/11 15:11:31.523 DEBUG|      base_sysinfo:0124| Loggable saves logs to /usr/local/autotest/results/default/platform_ToolchainOptions/sysinfo/iteration.1/schedstat.after
07/11 15:11:31.523 DEBUG|             utils:0218| Running 'logger "autotest finished iteration /usr/local/autotest/results/default/platform_ToolchainOptions/sysinfo/iteration.1"'
07/11 15:11:31.527 DEBUG|              test:0420| after_iteration_hooks completed
07/11 15:11:31.527 WARNI|              test:0637| The test failed with the following exception
Traceback (most recent call last):
  File "/usr/local/autotest/common_lib/test.py", line 631, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  File "/usr/local/autotest/common_lib/test.py", line 831, in _call_test_function
    return func(*args, **dargs)
  File "/usr/local/autotest/common_lib/test.py", line 495, in execute
    dargs)
  File "/usr/local/autotest/common_lib/test.py", line 362, in _call_run_once_with_retry
    postprocess_profiled_run, args, dargs)
  File "/usr/local/autotest/common_lib/test.py", line 400, in _call_run_once
    self.run_once(*args, **dargs)
  File "/usr/local/autotest/tests/platform_ToolchainOptions/platform_ToolchainOptions.py", line 324, in run_once
    raise error.TestFail(fail_summary_msg)
TestFail: Test Libgcc_s Users 1 failures
 
216212704-chromeos-test%2Fchromeos6-row4-rack11-host8%2Fplatform_ToolchainOptions%2Fdebug%2Fplatform_ToolchainOptions.txt
13.4 KB View Download
Owner: manojgupta@chromium.org
Status: Assigned (was: Unconfirmed)
Manoj,

Can you help take a look at this failure and see if we can pinpoint what caused the failure?

I'm not sure if it was just in this CQ run, but if it is, you can find the list of CLs here:
https://luci-milo.appspot.com/buildbot/chromeos/eve-paladin/3632
Owner: chirantan@chromium.org
07/11 15:11:31.518 ERROR|platform_Toolchain:0321| Test Libgcc_s Users 1 failures
FAILED:
/usr/bin/9s

Seems to coming from https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/1112870

/usr/bin/9s should be added to the whitelist just like https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/1104304/1
Are we going to have to do this for every new rust binary because that's not going to work at all.

The fact is that rust needs the unwinding functionality from libgcc_s.  From what I can tell there is no equivalent functionality in compiler-rt.

I'd rather just disable that test instead.
Rust can switch to use libunwind instead of libgcc_s.
Mergedinto: 814480
Status: Duplicate (was: Assigned)
I'd rather fix rust to use libunwind.

Sign in to add a comment