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

Test bazel test //... in all configurations #1569

Merged
merged 5 commits into from
Jul 19, 2021
Merged

Test bazel test //... in all configurations #1569

merged 5 commits into from
Jul 19, 2021

Conversation

aherrmann
Copy link
Member

As discussed in #1553 (comment) and #1553 (comment) bazel test //... was previously not fully tested in all configurations. The nixpkgs pipelines only tested bazel test //... --build_tests_only and the bindist configurations only tested bazel test //tests/.... This PR changes this so that all configurations and the coverage tests use bazel test //.... This required adding exclusion tags to some targets that don't work in all configurations.

These are targets that require dynamic libraries to build which are not
available in profiling mode.
Do not limit the wildcard to //tests/... or the build to
--build_tests_only.

Set --build_tag_filters in profiling tests, --test_tag_filters only
affects test execution but not builds.

Take //... expansion on Windows into account
@aherrmann aherrmann requested a review from Radvendii July 16, 2021 16:08
@Radvendii
Copy link
Contributor

Why was it like this before? Are we assuming it's because of the tests that fail in some configurations?

@aherrmann
Copy link
Member Author

Why was it like this before? Are we assuming it's because of the tests that fail in some configurations?

Historical reasons. The nixpkgs pipelines existed first and the bindist pipelines were only introduced later and only incrementally. Some parts still require Nix provided tools that have no replacement in the bindist toolchains, e.g. sphinx in //docs/....

Copy link
Contributor

@Radvendii Radvendii left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, seems good to me.

@aherrmann aherrmann added the merge-queue merge on green CI label Jul 19, 2021
@aherrmann
Copy link
Member Author

GitHub App like Mergify are not allowed to merge pull request where .github/workflows is changed.

Requires manual merge.

@aherrmann aherrmann merged commit e65211d into master Jul 19, 2021
@aherrmann aherrmann deleted the run-tests branch July 19, 2021 13:56
@mergify mergify bot removed the merge-queue merge on green CI label Jul 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants