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.

Sign up for GitHub

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

Jump to bottom

Fix problems with missing selective checks on new types of unit tests #36372

Merged
merged 1 commit into from
Dec 22, 2023
Merged

Fix problems with missing selective checks on new types of unit tests #36372

merged 1 commit into from
Dec 22, 2023

Commits on Dec 22, 2023

  1. Fix problems with missing selective checks on new types of unit tests 

    When the DB/NonDB tests were introduced (apache#35160) new test types have
been added (separating various Python test types from generic
Operator test type). However we have not added matching of the python
operator and test files into the right selective unit test type. This
caused that when only `operators/python.py` and `tests/test_python` were
changed, then `Operators` test type was run but the specific Python *
test types were not run.

This PR fixes it for current test type (including also separated
Serialization test type) and for the future - instead of matching
selected test type we match all of them except the few that we
now are "special" ("Always, Core, Other, PlainAsserts").
    @potiuk
    potiuk committed Dec 22, 2023
    Configuration menu
    Copy the full SHA
    f0948f7 View commit details
    Browse the repository at this point in the history