Disable audio loopback tests in generic-worker while audio-loopback broken in AWS#7230
Merged
Disable audio loopback tests in generic-worker while audio-loopback broken in AWS#7230
Conversation
petemoore
requested review from
lotas and
matt-boris
and removed request for
a team
lotas
approved these changes
Sep 2, 2024
petemoore
added a commit
that referenced
this pull request
Sep 3, 2024
These tests were disabled in #7230 due to a temporary problem with workers in GCP. Since that issue has been resolved the tests can be re-enabled.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Unfortunately we had to move Generic Worker Ubuntu workloads to AWS from GCP while our images are broken in GCP.
This (temporarily) disables the loopback audio tests, which don't run in AWS, since audio loopback is currently not working there.
When we move workloads back to Google Cloud, we should be able to safely revert this commit.