New issue
Advanced search Search tips

Issue 882744 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocking:
issue 878698



Sign in to add a comment

bisect-kit: stop collecting crash log to speed up test run

Project Member Reported by kcwu@chromium.org, Sep 11

Issue description

Since 10924.0.0, lots (hundred or more) of crashes during test run due to selinux policy violation.
Many of these crashes are relevant to the test we want running, so the test didn't fail. However, the test framework still analyze and collect crash logs. This takes extra half hours or more time.

This affected bisect duration a lot. Before these crashes resolved, and prevent future similar situation, we should be able to disable crash log collecting. I skim the source code and haven't found command line flag to do so.

 
This slow down is only observed in my test_that run. The test result of official lab run is still fast. I don't know the reason of difference yet.

Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Sign in to add a comment