Next | Query returned 9 messages, browsing 1 to 10 | previous

History of commit frequency

CVS Commit History:


   2020-01-07 09:48:43 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-test-timeout: updated to 1.3.4

1.3.4
Give the threads a name to help debugging.
Changed location to https://github.com/pytest-dev/pytest-timeout because \ 
bitbucket is dropping mercurial support.
   2018-11-19 11:30:29 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-test-timeout: updated to 1.3.3

1.3.3
Fix support for pytest >= 3.10.
   2018-08-28 08:31:47 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-test-timeout: updated to 1.3.2

1.3.2:
Unknown changes
   2018-07-24 10:23:20 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-test-timeout: updated to 1.3.1

1.3.1:
Fix deprecation warning on Python 3.6.
Create a valid tag for the release. Somehow this didn't happen for 1.3.0, that \ 
tag points to a non-existing commit.
   2018-06-24 11:45:13 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-test-timeout: updated to 1.3.0

1.3.0:
Make it possible to only run the timeout timer on the test function and not the \ 
whole fixture setup + test + teardown duration
Use the new pytest marker API
   2017-11-30 09:18:32 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-test-timeout: updated to 1.2.1

1.2.1
Fix for pytest 3.3
Update supported python versions: - Add CPython 3.6. - Drop CPyhon 2.6 (as did \ 
pytest 3.3) - Drop CPyhon 3.3 - Drop CPyhon 3.4
   2017-11-26 17:56:06 by Adam Ciarcinski | Files touched by this commit (1)
Log message:
Removed unused lines
   2017-11-06 14:35:03 by Thomas Klausner | Files touched by this commit (1)
Log message:
py-test-timeout: follow redirect
   2017-10-19 08:52:03 by Adam Ciarcinski | Files touched by this commit (4)
Log message:
This is a plugin which will terminate tests after a certain timeout. When doing
so it will show a stack dump of all threads running at the time. This is useful
when running tests under a continuous integration server or simply if you don't
know why the test suite hangs.

Note that while by default on POSIX systems py.test will continue to execute
the tests after a test has timed, out this is not always possible. Often the
only sure way to interrupt a hanging test is by terminating the entire process.
As this is a hard termination (os._exit()) it will result in no teardown, JUnit
XML output etc. But the plugin will ensure you will have the debugging output
on stderr nevertheless, which is the most important part at this stage.

Next | Query returned 9 messages, browsing 1 to 10 | previous