Skip to content

Conversation

@zcbenz
Copy link
Contributor

@zcbenz zcbenz commented Oct 13, 2021

Description of Change

Checking file size is not a reliable way to test contentTracing.startRecording({excluded_categories}), since there might still be lots of events in the meta category.

This PR changes the test to check the occurrence of certain events instead.

Release Notes

Notes: none

@electron-cation electron-cation bot added the new-pr 🌱 PR opened recently label Oct 13, 2021
@zcbenz zcbenz changed the title spec: fix flaky contentTracing test test: fix flaky contentTracing.startRecording spec Oct 13, 2021
@electron-cation electron-cation bot removed the new-pr 🌱 PR opened recently label Oct 13, 2021
@zcbenz zcbenz force-pushed the content-tracing-why-fails branch from 138d7f0 to 9b25e73 Compare October 13, 2021 11:41
@jkleinsc
Copy link
Member

Merging as CI failure is known flake unrelated to this PR.

@jkleinsc jkleinsc merged commit a751845 into main Oct 13, 2021
@jkleinsc jkleinsc deleted the content-tracing-why-fails branch October 13, 2021 14:06
@release-clerk
Copy link

release-clerk bot commented Oct 13, 2021

No Release Notes

@trop
Copy link
Contributor

trop bot commented Oct 13, 2021

I have automatically backported this PR to "16-x-y", please check out #31411

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants