1. 03 Apr, 2019 1 commit
  2. 19 Feb, 2019 1 commit
  3. 12 Feb, 2019 3 commits
    • Tamer Tas's avatar
      [testrunner] enable the progress indicator · baeb4e32
      Tamer Tas authored
      Using test generators meant that we had to remove the progress indicator since
      the total number of tests weren't known before-hand.
      
      This CL implements a progress indicator using test number estimations.
      
      cctest and unittests progress indicator is accurate, however estimating
      means the progress will terminate over 100% in big test suites and sometimes
      under 100%.
      
      R=machenbach@chromium.org
      CC=​sergiyb@chromium.org,yangguo@chromium.org
      
      Bug: v8:8769
      Change-Id: I40ca5b40f9b1223376d33707f0945900ea98cea3
      Reviewed-on: https://chromium-review.googlesource.com/c/1460471
      Commit-Queue: Tamer Tas <tmrts@chromium.org>
      Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#59538}
      baeb4e32
    • Tamer Tas's avatar
      [fuzzer] create a test-suite for the fuzzer · e2207c67
      Tamer Tas authored
      Testrunner test-suite doesn't have automated tests for the Fuzzer. A significant
      change for the testrunner may break the fuzzers. We don't have a way to catch
      even the syntax errors for the fuzzer before landing CLs.
      
      This CL creates a rudimentary test-suite that runs the fuzzer without any tests
      to see if APIs still work as intended.
      
      R=machenbach@chromium.org
      CC=yangguo@chromium.org,sergiyb@chromium.org
      
      No-Try: true
      Bug: v8:8763
      Change-Id: Ib4519ca093de2af5279964edd164cee04aae77a8
      Reviewed-on: https://chromium-review.googlesource.com/c/1466301Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Commit-Queue: Tamer Tas <tmrts@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#59535}
      e2207c67
    • Tamer Tas's avatar
      [testrunner] enable variant sharding · ad5b6d7d
      Tamer Tas authored
      Testrunner runs variants of a test sequentially without taking sharding into
      account. A slow test with slow variants slows down the whole test run no matter
      the sharding configuration.
      
      This CL implements a test hashing algorithm and variant sharding for test
      variants.
      
      R=machenbach@chromium.org
      CC=yangguo@chromium.org,sergiyb@chromium.org
      
      Bug: v8:8174
      Change-Id: I15f8c547fa2f361fb6c53bf8d5df055d3df38d3e
      Reviewed-on: https://chromium-review.googlesource.com/c/1458016
      Commit-Queue: Tamer Tas <tmrts@chromium.org>
      Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#59530}
      ad5b6d7d
  4. 07 Feb, 2019 1 commit
  5. 01 Feb, 2019 3 commits
  6. 21 Jan, 2019 2 commits
  7. 18 Jan, 2019 1 commit
  8. 19 Dec, 2018 1 commit
  9. 22 Nov, 2018 1 commit
  10. 30 Oct, 2018 1 commit
  11. 22 Oct, 2018 1 commit
  12. 16 Oct, 2018 1 commit
  13. 10 Oct, 2018 1 commit
  14. 02 Oct, 2018 1 commit
  15. 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
  16. 01 Feb, 2018 1 commit
  17. 31 Jan, 2018 1 commit
    • Michal Majewski's avatar
      Reland "[test] Random seed processor" · 5ede3cb5
      Michal Majewski authored
      This is a reland of 0db74d49.
      
      Original change's description:
      > [test] Random seed processor
      > 
      > 1. --total-timeout-sec now available for ./run-tests.py. It can be
      > useful with infinite seed stressing
      > 2. random seed dropped from the context. Now JSON progress indicator
      > gets it from the list of command args.
      > 
      > Bug: v8:6917
      > Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng
      > Change-Id: I73e535bc8face9b913c696b8d5e3a246fa231004
      > Reviewed-on: https://chromium-review.googlesource.com/888524
      > Commit-Queue: Michał Majewski <majeski@google.com>
      > Reviewed-by: Michael Achenbach <machenbach@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#50964}
      
      Bug: v8:6917
      Change-Id: I1ea376a4abffce5ab65f4834ea7e6d6011765ffa
      Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng
      Reviewed-on: https://chromium-review.googlesource.com/894204Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Commit-Queue: Michał Majewski <majeski@google.com>
      Cr-Commit-Position: refs/heads/master@{#50978}
      5ede3cb5
  18. 30 Jan, 2018 2 commits
  19. 24 Jan, 2018 1 commit
  20. 22 Jan, 2018 1 commit
  21. 17 Jan, 2018 3 commits
  22. 16 Jan, 2018 4 commits
  23. 15 Jan, 2018 2 commits
  24. 12 Jan, 2018 1 commit
  25. 10 Jan, 2018 1 commit
  26. 08 Jan, 2018 2 commits
  27. 03 Jan, 2018 1 commit