Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: fix flaky contentTracing.startRecording spec #31409

Merged
merged 1 commit into from
Oct 13, 2021

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 in the last 24 hours 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 in the last 24 hours 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.

2 participants