-
Notifications
You must be signed in to change notification settings - Fork 83
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
Cache cannot rebuid properly when nested paths specified in mount #87
Comments
@dmitweb Thanks for the feedback. Have you actually checked the checksum of this manually by comparing them before and after? I just want to be sure that yarn or npm doesn't intercept in anyhow. It'd be great if you can provide a simple case to reproduce this, maybe something public? |
Yes, i checked them. First screenshot from reproduce, second screenshot from my app. Code that check checksum is same. After many tests, I realized that the main problem with caching nested paths. Below i provide repo reproduce issue. Normal case: after first run drone pipeline, result must be cached and first yarn install must echo Repo: after first run drone pipeline, yarn install command reinstall deps ps. if comment line packages/test/node_modules from mount (restore, rebuild) all works fine, but in my project i have much many deps in package.json, and some of them install in packages/test/node_modules, so i must cache this folder too, this leads to diff in checksums, btw i don't know why https://github.com/dmitweb/drone-cache-bug I hope you can figure it out |
@dmitweb Thank you very much for your elaborate response. I'll look into it and do my best to figure it out. |
The problem still continues. Logs from with the latest version:
|
@dmitweb I know it's been a while, finally, I've got a fix candidate dmitweb/drone-cache-bug#1 |
Feel free to open this one again if the latest version doesn't solve your problem. It'll be in the next release otherwise. |
Describe the bug
I try cache yarn.lock file, but when it's extracted from tar it md5 checksum different. This leads to reinstall node_modules dependencies.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
md5sum file before and after must match
Maintainer's note:
The text was updated successfully, but these errors were encountered: