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

Issue 633004 link

Starred by 3 users
Status: Fixed
Owner:
█ aizatsky@chromium.org
Last visit > 30 days ago
Closed: Aug 2016
Cc:
kcc@chromium.org
mbarbe...@chromium.org
thakis@chromium.org
█ euge...@chromium.org
█ glider@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocking:
issue 616183



Sign in to add a comment

Sanitizer coverage files failing to get written on Mac

Project Member Reported by infe...@chromium.org, Jul 31 2016 
We recently enabled sanitizer edge coverage on mac bots (after they were scaled from 20 to 120 bots). I see these errors in the report and coverage sancov file is not written to disk, is there some issue with writing paths with spaces ?

==55696==SanitizerCoverage: failed to open /b/tmp/Chromium Helper.55696.sancov for writing (reason: 1)
==55696==SanitizerCoverage: failed to open /b/tmp/Chromium Framework.55696.sancov for writing (reason: 1)
Received signal 6
 [0x000293d0001a]
....
 [0x00000000001d]
[end of stack trace]

Comment 1 by kcc@chromium.org, Aug 2 2016

Cc: kcc@chromium.org
Owner: aizatsky@chromium.org

Comment 2 by infe...@chromium.org, Aug 8 2016

Cc: thakis@chromium.org
Status: Fixed (was: Assigned)
This has started working just rcently and i can see .sancov files created, i have no clue what fixed it though. this started working before the clang roll that Nico did today.
►

Sign in to add a comment