Skip to content

Make it possible for CronetClient to own the lifetime of an existing CronetEngine #22

Make it possible for CronetClient to own the lifetime of an existing CronetEngine

Make it possible for CronetClient to own the lifetime of an existing CronetEngine #22

Triggered via pull request February 22, 2024 02:35
Status Failure
Total duration 29s
Artifacts

publish.yaml

on: pull_request
publish  /  validate
19s
publish / validate
publish  /  publish
0s
publish / publish
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 notice
publish / validate
Process completed with exit code 1.
publish / validate
pub publish dry-run failed; add the `publish-ignore-warnings` label to ignore