| Key | Value |
|---|---|
| FileName | ./usr/lib/python3/dist-packages/pytest_timeout-1.3.3.egg-info/top_level.txt |
| FileSize | 15 |
| MD5 | 1A64976C65E053E30344B301F97BB5B3 |
| RDS:package_id | 280719 |
| SHA-1 | D6425100D95730EB31732B985C74A390FB42F1C9 |
| SHA-256 | EA0D6A4CD670564534F3E1DAE4146B30C8FFBB3944B60DAF1556F3283C1C22BF |
| SSDEEP | 3:Q:Q |
| TLSH | |
| insert-timestamp | 1751759474.1029809 |
| source | RDS_2025.03.1_android.db |
| tar:gname | root |
| tar:uname | root |
| hashlookup:parent-total | 151 |
| hashlookup:trust | 100 |
The searched file hash is included in 151 parent files which include package known and seen by metalookup. A sample is included below:
| Key | Value |
|---|---|
| MD5 | 722B77ABD1962A157784CE3C3BF7B55C |
| 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. |
| PackageName | python38-pytest-timeout |
| PackageRelease | 18.1 |
| PackageVersion | 2.0.2 |
| SHA-1 | 0168D0892751DCC22BB28AF710849544D94A1FC8 |
| SHA-256 | B407AE7EA17CC8BEA8E3E4A24D20720C55112B7048923A197744FDA716748BDD |
| 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 |
|---|---|
| MD5 | 62558C3CE30CDFA88B94EF5F115665EF |
| 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. |
| PackageName | python3-pytest-timeout |
| PackageRelease | 2.1 |
| PackageVersion | 2.0.2 |
| SHA-1 | 03768E1706F31DC8447376C0F94A1A49073EFFDA |
| SHA-256 | 09A0D26FDBC60133671973F2038BA56DAC64BE8A657AA006B51F9656A2CB3A6B |
| Key | Value |
|---|---|
| MD5 | 16C953DD04787680D0E710769F407653 |
| 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. |
| PackageMaintainer | Fedora Project |
| PackageName | python3-pytest-timeout |
| PackageRelease | 3.fc34 |
| PackageVersion | 1.4.2 |
| SHA-1 | 0405470EA65F189148E45064FC404C8B0F43D73F |
| SHA-256 | FD71BCBD00B1875CFB2B00C75DD4A4D891EC2C8893F52377F31A58FCCB522235 |
| Key | Value |
|---|---|
| MD5 | F86623732FF674B79869FF2694DF75E9 |
| 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. |
| PackageName | python38-pytest-timeout |
| PackageRelease | 17.10 |
| PackageVersion | 1.4.2 |
| SHA-1 | 0498E7723FD9F1300EF42621DACB2E5DC4964D8A |
| SHA-256 | 0A6D6F5105876049198F910C6A7AF5D9EFE90D10E1AB22F39ACE282E591E73E2 |
| Key | Value |
|---|---|
| MD5 | 6DA0910FE3ECD2D5A15BA9F11939DD27 |
| 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. |
| PackageName | python3-pytest-timeout |
| PackageRelease | 2.1 |
| PackageVersion | 2.0.2 |
| SHA-1 | 051C811E728B6A9A2C8D195B1F58D32D37DABCD2 |
| SHA-256 | B54F3EA9B504F9AE63C6AE55D5E17B34928CF998A92A085F5D108DDA63999DA0 |
| 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 | 8C6DC97EBC4A73EBC0E526B91050D99E |
| 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. |
| PackageName | python3-pytest-timeout |
| PackageRelease | lp153.2.1 |
| PackageVersion | 2.0.2 |
| SHA-1 | 0A0BC64C2411ADA68F9DB28F5F32CB9F53821C56 |
| SHA-256 | 6448DD3B5E5B5D1A85A008C91640590AEDDD346C1081F681D889B56C1B7AA60B |
| Key | Value |
|---|---|
| MD5 | 877C5B9EFDC1DE7D49EFF9A16CE8C1D3 |
| 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 | python39-pytest-timeout |
| PackageRelease | 1.1 |
| PackageVersion | 2.0.2 |
| SHA-1 | 0CABD43F9B1394701088FF9C8A7D7C65ED328946 |
| SHA-256 | 4BF7591D250F6CC5288773FFE0A04856A02BAC01573600E2FF8DA5B316564E22 |