Without adding the build directory to the PATH,
QStandardPaths::findExecutable will return the temp extractor from the
system, i.e. testing the wrong executable.
Details
- Reviewers
ngraham astippich poboiko - Group Reviewers
Frameworks Baloo - Commits
- R824:0c782040b212: Let tests use the baloo_filemetadata_temp_extractor from the build dir
ctest
Diff Detail
- Repository
- R824 Baloo Widgets
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Windows CI seems not to be happy about this
https://build.kde.org/job/Applications/job/baloo-widgets/job/kf5-qt5%20WindowsMSVCQt5.11
Actually, it is quite happy to report it can not execute the binary in build/bin/, which is IMHO an error in the CI setup.
I don't have windows, so someone else has to look into this.
Sorry, I don't see where it's complaining about not finding the right binary?
(Not finding Dr Konqi is expected, given that it's part of Plasma and not a dependency of baloo-widgets)
Its complaining about not being able to execute the right binary, exception code 0xc0000315.
Given that Baloo Widgets isn't the only project showing that class of failure, it's more likely to be a case of ECM getting something wrong.
(The CI system doesn't do anything special when it comes to this part of the execution)