Parents (Total: 43)

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

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.8/packages//powerpc64//py3-test-timeout-1.3.4p0.tgz
MD5	B63D156A714CCB91BBB2BA8698B63740
SHA-1	03570FFAE870138A2E3F1FDEA6344B9D43F06148
SHA-256	D669C09DA5E99C2C6286680CF159BCF0D0495058768F6017F626FD3F9388C8CD
SSDEEP	192:GmxlcXbbiBALaN9HGC/6htoRgO05L1zl4f7uPiGra5vxoan1miHffzYn/:Gm4LbiCcHs1kuixog1/HzY/
TLSH	T10152D033717CD15641CE90B9AEB2F98F424B54D084EFAF9A802B57C1841BF8156E0F68

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.8/packages//sparc64//py3-test-timeout-1.3.4p0.tgz
MD5	7AE183E5B4252F3910F370766535814D
SHA-1	07D1179C144DAAE10BBF46C9AC0CF40A97A61703
SHA-256	B4F181D8044F19B21C100640EABE8C46FBBFFFEDBBCBFCA19DD937E228855A87
SSDEEP	384:GhsV44rOmRZ7WOTr19dF7O2iN5YaUNweFQIu65lM0YSEX:CsV4OOsxr19z78w6jIZlUNX
TLSH	T1CB52C0F005AB04C9DD7736EB607A335622F998436B1E8399994542F372F8B7EA7012D2

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.7/packages//sparc64//py-test-timeout-1.3.4.tgz
MD5	FA95AA12A049242C82940AEE9DEAECD3
SHA-1	0822EAAC7D59C4B345EF460D828358C835F555C5
SHA-256	524F59EF0B841D6F09D2C5E92B2CE82F8C435281B3FFD24C4808FEC725E91652
SSDEEP	384:dC3PQqxSuASqK0BJZCbdTlWzScFmaYWSUz8:s3VxSuAlnqlslTY
TLSH	T13B62D05746FCC33DDBEC107ACC95A03074697ABB0B4E1C17D6105B2E0D26886C46E2EB

Key	Value
MD5	39B81F05F61CAB921A7A30D080170733
PackageArch	noarch
PackageDescription	This 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.
PackageMaintainer	https://bugs.opensuse.org
PackageName	python3-pytest-timeout
PackageRelease	lp152.1.1
PackageVersion	1.3.4
SHA-1	1264AF5ACFE4CDD4D542BD1F44781649F4DE8C0C
SHA-256	2528E0FE1D04E209B1F96B74BA6D02C47F7C914E525E42C8D25FC3CEB5641497

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.7/packages//i386//py-test-timeout-1.3.4.tgz
MD5	7A9BE0DF4475F301608D5650A82FDE5C
SHA-1	17C2845FCBE2F5475A7F7DD4A3BC8815FBF167A6
SHA-256	3B645997F58A33B91FF38A983CE2FBB0F180D412A50CD7CB685F4DCC3F4C172B
SSDEEP	384:M53lvGSuASqK0BJZCFyuoMRq6MFZyYnZOgTFyKon:s3lvGSuAlnlVMRCFZJnZB4xn
TLSH	T12062C06161B4C67B687F373ACCB1A07A767572A30DDB3517C224164A81E81A38E1C2FB

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.7/packages//i386//py3-test-timeout-1.3.4.tgz
MD5	2336AFC31721E459CFE568F4E79F931B
SHA-1	1A053409A69298B7190C263913C6FAA744F57B71
SHA-256	E4D88F3D06A65B60960D1CC56D3242C10B49833C8DD43BFC412D4E0E3E0670A4
SSDEEP	384:SQ38d+SMXq9o5MBxqW4QdR2MhKwQPLevImpXLkvh/Ev:SQ3kpMa0MBxqW4Q/jQPLevzgZcv
TLSH	T1D552C0F528072139E4F460D248914D3790DCB6C55FD6069C3E69D79E02D2F95AC6BC0B

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.7/packages//mips64el//py3-test-timeout-1.3.4.tgz
MD5	23FCF0886B78D0D9A09B9C6935165CD4
SHA-1	20B18C6E04367D9463856AF198E8F7A6C4158D2C
SHA-256	B0171ABDA0204D9A15A6D19D0B6BC9DA84D800F76D6515BB9A697BC4C79F6B39
SSDEEP	384:oB3PPXoyL6LtJl1vOeEJFXUCS80g7RdAVYGeKSwYzqHlj:oB3HoyL6LtP9mFXP1MVYGT2mFj
TLSH	T1A052CF215D356134EC1210205A38A03AB662B4E96C9BA1B7F3CEB2D310713D7DFEDA38

Key	Value
MD5	7E054D6E8D8055F3D25634EE037B280A
PackageArch	noarch
PackageDescription	This 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.
PackageMaintainer	https://bugs.opensuse.org
PackageName	python2-pytest-timeout
PackageRelease	lp152.1.1
PackageVersion	1.3.4
SHA-1	26196AC5CEC51809F7D5F7C01100B4A0AE812E78
SHA-256	FFB8D648F7CCBFBDEFE6518F35F8F1EFB8983FD8244299E72462D9AE211DDD3B

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.8/packages//mips64el//py3-test-timeout-1.3.4p0.tgz
MD5	87C750D4A646721848261EC309DE100E
SHA-1	2699DD495F8656B81A4FFE90115155C62B26FC8F
SHA-256	B2F90B68A9C555173BBA0EFCE7B23FF44BD33A74036BABC549A197E9C7B67E60
SSDEEP	384:Gu4NbI5pjotskpO2qmycl6Gm/AQvh/F6PhHK8m9sF+r44pFCJ:p4ZI5mtsoqm1IFvh96Py9sC44aJ
TLSH	T19E52D0046B659CC6B48BF3927261E23410F5C55EC6ABF645844FF9EB398163D86720CF

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.7/packages//mips64//py3-test-timeout-1.3.4.tgz
MD5	3C92A7C3449F5062AB940A52690C4578
SHA-1	2940717003C46429EDFBAA51AC98BB27C2FF56CA
SHA-256	F63B79EBEACBFA1AC62460101C7899A522EB4B9C478B7341BA08F09B6C4AE54C
SSDEEP	384:tZ3Cz981WWRYNhJMHFSFus1LijvPVGHli285l8tRa:tZ3t1DY9uaejvPVG8Z8Da
TLSH	T1A252D0702EA3441118172766B4B9C41182ABF6D076E4393F03A75C5AD977E299BCCE3B