<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi smcv,</p>
<p>I would like to update the lastest build status of mutter on
loong64.</p>
<p>please view the link
<a class="moz-txt-link-freetext" href="https://buildd.debian.org/status/fetch.php?pkg=mutter&arch=loong64&ver=46.4-1&stamp=1725050681&raw=0">https://buildd.debian.org/status/fetch.php?pkg=mutter&arch=loong64&ver=46.4-1&stamp=1725050681&raw=0</a>.<br>
</p>
<p>On Thu, 18 Jan 2024 09:49:33 +0000 Simon McVittie <smcv@debian.org>
wrote:</smcv@debian.org></p>
<p><smcv@debian.org></smcv@debian.org></p>
<smcv@debian.org>> On Thu, 18 Jan 2024 at 11:17:08 +0800, yaling
fang wrote:<br>
> > Only five cases failed, so I want disabled the case
failed firstly.<br>
> <br>
> If our immediate reaction to tests failing on a new
architecture is to<br>
> disable them, then the tests have no purpose.<br>
> <br>
> As I asked before: do mutter-based window managers *work* on
loong64?<br>
> <br>
> At the moment, the only evidence we have for whether this
package is<br>
> usable on loong64 is whether its tests pass.<br>
> <br>
> > test: mutter:core+mutter/x11 / x11<br>
> ...<br>
> > /home/mutter/mutter-44.7/src/tests/x11-test.sh: line 15:
/dev/stderr: No such file or directory<br>
> <br>
> This is a problem with your test environment: please set up
/dev correctly.<br>
> If you had read the log file, you would already have seen
this.<br>
> <br>
> > test: mutter:cogl+cogl/conform / cogl-test-journal-gl3<br>
> ...<br>
> >
ERROR:../src/tests/cogl/conform/test-journal.c:41:test_journal_unref_flush:
assertion failed (data == reference_data)<br>
> <br>
</smcv@debian.org>
<p>35/185 mutter:cogl+cogl/conform /
cogl-test-journal-gl3
OK 2.21s</p>
<smcv@debian.org>> <br>
> > test: mutter:cogl+cogl/conform / cogl-test-journal-gles2<br>
> ...<br>
> >
ERROR:../src/tests/cogl/conform/test-journal.c:41:test_journal_unref_flush:
assertion failed (data == reference_data)<br>
> <br>
</smcv@debian.org>
<p><smcv@debian.org>> Same as -gl3 (and probably the same root
cause).</smcv@debian.org></p>
<p><smcv@debian.org>36/185 mutter:cogl+cogl/conform /
cogl-test-journal-gles2
OK 2.20s<br>
</smcv@debian.org></p>
<p><smcv@debian.org></smcv@debian.org></p>
<smcv@debian.org>> <br>
> > test: mutter:core+mutter/compositor / stage-views<br>
> ...<br>
> >
mutter-stage-views-test:ERROR:../src/tests/stage-view-tests.c:686:on_transition_stopped:
assertion failed (test->phase == 2): (1 == 2)<br>
> <br>
> Again, this assertion failure indicates a bug somewhere;
please investigate.<br>
</smcv@debian.org>
<p><smcv@debian.org>128/185 mutter:core+mutter/compositor /
stage-views
OK 4.32s</smcv@debian.org></p>
<p><smcv@debian.org></smcv@debian.org></p>
<smcv@debian.org>> > test: mutter:core+mutter/unit /
anonymous-file<br>
> ...<br>
> >
mutter-anonymous-file-test:ERROR:../src/tests/anonymous-file.c:108:test_open_write_read:
assertion failed: (fd != -1)<br>
> <br>
> A file that should have been readable was not readable.
Please investigate<br>
> why.<br>
</smcv@debian.org>
<p>129/185 mutter:core+mutter/unit /
anonymous-file
OK 2.02s<br>
</p>
<smcv@debian.org></smcv@debian.org>Now, there are still 2 failing
tests.<br>
```<br>
182/185 mutter:core+mutter/x11 /
x11
FAIL 10.27s (exit status 133 or signal 5 SIGTRAP)<br>
183/185 mutter:core+mutter/x11 /
x11-sync
FAIL 10.27s (exit status 133 or signal 5 SIGTRAP)<br>
<br>
Ok: 178<br>
Expected Fail: 5 <br>
Fail: 2 <br>
Unexpected Pass: 0 <br>
Skipped: 0 <br>
Timeout: 0 <br>
<p>```</p>
<p>Could you add loong64 to the override_dh_auto_test lists in
d/rules?</p>
</body>
</html>