Result for 6936433070E2F31D615F490B9DFC890194BBFA47

Query result

Key Value
FileName./usr/lib/python3.6/site-packages/__pycache__/pytest_timeout.cpython-36.opt-1.pyc
FileSize10342
MD577858FED6797C89FB4490DC4C148F997
SHA-16936433070E2F31D615F490B9DFC890194BBFA47
SHA-25612589C2732BD2A28D7931A8C2E1FCD7A1B1AAEAE88E2ED2447BA5087F572E10E
SSDEEP192:mKIkrrlAsaBI5Q7MoOXvAbyCyMNNy6uHWPbEGJLDkI:msrlAsaBI5Q7Mo9egNjjxJLDkI
TLSHT10E22F78A4607AF2BFCDAF3B4D56E43E41B32D37B330A45A27409926D2D045C94E72ADC
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
MD531FC57E3C38FC9904CBEF1E031ADDF59
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
PackageReleaselp151.2.1
PackageVersion1.3.0
SHA-18B319E0A081BFF336EE3C84C542D5499F1937B86
SHA-2569DB80ED9359693B8B2AF889AEDA5D1D412569ACB49AC8CC4319CF38BC2273A83
Key Value
MD556AB0C0357A8DD50E4EECB437E788714
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
PackageReleaselp150.2.1
PackageVersion1.3.0
SHA-1A638B9CCDA0041D4388ACBFD86D38C8DE2FF58FE
SHA-256431DE81E902A4A385D639229B37D8A8468FE2AF86AD7ECB5F2A3680C1B7F2684