Circle CI unable to resolve dependencies #3627
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#3627
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In this comment, I report an issue where Circle CI tests are apparently failing to install dependencies, implicating pip 19.1.1 in not filtering the dependencies correctly.
Relying on pip 19.2 appears to work around the issue.
I don't see anything relevant in the pip changelog.
Looking at pyrsistent, it appears as if 0.17.0-0.17.2 did not have python_requires and were yanked.
But it seems that pip 19.1 doesn't support yanking.
Yep. That's the issue. Yanking wasn't supported until pip 19.2.
So we're either going to need to bump to pip 19.2 or start providing separate dependency strings (and our dependencies' dependencies) for Python 2 and Python 3.
I recommend to bump pip.
Looking at the CI jobs, the master and branch jobs look very different, even though master has been merged back into the branch. So the issue seems to be CircleCI is caching something from when the branch was created.
Aha, so re-running the failed jobs in Circle CI allowed them to pass. Whatever the problem was has passed.