1. 30 Jun, 2022 1 commit
  2. 28 Jun, 2022 1 commit
  3. 27 Jun, 2022 1 commit
  4. 20 Jun, 2022 1 commit
  5. 15 Jun, 2022 1 commit
  6. 11 May, 2022 1 commit
  7. 10 May, 2022 1 commit
    • Michael Achenbach's avatar
      Revert "[maglev] Turn on fuzzing for --maglev" · 7e9715d8
      Michael Achenbach authored
      This reverts commit b8b7a3a2.
      
      Reason for revert:
      https://crbug.com/1324097
      https://crbug.com/v8/12859
      
      Let's maybe only reland the clusterfuzz_trials part until the rest
      is sorted out.
      
      Original change's description:
      > [maglev] Turn on fuzzing for --maglev
      >
      > Turn on fuzzing for Maglev to get additional test coverage.
      >
      > Bug: v8:7700
      > Change-Id: I5b72d851639e31dff1bd91361cd81ad448c2d69e
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3629334
      > Auto-Submit: Jakob Linke <jgruber@chromium.org>
      > Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      > Reviewed-by: Toon Verwaest <verwaest@chromium.org>
      > Reviewed-by: Michael Achenbach <machenbach@chromium.org>
      > Cr-Commit-Position: refs/heads/main@{#80416}
      
      Bug: v8:7700, chromium:1324097, v8:12859
      Change-Id: I926319988c3b9a2bc6dd083c69691a6536838782
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3634963
      Auto-Submit: Michael Achenbach <machenbach@chromium.org>
      Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
      Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
      Cr-Commit-Position: refs/heads/main@{#80440}
      7e9715d8
  8. 09 May, 2022 1 commit
  9. 03 May, 2022 1 commit
  10. 22 Apr, 2022 1 commit
  11. 19 Apr, 2022 1 commit
  12. 04 Apr, 2022 2 commits
  13. 29 Mar, 2022 1 commit
  14. 14 Mar, 2022 1 commit
  15. 18 Feb, 2022 2 commits
  16. 15 Feb, 2022 1 commit
  17. 07 Feb, 2022 2 commits
  18. 28 Jan, 2022 1 commit
  19. 12 Nov, 2021 1 commit
  20. 21 Oct, 2021 1 commit
  21. 13 Oct, 2021 1 commit
  22. 31 Aug, 2021 1 commit
    • Michael Achenbach's avatar
      [js-fuzzer] Make db more robust to failing code fragments. · 0ffc1ba5
      Michael Achenbach authored
      Until now, the cross-over mutator would choke on several expressions
      from DB and bail out (just wastes some time). We also have a script,
      test_db.js to test on how many expressions it is going to bail out.
      
      With this change, we already omit adding such expressions to the
      DB in the first place. As a result, the test_db script now returns
      zero failing expressions (while all other expressions remain).
      
      Regression tests that now no longer apply are removed, instead a
      test is added that ensures that a failing expression isn't added
      to the DB.
      
      No-Try: true
      Bug: chromium:1044942
      Change-Id: I14a4fe802c99114cf3a8f71188273475a7cb9c13
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3129340Reviewed-by: 's avatarLiviu Rau <liviurau@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#76598}
      0ffc1ba5
  23. 30 Aug, 2021 3 commits
  24. 28 Aug, 2021 1 commit
  25. 18 Aug, 2021 1 commit
  26. 16 Aug, 2021 1 commit
  27. 12 Aug, 2021 1 commit
  28. 01 Jun, 2021 1 commit
  29. 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
  30. 12 Apr, 2021 1 commit
  31. 22 Mar, 2021 1 commit
  32. 19 Mar, 2021 1 commit
  33. 10 Mar, 2021 1 commit
  34. 12 Feb, 2021 1 commit
  35. 01 Dec, 2020 1 commit
    • Michael Achenbach's avatar
      Reland "Enable simulating errors to test fuzzer reliability" · 886d7cfe
      Michael Achenbach authored
      This is a reland of 4ad08c82
      
      The reland organizes the different error types in separate functions
      for separate call stacks. Error simulation is also guarded by
      a minimum file size to prevent Clusterfuzz from getting stuck with
      its bad-build check.
      
      Original change's description:
      > Enable simulating errors to test fuzzer reliability
      >
      > This adds a d8 flag --simulate-errors, which on shutdown will cause
      > certain errors. This enables testing the reliability of sanitizers.
      >
      > This will cause a fatal error, a dcheck (if available) or a
      > violation that can be detected with one of the following sanitizers:
      > ASAN, UBSAN, MSAN, CFI.
      >
      > The same flag used in differential fuzzing will cause an error
      > subsumed with the error state "fake_difference".
      >
      > Bug: chromium:1152412
      > Change-Id: I4b36c6fe716797004d634263617d22ca67b05600
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2554999
      > Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      > Reviewed-by: Clemens Backes <clemensb@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#71430}
      
      Bug: chromium:1152412
      Change-Id: I604258b4c1ebd215c26b1de6b2822663f857bf64
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2565125
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Reviewed-by: 's avatarClemens Backes <clemensb@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#71538}
      886d7cfe