From: "me at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: bunsen@sourceware.org
Subject: [Bug bunsen/25386] New: [post v1.0] general caching infrastructure for analysis results
Date: Wed, 01 Jan 2020 00:00:00 -0000 [thread overview]
Message-ID: <bug-25386-12167@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=25386
Bug ID: 25386
Summary: [post v1.0] general caching infrastructure for
analysis results
Product: bunsen
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: bunsen
Assignee: bunsen at sourceware dot org
Reporter: me at serhei dot io
Target Milestone: ---
Analysis scripts could provide Bunsen with some info for caching.
If the same analysis runs later and the source data is still valid, Bunsen
would then output the stored results.
In more advanced cases, the
related to pr25091 (which requires a basic version of this specific to
+new_regressions)
and to pr25076 (probably requires this to make the web service practical)
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-01-14 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 0:00 me at serhei dot io [this message]
2020-01-01 0:00 ` [Bug bunsen/25386] " me at serhei dot io
2022-09-16 17:24 ` serhei at serhei dot io
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-25386-12167@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).