From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: thrift: update (openssl3)
Date: Tue, 14 Mar 2023 22:18:28 +0100 [thread overview]
Message-ID: <20230314211828.Rv_BnQH8XWXQd2hFfvXo9d5gvD3YHYTxe3DZ__pC3r0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41967@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1702 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/pull/41967#issuecomment-1418203294
Comment:
This test was passing before on x86:
```
383/408 Test #383: TServerIntegrationTest ...........***Exception: SegFault 3.85 sec
terminate called after throwing an instance of 'std::system_error'
what(): Resource temporarily unavailable
Running 13 test cases...
unknown location(0): fatal error: in "constructors/test_threaded_stress": signal: SIGABRT (application abort requested)
/builddir/thrift-0.17.0/lib/cpp/test/TServerIntegrationTest.cpp(373): last checkpoint: "test_threaded_stress" test entry
Thrift: Sun Feb 5 15:50:46 2023 TSocket::open() connect() <Host: 127.0.0.1 Port: 32931>: Connection refused
Thrift: Sun Feb 5 15:50:46 2023 TSocket::open() connect() <Host: 127.0.0.1 Port: 32931>: Connection refused
terminate called recursively
unknown location(0): fatal error: in "constructors/test_threadpool_factory": signal: SIGABRT (application abort requested)
/builddir/thrift-0.17.0/lib/cpp/test/TServerIntegrationTest.cpp(378): last checkpoint: "test_threadpool_factory" test entry
Thrift: Sun Feb 5 15:50:46 2023 TSocket::open() connect() <Host: 127.0.0.1 Port: 32931>: Connection refused
Thrift: Sun Feb 5 15:50:46 2023 TSocket::open() connect() <Host: 127.0.0.1 Port: 32931>: Connection refused
terminate called recursively
unknown location(0): fatal error: in "constructors/test_threadpool": signal: SIGABRT (application abort requested)
/builddir/thrift-0.17.0/lib/cpp/test/TServerIntegrationTest.cpp(393): last checkpoint: "test_threadpool" test entry
```
Could the failure be triggered by some change in the containers?
next prev parent reply other threads:[~2023-03-14 21:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 15:26 [PR PATCH] thrift: update distfiles, bump for openssl dkwo
2023-01-30 17:08 ` [PR PATCH] [Updated] " dkwo
2023-01-30 17:12 ` dkwo
2023-01-30 17:13 ` dkwo
2023-01-30 18:15 ` [PR REVIEW] " Duncaen
2023-01-30 18:16 ` Duncaen
2023-01-30 18:18 ` [PR PATCH] [Updated] " dkwo
2023-01-30 18:18 ` [PR REVIEW] " dkwo
2023-01-30 18:21 ` [PR PATCH] [Updated] " dkwo
2023-01-30 18:22 ` dkwo
2023-02-01 16:10 ` [PR REVIEW] thrift: update (openssl3) kruceter
2023-02-01 16:10 ` kruceter
2023-02-01 16:10 ` kruceter
2023-02-01 16:12 ` Duncaen
2023-02-01 16:33 ` dkwo
2023-02-01 16:33 ` [PR REVIEW] " dkwo
2023-02-01 16:34 ` dkwo
2023-02-01 16:35 ` [PR PATCH] [Updated] " dkwo
2023-02-01 16:35 ` dkwo
2023-02-03 23:20 ` kruceter
2023-02-03 23:26 ` [PR REVIEW] " paper42
2023-02-04 16:26 ` [PR PATCH] [Updated] " dkwo
2023-02-04 16:27 ` [PR REVIEW] " dkwo
2023-02-05 15:43 ` [PR PATCH] [Updated] " dkwo
2023-02-05 18:05 ` dkwo
2023-03-06 18:20 ` [PR PATCH] [Updated] " dkwo
2023-03-14 21:18 ` dkwo [this message]
2023-06-02 15:16 ` dkwo
2023-06-02 15:58 ` dkwo
2023-06-02 16:04 ` [PR PATCH] [Updated] " dkwo
2023-06-02 16:13 ` dkwo
2023-06-28 20:42 ` dkwo
2023-06-28 20:48 ` Bnyro
2023-06-28 20:52 ` [PR PATCH] [Merged]: " Duncaen
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=20230314211828.Rv_BnQH8XWXQd2hFfvXo9d5gvD3YHYTxe3DZ__pC3r0@z \
--to=dkwo@users.noreply.github.com \
--cc=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).