You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/eng_sys_checks.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,7 @@
7
7
-[The pyproject.toml](#the-pyprojecttoml)
8
8
-[Environment variables important to CI](#environment-variables-important-to-ci)
9
9
-[Atomic Overrides](#atomic-overrides)
10
+
-[Enable test logging in CI pipelines](#enable-test-logging-in-ci-pipelines)
10
11
-[Analyze Checks](#analyze-checks)
11
12
-[MyPy](#mypy)
12
13
-[Pyright](#pyright)
@@ -167,6 +168,16 @@ The name that you should use is visible based on what the `tox environment` that
167
168
-`AZURE_SERVICEBUS_PYRIGHT=true` <-- enable a check that normally is disabled in `pyproject.toml`
168
169
-`AZURE_CORE_PYLINT=false` <-- disable a check that normally runs
169
170
171
+
### Enable test logging in CI pipelines
172
+
173
+
You can enable test logging in a pipeline by setting the queue time variable `PYTEST_LOG_LEVEL` to the desired logging [level](https://docs.python.org/3/library/logging.html#logging-levels). For example,
174
+
175
+
`PYTEST_LOG_LEVEL=INFO`
176
+
177
+
This also works locally with tox by setting the `PYTEST_LOG_LEVEL` environment variable.
178
+
179
+
Note that if you want DEBUG level logging with sensitive information unredacted in the test logs, then you still must pass `logging_enable=True` into the client(s) being used in tests.
180
+
170
181
## Analyze Checks
171
182
172
183
Analyze job in both nightly CI and pull request validation pipeline runs a set of static analysis using external and internal tools. Following are the list of these static analysis.
0 commit comments