1. 30 Sep, 2021 1 commit
  2. 25 Jun, 2021 1 commit
  3. 29 Apr, 2021 1 commit
  4. 19 Nov, 2020 1 commit
  5. 06 Jul, 2020 1 commit
  6. 23 Jun, 2020 1 commit
  7. 19 Feb, 2019 1 commit
  8. 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
  9. 12 Dec, 2017 1 commit
  10. 04 Aug, 2016 1 commit
    • machenbach's avatar
      [test] Enable test status filtering by variant · 03f51248
      machenbach authored
      This adds the possibility to address test cases in the
      status file with the variant under which the test is running.
      This is only allowed in top-level sections.
      
      Example:
      [{
        'test-case': [PASS, SLOW],
      }]
      
      ['variant == foo', {
        'test-case': [FAIL],
      }]
      
      The test case "test-case" is marked as slow in all variants.
      Additionally, in variant foo, it'll be expected to fail.
      
      This CL also exemplifies the new feature with test cases
      running under the ignition_turbofan variant. The
      corresponding legacy flag is deprecated.
      
      BUG=v8:5238
      
      Review-Url: https://codereview.chromium.org/2203013002
      Cr-Commit-Position: refs/heads/master@{#38342}
      03f51248
  11. 15 Mar, 2016 1 commit
  12. 07 Jul, 2015 2 commits
  13. 30 Jan, 2015 1 commit
  14. 16 Jan, 2015 1 commit
  15. 02 Sep, 2014 3 commits
  16. 21 May, 2014 1 commit
  17. 21 Mar, 2014 1 commit
  18. 12 Feb, 2014 1 commit
  19. 31 Jan, 2014 1 commit
  20. 25 Sep, 2013 1 commit
  21. 24 Sep, 2012 1 commit
  22. 16 Nov, 2011 1 commit
  23. 17 Feb, 2011 1 commit
  24. 31 Aug, 2010 1 commit
  25. 28 Apr, 2010 1 commit
  26. 25 Jan, 2010 1 commit
  27. 02 Dec, 2009 1 commit
  28. 21 Nov, 2008 1 commit
  29. 31 Oct, 2008 1 commit
  30. 09 Sep, 2008 1 commit
  31. 02 Sep, 2008 1 commit
  32. 22 Aug, 2008 1 commit
    • christian.plesner.hansen's avatar
      Included mjsunit JavaScript test suite and C++ unit tests. · c42f5829
      christian.plesner.hansen authored
      In the shell sample don't print the result of executing a script, only
      evaluating expressions.
      
      Fixed issue when building samples on Windows using a shared V8
      library.  Added visibility option on Linux build which makes the
      generated library 18% smaller.
      
      Changed build system to accept multiple build modes in one build and
      generate seperate objects, libraries and executables for each mode.
      
      Removed deferred negation optimization (a * -b => -(a * b)) since this
      visibly changes operand conversion order.
      
      Improved parsing performance by introducing stack guard in preparsing.
      Without a stack guard preparsing always bails out with stack overflow.
      
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@16 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      c42f5829