From: "serhei at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: bunsen@sourceware.org
Subject: [Bug bunsen/25339] [v1.0] dejazilla-style log uploading service
Date: Fri, 16 Sep 2022 17:21:53 +0000 [thread overview]
Message-ID: <bug-25339-12167-LRJ24kGXCD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25339-12167@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25339
Serhei Makarov <serhei at serhei dot io> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |OBSOLETE
Status|NEW |RESOLVED
--- Comment #1 from Serhei Makarov <serhei at serhei dot io> ---
The PR as formulated is not relevant to the new master branch. We could
theoretically add back a secure uploading endpoint, but the canonical way of
adding test results to Bunsen now is to push to a Git repo such as
https://sourceware.org/git/bunsendb.git . If latency becomes an issue, the Git
repo admins could add a post-commit hook to re-run the pipeline (automatically,
or after some threshold of number of results / latency has been reached).
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2022-09-16 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 0:00 [Bug bunsen/25339] New: " me at serhei dot io
2022-09-16 17:21 ` serhei at serhei dot io [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=bug-25339-12167-LRJ24kGXCD@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=bunsen@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).