The GitHub Actions job "Required Checks" on texera.git/ci-log-verbosity has failed. Run started by GitHub user aglinxinyuan (triggered by aglinxinyuan).
Head commit for run: d7982b020c8f98be3ee1655a233d23bf1b5ebe5f / Xinyuan Lin <[email protected]> ci: extend the log-level backstop to every service with a level knob Review follow-up on the amber-only scoping: the WARN backstop wired to "Enable debug logging" now covers every CI step that runs or boots a component with a log-level configuration, keeping one consistent level across the board: - platform test step: all six platform services read TEXERA_SERVICE_LOG_LEVEL into their Dropwizard logging config (logback vocabulary, WARN); - platform-integration + amber-integration boot smoke steps: same env for the packaged services; safe because smoke-boot's verdict is LISTEN-based, never log-scraping (#6332); - pyamber unit + Python integration pytest steps: LOGURU_LEVEL=WARNING (loguru vocabulary) for loguru's default stderr sink, which prints straight into the CI log because pytest runs with -s; test-local sinks with an explicit level are unaffected; - agent-service unit tests: TEXERA_SERVICE_LOG_LEVEL=WARN - env.ts validates ["ERROR","WARN","INFO","DEBUG"] before mapping to pino's lowercase levels, so the logback spelling is correct there too. Components with no log-level configuration (frontend, infra, pyright-language-service) are left alone. Report URL: https://github.com/apache/texera/actions/runs/30149304989 With regards, GitHub Actions via GitBox
