Your message dated Sun, 13 Aug 2023 00:02:24 +0200
with message-id <zngbcl0rd9ek5...@thunder.hadrons.org>
and subject line Re: Bug#1043118: victoriametrics: FTBFS: test failure
has caused the Debian Bug report #1043118,
regarding victoriametrics: FTBFS: test failure
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1043118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: victoriametrics
Version: 1.79.5+ds1-2
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=victoriametrics&arch=amd64&ver=1.79.5%2Bds1-2%2Bb6&stamp=1691274080&raw=0
=== RUN TestMergeForciblyStop
2023-08-05T22:21:13.980Z panic
VictoriaMetrics/lib/storage/inmemory_part.go:37 BUG: Inmemory.InitFromRows must
accept at least one row
--- FAIL: TestMergeForciblyStop (0.00s)
panic: BUG: Inmemory.InitFromRows must accept at least one row [recovered]
panic: BUG: Inmemory.InitFromRows must accept at least one row
goroutine 31839 [running]:
testing.tRunner.func1.2({0x6f7a60, 0xc003b2e4b0})
/usr/lib/go-1.20/src/testing/testing.go:1526 +0x24e
testing.tRunner.func1()
/usr/lib/go-1.20/src/testing/testing.go:1529 +0x39f
panic({0x6f7a60, 0xc003b2e4b0})
/usr/lib/go-1.20/src/runtime/panic.go:884 +0x213
github.com/VictoriaMetrics/VictoriaMetrics/lib/logger.logMessage({0x742b44,
0x5}, {0xc00507f300, 0x37}, 0x0?)
/<<PKGBUILDDIR>>/_build/src/github.com/VictoriaMetrics/VictoriaMetrics/lib/logger/logger.go:269
+0x965
github.com/VictoriaMetrics/VictoriaMetrics/lib/logger.logLevelSkipframes(0x1,
{0x742b44, 0x5}, {0x75c548?, 0xc00503fcc8?}, {0x0?, 0x90?, 0x72aba0?})
/<<PKGBUILDDIR>>/_build/src/github.com/VictoriaMetrics/VictoriaMetrics/lib/logger/logger.go:137
+0x1a5
github.com/VictoriaMetrics/VictoriaMetrics/lib/logger.logLevel(...)
/<<PKGBUILDDIR>>/_build/src/github.com/VictoriaMetrics/VictoriaMetrics/lib/logger/logger.go:129
github.com/VictoriaMetrics/VictoriaMetrics/lib/logger.Panicf(...)
/<<PKGBUILDDIR>>/_build/src/github.com/VictoriaMetrics/VictoriaMetrics/lib/logger/logger.go:125
github.com/VictoriaMetrics/VictoriaMetrics/lib/storage.(*inmemoryPart).InitFromRows(0xc00007ccf0,
{0x0, 0x0, 0x0})
/<<PKGBUILDDIR>>/_build/src/github.com/VictoriaMetrics/VictoriaMetrics/lib/storage/inmemory_part.go:37
+0x5e
github.com/VictoriaMetrics/VictoriaMetrics/lib/storage.newTestBlockStreamReader(0xc0000a6150?,
{0x0, 0x0, 0x0})
/<<PKGBUILDDIR>>/_build/src/github.com/VictoriaMetrics/VictoriaMetrics/lib/storage/block_stream_reader_test.go:151
+0x48
github.com/VictoriaMetrics/VictoriaMetrics/lib/storage.TestMergeForciblyStop(0xc004101380)
/<<PKGBUILDDIR>>/_build/src/github.com/VictoriaMetrics/VictoriaMetrics/lib/storage/merge_test.go:358
+0xce
testing.tRunner(0xc004101380, 0x7e12e8)
/usr/lib/go-1.20/src/testing/testing.go:1576 +0x10b
created by testing.(*T).Run
/usr/lib/go-1.20/src/testing/testing.go:1629 +0x3ea
FAIL github.com/VictoriaMetrics/VictoriaMetrics/lib/storage 10.215s
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Version: 1.79.5+ds1-3
Hi!
On Sun, 2023-08-06 at 11:16:41 +0200, [EXT] Sebastian Ramacher wrote:
> Source: victoriametrics
> Version: 1.79.5+ds1-2
> Severity: serious
> Tags: ftbfs sid trixie
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: sramac...@debian.org
> https://buildd.debian.org/status/fetch.php?pkg=victoriametrics&arch=amd64&ver=1.79.5%2Bds1-2%2Bb6&stamp=1691274080&raw=0
I could not reproduce this, but there was another build failure that
had since been fixed upstream, so that was cherry picked and the
package uploaded. Then there was an aliased directory symlink that was
breaking dpkg in the cheggaaa v1 package, but that has since been
fixed, and the rebuilds now seem to all have succeeded. So I'm going
to close this for now.
If this happens again we can try to look at the new error then.
Closing.
Thanks,
Guillem
--- End Message ---
