The rust_test does not allow users to <a href="https:

Unable to tag a rust_test as manual about rules_rust HOT 3 CLOSED

bazelbuild commented on July 3, 2024

Unable to tag a rust_test as manual

from rules_rust.

Comments (3)

acmcarther commented on July 3, 2024

tags is an accepted field for rust_test according to my local testing.

I tried the following values:

exclusive: Unclear if this one worked, no observable effect
manual: This is supposed to cause the test not to be included in aggregate builds. This did not work for me either with @examples//... or with @examples//hello_lib:all (the test was run).
external: Ostensibly, this forces the test not to cache. This worked in local testing for me

I wonder if we need to specially implement manual...

from rules_rust.

acmcarther commented on July 3, 2024

Apologies -- Addendum:

Manual does also work for me (note the omission of @examples//hello_lib:hello_lib_test).

$ bazel test @examples//...
INFO: Analysed 21 targets (0 packages loaded).
INFO: Found 13 targets and 8 test targets...
INFO: Elapsed time: 0.171s, Critical Path: 0.01s
INFO: 0 processes.
INFO: Build completed successfully, 1 total action
@examples//fibonacci:fibonacci_doc_test                         (cached) PASSED in 0.6s
@examples//fibonacci:fibonacci_test                             (cached) PASSED in 0.1s
@examples//hello_lib:greeting_test                              (cached) PASSED in 0.1s
@examples//hello_lib:hello_lib_doc_test                         (cached) PASSED in 0.5s
@examples//hello_runfiles:hello_runfiles_test                   (cached) PASSED in 0.1s
@examples//hello_world:hello_world_doc_test                     (cached) PASSED in 0.7s
@examples//matrix:matrix_test                                   (cached) PASSED in 0.2s
@examples//matrix:native_matrix_test                            (cached) PASSED in 0.1s

Executed 0 out of 8 tests: 8 tests pass.
There were tests whose specified size is too big. Use the --test_verbose_timeout_warnings command line option to see wINFO: Build completed successfully, 1 total action

$ bazel test @examples//hello_lib:all
INFO: Analysed 7 targets (0 packages loaded).
INFO: Found 5 targets and 2 test targets...
INFO: Elapsed time: 0.124s, Critical Path: 0.00s
INFO: 0 processes.
INFO: Build completed successfully, 1 total action
@examples//hello_lib:greeting_test                              (cached) PASSED in 0.1s
@examples//hello_lib:hello_lib_doc_test                         (cached) PASSED in 0.5s

Executed 0 out of 2 tests: 2 tests pass.
There were tests whose specified size is too big. Use the --test_verbose_timeout_warnings command line option to see wINFO: Build completed successfully, 1 total action

from rules_rust.