Stefan =?utf-8?q?Gränitz?= <[email protected]>, Stefan =?utf-8?q?Gränitz?= <[email protected]>, Stefan =?utf-8?q?Gränitz?= <[email protected]> Message-ID: In-Reply-To: <llvm.org/llvm/llvm-project/pull/[email protected]>
DavidSpickett wrote: > FYI: pre-commit tests aren't particularly helpful. The Windows bot didn't > seem to do anything Windows lldb has been disabled, I don't know why but it is expected. > and the Linux bots only reported timing data, but not which tests > passed/skipped. That would be nice but you can check via the xml results as well (this is what the test reporting automation uses). If you know where to find the artifacts that is. This page shows them https://github.com/llvm/llvm-project/actions/runs/22400418943?pr=183302, but not all the individual pages do. Download the x64 files and you'll find an XML file. I see that it contains: ``` <testcase classname="lldb-api.symstore/PDB" name="TestSymStoreLocalPDB.py" time="0.45"> <skipped message="Unsupported configuration"/> </testcase> ```` Or the more chaotic solution is to stick a `self.Fail()` in there and it'll be part of the test report. https://github.com/llvm/llvm-project/pull/183302 _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
