From: "Girar awaiter (zerg)" <girar-builder@altlinux.org>
To: "Sergey V. Turchin" <zerg@altlinux.org>
Cc: girar-builder-p10@altlinux.org,
sisyphus-incominger@lists.altlinux.org,
girar-builder-p10@lists.altlinux.org
Subject: [#341419] [test-only] p10 FAILED (try 2) ell.git=0.59-alt1 bluez.git=5.72-alt2
Date: Mon, 26 Feb 2024 09:23:17 +0000
Message-ID: <girar.task.341419.2.1@gyle.mskdc.altlinux.org> (raw)
In-Reply-To: <girar.task.341419.1.1@gyle.mskdc.altlinux.org>
https://git.altlinux.org/tasks/341419/logs/events.2.1.log
subtask name aarch64 armh i586 ppc64le x86_64
#40 ell 47 1:06 29 54 28
#100 bluez 3:38 failed 2:33 3:48 2:11
2024-Feb-26 09:17:15 :: test-only task #341419 for p10 resumed by zerg:
2024-Feb-26 09:17:15 :: message: update
#40 build 0.59-alt1 from /gears/e/ell.git fetched at 2024-Feb-26 09:17:06 from sisyphus
#100 build 5.72-alt2 from /gears/b/bluez.git fetched at 2024-Feb-26 08:40:14 from sisyphus
2024-Feb-26 09:17:15 :: created build repo
2024-Feb-26 09:17:16 :: #100: force rebuild
2024-Feb-26 09:17:17 :: [aarch64] #40 ell.git 0.59-alt1: build start
2024-Feb-26 09:17:17 :: [i586] #40 ell.git 0.59-alt1: build start
2024-Feb-26 09:17:17 :: [armh] #40 ell.git 0.59-alt1: build start
2024-Feb-26 09:17:17 :: [x86_64] #40 ell.git 0.59-alt1: build start
2024-Feb-26 09:17:17 :: [ppc64le] #40 ell.git 0.59-alt1: build start
2024-Feb-26 09:17:45 :: [x86_64] #40 ell.git 0.59-alt1: build OK
2024-Feb-26 09:17:45 :: [x86_64] #100 bluez.git 5.72-alt2: build start
2024-Feb-26 09:17:46 :: [i586] #40 ell.git 0.59-alt1: build OK
2024-Feb-26 09:17:46 :: [i586] #100 bluez.git 5.72-alt2: build start
2024-Feb-26 09:18:04 :: [aarch64] #40 ell.git 0.59-alt1: build OK
2024-Feb-26 09:18:04 :: [aarch64] #100 bluez.git 5.72-alt2: build start
2024-Feb-26 09:18:11 :: [ppc64le] #40 ell.git 0.59-alt1: build OK
2024-Feb-26 09:18:11 :: [ppc64le] #100 bluez.git 5.72-alt2: build start
2024-Feb-26 09:18:23 :: [armh] #40 ell.git 0.59-alt1: build OK
2024-Feb-26 09:18:24 :: [armh] #100 bluez.git 5.72-alt2: build start
2024-Feb-26 09:19:56 :: [x86_64] #100 bluez.git 5.72-alt2: build OK
2024-Feb-26 09:20:19 :: [i586] #100 bluez.git 5.72-alt2: build OK
2024-Feb-26 09:21:42 :: [aarch64] #100 bluez.git 5.72-alt2: build OK
2024-Feb-26 09:21:59 :: [ppc64le] #100 bluez.git 5.72-alt2: build OK
[armh] ./test-driver: line 109: 265790 Segmentation fault "$@" > $log_file 2>&1
[armh] FAIL: unit/test-vcp
[armh] armh-alt-linux-gnueabi-gcc -DHAVE_CONFIG_H -I. -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I./lib -DMIDI_TEST -pipe -frecord-gcc-switches -Wall -g -O2 -fomit-frame-pointer -march=armv7-a -mthumb -DFIRMWARE_DIR=\""/lib/firmware"\" -c -o unit/test_midi-test-midi.o `test -f 'unit/test-midi.c' || echo './'`unit/test-midi.c
[armh] --
[armh] # SKIP: 0
[armh] # XFAIL: 0
[armh] # FAIL: 1
[armh] # XPASS: 0
[armh] # ERROR: 0
[armh] See ./test-suite.log
2024-Feb-26 09:23:16 :: [armh] bluez.git 5.72-alt2: remote: build failed
2024-Feb-26 09:23:16 :: [armh] #100 bluez.git 5.72-alt2: build FAILED
2024-Feb-26 09:23:16 :: [armh] requesting cancellation of task processing
2024-Feb-26 09:23:17 :: [armh] build FAILED
2024-Feb-26 09:23:17 :: task #341419 for p10 FAILED
next prev parent reply other threads:[~2024-02-26 9:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 8:45 [#341419] [test-only] p10 FAILED bluez.git=5.72-alt2 Girar awaiter (zerg)
2024-02-26 9:23 ` Girar awaiter (zerg) [this message]
2024-02-26 12:35 ` [#341419] p10 TESTED (try 3) ell.git=0.59-alt1 bluez.git=5.72-alt1.p10.1 Girar awaiter (zerg)
2024-02-26 12:46 ` [#341419] p10 EPERM (try 4) " Girar awaiter (zerg)
2024-03-13 13:21 ` [#341419] p10 DONE (try 5) " Girar pender (amakeenk)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=girar.task.341419.2.1@gyle.mskdc.altlinux.org \
--to=girar-builder@altlinux.org \
--cc=devel@lists.altlinux.org \
--cc=girar-builder-p10@altlinux.org \
--cc=girar-builder-p10@lists.altlinux.org \
--cc=sisyphus-incominger@lists.altlinux.org \
--cc=zerg@altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
ALT Linux Girar Builder robot reports
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/sisyphus-incominger/0 sisyphus-incominger/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 sisyphus-incominger sisyphus-incominger/ http://lore.altlinux.org/sisyphus-incominger \
sisyphus-incominger@lists.altlinux.org sisyphus-incominger@lists.altlinux.ru sisyphus-incominger@lists.altlinux.com
public-inbox-index sisyphus-incominger
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.sisyphus-incominger
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git