issues
search
tonybaloney
/
pytest-freethreaded
MIT License
31
stars
3
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Setting threads and iterations to 1 results in tests running twice, once on main thread and once on ThreadPoolExecutor-0_0
#20
dan-glass
opened
1 week ago
0
Introduce `@pytest.mark.threadunsafe` to disable thread-based parallelism for specific tests
#19
ogrisel
opened
1 month ago
1
Fix typo in README
#18
hugovk
closed
1 month ago
0
Make function-scope fixtures run in the same thread as the test function itself
#17
ogrisel
opened
1 month ago
6
bug in lib? or stdlib? sorry
#16
davidszotten
opened
1 month ago
2
change readme executions mentions to iterations
#15
braingram
closed
1 month ago
0
Documentation and code don't agree on the flag for number of executions
#14
glandium
opened
1 month ago
0
Replace `typing.Union` with `|`.
#13
toshihikoyanase
closed
1 month ago
0
Found concurrency errors in scikit-image
#12
toshihikoyanase
opened
1 month ago
3
Found segmentation fault in Pillow
#11
glandium
closed
3 weeks ago
5
Found concurrency errors in Pillow
#10
glandium
opened
1 month ago
0
Found segmentation fault in Pillow
#9
m-clare
closed
3 weeks ago
10
Capture the warnings when you import a module which does not declare no-GIL support
#8
tonybaloney
opened
1 month ago
4
Try running standard library with a concurrency-repeat patterns
#7
tonybaloney
opened
1 month ago
1
Implement a hook function that launches the test in a thread pool
#6
tonybaloney
closed
1 month ago
1
Refactor package into a folder and use flit
#5
tonybaloney
closed
1 month ago
0
Use flit for package builds instead of hatch
#4
tonybaloney
closed
1 month ago
2
Now checks if GIL is enabled before running tests, fails if true
#3
NCLI
closed
1 month ago
0
During pytest initialization, fail if the GIL is enabled
#2
tonybaloney
closed
1 month ago
0
Create an option to set the number of threads
#1
tonybaloney
closed
1 month ago
3