Result for 356C071D64C5AE9D440A9EE471FD68B599CBF7E7

Query result

Key Value
FileNamepytest_timeout.py
FileSize14752
MD5CC51FE8116BCEC14D63E20CA32C2EADA
RDS:package_id280719
SHA-1356C071D64C5AE9D440A9EE471FD68B599CBF7E7
SHA-2564A4145393AC0C997902652658760829DACEB4FB780FDB6DBFF4254A417FB3605
SSDEEP384:DNVC5/ecZWw6wG8gtb8pKLSz4sbb4wKL9:DAZ0bJ
TLSHT10362410BD40B9921D6D69C3CEEA7A2D133557B5B770219BC7C9CE1982F0543982F23AE
insert-timestamp1751759438.5908105
sourceRDS_2025.03.1_android.db
tar:gnameroot
tar:unameroot
hashlookup:parent-total30
hashlookup:trust100

Network graph view

Parents (Total: 30)

The searched file hash is included in 30 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD516C953DD04787680D0E710769F407653
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.
PackageMaintainerFedora Project
PackageNamepython3-pytest-timeout
PackageRelease3.fc34
PackageVersion1.4.2
SHA-10405470EA65F189148E45064FC404C8B0F43D73F
SHA-256FD71BCBD00B1875CFB2B00C75DD4A4D891EC2C8893F52377F31A58FCCB522235
Key Value
MD5F86623732FF674B79869FF2694DF75E9
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.
PackageNamepython38-pytest-timeout
PackageRelease17.10
PackageVersion1.4.2
SHA-10498E7723FD9F1300EF42621DACB2E5DC4964D8A
SHA-2560A6D6F5105876049198F910C6A7AF5D9EFE90D10E1AB22F39ACE282E591E73E2
Key Value
MD5AD8369941D0A2607CA2EBCC58A2B0F06
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.
PackageMaintainerguillomovitch <guillomovitch>
PackageNamepython3-pytest-timeout
PackageRelease1.mga8
PackageVersion1.4.2
SHA-11213C011662C2F39FF8FDC284F2D22CC0DBD146B
SHA-25633876205DCB5A61A7F38F67DC7C21F7FE6309DB49EEE8293294005AF66FBBFCE
Key Value
MD5E374AFC6CB353E9CDB20EC577B2F9AFD
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.
PackageNamepython39-pytest-timeout
PackageRelease17.10
PackageVersion1.4.2
SHA-1172222EB9C1EB19F0A2D0239A0B8BE82A0FCEC17
SHA-25688CE3A9F3BC32731ABAC14166AA5BECD7029A80D9DA63D3805416E6547619984
Key Value
FileNamehttps://ftp.lysator.liu.se/pub/OpenBSD/6.9/packages//amd64//py3-test-timeout-1.4.2.tgz
MD58B166AAEB166ABE88BC2FE36ED368DF6
SHA-123CBF4FE2E33C90C5808099737BDDFBEA75BCE37
SHA-2562C585731442AF9DE2AA80876C426B5E54E3FAC97674A2B8BCE99F3447B048E65
SSDEEP384:p92TyOQgi0NXgpoJzqG7LgGFIFQ4wEQmm+ml4upqzjne:p92mOQT0jJzqcgGbyqeuUe
TLSHT11472C021A223DC9F22B865B9D51111772905C8A7D0D1BF8B325F7B3F8899CFA0E92119
Key Value
FileNamehttp://dl-cdn.alpinelinux.org/alpine/latest-stable//main//x86//py3-pytest-timeout-1.4.2-r2.apk
MD51F6E03F74DE2A8DD5ACF79C23C934AC3
SHA-12BB3972C70840E632C98CC199637CA211059392C
SHA-25666861D49BC0B1D2725AC6AA74D0D24D48A1FB8A1CC756719E370494D1A83A3F8
SSDEEP384:IKnqbUWg63cxsw8ONwH+Kw9ghR0F29Hm3/fIUbX7cjKsch62WaaaX:IiqSucxD9t9g/pw33dX7AKdQJaaaX
TLSHT12172E02291EF4B573E0621B42FA7496064E94C31D0E2D69372FC87B845AFEF14F22D26
Key Value
MD50298FBD033B6B51CC9D488C0BA2E2CE1
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.5
PackageVersion1.4.2
SHA-13105262E83DDB75465E5DA7B8C81ABA714D906B8
SHA-256EA2FF3C3026E4951CB1628CA4E075F4EC3F525EC8128FDBFE4694F164294B187
Key Value
FileNamehttps://ftp.lysator.liu.se/pub/OpenBSD/6.9/packages//i386//py3-test-timeout-1.4.2.tgz
MD575FBB9863036694E0F3DB71292F24750
SHA-13223450CD4E607A5B78A798E7CA99534D4C993C2
SHA-25650C7512A5BAEE5582D66A3AD78545ABB92F45FD46893EBAC8733F7345BB25F51
SSDEEP384:lK9YdmsECzyx1CGqasQVZj9mhL7nore+THybrZgFBlrEH+z6:o9Ydq0NGqqVZjQhL7nqf6412
TLSHT19F72E140725A67C0347262D78AEAD8371A58C309AD7D3741A207687BE7CF50D95023EF
Key Value
FileNamehttp://dl-cdn.alpinelinux.org/alpine/latest-stable//main//armhf//py3-pytest-timeout-1.4.2-r2.apk
MD5723AD28463C7E37185B28655C73D1450
SHA-133AB1FAC8B8EFC0C67C1B55158B26F121E4516B0
SHA-256AA4A5A183D1601CFF8ACE3923D5B62C726FFEE635ECA82B789A2AD190661911D
SSDEEP384:4sNCbUWg63cxsw8ONwH+Kw9ghR0F29Hm3/fIUbX7cjKsch62WaaaX:4sNCSucxD9t9g/pw33dX7AKdQJaaaX
TLSHT19272D17191EF87533E0625B02F974860A4EA8D219492C69361B847F8866FEF14F62D27
Key Value
MD53BBD9FC8595FC41156691B8043CA82BE
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
PackageReleaselp153.2.14
PackageVersion1.4.2
SHA-139DCE83CAD287D3C25BC1976F2FD73977D26D96C
SHA-25620E85B960D20D1E2A48A7586067B48CB673EC2EE4A6AAD7AC3BDFCED28B5B180