AuroraMiddleware/v8
1
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity
8267c7e12c
v8/tools/clusterfuzz/trials
History
Michael Achenbach 0199cde71f [trials] Add new contradictions after readonly-flags introduction 
No-Try: true
Bug: v8:10577
Change-Id: I9d17d907f900dbb734ed6e6c22bf7a75766082c0
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4154412
Commit-Queue: Jakob Linke <jgruber@chromium.org>
Auto-Submit: Michael Achenbach <machenbach@chromium.org>
Reviewed-by: Jakob Linke <jgruber@chromium.org>
Cr-Commit-Position: refs/heads/main@{#85205}
2023-01-11 10:17:41 +00:00
..
BUILD.gn [clusterfuzz] Split directory structure 2022-02-07 15:38:46 +00:00
clusterfuzz_trials_config.json [trials] Add new contradictions after readonly-flags introduction 2023-01-11 10:17:41 +00:00
PRESUBMIT.py Add flag contradictions for ClusterFuzz and a README 2022-08-02 10:40:37 +00:00
README.md Add flag contradictions for ClusterFuzz and a README 2022-08-02 10:40:37 +00:00

README.md

It is possible to add trials from the source code side by adding the below line to clusterfuzz_trials_config.json:

{
  "app_args": "FLAG_NAME",
  "app_name": "APP_NAME",
  "probability": PROBABILITY,
  "contradicts": ["FLAG1", "FLAG2", ...]
}
  • app_args: the name of the flag we want to add.
  • app_name: the name of the app we are adding the flag for, this must be d8 on V8.
  • probability: the probability of this flag to be selected.
  • contradicts (optional): the flags that contradict the flag referred to in app_args. This will stop flags that contradict each other from being added in the same trial.