potiuk opened a new pull request, #27260: URL: https://github.com/apache/airflow/pull/27260
This PR improves the ways important information ise printed in CI. Currently some of the errors and important information is printed inside the folded console output when they are run. This is nice to have the folded content in case of success but in case of error we want to surface errors directly in the CI output so that the user does not have to find and unfold the information. Sometimes (for example in printing which dependencies got upgraded) we also want to surface some important part of the output even if there is a success. This is a foundational change that makes it possible and easy, we are going to add more of those as we find them. This change improves surfacing of the information in three cases: 1) Test failures When there is an error in tests, we should now see the (only the part containing error and traceback) see the failure details outside of the folded content - the folded content will still contain all the details of the test run, but you would not have to unfold it in order to see the actual error. 2) Errors when testing provider installation When there are errors when installing providers, the errors were initially inside of the folded "run" command and the run command did not even have indication that there was an error (just exit code information was printed). This change ends CI group when errors are detected (in CI) which makes the errors show up outside of the group. 3) Showing changed constraints Showing changed constraints when upgrading to newer dependencies is always interesting - regardless from being it error or success. With this change, we are showing just the constraints printed in the main logs. <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of an existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in a newsfragment file, named `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [newsfragments](https://github.com/apache/airflow/tree/main/newsfragments). -- 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]
