How to Install and Uninstall python310-pytest-timeout Package on openSuSE Tumbleweed

Last updated: November 14,2024

1. Install "python310-pytest-timeout" package

Please follow the steps below to install python310-pytest-timeout on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                python310-pytest-timeout
            
                    
    
    Copied

2. Uninstall "python310-pytest-timeout" package

Please follow the guidelines below to uninstall python310-pytest-timeout on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                python310-pytest-timeout
            
                    
    
    Copied

3. Information about the python310-pytest-timeout package on openSuSE Tumbleweed

Information for package python310-pytest-timeout:
-------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python310-pytest-timeout
Version : 2.2.0-1.2
Arch : noarch
Vendor : openSUSE
Installed Size : 65.5 KiB
Installed : No
Status : not installed
Source package : python-pytest-timeout-2.2.0-1.2.src
Upstream URL : https://github.com/pytest-dev/pytest-timeout/
Summary : Pytest plugin to abort hanging tests
Description :
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.