Memory erasure tests regression on the devel branch
The memory erasure tests have been failing on the devel branch for a few weeks.
- First failure: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/1442/ (Oct 15, 2018 11:07:16 PM; f1d545b1dc0d972076cfb7cba0e74622880da082), triggered by https://jenkins.tails.boum.org/job/build_Tails_ISO_devel/3183/
- Last success: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/1441/ (Oct 9, 2018 7:56:14 AM, d1abfbaf9e585fa9e68dda279208677c941b65e9), triggered by https://jenkins.tails.boum.org/job/build_Tails_ISO_devel/3173/
Significant changes between these commits:
- Linux upgraded from 4.17.0-3 to 4.18.0-2 and accordingly, aufs4-standalone upgraded from 01543e47eae7653c7e9a35a7204301f8a0b3ca50 to bdda97c749604bb9ea3f19e0c1ffac9042e79f77 → I doubt that matters because our stable branch also includes this change and there, the tests pass
-
debianAPT snapshot updated from 2018100901 to 2018101503 which includes at least systemd 237-3~bpo9+1 → 239-7~bpo9+1
Sadly, the build artifacts for these 2 ISO build jobs and most of the
relevant APT snapshots have been GC’ed already. Still, comparing the
.build-manifest for the last successful builds of stable and devel and
filtering out those that were upgraded in Debian after 20181015, the
only potential culprit I see is the systemd 237-3~bpo9+1 →
239-7~bpo9+1 upgrade, which happened on 20181009 but strictly after the
2018100901 debian APT snapshot.
Feature Branch: bugfix/16097-memory-erasure-on-shutdown
Attachments
Related issues
- Related to #16100 (closed)
- Blocks #15507 (closed)
- Blocks #16312 (closed)
- Blocks #16352 (closed)
Original created by @intrigeri on 16097 (Redmine)