Log which "test case" we are running in TritonAndBlasSupport... Regular2DDot

gflegar · tensorflower-gardener · commit 41cc4b5986c3 · 2025-02-25T05:20:41.000-08:00
It is not quite ideal that we have a test that in effect consists of several test-cases, since it's difficult to figure out which one failed when one of them crashes.

I do understand the idea that we want an easy to see support matrix, and splitting it up into individual tests would prevent us from doing that.

As a middle ground, adding some logging so it's easy to tell what failed from the log.

PiperOrigin-RevId: 730839144
diff --git a/third_party/xla/xla/backends/gpu/codegen/triton/dot_algorithms_test.cc b/third_party/xla/xla/backends/gpu/codegen/triton/dot_algorithms_test.cc
@@ -1435,6 +1435,7 @@ TEST_P(TritonAndBlasSupportForDifferentTensorSizes, Regular2DDot) {
     csv.nextRow();
     csv.appendValue(m);
     for (int n = 1; n <= kMaxSize; n *= kStepSize) {
+      LOG(INFO) << "Running test for m=" << m << ", n=" << n;
       auto run = [&](std::string backend, absl::string_view pattern,
                      const DebugOptions& options) -> absl::string_view {
         auto test_name = absl::StrReplaceAll(TestName(), {{"/", "_"}});
