Reland "tracing: Address TracingControllerAndroid test failures."
This is a reland of 2fc9f6f2 The crashes in flakiness were due to calling destroy() on the wrong thread, which has been addressed in the new patch set. Original change's description: > tracing: Address TracingControllerAndroid test failures. > > Fixes the flakiness of buffer usage / known categories tests by > resolving an accidental race condition. Also restricts disabling > the other two tests to <= kitkat devices since those seem to be > the only ones that show (inexplicable) flakiness. > > TBR=yfriedman@chromium.org > > Bug: 899894 > Change-Id: I0225c1519ea19910492ffb60a242bcc71b2275b4 > Reviewed-on: https://chromium-review.googlesource.com/c/1307433 > Reviewed-by: Eric Seckler <eseckler@chromium.org> > Commit-Queue: Eric Seckler <eseckler@chromium.org> > Cr-Commit-Position: refs/heads/master@{#604209} Bug: 899894 Change-Id: I3cb002950f32bc6b6b4d25892adc3073c2fdb967 Reviewed-on: https://chromium-review.googlesource.com/c/1327407Reviewed-by:Sami Kyöstilä <skyostil@chromium.org> Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Commit-Queue: Eric Seckler <eseckler@chromium.org> Cr-Commit-Position: refs/heads/master@{#606570}
Showing
Please register or sign in to comment