Result for 52D785F81CEF598210D92997B5C88D88160D8341

Query result

Key Value
FileName./usr/lib/python3.8/site-packages/__pycache__/pytest_timeout.cpython-38.pyc
FileSize10510
MD5D6518D73D5BB06E9FDF9788A433C1440
SHA-152D785F81CEF598210D92997B5C88D88160D8341
SHA-2566CE2741C5689D780CAB179DD43E9ED9F0AFEEF0DCA102B4175D92D8961CCEC9D
SSDEEP192:kV3lmrSY/3IHcfq2RBiT8Cqqh4HOxd5wrF2DBnKfkF:sYSY/3IHcC/T8CxNxd582DBnKfK
TLSHT1D42219E59907A665FCD2F3B8816E07F09332D333331B55A3B408D1691E157C95EBAAC8
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