Result for DDAD3D7737FA776A5EF8E5094949443E2AB2F846

Query result

Key Value
FileName./usr/lib/python2.7/site-packages/pytest_timeout.pyo
FileSize13195
MD58274722430F699BE7A3BF759F5AD54CE
SHA-1DDAD3D7737FA776A5EF8E5094949443E2AB2F846
SHA-256770A1CA31A1E66490AD56D740F31403FA07CBBC991B9106A0A225FD6FF961915
SSDEEP192:GKYIqp+2J+7pY/r76zwzXYfT6ZcwDWKZdj2Jga+WYfuFgP15YefyO:EMxtEr28DYb6Otsdb9u+EO1
TLSHT134425081B3AA4667D9D08434E5F40797EF76F2B362022B8126B9E07D26C8379C47B3C5
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
MD50F259CAA954694C150861A43CC85610E
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.
PackageNamepython2-pytest-timeout
PackageReleaselp150.2.1
PackageVersion1.3.0
SHA-1BD593C3DDE9695340B162C555B83CD1F3E4FF093
SHA-256E2EDABE87F26B5468CF33D29B48E492D4C817588F7D31C39357DDF8DF8411E3E
Key Value
MD54482308A6EAB04E48C15AEB52B3B06BA
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.
PackageNamepython2-pytest-timeout
PackageReleaselp151.2.1
PackageVersion1.3.0
SHA-1D954FF36DBFC24FA9ABF423A8683005164CE0DC8
SHA-25673C90760563D5303FB7EB56BFEA5669CEB93AF87CF98E995237530DC56E93984