1. 03 May, 2022 1 commit
  2. 14 Mar, 2022 1 commit
  3. 07 Feb, 2022 1 commit
  4. 12 Nov, 2021 1 commit
  5. 17 May, 2021 1 commit
    • Michael Achenbach's avatar
      [foozzie] Prioritize reporting differences with x64 if present · 8590942c
      Michael Achenbach authored
      tldr: This adds an on-demand comparison with x64 when a difference to
      a non-x64 build is detected.
      
      Normally foozzie compares the baseline build (just ignition), with
      two secondary builds. One, the default, always uses the shipping
      configuration, the second passes additional flags. Both can use a
      different architecture than the baseline build as well.
      
      Differences between ignition and turbofan are then often detected
      independent of the architectures used, but reported several times
      (for each compared architecture).
      
      This makes the reporting more specific, by running another build on
      demand that uses the baseline architecture, but otherwise the same
      configuration that showed a difference. If it shows the difference as
      well, the baseline architecture is used for the report.
      
      As a result only pure architecture differences will be reported with
      an architecture other than x64.
      
      This also adds some minor refactorings to reduce the code complexity
      when looping over comparisons.
      
      For testing this, the fake-d8s are extended with different behavior
      for different flags passed. We add two test cases for testing:
      x64 vs. ia32 with difference in x64 and ia32
      x64 vs. ia32 with difference only in ia32
      
      Bug: chromium:1196633
      No-Try: true
      Test: tools/clusterfuzz/v8_foozzie_test.py
      Change-Id: Ic470ae8f0b37fb1628b32e4fafc0c39377e16f8c
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2897099Reviewed-by: 's avatarLiviu Rau <liviurau@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#74612}
      8590942c
  6. 27 Nov, 2020 1 commit
  7. 29 Jun, 2020 1 commit
    • Michael Achenbach's avatar
      [foozzie] Align running main comparisons and smoke tests · ca674858
      Michael Achenbach authored
      This shares the code of running the comparisons on the fuzz test
      and on the smoke tests. While this change retains behavior for running
      the fuzz test, the smoke test has slight changes in favor of code
      readability:
      
      1. Smoke tests can now bail out on output suppressions (There are
      none now. And if we'd ever add any we'd need to write them in a way,
      such that they ignore the output of the smoke tests, which don't
      have much output anyways).
      2. Crashes in smoke tests are now a hard failure. This is a desired
      feature anyways. It's unlikely that the smoke test crashes as then
      nothing would work.
      
      No-Try: true
      Bug: chromium:1100114
      Change-Id: Ice3c6d18b549727c486a70756a72038c8b2029ac
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2273125
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Reviewed-by: 's avatarLiviu Rau <liviurau@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#68586}
      ca674858
  8. 20 Apr, 2020 1 commit
  9. 31 Jan, 2020 1 commit
  10. 02 Sep, 2019 1 commit
  11. 12 Jul, 2019 1 commit
  12. 06 May, 2019 1 commit
  13. 03 Apr, 2019 1 commit
  14. 18 Mar, 2019 1 commit
  15. 28 Feb, 2019 1 commit
  16. 19 Jul, 2018 2 commits
  17. 06 Apr, 2018 1 commit
  18. 22 Feb, 2018 1 commit
  19. 15 Jan, 2018 1 commit
    • Michael Achenbach's avatar
      [foozzie] Add flag experiments for gc fuzzing · 74a2a8f6
      Michael Achenbach authored
      This will add three gc fuzzing flags with 5% likelihood each to the second
      correctness fuzzing config. The random checks are determined by the
      top-level random-seed passed to the script.
      
      This change depends on setting the fuzzer random seed as default to the
      standard random seed, since the former isn't explicitly passed by
      clusterfuzz.
      
      NOTRY=true
      TBR=hpayer@chromium.org
      
      Bug: v8:7012
      Change-Id: I794dc48bb953b6a95bbc4fc4305ad561bc13b6ee
      Reviewed-on: https://chromium-review.googlesource.com/865912Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#50577}
      74a2a8f6
  20. 24 Oct, 2017 1 commit
  21. 31 Jul, 2017 1 commit
  22. 10 Jul, 2017 1 commit
  23. 15 May, 2017 1 commit
  24. 14 Mar, 2017 1 commit
  25. 10 Mar, 2017 1 commit
  26. 03 Feb, 2017 1 commit
  27. 18 Jan, 2017 1 commit
  28. 16 Jan, 2017 1 commit
  29. 13 Jan, 2017 2 commits
  30. 20 Dec, 2016 2 commits