Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E5A3D200C34 for ; Mon, 27 Feb 2017 14:34:48 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id E4166160B6C; Mon, 27 Feb 2017 13:34:48 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 37C9E160B60 for ; Mon, 27 Feb 2017 14:34:48 +0100 (CET) Received: (qmail 66292 invoked by uid 500); 27 Feb 2017 13:34:47 -0000 Mailing-List: contact issues-help@jmeter.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@jmeter.apache.org Delivered-To: mailing list issues@jmeter.apache.org Received: (qmail 66280 invoked by uid 99); 27 Feb 2017 13:34:47 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Feb 2017 13:34:47 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id C6A77C150C for ; Mon, 27 Feb 2017 13:34:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.651 X-Spam-Level: X-Spam-Status: No, score=0.651 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id uJjS5vqXJG7t for ; Mon, 27 Feb 2017 13:34:44 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id A07715F23A for ; Mon, 27 Feb 2017 13:34:44 +0000 (UTC) Received: from asf-bz1-us-mid.priv.apache.org (nat1-us-mid.apache.org [23.253.172.122]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTPS id 09218E00D5 for ; Mon, 27 Feb 2017 13:34:43 +0000 (UTC) Received: by asf-bz1-us-mid.priv.apache.org (ASF Mail Server at asf-bz1-us-mid.priv.apache.org, from userid 33) id AC242606CC; Mon, 27 Feb 2017 13:34:42 +0000 (UTC) From: bugzilla@apache.org To: issues@jmeter.apache.org Subject: [Bug 60779] New: GUI: Option to clean logs in Log Viewer console automatically before test execution Date: Mon, 27 Feb 2017 13:34:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: JMeter X-Bugzilla-Component: Main X-Bugzilla-Version: 3.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: luborpetr@gmail.com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: issues@jmeter.apache.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 target_milestone attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bz.apache.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 archived-at: Mon, 27 Feb 2017 13:34:49 -0000 https://bz.apache.org/bugzilla/show_bug.cgi?id=3D60779 Bug ID: 60779 Summary: GUI: Option to clean logs in Log Viewer console automatically before test execution Product: JMeter Version: 3.1 Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P2 Component: Main Assignee: issues@jmeter.apache.org Reporter: luborpetr@gmail.com Target Milestone: --- Created attachment 34782 --> https://bz.apache.org/bugzilla/attachment.cgi?id=3D34782&action=3Dedit Clean Logs Feature integration in options menu Hello, Could you please add new configurable feature into JMeter GUI, enabling possibility to clean logs in Log Viewer console automatically before test execution? Motivation: While debugging new test plans, I often end in a situation, where I was una= ble to clearly distinguish log entries from actual test run and previous attemp= ts. This new feature (when enabled) will clean log entries before test executio= n, so the logs you see after the test is done relates just to one particular attempt. Use case description: 1) User enabled "log clean feature" in JMeter options menu 2) User clicks on =E2=80=9CStart=E2=80=9D button 3) Log Viewer console entries are cleaned (if there were any from prev= ious runs) 4) Test execution continues usual way When the feature is disabled, Log viewer contains logs from all tests playe= d as it is for now.. Example how this feature can be integrated into GUI in attached screenshot. Thanks a lot. L. --=20 You are receiving this mail because: You are the assignee for the bug.=