Benchmark submissions to elastic have wrong build type

[msimberg]

It seems like there are still cases where the BUILD_TYPE variable is set to Release even though the image used for testing has debug in the name, indicating that it was indeed a debug build. E.g. this query shows two runs with build type Release but with debug and release in the image name: https://kibana.cscs.ch/s/fm/app/discover#/view/79fab3e4-f59f-451f-9821-4b8ced9151e4?_g=(filters:!(),refreshInterval:(pause:!t,value:60000),time:(from:'2024-12-10T10:30:00.000Z',to:'2024-12-10T11:30:00.000Z'))&_a=(columns:!(),dataSource:(dataViewId:e19016d9-f64b-4ebd-8f7f-a1cb498cd3a3,type:dataView),filters:!(),grid:(),hideChart:!f,interval:auto,query:(language:kuery,query:'data_stream.dataset%20:%22service.pika%22%20and%20ci.CI_COMMIT_BRANCH:%20%22main%22%20and%20data_stream.namespace:%22alps%22%20and%20metric.benchmark.name:%22task_size%20-%20thread_pool_scheduler%20-%20task-yield%22%20%20and%20build_configuration.BUILD_TYPE:%22Release%22%20and%20build_configuration.COMPILER:%22gcc@11.4.0%22'),sort:!(!('@timestamp',desc))). I haven't investigated whether there are also cases where both runs have Debug incorrectly.

[aurianer]

The variables including the BUILD_TYPE are not printed in the logs of the build (see here), I think it would be nice to have them printed. What do you think?

[msimberg]

The variables including the BUILD_TYPE are not printed in the logs of the build (see here), I think it would be nice to have them printed. What do you think?

Yep, that certainly wouldn't hurt.

Note that for this particular issue I think the build type is correct at the build step, but my guess is that the propagation of environment variables through the dotenv files isn't working as expected in the test step (likely due to the matrix setup?). So at the very least we'd also want to print relevant environment variables in the test step as well, not only the build step(s).

[aurianer]

Yes I was thinking the same but still wanted to do a sanity check

[msimberg]

Yes I was thinking the same but still wanted to do a sanity check

Yeah, for sure. Whatever the actual cause of this issue is, being more verbose is 100% welcome in any case.