Skip to content

Fixed bazel configuration ambiguity for non HTTP3 builds #10180

Fixed bazel configuration ambiguity for non HTTP3 builds

Fixed bazel configuration ambiguity for non HTTP3 builds #10180

Triggered via pull request June 4, 2024 18:22
@tedjpooletedjpoole
synchronize #34483
Status Success
Total duration 1m 9s
Artifacts 1

request.yml

on: pull_request_target
request  /  incoming
43s
request / incoming
request  /  ...  /  start
7s
request / checks / start
Fit to window
Zoom out
Zoom in

Artifacts

Produced during runtime
Name Size
env Expired
2.34 KB