Result for 15E44A8752BD57914D0625FEDD3AFF4A15B71638

Query result

Key Value
FileName./usr/share/doc/python-stestr-doc/html/api/subunit_trace.html
FileSize8109
MD56123DCFFB6BEF1270EF5078D98811CE6
SHA-115E44A8752BD57914D0625FEDD3AFF4A15B71638
SHA-256AED1C1461582E856F2FE29B471BA6215329B878041C89BB095292CE7E8E2C96F
SSDEEP96:tkuWDmfQPD9WjmAQsYIuBTPqfE8DazgmitTvX8JH/oJCJaziuaz3ehaLJE2LoB2U:tYZ1AohTP43Kitr81oMXuphaLHLNeWoZ
TLSHT1A7F1026398F226370123D1DAE6A81766BDD7C49BE1012804B5FC6B6C8FC6E58BD27D0D
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

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

Key Value
FileSize99404
MD57475837E424E18D4FBBA63E2AEE1D688
PackageDescriptiontest runner similar to testrepository - doc Stestr stands for Slim/Super Test Repository. It is a fork of the testrepository that concentrates on being a dedicated test runner for Python projects. The generic abstraction layers which enabled testr to work with any subunit emitting runner are gone. Stestr hard codes python-subunit-isms into how it works. The code base is also designed to try and be explicit, and to provide a Python API that is documented and has examples. . While stestr was originally forked from testrepository it is not 100% backwards compatible with testrepository. At a high level the basic concepts of operation are shared between the 2 projects but the actual usage between the 2 is not exactly the same. . This package contains the documentation.
PackageMaintainerDebian OpenStack <team+openstack@tracker.debian.org>
PackageNamepython-stestr-doc
PackageSectiondoc
PackageVersion3.0.1-2
SHA-1A05D8AD97615622F725113DA0E5F3225B1F476AA
SHA-256384C2FEFA51618DA728A27ACFA6C972C7E8B5A66E98FDEFDB05051894AF3B957