On 28.03.24 15:00, Santiago Vila wrote:
In either case, this is still happening for me in the current version:Lucas Nussbaum <lu...@debian.org> wrote:FAILED: 1:48: parse error: unexpected character inside braces: '0'
I think you are taking the "FAILED" out of context and misinterpreting the test output. Those are TestRulesUnitTest/* subtests, which are expected to fail. The summary at the end shows the expected results:
=== RUN TestRulesUnitTest
...
=== RUN TestRulesUnitTest/Bad_input_series
Unit Testing: ./testdata/bad-input-series.yml
FAILED:
1:48: parse error: unexpected character inside braces: '0'
...
--- PASS: TestRulesUnitTest (0.38s)
--- PASS: TestRulesUnitTest/Passing_Unit_Tests (0.22s)
--- PASS: TestRulesUnitTest/Long_evaluation_interval (0.13s)
--- PASS: TestRulesUnitTest/Bad_input_series (0.00s)
--- PASS: TestRulesUnitTest/Bad_PromQL (0.00s)
--- PASS: TestRulesUnitTest/Bad_rules_(syntax_error) (0.00s)
--- PASS: TestRulesUnitTest/Bad_rules_(error_evaluating) (0.00s)
--- PASS: TestRulesUnitTest/Simple_failing_test (0.01s)
--- PASS: TestRulesUnitTest/Disabled_feature_(@_modifier) (0.00s)
--- PASS: TestRulesUnitTest/Enabled_feature_(@_modifier) (0.00s)
--- PASS: TestRulesUnitTest/Disabled_feature_(negative_offset) (0.00s)
--- PASS: TestRulesUnitTest/Enabled_feature_(negative_offset) (0.00s)
You will see this in the output of _passing_ debci test runs.
Please can you find in your logs the _actual_ failing test or tests,
because it is not TestRulesUnitTest.
If you are running tests on a VM with a single core, it's quite likely that you're hitting the test timeout, which I would find a more reasonable explanation for the dh_auto_test_error, since the Prometheus tests are quite extensive. They will take more than an hour on an 11th gen Intel Core i7 if I set GOMAXPROCS=1. Since debian/rules is setting a test timeout of 20m by default, this would fail.
OpenPGP_signature.asc
Description: OpenPGP digital signature
