From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by dpdk.org (Postfix, from userid 33) id E7EB01B3A1; Tue, 12 Feb 2019 16:38:53 +0100 (CET) From: bugzilla@dpdk.org To: ci@dpdk.org Date: Tue, 12 Feb 2019 15:38:54 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: lab X-Bugzilla-Component: dashboard X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jplsek@iol.unh.edu X-Bugzilla-Status: CONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: ci@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys 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://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-ci] [Bug 207] JS homepage TypeError with Chrome X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2019 15:38:54 -0000 https://bugs.dpdk.org/show_bug.cgi?id=3D207 Bug ID: 207 Summary: JS homepage TypeError with Chrome Product: lab Version: unspecified Hardware: All OS: All Status: CONFIRMED Severity: normal Priority: Normal Component: dashboard Assignee: ci@dpdk.org Reporter: jplsek@iol.unh.edu CC: jplsek@iol.unh.edu Target Milestone: --- With Chrome [on Windows 10], we get a reported error of: "TypeError: Failed= to fetch" from the Javascript on the homepage. A similar issue occurred with Firefox a while back, but I was able to repro= duce it and handle it (the error occurred when the user tried to go to a differe= nt page in the middle of the JS requesting a page). From the users perspective, there was no issue/difference. It was just an unnecessary exception being thrown. With this issue, I'm not sure if there is a difference, since I am unable to reproduce it. It's possible that it's the same issue as above, but for Chro= me. Putting this ticket in, in case some notices it, and can hopefully report on how to reproduce it. --=20 You are receiving this mail because: You are the assignee for the bug.=