Commit 735eda8
[SPARK-54874][TESTS][INFRA] Avoid interleave failed test logs with test outputs
### What changes were proposed in this pull request?
1. `FAILURE_REPORTING_LOCK` is only for the unified logger file, we don't need that for `per_test_output`
2. Use `LOGGER` instead of `print` to print data because `LOGGER` has an internal lock to avoid interleave
3. Put all the lines together and print it once to avoid interleave
### Why are the changes needed?
We have a thread pool to run different individual tests and the test output is interleaved with error messages.
https://github.com/apache/spark/actions/runs/20594052053/job/59144974177
It's difficult to tell which test the debugging message belongs to.
### Does this PR introduce _any_ user-facing change?
No
### How was this patch tested?
Locally it works
### Was this patch authored or co-authored using generative AI tooling?
No
Closes #53648 from gaogaotiantian/avoid-interleave-logs.
Authored-by: Tian Gao <[email protected]>
Signed-off-by: Ruifeng Zheng <[email protected]>1 parent 1fc6ff2 commit 735eda8
1 file changed
+12
-7
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
301 | 301 | | |
302 | 302 | | |
303 | 303 | | |
| 304 | + | |
304 | 305 | | |
305 | 306 | | |
306 | | - | |
307 | 307 | | |
308 | | - | |
309 | | - | |
310 | | - | |
311 | | - | |
312 | | - | |
313 | | - | |
| 308 | + | |
| 309 | + | |
| 310 | + | |
| 311 | + | |
| 312 | + | |
| 313 | + | |
| 314 | + | |
| 315 | + | |
| 316 | + | |
| 317 | + | |
| 318 | + | |
314 | 319 | | |
315 | 320 | | |
316 | 321 | | |
| |||
0 commit comments