The memory is measured after the agent reaches its control plane
CI / test (push) Successful in 9m5s
CI / test (push) Successful in 9m5s
Measuring it in the startup scan held every agent half a second or more before registering, which on a shared CI runner was past the failover tests' wait. Now it runs once a process, in the background, the first time it is asked for, and Heartbeat.mem_bandwidth_gbs carries it when known; the control plane keeps the last figure and a heartbeat without one leaves it. The agent's tests do not measure. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
84444e71c8
commit
e70d6caa2f
6 files changed
+83
-8
No files matched your search
@@ -0,0 +1,13 @@
|
||||
package agent
|
||||
|
||||
import (
|
||||
"os"
|
||||
"testing"
|
||||
)
|
||||
|
||||
func TestMain(m *testing.M) {
|
||||
// Half a gigabyte read per test binary, and contending with the tests
|
||||
// for the CPUs: these never look at the figure.
|
||||
measureBandwidth = func() float64 { return 0 }
|
||||
os.Exit(m.Run())
|
||||
}
|
||||
Reference in new issue
Block a user