1. 28 Sep, 2020 1 commit
  2. 16 Jan, 2020 1 commit
    • Michael Achenbach's avatar
      [testrunner] Prevent erroneous overriding of signal handlers · d64a48db
      Michael Achenbach authored
      When an overall timeout is reached, swarming sends a SIGTERM to
      terminate the test runner. The test runner has a signal handler on the
      main process to terminate all workers gracefully.
      
      Additionally, every worker process installs a signal handler for
      terminating ongoing tests wrapped by command.Command.
      
      Also, command.Command is used on the main process to list tests for
      cctest and gtest executables, which led to overriding the test runner's
      main signal handler.
      
      This CL disables using signal handlers in commands by default and only
      explicitly enables it in safe source locations.
      
      Bug: v8:8292
      Change-Id: Ifceadaff75bdd2b77e761498bccbe00b6a3e265c
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2002528Reviewed-by: 's avatarTamer Tas <tmrts@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#65815}
      d64a48db
  3. 16 Jul, 2019 1 commit
  4. 14 Jun, 2019 1 commit
  5. 17 May, 2019 1 commit
  6. 10 May, 2019 1 commit
  7. 09 May, 2019 2 commits
  8. 04 May, 2019 1 commit
    • Sergiy Belozorov's avatar
      [tools] Default to 4 retries for all perf tests · b3e2bcf9
      Sergiy Belozorov authored
      Overall, total test runtime that was wasted due to timeouts is 3420 seconds in
      the last 2 weeks. Even with 4 retries, assuming all of them time out, needed
      additional capacity is under 2 hours per week. Based on this analysis, I think
      it's safe to land this CL.
      
      Note that this is not intended as a long-term solution of the timeout problem,
      but rather a temporary solution to prevent ongoing errors. Proper investigation
      and correct long-term solution are still needed and tracked in the bug.
      
      R=machenbach@chromium.org, tmrts@chromium.org
      
      Bug: chromium:841700
      Change-Id: Id16e6b784fa85bb9e28ed8c6b267b583636e2dc1
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1593342Reviewed-by: 's avatarTamer Tas <tmrts@chromium.org>
      Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Commit-Queue: Sergiy Belozorov <sergiyb@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#61224}
      b3e2bcf9
  9. 29 Apr, 2019 1 commit
  10. 26 Apr, 2019 3 commits
  11. 24 Apr, 2019 2 commits
  12. 23 Apr, 2019 3 commits
  13. 16 Apr, 2019 1 commit
  14. 12 Apr, 2019 3 commits
  15. 10 Apr, 2019 1 commit
  16. 19 Feb, 2019 1 commit
  17. 06 Feb, 2019 1 commit
  18. 01 Feb, 2019 1 commit
  19. 31 Jan, 2019 1 commit
  20. 21 Dec, 2018 1 commit
  21. 20 Dec, 2018 1 commit
  22. 30 Oct, 2018 1 commit
  23. 20 Oct, 2018 1 commit
  24. 16 Oct, 2018 1 commit
  25. 09 Oct, 2018 3 commits
  26. 12 Sep, 2018 1 commit
  27. 11 Aug, 2018 1 commit
  28. 10 Aug, 2018 1 commit
    • Michael Achenbach's avatar
      Reland "[test] Add logic to run tests on Android" · b2537f21
      Michael Achenbach authored
      This is a reland of 4c094342
      
      Original change's description:
      > [test] Add logic to run tests on Android
      > 
      > This adds a new command abstraction for running commands on Android
      > using dockered devices on swarming.
      > 
      > The new abstraction handles pushing all required files to the device.
      > The logic used for pushing and running is reused from the perf runner.
      > 
      > This adds only the mjsunit test suite. Others will be handled in
      > follow up CLs. The suite logic is enhanced with auto-detection of files
      > to be pushed to devices, for e.g. load or import statements.
      > 
      > Some test cases need an extra resource section for specifying required
      > files.
      > 
      > Remaining failing tests are marked in the status files for later
      > triage.
      > 
      > Bug: chromium:866862
      > Change-Id: I2b957559f07fdcd8c1bd2f7034f5ba7754a31fb7
      > Reviewed-on: https://chromium-review.googlesource.com/1150153
      > Reviewed-by: Sergiy Byelozyorov <sergiyb@chromium.org>
      > Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#55041}
      
      Bug: chromium:866862
      Change-Id: Icf7e04c75d4abeab7254d10ba21240e46b0022ae
      Reviewed-on: https://chromium-review.googlesource.com/1170643Reviewed-by: 's avatarSergiy Byelozyorov <sergiyb@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#55059}
      b2537f21
  29. 09 Aug, 2018 2 commits