1. 01 Mar, 2018 1 commit
  2. 20 Feb, 2018 1 commit
    • Michael Achenbach's avatar
      [test] Abort testing immediately on interrupt and sigterm · 4a2d9b1b
      Michael Achenbach authored
      This is a partial revert of:
      https://crrev.com/c/890938 and https://crrev.com/c/893982
      
      Before this CL, the test runner blocked on ongoing tests in order to
      process their results after an internal timeout. However, the logic
      required for this feature was overly complicated and prevented an
      acceptable implementation for fast aborts. Furthermore, also the fuzzers
      suffered from timeouts on swarming due to hanging tests.
      
      Instead, we now abort immediately on internal timeout (used on
      fuzzers), SIGINT (Ctrl-C) and SIGTERM. Ongoing tests are immediately
      terminated and their results are disregarded. On SIGTERM and SIGINT,
      we return with non-zero exit codes, and zero on internal timeout.
      
      This will also properly return json output, when the external hard
      timeout is reached on swarming (causes SIGTERM).
      
      TBR=sergiyb@chromium.org
      
      Bug: v8:7423, chromium:813065
      Change-Id: Ib20f835f58a0970693bdd3b21dc5d766d8e115d8
      Reviewed-on: https://chromium-review.googlesource.com/924852Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#51399}
      4a2d9b1b
  3. 03 Feb, 2018 1 commit
  4. 02 Feb, 2018 1 commit
    • Michael Achenbach's avatar
      [test] Properly load mjsunit.js on endurance fuzzer · f4411a32
      Michael Achenbach authored
      Load mjsunit.js inside the realm as otherwise the functions are not
      available in the realm's scope.
      
      This also prints timestamps after each test to easier track down slow
      tests.
      
      We also pass --omit-quit to not stop too early.
      
      This also adds the ability to skip certain tests for endurance
      fuzzing and skips some tests with known problems.
      
      TBR=ulan@chromium.org,hpayer@chromium.org
      
      Bug: v8:6972, v8:7400
      Change-Id: I44464c28bfb10c84f2e59972e7b86945a47ca3b3
      Reviewed-on: https://chromium-review.googlesource.com/899008Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#51066}
      f4411a32
  5. 01 Feb, 2018 2 commits
  6. 31 Jan, 2018 5 commits
  7. 30 Jan, 2018 2 commits
  8. 22 Jan, 2018 1 commit
  9. 19 Jan, 2018 1 commit
  10. 17 Jan, 2018 2 commits
  11. 16 Jan, 2018 1 commit
  12. 12 Jan, 2018 3 commits
  13. 27 Dec, 2017 1 commit
    • Michael Achenbach's avatar
      [test] Add basic test-runner system tests · 13485a69
      Michael Achenbach authored
      This tests some high-level scenarios of the V8 test runner, with
      fake executable, test-suite extension and build configs.
      
      The runners are slightly modified to be easier testable. Args
      are passed from the tests now and the V8 root folder can be faked
      by the tests.
      
      We support coverage if python coverage 4.0 is installed. Otherwise
      we run without it.
      
      Bug: v8:6917
      Change-Id: Ib149fd88027cbdc3382bcaea2d82020582f79d2d
      Reviewed-on: https://chromium-review.googlesource.com/831506
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Reviewed-by: 's avatarSergiy Byelozyorov <sergiyb@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#50310}
      13485a69
  14. 07 Nov, 2017 2 commits
  15. 02 Nov, 2017 3 commits
  16. 27 Oct, 2017 1 commit
  17. 26 Oct, 2017 2 commits
  18. 25 Oct, 2017 2 commits
  19. 24 Oct, 2017 3 commits
  20. 23 Oct, 2017 1 commit
  21. 19 Oct, 2017 2 commits
  22. 18 Oct, 2017 1 commit
  23. 16 Oct, 2017 1 commit