Skip to content
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

Remove log tests from Livy #46272

Merged
merged 1 commit into from
Jan 30, 2025

Conversation

potiuk
Copy link
Member

@potiuk potiuk commented Jan 30, 2025

Similarly to #46263 - there is no real value in keeping tests for logs in Livy - and caplog tests are known to be super vulnerable to side-effects from other tests. Since those tests add no value, we should just remove them without replacement.


^ 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.rst or {issue_number}.significant.rst, in newsfragments.

Similarly to apache#46263 - there is no real value in keeping tests for
logs in Livy - and caplog tests are known to be super vulnerable
to side-effects from other tests. Since those tests add no value,
we should just remove them without replacement.
@jedcunningham jedcunningham merged commit 8e39da3 into apache:main Jan 30, 2025
62 checks passed
got686-yandex pushed a commit to got686-yandex/airflow that referenced this pull request Jan 30, 2025
Similarly to apache#46263 - there is no real value in keeping tests for
logs in Livy - and caplog tests are known to be super vulnerable
to side-effects from other tests. Since those tests add no value,
we should just remove them without replacement.
dabla pushed a commit to dabla/airflow that referenced this pull request Jan 30, 2025
Similarly to apache#46263 - there is no real value in keeping tests for
logs in Livy - and caplog tests are known to be super vulnerable
to side-effects from other tests. Since those tests add no value,
we should just remove them without replacement.
ambika-garg pushed a commit to ambika-garg/airflow that referenced this pull request Jan 30, 2025
Similarly to apache#46263 - there is no real value in keeping tests for
logs in Livy - and caplog tests are known to be super vulnerable
to side-effects from other tests. Since those tests add no value,
we should just remove them without replacement.
@ashb ashb changed the title Remove caplog from Livy tests Remove log tests from Livy Feb 7, 2025
niklasr22 pushed a commit to niklasr22/airflow that referenced this pull request Feb 8, 2025
Similarly to apache#46263 - there is no real value in keeping tests for
logs in Livy - and caplog tests are known to be super vulnerable
to side-effects from other tests. Since those tests add no value,
we should just remove them without replacement.
ambika-garg pushed a commit to ambika-garg/airflow that referenced this pull request Feb 17, 2025
Similarly to apache#46263 - there is no real value in keeping tests for
logs in Livy - and caplog tests are known to be super vulnerable
to side-effects from other tests. Since those tests add no value,
we should just remove them without replacement.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants