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

Unable to specify a bazel test Run Configuration with multiple specific targets #70

Closed
EricCousineau-TRI opened this issue Apr 3, 2017 · 2 comments

Comments

@EricCousineau-TRI
Copy link

I am running a suit of tests, and would like to use CLion to parse the compiler errors and ultimate program output. The functional equivalent of what I would like is something to the effect of:

$ cd drake/solvers
$ bazel test :equality_constrained_qp_solver_test :mathematical_program_test :moby_lcp_solver_test

If I specify this as a Run Configuration, and then specify the following as my Target expression:

//drake/solvers:equality_constrained_qp_solver_test //drake/solvers:mathematical_program_test //drake/solvers:moby_lcp_solver_test

I get the following error:

Error:ERROR: invalid target format '//drake/solvers:equality_constrained_qp_solver_test //drake/solvers:mathematical_program_test //drake/solvers:moby_lcp_solver_test': target names may not contain ' '

I believe this could be resolved if the individual arguments were permitted to be quoted separately, to still allow for generic patterns.

As a workaround, I am adding a temporary test_suite to my BUILD file.

@EricCousineau-TRI EricCousineau-TRI changed the title Unable to specify a bazel test Run Configuration with multiple targets Unable to specify a bazel test Run Configuration with multiple specific targets Apr 3, 2017
@brendandouglas
Copy link
Contributor

We don't support multi-target configurations yet. At the moment, the only workaround is the one you've found -- to use test_suites or similar.

You could also run '//drake/solver:all' if you wanted to run all the tests in that package, not just those three.

@sgowroji
Copy link
Member

Hi there! We're doing a clean up of old issues and will be closing this one. Please reopen if you’d like to discuss anything further. We’ll respond as soon as we have the bandwidth/resources to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants