From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 85327 invoked by alias); 15 Jan 2020 19:40:07 -0000 Mailing-List: contact bunsen-help@sourceware.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Sender: bunsen-owner@sourceware.org Received: (qmail 85288 invoked by uid 48); 15 Jan 2020 19:40:03 -0000 From: "me at serhei dot io" To: bunsen@sourceware.org Subject: [Bug bunsen/25091] [v1.0] analysis: which regressions are truly new? Date: Wed, 01 Jan 2020 00:00:00 -0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: bunsen X-Bugzilla-Component: bunsen X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: me at serhei dot io X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: bunsen at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2020-q1/txt/msg00009.txt https://sourceware.org/bugzilla/show_bug.cgi?id=3D25091 --- Comment #2 from Serhei Makarov --- Figuring out how to cache the +new_regressions analysis in a reasonable way. The problem is that +new_regressions can be run with different key=3D* and window_size/novelty_threshold=3D* arguments. So the cached data must be sto= red in a way that allows recomputation if necessary. My current thought is to store - list of single_change: (name, subtest, outcome_pair) - map of commit_pair -> list of key or '*' - map of commit_pair -> list of (index of) single_change --=20 You are receiving this mail because: You are the assignee for the bug.