- 10 Jul, 2020 1 commit
-
-
Adam Klein authored
Bug: v8:10619 Change-Id: I644c3421085b029aaf9b4de3b262ca8a4734539e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2292916Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#68812}
-
- 19 Feb, 2019 1 commit
-
-
Vadim Gorbachev (bmsdave) authored
There are now less that 400 days until the end of life of Python 2(aka _legacy_ Python) https://pythonclock.org/ . The code compatibility check for python2 and python3 used the following tools: futurize, flake8 You can see the reports here: https://travis-ci.com/bmsdave/v8/builds This CL was uploaded by git cl split. Bug: v8:8594 Change-Id: I661c52a70527e8ddde841fee6d4dcba282b4a938 Reviewed-on: https://chromium-review.googlesource.com/c/1470123 Commit-Queue: Sergiy Belozorov <sergiyb@chromium.org> Reviewed-by: Sergiy Belozorov <sergiyb@chromium.org> Cr-Commit-Position: refs/heads/master@{#59675}
-
- 04 Nov, 2018 1 commit
-
-
Jungshik Shin authored
ICU 63.1 fixed it and v8's ICU was rolled to ICU 63.1 TBR=sigurds@chromium.org Bug: v8:8110 Change-Id: Ic44c8f4293d6d39b597a90318f0acbf5aea6eccf Reviewed-on: https://chromium-review.googlesource.com/c/1316615Reviewed-by: Jungshik Shin <jshin@chromium.org> Commit-Queue: Jungshik Shin <jshin@chromium.org> Cr-Commit-Position: refs/heads/master@{#57227}
-
- 10 Oct, 2018 1 commit
-
-
Maya Lekova authored
Bug: v8:8110 Change-Id: I5d180782aed530b059978d4d594df91aa472656a Reviewed-on: https://chromium-review.googlesource.com/c/1273015Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Maya Lekova <mslekova@chromium.org> Cr-Commit-Position: refs/heads/master@{#56507}
-
- 31 Aug, 2018 1 commit
-
-
Sathya Gunasekaran authored
Bug: v8:8110 Change-Id: I7531ca961d0a0ed612ea3571c2bbef290b87c035 Reviewed-on: https://chromium-review.googlesource.com/1196689Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Cr-Commit-Position: refs/heads/master@{#55559}
-
- 25 Oct, 2017 1 commit
-
-
Michael Lippautz authored
This reverts commit e26cd874. Reason for revert: The issue has been fixed. See related bug for description and CLs. Original change's description: > [heap] Add TSAN suppression for lock-order inversion in Scavenger > > The Scavenger currently requires taking the lock for OLD->NEW processing > and can also take another lock for sweeping a different page. > > Since order of pages during scavenge and sweep is unstable this may > result in lock order inversion reports on TSAN when long-running > programms are only executed on a single thread. > > The report is a false positve, hence flag it as suppression until we > redesign this particular piece. > > No-try: true > Bug: v8:6923 > Change-Id: I82355be1c8d83ea61cc21152aeb10b58b1dc4b86 > Reviewed-on: https://chromium-review.googlesource.com/716261 > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Commit-Queue: Michael Lippautz <mlippautz@chromium.org> > Cr-Commit-Position: refs/heads/master@{#48504} # Not skipping CQ checks because original CL landed > 1 day ago. Bug: v8:6923 Change-Id: I7711466c6e2175dcab8d64d6a642e458e1cde3f5 Reviewed-on: https://chromium-review.googlesource.com/738110Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Hannes Payer <hpayer@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#48913}
-
- 12 Oct, 2017 1 commit
-
-
Michael Lippautz authored
The Scavenger currently requires taking the lock for OLD->NEW processing and can also take another lock for sweeping a different page. Since order of pages during scavenge and sweep is unstable this may result in lock order inversion reports on TSAN when long-running programms are only executed on a single thread. The report is a false positve, hence flag it as suppression until we redesign this particular piece. No-try: true Bug: v8:6923 Change-Id: I82355be1c8d83ea61cc21152aeb10b58b1dc4b86 Reviewed-on: https://chromium-review.googlesource.com/716261Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#48504}
-
- 27 Jun, 2017 2 commits
-
-
Michael Achenbach authored
This'll make the workflow more flexible as in GN world, the builddir is often not in the currently hardcoded out/Release. NOTRY=true Bug: chromium:645890 Change-Id: Id2afc8d8fea322ac98b65b7e9d28a2ba8c0dd0ac Reviewed-on: https://chromium-review.googlesource.com/549899 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#46258}
-
Michael Achenbach authored
This broke after https://codereview.chromium.org/2860653002 NOTRY=true TBR=ochang@chromium.org,jarin@chromium.org Bug: v8:5502 Change-Id: I062f6601da0b8249d7749275fc415a72e42d0e40 Reviewed-on: https://chromium-review.googlesource.com/549931 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#46248}
-
- 14 Oct, 2016 1 commit
-
-
machenbach authored
This differentiates sancov files from several runs of the same test. This situation happens when a test fails and is rerun for flake checking. BUG=v8:5502 Review-Url: https://codereview.chromium.org/2414093003 Cr-Commit-Position: refs/heads/master@{#40304}
-
- 21 Mar, 2016 1 commit
-
-
machenbach authored
Unittest for feature added in: https://codereview.chromium.org/1808663002/ BUG=chromium:568949 LOG=n NOTRY=true Review URL: https://codereview.chromium.org/1810043004 Cr-Commit-Position: refs/heads/master@{#34923}
-
- 16 Mar, 2016 1 commit
-
-
machenbach authored
This will allow to only load json data for the files under review instead of the whole data set. This will be called on the infra-side after all coverage data has been merged. Also fix a bunch of log lines. BUG=chromium:568949 LOG=n NOTRY=true Review URL: https://codereview.chromium.org/1808663002 Cr-Commit-Position: refs/heads/master@{#34834}
-
- 10 Mar, 2016 1 commit
-
-
machenbach authored
This adds a function to the sancov_merger that merges the output files of one swarming shard in parallel. This will be called from the infrastructure when collecting/merging swarming results. The tool will be called subsequently for each shard. On the first call, the target dir will be empty and the sancov files will just be moved. BUG=chromium:568949 LOG=n NOTRY=true Review URL: https://codereview.chromium.org/1782843002 Cr-Commit-Position: refs/heads/master@{#34678}
-
- 08 Mar, 2016 1 commit
-
-
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}
-
- 09 Oct, 2014 2 commits
-
-
jochen@chromium.org authored
TBR=machenbach@chromium.org LOG=n BUG=none Review URL: https://codereview.chromium.org/646493002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24487 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jochen@chromium.org authored
Also suppress a deliberate lock cycle in test-lockers BUG=none R=glider@chromium.org, machenbach@chromium.org LOG=n Review URL: https://codereview.chromium.org/642023002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24484 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-