Turbo generates two different hashes on different machines #9004
Unanswered
mohdmusthafaneo
asked this question in
Help
Replies: 1 comment 3 replies
-
Hey! It looks like the hash of the This could also be because of global dependencies. Turbo includes some env vars by default that could explain this - this would show up in the summary file under the global heading |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Summary
I have a project running on
turbo@2.0.12
. I added 5 packages. I am also using remote caching (self hosted). Whenever I runturbo lint
, the linting gets completed and cache is stored in remote against a hash. but when my teammate does the same, he gets entirely different hash even though all the inputs for the hash generation is same.I checked the summary of the linting by running
turbo lint --summarize
, and I can see all the dependencies (files) and hash of external dependencies are same. but the final hash is different. I also made sure we both are running same osubuntu 24
andnode 20.16.0
andturbo 2.0.12
, but still get different hashAdditional information
turbo.json
"lint": {
"dependsOn": [
"^lint"
],
"outputs": []
},
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions