Opened at 2022-12-12T15:04:59Z
Last modified at 2024-12-19T20:59:14Z
#3951 assigned defect
Tox breaks Tahoe-LAFS CI a lot
Reported by: | exarkun | Owned by: | blaisep |
---|---|---|---|
Priority: | normal | Milestone: | Contributor Experience |
Component: | dev-infrastructure | Version: | n/a |
Keywords: | Cc: | ||
Launchpad Bug: |
Description
New releases of Tox frequently break Tahoe-LAFS.
We can mitigate this by pinning Tox versions more precisely so that we only upgrade it when we _want_ to upgrade it (#3950). However, I propose that we don't want to spend our maintenance efforts on chasing incompatible Tox changes that don't provide useful functionality.
How about we stop using Tox entirely?
There are some obvious alternatives. Nix is one. Nox is another (seriously). Perhaps if we look around a little bit we'll find others.
Change History (2)
comment:1 Changed at 2024-12-19T16:47:46Z by blaisep
comment:2 Changed at 2024-12-19T20:59:14Z by blaisep
- Component changed from unknown to dev-infrastructure
- Milestone changed from undecided to Contributor Experience
- Owner set to blaisep
- Status changed from new to assigned
This will be related to https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4053
Investigate https://nox.thea.codes/en/stable/tutorial.html