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 AnalysisCache outputs are not reproducible #283

Open
JaredNeil opened this issue May 28, 2020 · 2 comments
Open

Zinc AnalysisCache outputs are not reproducible #283

JaredNeil opened this issue May 28, 2020 · 2 comments

Comments

@JaredNeil
Copy link
Contributor

JaredNeil commented May 28, 2020

The *.gz files contain a timestamp in the gzip header (mtime). (See next comment for correction)
This is a problem because the apis.gz and relations.gz outputs are used as inputs to downstream actions.
Are those files necessary as inputs? Removing them doesn't seem to break anything, but I'm not sure what Zinc uses them for.
If they are needed, we'll need to find a reproducible way to create them.

@JaredNeil
Copy link
Contributor Author

JaredNeil commented May 28, 2020

After further investigation it is not the timestamp like I thought. Instead it's that the APIs message has unordered elements, which are sometimes serialized in a different order.

@pauldraper
Copy link
Contributor

pauldraper commented Jun 1, 2020

There are used here.

I think they make incremental compilation work more effectively if it is enabled.
You could ask on the Zinc Gitter. I am not certain they are necessary.

They are used for sbt test discovery in scala_test, and they are necessary for that.

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

No branches or pull requests

2 participants