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

Issue 770719 link

Starred by 1 user
Status: Fixed
Owner:
█ kateso...@chromium.org
Last visit > 30 days ago
Closed: Dec 2017
Cc:
mbarbe...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 0
Type: Bug

Blocking:
issue 765834



Sign in to add a comment

Ensure that Predator can handle CHECK failures for all build types (e.g. MSan)

Project Member Reported by infe...@chromium.org, Oct 2 2017

Comment 1 by mbarbe...@chromium.org, Oct 31 2017

Status: Fixed (was: Assigned)
Still not finding a result, but if the issue was an exception or failure to parse the stack that at least seems to be fixed now.

Comment 2 by infe...@chromium.org, Oct 31 2017

Cc: mbarbe...@chromium.org
Status: Assigned (was: Fixed)
Actually this means that we just can't process check failures with non-asan stack, that is bad, reopening.

Comment 3 by mbarbe...@chromium.org, Oct 31 2017

Cc: kateso...@chromium.org
Owner: ----
Status: Untriaged (was: Assigned)
Summary: Ensure that Predator can handle CHECK failures for all build types (e.g. MSan) (was: MSAN stack, failed to parse stacktrace)
We should be able to, but let's discuss this later. Bumping back to untriaged to make this easier to find.

Comment 4 by mbarbe...@chromium.org, Oct 31 2017

Cc: -kateso...@chromium.org
Owner: kateso...@chromium.org
Status: Assigned (was: Untriaged)

Comment 5 by infe...@chromium.org, Dec 12 2017

Labels: -Pri-1 Pri-0

Comment 6 by infe...@chromium.org, Dec 12 2017

Status: Fixed (was: Assigned)
►

Sign in to add a comment