From: Andreas Schwab <schwab@linux-m68k.org>
To: overseers@sourceware.org
Subject: Command time limit exceeded: "/home/inbox/public-inbox-mda-true.sh"
Date: Sun, 18 Sep 2022 10:26:38 +0200 [thread overview]
Message-ID: <87r109xf41.fsf@linux-m68k.org> (raw)
I got two bounces for inbox@sourceware.org:
<inbox@sourceware.org> (expanded from <gcc-testresults@gcc.gnu.org>): Command
time limit exceeded: "/home/inbox/public-inbox-mda-true.sh"
Reporting-MTA: dns; sourceware.org
X-Postfix-Queue-ID: EB4DB396E06A
X-Postfix-Sender: rfc822; schwab@suse.de
Arrival-Date: Sat, 17 Sep 2022 07:12:04 +0000 (GMT)
Final-Recipient: rfc822; inbox@sourceware.org
Original-Recipient: rfc822;gcc-testresults@gcc.gnu.org
Action: failed
Status: 5.3.0
Diagnostic-Code: x-unix; internal software error
<inbox@sourceware.org> (expanded from <gcc-testresults@gcc.gnu.org>): Command
time limit exceeded: "/home/inbox/public-inbox-mda-true.sh"
Reporting-MTA: dns; sourceware.org
X-Postfix-Queue-ID: B6B58385B837
X-Postfix-Sender: rfc822; schwab@suse.de
Arrival-Date: Sun, 18 Sep 2022 07:11:59 +0000 (GMT)
Final-Recipient: rfc822; inbox@sourceware.org
Original-Recipient: rfc822;gcc-testresults@gcc.gnu.org
Action: failed
Status: 5.3.0
Diagnostic-Code: x-unix; internal software error
The second mail has been properly archived by inbox anyway:
https://inbox.sourceware.org/gcc-testresults/6326c4bd.xsw2e8AsD+VB1+kt%25schwab@suse.de/T/
but the first one is missing:
https://inbox.sourceware.org/gcc-testresults/63257341.fDpdayQ0R%2FQ7zx49%25schwab@suse.de/T/
(linked from https://inbox.sourceware.org/gcc-testresults/, but gives 404)
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next reply other threads:[~2022-09-18 8:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 8:26 Andreas Schwab [this message]
2022-09-20 17:27 ` Frank Ch. Eigler
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=87r109xf41.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).