Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #16625
| Path | csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod |
|---|---|
| From | Andreas Tille <andreas@an3as.eu> |
| Newsgroups | linux.debian.maint.python |
| Subject | Re: [Help] New package python-loky build time test times out |
| Date | Wed, 25 Dec 2024 22:30:01 +0100 |
| Message-ID | <JXH73-2znP-7@gated-at.bofh.it> (permalink) |
| References | <JXDG9-2vjp-3@gated-at.bofh.it> <JXDPQ-2vAJ-1@gated-at.bofh.it> <JXH73-2znP-9@gated-at.bofh.it> |
| X-Mailbox-Line | From debian-python-request@lists.debian.org Wed Dec 25 21:26:33 2024 |
| Old-Return-Path | <andreas@an3as.eu> |
| X-Amavis-Spam-Status | No, score=-6.798 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, LDO_WHITELIST=-5, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001] autolearn=ham autolearn_force=no |
| X-Policyd-Weight | using cached result; rate:hard: -4.6 |
| MIME-Version | 1.0 |
| Content-Type | text/plain; charset=us-ascii |
| Content-Disposition | inline |
| X-Mailing-List | <debian-python@lists.debian.org> archive/latest/22719 |
| List-ID | <debian-python.lists.debian.org> |
| List-URL | <https://lists.debian.org/debian-python/> |
| List-Archive | https://lists.debian.org/msgid-search/Z2x4eeHMERPtpjza@an3as.eu |
| Approved | robomod@news.nic.it |
| Lines | 23 |
| Organization | linux.* mail to news gateway |
| Sender | robomod@news.nic.it |
| X-Original-Date | Wed, 25 Dec 2024 22:26:17 +0100 |
| X-Original-Message-ID | <Z2x4eeHMERPtpjza@an3as.eu> |
| X-Original-References | <Z2xFFbq2vXFRtB0N@an3as.eu> <Z2xGmc4SThmBpku0@belkar.wrar.name> <1778a548-dff6-4b86-aa17-f8775a53f220@gmail.com> |
| Xref | csiph.com linux.debian.maint.python:16625 |
Show key headers only | View raw
Am Wed, Dec 25, 2024 at 09:43:02PM +0100 schrieb Gregor Riepl: > > Why do you think it's the build-time test? > > The build output looks quite strange to me. > > It almost seems like it gets stuck in the middle of a copy job - the last log line is cut off, but this could be a log buffering issue. The build log is not complete - sorry, forgot to add this information. > @Andreas Did you test the build process (as it's done by Salsa) in a local chroot or build container? I asked for help since it does not finish in my local pbuilder chroot. > Does it get stuck there as well, do you see more output, or perhaps excessive memory usage / CPU load? It might make sense if someone tries to reproduce with sbuild or something else. Kind regards Andreas. -- https://fam-tille.de
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar
[Help] New package python-loky build time test times out Andreas Tille <andreas@an3as.eu> - 2024-12-25 18:50 +0100
Re: [Help] New package python-loky build time test times out Andrey Rakhmatullin <wrar@debian.org> - 2024-12-25 19:00 +0100
Re: [Help] New package python-loky build time test times out Andreas Tille <andreas@an3as.eu> - 2024-12-25 22:30 +0100
Re: [Help] New package python-loky build time test times out Andreas Tille <andreas@an3as.eu> - 2024-12-25 22:30 +0100
Re: [Help] New package python-loky build time test times out c.buhtz@posteo.jp - 2024-12-25 20:40 +0100
Re: [Help] New package python-loky build time test times out Andrey Rakhmatullin <wrar@debian.org> - 2024-12-25 21:00 +0100
Re: [Help] New package python-loky build time test times out c.buhtz@posteo.jp - 2024-12-26 09:50 +0100
Re: [Help] New package python-loky build time test times out Andrey Rakhmatullin <wrar@debian.org> - 2024-12-26 11:00 +0100
csiph-web