kernelci / kernelci/kernelci-pipeline
Unusual test name of `kunit` skip tests
- Dominant language
- Python
- Stars
- 11
- Forks
- 40
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 14
Description
An investigation is required for an issue I observed for the `kunit` tests.
I noticed the below node with a comment-like description in its name i.e. "example_mark_skipped_test # SKIP this test should be skipped":
```
$ curl https://staging.kernelci.org:9000/node/665964f3f35620b4ed11befa
{"id":"665964f3f35620b4ed11befa","kind":"test","name":"example_mark_skipped_test # SKIP this test should be skipped","path":["checkout","kunit-x86_64","exec","example","example_mark_skipped_test # SKIP this test should be skipped"],"group":"kunit-x86_64","parent":"665964f3f35620b4ed11bef7","state":"done","result":"fail","artifacts":null,"data":{"error_code":null,"error_msg":null,"test_source":null,"test_revision":null,"platform":"kubernetes","device":null,"runtime":"k8s-gke-eu-west4","job_id":null,"job_context":null,"regression":null,"kernel_revision":{"tree":"android","url":"https://android.googlesource.com/kernel/common","branch":"android14-5.15","commit":"d94e16579b8bdab145ea9f655c60b83ee0b2edee","describe":"android14-5.15.149_r00-121-gd94e16579b8b","version":{"version":5,"patchlevel":15,"sublevel":null,"extra":"-30003-gd94e16579b8b","name":null},"patchset":null},"arch":"x86_64","defconfig":null,"config_full":null,"compiler":null,"kernel_type":null},"debug":null,"jobfilter":null,"created":"2024-05-31T05:49:39.298000","updated":"2024-05-31T05:49:39.298000","timeout":"2024-05-31T11:49:39.298000","holdoff":null,"owner":"staging.kernelci.org","submitter":"9790c38bd29c1375fc96ed92b9b4bfab","user_groups":[]}
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the reported node ID and trace how the KernelCI pipeline creates KUnit test nodes and assigns their names. Reproduce or inspect the handling of the `# SKIP` description, then identify the pipeline behavior responsible for the unusual name and confirm the corrected node naming with a KUnit skip test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100