Bug #9883

Tests can fail with "Not enough memory to check for upgrades" window on top of others

Added by kytv 2015-08-02 13:56:56 . Updated 2015-08-11 10:46:06 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Test suite
Target version:
Tails_1.5
Start date:
2015-08-02
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

  • Should the TailsToaster VM receive an increase of its RAM?; or
  • should the tests anticipate this error being a possibility?; or
  • all of the above?

And/or should there be a fix/change made elsewhere?

Files

checks-2015-08-02T10_59_39+00_00.png (95625 B) kytv, 2015-08-03 05:30:07
i2p-2015-08-02T20_25_59+00_00.png (128488 B) kytv, 2015-08-03 05:31:59

Subtasks

Related issues

Related to Tails - Bug #9929: Increased memory needs in 1.5 cause issues Resolved 2015-08-06

History

#1 Updated by intrigeri 2015-08-03 04:27:02

  • Assignee set to kytv
  • QA Check set to Info Needed

Which tests, exactly, and at what step?

#2 Updated by kytv 2015-08-03 05:40:30

It’s more of a theoretical can cause tests to fail but I saw it in the (unpublished) I2P tests that I’ve been developing. I’m checking that I2P is running in Hidden Mode but the low ram error is covering the window as shown in the attached file. In this particular case I can/will focus the I2P Browser window.

Last night I saw it (=“low ram”) come up during the “Report an Error” launcher step in German. The test failed but for a different reason (to be determined whether it’s just my build or something else).

I’m fairly certain that I’ve seen the “low RAM” error pop up elsewhere in the test suite while I’ve been working on it but it hasn’t caused any test suite failures.

#3 Updated by intrigeri 2015-08-03 06:12:58

  • Assignee changed from intrigeri to kytv
  • QA Check set to Info Needed

Can it be reproduced in a scenario that runs the “available upgrades have been checked” step before doing anything memory-consumming? Or perhaps that step is missing in some places?

#4 Updated by intrigeri 2015-08-03 06:15:08

Have you seen this failure in a scenario that runs the “available upgrades have been checked” step before doing anything memory-intensive? Perhaps that step is missing in some places?

#5 Updated by intrigeri 2015-08-03 09:33:03

  • Status changed from New to Confirmed

I’m seeing such failures too (maybe caused by Bug #9748).

#6 Updated by intrigeri 2015-08-03 10:32:39

intrigeri wrote:
> I’m seeing such failures too (maybe caused by Bug #9748).

Indeed, I take this back: I only see such failures on branches based on devel, that are affected by Bug #9748, and not on branches based on stable.

#7 Updated by kytv 2015-08-06 08:12:25

  • related to Bug #9929: Increased memory needs in 1.5 cause issues added

#8 Updated by intrigeri 2015-08-06 09:14:47

  • Status changed from Confirmed to In Progress
  • Target version set to Tails_1.5
  • % Done changed from 0 to 50
  • QA Check changed from Info Needed to Ready for QA

kytv, please confirm that this is fixed on the testing branch. Thanks in advance!

#9 Updated by kytv 2015-08-07 15:59:57

  • Assignee changed from kytv to intrigeri
  • QA Check changed from Ready for QA to Pass

I’m happy with the fix.

#10 Updated by intrigeri 2015-08-08 01:18:53

  • Status changed from In Progress to Fix committed

Thanks!

#11 Updated by intrigeri 2015-08-08 01:39:20

  • Assignee deleted (intrigeri)
  • % Done changed from 50 to 100

#12 Updated by BitingBird 2015-08-11 10:46:06

  • Status changed from Fix committed to Resolved