Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help |
The search service can find package by either name (apache), provides(webserver), absolute file names (/usr/bin/apache), binaries (gprof) or shared libraries (libXm.so.2) in standard path. It does not support multiple arguments yet...
The System and Arch are optional added filters, for example System could be "redhat", "redhat-7.2", "mandrake" or "gnome", Arch could be "i386" or "src", etc. depending on your system.
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 pytest 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.
Package | Summary | Distribution | Download |
python310-pytest-timeout-2.3.1-1.2.noarch.html | Pytest plugin to abort hanging tests | OpenSuSE Tumbleweed for noarch | python310-pytest-timeout-2.3.1-1.2.noarch.rpm |
python310-pytest-timeout-2.3.1-1.2.noarch.html | Pytest plugin to abort hanging tests | OpenSuSE Ports Tumbleweed for noarch | python310-pytest-timeout-2.3.1-1.2.noarch.rpm |
Pytest plugin to abort hanging tests | python310-pytest-timeout-2.3.1-1.2.noarch.rpm |
Generated by rpm2html 1.6