Joey Hess 1cacfd1b19 avoid setEnv in test framework when tasty is running ... setEnv is not thread safe and could cause a getEnv by another thread to segfault, or perhaps other had behavior. This is particularly a problem when using tasty, because tasty runs the test in a thread, and a getEnv in another thread. The use of top-level TMVars is ugly, but ok because only 1 test actually runs at a time per process. Because it has to chdir into the test repo. The setEnv that remains happens before tasty is running. Sponsored-by: Dartmouth College's Datalad project		2022-05-18 16:45:20 -04:00
..
Framework.hs	avoid setEnv in test framework when tasty is running	2022-05-18 16:45:20 -04:00