Can we eliminate the test_might_fail in the last test of t/0700-unifyfs-stage-full.t
Nobody has claimed this yet.
- #617 by @craigsteffen — closed without merging
- Dominant language
- C
- Stars
- 122
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
### System information
Type | Version/Name
--- | ---
Operating System | all
OS Version |
Architecture |
UnifyFS Version |
### Describe the problem you're observing
The last test in the file t/0700-unifyfs-stage-full.t has the test tag:
test_might_fail
This shouldn't be necessary. We think it was put in at some point because Travis was tripping over that test. The test normally works correctly on real systems.
### Describe how to reproduce the problem
### Include any warning or errors or releveant debugging data
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with t/0700-unifyfs-stage-full.t, inspect the final test and its test_might_fail tag, then review the closed pull request #617 for context. Run that test on the supported environment and confirm it passes reliably without the tag; done means the workaround is removed and the test remains stable.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100