kubernetes runners missing logs and test naming wrong
Maintainers usually reply within 1 day
@nuclearcat is already working on this.
Since Jul 30, 2026.
Assessment
This issue has not been assessed yet.
Description
Two issues
- Log files from the K8 runners are not appearing (i.e. when you look at results there are no logs)
- Test names don't fit the normal format. i.e. accel (from kselftest) come back as accel, and not kselftest-accel (are these runners using test-def?)
- Dominant language
- Python
- Stars
- 120
- Forks
- 108
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 21
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from kernelci/kernelci-core
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
kernelci/kernelci-core#2591 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
kernelci/kernelci-core#3234 ·
Maintainers usually reply within 1 day
-
good first issue techdebt
Difficulty 5/5 Over a week Newbie friendliness 35/100
kernelci/kernelci-core#3197 · 3 comments ·
Maintainers usually reply within 1 day
-
chromeos techdebt
Difficulty 5/5 Over a week Newbie friendliness 35/100
kernelci/kernelci-core#3196 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 20/100
kernelci/kernelci-core#3131 · 3 comments ·
Maintainers usually reply within 1 day
All issues in kernelci/kernelci-core
Similar issues
-
Improve Task Cache Windows Registry events to carry the task subkey's last written time and key pathOpen
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
log2timeline/plaso#5299 · 1 comment ·
Maintainers usually reply within 2 days
-
deployment release-lag
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nolte/kamerplanter#2047 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
ClanGenOfficial/clangen#6216 · 1 comment ·
Maintainers usually reply within 1 day
-
API bug connectors
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
pyinfra-dev/pyinfra#1986 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
521xueweihan/HelloGitHub#3847 ·