From: Frank Pursel <frank.pursel@gmail.com>
To: 60976@debbugs.gnu.org
Subject: [bug#60976] [PATCH] gnu: Add ditaa.
Date: Wed, 08 Mar 2023 16:25:47 -0800 [thread overview]
Message-ID: <871qlypy7o.fsf@Ginko.mail-host-address-is-not-set> (raw)
In-Reply-To: <63cb23b3.650a0220.26d15.f66d@mx.google.com>
It is odd that this latest patchset obtained the qa successful badge a
few days after it was posted but then, seemingly spontaneously, the qa
badge reverted to unknown. This is not the first time I've seen the
system complete testing and post the results only to lose it's memory
and then reschedule the work. Seems like a persistence or memoization
mechanism is failing.
Regards,
Frank
prev parent reply other threads:[~2023-03-09 0:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 18:46 [bug#60976] [PATCH] gnu: Add ditaa Frank Pursel
2023-01-24 10:44 ` Simon Tournier
2023-01-25 2:50 ` Frank Pursel
2023-01-25 10:10 ` zimoun
2023-01-25 17:42 ` Frank Pursel
2023-01-26 12:36 ` Simon Tournier
2023-01-26 16:46 ` [bug#60976] [PATCH v4 1/3] gnu: Add java-jericho-html Frank Pursel
2023-01-26 16:53 ` [bug#60976] [PATCH v4 2/3] gnu: Add java-libbatik Frank Pursel
2023-01-26 17:01 ` [bug#60976] [PATCH v4 3/3] gnu: Add ditaa Frank Pursel
2023-08-28 22:50 ` bug#60976: " Vagrant Cascadian
2023-01-26 16:46 ` [bug#60976] [PATCH v3 1/4] gnu: Add java-jericho-html Frank Pursel
2023-02-26 7:47 ` Julien Lepiller
2023-01-26 16:46 ` [bug#60976] [PATCH 1/3] " Frank Pursel
2023-01-27 13:41 ` [bug#60976] [PATCH 3/3] Add ditaa Frank Pursel
2023-01-28 4:49 ` [bug#60976] [PATCH] gnu: " Frank Pursel
2023-03-09 0:25 ` Frank Pursel [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871qlypy7o.fsf@Ginko.mail-host-address-is-not-set \
--to=frank.pursel@gmail.com \
--cc=60976@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).