Re: [ITA] glib2.0
Jon Turney via Cygwin-apps <[email protected]>
| Newsgroups | gmane.os.cygwin.applications |
|---|---|
| Message-ID | <[email protected]> |
On 09/05/2025 13:49, Takashi Yano via Cygwin-apps wrote: > On Sun, 4 May 2025 21:44:34 +0100 > Jon Turney wrote: >> On 23/02/2025 12:33, Takashi Yano via Cygwin-apps wrote: >>> Hi, >>> >>> I would like to adopt glib2.0 package, because latest pango 1.56.1 >>> requires newer glib2.0. >> Thanks very much for adopting this package (since it has over 900 >> rdepends, it's kind of important!) >> >> Since glib has an extensive test suite, I humbly suggest you might want >> to run it on occasion, to look out for regressions. >> >> I have somewhere some more extensive notes on the existing failures and >> their causes, beyond the cygwin/newlib shortcomings identified in [1], >> which I can dig out and share with you, if you like. >> >> [1] https://cygwin.com/pipermail/cygwin-developers/2023-July/012637.html > > Thanks for the advice. Currently, the test result is: > Ok: 337 > Expected Fail: 0 > Fail: 24 > Unexpected Pass: 0 > Skipped: 5 > Timeout: 26 > > Does this seem to regress from that when you checked? So, in my notes I have written OK: 224 Fail: 20 Timeout: 26 It seems quite a few new tests have been added. (but then I went back and fixed a something in my test environment, and then added glib-testsuite-fixes-for-cygwin.patch, but didn't record the numbers afterwards, so perhaps not very useful) I do have the attached notes on the specific tests that failed, and the few where I did a bit more investigation. I guess I should have just checked that in to the git repo. Sorry I didn't keep more meticulous records.
glib-failures.txt
(text/plain, 5.4 KB)
37/270 glib:glib / collate FAIL 8.16s killed by signal 6 SIGABRT 43/270 glib:glib+slow / gdatetime FAIL 8.54s killed by signal 6 SIGABRT 68/270 glib:glib / test-printf FAIL 4.01s killed by signal 11 SIGSEGV 81/270 glib:glib / uri FAIL 7.86s killed by signal 6 SIGABRT 108/270 glib:glib / unix FAIL 14.73s killed by signal 6 SIGABRT 116/270 glib:gobject / signals FAIL 13.94s killed by signal 6 SIGABRT 121/270 glib:glib / mainloop TIMEOUT 60.56s killed by signal 15 SIGTERM 138/270 glib:gio / appmonitor FAIL 17.22s killed by signal 6 SIGABRT 160/270 glib:gio / giomodule FAIL 20.49s killed by signal 6 SIGABRT 166/270 glib:gio / network-address FAIL 20.88s killed by signal 6 SIGABRT 169/270 glib:gio / socket FAIL 22.19s killed by signal 6 SIGABRT 170/270 glib:gio+slow+flaky / testfilemonitor FAIL 21.79s killed by signal 6 SIGABRT 174/270 glib:gobject / threadtests TIMEOUT 60.18s killed by signal 15 SIGTERM 175/270 glib:gio / gdbus-peer FAIL 19.69s killed by signal 6 SIGABRT 178/270 glib:gio / unix-fd FAIL 17.23s killed by signal 6 SIGABRT 182/270 glib:gio / live-g-file FAIL 37.34s killed by signal 6 SIGABRT 185/270 glib:gio / gdbus-server-auth TIMEOUT 60.43s killed by signal 15 SIGTERM 187/270 glib:gio / stream-rw_all TIMEOUT 60.34s killed by signal 15 SIGTERM 188/270 glib:gio / desktop-app-info TIMEOUT 60.21s killed by signal 15 SIGTERM 189/270 glib:gio / gdbus-bz627724 TIMEOUT 64.27s killed by signal 6 SIGABRT 190/270 glib:gio / gdbus-connection TIMEOUT 60.17s killed by signal 6 SIGABRT 191/270 glib:gio / gdbus-connection-loss TIMEOUT 60.58s killed by signal 6 SIGABRT 192/270 glib:gio / gdbus-connection-slow TIMEOUT 60.71s killed by signal 6 SIGABRT 193/270 glib:gio / gdbus-exit-on-close TIMEOUT 61.67s killed by signal 15 SIGTERM 194/270 glib:gio / gdbus-introspection TIMEOUT 60.32s killed by signal 6 SIGABRT 195/270 glib:gio / gdbus-names TIMEOUT 60.13s killed by signal 6 SIGABRT 196/270 glib:gio / gdbus-proxy TIMEOUT 60.12s killed by signal 6 SIGABRT 197/270 glib:gio / gdbus-proxy-threads TIMEOUT 60.32s killed by signal 6 SIGABRT 198/270 glib:gio / gdbus-proxy-unique-name TIMEOUT 62.99s killed by signal 6 SIGABRT 199/270 glib:gio / gdbus-proxy-well-known-name TIMEOUT 61.04s killed by signal 6 SIGABRT 200/270 glib:gio / gdbus-test-codegen TIMEOUT 61.20s killed by signal 6 SIGABRT 201/270 glib:gio+slow / actions TIMEOUT 180.16s 202/270 glib:gio / gnotification TIMEOUT 68.57s killed by signal 15 SIGTERM 203/270 glib:gio / gdbus-test-codegen-old TIMEOUT 61.41s killed by signal 6 SIGABRT 204/270 glib:gio / gdbus-test-codegen-min-required-2-64 TIMEOUT 60.45s killed by signal 6 SIGABRT 205/270 glib:gio / gdbus-non-socket FAIL 11.93s killed by signal 6 SIGABRT 207/270 glib:gio / gdbus-connection-flush FAIL 13.83s killed by signal 6 SIGABRT 220/270 glib:gio+slow / gdbus-export TIMEOUT 182.78s killed by signal 6 SIGABRT 229/270 glib:gio / gapplication TIMEOUT 60.32s 241/270 glib:gio / dbus-appinfo TIMEOUT 60.33s killed by signal 15 SIGTERM 262/270 glib / glib-doc-check FAIL 0.29s exit status 2 269/270 glib:gio+slow / gdbus-threading TIMEOUT 180.26s killed by signal 6 SIGABRT 270/270 glib:gio+slow / gmenumodel TIMEOUT 180.35s collate: "üĠണ" converted to "en_US" locale is null string (conversion fails) this seems reasonable this makes it not sort as "u", which the test expects gdatetime: expects O modifier in strftime (%OH etc.) to produce Persian digit characters in fa_IR.utf-8 locale, we don't do that test-printf: triggers a segfault in newlib sprintf signals: garbage in hibyte of long passed through ffi appmonitor: gamin is started, but doesn't notice or report the change? network_address: looking for scope on loopback_4 interface doesn't work as expected testfilemonitor: looks like GPollFileMonitor doesn't notice any changes live-g-file: able to move a file to directory without x permission, seems wrong stream_rw-all: test_read_write_all_async_pipe blocks when claims it's writable... (this seems a bit wonky as just because it can take 1 byte doesn't mean it can take 100, but adjusting the number in obvious ways doesn't help)