Result for A72984B018DDE57043776A69AB048A38D06CDB81

Query result

Key Value
FileName./usr/lib/python2.7/site-packages/pytest_timeout.pyo
FileSize11005
MD5462AAEAC6683BD1ECB0086D322B08115
SHA-1A72984B018DDE57043776A69AB048A38D06CDB81
SHA-2561B6BE17D61A43A439D11D75A51EF641427EF64A62251974040B2D3C32B1A2179
SSDEEP192:8nwn+2J+11QfXmf4jJe6CR4IzHS5LAgbzh3YFuBgAzYijI:8fxfsXmAjJe6DtFuuKr2I
TLSHT133326381B3EA5963D8E18434A1B40757DF76F2B3A2022B8176B9D07D1AC8379C57B3C6
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD5F0AE3984307F98354B2EA8973A2D9177
PackageArchnoarch
PackageDescriptionThis 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. See below for detailed information on the timeout methods and their side-effects.
PackageMaintainerhttps://bugs.opensuse.org
PackageNamepython2-pytest-timeout
PackageReleaselp150.1.3
PackageVersion1.2.1
SHA-1F97F05A37CB2C68351A52D94005C59FDC7E0CEBC
SHA-256BFA3EF6846114AAE2152320CB07D1AF18E0865A8CB75B1B9E460CA8CB27AEA03