Giters

slashbeast / pkg-testing-tools

Archived project, no further development will happen in this repository. Set of tools to simplify package testing for arch stabilizations and package bumps in Gentoo

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Saving build.log with --report or some other parameter

juippis opened this issue · comments

commented

The problem I currently have is that if say 4/16 tests fail, I will only see the failed USE flag combination in the end report, and I'll have to emerge the package again using those USE flags. I'd much rather just open the build.log.

Now my idea is either pair saving build.log to --report, or have a new one, --store-build-log etc. Ideally it'd be saved to a specified path with a date stamp to differ multiple errors for the same package.

--store-build-log '/tmp' would do
/tmp/www-client-firefox-84.0.2-2020-01-09-11-10-48.log
CATEGORY-PACKAGE-YYYY-MM-DD-HH-MM-SS.log

commented

This issue is related to #3 (but I think my idea to handle it is more concrete, not maybe better)
:)

commented

I can workaround this by using PORTAGE_LOGDIR in my env/test.conf which pretty much does what I want.