-
Notifications
You must be signed in to change notification settings - Fork 10
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
[Bug]: v0.1.7 fails when run via chromatic in CI #211
Comments
Due to the description, #196 might be the cause but I don't know why. I'm not familiar with Chromatic, either. Could you provide a minimal reproduction so we can debug it in a Linux environment? You could prefix your command with |
I ended up having to do |
The Chromatic team could also fix this by adding something like https://github.com/chromaui/chromatic-cli/pull/1110/files#diff-788a73045dad6838b61028993c01fdd65c7ea28c9b1da0a91cc7d5caeb50f9cfR144 - specifically, |
@etripier Thanks for the inspection, I'll revert the path at first (keep using find-cache-dir). |
Details
After upgrading to 0.1.7 our chromatic jobs fail with the following error message. A downgrade to v0.1.6 resolves the problem entirely. I could not determine what the root cause is, but maybe it has something to do with the cache dir change made in v0.1.7.
The problem only appears when the chromatic task is run by the CI. When its triggered locally everything runs fine.
Here is the error message:
The text was updated successfully, but these errors were encountered: