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

Zinc doesn't invalidate when it should #4664

Closed
benjyw opened this issue Jun 9, 2017 · 10 comments
Closed

Zinc doesn't invalidate when it should #4664

benjyw opened this issue Jun 9, 2017 · 10 comments
Assignees
Labels
Milestone

Comments

@benjyw
Copy link
Contributor

benjyw commented Jun 9, 2017

See https://github.com/benjyw/pants/blob/benjy/invalidation_bug_repro/BUG_REPRO.md for details and a branch that reproduces this.

@benjyw benjyw added this to the 1.4.0 milestone Jun 9, 2017
@benjyw
Copy link
Contributor Author

benjyw commented Jan 4, 2018

Giving this a bump. I don't remember if we think this is a Pants issue or a Zinc issue. If the former, I can take a look myself.

@stuhood
Copy link
Member

stuhood commented Jan 4, 2018

@benjyw : One thing to check would be whether it still fails in #4729, which upgrades us to much newer zinc.

@benjyw
Copy link
Contributor Author

benjyw commented Jan 5, 2018

That change isn't in master though, right?

@stuhood
Copy link
Member

stuhood commented Jan 5, 2018

It is not, no. I hope to get some more time to work on landing it soon, only relatively minor issues remain (related to requiring that zinc run in JDK8+, and forking if an older JVM is requested for java compilation).

@benjyw
Copy link
Contributor Author

benjyw commented Jan 5, 2018

I notice that 33e98e1 upgraded us to 1.0.0-X20 though. Isn't that newer than -X16?

@benjyw
Copy link
Contributor Author

benjyw commented Jan 5, 2018

Wait, we're at 1.0.3 in master. I'm too confused. However it does appear that this does not repro in current master. I tried to sync back past 33e98e1 but failed to build the native engine. Sigh.

@benjyw
Copy link
Contributor Author

benjyw commented Jan 5, 2018

Anyway, this no longer repros, possibly thanks to 33e98e1. Closing.

@benjyw benjyw closed this as completed Jan 5, 2018
@stuhood
Copy link
Member

stuhood commented Jan 5, 2018

33e98e1 updates the JVM portion of zinc, but doesn't use it in pants. That's what #4729 will do.

@benjyw
Copy link
Contributor Author

benjyw commented Jan 5, 2018

Hmm, well then perhaps 3e5f680 is the fix.

@benjyw
Copy link
Contributor Author

benjyw commented Jan 5, 2018

TODO: For peace of mind, find the commit that fixed this before closing this issue.

Doing so requires a solution for building older native engine versions. See #4909.

@benjyw benjyw reopened this Jan 5, 2018
@benjyw benjyw closed this as completed Jan 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants