1. 29 Jun, 2020 1 commit
    • Ng Zhi An's avatar
      [Py3] Get python scripts in tools closer to Py3 · 4af3f7be
      Ng Zhi An authored
      This modernizes python code without breaking Py2 compat.
      
      Ran with command:
      
      futurize --stage1 -w predictable_wrapper.py
      futurize --stage1 -w run-num-fuzzer.py
      futurize --stage1 -w run-tests.py
      futurize --stage1 -w v8_presubmit.py
      
      This only adds the absolute import, which use these semantics. It
      doesn't do anything differently in our case, these scripts are already
      doing absolute imports. But with these changes, running `futurize
      --stage2` will be less messy.
      
      Bug: v8:9871
      Change-Id: I28182ab73dac6cfcbd544c2046026f14e5157eb3
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2252555Reviewed-by: 's avatarTamer Tas <tmrts@chromium.org>
      Commit-Queue: Zhi An Ng <zhin@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#68588}
      4af3f7be
  2. 19 Jan, 2018 1 commit
  3. 10 Nov, 2017 1 commit
  4. 13 Oct, 2017 1 commit
  5. 11 Oct, 2017 1 commit
  6. 25 Jul, 2017 1 commit
  7. 13 Jul, 2017 3 commits
  8. 12 Jul, 2017 1 commit
    • Camillo Bruni's avatar
      Reland "[mjsunit] Improve mjsunit stracktrace readability" · 34874b3b
      Camillo Bruni authored
      This is a reland of f720d024
      Original change's description:
      > [mjsunit] Improve mjsunit stracktrace readability
      > 
      > Format the function name and file-position into proper columns to easily spot
      > where the test code ends and the mjsunit framework code starts.
      > 
      > BEFORE:
      > Stack: Error
      >     at new MjsUnitAssertionError (test/mjsunit/mjsunit.js:36:18)
      >     at failWithMessage (test/mjsunit/mjsunit.js:310:11)
      >     at fail (test/mjsunit/mjsunit.js:327:12)
      >     at assertEquals (test/mjsunit/mjsunit.js:398:7)
      >     at closure (test/mjsunit/regress/regress-4121.js:20:7)
      >     at literals_sharing_test (test/mjsunit/regress/regress-4121.js:27:3)
      >     at test (test/mjsunit/regress/regress-4121.js:37:5)
      >     at eval (eval at <anonymous> (test/mjsunit/regress/regress-4121.js:49:6), <anonymous>:1:1)
      >     at test/mjsunit/regress/regress-4121.js:49:6
      >     at Array.forEach.call (test/mjsunit/regress/regress-4121.js:50:7)
      >     throw new MjsUnitAssertionError(message);
      > 
      > AFTER:
      > Stack: MjsUnitAssertionError
      >     at assertEquals          test/mjsunit/mjsunit.js 398:7
      >     at closure               test/mjsunit/regress/regress-4121.js 20:7
      >     at literals_sharing_test test/mjsunit/regress/regress-4121.js 27:3
      >     at test                  test/mjsunit/regress/regress-4121.js 37:5
      >     at eval                  eval at <anonymous> (test/mjsunit/regress/regress-4121.js:49:6)
      >     at                       test/mjsunit/regress/regress-4121.js 49:6
      >     at Array.forEach.call    test/mjsunit/regress/regress-4121.js 50:7
      >     throw new MjsUnitAssertionError(message);
      > 
      > 
      > Change-Id: Iad3460a648e26effb43c00426ab043743ee6a138
      > Reviewed-on: https://chromium-review.googlesource.com/563627
      > Reviewed-by: Michael Achenbach <machenbach@chromium.org>
      > Reviewed-by: Igor Sheludko <ishell@chromium.org>
      > Commit-Queue: Camillo Bruni <cbruni@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#46589}
      
      Change-Id: I44bf07f7be4114369315605542cafd17345b4397
      Reviewed-on: https://chromium-review.googlesource.com/567063Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Commit-Queue: Camillo Bruni <cbruni@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#46602}
      34874b3b
  9. 02 Dec, 2016 1 commit
    • mstarzinger's avatar
      [compiler] Make --debug-code the default in debug builds. · 651c1b86
      mstarzinger authored
      This enables {FLAG_debug_code} by default in debug builds. The advantage
      is that generated code contained within the snapshot will contain such
      debug code. Before we would only get coverage for these pieces with the
      no-snapshot builds, which have a meager coverage. One can still pass the
      inverse --no-debug-code flag to ensure generated code remains readable
      within debug builds as well.
      
      R=machenbach@chromium.org
      
      Review-Url: https://codereview.chromium.org/2528913002
      Cr-Commit-Position: refs/heads/master@{#41451}
      651c1b86
  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. 01 Aug, 2016 1 commit
  12. 12 Jul, 2016 1 commit
  13. 26 Apr, 2016 1 commit
  14. 15 Mar, 2016 1 commit
  15. 10 Mar, 2016 1 commit
  16. 08 Mar, 2016 1 commit
    • machenbach's avatar
      [coverage] Enable sanitizer coverage. · 33ffced5
      machenbach authored
      This adds sanitizer-coverage compilation, test-runner
      features and post processing.
      
      Sanitizer coverage is expected to be used together with
      asan.
      
      During test runner execution, the produced sancov files
      are disambiguated and match the pattern:
      <executable name>.test.<test id>.sancov.
      
      Two additional scripts are added for merging raw sancov
      files and for generating json data containing all
      instrumented lines + all covered lines from merged sancov
      files. Both scripts use multiprocessing for speed.
      
      The json data will later be uploaded to google storage
      for further use, e.g. to show coverage data in rietveld.
      
      Sancov documentation:
      http://clang.llvm.org/docs/SanitizerCoverage.html
      
      BUG=chromium:568949
      LOG=n
      NOTRY=true
      TEST=python -m unittest sancov_formatter_test
      TEST=python -m unittest sancov_merger_test
      
      Review URL: https://codereview.chromium.org/1737263003
      
      Cr-Commit-Position: refs/heads/master@{#34578}
      33ffced5
  17. 18 Feb, 2016 1 commit
  18. 14 Dec, 2015 1 commit
  19. 27 Nov, 2015 1 commit
  20. 23 Nov, 2015 1 commit
  21. 06 Nov, 2015 1 commit
  22. 17 Sep, 2015 1 commit
  23. 07 Aug, 2015 1 commit
  24. 23 Jun, 2015 1 commit
  25. 30 Jan, 2015 1 commit
  26. 20 Jan, 2015 1 commit
  27. 16 Jan, 2015 1 commit
  28. 05 Dec, 2014 1 commit
  29. 22 Oct, 2014 1 commit
  30. 23 Jul, 2014 1 commit
  31. 08 Jul, 2014 1 commit
  32. 02 Jul, 2014 1 commit
  33. 28 May, 2014 1 commit
  34. 15 May, 2014 1 commit
  35. 10 Apr, 2014 1 commit
  36. 09 Apr, 2014 1 commit
  37. 25 Feb, 2014 1 commit
  38. 31 Jan, 2014 1 commit