Hi smcv,
I would like to update the lastest build status of mutter on loong64.
please view the link
https://buildd.debian.org/status/fetch.php?pkg=mutter&arch=loong64&ver=46.4-1&stamp=1725050681&raw=0.
On Thu, 18 Jan 2024 09:49:33 +0000 Simon McVittie wrote:
> On Thu, 18 Jan 2024 at 11:17:08 +0800, yaling fang wrote:
> > Only five cases failed, so I want disabled the case failed firstly.
>
> If our immediate reaction to tests failing on a new architecture is to
> disable them, then the tests have no purpose.
>
> As I asked before: do mutter-based window managers *work* on loong64?
>
> At the moment, the only evidence we have for whether this package is
> usable on loong64 is whether its tests pass.
>
> > test: mutter:core+mutter/x11 / x11
> ...
> > /home/mutter/mutter-44.7/src/tests/x11-test.sh: line 15:
/dev/stderr: No such file or directory
>
> This is a problem with your test environment: please set up /dev
correctly.
> If you had read the log file, you would already have seen this.
>
> > test: mutter:cogl+cogl/conform / cogl-test-journal-gl3
> ...
> >
ERROR:../src/tests/cogl/conform/test-journal.c:41:test_journal_unref_flush:
assertion failed (data == reference_data)
>
35/185 mutter:cogl+cogl/conform / cogl-test-journal-gl3 OK
2.21s
>
> > test: mutter:cogl+cogl/conform / cogl-test-journal-gles2
> ...
> >
ERROR:../src/tests/cogl/conform/test-journal.c:41:test_journal_unref_flush:
assertion failed (data == reference_data)
>
> Same as -gl3 (and probably the same root cause).
36/185 mutter:cogl+cogl/conform / cogl-test-journal-gles2
OK 2.20s
>
> > test: mutter:core+mutter/compositor / stage-views
> ...
> >
mutter-stage-views-test:ERROR:../src/tests/stage-view-tests.c:686:on_transition_stopped:
assertion failed (test->phase == 2): (1 == 2)
>
> Again, this assertion failure indicates a bug somewhere; please
investigate.
128/185 mutter:core+mutter/compositor / stage-views OK 4.32s
> > test: mutter:core+mutter/unit / anonymous-file
> ...
> >
mutter-anonymous-file-test:ERROR:../src/tests/anonymous-file.c:108:test_open_write_read:
assertion failed: (fd != -1)
>
> A file that should have been readable was not readable. Please
investigate
> why.
129/185 mutter:core+mutter/unit / anonymous-file OK 2.02s
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?
