-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
[CI] Enable audio tests in Chrome #23665
Merged
Merged
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
42e032e
Minor: Firefox now supports wasm64
cwoffenden c858dea
The AW test should now fail, waiting on audio playback
cwoffenden 29451a4
Confirmed failure, now flagging as needing audio
cwoffenden b7fb25a
Correctly halt for btest_exit()
cwoffenden a9132c8
Attempt to run CI with autoplay enabled
cwoffenden 92c8b5c
Retrying without wasm64
cwoffenden a42c6d4
Try adding a dummy sound device...
cwoffenden 4b80dd2
Try with a full path...
cwoffenden 9bcf181
Try with Chrome flags for audio...
cwoffenden f9a781b
Try dummy audio for FF; remove LACKS_SOUND_HARDWARE
cwoffenden e8ca2c4
Removed FF flags (they don't work)
cwoffenden 9fd83f7
Flagged tests as requiring sound hardware
cwoffenden 9e63502
Revert back test (changes moved to #23695)
cwoffenden e9f37db
Finish moving test code to other PR
cwoffenden 5d27dc8
SDL audio tests with wasm64 disabled for now
cwoffenden 9008192
Changed todo to URL of PR
cwoffenden File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we make this change should we also remove the
EMTEST_LACKS_SOUND_HARDWARE
setting above?I'm kind of inclined to make this change as its one separate PR, e.g.
[CI] Enable audio testing on chrome
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't have much time today so it was mostly experimenting and coming back to it, but:
EMTEST_LACKS_SOUND_HARDWARE
✅Is it fine to always enable the dummy sound hardware and bypass the media interaction? I can't think what this would break (and where real sound hardware is present its used as a preference, at least from my manual testing).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I imagine enabling dummy sounds hardware and bypass the interaction check should be fine for all out tests..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I limited removing
EMTEST_LACKS_SOUND_HARDWARE
to Chrome (FF I can't get to work, documented in the comments).