Summary: | net-analyzer/zabbix-5.2.6 fails tests | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
Component: | Current packages | Assignee: | Miroslav Šulc <fordfrog> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | public, whissi |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 777855 | ||
Attachments: |
build.log.xz
make check output for zabbix 5.2.5 |
Description
Agostino Sarubbo
2021-03-09 10:39:44 UTC
Created attachment 690180 [details]
build.log.xz
build log and emerge --info (compressed because it exceeds attachment limit, use 'xzless' to read it)
Possible context of error(s): go: cannot find main module; see 'go help modules' 2021/03/09 09:19:05.283223 [0] cache is full and cannot cannot find a value to replace, adding new instead 2021/03/09 09:19:05.283265 [0] cache is full and cannot cannot find a value to replace, adding new instead conf_test.go:162: Returned error: Cannot assign configuration: cannot find mandatory parameter Text 2021/03/09 09:19:05.217205 deactivate exporter task for item 1 because of error: Invalid update interval "xyz". Looks like there are failing tests upstream. I can replicate this by running commands manually (without portage):
> make check
...
--- FAIL: TestPassiveRunner (0.01s)
manager_test.go:234: starting time Mar 9 10:21:50
manager_test.go:396: Plugin debug1:$start: no matching timestamp for offset 1
manager_test.go:396: Plugin debug2:$start: no matching timestamp for offset 1
manager_test.go:396: Plugin debug3:$start: no matching timestamp for offset 1
manager_test.go:396: Plugin debug3:$stop: no matching timestamp for offset 93601
manager_test.go:396: Plugin debug2:$stop: no matching timestamp for offset 183601
...
FAIL
FAIL zabbix.com/internal/agent/scheduler 0.028s
...
--- FAIL: TestFileExists (0.00s)
exists_test.go:44: vfs.file.exists returned invalid result
FAIL
FAIL zabbix.com/plugins/vfs/file 0.006s
...
I tried commenting out some of the tests, but this part is weird: manager_test.go:396: Plugin debug1:$start: no matching timestamp for offset 1 manager_test.go:396: Plugin debug2:$start: no matching timestamp for offset 1 manager_test.go:396: Plugin debug3:$start: no matching timestamp for offset 1 manager_test.go:396: Plugin debug3:$stop: no matching timestamp for offset 93601 manager_test.go:396: Plugin debug2:$stop: no matching timestamp for offset 183601 These errors are preceded by messages like: cannot monitor metric "debug1": The "debug1" key is not supported in test or single passive check mode As if the metrics that are being tested are not supported in test mode? Created attachment 690303 [details]
make check output for zabbix 5.2.5
Also failing tests for x86. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=255eb48f0fa1ecf60e08194146046bd91dd01d26 commit 255eb48f0fa1ecf60e08194146046bd91dd01d26 Author: Miroslav Šulc <fordfrog@gentoo.org> AuthorDate: 2021-06-30 10:59:47 +0000 Commit: Miroslav Šulc <fordfrog@gentoo.org> CommitDate: 2021-06-30 11:00:03 +0000 net-analyzer/zabbix: tests disabled upstream tests fail so disabling them for now Closes: https://bugs.gentoo.org/775011 Package-Manager: Portage-3.0.20, Repoman-3.0.3 Signed-off-by: Miroslav Šulc <fordfrog@gentoo.org> net-analyzer/zabbix/zabbix-5.0.12-r1.ebuild | 3 +++ net-analyzer/zabbix/zabbix-5.2.6-r1.ebuild | 3 +++ net-analyzer/zabbix/zabbix-5.4.1-r1.ebuild | 3 +++ 3 files changed, 9 insertions(+) |