https://perf.golang.org/dashboard/?benchmark=regressions 是由于处理程序中的恐慌而损坏的:
2022/09/19 21:52:14 http2: panic serving 10.102.129.129:15437: runtime error: index out of range [341] with length 341
goroutine 2971853 [running]:
net/http.(*http2serverConn).runHandler.func1()
/usr/local/go/src/net/http/h2_bundle.go:5896 +0x125
panic({0xeb82c0, 0xc0004128b8})
/usr/local/go/src/runtime/panic.go:838 +0x207
golang.org/x/build/perf/app.renameBenchmarksWithRegressions({0xc0000a8700, 0xcf, 0xcf?}, 0xb7782e?)
/app/perf/app/dashboard.go:394 +0x4bd
golang.org/x/build/perf/app.groupBenchmarkResults(0xf6c917?, 0x1)
/app/perf/app/dashboard.go:426 +0x65
golang.org/x/build/perf/app.fetchAllBenchmarks({0x10a8b10, 0xc000b2b3c0}, {0x10a8d78, 0xc0007345c0}, 0x48?, {0x450797?, 0x23?, 0x1b8e440?}, {0xc0c25702dd2d545a, 0x1e0f2939c9606, ...})
/app/perf/app/dashboard.go:272 +0x1a5
2022-09-19 14:52:14.146 PDT
...
我暂时无法看到为什么会发生这种情况,但也许我们有两个具有相同名称的基准测试,导致回归Map中的冲突。稍后我可以花更多时间进行检查。
cc @dr2chase@mknyszek
1条答案
按热度按时间dba5bblo1#
这实际上已经解决了,即使将视图扩展到90天,这也很奇怪。