potiuk opened a new pull request, #28096:
URL: https://github.com/apache/airflow/pull/28096

   Warnings printed in CI have been making it difficult to see what is going on 
(they were taking far too much space after the test results and GitHub CI UI 
rendered those multi-line warnings slowly.
   
   Also we did not have the right tools to capture the number and list of 
warnings that we should deal with.
   
   We are usign pytest-capture-warnings plugin now that improves the situation 
twofold:
   
   * warning summary printed by the plugin in the output is shorter - each 
warning is at most one line
   * the warning text files are uploaded as artifacts which make them usable in 
any kind of approach where we want to attempt to start an effort to remove all 
warnings
   
   <!--
   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]

Reply via email to