test_multi_threading_lock_unlock may be flaky
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 128
- Forks
- 110
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 10
Description
Description of issue
We had an intermittent failure of test_multi_threading_lock_unlock with niscope in our Internal Suite.
All the suite tells us is AssertionError.
There is probably some flakiness due to the timing or timeouts.
System report
This occurred with an in-dev NI-SCOPE 23.5.0 (2023 Q3) and niscope 1.4.5.
Steps to reproduce issue
Run the system tests.
It's only failed once and this is an issue with flakiness, so it'll likely be hard to reproduce.
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 by locating and running the system test containing test_multi_threading_lock_unlock against niscope. Investigate the timing or timeout conditions behind the intermittent AssertionError; done means the test no longer flakes and the system test remains passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100