From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] python3-lz4 segfaults when running tests on x86_64-musl
Date: Wed, 01 Jun 2022 04:14:18 +0200 [thread overview]
Message-ID: <20220601021418.F2t14RmwxVW-LvU5lI3fSSk06Cb47pIolEusYfmSvdU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30060@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]
Closed issue by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/30060
Description:
### System
* xuname:
```
Void 5.10.27_1 x86_64-musl AuthenticAMD uptodate FFFF
```
* package: `python3-lz4-3.1.3_1`
### Expected behavior
Running `xbps-src check python3-lz4` in an `x86_64-musl` masterdir should succeed.
### Actual behavior
As run:
```
........................................................................ [ 14%]
..../void-packages/common/build-style/python3-module.sh: line 26: 6982 Segmentation fault python3 -m pytest ${make_check_args} ${make_check_target}
```
Adding `make_check_args="-v"`:
```
tests/block/test_block_0.py::test_1[data7-mode29-store_size1-dictionary4-return_bytearray1] PASSED [ 15%]
tests/block/test_block_0.py::test_2[data0-mode0-store_size0-dictionary0] /void-packages/common/build-style/python3-module.sh: line 26: 12230 Segmentation fault python3 -m pytest ${make_check_args} ${make_check_target}
```
### Steps to reproduce the behavior
```
# On an x86_64-musl host:
./xbps-src binary-bootstrap
# On an x86_64 host:
./xbps-src binary-bootstrap x86_64-musl
sed -i '/^build_style/a make_check_args="-v"' srcpkgs/python3-lz4/template
./xbps-src check python3-lz4
```
@ericonr, if you're bored and looking for something to think about. Alpine is no help because their version of `py3-lz4` is much older.
prev parent reply other threads:[~2022-06-01 2:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 22:47 [ISSUE] python3-lz4 segaults " ahesford
2021-04-06 23:11 ` ahesford
2022-05-17 2:14 ` python3-lz4 segfaults " github-actions
2022-06-01 2:14 ` github-actions [this message]
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=20220601021418.F2t14RmwxVW-LvU5lI3fSSk06Cb47pIolEusYfmSvdU@z \
--to=ml@inbox.vuxu.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).