================
@@ -1,9 +1,10 @@
 // Test clang-ssaf-format --list output without any loaded plugins.
 
 // RUN: clang-ssaf-format --list \
-// RUN:   | FileCheck %s
+// RUN:   | FileCheck %s --match-full-lines
 
 // CHECK: Registered serialization formats:
 // CHECK-EMPTY:
-// CHECK-NEXT:   1. json - JSON serialization format
-// CHECK-NEXT:      Analyses: (none)
+// CHECK-DAG: [[NthFormat:[0-9]+]]. json - JSON serialization format
+// CHECK-DAG:     Analyses:
+// CHECK-DAG:         [[NthFormat]].[[MthSummary:[0-9]+]]. CallGraph - JSON 
Format info for CallGraph summary
----------------
steakhal wrote:

The pattern matching here is for accounting for downstream added new formats 
and analyses. Because I suspect those might get interleaved with the 
upstream-supported formats and analyses. Hence the `DAG`matching with patterns, 
so that at least the right parts match for the right format.

https://github.com/llvm/llvm-project/pull/189681
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to