Open github-actions[bot] opened 1 year ago
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4030198928
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4032842275
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4048393801
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4048461393
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4048526821
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4100996636
https://github.com/paketo-buildpacks/jammy-full-stack/releases/tag/v0.0.65 has been released, there was an issue uploading the tarball to release
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4117473391
https://github.com/paketo-buildpacks/jammy-full-stack/releases/tag/v0.0.66 has been released, there was an issue uploading the tarball to release. Why does this keep happening?
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4249330985
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4249429248
Network issue connecting to ubuntu.com. Subsequent runs succeeded.
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4259293556
Acceptance test 403
flake which has resolved itself on subsequent runs
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4303884340
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4304077896
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4304156807
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4304221445
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4304319416
Various issues related to pulling GCR images:
/usr/bin/docker pull ghcr.io/paketo-buildpacks/actions/release/download-asset:latest
Error response from daemon: Head "https://ghcr.io/v2/paketo-buildpacks/actions/release/download-asset/manifests/latest":
This looks to be passing now on subsequent runs, this might be due to a GCR outage
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4344430644
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4352565540
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4357163403
Acceptance test 403 flake which has resolved itself on subsequent runs
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4403292110
Flake pulling GCR images for the USN polling job, which is now passing.
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4427156120
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4427347927
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4427459140
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4427550947
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4427641970
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4427751340
Failed to pull docker image for build because ghcr.io was down. It is back up and subsequent runs succeeded.
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4435174520
Error: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.
during diff checking, but this appears to now be passing on subsequent runs.
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4440850600
Failed to install jam when creating stack. Likely a flake.
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4590428819
503 Service Unavailable
parsing the RSS feed from ubuntu, but this is now passing on subsequent runs
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4600160769
Internal GitHub flake: Internal server error occurred while resolving "paketo-buildpacks/github-config/actions/release/find-and-download-asset@main"
Subsequent runs succeeded.
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4674361258
403 error during acceptance tests which has passed on subsequent runs
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4792051616
Internal GitHub issue - network issue pulling docker image. Subsequent runs succeeded.
Error response from daemon: Get "https://ghcr.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4818055989
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4850812183
Error uploading build oci asset, but it has been added successfully in a subsequent run.
Error: failed to complete request: Post "https://uploads.github.com/repos/paketo-buildpacks/jammy-full-stack/releases/101458910/assets?name=jammy-full-stack-0.0.93-build.oci": read tcp 172.17.0.2:55900->140.82.114.13:443: read: connection timed out
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4937659759
Failed with no output - internal GitHub error.
Create Release workflow failed. Please take a look to ensure CVE patches can be released. (cc @paketo-buildpacks/stacks-maintainers).