nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 450821
Commit: 966f3988e607730b03fd7f95fd0a2de30f3895d8

x86_64-linux

10/15 Test #10: message_test .....................   Passed    0.02 sec
      Start 11: match_rule_test
11/15 Test #11: match_rule_test ..................   Passed    0.01 sec
      Start 12: message_router_test
12/15 Test #12: message_router_test ..............   Passed    0.02 sec
      Start 13: service_test
13/15 Test #13: service_test .....................   Passed    0.24 sec
      Start 14: service_watcher_test
14/15 Test #14: service_watcher_test .............   Passed    0.11 sec
      Start 15: signal_delivery_test
15/15 Test #15: signal_delivery_test .............   Passed    0.24 sec
93% tests passed, 1 tests failed out of 15
Total Test time (real) = 609.91 sec
The following tests FAILED:

1 - async_execution_load_test (Failed)

Errors while running CTest

make: *** [Makefile:71: test] Error 8

The check fails in dbus-cpp make me unable to build the lomiri nixos test, i am hoping this one is just flaky.
Edit: was flaky.

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 450821 --package nixosTests.lomiri
Commit: 966f3988e607730b03fd7f95fd0a2de30f3895d8

x86_64-linux

You don't happen to have a full log for the dbus-cpp failure, do you? Would love to know if that's fixable, or just something we'll have to accept and disable the flaky test.

I do actually still have the build log! And for once i didn't accidentally override it with a new build...
dbus-cpp-log.txt

I do actually still have the build log! And for once i didn't accidentally override it with a new build... dbus-cpp-log.txt

Thanks!

• AsyncExecutionLoadTest.RepeatedlyInvokingAnAsyncFunctionWorks is hammering DBus with 5x100 requests, counts how many succeeded, and hopes to have exactly 500 successful roundtrips within 10 minutes. No reporting on what the error was that a DBus request may've run into, so hard to say why 22 of those requests failed.
  Will keep that suite enabled for now and try to make a patch that prints more useful information, to see if this is just a spurious issue with DBus (and thus not worth blocking the build on) or something that's fixable in the setup.
• Executor.TimeoutsAreHandledCorrectly indicates that some memory corruption is happening somewhere (malloc(): unaligned fastbin chunk detected). Don't know a fix OTTOMH, and I can't reproduce it.
  I'll report it upstream and disable the affected suite, in hopes that this is an issue specifically with the way this test is written…

Latest commit should either fix dbus-cpp, or make the output abit more verbose to help with debugging.

Command: nixpkgs-review pr 450821 --package nixosTests.lomiri

(If you want to be super thorough, some of the packages that are end-user applications also have their own VM tests, like lomiri.teleports. But I don't think any of them to have functional changes from any of this.)

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 450821
Commit: 9e32dc6ddb6c513a6567ff366baeadd5133162af

x86_64-linux

I wouldn't be super worried about dbus-cpp, it built/tested on the community builder just fine, it might just be my laptop being cursed. If it builds on hydra, it'll be fine.
That said, it now also just succeeded on my laptop, so i am not sure what is going on.

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 450821 --package nixosTests.lomiri
Commit: 6ef09c0005e5f5974cdd70d8d2422dca89ecd92d

x86_64-linux