1. 26 Jul, 2022 1 commit
  2. 02 Jun, 2022 1 commit
  3. 08 Oct, 2020 1 commit
  4. 07 Oct, 2020 1 commit
    • Michael Achenbach's avatar
      [test] Overhaul mode processing in test runner · 608b732d
      Michael Achenbach authored
      This simplifies mode processing as follows:
      - Passing the --mode parameter is deprecated.
      - The build output is now only searched in the --outdir parameter
      that was passed (previously some combinations of mode and outdir
      were possible).
      - The mode is deduced from the build artifacts based on the gn
      arguments "is_debug" and "dcheck_always_on".
      - Timeouts and status file entries in release mode with dchecks are
      treated like in debug mode.
      
      This change was prepared on the infrastructure side by deprecating
      the --mode flag and passing --outdir=out/build:
      https://crrev.com/c/2426643
      
      Bug: chromium:1132088, v8:10893
      Change-Id: I0f34ebc003b220f07df4ecdbf69ea6c06ac1f66a
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2450016Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70363}
      608b732d
  5. 05 May, 2020 1 commit
  6. 11 Jul, 2019 1 commit
    • Mythri A's avatar
      Check that function was prepared before optimizing using manually · b086cb7b
      Mythri A authored
      With lazy feedback allocation and bytecode flushing we need to call
      %PrepareFunctionForOptimize before we call %OptimizeFunctionOnNextCall/
      %OptimizeOsr. This cl:
      1. Adds an additional state in pending optimized table to check if the
      optimization was triggered manually.
      2. Changes the compilation pipeline to delete the entry from pending
      optimized table only if the optimization was triggered through
      %OptimizeFunctionOnNextCall / %OptimizeOsr.
      3. Adds a check to enforce %PrepareFunctionForOptimize was called.
      4. Adds a new run-time flag to only check in the d8 test runner. We
      don't want this check enabled in other cases like clusterfuzz that doesn't
      ensure %PrepareFunctionForOptimize is called.
      
      Bug: v8:8394, v8:8801, v8:9183
      Change-Id: I9ae2b2da812e313c746b6df0b2da864c2ed5de51
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1664810
      Commit-Queue: Mythri Alle <mythria@chromium.org>
      Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#62653}
      b086cb7b
  7. 11 Apr, 2019 1 commit
  8. 05 Apr, 2019 1 commit
    • Michael Achenbach's avatar
      [test] Expose variant flags in json output · ff0b9dd3
      Michael Achenbach authored
      For standard test failures, the variant name is enough to deduce the
      full command line of the test. This is used to create the flako
      command line on the infra side.
      
      Test failures from numfuzz have additional variant_flags, calculated
      by the fuzzer, which don't match a variant name. Exposing those in
      the test results will enable printing a proper flako command line
      on infra side for numfuzz cases.
      
      Bug: v8:8971
      Change-Id: Ie47d42a0b34037da458b474f2a9ab38f1a5d238a
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1554689Reviewed-by: 's avatarSergiy Belozorov <sergiyb@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#60656}
      ff0b9dd3
  9. 07 Feb, 2019 1 commit
  10. 31 Jan, 2018 1 commit
    • Michal Majewski's avatar
      Reland "[test] Random seed processor" · 5ede3cb5
      Michal Majewski authored
      This is a reland of 0db74d49.
      
      Original change's description:
      > [test] Random seed processor
      > 
      > 1. --total-timeout-sec now available for ./run-tests.py. It can be
      > useful with infinite seed stressing
      > 2. random seed dropped from the context. Now JSON progress indicator
      > gets it from the list of command args.
      > 
      > Bug: v8:6917
      > Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng
      > Change-Id: I73e535bc8face9b913c696b8d5e3a246fa231004
      > Reviewed-on: https://chromium-review.googlesource.com/888524
      > Commit-Queue: Michał Majewski <majeski@google.com>
      > Reviewed-by: Michael Achenbach <machenbach@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#50964}
      
      Bug: v8:6917
      Change-Id: I1ea376a4abffce5ab65f4834ea7e6d6011765ffa
      Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng
      Reviewed-on: https://chromium-review.googlesource.com/894204Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Commit-Queue: Michał Majewski <majeski@google.com>
      Cr-Commit-Position: refs/heads/master@{#50978}
      5ede3cb5
  11. 30 Jan, 2018 2 commits
  12. 16 Jan, 2018 3 commits