Roland Clobus authored Sep 03, 2022 and Holger Levsen committed Sep 05, 2022

Signed-off-by: Holger Levsen <holger@layer-acht.org>

Roland Clobus authored Aug 28, 2022 and Holger Levsen committed Aug 29, 2022

archive was synced while building an ISO image

Also update the logparse rules with the new messages

Signed-off-by: Holger Levsen <holger@layer-acht.org>

Roland Clobus authored Jan 24, 2022 and Holger Levsen committed Jan 24, 2022

reproducible_debian_live_build: Show info lines in Jenkins when a reproducible hooks has been active

Signed-off-by: Holger Levsen <holger@layer-acht.org>

reproducible: don't be so trigger-happy in deleting schroot internal stuff, call to schroot -e to terminate the schroots instead

Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Signed-off-by: Holger Levsen <holger@layer-acht.org>

Signed-off-by: Holger Levsen <holger@layer-acht.org>

Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Signed-off-by: Holger Levsen <holger@layer-acht.org>

Signed-off-by: Holger Levsen <holger@layer-acht.org>

Signed-off-by: Holger Levsen <holger@layer-acht.org>

Signed-off-by: Holger Levsen <holger@layer-acht.org>

Signed-off-by: Holger Levsen <holger@layer-acht.org>

Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Signed-off-by: Holger Levsen <holger@layer-acht.org>

Signed-off-by: Holger Levsen <holger@layer-acht.org>

Revert "reproducible: add logparse rules to ignore two warnings from unrelated packages installations"

if we have to _ignroe the warnings_ they would need to be "ok" lines,
not "warning", but I can't find a reason as to why they would be
triggered from this logparse rules files, so perhaps it was meant to be
put in another one.

Let me revert this for now.

This reverts commit 99e3da67.

Signed-off-by: Holger Levsen <holger@layer-acht.org>

reproducible: fix the auto-offline thing by checking content of the permalinks file instead of following the lastSuccessfulBuild link that is not being updated anymore.  bad jenkins.

Signed-off-by: Mattia Rizzolo <mattia@debian.org>

today we missed a warning because we weren't checking for a particular
string.  dsa-check-running-kernel has several other warning state, so
just mark the build as unstable whenever it exists non-0.

Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Signed-off-by: Holger Levsen <holger@layer-acht.org>

reproducible: expand the check for the wrong future to also detect when we accidentally came back to the present

Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Signed-off-by: Mattia Rizzolo <mattia@debian.org>

node_health_check: check for a more general `systemctl is-system-running` to check the status of all services

so we cover more stuff than only haveged

Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Signed-off-by: Holger Levsen <holger@layer-acht.org>

Signed-off-by: Holger Levsen <holger@layer-acht.org>

Signed-off-by: Holger Levsen <holger@layer-acht.org>

Signed-off-by: Holger Levsen <holger@layer-acht.org>

Signed-off-by: Holger Levsen <holger@layer-acht.org>

Signed-off-by: Holger Levsen <holger@layer-acht.org>

Signed-off-by: Holger Levsen <holger@layer-acht.org>

Signed-off-by: Holger Levsen <holger@layer-acht.org>

reproducible maintenance: detect temporary diffoscope schroot problems and (prepare to) reschedule automatically (not doing so yet)

reproducible: look for reproducible_build.sh processes with pid 1 as parent (=orphans) and let the maintenance job become unstable if found