-
Notifications
You must be signed in to change notification settings - Fork 35
Weird error in synced environment #221
Comments
I'm 99% sure this is not an issue with elm-test. We're not touching the elm-stuff directory ourselves. Is it possible for you to exclude elm-stuff from synchronizing? It's very likely to contain per-computer data, so it should be generated locally on each device. |
yes I do. I have changed the setting to avoid that and will report back when I have more data |
I'm not using any kind of synced environment; just using NPM and having the same problem. |
all I can add is that the frequency does seem to have gone down significantly, but I did still get the error again recently while using my other device. Had to delete all elm-stuff directories |
Correction: the node test runner does modify elm-stuff, to add some generated elm files. |
We are also experiencing this issue, though we are using Docker which might result in a similar situation as syncing multiple computers. Removing |
I'm in the same boat, running [email protected]. I have no sync running but my path setup is atypical (because of Webpacker) but I have some private packages installed using elm-install. Not sure if it's related, I suspect the unusual path setup because before migrating to Webpacker, with normal setup ( |
I use a sync program to keep my to dev computers in sync. It works in general, but I experience issues with elm-test, as when I switch from one computer to another, elm-test fails until I delete the elm-package directories (seemingly in both the root and
tests
directories). What I see isThe text was updated successfully, but these errors were encountered: