Source: prometheus Version: 2.53.3+ds1-1 Severity: normal Dear Maintainer,
On Debian CI, one of the runs of prometheus failed because of a failure of the test "TestQueryConcurrency": https://ci.debian.net/packages/p/prometheus/testing/ppc64el/58296167/ 578s === RUN TestQueryConcurrency 578s engine_test.go:108: 578s Error Trace: /tmp/autopkgtest-lxc.343aby_v/downtmp/autopkgtest_tmp/.build/src/github.com/prometheus/prometheus/promql/engine_test.go:108 578s Error: Query within concurrency threshold not being executed 578s Test: TestQueryConcurrency 578s unexpected fault address 0x7fff39681389 578s fatal error: fault 578s [signal SIGSEGV: segmentation violation code=0x1 addr=0x7fff39681389 pc=0x9f7b4] This run was triggered by an update to golang-golang-x-exp that did not change any of the non-testing related code. So it should not have any incidence on the dependent packages. I decided to run it once again with the same configuration and this time it passed without issues: https://ci.debian.net/packages/p/prometheus/testing/ppc64el/58300217/ So it seems this test is flaky, I am not sure what it the best way to deal with it.
