Result for 0CEE04010C11B39259FFD3C07A69191646D3517A

Query result

Key Value
FileName./usr/share/pycentral/buildbot/site-packages/buildbot/test/test_buildreq.py
FileSize7019
MD54755FE83866704346753C6CC3B69D4AA
SHA-10CEE04010C11B39259FFD3C07A69191646D3517A
SHA-256DE9063C7499AA83BE3A5B83B87D28B2CA7FC6C243A8B2EE28E0374B909162AE2
SSDEEP192:5wNAAjTdVI0zQLz/U7ZV9U/TKX2HZM9IOwB+r6FOfRB7hKqEQhh:5kw+r6FO5BgqF
TLSHT1CFE1AFB6447326739B97D8A74032175ACB3F44A3D98A4870BE3D02485F29E3571E9EF8
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

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

Key Value
FileSize857434
MD548BC2EA3DD62E91CB6859811C1A16092
PackageDescriptiona system to automate the compile/test cycle The BuildBot is a system to automate the compile/test cycle required by most software projects to validate code changes. By automatically rebuilding and testing the tree each time something has changed, build problems are pinpointed quickly, before other developers are inconvenienced by the failure. The guilty developer can be identified and harassed without human intervention. . By running the builds on a variety of platforms, developers who do not have the facilities to test their changes everywhere before checkin will at least know shortly afterwards whether they have broken the build or not. Warning counts, lint checks, image size, compile time, and other build parameters can be tracked over time, are more visible, and are therefore easier to improve.
PackageMaintainerUbuntu MOTU Developers <ubuntu-motu@lists.ubuntu.com>
PackageNamebuildbot
PackageSectiondevel
PackageVersion0.7.5-1.1
SHA-1638A821941963477CC42BBB389FED71316091819
SHA-256FC93B15D202561E26411573E6DA65C88F814487AC621074AB083C0592A76C2EF
Key Value
FileSize857346
MD5D6F3F01E6A1EC94C505CCC4CC1F2D377
PackageDescriptiona system to automate the compile/test cycle The BuildBot is a system to automate the compile/test cycle required by most software projects to validate code changes. By automatically rebuilding and testing the tree each time something has changed, build problems are pinpointed quickly, before other developers are inconvenienced by the failure. The guilty developer can be identified and harassed without human intervention. . By running the builds on a variety of platforms, developers who do not have the facilities to test their changes everywhere before checkin will at least know shortly afterwards whether they have broken the build or not. Warning counts, lint checks, image size, compile time, and other build parameters can be tracked over time, are more visible, and are therefore easier to improve.
PackageMaintainerUbuntu MOTU Developers <ubuntu-motu@lists.ubuntu.com>
PackageNamebuildbot
PackageSectiondevel
PackageVersion0.7.5-1
SHA-1DEEDDAE65643F1AA74216CEDB823D1FC2F549716
SHA-25627E0A4FF4BA98D6E2AF56C2FC4E74F0AD86BA4E9D192158808AF2F3DFB61968A