1. 20 Apr, 2016 2 commits
  2. 14 Mar, 2016 1 commit
    • littledan's avatar
      Make test262 test runner check for which exception is thrown · f3568ca4
      littledan authored
      test262 "negative" test expectations list which exception is thrown. The ES2017
      draft specification is very specific about which exception class is thrown
      from which path, and V8 works hard to be correct with respect to that spec.
      
      Previously, the test262 test runner would accept any nonzero status code,
      such as from a crash, or a FAIL printed out, for a negative test. This
      patch makes negative tests check for the right answer using a quick-and-dirty
      parsing of the exception printing from d8 to find the exception class.
      It invokes d8 in a way to get a status code of 0 from thrown exceptions
      so that 'negative' tests aren't actually implemented by negating the output.
      
      Amazingly, this didn't catch any test262 failures, but I verified the extra
      checking interactively by changing a negative test to expect a different type
      and saw it fail.
      
      BUG=v8:4803
      R=machenbach
      LOG=Y
      
      Review URL: https://codereview.chromium.org/1766503002
      
      Cr-Commit-Position: refs/heads/master@{#34763}
      f3568ca4
  3. 28 Feb, 2016 1 commit
  4. 25 Feb, 2016 1 commit
  5. 19 Feb, 2016 1 commit
    • machenbach's avatar
      [Swarming] Speed up test262 upload/download. · 6cecb3eb
      machenbach authored
      This experimentally implements taring/untaring the test data
      for test262 on the v8-side before test isolation and when
      running the tests.
      
      It archives on demand only if the tar is outdated compared
      to the contained files. This comes with a cost of ~1s extra
      to run gyp on linux and ~6s extra on windows. Ninja is
      lightning fast afterwards in detecting changes. Also, we
      archive only when test_isolation_mode is set and when
      the test262_run target is required.
      
      The archiving itself costs ~30s on all platforms. But as the
      files will change seldom this shouldn't have a big impact.
      
      Extraction on the test runner side is below 2s on mac and
      linux. The speedup is enormous. Around 5 minutes were spent
      on download on swarming slaves before, which is now only
      a few seconds. So total test time for release (no variants),
      e.g. goes from 8 to 3 minutes.
      
      BUG=chromium:535160
      LOG=n
      
      Review URL: https://codereview.chromium.org/1713993002
      
      Cr-Commit-Position: refs/heads/master@{#34155}
      6cecb3eb
  6. 06 Nov, 2015 1 commit
  7. 15 Oct, 2015 1 commit
  8. 08 Oct, 2015 1 commit
  9. 07 Oct, 2015 3 commits
  10. 06 Oct, 2015 1 commit
  11. 25 Sep, 2015 1 commit
  12. 17 Sep, 2015 3 commits
  13. 06 Jul, 2015 3 commits
  14. 21 May, 2014 1 commit
  15. 28 Feb, 2014 2 commits
  16. 20 Sep, 2013 1 commit
  17. 19 Sep, 2013 1 commit
  18. 10 May, 2013 1 commit
  19. 18 Apr, 2013 1 commit
  20. 15 Nov, 2012 2 commits
  21. 24 Sep, 2012 1 commit
  22. 05 Jun, 2012 1 commit
  23. 11 May, 2012 1 commit
  24. 16 Apr, 2012 1 commit
  25. 13 Apr, 2012 1 commit
  26. 28 Mar, 2012 1 commit
  27. 07 Mar, 2012 1 commit
  28. 16 Dec, 2011 1 commit
  29. 07 Oct, 2011 1 commit
  30. 26 Jul, 2011 1 commit
  31. 23 Mar, 2011 1 commit