-
Notifications
You must be signed in to change notification settings - Fork 84
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
swift flakes #2621
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://pipelines.actions.githubusercontent.com/serviceHosts/2572548a-83bf-41e9-89ac-d1bb895f7e73/_apis/pipelines/1/runs/91439/signedlogcontent/4?urlExpires=2022-10-20T16%3A12%3A57.9145160Z&urlSigningMethod=HMACV1&urlSignature=44bCD28UcFtBp7tNUW9aos1UCz0Zxr%2FhesO2jeH%2BzwM%3D
INFO: Repository remote_coverage_tools instantiated at:
/DEFAULT.WORKSPACE.SUFFIX:4:6: in
/private/var/tmp/_bazel_runner/b225883c33850f3f191a570e7b70ec29/external/bazel_tools/tools/build_defs/repo/utils.bzl:233:18: in maybe
Repository rule http_archive defined at:
/private/var/tmp/_bazel_runner/b225883c33850f3f191a570e7b70ec29/external/bazel_tools/tools/build_defs/repo/http.bzl:355:31: in
ERROR: /Users/runner/work/envoy-mobile/envoy-mobile/test/swift/stats/BUILD:5:24: While resolving toolchains for target //test/swift/stats:test.internal.__test_bundle: No matching toolchains found for types @bazel_tools//tools/cpp:toolchain_type.
To debug, rerun with --toolchain_resolution_debug='@bazel_tools//tools/cpp:toolchain_type'
If platforms or toolchains are a new concept for you, we'd encourage reading https://bazel.build/concepts/platforms-intro.
ERROR: Analysis of target '//test/swift/stats:test' failed; build aborted:
INFO: Elapsed time: 251.808s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (104 packages loaded, 1146 targets configured)
ERROR: Couldn't start the build. Unable to run tests
INFO: Streaming build results to: https://envoy.cluster.engflow.com/invocation/bdbde0f4-2582-4e84-aacf-134495dacb54
FAILED: Build did NOT complete successfully (104 packages loaded, 1146 targets configured)
FAILED: Build did NOT complete successfully (104 packages loaded, 1146 targets configured)
Error: Process completed with exit code 1.
The text was updated successfully, but these errors were encountered: