- 11 Nov, 2019 1 commit
-
-
Liviu Rau authored
When a test fails the exit code of the process is printed in the logs in the decimal format. On Windows searching for the actual error is pretty difficult in this format since we are dealing with negative values errors. We print now the hex format of the same exit value next to the original one. Example failure of a test: https://ci.chromium.org/p/v8/builders/try/v8_win64_dbg/b8897355488287117696 https://logs.chromium.org/logs/v8/buildbucket/cr-buildbucket.appspot.com/8897355488287117696/+/steps/Check/0/stdout https://logs.chromium.org/logs/v8/buildbucket/cr-buildbucket.appspot.com/8897355488287117696/+/steps/Check/0/logs/RunWasmInterpreter_Int32Const_many/0 Bug: v8:9810 Change-Id: I51b65d6105bda6516707a764dbd41fd36c9dfc80 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1903975 Commit-Queue: Liviu Rau <liviurau@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Tamer Tas <tmrts@chromium.org> Cr-Commit-Position: refs/heads/master@{#64878}
-
- 23 Apr, 2019 1 commit
-
-
Sergiy Belozorov authored
This is part of the refactoring to allow exporting more information about test execution to the recipes and upload this information to ChromePerf. This fixes running secondary even after primary run fails, which will allow us to differentiate between test and infra failures as latter ones will also affect refbuilds and re-runs without patch. R=machenbach@chromium.org, tmrts@chromium.org Bug: chromium:841700 Change-Id: I29ce49d2f8c5e73158f1d41a73c51f2b35929f36 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1570006 Commit-Queue: Sergiy Belozorov <sergiyb@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#60946}
-
- 23 Jan, 2018 1 commit
-
-
Michal Majewski authored
Since we're not winning anything by changing the result between processors on the main process, reduce is noop there and result is immutable. Bug: v8:6917 Change-Id: Ieb282e7abd4ab31162aee6b52493a6e1b6a25109 Cq-Include-Trybots: luci.v8.try:v8_linux64_fyi_rel_ng Reviewed-on: https://chromium-review.googlesource.com/878239 Commit-Queue: Michał Majewski <majeski@google.com> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#50784}
-
- 15 Dec, 2017 1 commit
-
-
Michal Majewski authored
Bug: v8:6917 Change-Id: Ifc3dac7a82fa67dda1f8b166fbd3f76a123ffba2 Reviewed-on: https://chromium-review.googlesource.com/824365 Commit-Queue: Michał Majewski <majeski@google.com> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Sergiy Byelozyorov <sergiyb@chromium.org> Cr-Commit-Position: refs/heads/master@{#50122}
-
- 09 Nov, 2017 1 commit
-
-
Michal Majewski authored
Bug: v8:6917 Change-Id: I7dae0715264cdf9f963f2454b101f6260d8493ff Reviewed-on: https://chromium-review.googlesource.com/758837Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michał Majewski <majeski@google.com> Cr-Commit-Position: refs/heads/master@{#49256}
-
- 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}
-
- 10 Jul, 2014 1 commit
-
-
machenbach@chromium.org authored
This also adds an assert that makes sure allocations are printed. BUG=391747 LOG=n R=ishell@chromium.org Review URL: https://codereview.chromium.org/377213005 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22313 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 08 Jul, 2014 1 commit
-
-
machenbach@chromium.org authored
BUG=391747 LOG=n R=ishell@chromium.org Review URL: https://codereview.chromium.org/371363003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22285 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 24 Sep, 2012 1 commit
-
-
jkummerow@chromium.org authored
Review URL: https://codereview.chromium.org/10919265 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@12583 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 08 Feb, 2012 1 commit
-
-
jkummerow@chromium.org authored
TEST="out/ia32.release/d8 te<tab>" gets completed to "test/" with trailing slash Review URL: https://chromiumcodereview.appspot.com/9363025 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10649 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 07 Feb, 2012 1 commit
-
-
yangguo@chromium.org authored
Review URL: https://chromiumcodereview.appspot.com/9346017 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10623 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 06 Feb, 2012 1 commit
-
-
jkummerow@chromium.org authored
Review URL: https://chromiumcodereview.appspot.com/9307122 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10612 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 07 Apr, 2011 1 commit
-
-
vegorov@chromium.org authored
GCMole is a simple static analysis tool that searches for GC-usafe evaluation order dependent callsites. Review URL: http://codereview.chromium.org/6812002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@7540 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 29 Mar, 2011 1 commit
-
-
lrn@chromium.org authored
The target doesn't compile yet, due to v8 dependencies introduced by isolates. Review URL: http://codereview.chromium.org/6772002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@7404 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 09 Sep, 2008 1 commit
-
-
christian.plesner.hansen@gmail.com authored
Added presubmit step to check copyright. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@242 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 08 Sep, 2008 1 commit
-
-
sgjesse authored
when the PATH to cl.exe is specified through env overrides. Changed explicit EVN update with call to ApplyEnvOverrides git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@213 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 22 Aug, 2008 1 commit
-
-
christian.plesner.hansen authored
In the shell sample don't print the result of executing a script, only evaluating expressions. Fixed issue when building samples on Windows using a shared V8 library. Added visibility option on Linux build which makes the generated library 18% smaller. Changed build system to accept multiple build modes in one build and generate seperate objects, libraries and executables for each mode. Removed deferred negation optimization (a * -b => -(a * b)) since this visibly changes operand conversion order. Improved parsing performance by introducing stack guard in preparsing. Without a stack guard preparsing always bails out with stack overflow. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@16 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-