We're standing up a new CI pool to run tests with Wayland. GTests mostly all pass with the exception of cubeb.basic_stream_operations and cubeb.stream_position. Here is the relevant log:

[task 2023-08-02T14:30:02.098Z] 14:30:02     INFO -  TEST-START | cubeb.basic_stream_operations
[task 2023-08-02T14:30:02.106Z] 14:30:02  WARNING -  TEST-UNEXPECTED-FAIL | cubeb.basic_stream_operations | Expected equality of these values:
[task 2023-08-02T14:30:02.106Z] 14:30:02     INFO -    position
[task 2023-08-02T14:30:02.106Z] 14:30:02     INFO -      Which is: 74
[task 2023-08-02T14:30:02.107Z] 14:30:02     INFO -    0u
[task 2023-08-02T14:30:02.107Z] 14:30:02     INFO -      Which is: 0 @ /builds/worker/checkouts/gecko/media/libcubeb/test/test_sanity.cpp:423
[task 2023-08-02T14:30:02.107Z] 14:30:02  WARNING -  TEST-UNEXPECTED-FAIL | cubeb.basic_stream_operations | test completed (time: 8ms)
[task 2023-08-02T14:30:02.107Z] 14:30:02     INFO -  TEST-START | cubeb.stream_position
[task 2023-08-02T14:30:02.120Z] 14:30:02  WARNING -  TEST-UNEXPECTED-FAIL | cubeb.stream_position | Expected equality of these values:
[task 2023-08-02T14:30:02.120Z] 14:30:02     INFO -    position
[task 2023-08-02T14:30:02.121Z] 14:30:02     INFO -      Which is: 147
[task 2023-08-02T14:30:02.121Z] 14:30:02     INFO -    0u
[task 2023-08-02T14:30:02.123Z] 14:30:02     INFO -      Which is: 0 @ /builds/worker/checkouts/gecko/media/libcubeb/test/test_sanity.cpp:481
[task 2023-08-02T14:30:02.139Z] 14:30:02  WARNING -  TEST-UNEXPECTED-FAIL | cubeb.stream_position | test completed (time: 13ms)

from:
https://treeherder.mozilla.org/logviewer?job_id=424653498&repo=try&lineNumber=2776

These tasks can be run on try with:

$ ./mach try fuzzy --full -q "^test-linux2204-64-wayland/opt-gtest-1proc"

We'll need to fix or skip these tests so we can enable the rest of the suite with Wayland. I'll admit, I'm not sure how to skip these tests or I'd go ahead and do it.

Because this is a new test environment, there's also a high likelihood that there is something missing there that needs to be installed. If this is the case, we'd appreciate help figuring out what needs to change.

Can we get in with a debugger, or can we get a pernosco recording? What's the best way to debug this?

Good question! I tried to create an interactive task but it didn't work. I'll follow-up with Release SRE to see if we can get that going.

As far as Pernosco, I'm not sure, I've never used it before. I tried a try push with --pernosco but nothing happened (maybe I need to be added? Or it's still running?). Though this pool is different in that it uses a VM to run the tests rather than a Docker image, so Pernosco might not work with it.

I guess it would be possible to stand up an Ubuntu 22.04 VM that uses Wayland and run tests in there. That's obviously not very convenient though..

It doesn't look related to Wayland at all - I guess it's caused by new Ubutnu 22.04 environment.

The severity field is not set for this bug.
:karlt, could you have a look please?

For more information, please visit BugBot documentation.