Result for 3D4347DF1BB740E351DDA228334C922942A86946

Query result

Key Value
FileName./usr/lib/python3.9/site-packages/__pycache__/pytest_timeout.cpython-39.pyc
FileSize12243
MD5AC7B66051AC241FF4B86168B3A161F31
SHA-13D4347DF1BB740E351DDA228334C922942A86946
SHA-256FC5478B91FEE5F35A84E9D6EA557185D63F6E221803D2FD63A87094C5317CFEC
SSDEEP192:AsbmrKRz/5GdMbcKvGsN2WQ38TeaksqpHHBI4ynw2t7D/h/GK4r:XYKRzBGObcQ1NMMTeak3anvt7D/h+Ke
TLSHT1C94209E999076735FCD1F778813E47F09722D327332B95A67409D1982F012988E7A6DC
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

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

Key Value
MD54860F7435B8740C338A35410B0BF93AE
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.
PackageNamepython39-pytest-timeout
PackageRelease1.3
PackageVersion1.4.2
SHA-19FC15A9DF3775DAE50A4AA0320755E1C6C47F16B
SHA-256905C9F86793FE6F4B696455ECCAC8CB575E0BD60A436802A33B6936158C3F292
Key Value
MD5E374AFC6CB353E9CDB20EC577B2F9AFD
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.
PackageNamepython39-pytest-timeout
PackageRelease17.10
PackageVersion1.4.2
SHA-1172222EB9C1EB19F0A2D0239A0B8BE82A0FCEC17
SHA-25688CE3A9F3BC32731ABAC14166AA5BECD7029A80D9DA63D3805416E6547619984