If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Unhide ASan gtests on release branches if they ever have a reasonable failure percentage

NEW
Unassigned

Status

Tree Management
Visibility Requests
10 months ago
10 months ago

People

(Reporter: philor, Unassigned)

Tracking

(Depends on: 2 bugs)

Details

Comment hidden (empty)
FWIW, the buildbot-based jobs had to run on a different instance from the other ASAN tests as well (Ubuntu ASAN VM large 12.04 x64 opt test gtest). Greg, can you help find an owner for this?
Flags: needinfo?(garndt)
(Reporter)

Comment 2

10 months ago
If exclusions weren't such a pain to edit I would have included buildbot too, since it has failed 6 of the last 10 runs on mozilla-release (the last one where it's still running) from bug 1303927.

Comment 3

10 months ago
So it sounds like the ASAN gtests must run on a different instance type....do we know if that's the cause of the failures here for TaskCluster? Looping Joel in in case he has any idea as I do not know much about these tests.
Flags: needinfo?(garndt) → needinfo?(jmaher)
given that these are hidden on treeherder for all branches for both buildbot/taskcluster, we should question the value of having these around- adding :decoder, :mccr8, :chmanchester as they are interested parties
Flags: needinfo?(jmaher)
I'm not familiar with gtests, so I don't know how useful it is to run them in ASan.
gtests are C++ unit tests. Running them under ASan sounds like a reasonable and desirable thing to do.
You need to log in before you can comment on or make changes to this bug.