1. 31 Oct, 2014 1 commit
  2. 20 Oct, 2014 1 commit
  3. 11 Sep, 2014 1 commit
  4. 25 Aug, 2014 1 commit
  5. 22 Aug, 2014 1 commit
    • rossberg@chromium.org's avatar
      test/test262: update testcfg.py for new test262 · cc07503b
      rossberg@chromium.org authored
      testcfg.py:
      
      - update revision and MD5
      - remove non-mandatory harness files
      - use test parser distributed with test262
      - new attribute `suite.harnesspath`
      - new method GetIncludesForTest
      - GetSourceForTest: cache source on testcase
      - IsNegativeTest: use parseTestRecord
      - use 7-char sha hash [1]
      - DRY setting up paths to test262 suite, harness, etc
      - clean up helper fns
      
      harness-adapter.js:
      
      - add $DONE function to adapter [2]
      
      1: github tar file has 7-char sha embedded in dir name
      script cannot find directory to rename if they don't match exactly
      
      2: test262 uses a `$DONE` function for async tests with
      semantics like those of mocha's `done`.
      
      Briefly: done(arg) => if (arg) { /* failure */ }
      
      Implemented a version of this for v8, using v8-specific
      api (`print`, `quit`)
      
      BUG=v8:3513
      LOG=N
      R=jkummerow@chromium.org
      
      Review URL: https://codereview.chromium.org/478163002
      
      git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23313 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      cc07503b
  6. 21 May, 2014 1 commit
  7. 28 Feb, 2014 2 commits
  8. 20 Sep, 2013 1 commit
  9. 19 Sep, 2013 1 commit
  10. 10 May, 2013 1 commit
  11. 18 Apr, 2013 1 commit
  12. 15 Nov, 2012 2 commits
  13. 24 Sep, 2012 1 commit
  14. 05 Jun, 2012 1 commit
  15. 11 May, 2012 1 commit
  16. 16 Apr, 2012 1 commit
  17. 13 Apr, 2012 1 commit
  18. 28 Mar, 2012 1 commit
  19. 07 Mar, 2012 1 commit
  20. 16 Dec, 2011 1 commit
  21. 07 Oct, 2011 1 commit
  22. 26 Jul, 2011 1 commit
  23. 23 Mar, 2011 1 commit
  24. 21 Mar, 2011 1 commit
  25. 10 Jan, 2011 1 commit
    • ricow@chromium.org's avatar
      Enable sharding of individual testsuites in tools/test.py · b4ea8c7f
      ricow@chromium.org authored
      This patch enables two new flags for the tools/test.py script;
      --shard-count - giving the ability to split the tests to be run
      into shard-count chunks.
      --shard-run - giving the ability to specify which of the shards to actually run.
      
      Example
        tools/test.py -j15 --shard-count=2 --shard-run=1 mozilla
      would split the mozilla tests into two chunks and run the tests in the first chunk
      
      Running:
        tools/test.py -j15 --shard-count=2 --shard-run=1 mozilla
        tools/test.py -j15 --shard-count=2 --shard-run=2 mozilla
      is equivalent (in terms of test coverage) of just running:
        tools/test.py -j15 mozilla
      
      In addition, tests are now sorted before they are returned from the
      test specific ListTests methods (sputnik and mozilla tests where
      already sorted before they where returned).
      
      This change is needed to split a single test suite over two slaves on
      the waterfall.
      
      
      Review URL: http://codereview.chromium.org/6127003
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@6248 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      b4ea8c7f
  26. 24 Aug, 2010 1 commit
  27. 15 Sep, 2009 1 commit
  28. 03 Dec, 2008 1 commit
  29. 09 Sep, 2008 1 commit
  30. 08 Sep, 2008 1 commit
  31. 29 Aug, 2008 1 commit
  32. 28 Aug, 2008 1 commit
  33. 27 Aug, 2008 2 commits