Version: 2.45.3+ds-3
El 28/3/24 a las 23:38, Daniel Swarbrick escribió:
On 28.03.24 23:33, Santiago Vila wrote:
If you prefer I could report this build failure in a new report
(or you can also use the clone command so that the bug has a new number,
then close the old bug).
Please report a
On 28.03.24 23:33, Santiago Vila wrote:
If you prefer I could report this build failure in a new report
(or you can also use the clone command so that the bug has a new number,
then close the old bug).
Please report a new bug, with just the relevant info regarding the new
build failure.
We
El 28/3/24 a las 22:42, Daniel Swarbrick escribió:
I think you are taking the "FAILED" out of context and misinterpreting the test
output.
This is very likely, yes, and I'm sorry for that.
If you prefer I could report this build failure in a new report
(or you can also use the clone command
As expected:
=== RUN TestQuerierIndexQueriesRace/[m!="0"___name__="metric"]
panic: test timed out after 20m0s
...
FAILgithub.com/prometheus/prometheus/tsdb 1200.016s
On 28.03.24 23:13, Santiago Vila wrote:
Ok, I'm attaching one of my build logs for version 2.45.3+ds-3.
This one was
El 28/3/24 a las 22:42, Daniel Swarbrick escribió:
Please can you find in your logs the _actual_ failing test or tests, because it
is not TestRulesUnitTest.
Ok, I'm attaching one of my build logs for version 2.45.3+ds-3.
This one was tried on a m6a.large instance from AWS, which has 2 CPUs.
On 28.03.24 15:00, Santiago Vila wrote:
In either case, this is still happening for me in the current version:
Lucas Nussbaum 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.
On 28.03.24 15:00, Santiago Vila wrote:
Daniel Swarbrick wrote:
* Add new 0022-Support-prometheus-common-0.47.0.patch (Closes: #1064765)
Hello. I don't quite understand how the above fix is related to
the bug itself (but maybe it's because I don't know prometheus internals).
As described
found 1064765 2.45.3+ds-3
thanks
Daniel Swarbrick wrote:
* Add new 0022-Support-prometheus-common-0.47.0.patch (Closes: #1064765)
Hello. I don't quite understand how the above fix is related to
the bug itself (but maybe it's because I don't know prometheus internals).
In either case, this
It appears that bumping prometheus/common to 0.47.0 in the prometheus
go.mod will reproduce the test failure.
prometheus/common 0.46.0 and earlier does not provoke the test failure.
OpenPGP_signature.asc
Description: OpenPGP digital signature
9 matches
Mail list logo
