i'm running this on master, and it seems like an e...
# general
a
i'm running this on master, and it seems like an error to not check that the second target exists (it doesn't) -- does this repro for anyone and is this a known issue / a feature?
Copy code
> ./pants test tests/python/pants_test/option:a
# ...
ResolveError: "a" was not found in namespace "tests/python/pants_test/option". Did you mean one of:
          :options_integration
          :testing
> ./pants test tests/python/pants_test/option:{testing,a}
# ...
 ===== 158 passed, 1 xfailed in 2.77 seconds ======
                     
                   tests/python/pants_test/option:testing                                          .....   SUCCESS
23:25:48 00:12     [junit]
23:25:48 00:12     [go]
23:25:48 00:12     [node]
               Waiting for background workers to finish.
23:25:49 00:13   [complete]
               SUCCESS
e
Repros for me and that's definitely a bug.
💔 1
w
probably introduced in https://github.com/pantsbuild/pants/pull/6366, which was fixing a separate bug.
...or maybe not!
a
i’m not having a great time right now but expect to be able to get to it today, let me know if anyone else wants to take it. i’m pretty confident i can do this today though
w
Filing would be more than enough. And no rush!
a
i'm fully aware it wasn't necessary but it was fun and the idea of silently accepting invalid target specs really irked me for some reason