Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.14.14-200.fc34
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=77572151
The results of these automated tests are provided below.
Overall result: PASSED
Tests: OK
From: Herton R. Krzesinski on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1435#note_709444857
Acked-by: Herton R. Krzesinski
(via approve button)
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an
From: Justin M. Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1435#note_709420265
Acked-by: Justin M. Forbes
(via approve button)
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email
From: Jiri Olsa on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1435
NOTE: Truncated patchset since committer email 'jo...@kernel.org'
does not match the submitter's GitLab public email address
'jo...@redhat.com'.
Fixes to enable bpf selftest rpm
From: Justin M. Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1433#note_709390882
I am generally okay with this approach. As a separate MR from someone, it
might be interesting to have the config scripts actually do a full check, but
instead of error, just print
From: Don Zickus on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1433#note_709380590
@jstancek - interesting approach. I am open to this latest change. We might
be able to use something similar for -rt and/or -auto and future variants.
@jmflinuxtx - any thoughts on this
From: Don Zickus on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1433#note_709358307
Just an FYI, the CKI team is looking to heavily use gcov as part of the
testing process. In fact, this might be required for us to get certified for
Functional Safety Linux in Auto. So
From: Jan Stancek
redhat/configs: create a separate config for gcov options
Use existing config infrastructure to build and validate
gcov-enabled configs. Meaning for each arch we also apply
GCOV options on top and validate it.
From same options dir (kgcov) build also partial config, which
From: Jan Stancek on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1433#note_709281351
> I am not sure if that hides other things that should be enabled
It does, but gcov was always best-effort kind of feature. It's not built by
default in ARK or RHEL. So I didn't think
