From c8d8ff2a1cb05534eecc5fd47649e67851086293 Mon Sep 17 00:00:00 2001 From: Clemens Backes Date: Mon, 9 Mar 2020 13:59:44 +0100 Subject: [PATCH] [wasm] Remove obsolete flags from inspector test We now always tier down to Liftoff when the debugger is enabled, hence we don't need to force Liftoff-only execution in the test. R=thibaudm@chromium.org CC=duongn@microsoft.com Bug: v8:9654 Change-Id: I9b9e21b2ee977b349bb4f5d0e34c6ebf82166cb9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2093504 Reviewed-by: Thibaud Michaud Commit-Queue: Clemens Backes Cr-Commit-Position: refs/heads/master@{#66630} --- test/inspector/debugger/wasm-scope-info-liftoff.js | 4 ---- 1 file changed, 4 deletions(-) diff --git a/test/inspector/debugger/wasm-scope-info-liftoff.js b/test/inspector/debugger/wasm-scope-info-liftoff.js index a945d77626..9cdb36b51b 100644 --- a/test/inspector/debugger/wasm-scope-info-liftoff.js +++ b/test/inspector/debugger/wasm-scope-info-liftoff.js @@ -2,10 +2,6 @@ // Use of this source code is governed by a BSD-style license that can be // found in the LICENSE file. -// TODO(clemensb): In the long term this test should also work without any -// flags, once we tier down to Liftoff when the debugger is enabled. -// Flags: --liftoff --no-wasm-tier-up - let {session, contextGroup, Protocol} = InspectorTest.start( 'Test retrieving scope information from compiled Liftoff frames'); session.setupScriptMap();