--- FAIL: TestAllocations (0.02s)
ed25519_test.go:202: expected zero allocations, got 3e+01
Testing performance profiles is brittle: it currently fails on the noopt builder, and on the dev.boringcrypto branch. Even if we skipped it on both, it would fail on go test all if run without optimizations, like Delve does.
We can make it run only on a specific builder, but I am worried that will eventually drift out of sync with builder naming and end up never running. Better than nothing, I guess.
Testing performance profiles is brittle: it currently fails on the
nooptbuilder, and on thedev.boringcryptobranch. Even if we skipped it on both, it would fail ongo test allif run without optimizations, like Delve does.We can make it run only on a specific builder, but I am worried that will eventually drift out of sync with builder naming and end up never running. Better than nothing, I guess.