aglinxinyuan commented on PR #6797: URL: https://github.com/apache/texera/pull/6797#issuecomment-5077500197
Extended the backstop beyond amber in d7982b020c — every CI step that runs or boots a component with a log-level knob now carries the same wiring (`WARN`/`WARNING` normally, `DEBUG` on an **Enable debug logging** re-run): | Job / step | Env | Why that spelling | |---|---|---| | `platform` test step (all six services) | `TEXERA_SERVICE_LOG_LEVEL=WARN` | Dropwizard `logging.level` → logback vocabulary | | `platform-integration` boot smoke | `TEXERA_SERVICE_LOG_LEVEL=WARN` | same; safe — smoke-boot's verdict is LISTEN-based, never log-scraping (#6332) | | `amber-integration` texera-web + computing-unit-master boot smokes | `TEXERA_SERVICE_LOG_LEVEL=WARN` | same | | `pyamber` pytest + `amber-integration` Python integration pytest | `LOGURU_LEVEL=WARNING` | loguru's default stderr sink (pytest runs with `-s`, so it prints straight into the CI log); loguru has no `WARN`. Test-local sinks with an explicit level are unaffected — checked, the only one passes `level="WARNING"` explicitly | | `agent-service` unit tests | `TEXERA_SERVICE_LOG_LEVEL=WARN` | `env.ts` validates `["ERROR","WARN","INFO","DEBUG"]` then maps to pino's lowercase levels | Left alone per the "no log config → skip" rule: frontend, infra, pyright-language-service (none of them read a log-level variable). pekko is already covered everywhere via `PekkoConfig.normalizePekkoLogLevel`, since all JVM services share `cluster.conf`. -- 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]
