miniblog.

← Back to all posts
Jan 19, 2017 at 19:03
Go is exploring a smart test runner which only re-runs tests that depend on changed code: https://github.com/golang/go/issues/11193 (rare in other languages!)
cmd/go: cache test results in go test · Issue #11193 · golang/go
cmd/go: cache test results in go test · Issue #11193 · golang/go
It would be nice to have a mode for go test that cached test results, so that you could change a package and then do 'go test ...' and have it only actually rerun the tests that depend on that pack...

Related Posts

Sep 2, 2023 at 06:06
Distributing binaries built against musl is counter-intuitive to me. When I run them on my machine, they're dynamically linked to glibc! The main advantage AIUI is that you don't depend on new glibc features, so you get a more portable executable.
Dec 24, 2021 at 19:10
Cunning trick to ease upgrades in Rust. Each semver upgrade is a distinct type, but a library can depend on an older version of itself and preserve the types!
GitHub - dtolnay/semver-trick: How to avoid complicated coordinated upgrades
GitHub - dtolnay/semver-trick: How to avoid complicated coordinated upgrades
How to avoid complicated coordinated upgrades. Contribute to dtolnay/semver-trick development by creating an account on GitHub.
May 10, 2021 at 04:26
3
JS projects can accumulate a ton of dependencies, but TIL that npm can explain why you have them. `npm explain foo` or `npm why foo` shows the dependency path to foo. Super handy when you weren't expecting to depend on something.