Open
Bug 1303021
Opened 8 years ago
Updated 2 years ago
Intermittent ASAN-TC gtest | test failed with return code 1 due to "AddressSanitizer failed to allocate 0x10000 (65536) bytes of stack depot (error code: 12)"
Categories
(Testing :: GTest, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: intermittent-bug-filer, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: intermittent-failure)
Filed by: rvandermeulen [at] mozilla.com
https://treeherder.mozilla.org/logviewer.html#?job_id=3552229&repo=mozilla-aurora
https://queue.taskcluster.net/v1/task/HN8j8-VrT8et1MZ78eg68w/runs/1/artifacts/public%2Flogs%2Flive_backing.log
I really have no idea where to put this since it's not clear if it's an issue with how we're configuring our ASAN test slaves on Taskcluster or something else.
Comment 1•8 years ago
|
||
I don't see this on trunk, though. Did we fix this issue there already before they went to Tier 1? Maybe said fix can be backported to 50?
Comment 2•8 years ago
|
||
Joel, is it possible that we changed the instance types these run on at some point between 50 and 51?
Flags: needinfo?(jmaher)
Comment 3•8 years ago
|
||
in irc, aurora is running desktop-test-xlarge, I don't see any changes for trunk branches, it could be in-tree configs or something- we will merge in 2 business days- what is the rush?
Flags: needinfo?(jmaher)
Comment 4•8 years ago
|
||
Presumably they'll still be frequently failing on Beta for the duration of that cycle too...
Comment 5•8 years ago
|
||
It's worth noting that buildbot GTest has been timing out on aurora - bug 1115253.
The TC instance type appears to be c3.xlarge, which seems right to me.
[taskcluster 2016-09-15 12:50:49.593Z] Task ID: HN8j8-VrT8et1MZ78eg68w
[taskcluster 2016-09-15 12:50:49.593Z] Worker ID: i-0b1b2558cb46838dc
[taskcluster 2016-09-15 12:50:49.593Z] Worker Group: us-west-1c
[taskcluster 2016-09-15 12:50:49.593Z] Worker Node Type: c3.xlarge
[taskcluster 2016-09-15 12:50:49.593Z] Worker Type: desktop-test-xlarge
TC and buildbot won't have exactly the same environment of course -- there's the introduction of docker if nothing else -- but everything else is generally behaving, and GTest has been fine on trunk.
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment 9•8 years ago
|
||
According to https://treeherder.mozilla.org/#/jobs?repo=try&revision=7e67649a365cedb0c2c79e575f4d4f37b7fa551d&group_state=expanded&noautoclassify&filter-searchStr=aa0b3558297f2348c36d172446a31d67b580e747 we should expect to see a lot of this again with 51 on beta, like maybe a third this, a third the "timeout" which totally isn't a timeout, it's bug 1303927, and a third green.
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Updated•7 years ago
|
Comment 21•7 years ago
|
||
Oh, that's why I'm suddenly having to star as this on esr, Treeherder removed the annotation that was hiding it.
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Updated•7 years ago
|
Component: General → GTest
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Updated•5 years ago
|
Blocks: asan-maintenance
Comment hidden (Intermittent Failures Robot) |
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•