Bug #10288: Fix newly identified issues to make our test suite more robust and faster
Step "I shutdown and wait for Tails to finish wiping the memory" fails when memory wiping causes a freeze
Revert "Test suite: mark scenarios that wipe memory as fragile."
This reverts commit 24b59bf21447968731e1583987624812af2359f7.
#8 Updated by Staples over 3 years ago
I have this issue on every release only when using the late 2011 model Macbook Pro. I get no asterisks or anything. I'm prompted to remove the USB or DVD stick as usual than there is a line saying "starting new kernel" . After waiting long enough the latop beeps endlessly till I hold down the power button to shut down. I don't know why I'm using macbook to boot tails on a persistant USB anyways, from what I've read its not possible to boot on macbook pro in the first place...
#16 Updated by anonym about 3 years ago
- Assignee changed from anonym to intrigeri
- QA Check set to Info Needed
We have lost the jenkins artifacts for this one.
This is still the case, and I in fact have no idea how this step is fragile. Looking at the code for the step I would imagine something similar to #9707 but apparently there strong reason to think it is something else according to #10776#note-3. So I am clueless. Do you remember anything about this, intrigeri?
#17 Updated by intrigeri about 3 years ago
- Assignee changed from intrigeri to anonym
Do you remember anything about this, intrigeri?
No, sorry. I suggest you enable the branch on Jenkins again, as I did a couple times in the past already, in order to gather data… and then try to look into it before it disappears :)
#19 Updated by anonym almost 3 years ago
- Target version changed from Tails_2.7 to 284
Actually, we have this commit:
commit 0aaeb150e3c42f39f9f2878a4e268433193d6a7d Merge: 71ac15e 914bbbc Author: intrigeri <email@example.com> Date: Wed Jun 1 14:03:10 2016 +0000 Merge branch 'test/10776-fragile-memory_wipe' into bugfix/10733-run-memory-erasure-hook-earlier
@fragileuntagging has already hit our base branches, so the data can be collected from any branch. However, due to #11786 this step (and any step that depends on Tails successfully shutting down or rebooting) is indeed fragile, but due to an actual bug in Tails. I say: let's block on #11786, and revisit this one after #11786 has been solved for a while, when we have relevant data to find any test suite-specific problem.
#24 Updated by anonym almost 3 years ago
- Status changed from Confirmed to In Progress
- Target version changed from Tails 2.10 to Tails_2.11
Let's backport the workaround we have in
feature/stretch, cd66f0ba49af773489db3a1bf15294255f681ecd, into
devel and revisit this at the next CI meeting.
#27 Updated by anonym almost 3 years ago
- Status changed from In Progress to Fix committed
- Assignee deleted (
- % Done changed from 0 to 100
These commits are now in
7269748273 Work around Tails freezing during memory wiping. 41d88dcdd3 Work around another instance of #11786. 2c9f39bb00 Try to identify #11786 explicitly.
I've tested them locally, and they correctly react when #11786 appears. Let's investigate and discuss the results during the next CI meeting.