nielifeng commented on PR #11601: URL: https://github.com/apache/seatunnel/pull/11601#issuecomment-5140077640
Independent verification completed on head `0e79c6b3578202d209677857eee614e11e839bed`. Results: - `./mvnw -pl seatunnel-trace/seatunnel-trace-analyzer spotless:apply` passed. - `./mvnw -pl seatunnel-trace/seatunnel-trace-analyzer verify` passed: 18 tests, 0 failures/errors/skips. - A runtime A/B probe used one valid trace record and an intentionally invalid report output path. Before this change, the same `NoSuchFileException` stack trace appeared twice (Log4j plus raw `printStackTrace`). On this PR head, it appears once through Log4j, followed only by the existing concise `Error:` line; exit status remains 1. The change is behaviorally focused and I found no regression in the analyzer module. The GitHub Build check is currently `action_required`, so it still needs the normal workflow approval/run. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
