Project

General

Profile

Bug #12041

Bug #10288: Fix newly identified issues to make our test suite more robust and faster

Spurious reboot breaks test suite which cannot connect to the remote shell

Added by intrigeri almost 3 years ago. Updated over 2 years ago.

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Test suite
Target version:
-
Start date:
12/19/2016
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

After we deal with the boot menu the kernel starts booting, but then suddenly we reboot. This second time we don't add the magic kernel commandline options, so the remote shell is not running when we reach the Greeter.

  Scenario: VirtualBox guest modules are available                # features/virtualization.feature:4
    Given a computer                                              # features/step_definitions/common_steps.rb:122
    And the computer is an old pentium without the PAE extension  # features/step_definitions/erase_memory.rb:29
[log] CLICK on (1024,384)
[log] TYPE " autotest_never_use_this_option blacklist=psmouse 
" 
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
    And I start Tails from DVD with network unplugged and I login # features/step_definitions/common_steps.rb:196
      Remote shell seems to be down
      Last ignored exception was: Errno::ECONNRESET: Connection reset by peer @ io_fillbuf - fd:37  (Timeout::Error)
      ./features/support/helpers/misc_helpers.rb:83:in `rescue in try_for'
      ./features/support/helpers/misc_helpers.rb:33:in `try_for'
      ./features/support/helpers/exec_helper.rb:16:in `wait_until_remote_shell_is_up'
      ./features/support/helpers/vm_helper.rb:485:in `wait_until_remote_shell_is_up'
      ./features/step_definitions/common_steps.rb:345:in `/^the computer (re)?boots Tails$/'
      ./features/step_definitions/common_steps.rb:204:in `/^I start Tails( from DVD)?( with network unplugged)?( and I login)?$/'
      features/virtualization.feature:7:in `And I start Tails from DVD with network unplugged and I login'
    When Tails has booted a 32-bit kernel                         # features/step_definitions/checks.rb:99
    Then the VirtualBox guest modules are available               # features/step_definitions/checks.rb:126
      Scenario failed at time 02:55:57

02_55_57_VirtualBox_guest_modules_are_available.mkv (331 KB) intrigeri, 12/19/2016 05:10 PM

00_11_32_Anti-test__no_memory_erasure_on_an_old_computer.mkv (1.14 MB) intrigeri, 12/19/2016 05:11 PM


Related issues

Related to Tails - Bug #11892: Sometimes the remote shell doesn't start because of missing initial Space when modifying the kernel cmdline In Progress 10/31/2016

History

#1 Updated by intrigeri almost 3 years ago

  • Subject changed from Test suite cannot sometimes connect to the remote shell: "Errno::ECONNRESET: Connection reset by peer @ io_fillbuf" to Spurious reboot breaks test suite which cannot connect to the remote shell
  • Description updated (diff)

#3 Updated by anonym over 2 years ago

Possible solution: similar to the TAB spamming + reboot madness, we could recover by doing a reboot (+ redo the boot steps) if we reach the Greeter and the remote shell is down.

#4 Updated by u about 1 year ago

  • Related to Bug #11892: Sometimes the remote shell doesn't start because of missing initial Space when modifying the kernel cmdline added

Also available in: Atom PDF