1. 05 Jan, 2018 15 commits
  2. 04 Jan, 2018 21 commits
  3. 03 Jan, 2018 4 commits
    • Bill Budge's avatar
      Revert "[test] Move has unexpected output to outproc." · 1685b5d2
      Bill Budge authored
      This reverts commit 71605b3e.
      
      Reason for revert: Seems to break static-initializers step:
      https://build.chromium.org/p/client.v8/builders/V8%20Linux64/builds/22156
      
      Original change's description:
      > [test] Move has unexpected output to outproc.
      > 
      > Expected outcomes optimized to serialize [PASS] as None.
      > 
      > Keeping expected outcomes inside output processors should be
      > optimized in the future. Few possible optimizations:
      > - separate classes for tests that are expected to PASS - done as
      > an example in mozilla test suite.
      > - cache output processors inside testcase.
      > - share output processors between copies of the same test - needs
      > some updates to the create_variant to update outproc only if
      > expected outcomes changed.
      > 
      > Bug: v8:6917
      > Change-Id: Ie73f1dcdf17fdfc65bce27228f818b1dd1e420c9
      > Reviewed-on: https://chromium-review.googlesource.com/843025
      > Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      > Reviewed-by: Michael Achenbach <machenbach@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#50347}
      
      TBR=machenbach@chromium.org,sergiyb@chromium.org,majeski@google.com
      
      Change-Id: Ice1f3aee0a26f7f38996459d38fd6e0bd964113d
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Bug: v8:6917
      Reviewed-on: https://chromium-review.googlesource.com/849572Reviewed-by: 's avatarBill Budge <bbudge@chromium.org>
      Commit-Queue: Bill Budge <bbudge@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#50348}
      1685b5d2
    • Michal Majewski's avatar
      [test] Move has unexpected output to outproc. · 71605b3e
      Michal Majewski authored
      Expected outcomes optimized to serialize [PASS] as None.
      
      Keeping expected outcomes inside output processors should be
      optimized in the future. Few possible optimizations:
      - separate classes for tests that are expected to PASS - done as
      an example in mozilla test suite.
      - cache output processors inside testcase.
      - share output processors between copies of the same test - needs
      some updates to the create_variant to update outproc only if
      expected outcomes changed.
      
      Bug: v8:6917
      Change-Id: Ie73f1dcdf17fdfc65bce27228f818b1dd1e420c9
      Reviewed-on: https://chromium-review.googlesource.com/843025
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#50347}
      71605b3e
    • Michael Achenbach's avatar
      [test] Refactor commands into OS-specific versions · e8912359
      Michael Achenbach authored
      This seperates OS-specific code of the Command class into a Posix and a
      WindowsCommand to simplify scattered OS checks.
      
      This also removes some temporary mac debug output that's obsolete after
      https://crbug.com/v8/6927 got resolved.
      
      TBR=sergiyb@chromium.org
      
      Bug: v8:6917
      Change-Id: Iaab3b527ce556dfba797a164ae58e8dd358eb56f
      Reviewed-on: https://chromium-review.googlesource.com/847000Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#50346}
      e8912359
    • Michael Achenbach's avatar
      Revert "Skip Execution::Call in CompileFunctionInContext." · d55f9297
      Michael Achenbach authored
      This reverts commit ce8f5141.
      
      Reason for revert: Changes a layout test:
      https://build.chromium.org/p/client.v8.fyi/builders/V8-Blink%20Linux%2064/builds/20693
      
      Original change's description:
      > Skip Execution::Call in CompileFunctionInContext.
      > 
      > We execute the top-level function only to get to the wrapped function.
      > We could do the same by simply instantiating it.
      > 
      > Other approaches would change the parser so that the top-level function
      > is the wrapped function. However, that change violates existing scoping
      > invariants and fixing it would add a lot more complexity to the parser.
      > 
      > R=​adamk@chromium.org, marja@chromium.org
      > 
      > Bug: v8:7172
      > Change-Id: I7272b8b58fc739d47a44da3a9d4a914af3e8cf3d
      > Reviewed-on: https://chromium-review.googlesource.com/836367
      > Reviewed-by: Adam Klein <adamk@chromium.org>
      > Commit-Queue: Yang Guo <yangguo@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#50333}
      
      TBR=adamk@chromium.org,marja@chromium.org,yangguo@chromium.org
      
      Change-Id: I922fdd2410512d837705263e092a09e041b9d28f
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Bug: v8:7172
      Reviewed-on: https://chromium-review.googlesource.com/849215Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#50345}
      d55f9297