potiuk commented on PR #38441:
URL: https://github.com/apache/airflow/pull/38441#issuecomment-2016911399
> An alternative would be use use 2>&1 in the shell call to redirect all
stderr to stdout?
> In total meaning: breeze ci selective-check 2>&1 | tee ${GITHUB_OUTPUT} ?
We already do that actually
https://github.com/apache/airflow/blob/694826d1bd0a1593e676deed862519fac73266a4/.github/workflows/build-images.yml#L154
We print diagnostics information to stdout so that it can be seen in colour
- for example here
https://github.com/apache/airflow/actions/runs/8411260687/job/23030711777?pr=38437#step:8:849
In the past I also tried to revert it - i.e. print all the diagnostics to
stderr, and then print the outputs to stdout and do `> ${GITHUB_OUTPUT}` - but
it was far too easy to overlook something and it's better to redirect stderr to
GITHUB_OUTPUTS and leave stdout for diagnostics. Then we only have to catch all
the exceptions like this and print traceback to stdout, it's far easier than
trace down or pass "stderr" as the diagnostic output.
--
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]
