Result for 1DCDA8EF268242E532CDABD6EEA4115F058A05DD

Query result

Key Value
FileName./usr/lib/python3.8/site-packages/__pycache__/pytest_timeout.cpython-38.opt-1.pyc
FileSize10510
MD5AEE893F90592C31A02F4BEE404759AB9
SHA-11DCDA8EF268242E532CDABD6EEA4115F058A05DD
SHA-256B34FE40256FB841C4B3B6CFDF21E2FE3638A1F80E097D6C681D3BD41D3432CE9
SSDEEP192:kV3lmrmB/EI0cTHM2y6BVTLFKqqh4H90htylx4ry3DBkdkkF:sYmB/EI0cgCTL4x+0hclxr3DBkuK
TLSHT1EA2208A99A07E665FCD1F7B4806E43FC9732D337730749A77808A0AD1D116884EB66C9
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
MD52D9A65AB9BC606889CD31C6050ED3439
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.
PackageNamepython3-pytest-timeout
PackageRelease2.3
PackageVersion1.3.4
SHA-1D2F422C159238EAC77C230D4770EEB1770B30CF7
SHA-25633BD35AB249B21A1F3EFF928AD6F227BEA9C4121507A0A1A897D6D83759A8FD5