On Mon, Sep 2, 2024 at 5:12 AM zhangdandan <zhangdan...@loongson.cn> wrote: > Now, there are still 2 failing tests. > ``` > 182/185 mutter:core+mutter/x11 / x11 > FAIL 10.27s (exit status 133 or signal > 5 SIGTRAP) > 183/185 mutter:core+mutter/x11 / x11-sync > FAIL 10.27s (exit status 133 or signal > 5 SIGTRAP) > > Ok: 178 > Expected Fail: 5 > Fail: 2 > Unexpected Pass: 0 > Skipped: 0 > Timeout: 0 > > ``` > > Could you add loong64 to the override_dh_auto_test lists in d/rules?
Well that is progress. The Debian GNOME team requests that we have some proof that mutter actually works on a non-release architecture before disabling test failures. The goal here from our perspective is not trying to get loong64 to build 99% of Debian packages, but whether those built packages actually are usable. The strongest evidence is if you can show that GNOME Shell works on that architecture. Alternatively, gnome-settings-daemon has build tests that use mutter. Those currently aren't run on several architectures because mutter is so broken that the tests fail. If you can remove the !loong64 overrides from its debian/control so that the mutter tests run and all pass, I think that could be enough evidence too. Thank you, Jeremy Bícha
