PyPy CI: allmydata.test.test_system.SystemTest.test_filesystem sometimes fails #3321
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
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#3321
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?
There are these intermittent failures on pypy2.7-buster on CircleCI (example), which goes away when the task is restarted:
Possibly related to #3299.
PyPy CI: allmydata.test.test_system.SystemTest sometimes failsto PyPy CI: allmydata.test.test_system.SystemTest.test_filesystem sometimes failsAnother example - https://app.circleci.com/pipelines/github/tahoe-lafs/tahoe-lafs/901/workflows/b7919505-f9da-465c-93fc-3e72ebf2ae7a/jobs/29878
test_filesystem
is too big to make any sense of. I filed https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3438 for breaking one piece off of it.(https://github.com/tahoe-lafs/tahoe-lafs/pull/875)
(https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3572) was a duplicate of this