Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.14.13-200.fc34
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=77444635
The results of these automated tests are provided below.
Overall result: PASSED
Tests: OK
From: Jan Stancek on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1433#note_706658593
I think reason for handling this as build option (in spec file) was that you
could build everything from one srpm. Right now we have 'generic' and 'debug'
config variants, we could add
From: Justin M. Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1431#note_706603437
Acked-by: Justin M. Forbes
(via approve button)
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email
From: Don Zickus on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1433#note_706578162
I ran into this too. I am not a fan of this approach. It solves the problem,
sure. However, part of the problem is that the gcov stuff is hidden behind
the spec file magic. This makes
From: Jan Stancek
redhat: relax configchecks for gcov build
gcov build patches config file during build, which can lead to
configchecks failing with either unset variable or because it
finds a difference between options in source tree and buildroot.
Relax the check for gcov builds to prevent
From: Vladis Dronov on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1431#note_706277921
LGTM
i do not have the "approve" button in a web-interface so i cannot approve
using it.
___
kernel mailing list --
