Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bot] Update dependencies #1207

Merged
merged 2 commits into from
Oct 26, 2021
Merged

[Bot] Update dependencies #1207

merged 2 commits into from
Oct 26, 2021

Conversation

manylinux-bot[bot]
Copy link
Contributor

@manylinux-bot manylinux-bot bot commented Oct 12, 2021

Update the versions of our dependencies.

PR generated by "Update dependencies" workflow.

@henryiii
Copy link
Contributor

henryiii commented Oct 12, 2021

error: failed to solve:
failed to compute cache key: mount callback failed on /tmp/containerd-mount846069579:
failed to convert whiteout file ".wh.build_scripts":
unlinkat /tmp/containerd-mount846069579/build_scripts/update-system-packages.sh:
operation not permitted

I think the failed travis jobs just need to be restarted?

@mayeut
Copy link
Member

mayeut commented Oct 12, 2021

ppc64le builds are failing depending on which cloud they get dispatched... restarting them keep sending them to saopaulo workers which are failing... I'll keep retrying....

@henryiii
Copy link
Contributor

henryiii commented Oct 17, 2021

Would you like to try kicking at Travis again? Probably getting close to a cibuildwheel release, I think pypa/cibuildwheel#854 and pypa/cibuildwheel#875 are about all that's left, and I think getting pip 21.3 at the same time might be nice.

(unless this gets rebuilt automatically with the weekly bump, which is about to happen)

@henryiii
Copy link
Contributor

Wow, I can actually restart builds, nice. :) Not sure that will help, though, as in other projects Travis is loving the saopaulo workers, probably because they are always free due to always failing. :)

@henryiii
Copy link
Contributor

I've reached out to Travis CI support, and they are investigating the issue.

@henryiii
Copy link
Contributor

I can make a PR to move to emulated builds on GitHub actions for ppc64le. They take 3 hours or so, though that's from scratch with no caching.

Why do these use "buildkit" as the build frontend, instead of through buildx, like the others? It didn't seem to be needed for GHA.

@henryiii
Copy link
Contributor

Actually, that was for manylinux_2_24. manylinux2014 takes 5 hours and 15 minutes with no caching. 😮

@auvipy auvipy closed this Oct 23, 2021
@auvipy auvipy reopened this Oct 23, 2021
@henryiii
Copy link
Contributor

henryiii commented Oct 23, 2021

Can you retrigger the bot? Would be nice to get pip 21.3.1 while we are at it. Workflow dispatch, I think.

@henryiii
Copy link
Contributor

henryiii commented Oct 23, 2021

Also, that musllinux ppc64le job seems to work the second time, when the cache is empty it fails to solve, and then the second time it works. Nevermind, I guess there's a chance of a solve failure unrelated to ppc64le, as it's actually one of the classic jobs that hit that.

@henryiii
Copy link
Contributor

henryiii commented Oct 25, 2021

The update dependency bot is broken:

nox > python update_native_dependencies.py
Traceback (most recent call last):
  File "/home/runner/work/manylinux/manylinux/update_native_dependencies.py", line 159, in <module>
    main()
  File "/home/runner/work/manylinux/manylinux/update_native_dependencies.py", line 150, in main
    _update_cpython(args.dry_run)
  File "/home/runner/work/manylinux/manylinux/update_native_dependencies.py", line 37, in _update_cpython
    if latest_version > current_version:
TypeError: '>' not supported between instances of 'NoneType' and 'Version'

@henryiii
Copy link
Contributor

Looks like lastversion is unable to find Python, opened an issue upstream.

@henryiii
Copy link
Contributor

The bug in lastversion was introduced in 1.6.0 (and retained in 2.0.0). 1.5.1 is the last working version. We can pin that to get this working again for now.

@henryiii
Copy link
Contributor

henryiii commented Oct 26, 2021

I can't suggest on something that didn't change in the PR, but

session.install("lastversion", "packaging", "requests")

could be changed to

    session.install("lastversion!=1.6.0,!=2.0.0", "packaging", "requests")

And the bot would need to be rerun. Or we could wait to see if there's a new release from lastversion with a fix; as soon as that's out, rerunning will automatically update this PR.

Edit: changed ==1.5.1 to instead exclude just the broken versions, assuming the next one will be fixed.

@auvipy auvipy merged commit cf1e11e into main Oct 26, 2021
@auvipy auvipy deleted the update-dependencies-pr branch October 26, 2021 15:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants