Integration test step goes green even if actual tests fail #2922
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#2922
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?
Is maybe the "tox" command not propagating its exit-code .. "or something"? See e.g. https://travis-ci.org/tahoe-lafs/tahoe-lafs/jobs/375959463
Locally at least (Debian stretch)
tox -e integration
does correctly return1
(if e.g. the "Chutney" tests fail, in the case I was looking at).Hm. I think someone clicked the rebuild button on that travis build. Travis re-uses build numbers! So when you rebuild a failed job you lose all of the state from the failed run and it is replaced by the results of the new run. Fun stuff.
This sounds like a terrible bug sadly all of the information associated with the failure is gone.
We should re-open this if we observe the problem again and include all relevant information on the ticket instead of linking out to travis to avoid losing it again.
FWIW, fortunately or unfortunately, I've seen failed integration test runs on CI... so this doesn't always happen. :/