1. 23 Jun, 2020 1 commit
  2. 05 Aug, 2019 1 commit
    • Michael Achenbach's avatar
      Reland "[test] Print hanging tests on linux on test-runner termination" · cdfadf4a
      Michael Achenbach authored
      This is a reland of 3fc96631
      
      The private method on_event in timeout proc is now renamed to be truly
      private.
      
      Original change's description:
      > [test] Print hanging tests on linux on test-runner termination
      >
      > This will print the list of processes still running before and after
      > joining workers during termination. This will help debugging hanging
      > tests during flake-bisect or with num-fuzzer, which both terminate
      > on total timeout and currently still sometimes hang without printing
      > processes.
      >
      > Bug: v8:8292
      > Change-Id: I124b65fa35b8d7a6aa198fcf50f2c20df94dc51a
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1735312
      > Reviewed-by: Tamer Tas <tmrts@chromium.org>
      > Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#63065}
      
      Bug: v8:8292
      Change-Id: Ibad1172666d6f4d2c07884a54edfe9d6499b57fe
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1735318Reviewed-by: 's avatarTamer Tas <tmrts@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#63072}
      cdfadf4a
  3. 07 Apr, 2019 1 commit
  4. 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
  5. 31 Jan, 2018 1 commit
  6. 25 Jan, 2018 1 commit
  7. 24 Jan, 2018 2 commits