Result for 14A6E591B307D3975A5888B5FFD69CA3A162402E

Query result

Key Value
FileName./usr/share/doc/python-stestr-doc/html/api/repository/memory.html
FileSize10105
MD52F4512CB42F2DEE8E5245AF55A51067E
SHA-114A6E591B307D3975A5888B5FFD69CA3A162402E
SHA-256C338DCD63FC46BA635A60C2D3B7849C904394F75E86413D41D676EE3FF5A63AD
SSDEEP192:PjxoWhnX1/ZWg2T0bLReEtMjFp3LlIfnz17:PThnXfFde7SfnzZ
TLSHT1F922EC0196F65D330627A3DBB2A40F26B6C3C407E5891C06B5FD46A84BD7DD0AA67B3C
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
FileSize101188
MD57DF497AF7CFA8E1EBD8221A7206984EC
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.1.0-2
SHA-1508FCBC9561B201A4E370A2B19722A99FE1F359C
SHA-2569FF6D6F6D675CA66A6B5D3A1043B269ADDE5A483C7056B2E65602ACB6EF71F1B