On Monday 9 September 2024 12:09:44 GMT-7 Christian Ehrlicher via
Development
wrote:
I try to get in some provisioning scripts into qt5.git but it constantly
fails in tst_moc for windows-11_23H2-minimal-static with a timeout.
QtBase points to aec8398d71d351e956683a695af51317fe65097e from start of
september. Don't know what else to do or how to figure out what's going
on wrong there.
Presumably the offending change is not in there, because it passed the CI to
get that change integrated in the first place. In fact, the qtbase update that
got us to that commit did not include any changes to moc, tst_moc or testlib.

But there is one change in COIN itself relating to the windows minimal-static
build, which was the update from MSVC 2019 to 2022.

I also see more than one qt5 integration passing earlier today.
Tried to reproduce it locally and think I found a hint on what's going
wrong even though I could it only reproduce it with the MimerSql plugin:

All test executables are linked against all available static plugins -
so they also get linked against the MimerSql and Interbase plugin. On my
system the dependent mimer64.dll was not in the PATH and I got an error
message about this. This seems to be fine on the test machine as the
MimerSql plugin is there already for a long time.
For Interbase/Firebird I would guess the dependency to fbclient.dll is
pulled in and it's not in the PATH. The interesting question is why the
six tests before tst_moc don't have this problem though.

The fix is to simply disable the sql plugins for the static builds as I
already did for sles-15 static builds. Hope this really fixes my issues :)


Cherrs,
Christian
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Reply via email to