Open github-actions[bot] opened 1 year ago
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3455191817
Failed to build Docker image for action - internal github failure.
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3469824245
Failed to build Docker image for action - internal github failure.
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3489664232
Failed to upload release. Re-running.
Error: failed to complete request: Post "https://uploads.github.com/repos/paketo-buildpacks/jammy-full-stack/releases/83418200/assets?name=jammy-full-stack-0.0.36-build.oci": read tcp 172.17.0.2:43766->140.82.112.13:443: read: connection timed out
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3489942731
Failed to upload release (timeout). Re-running.
Error: failed to complete request: Post "https://uploads.github.com/repos/paketo-buildpacks/jammy-full-stack/releases/83429412/assets?name=jammy-full-stack-0.0.36-build.oci": read tcp 172.17.0.2:60708->140.82.114.14:443: read: connection timed out
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3503720860
I/O timeout getting USNs. This could be a candidate for potential retry logic - we should explore.
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3515118842
Failure uploading build.oci release asset, but it has succeeded on the next run.
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3542613108
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3548761261
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3548819069
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3548872069
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3548930743
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3549084790
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3549146001
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3549195431
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3595168897
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3595287208
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3595458412
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3595542623
403 error while accessing http://archive.ubuntu.com/ubuntu/dists/jammy/multiverse/binary-amd64/Packages, but this seems to be an ubuntu website issue, and it's now been resolved and a release has been cut
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3644522637
Upstream issue getting USNs: error parsing rss feed: http error: 503 Service Unavailable
- hit retry limit. Succeeded on subsequent runs. Closing.
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3696212210
503
getting USNs - resolved itself and subsequent builds passed. Closing.
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3847292752
unexpected response status: 403 Forbidden
on stack acceptance tests which appears to be a flake because the next run has passed and a release has been cut
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3852419360
I/O timeout out creating release; re-running.
Error: failed to complete request: Post "https://uploads.github.com/repos/paketo-buildpacks/jammy-full-stack/releases/88086971/assets?name=jammy-full-stack-0.0.53-build.oci": read tcp 172.17.0.2:58992->140.82.112.13:443: read: connection timed out
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3852419360
Failed again for the same reason (I/O timeout uploading release asset). Re-running.
(Finally succeeded and created a new release)
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3860363608
403
getting asset from GitHub during integration test. Subsequent runs passed. Closing.
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3908746384
Failed to download Ubuntu package during stack creation. Closing.
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/o/openssl/openssl_3.0.2-0ubuntu1_amd64.deb Could not connect to archive.ubuntu.com:80 (185.125.190.39), connection timed out Could not connect to archive.ubuntu.com:80 (185.125.190.36), connection timed out
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3942418789
Failed to download asset from github. Re-running.
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/3942838947
IO timeout uploading asset to github release. Re-running.
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4003777888
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4003964344
No logs available. Subsequent runs succeeded. Closing.
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4028024330
Another failure occurred: https://github.com/paketo-buildpacks/jammy-full-stack/actions/runs/4028079863
503 Service Unavailable
while getting USNs. Passing now so I am closing this out
Create Release workflow failed. Please take a look to ensure CVE patches can be released. (cc @paketo-buildpacks/stacks-maintainers).