- Package:
- src:sysbench
- Source:
- sysbench
- Submitter:
- Paul Gevers
- Date:
- 2022-06-09 10:21:03 UTC
- Severity:
- serious
- Tags:
Dear maintainer(s),
With a recent upload of luajit the autopkgtest of knot-resolver fails in
testing when that autopkgtest is run with the binary packages of luajit
from unstable. It passes when run with only packages from testing. In
tabular form:
pass fail
luajit from testing 2.1.0~beta3+git20210112+dfsg-2
knot-resolver from testing 5.4.4-1
all others from testing from testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of luajit to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=luajit
https://ci.debian.net/data/autopkgtest/testing/ppc64el/k/knot-resolver/18781119/log.gz
/usr/sbin/kresd + /usr/bin/kdig roundtrip tests
------------
workdir: /tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts
IP addr: 127.148.62.213
kresd args: --addr=127.148.62.213@8053 --tls=127.148.62.213@8853
--noninteractive
--config=/tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts/kresd.conf
--verbose --verbose --verbose
make Certificate Authority key and certificate
----------------------------------------------
Generating a 3072 bit RSA private key...
Generating a self signed certificate...
X.509 Certificate Information:
Version: 3
Serial Number (hex): 2b34f0d7e93fd713653dda432ddeffed7f9f834b
Validity:
Not Before: Fri Jan 28 19:35:43 UTC 2022
Not After: Wed Feb 09 19:35:43 UTC 2022
Subject: CN=testing certificate authority (NOT FOR PRODUCTION)
Subject Public Key Algorithm: RSA
Algorithm Security Level: High (3072 bits)
Modulus (bits 3072):
00:98:66:36:e9:ce:d2:58:89:bc:a9:ec:ac:21:5e:4b
d2:f3:70:af:5c:41:11:d2:0f:fa:e2:f1:54:65:bc:86
06:4c:55:9f:0e:c3:72:8a:81:75:c3:be:2a:37:20:6a
ce:45:4d:22:00:92:d8:f3:ff:0c:d1:c3:9e:1b:0e:f9
c4:48:38:22:84:f7:a0:6a:bd:e9:34:9d:91:35:00:7b
97:28:c7:6b:49:14:ed:50:81:07:7e:cc:cb:3c:79:cb
fb:52:3d:3c:e0:c5:d9:1d:b5:1f:49:f4:55:74:db:a9
e7:58:fd:83:b6:56:ef:82:07:8f:6f:af:ec:26:b5:40
b4:23:1f:5c:b5:13:47:28:13:8a:58:58:19:f4:8f:3d
7e:12:c2:75:0c:7e:bd:f3:7d:89:f6:b6:3f:8f:63:99
1b:9d:e6:0c:63:fa:a5:5c:5e:08:27:d7:fd:af:3f:7c
54:74:4d:44:3b:ed:66:1a:05:ca:60:94:87:6d:47:c2
5e:8c:3f:1b:d9:60:21:4f:a4:30:1c:0a:21:da:34:0d
a5:cc:df:70:f4:82:71:d4:05:eb:31:0a:2f:59:db:dd
5a:38:15:2a:39:c0:1c:14:2c:cc:3e:b1:dc:97:3d:d7
ff:95:3c:b7:9a:c9:e4:e4:d1:ee:8e:5f:f0:41:d1:f8
2d:4b:6a:36:8d:e8:33:ad:92:b1:7d:65:07:29:56:36
4a:ee:62:75:58:70:f0:99:31:b5:d9:08:8c:68:13:a2
f6:93:38:a9:d7:f9:84:a2:06:29:6f:c8:4c:53:ec:de
37:4b:0a:3c:a9:69:df:57:fd:f0:94:da:d1:a8:5a:8d
40:80:e4:80:5d:85:4c:4a:2f:94:81:9f:e5:a6:a2:49
10:bf:ff:10:11:9f:c6:9d:4d:04:d4:46:f3:25:7c:62
93:7a:43:c9:2d:6a:d5:5a:f2:4a:b7:35:5e:a1:08:f4
a7:30:7a:50:a2:67:c1:f7:2b:17:43:29:0e:3b:34:48
c5
Exponent (bits 24):
01:00:01
Extensions:
Basic Constraints (critical):
Certificate Authority (CA): TRUE
Path Length Constraint: 1
Name Constraints (critical):
Permitted:
DNSname: example
Key Usage (critical):
Certificate signing.
Subject Key Identifier (not critical):
9d5a5828bca2466ede2e930de28e9316dcab390d
Other Information:
Public Key ID:
sha1:9d5a5828bca2466ede2e930de28e9316dcab390d
sha256:f449822d822c9521c68c0b9b0135dd0fe61f7704c65d4f695daf70b73cb4b116
Public Key PIN:
pin-sha256:9EmCLYIslSHGjAubATXdD+YfdwTGXU9pXa9wtzy0sRY=
Signing certificate...
make Bogus Certificate Authority key and certificate
----------------------------------------------------
Generating a 3072 bit RSA private key...
Generating a self signed certificate...
X.509 Certificate Information:
Version: 3
Serial Number (hex): 11e67e6b00d10bc15b65d02f19592b5ddea5cedd
Validity:
Not Before: Fri Jan 28 19:35:44 UTC 2022
Not After: Wed Feb 09 19:35:44 UTC 2022
Subject: CN=testing certificate authority (NOT FOR PRODUCTION)
Subject Public Key Algorithm: RSA
Algorithm Security Level: High (3072 bits)
Modulus (bits 3072):
00:db:a6:14:19:6f:9f:dc:33:b9:01:28:2f:42:f2:8a
f7:c0:90:77:47:88:b7:52:5c:2c:94:f4:ce:f8:bb:4d
82:ef:5c:5d:5a:11:88:e8:8a:ef:1e:40:53:2e:a6:d1
07:af:56:e8:05:4a:ed:1f:ff:70:4e:1a:dd:f5:f7:c4
fc:61:62:f5:a1:55:29:54:16:7c:af:98:a1:8d:70:f7
b7:e2:aa:4d:78:2b:55:2f:58:cc:45:a4:2c:92:ff:18
b4:e3:8f:83:d4:de:39:98:19:8f:40:e3:c4:78:53:43
53:b1:ab:c1:33:f6:61:e1:4c:17:f0:d1:58:a9:02:af
e3:7b:6b:64:7a:5c:11:58:d1:8b:40:77:49:07:cb:e2
16:f5:e9:d8:ad:13:56:ab:f1:96:b2:4e:6e:1b:e5:c2
95:8e:d3:3a:fd:fb:c5:da:2f:b6:88:4c:27:f7:14:2d
bb:f7:38:c9:55:4d:c3:51:25:61:bf:f1:6d:9c:cd:89
99:76:cf:31:34:ab:6f:22:31:1f:f6:eb:b8:0c:4f:83
1c:90:77:00:14:d5:0a:51:08:cd:32:5b:e8:21:ef:6a
7a:6d:da:07:5b:d2:72:56:75:45:0f:6a:d9:b0:7f:71
59:31:49:b0:e4:45:e6:b6:8d:76:65:3d:96:64:35:27
12:ac:53:95:10:46:17:e2:64:cd:ad:a9:01:82:0d:44
f7:64:fa:4b:9c:42:35:07:75:38:a0:4e:9c:84:e2:69
54:4b:80:1c:09:62:2c:29:df:47:cf:46:69:fd:ab:98
aa:aa:28:a8:ac:3e:99:d8:bc:d9:74:ae:de:d9:0a:9e
54:5d:7c:c5:83:5c:07:1d:52:88:29:4e:0d:bc:51:e9
21:62:ca:6c:3f:e7:b2:d9:a7:72:59:b1:26:e6:ef:5a
b5:e5:6e:96:1a:c6:6b:24:9d:1b:04:9c:8d:fd:e9:d8
48:30:c2:78:20:e0:d7:eb:84:84:b9:71:e0:13:70:7d
07
Exponent (bits 24):
01:00:01
Extensions:
Basic Constraints (critical):
Certificate Authority (CA): TRUE
Path Length Constraint: 1
Name Constraints (critical):
Permitted:
DNSname: example
Key Usage (critical):
Certificate signing.
Subject Key Identifier (not critical):
cb341b3dbac0cbc8607ab48daa2219b3c05fb24d
Other Information:
Public Key ID:
sha1:cb341b3dbac0cbc8607ab48daa2219b3c05fb24d
sha256:4ebf7681ca33ddd776669c77039d948f9bcecc420c29cf960efcfef541228aeb
Public Key PIN:
pin-sha256:Tr92gcoz3dd2Zpx3A52Uj5vOzEIMKc+WDvz+9UEiius=
Signing certificate...
make End Entity key and certificate
-----------------------------------
Generating a 3072 bit RSA private key...
Generating a signed certificate...
X.509 Certificate Information:
Version: 3
Serial Number (hex): 0fb6cbc435bcc30d3736d39d58617c6fc39163c4
Validity:
Not Before: Fri Jan 28 19:35:44 UTC 2022
Not After: Mon Feb 07 19:35:44 UTC 2022
Subject: CN=test.example
Subject Public Key Algorithm: RSA
Algorithm Security Level: High (3072 bits)
Modulus (bits 3072):
00:ed:8f:89:4f:42:44:0c:77:25:89:89:fa:56:3c:8f
06:77:67:5a:a4:15:36:d5:59:7a:bb:08:9d:0f:0a:1f
7b:1d:b1:9a:c1:e6:68:71:f9:eb:d8:7e:ea:7f:f7:00
ea:67:4f:7c:dd:0e:ef:88:bf:57:3b:66:f3:a5:9c:9b
67:10:de:5c:a7:5c:e8:d2:0d:c7:d0:62:02:fa:5a:b8
1b:fe:22:59:a8:b9:97:2d:ec:42:0f:8e:33:05:59:d1
36:af:ca:39:82:9d:da:8b:c7:58:94:ca:e7:b2:98:48
31:ed:58:54:bd:41:43:35:e0:14:43:e0:08:60:67:fa
f4:e9:81:63:86:b7:3d:66:e1:ac:d1:e6:37:90:e7:4d
d5:b6:f7:9f:35:53:cb:cb:90:24:17:e4:9c:43:ee:04
1e:e6:75:b0:22:d3:79:d5:a9:83:51:f5:c9:08:dd:25
91:68:9a:fa:e3:f8:a0:07:71:9a:37:b5:41:3d:5e:8d
a3:27:9c:fe:f3:55:fa:b0:33:26:6d:9f:c3:7c:9e:f8
61:3d:7c:76:97:0a:90:af:28:d0:5c:87:f6:86:b8:d7
4e:fe:0a:b7:93:41:77:b6:20:85:a3:17:ec:64:9c:1f
ea:98:73:5d:ce:2a:9e:2a:3b:8e:d0:f2:0a:2c:93:50
f7:bd:2d:63:91:0a:c8:98:8e:b4:97:28:e0:af:6c:b1
4b:e3:05:16:02:54:f0:bf:74:a3:c9:47:f9:89:d6:ed
5f:83:30:ae:a6:91:59:31:14:13:d3:71:65:7b:70:61
39:e7:71:7e:0b:2e:8c:55:5a:8f:1f:4a:27:c7:33:0c
48:d7:d8:61:dd:36:21:33:fc:b8:89:d4:48:70:8e:dd
f5:f0:26:83:86:4e:b1:89:2f:6b:63:74:dd:eb:c9:be
16:20:15:16:e8:2f:10:89:63:14:2c:40:cd:5d:b4:a0
ae:6b:3f:e1:7d:5b:5a:13:7a:7a:c8:29:28:21:4c:e0
73
Exponent (bits 24):
01:00:01
Extensions:
Basic Constraints (critical):
Certificate Authority (CA): FALSE
Subject Alternative Name (not critical):
DNSname: test.example
Key Purpose (not critical):
TLS WWW Server.
Key Usage (critical):
Digital signature.
Subject Key Identifier (not critical):
e7b5b10827689a7f2d6df9f8f862c4822383be14
Authority Key Identifier (not critical):
9d5a5828bca2466ede2e930de28e9316dcab390d
Other Information:
Public Key ID:
sha1:e7b5b10827689a7f2d6df9f8f862c4822383be14
sha256:45999ab3834303a5e1bea7371c8ad58cc57d085d884a0b0354717ecd84829fa0
Public Key PIN:
pin-sha256:RZmas4NDA6Xhvqc3HIrVjMV9CF2ISgsDVHF+zYSCn6A=
Signing certificate...
set up kresd daemon on 127.148.62.213 on ports 8053 (UDP, TCP) and 8853
(TLS)
-----------------------------------------------------------------------------
/tmp/autopkgtest-lxc.7e24ymsu/downtmp/build.B0Q/src/debian/tests/roundtrip:
line 96: 1789 Segmentation fault "$kresd" "${kresd_args[@]}" "$d"
2> "$d/kresd.err"
test UDP with kdig
------------------
;; WARNING: response timeout for 127.148.62.213@8053(UDP)
;; ERROR: failed to query server 127.148.62.213@8053(UDP)
cleaning up
-----------
921111 4 drwxrwxrwt 2 root root 4096 Jan 28 19:35
/tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts
927166 8 -rw------- 1 root root 8167 Jan 28 19:35
/tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts/bogus-key.pem
927161 4 -rw-r--r-- 1 root root 136 Jan 28 19:35
/tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts/ca.template
927176 4 -rw-r--r-- 1 root root 415 Jan 28 19:35
/tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts/kresd.conf
927174 4 -rw-r--r-- 1 root root 1602 Jan 28 19:35
/tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts/ee-cert.pem
927171 8 -rw------- 1 root root 8170 Jan 28 19:35
/tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts/ee-key.pem
927177 4 -rw-r--r-- 1 root root 138 Jan 28 19:35
/tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts/kresd.err
927162 8 -rw------- 1 root root 8167 Jan 28 19:35
/tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts/ca-key.pem
927167 4 -rw-r--r-- 1 root root 1590 Jan 28 19:35
/tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts/bogus-cert.pem
927168 4 -rw-r--r-- 1 root root 92 Jan 28 19:35
/tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts/ee.template
927172 4 -rw-r--r-- 1 root root 2218 Jan 28 19:35
/tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts/ee-pubkey.pem
927165 4 -rw-r--r-- 1 root root 1590 Jan 28 19:35
/tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts/ca-cert.pem
==> /tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts/kresd.err <==
[system] increasing file-descriptor limit: 1024 -> 1048576
[tls ] session ticket: epoch 401220, scheduling rotation check in
2671525 ms
autopkgtest [19:35:47]: test roundtrip
Control: reassign -1 src:luajit 2.1.0~beta3+git20210112+dfsg-2 Control: retitle -1 luajit SEGFAULTs on ppc64el knot-resolver has been removed from testing due to this bug report, but can't migrate back because a newer version fails to build on ppc64el. Also other reverse dependencies of luajit show SEGFAULT in their autopkgtest on ppc64el, so this seems a problem in luajit. Unfortunately (Release Team member opinion) luajit is a key package so can't be trivially removed. Can you (maintainer and ppc64el porters) please have a look? Paul
Hi, If this issue is difficult to fix, how about removing luajit from ppc64el? I noticed that the only reverse (build) dependent key package of luajit (src:efl) already switched to plain lua on ppc64el (probably because of this issue). Paul
Hi Paul, sorry for the late reply. As I said on debian-devel, I've not enough expertise nor hope on that topic. Switching to lua is the way I went a few times, instead on relying on luajit. F.
clone 1004511 -1 -14 block 1004511 by -1 retitle -1 please replace (build) dependency luajit with lua on ppc64el retitle 1004511 RM: luajit [ppc64el] -- ROP; segfaults severity 1004511 normal reassign 1004511 ftp.debian.org clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12 -13 reassign -1 src:aegisub 3.2.2+dfsg-6 reassign -2 src:ettercap 1:0.8.3.1-6 reassign -3 src:knot-resolver 5.4.4-1 reassign -4 src:love 11.3-1 reassign -5 src:luakit 1:2.3-1 reassign -6 src:nageru 2.1.0-1 reassign -7 src:nginx 1.20.2-2 reassign -8 src:obs-studio 27.2.4+dfsg1-1 reassign -9 src:rspamd 3.2-1 reassign -10 src:snort 2.9.15.1-6 reassign -11 src:sysbench 1.0.20+ds-2 reassign -12 src:trafficserver 9.1.2+ds-1 reassign -13 src:uwsgi-plugin-luajit 0.0.7 retitle -14 please prevent successful build on ppc64el until it works thanks Hi, Not convinced I'm totally right there's no key packages in the list above, but let's go this route unless somebody puts up the effort to *maintain* the ppc64el parts. The list above only includes direct depends of libluajit-5.1, I still need to figure out which packages build depend on libluajit-5.1-dev on ppc64el and successfully build there. For the bug which remains assigned to luajit, I want it to ensure that in the future we don't accidentally have a successful build on ppc64el with broken content, so please either drop ppc64el from the list of architectures for which it builds or, better, add a build-time test that fails while luajit segfaults. Paul
Hello, Bug #1011307 in sysbench reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/jcfp/sysbench/-/commit/b8e6a60fc1013421e160158617162e9ec5bc4b9e (this message was generated automatically) -- Greetings https://bugs.debian.org/1011307
We believe that the bug you reported is fixed in the latest version of
sysbench, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1011307@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jeroen Ploemen <jcfp@debian.org> (supplier of updated sysbench package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Tue, 24 May 2022 16:02:10 +0000
Source: sysbench
Architecture: source
Version: 1.0.20+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Jeroen Ploemen <jcfp@debian.org>
Changed-By: Jeroen Ploemen <jcfp@debian.org>
Closes: 1011307
Changes:
sysbench (1.0.20+ds-3) unstable; urgency=medium
.
* Control: disable ppc64el because of problems with luajit on that
arch. (Closes: #1011307)
Checksums-Sha1:
11c1b59888a4ecb6802024a980aa99ce86138c9a 2791 sysbench_1.0.20+ds-3.dsc
686a68e9372abe777cd5151a9a7eedd921ca0830 11624 sysbench_1.0.20+ds-3.debian.tar.xz
df38f32d68d169a37d14cd295d77fa0616ba4a32 8543 sysbench_1.0.20+ds-3_source.buildinfo
Checksums-Sha256:
8c6151bd82efa91f35f206e297e8e4873ab45889bbe7c3e309e101f043e2410a 2791 sysbench_1.0.20+ds-3.dsc
9b748c23c49f600614bc0786b85e4bac89077b8dc14582c81cfbb0e0556ffb89 11624 sysbench_1.0.20+ds-3.debian.tar.xz
070fa38c72782164ae4eeffd198b0eb91dc6bbc83e413706205aad39adc43477 8543 sysbench_1.0.20+ds-3_source.buildinfo
Files:
77c67534532734c4834bca9d614b7e1c 2791 misc optional sysbench_1.0.20+ds-3.dsc
65cec1527f8dce79b80bac3e6e6ed287 11624 misc optional sysbench_1.0.20+ds-3.debian.tar.xz
cfaf99e7f0786d4af8037839f5dddc9f 8543 misc optional sysbench_1.0.20+ds-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEd8lhnEnWos3N8v+qQoMEoXSNzHoFAmKNAbYACgkQQoMEoXSN
zHrCqg//XSgHf21WWQZvxiuu2S/yaXv7bKB3qvG/aY36IeSkjd5jbZtx0oPnRQRy
2NAn3O4y2idQWwK4T8q7qNLU/Bnt38evqA2GoDAthr+kuwX2ajbsi+07WBgcbp/m
HDXlVBEvVAaRzWVBKngZC0a7M9aXxc4jXX6TKWMh7TyIi5N3t2XXHZRoYZGM0cME
br7Ri51lXHOe75yuunJc4aYcrw2/aHIHdo/K88EdHXTyYXQjsNriDIvT/8IZo5Ov
cXyN9RtLYbQeLoTUkaM6khLwgi1/7PtwEk83edz+jR5v6jEqDdEzC9fjPfrQJ0s0
solJ+QPFCb3C76CpnrSMCOMfqrWLP3rDpKyYNv3rQeDEj8wB32A1yfFssGd+5J3y
Xl0OaVKKN2BFXzf4H8spYUdOq3/etGK2wdYh+NRG5kRlqimefgHnl7iJt5cjb65W
epvsIHbEekPZt/1h3kT0+QRnw5l2QkuTtnZHyXSV3NSxXjZK8+Ahju19oxi307In
Ijb5oa68d+P3ZHIomwqaZ+A4Uvi3YgzQsTyMDObsp3w7wFt318r1qym5smkl5cc0
h1lhNrFtss//EE9x1vjxWcHIr3IF+iKE/VgKkj66NiO9M0+TX9XBdRgcPjgdklho
Jv6/DE/3DElJSJxeF70iqPNDi0gTFOjsd/uVy+31m+etRds/hZY=
=G4mE
-----END PGP SIGNATURE-----
A request for the removal of sysbench from ppc64el has been filed in order to allow the recent upload to migrate to testing, see #1012484.
Hi Jeroen, Thanks for fixing this bug. However, in the mean time the maintainer of luajit found an alternative solution (by introducing an alternative luajit source package called luajit2). See transition bug #1012362). So, if you want to you can add support for ppc64el back to your package and close the RM bug. Sorry for the extra work this bug caused, but when I filed it it wasn't clear on what timescale this would happen and if it would work out. Paul