promql: Deactivate three failing tests for the time being

These tests fail on darwin/arm64.

One is expected, because the test demonstrates the limits of the
numerical accuracy of our methods, and different inaccurate outcomes
on different hardware are expected.

The other two are mysterious at the moment, see
https://github.com/prometheus/prometheus/issues/16714 for detailed
discussion and debugging.

Signed-off-by: beorn7 <beorn@grafana.com>
This commit is contained in:
beorn7 2025-06-10 21:44:05 +02:00
parent ea75bc18e9
commit c3da460474
2 changed files with 12 additions and 7 deletions

View File

@ -593,8 +593,10 @@ eval instant at 1m avg(data{test="big"})
eval instant at 1m avg(data{test="-big"})
{} -9.988465674311579e+307
eval instant at 1m avg(data{test="bigzero"})
{} 0
# This test fails on darwin/arm64.
# Deactivated until issue #16714 is fixed.
# eval instant at 1m avg(data{test="bigzero"})
# {} 0
# If NaN is in the mix, the result is NaN.
eval instant at 1m avg(data)

View File

@ -1010,8 +1010,10 @@ load 10s
eval instant at 1m sum_over_time(metric[2m])
{} 2
eval instant at 1m avg_over_time(metric[2m])
{} 0.5
# This test fails on darwin/arm64.
# Deactivated until issue #16714 is fixed.
# eval instant at 1m avg_over_time(metric[2m])
# {} 0.5
# More tests for extreme values.
clear
@ -1082,9 +1084,10 @@ load 5s
# needed to do something like sorting the values (which is hard given
# how the PromQL engine works). The question is how practically
# relevant this scenario is.
eval instant at 55s avg_over_time(metric11[1m])
{} -1.881783551706252e+203
# {} -44.848083237000004 <- This is the correct value.
# eval instant at 55s avg_over_time(metric11[1m])
# {} -44.848083237000004 <- This is the correct value.
# {} -1.881783551706252e+203 <- This is the relust on linux/amd64.
# {} 2.303079268822384e+202 <- This is the relust on darwin/arm64.
# Test per-series aggregation on dense samples.
clear