Result for 0B056DE20514CBB1CD6012650CB9151AE11C45B8

Query result

Key Value
FileName./usr/lib/python3.6/site-packages/__pycache__/pytest_timeout.cpython-36.opt-1.pyc
FileSize8593
MD59C9AB479C21F085EC8CB97DA0BF8DC42
SHA-10B056DE20514CBB1CD6012650CB9151AE11C45B8
SHA-2566E8AD5AB50DF42001EDF6B66C7DA0E930285AC38E3338AAE361D8EBCB25A0677
SSDEEP192:gn32SagNroc3ZvyCZFrHjK77RzsLDBFT8:k2SagNrz3pPKlsLDBJ8
TLSHT11502F68B4607E63AFCD1F6B4806953E457328337BB5B86937409C2996E065C41EB2BD8
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