-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Fix error propagation in new tests #44087
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix error propagation in new tests #44087
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot wasn't able to review any files in this pull request.
Files not reviewed (2)
- scripts/ci/testing/run_breeze_command_with_retries.sh: Language not supported
- scripts/ci/testing/run_unit_tests.sh: Language not supported
0900de0 to
3f53375
Compare
|
We will also have to merge #44088 to revert the failing API tests. |
|
Now - we detect those errors properlu. |
gopidesupavan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, all the failing tests are related to other pr.
3f53375 to
ce99b2a
Compare
|
added fix here for the failed tests: #44093 |
The apache#43979 introduced unit_tests.sh script that did not properly propagate error codes (no -e/+e setting). This PR fixes it - also fixes an edge case where the -e setting is not restored in run breeze commmand script.
ce99b2a to
bf956ae
Compare
The apache#43979 introduced unit_tests.sh script that did not properly propagate error codes (no -e/+e setting). This PR fixes it - also fixes an edge case where the -e setting is not restored in run breeze commmand script.
The #43979 introduced unit_tests.sh script that did not properly propagate error codes (no -e/+e setting).
This PR fixes it - also fixes an edge case where the -e setting is not restored in run breeze commmand script.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.