Replies: 1 comment 1 reply
-
interesting! there is one comment at Line 467 in 26efb60 if it persists, it would be useful to have something closer to a repro; though maybe difficult if it requires a big chunk of the private code... |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I realize this is most likely not a problem with Insta itself but the error is manifesting through insta and there's some very smart folks here so I figure it can't hurt to ask for ideas.
I have a private repo that uses insta for snapshotting in tests. A couple of weeks ago I started intermittently getting this bizarre series of errors when running
cargo test
:Then any other test that touches insta fails with:
If I run with
cargo test -- --test-threads 1
no error. Bizarrely if I then runcargo test -- --test-threads 12
in the same session it no longer fails. So it seems that a successful run populates some sort of cache, but I don't see any env vars changed / don't know where to look for that or who is caching something.This has persisted across total wipes of my computer and a logic board (and hence SSD) replacement. I have not been able to reproduce on any other computer (other MacBooks, GitHub Codespace, CI, etc.).
It does seem to somehow be specific to this repo (which I unfortunately cannot share); other repos that use insta run fine.
The computer is an M4 MacBook Pro.
Beta Was this translation helpful? Give feedback.
All reactions