spockframework / spockframework/spock
PollingConditionsSpec.provides fine-grained control over polling fails on AppVeyor
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 483
- PR merge metrics
- No merged PRs in 30d
Description
It failed in #626 only on Windows. Verify if there order is important in this test.
:spock-specs:test
Download https://repo1.maven.org/maven2/com/h2database/h2/1.3.176/h2-1.3.176.pom
Download https://repo1.maven.org/maven2/com/h2database/h2/1.3.176/h2-1.3.176.jar
spock.util.concurrent.PollingConditionsSpec > provides fine-grained control over polling rhythm FAILED
Condition not satisfied:
spans[0] < spans[1]
| | | | |
| 266 | | 203
| | [266, 203, 406]
| false
[266, 203, 406]
at spock.util.concurrent.PollingConditionsSpec.provides fine-grained control over polling rhythm(PollingConditionsSpec.groovy:118)
1378 tests completed, 1 failed, 24 skipped
:spock-specs:test FAILED
Contributor guide
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 PollingConditionsSpec.groovy at line 118 and run :spock-specs:test in a Windows/AppVeyor environment. Investigate whether the polling-rhythm assertion depends on execution order or timing. Done means the test no longer fails intermittently on Windows while still checking the intended polling behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100