Re: [PR] Print selective-check traceback on stdout rather than stderr [airflow]

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

Re: [PR] Print selective-check traceback on stdout rather than stderr [airflow]

potiuk merged PR #38441: URL: https://github.com/apache/airflow/pull/38441 -- 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: commits-unsubscr...@airflow.a

Re: [PR] Print selective-check traceback on stdout rather than stderr [airflow]

potiuk commented on PR #38441: URL: https://github.com/apache/airflow/pull/38441#issuecomment-2016903858 Should help to diagnose issues like https://github.com/apache/airflow/actions/runs/8410545233/job/23029279435 -- This is an automated message from the Apache Git Service. To respond t

[PR] Print selective-check traceback on stdout rather than stderr [airflow]

potiuk opened a new pull request, #38441: URL: https://github.com/apache/airflow/pull/38441 We are using stdout of selective-check to print diagnostic information and stderr is redirected to produce outputs for GIHUB_OUTPUTS special variable in GitHub Actions. However this means that when t