Failure: Create Draft Release workflow

[github-actions[bot]]

Create Draft Release workflow failed.

[github-actions[bot]]

Another failure occurred: https://github.com/paketo-buildpacks/python/actions/runs/2737781897

[robdimsdale]

Failed to upload. Re-running.

Error: failed to complete request: Post "https://uploads.github.com/repos/paketo-buildpacks/python/releases/72828148/assets?name=python-2.0.0.cnb": write tcp 172.17.0.2:40090->140.82.114.14:443: write: connection reset by peer

[robdimsdale]

Succeeded - closing.

[github-actions[bot]]

Another failure occurred: https://github.com/paketo-buildpacks/python/actions/runs/2764588145

[robdimsdale]

Failed to upload. Re-running:

Error: failed to complete request: Post "https://uploads.github.com/repos/paketo-buildpacks/python/releases/73231472/assets?name=python-2.0.0.cnb": read tcp 172.17.0.2:57890->140.82.112.14:443: read: connection reset by peer

[robdimsdale]

Succeeded - closing.

[github-actions[bot]]

Another failure occurred: https://github.com/paketo-buildpacks/python/actions/runs/2800530176

[github-actions[bot]]

Another failure occurred: https://github.com/paketo-buildpacks/python/actions/runs/2800799681

[github-actions[bot]]

Another failure occurred: https://github.com/paketo-buildpacks/python/actions/runs/2800902122

[robdimsdale]

I think these recent failures are because the pip version has been bumped but the corresponding packages in requirements.txt are out of date. I've also seen this type of failure when the python version is too old.

I see that the PRs failed the integration tests for the same reason but were merged anyway. @paketo-buildpacks/python-maintainers am I missing something about why we felt we could merge the PR?

[robdimsdale]

Ah, I see we're fixing it in https://github.com/paketo-buildpacks/python/pull/500/files

Still, I think it would be cleaner to have fixed the integration tests separately from adding jammy support.

[joshuatcasey]

Still, I think it would be cleaner to have fixed the integration tests separately from adding jammy support.

I agree - but strangely enough the integration tests were passing when running without an integration.json file, but failing for bionic in the jammy PR. I probably could have done an intermediate PR to add an integration.json with only bionic and the integration tests fixes, but it didn't seem worth it.

[github-actions[bot]]

Another failure occurred: https://github.com/paketo-buildpacks/python/actions/runs/4221345780

[robdimsdale]

This looks like an issue downloading tools. Re-triggering.

Installing jam v1.7.0 Error: Process completed with exit code 22.

[github-actions[bot]]

Another failure occurred: https://github.com/paketo-buildpacks/python/actions/runs/4562071162

[robdimsdale]

Network flake downloading/install CPython. Re-running.

            [builder]     Selected CPython version (using pyproject.toml): 3.11.2
            [builder] 
            [builder]   Executing build process
            [builder]     Installing CPython 3.11.2
            [builder] unexpected EOF
            [builder] ERROR: failed to build: exit status 1

[github-actions[bot]]

Another failure occurred: https://github.com/paketo-buildpacks/python/actions/runs/5058807856

[robdimsdale]

  Uploading asset: build/buildpackage.cnb -> python-2.12.0.cnb
Error: failed to complete request: Post "https://uploads.github.com/repos/paketo-buildpacks/python/releases/103968616/assets?name=python-2.12.0.cnb": unexpected EOF

Failed on all automatic retries - succeeded when re-run manually.

[github-actions[bot]]

Another failure occurred: https://github.com/paketo-buildpacks/python/actions/runs/6126149774

[github-actions[bot]]

Another failure occurred: https://github.com/paketo-buildpacks/python/actions/runs/10696348097