the codelets are built but not tested in pipeline

Currently, the codelets are commited as .o files under jbpf_tests/test_files/codelets directory. These static .o files are prebuilt and commited.

In pipeline, the codelets are built, but not used to run the tests. This will create test gaps:

On ubuntu22.04, the clang version is 14.
On ubuntu24.04, the clang version is 18.1

Despite that the codelets are both built and tested in the pipeline for all variants, however, the codelets may fail the verifications.

For example, the codelet is compiled at ubuntu22.04 with clang 14, passing the verification. However the same codelet fails verification at clang 18 on ubuntu24.04

my bad, the codelet verification failed is due to the jbpf_printf_debug that I added. So the question is: would the codelet built using one clang version pass verification but fail on another?

Start in jbpf_tests/test_files/codelets and inspect how the pipeline builds the codelets versus how tests consume the committed .o files. Compare the Ubuntu 22.04/clang 14 and Ubuntu 24.04/clang 18.1 pipeline variants. Done means tests exercise the codelets built in each pipeline variant and expose verification failures caused by compiler differences.