Skip to contentSkip to conversation

Clang Testsuite Integration – Initial Progress and Next Steps

DISCUSSION Sundeep KOKKONDA 2 participants 3 messages Aug 4, 2025

lore
Share & tools
lore
#0 lore raw

Hello,

We're currently working on integrating the Clang testsuite into the Yocto Project. As a first step, we've implemented an |oe-selftest| for |clang-native| (we understand this isn't the final goal).

The changes are available here:
🔗 https://git.yoctoproject.org/poky-contrib/log/?h=skokkonda/clang-native

_We are now working on enabling support for testing on target systems. Based on our initial analysis:_

*

The |lit| framework used by Clang doesn't natively support SSH-based remote execution, unlike DejaGnu which provides built-in support for remote testing. So, additional customization is required to enable remote test execution.

*

To enable remote testing, a |lit.site.cfg| file must be generated and configured with SSH access details and target-specific parameters.

*

Currently, QEMU is not launching after the build completes within |oe-selftest|, which is a blocker we’re investigating.

*

Once QEMU is successfully launched, we'll establish SSH connectivity and begin running tests on the target. This will help identify any missing runtime dependencies or other causes of test failures.

We welcome any suggestions or guidance from the community on this approach.

Thanks,

Sundeep KOKKONDA.

#1 lore raw
Quoted 5 lines · Sundeep KOKKONDA

Hello,

We're currently working on integrating the Clang testsuite into the Yocto Project. As a first step, we've implemented an oe-selftest for clang-native (we understand this isn't the final goal).

Quoted 9 lines

The changes are available here:
🔗 https://git.yoctoproject.org/poky-contrib/log/?h=skokkonda/clang-native

We are now working on enabling support for testing on target systems. Based on our initial analysis:

The lit framework used by Clang doesn't natively support SSH-based remote execution, unlike DejaGnu which provides built-in support for remote testing. So, additional customization is required to enable remote test execution.

To enable remote testing, a lit.site.cfg file must be generated and configured with SSH access details and target-specific parameters.

This approach seems right to me. something like below might work for ssh'ing into target and running tests.

ssh_cmd = f"ssh ..."
config.substitutions.append(('%run', ssh_cmd))

Quoted 2 lines

Currently, QEMU is not launching after the build completes within oe-selftest, which is a blocker we’re investigating.

like ssh case you should be able to run with config.substitutions.append(('%run', launch_qemu))

Quoted 9 lines

Once QEMU is successfully launched, we'll establish SSH connectivity and begin running tests on the target. This will help identify any missing runtime dependencies or other causes of test failures.

We welcome any suggestions or guidance from the community on this approach.

Thanks,

Sundeep KOKKONDA.

#2 lore raw

btw take a look at https://github.com/llvm/llvm-test-suite.git as well. it would be good to add this to test matrix once tests are working.

Quoted 40 lines · Khem Raj
Quoted 5 lines · Sundeep KOKKONDA

Hello,

We're currently working on integrating the Clang testsuite into the Yocto Project. As a first step, we've implemented an oe-selftest for clang-native (we understand this isn't the final goal).

Quoted 9 lines

The changes are available here:
🔗 https://git.yoctoproject.org/poky-contrib/log/?h=skokkonda/clang-native

We are now working on enabling support for testing on target systems. Based on our initial analysis:

The lit framework used by Clang doesn't natively support SSH-based remote execution, unlike DejaGnu which provides built-in support for remote testing. So, additional customization is required to enable remote test execution.

To enable remote testing, a lit.site.cfg file must be generated and configured with SSH access details and target-specific parameters.

This approach seems right to me. something like below might work for ssh'ing into target and running tests.

ssh_cmd = f"ssh ..."
config.substitutions.append(('%run', ssh_cmd))

Quoted 2 lines

Currently, QEMU is not launching after the build completes within oe-selftest, which is a blocker we’re investigating.

like ssh case you should be able to run with config.substitutions.append(('%run', launch_qemu))

Quoted 9 lines

Once QEMU is successfully launched, we'll establish SSH connectivity and begin running tests on the target. This will help identify any missing runtime dependencies or other causes of test failures.

We welcome any suggestions or guidance from the community on this approach.

Thanks,

Sundeep KOKKONDA.