From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4661B3985C22; Thu, 29 Oct 2020 14:50:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4661B3985C22 From: "fche at redhat dot com" To: elfutils-devel@sourceware.org Subject: [Bug debuginfod/26810] New: handle duplicate buildid data sources, with some stale Date: Thu, 29 Oct 2020 14:50:24 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: elfutils X-Bugzilla-Component: debuginfod X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fche at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone Message-ID: 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-BeenThere: elfutils-devel@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Elfutils-devel mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Oct 2020 14:50:24 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D26810 Bug ID: 26810 Summary: handle duplicate buildid data sources, with some stale Product: elfutils Version: unspecified Status: NEW Severity: normal Priority: P2 Component: debuginfod Assignee: unassigned at sourceware dot org Reporter: fche at redhat dot com CC: elfutils-devel at sourceware dot org Target Milestone: --- On a large debuginfod test server, we observed that it's possible to have t= he same rpm/buildid identified with multiple locations, if the same content is accessible along several paths. That part's fine, but if some of the paths change - get removed - and before the next grooming pass, debuginfod gets confused. That's because multiple matches are tried in series (a sqlite sc= an loop), but an exception ("file not found") from one iteration can unintentionally cancel the scan. So we just need to put a try/catch around the handle_buildid_* function, to assure that other locations of the same content are attempted, regardless of exceptions. --=20 You are receiving this mail because: You are on the CC list for the bug.=