Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)

2023-04-22 Thread Otto Kekäläinen
For the record: After upload of MariaDB 1:10.11.2-3 the MTR test suite failed to start (just timed out) after the build, potentially because the server binary was crashing/defect. On a third try it passed. 1: https://buildd.debian.org/status/fetch.php?pkg=mariadb=s390x=1%3A10.11.2-3=1682066999=0

Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))

2023-02-25 Thread Daniel Black
btw, I never said it was the same bug. Given this was a hang and the MDEV-30728 was a corrupted page read it's likely to be different.

Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))

2023-02-25 Thread Otto Kekäläinen
Thanks for the update Dipak! FYI Paul: According to upstream devs the ppc64el failures we saw in autopkgtests were related to same kernel bug: https://jira.mariadb.org/browse/MDEV-30728 On Fri, 24 Feb 2023 at 11:10, Dipak Zope1 wrote: > > The issue is fixed in 5.10 upstream stable kernel

Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))

2023-02-24 Thread Dipak Zope1
, Paul Gevers Cc: 1030...@bugs.debian.org <1030...@bugs.debian.org>, Daniel Black , Tuukka Pasanen , Faustin Lammler , debian-s...@lists.debian.org Subject: [EXTERNAL] Re: Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: t

Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))

2023-02-13 Thread Dipak Zope1
: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout))) For the record, the failing Debian machines run: Linux ci-worker-s390x-01 5.10.0-21-s390x #1 SMP Debian 5.10.162-1 (2023-01-21) s390x GNU/Linux The passing Launchpad builders run: Linux bos02

Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))

2023-02-11 Thread Otto Kekäläinen
For the record, the failing Debian machines run: Linux ci-worker-s390x-01 5.10.0-21-s390x #1 SMP Debian 5.10.162-1 (2023-01-21) s390x GNU/Linux The passing Launchpad builders run: Linux bos02-s390x-013 5.4.0-137-generic #154-Ubuntu SMP Thu Jan 5 17:03:11 UTC 2023 s390x

Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))

2023-02-11 Thread Paul Gevers
Hi, On 11-02-2023 22:41, Andrew Hutchings wrote: On 11/02/2023 20:17, Paul Gevers wrote: Well, the buildd's don't run bookworm, but they run stable (which currently is bullseye). Sorry, I was told this was Bookworm blocker when this was emailed to me, not a Bullseye one. That is true. But

Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))

2023-02-11 Thread Andrew Hutchings
Hi Paul, On 11/02/2023 20:17, Paul Gevers wrote: Well, the buildd's don't run bookworm, but they run stable (which currently is bullseye). Sorry, I was told this was Bookworm blocker when this was emailed to me, not a Bullseye one. If the intention is to release 10.11 for Bookworm, surely

Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))

2023-02-11 Thread Paul Gevers
Hi, On Wed, 8 Feb 2023 11:42:10 + Andrew Hutchings wrote: Are we 100% sure that Bookworm's kernel on S390x is good? Well, the buildd's don't run bookworm, but they run stable (which currently is bullseye). I am seeing something weird on ci.debian.net too, which also runs stable. I

Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))

2023-02-08 Thread Daniel Black
Some crashes in the signal handler are the just created "MDEV-30613 output_core_info crashes in my_read()" with a probable cause. Doesn't help the original crash reason however. A single thread backtrace isn't sufficient on errors like: " InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded

Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))

2023-02-08 Thread Andrew Hutchings
Hi Otto, We are trying to figure this out but are going in completely blind as we don't have Bookworm on our S390x at the moment, and every other OS we test against is passing. This also doesn't look like anything 10.11 specific, some of this is code that hasn't been touched in a long time.

Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))

2023-02-07 Thread Sebastian Ramacher
Control: severity -1 serious On 2023-02-07 08:36:11 -0800, Otto Kekäläinen wrote: > Control: severity -1 normal > Control: tags -1 help > > The s390x build is still failing after 5 retries at > https://buildd.debian.org/status/package.php?p=mariadb. The issue > seems to be with Debian buildd, as

Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))

2023-02-07 Thread Otto Kekäläinen
Control: severity -1 normal Control: tags -1 help The s390x build is still failing after 5 retries at https://buildd.debian.org/status/package.php?p=mariadb. The issue seems to be with Debian buildd, as the Launchpad s390x build passed just fine without the need to retry anything:

Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout))

2023-02-06 Thread Otto Kekäläinen
And again same phenomenon in https://buildd.debian.org/status/fetch.php?pkg=mariadb=s390x=1%3A10.11.1-3=1675697634=0. Copy-pasting more context to track if the main.xml is the preceding test other times as well: main.group_by_innodb 'innodb'w2 [ pass ] 11

Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)

2023-02-05 Thread Otto Kekäläinen
Control: retitle -1 mariadb: FTBFS on s390x: crash on munmap(), free(), aligned_free() For the record, the latest build https://buildd.debian.org/status/fetch.php?pkg=mariadb=s390x=1%3A10.11.1-3=1675662468=0 shows other test failures again, but the stack trace seem to have munmap(), free(),