-
-
Notifications
You must be signed in to change notification settings - Fork 646
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
List in new engine with no args breaks #3798
Comments
missing attributes on |
ftr:
|
I didn't see it in initial PR. Probably is a lack of coverage. But are we supposed to call those goals without any args? |
the convention is that anytime you call pants with no target, for |
it could also be the case that the cause of these issues landed after your test PR - it might be a good idea to backmerge and re-run. |
So I started a new PR with all the changes I have, and it hasn't finished yet, but I already see a failure about "Exception message: 'LegacyAddressMapper' object has no attribute 'specs_to_addresses'" |
if no args given, v2 engine does noop on generating build_graph, and self.context.target_roots is empty. engine will call self.context.scan() which will create a MutableBuildGraph, with the addressmapper for v2 engine. if args are given (even "::"), v2 engine can generate build_graph, and self.context.target_roots is not empty. For fixing "list", i think we can just simply check options.target_specs in EngineInitializer.parse_commandline_to_spec_roots, if it is empty, we make it "::". |
this blocks #3740 |
@JieGhost did you happen to start on this one? I think I'm in a good position to repair this as part of the second bit of the |
Oops, Sorry Kris. I didn't see your message earlier. |
I think this one is merged. |
The text was updated successfully, but these errors were encountered: