On Tue, Sep 17, 2024 at 4:08 AM twp...@gmail.com <twpa...@gmail.com> wrote: > > However, I want to make go test cache's behavior more correct for a case > where it is currently incorrect for no measurable performance penalty. What > are the reasons for *not* doing this?
We do not want to record all aspects of the external environment that could possibly affect the test. That would be too much. So we need some way to know what should be recorded and what should not. What should that be? Our current approach is simple: we record environment variables that the test reads and we record files opened within the module but not files opened outside of the module. Note that if a test opens some file outside of the module, we cache the test results even if that file changes. What approach should we use for test caching that will tell us that umask should be cached? Ian -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcWFnA_T3QTq%3DHQ67MhP---OEzNU5-nsnVMd_PYRNZkNLQ%40mail.gmail.com.
