1. 02 Jan, 2019 1 commit
  2. 10 Oct, 2018 1 commit
  3. 18 Sep, 2018 1 commit
  4. 14 Sep, 2018 2 commits
    • intrigeri's avatar
      Test suite: give the VM some time to be reconfigured after plugging a disk. · c12b4030
      intrigeri authored
      I see "Drive 'pRUZWkrmDo' is not detected by Tails (Timeout::Error)" too often
      these days. In the debug log, I see "test -b /dev/sda" being called exactly once
      and the surrounding try_for(20) timing out. I think that the remote shell gets
      confused by update(domain_xml.to_s) which is called by plug_drive → plug_device,
      e.g. the serial port it uses may be very temporarily unavailable and we're
      unlucky enough that our remote shell client sends a request exactly at
      that time. To support this hypothesis, after the failure, when one of our After
      hooks runs this:
      
          if $vm && $vm.remote_shell_is_up?
            save_journal($config['TMPDIR'])
          end
      
      … the remote shell client is confused, complains the ID of the answer it
      receives is not the expected one, and the Journal is not saved
      (which incidentally makes it hard to debug the very problem I'm trying to solve
      here).
      c12b4030
    • intrigeri's avatar
      VeraCrypt test suite: bump timeout. · 2178fd8c
      intrigeri authored
      I've seen a few "Drive 'veracrypt' is not detected by Tails (Timeout::Error)".
      Let's see if a bigger timeout helps.
      2178fd8c
  5. 13 Sep, 2018 3 commits
  6. 12 Sep, 2018 1 commit
  7. 19 Aug, 2018 1 commit
  8. 07 Aug, 2018 1 commit
  9. 10 Jul, 2018 1 commit
    • intrigeri's avatar
      Test suite: make "AppArmor has (not )? denied" step more robust. · b2eb36d8
      intrigeri authored
      I've seen a false positive because journalctl was run too early: the Journal
      output for this scenario, saved as a test suite artifact, actually shows that
      the expected denial occurred.
      
      I think that when we use this step after "I do not see […]", which calls
      waitVanish, Cucumber + Sikuli can possibly win the race against systemd-journald
      and then we expect a log message that was not registered yet.
      
      So, let's try up to 10 times to find the log message we want and drop the
      ability to customize that delay (which is not used anywhere).
      b2eb36d8
  10. 07 Jul, 2018 1 commit
  11. 05 Jul, 2018 1 commit
    • intrigeri's avatar
      Test suite: make the audio test more robust (refs: #15023) · ec0699be
      intrigeri authored
      I did not manage to make it robust enough with Firefox 60 and this test was
      never meant to exercise the HTML5 player: it was introduced
      (commit:136db50c) to ensure our AppArmor
      confinement for Tor Browser did not break audio playback, so let's
      do this and not more, just like we're doing for the video test as well.
      ec0699be
  12. 03 Jul, 2018 4 commits
  13. 05 Mar, 2018 1 commit
  14. 20 Feb, 2018 2 commits
  15. 09 Dec, 2017 1 commit
    • anonym's avatar
      Test suite: fix the "I do not see ..." step's case. · f018bc11
      anonym authored
      The recently introduced always-on Sikuli image candidate search makes
      wait() not work so great when expected to fail (as in the "do not"
      case of this step) so let's use waitVanish() instead.
      
      And, while we're at it, let's not use the FindFailed override for
      waitVanish() -- it was purely a mistake that it was overridden!
      
      Will-fix: #14929
      f018bc11
  16. 08 Dec, 2017 1 commit
    • anonym's avatar
      Test suite: fix the "I do not see ..." step's case. · 94d51da6
      anonym authored
      The recently introduced always-on Sikuli image candidate search makes
      wait() not work so great when expected to fail (as in the "do not"
      case of this step) so let's use waitVanish() instead.
      
      And, while we're at it, let's not use the FindFailed override for
      waitVanish() -- it was purely a mistake that it was overridden!
      
      Will-fix: #14929
      94d51da6
  17. 04 Dec, 2017 2 commits
  18. 13 Nov, 2017 1 commit
  19. 09 Nov, 2017 1 commit
  20. 11 Oct, 2017 1 commit
    • anonym's avatar
      Test suite: allow more time for 'systemctl is-system-running' to succeed. · dd985681
      anonym authored
      Hypothesis: #14772 is due to a race occurring after `step "the time
      has synced"`, namely that the systemd units that will start when the
      time is synced (and probably the same check is used for this as in
      that step) haven't necessarily finished when we run `systemctl
      is-system-running`. So let's just give it some more time.
      
      Will-fix: #14772
      dd985681
  21. 04 Oct, 2017 1 commit
  22. 01 Oct, 2017 1 commit
  23. 25 Sep, 2017 3 commits
  24. 14 Sep, 2017 3 commits
  25. 09 Sep, 2017 1 commit
  26. 06 Sep, 2017 2 commits
  27. 05 Sep, 2017 1 commit