Result for 00E0AA1760C3D5265CD84D2A8378BE2B431EBC67

Query result

Key Value
FileName./usr/share/pyshared/buildbot/test/unit/test_scripts_base.py
FileSize7133
MD50481361598C1723BE77A1C7B1BFCF5E2
SHA-100E0AA1760C3D5265CD84D2A8378BE2B431EBC67
SHA-256DD6AFEDB8E1B2E4E56D77F905E5C9B985A22B7D7A91CA312E6F976D3AC38DCC0
SSDEEP96:lTFKQu6hI9BbjG9OaBFAG8XOV8F/y8mdcUfWuyOVWQjcPV5j4NiiNbPN1cMNF1R:lTFHXKbjQNjTy3QjcPV54QipPNn7
TLSHT16EE1CB78007386149783DABE949A6097893FEE67194D143AF6BFC6899F11A20D1E7CF0
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
FileSize2450240
MD5FA9B9EA2871D701BF00F8C355E34152C
PackageDescriptionsystem 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 Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamebuildbot
PackageSectiondevel
PackageVersion0.8.7p1-2
SHA-13B2069BE75557A86A47F66826CBA3DE22F6BC3AC
SHA-256A735C1D77A2A08E1DDE1B32E70C633A1E6366E9B2ACEAB4ADCF4A628C09D0263
Key Value
FileSize2452396
MD5C1050BA203934AF6A369C8DDE035B122
PackageDescriptionsystem 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 Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamebuildbot
PackageSectiondevel
PackageVersion0.8.7p1-1
SHA-13F1B02B0A4C655C492EF9EF623FE478814BED677
SHA-256813487189A8FE072A373B3DE3F6E0F2D1E51497B638AA3729EA2099EDFF65001