Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 872323 - net-misc/frr-8.2.2 doesn't output test results to test-suite.log
Summary: net-misc/frr-8.2.2 doesn't output test results to test-suite.log
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Sergey Popov
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-22 09:28 UTC by Agostino Sarubbo
Modified: 2022-09-22 16:05 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log (build.log,776.97 KB, text/plain)
2022-09-22 09:28 UTC, Agostino Sarubbo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Agostino Sarubbo gentoo-dev 2022-09-22 09:28:24 UTC
https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: net-misc/frr-8.2.2 passed test suite but did not execute any tests.
Discovered on: amd64 (internal ref: tinderbox_musl)

NOTE:
This machine uses MUSL libc
Comment 1 Agostino Sarubbo gentoo-dev 2022-09-22 09:28:27 UTC
Created attachment 813487 [details]
build.log

build log and emerge --info
Comment 2 Jakov Smolić archtester gentoo-dev 2022-09-22 10:58:25 UTC
Tests are being executed and pass correctly looking at the build log, but I guess it doesn't output the final results in the test-suite.log, which is what the QA check is looking for I guess. 

It looks like there is another file generated that contains test results

> - generated xml file: /var/tmp/portage/net-misc/frr-8.2.2/work/frr-frr->8.2.2/tests/tests.xml -

Maybe the QA check can be updated to look for these files as well (I'm not really sure if the same thing is happening with any other package in the tree, so it might also be a build system bug in frr...)
Comment 3 matoro archtester 2022-09-22 16:05:22 UTC
While technically true that the main test suite is invoked via run_tests.py which doesn't output in test-suite.log, there are some optional tests under pceplib/test that are executed based on an automagic dep on dev-util/cunit.  Add that as a dep and we kill two birds with one stone - increase test suite coverage and get rid of the warning.