Request for merging "gnome-team" branch

Hi Guix,

gnome-team currently has some important updates to gtk and webkitgtk

that I'd like to see on master. Unfortunately, CI has yet to rebuild

some Java stuff that is ultimately needed by the gnome metapackage. In

the meantime, I'd like y'all to try out some smaller packages –

substitutes for all webkit variants are available.

Cheers

retitle 70766 Request for merging "gnome-team" branch

thanks

Am Samstag, dem 04.05.2024 um 08:41 +0200 schrieb Liliana Marie

Prikler:

I locally built gnome and it builds fine; I haven't tested it yet,

however.

Cheers

Liliana Marie Prikler <liliana.prikler@gmail.com> writes:

Sounds good, there is the open merge request for core-updates, but I

think it's sensible to not block these changes until after core-updates

is dealt with as I think that is realistically still several weeks away

at least. If anyone thinks differently, we can wait instead, but I'll

mark the request to merge core-updates as being blocked by this issue to

signal this.

This might be getting ahead of ourselves as well, but would you be able

to rebase the branch, ideally on the most recently processed master

commit here [1], as that'll enable QA to work out what has changed on

the branch. This should also get rid of the merge commit on the

gnome-team branch, which I think is something to avoid.

1: https://data.qa.guix.gnu.org/repository/2/branch/master

Thanks,

Chris

block 70456 by 70766

thanks

I think being able to merge core-updates is still a few weeks away, so I

think there's time to build and merge gnome-team without delaying

core-updates.

If it does become a problem, we can always switch approach and wait

until after core-updates is merged to look at gnome-team.

Looks like there's some single test failure affecting qtbase. This might

not be because of the changes of this branch, it might just be a flaky

test.

406/507 Test #389: tst_qsqlthread ........................................***Failed 12.82 sec

********* Start testing of tst_QSqlThread *********

Config: Using QtTest library 6.6.3, Qt 6.6.3 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 11.3.0), unknown unknown

QINFO : tst_QSqlThread::initTestCase() SQLite will use the database located at /tmp/guix-build-qtbase-6.6.3.drv-0/tst_qsqlthread-KyeuJe/sqlite.db

QDEBUG : tst_QSqlThread::initTestCase() Opening: "SQLite"

PASS : tst_QSqlThread::initTestCase()

QDEBUG : tst_QSqlThread::simpleThreading(SQLite) Thread finished, total finished: 1

QDEBUG : tst_QSqlThread::simpleThreading(SQLite) Thread finished, total finished: 2

PASS : tst_QSqlThread::simpleThreading(SQLite)

FAIL! : tst_QSqlThread::readWriteThreading(SQLite) '(q2).exec()' returned FALSE. (QSQLITE@: (5) 'Unable to fetch row' || 'database is locked')

Loc: [/tmp/guix-build-qtbase-6.6.3.drv-0/qtbase-everywhere-src-6.6.3/tests/auto/sql/kernel/qsqlthread/tst_qsqlthread.cpp(157)]

QDEBUG : tst_QSqlThread::readWriteThreading(SQLite) Thread finished, total finished: 1

FAIL! : tst_QSqlThread::readWriteThreading(SQLite) 'threadFinishedCount >= 2' returned FALSE. ()

Loc: [/tmp/guix-build-qtbase-6.6.3.drv-0/qtbase-everywhere-src-6.6.3/tests/auto/sql/kernel/qsqlthread/tst_qsqlthread.cpp(376)]

QFATAL : tst_QSqlThread::readWriteThreading(SQLite) QThread: Destroyed while thread is still running

FAIL! : tst_QSqlThread::readWriteThreading(SQLite) Received a fatal error.

Totals: 2 passed, 1 failed, 0 skipped, 0 blacklisted, 10561ms

********* Finished testing of tst_QSqlThread *********

Received signal 6 (SIGABRT)

readWriteThreading function time: 5048ms, total time: 10561ms

CMake Error at tst_qsqlthreadWrapperRelWithDebInfo.cmake:18 (message):

/tmp/guix-build-qtbase-6.6.3.drv-0/build/tests/auto/sql/kernel/qsqlthread/tst_qsqlthread

execution failed with exit code Subprocess aborted.

I'm looking again at the blocked packages, there looks to be a flaky

test in python-scikit-image so I've sent a patch to disable it (#70997).

gtk is failing to build on aarch64-linux which is blocking lots of

packages, and the failure looks familiar but I haven't made any progress

looking at it.

Am Freitag, dem 17.05.2024 um 09:11 +0100 schrieb Christopher Baines:

That looks like trouble. I've fixed up some breaking builds on x86,

but I think we might have to block the merge for now if aarch can't be

fixed.

Feel free to prioritize the other pending merges if that makes more

sense.

Cheers