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

build(bazel): provide means of excluding whl_test locally #2940

Merged
merged 3 commits into from
Nov 27, 2024

Conversation

rkuester
Copy link
Contributor

Mark whl_test as size "large", so that it, and other tests of a
similar size, can be excluded with the --test_size_filters
option.

For even more convenience, provide a hook for developers to add
local .bazlerc-style defaults and configurations in
$root/bazelrc.local and ../$root/bazelrc.local.

This gives a convenient means of explicitly excluding whl_test
during local, incremental development runs of bazel test ...,
while not surprising users who don't opt in, and without
affecting CI.

whl_test's cached result is invalidated, and the test rerun,
following most git activity, because the git hash appears in the
Python package's version number. This combined with its long
runtime and network dependency makes it a nuisance when running
bazel test ... incrementally during development. Of course,
this test be run when developing changes that affect the package,
before pushing commits to main, and in CI.

BUG=see description

Mark whl_test as size "large", so that it, and other tests of a
similar size, can be excluded with the --test_size_filters
option.

For even more convenience, provide a hook for developers to add
localy .bazlerc-style defaults and configurations in
$root/bazelrc.local and ../$root/bazelrc.local.

This gives a convenient means of explicitly excluding whl_test
during local, incremental development runs of `bazel test ...`,
while not surprising users who don't opt in, and without
affecting CI.

whl_test's cached result is invalidated, and the test rerun,
following most git activity, because the git hash appears in the
Python package's version number. This combined with its long
runtime and network dependency makes it a nuisance when running
`bazel test ...` incrementally during development. Of course,
this test should be allowed to run when developing changes that
affect the package, before pushing commits to main, and in CI.
@rkuester rkuester requested a review from a team as a code owner November 26, 2024 23:03
@rkuester rkuester requested a review from suleshahid November 26, 2024 23:27
@mergify mergify bot merged commit 31b5246 into tensorflow:main Nov 27, 2024
30 checks passed
@rkuester rkuester deleted the feat-make-whltest-excludable branch November 27, 2024 01:01
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.

3 participants