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

Don't use bazel_plaforms to detect wasm builds. #6700

Merged
merged 1 commit into from
Jul 9, 2024

Conversation

copybara-service[bot]
Copy link
Contributor

Don't use bazel_plaforms to detect wasm builds.

We get into weird errors that look a lot like this.

@copybara-service copybara-service bot force-pushed the test_650621830 branch 3 times, most recently from 5449e29 to 98b4a06 Compare July 9, 2024 16:18
We get into weird errors that look a lot like [this][1].

[1]: bazelbuild/bazel#18567 (comment)

PiperOrigin-RevId: 650665259
@copybara-service copybara-service bot merged commit be4eba9 into master Jul 9, 2024
@copybara-service copybara-service bot deleted the test_650621830 branch July 9, 2024 16:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant