Skip to content

V
V8
Switch branch/tag
  1. 16 Mar, 2016 1 commit
    • machenbach's avatar
      [test] Remove feature to mark flaky tests. · 7f363d5d
      machenbach authored 
      The feature was removed from the bots a while ago. It was
superseeded by the flaky-test detection which reruns tests.

Remaining tests still marked as flaky most certainly pass
since a while.

Referencing all the bugs whose expectations lines get
removed by this.

BUG=v8:3838,v8:3525,v8:3125
LOG=n

Review URL: https://codereview.chromium.org/1802983002

Cr-Commit-Position: refs/heads/master@{#34804}
      7f363d5d
  3. 15 Mar, 2016 1 commit
  5. 14 Mar, 2016 1 commit
  7. 11 Mar, 2016 1 commit
  9. 10 Mar, 2016 1 commit
  11. 09 Mar, 2016 1 commit
  13. 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
  15. 26 Jan, 2016 1 commit
  17. 14 Jan, 2016 1 commit
  19. 05 Jan, 2016 1 commit
  21. 04 Jan, 2016 1 commit
    • machenbach's avatar
      [test] Add ignition test set. · ee665067
      machenbach authored 
      Add control for the ignition test suites. This will be
followed by a change on the infra side that targets the
ignition set instead of the hardcoded mjsunit.

After that, cctest can be enabled in a separate CL. This CL
already includes the logic for running cctest for ignition
on swarming.

BUG=v8:4280
LOG=N

Review URL: https://codereview.chromium.org/1559943002

Cr-Commit-Position: refs/heads/master@{#33089}
      ee665067
  23. 14 Dec, 2015 1 commit
  25. 27 Nov, 2015 1 commit
  27. 23 Nov, 2015 1 commit
  29. 06 Nov, 2015 1 commit
  31. 03 Nov, 2015 1 commit
    • machenbach's avatar
      [Swarming] Let test runner exit gracefully after test failures. · efcc7fb2
      machenbach authored 
      The flake detection is done on the infra-side according to
the contents of the json test results. We don't want the
runner to fail after flakes.

This was controlled on the infra side by accepting any exit
codes so far. After the swarming switch, this is more
difficult, because the runner is wrapped by the swarming
collect script. There, failing exit codes can mean many
things, including network failures. Therefore, we now
force exit code 0 with test failures if those failures
are reported in the formal test results json.

The infrastructure will take care of reporting the flakes
and failures accordingly.

BUG=chromium:535160
LOG=n

Review URL: https://codereview.chromium.org/1416373005

Cr-Commit-Position: refs/heads/master@{#31740}
      efcc7fb2
  33. 30 Oct, 2015 1 commit
  35. 20 Oct, 2015 1 commit
  37. 19 Oct, 2015 2 commits
  39. 16 Oct, 2015 1 commit
  41. 15 Oct, 2015 1 commit
  43. 12 Oct, 2015 1 commit
  45. 06 Oct, 2015 1 commit
    • machenbach's avatar
      [swarming] Run unittests together with default tests. · 35d2028d
      machenbach authored 
      This adds the unittests to the "default" test set. Now that
the "default" and the DEFAULT_TESTS (i.e. runner with
no arguments) are the same, removed DEFAULT_TESTS and use
TEST_MAP["default"] instead.

On the bots, where unittests and default were run in
separation before, the explicit unittests step should now
be skipped.

This is necessary for swarming, as the unittests step is
too small to justify its own swarming job.

BUG=chromium:535160
LOG=n

Review URL: https://codereview.chromium.org/1374733006

Cr-Commit-Position: refs/heads/master@{#31122}
      35d2028d
  47. 02 Oct, 2015 1 commit
  49. 29 Sep, 2015 2 commits
  51. 17 Sep, 2015 1 commit
  53. 11 Aug, 2015 1 commit
  55. 10 Aug, 2015 3 commits
  57. 07 Aug, 2015 1 commit
  59. 06 Aug, 2015 1 commit
  61. 29 Jul, 2015 2 commits
  63. 13 Jul, 2015 1 commit
  65. 23 Jun, 2015 1 commit
  67. 11 Jun, 2015 1 commit
  69. 10 Jun, 2015 1 commit