Add --debug-cts to run-cts command
The CTS itself has a debug option. This makes it print out way more info
including things like the adapterInfo.vendor and the sample points
for texture builtins. So, add a way to pass in that flag to the CTS
when using run-cts.
Change-Id: If34030b80bb6f7e8af0b5445cde341bbb16572d3
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/220974
Reviewed-by: dan sinclair <dsinclair@chromium.org>
Commit-Queue: dan sinclair <dsinclair@chromium.org>
Reviewed-by: dan sinclair <dsinclair@google.com>
Auto-Submit: Gregg Tavares <gman@chromium.org>
diff --git a/tools/src/cmd/run-cts/node/cmd.go b/tools/src/cmd/run-cts/node/cmd.go
index af3c3ea..b41c0af 100644
--- a/tools/src/cmd/run-cts/node/cmd.go
+++ b/tools/src/cmd/run-cts/node/cmd.go
@@ -58,6 +58,7 @@
unrollConstEvalLoops bool
genCoverage bool
compatibilityMode bool
+ debugCTS bool
skipVSCodeInfo bool
enforceDefaultLimits bool
dawn node.Flags
@@ -109,6 +110,7 @@
flag.BoolVar(&c.flags.genCoverage, "coverage", false, "displays coverage data")
flag.StringVar(&c.flags.coverageFile, "export-coverage", "", "write coverage data to the given path")
flag.BoolVar(&c.flags.compatibilityMode, "compat", false, "run tests in compatibility mode")
+ flag.BoolVar(&c.flags.debugCTS, "debug-cts", false, "enable CTS debugging option")
flag.BoolVar(&c.flags.skipVSCodeInfo, "skip-vs-code-info", false, "skips emitting VS Code information")
flag.BoolVar(&c.flags.enforceDefaultLimits, "enforce-default-limits", false, "enforce the default limits (note: powerPreference tests may fail)")
diff --git a/tools/src/cmd/run-cts/node/server.go b/tools/src/cmd/run-cts/node/server.go
index ef330e0..915ffbb 100644
--- a/tools/src/cmd/run-cts/node/server.go
+++ b/tools/src/cmd/run-cts/node/server.go
@@ -126,6 +126,9 @@
if c.flags.enforceDefaultLimits {
args = append(args, "--enforce-default-limits")
}
+ if c.flags.debugCTS {
+ args = append(args, "--debug")
+ }
for _, f := range c.flags.dawn {
args = append(args, "--gpu-provider-flag", f)
}
