- 17 Feb, 2020 1 commit
-
-
Michael Achenbach authored
Pass --no-lazy-feedback-allocation in all second runs depending on a probability. Also combine with --interrupt-budget=100. This also allows adding several extra flags behind one probability. The tests are improved to ensure valid flags and configs. No-Try: true Bug: v8:10215 Change-Id: I2766ef5044cd8c7096f6b76f39b60b568f550bde Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2059991 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by:
Tamer Tas <tmrts@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Mythri Alle <mythria@chromium.org> Cr-Commit-Position: refs/heads/master@{#66289}
-
- 12 Feb, 2020 1 commit
-
-
Michael Achenbach authored
This will allow sharing the configs between Python and JavaScript based fuzzers. No-Try: true Bug: chromium:1044942 Change-Id: Idd47ad31430cfed0629dbb5b9dd5fd2ef8c764f6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2051951Reviewed-by:
Liviu Rau <liviurau@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#66243}
-
- 12 Nov, 2019 1 commit
-
-
Michael Achenbach authored
We used the same random seed for all test cases of a fuzz session for transitioning from choosing the flags on V8 side. Since the grace period for stable bisection is over, we now use the same random number generator throughout the fuzz session which leads to a wider range of differently chosen flags. TBR=tmrts@chromium.org No-Try: true Bug: chromium:813833 Change-Id: I07b9fe5de378c01344afd486bfd85fcbf0fcd8d2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1906377Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#64910}
-
- 08 Nov, 2019 1 commit
-
-
Michael Achenbach authored
No-Try: true Bug: chromium:1021463 Change-Id: I15d45a51b7341b5767d8eb4c16e7d41508a2811b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1906568Reviewed-by:
Clemens Backes <clemensb@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#64862}
-
- 06 Nov, 2019 1 commit
-
-
Michael Achenbach authored
NOTRY=true Bug: v8:9946 Change-Id: If5b5470709edeaa13f7dea4ca83948e28356f352 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1901268Reviewed-by:
Georg Neis <neis@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#64810}
-
- 07 Oct, 2019 1 commit
-
-
Michael Achenbach authored
This adds a fake toolchain for pointer compression, used for correctness fuzzing. The toolchain enables us to have an extra build with inverse pointer-compression defaults side-by-side. The extra build is used similarly to existing x64/x86 comparisons, except that we now compare builds with different compile-time flags. Change-Id: I75491371262204b86eaa006ca8d04848f49121ac Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1829275Reviewed-by:
Tamer Tas <tmrts@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#64123}
-
- 30 Sep, 2019 2 commits
-
-
Michael Achenbach authored
NOTRY=true Change-Id: Icb4c3a1a544331baab5d6637daa12bea87044715 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1829268 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#64038}
-
Michael Achenbach authored
NOTRY=true Change-Id: Ie96e645851beb26e9a777379ad68f1c173acd80d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1829266Reviewed-by:
Clemens Backes [né Hammacher] <clemensb@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#64036}
-
- 12 Jul, 2019 1 commit
-
-
Michael Achenbach authored
NOTRY=true Bug: chromium:813833,chromium:983128 Change-Id: I449796b761f53bb15a3563604d5a4a9018035cb6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1697255Reviewed-by:
Tamer Tas <tmrts@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#62662}
-
- 11 Jul, 2019 1 commit
-
-
Michael Achenbach authored
In order to migrate the extra flags into the fuzzer and keep bisection stable, we need to use the same RNG state for each call to generating fuzz flags. Throughout one fuzzing session the same random-seed is used (https://crbug.com/983128) and we'll pass it to the fuzz config in a follow up. TBR=tmrts@chromium.org NOTRY=true Bug: chromium:813833 Change-Id: I3203c86028a5d283238e6ef739f82eccee1302b1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1697254 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#62646}
-
- 17 Jun, 2019 1 commit
-
-
Michael Achenbach authored
We have too many dupes in the no-ic comparisons. We'll increase the experiment size again once bugs are fixed. TBR=jarin@chromium.org NOTRY=true Bug: chromium:961709 Change-Id: Ic946100b45fd73e1bee59f188a766384836bcdcf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1660624Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#62212}
-
- 22 May, 2019 1 commit
-
-
Michael Achenbach authored
NOTRY=true Bug: v8:9277 Change-Id: If385439e2bdd8146fe3ba5734920b2096b6c1789 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1622853Reviewed-by:
Tamer Tas <tmrts@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#61724}
-
- 04 Feb, 2019 2 commits
-
-
Michael Achenbach authored
NOTRY=true Change-Id: I71c5fbfbb58cd13613506acabf446d9cffc6d23b Reviewed-on: https://chromium-review.googlesource.com/c/1451837Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#59333}
-
Michael Achenbach authored
This replaces the "trusted" with the "jitless" correctness-fuzzing experiment. The former is a no-op already. NOTRY=true Bug: v8:8778 Change-Id: Ie9b490df27071980b2049148844b8f716bbbb1f7 Reviewed-on: https://chromium-review.googlesource.com/c/1450120Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Sergiy Belozorov <sergiyb@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#59313}
-
- 19 Jul, 2018 1 commit
-
-
Clemens Hammacher authored
Instead of having a separate liftoff config, which is tested against the default (which currently means tier-up from liftoff to turbofan), just choose reasonable liftoff configs for the existing configs. 'ignition' now implies pure liftoff execution. 'ignition_turbo_opt' always compiles with turbofan. Other configs use the default (tier up). R=machenbach@chromium.org Bug: chromium:824098, v8:6600 Change-Id: I92c008fc1b1fa54d3161fb5695a095127d6ac263 Reviewed-on: https://chromium-review.googlesource.com/1141731Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#54548}
-
- 21 Mar, 2018 1 commit
-
-
Clemens Hammacher authored
This adds 5% testing of 'ignition' vs 'liftoff', which tests Turbofan vs Liftoff for wasm code, and tests Ignition vs Turbofan for javascript code. It also adds 3% testing of 'liftoff' (x64) vs 'liftoff' (ia32), which does standard x64 vs ia32 testing for javascript code. R=machenbach@chromium.org Bug: chromium:824098, v8:6600 Change-Id: I6a6afae0300efc33f3535541a11695a7bb32dcc5 Reviewed-on: https://chromium-review.googlesource.com/973161 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#52111}
-
- 22 Feb, 2018 1 commit
-
-
Michael Achenbach authored
We'll soon also host other configurations for general fuzzing, not only correctness fuzzing in the new tools/clusterfuzz folder. TBR=yangguo@chromium.org Bug: chromium:813833 Change-Id: Icd966bfec91cc547522bad5d1a842500b554754f Reviewed-on: https://chromium-review.googlesource.com/930331Reviewed-by:
Yang Guo <yangguo@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#51480}
-
- 21 Feb, 2018 1 commit
-
-
Michael Achenbach authored
Before, configurations were chosen on clusterfuzz side. This migrates the choice to the V8 repo, to enable easier changing it and to allow sharing it between different fuzzers. NOTRY=true TBR=sergiyb@chromium.org Bug: chromium:813833 Change-Id: I9890a36fd6aab171d3e13172fc55b274f189e532 Reviewed-on: https://chromium-review.googlesource.com/927681Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#51410}
-