New issue
Advanced search Search tips

Issue 866537 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
dats@chromium.org
chromeos-continuous-integration-fire-hose@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

EXPECT_DEATH reports SIGABRT as a test failure

Project Member Reported by la...@chromium.org, Jul 23 
If a builder happens to be running an EXPECT_DEATH unit test when a slave aborts for some reason (no longer needed by master), the EXPECT_DEATH will report the aborting SIGABRT as a test failure. This can cause confusion and bad annotation/blame.

Comment 1 by vapier@chromium.org, Jul 23 

i'm not sure there's anything feasible we could do with gtest or related testing frameworks.  if we're going to forcibly abort a slave, once we start down that path, we prob need a knob that says "ignore any results after this point in time".
►

Sign in to add a comment