[lit] Use dbg instead of note for tool detection#193662
[lit] Use dbg instead of note for tool detection#193662vitalybuka wants to merge 9 commits intomainfrom
Conversation
Created using spr 1.3.7
|
@llvm/pr-subscribers-libcxx @llvm/pr-subscribers-testing-tools Author: Vitaly Buka (vitalybuka) ChangesAlso remove unused parameter Don't output lines like these by default: I don't believe this information is usefull for a typical test run. Now they can be retrived with 'LIT_OPTS=--debug ninja check-llvm' Full diff: https://github.com/llvm/llvm-project/pull/193662.diff 1 Files Affected:
diff --git a/llvm/utils/lit/lit/llvm/config.py b/llvm/utils/lit/lit/llvm/config.py
index 9713f4333d99a..2a6c60fab6125 100644
--- a/llvm/utils/lit/lit/llvm/config.py
+++ b/llvm/utils/lit/lit/llvm/config.py
@@ -527,7 +527,6 @@ def use_llvm_tool(
name,
search_env=None,
required=False,
- quiet=False,
search_paths=None,
use_installed=False,
):
@@ -565,8 +564,7 @@ def use_llvm_tool(
self.lit_config.params.get("use_normalized_slashes")
):
tool = tool.replace("\\", "/")
- if not quiet:
- self.lit_config.note("using {}: {}".format(name, tool))
+ self.lit_config.dbg("using {}: {}".format(name, tool))
return tool
def _get_clang_paths(self, additional_tool_dirs):
|
boomanaiden154
left a comment
There was a problem hiding this comment.
I agree this information probably isn't helpful on a development machine, but I feel like it can be useful in some circumstances in CI setups when things go wrong.
It's not very much log output.
🪟 Windows x64 Test Results
Failed Tests(click on a test name to see its output) litlit.lit/use-llvm-tool.pyIf these failures are unrelated to your changes (for example tests are broken or flaky at HEAD), please open an issue at https://github.com/llvm/llvm-project/issues and add the |
🐧 Linux x64 Test Results
Failed Tests(click on a test name to see its output) litlit.lit/use-llvm-tool.pyIf these failures are unrelated to your changes (for example tests are broken or flaky at HEAD), please open an issue at https://github.com/llvm/llvm-project/issues and add the |
Then CI should run LIT_OPTS=-debug LLVM is quite big now, if we keep all debug logging it's hard to notice relevant issues It's easy to undo if it's someone will miss it |
…note-for-tool-detection
Created using spr 1.3.7 [skip ci]
Created using spr 1.3.7 [skip ci]
Also remove unused parameter
quiet.Don't output lines like these by default:
I don't believe this information is usefull for a typical test run.
Now they can be retrived with 'LIT_OPTS=--debug ninja check-llvm'