1. 12 Jan, 2017 1 commit
    • littledan's avatar
      [test] Allow command-line flags to be turned on per test262 test · f62f846c
      littledan authored
      This patch changes the test262 infrastructure to pass individual flags,
      specified in the status file, for tests for experimental features, rather
      than passing --harmony for all runs. With this change, it should be
      easier to run test262 tests in automation when developing new features.
      The new workflow would be, when adding a flag, include the flag in the
      test expectations file, and when removing the flag, remove the lines from
      the test expectations file. This way, the status file does not have to
      change when staging or unstaging, and you get the benefit of the automated
      tests before staging starts.
      
      R=adamk
      CQ_INCLUDE_TRYBOTS=master.tryserver.v8:v8_linux_noi18n_rel_ng
      
      Review-Url: https://codereview.chromium.org/2601393002
      Cr-Commit-Position: refs/heads/master@{#42249}
      f62f846c
  2. 07 Jan, 2017 1 commit
    • littledan's avatar
      [test] Process to locally develop and upstream test262 tests · 586deecb
      littledan authored
      This patch provides improved infrastructure for developing test262 tests
      together with V8. It has three parts:
      - The test262 test runner is updated to look for local versions of tests
        in the /test/test262/local-tests directory, which mirrors
        /test/test262/data. Additional tests can be added there and are run
        together with tests from upstream. Upstream tests can be locally
        updated by using the same name in local-tests; if a same-named test
        exists, then only the local version will be run. The local-tests
        directory is in the V8 repository, unlike the contents of the data
        directory, so tests can be added in the same patch as something else.
      - The tool /test/test262/upstream-local-tests.sh is added to create
        a patch against the test262 respository based on a patch which changes
        the local-tests directory.
      - The tool /test/test262/prune-local-tests.sh is added to remove
        redundant local tests on a test262 roll.
      
      See design doc:
      https://docs.google.com/document/d/16bj7AIDgZLv4WOsUEzQ5NzcEN9_xo095e88Pz8FC5rA/edit
      
      Review-Url: https://codereview.chromium.org/2611793002
      Cr-Commit-Position: refs/heads/master@{#42117}
      586deecb
  3. 27 Dec, 2016 1 commit
  4. 10 Oct, 2016 1 commit
  5. 07 Oct, 2016 1 commit
  6. 08 Aug, 2016 1 commit
    • machenbach's avatar
      [test] Deprecate test data download for most test suites · a2a59723
      machenbach authored
      This removes the test-download method for all but
      promises-aplus. They all only contain legacy code for
      deleting old archives.
      
      Only test262 needs to prepare sources on swarming, which is
      moved to a new method, called unconditionally.
      
      All references to --download-data and --download-data-only
      in the infrastructure can be removed after this.
      
      BUG=
      
      Review-Url: https://codereview.chromium.org/2227613002
      Cr-Commit-Position: refs/heads/master@{#38439}
      a2a59723
  7. 22 Jul, 2016 1 commit
  8. 20 Apr, 2016 2 commits
  9. 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
  10. 28 Feb, 2016 1 commit
  11. 25 Feb, 2016 1 commit
  12. 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
  13. 06 Nov, 2015 1 commit
  14. 15 Oct, 2015 1 commit
  15. 08 Oct, 2015 1 commit
  16. 07 Oct, 2015 3 commits
  17. 06 Oct, 2015 1 commit
  18. 25 Sep, 2015 1 commit
  19. 17 Sep, 2015 3 commits
  20. 06 Jul, 2015 3 commits
  21. 21 May, 2014 1 commit
  22. 28 Feb, 2014 2 commits
  23. 20 Sep, 2013 1 commit
  24. 19 Sep, 2013 1 commit
  25. 10 May, 2013 1 commit
  26. 18 Apr, 2013 1 commit
  27. 15 Nov, 2012 2 commits
  28. 24 Sep, 2012 1 commit
  29. 05 Jun, 2012 1 commit
  30. 11 May, 2012 1 commit
  31. 16 Apr, 2012 1 commit