<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>It's a rare port that actually passes all the tests.</div><div><br></div><div>Best to compare with a current system and the previous meson before you conclude anything is wrong for certain.</div><div><br></div><div>I've been running around enabling test suites on everything I can, including meson <<a href="https://github.com/macports/macports-ports/commit/03bd08aa3b13599ca75d899b86ce750aa614ba92#diff-b8e438400c56626bd7fee87efe334c96760964ae9bd38cf171148feb7702613c">https://github.com/macports/macports-ports/commit/03bd08aa3b13599ca75d899b86ce750aa614ba92#diff-b8e438400c56626bd7fee87efe334c96760964ae9bd38cf171148feb7702613c</a>> , in the hopes of getting people to be more rigorous about such things, but I'm often surprised at the poor performance of things on test suites.</div><div><br></div><div>K</div><div><br>On Feb 2, 2021, at 17:32, Craig Treleaven <<a href="mailto:ctreleaven@cogeco.ca">ctreleaven@cogeco.ca</a>> wrote:<br><br></div><blockquote type="cite"><div><blockquote type="cite"><span>On Feb 2, 2021, at 7:26 PM, Craig Treleaven <<a href="mailto:ctreleaven@cogeco.ca">ctreleaven@cogeco.ca</a>> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Anyway, I have 'port test meson' running on my 10.10 system even though I don’t expect anything. I don’t have a working virtualization system at the moment. Perhaps tomorrow I can get that back up and try the tests on 10.9 and earlier. And try to build dav1d to get better log info.</span><br></blockquote><span></span><br><span>Actually, the test phase failed on my 10.10 Mac. I think this is specific test that made it fall over:</span><br><span></span><br><span>g-ir-scanner: link: /usr/bin/clang -o "/opt/local/var/macports/build/_Users_craigtreleaven_mp_macports-ports_devel_meson/meson/work/meson-0.56.2/b b6aebd73f7/tmp-introspectof76ehud/Meson-1.0" -Os "/opt/local/var/macports/build/_Users_craigtreleaven_mp_macports-ports_devel_meson/meson/work/meson-0.56.2/b b6aebd73f7/tmp-introspectof76ehud/Meson-1.0.o" -L. -Wl,-rpath,. "-L/opt/local/var/macports/build/_Users_craigtreleaven_mp_macports-ports_devel_meson/meson/work/meson-0.56.2/b b6aebd73f7/samelibname" "-Wl,-rpath,/opt/local/var/macports/build/_Users_craigtreleaven_mp_macports-ports_devel_meson/meson/work/meson-0.56.2/b b6aebd73f7/samelibname" "-L/opt/local/var/macports/build/_Users_craigtreleaven_mp_macports-ports_devel_meson/meson/work/meson-0.56.2/b b6aebd73f7/" "-Wl,-rpath,/opt/local/var/macports/build/_Users_craigtreleaven_mp_macports-ports_devel_meson/meson/work/meson-0.56.2/b b6aebd73f7/" -lsample -lgobject-2.0 -lglib-2.0 -lintl -lgirepository-1.0 -lgio-2.0 -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lintl -Wl,-framework -Wl,CoreFoundation -L/opt/local/lib -Wl,-headerpad_max_install_names</span><br><span></span><br><span>dyld: Symbol not found: _meson_sample_get_type</span><br><span></span><br><span> Referenced from: /opt/local/var/macports/build/_Users_craigtreleaven_mp_macports-ports_devel_meson/meson/work/meson-0.56.2/b b6aebd73f7/tmp-introspectof76ehud/Meson-1.0</span><br><span> Expected in: /opt/local/var/macports/build/_Users_craigtreleaven_mp_macports-ports_devel_meson/meson/work/meson-0.56.2/b b6aebd73f7/samelibname/libsample.dylib</span><br><span> in /opt/local/var/macports/build/_Users_craigtreleaven_mp_macports-ports_devel_meson/meson/work/meson-0.56.2/b b6aebd73f7/tmp-introspectof76ehud/Meson-1.0</span><br><span>Command '['/opt/local/var/macports/build/_Users_craigtreleaven_mp_macports-ports_devel_meson/meson/work/meson-0.56.2/b b6aebd73f7/tmp-introspectof76ehud/Meson-1.0', '--introspect-dump=/opt/local/var/macports/build/_Users_craigtreleaven_mp_macports-ports_devel_meson/meson/work/meson-0.56.2/b b6aebd73f7/tmp-introspectof76ehud/functions.txt,/opt/local/var/macports/build/_Users_craigtreleaven_mp_macports-ports_devel_meson/meson/work/meson-0.56.2/b b6aebd73f7/tmp-introspectof76ehud/dump.xml']' died with <Signals.SIGTRAP: 5>.</span><br><span>ninja: build stopped: subcommand failed.</span><br><span></span><br><span></span><br><span>I also note that there are a lot of messages saying “dirty”, “missing”, “skipping”, and “warning”. I would hope that if the test phase ran to completion, it would produce a summary of anything important.</span><br><span></span><br><span>Craig</span><br><span></span><br></div></blockquote></body></html>