Result for AB24F815CFC64E57ED5BE0289961F75BE51CF051

Query result

Key Value
FileName./usr/lib/python3.6/site-packages/__pycache__/pytest_timeout.cpython-36.pyc
FileSize8593
MD5E7583C9BBE53BB42AF4829CD5C4A2E77
SHA-1AB24F815CFC64E57ED5BE0289961F75BE51CF051
SHA-256222D14C5530D97B00CD5A63C82CECF12DBE2AB4A9B1408E853A5EF675F783FFE
SSDEEP192:gnFBMSaSDKjSvyyCvMLH7MgGK2SELDj53K:oBMSaSDKjS9XGnjLDj53K
TLSHT1B102E68A5E07AA29FEE1F6B4816A43E4573BC33737DA85B37435C1192E045C41FB26D8
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
MD5364DF5347B0C77F4E16BD937AEAD0E10
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
PackageNamepython3-pytest-timeout
PackageReleaselp150.1.3
PackageVersion1.2.1
SHA-12CFA1D0B74353A819C833C30450371F9BC456C9A
SHA-256A8EDAC91FA8FED982069CB9C2E03A26C642EE6DEB32DFB46064837F88C989014