Age | Commit message (Collapse) | Author | Files | Lines |
|
and the schroot accordingly, to jenkins-reproducible-sid-debbindiff
|
|
|
|
|
|
suites. yet hardcode suite in the file
|
|
|
|
|
|
|
|
|
|
|
|
This makes it not wrap onto a newline on my rather low-resolution laptop.
The URL is more than sufficient I feel; it's kinda implicit that its a
request for someone to do something anyway - why would we be reporting it
to IRC otherwise, etc.
Signed-off-by: Chris Lamb <lamby@debian.org>
|
|
|
|
comparing two builds
|
|
|
|
|
|
|
|
reproducibly in the past becomes unreproducible
|
|
|
|
It can happen that the first build was successful, but the second build
not (e.g. because of failing tests, which has already been observed).
In this case, the whole build has to be marked FTBFS and debbindiff
doesn't need to be called.
|
|
|
|
|
|
|
|
|
|
|
|
outwhich which debbindiff version is used
|
|
/userContent where possible
|
|
|
|
to timeout
|
|
|
|
debbindiff run also exited successfully...
|
|
|
|
else downloading of 0ad* sources fails...
|
|
sourced after common-functions...
|
|
This reverts commit bbc7e44fd215538aff947c652235305c88474fbf.
|
|
|
|
after a build has started...
|
|
daily)
|
|
|
|
another job)
|
|
|
|
|
|
|
|
|
|
more and only fail+warn+notify if the 2nd download attempt also fails
|
|
package...
|
|
|
|
|
|
|
|
|
|
|
|
|