Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp34954399rwd; Sun, 9 Jul 2023 23:57:54 -0700 (PDT) X-Google-Smtp-Source: APBJJlGR0eKgazeWnflbpX5s/z7/cMhoOdD6XqdrMJxq+hNXqtd3xZxGeFiGDOnK1l3JtWpJJ3Ea X-Received: by 2002:a05:6358:5285:b0:12b:da97:aba6 with SMTP id g5-20020a056358528500b0012bda97aba6mr9771680rwa.24.1688972273990; Sun, 09 Jul 2023 23:57:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1688972273; cv=none; d=google.com; s=arc-20160816; b=g9YvI8f8LTof7STnYmt/zwKlZDTcADD5nzlCJnUU9dPyMA7wbLS7kkLBiLwRekqE4x RInQWdR7tj7ng4otrwSVFu/JfogrAaqWPzzDqayf13R5cnFW0VYTb+tsKV+BPTbnRf9t MhPOQiB0O3GoLQGjrMlKhvH6OG/LNYrqAMZt7hzYjrsU7xzCfNe2JqDW9k0lXXZ5Lc9P jWiBwHuuQ51cCB7KAFAofN5nfhaRjTufMxaWBMeJPbx3aljizQk9m3brwFwKKS6OU4uz LLlKSQrDCvQlc6SN70SlH1ZQ24Q/ZlxL6z49R1s7hvbp343LmHrR0y+gYAEnXphiRNty jZqg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=/F7a4hoQC/aBudaAPsVOcAMIYu1NIpm3g9xPbVkOfXs=; fh=tcl19X2u8PtEELiqC9wF/fi8DNcGozPCtYGeW6FgzSg=; b=AAD9UnFhm7G+DD40zn8IXurY+aPjY6VkjHSPT+QItW8EEBnkYLCsy2Bn+O1vdOb07/ V9gBpnfSbDeTMbwIzDQP7jyhHU12MBr7gK9PE9P1cgAvLeSA4aDP90qxeuYIRNhOFFdW Twr5sdHsUxyySmNX7pqgt8JCu3izT2Hf11QGU3FEANDmFmo0Cecd//EPqhdFktj0a1K1 DgUNx3/3i/Q0XdbPGw9O4iASB+PBxGdCCLUJNjQUVHoptxkM6JHtWNtclqYAaWbQQD4l DdpC86+HGLzel4d7otoXbibXkC/UCEiQmZPILXf0dCUG0XBvH38VzO05uaCM/Vm13VID 8DBg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id e12-20020a63db0c000000b00535540cc8ccsi2766531pgg.375.2023.07.09.23.57.41; Sun, 09 Jul 2023 23:57:53 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229864AbjGJGas (ORCPT + 99 others); Mon, 10 Jul 2023 02:30:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36964 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229758AbjGJGap (ORCPT ); Mon, 10 Jul 2023 02:30:45 -0400 Received: from 1wt.eu (ded1.1wt.eu [163.172.96.212]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 10F4E123; Sun, 9 Jul 2023 23:30:43 -0700 (PDT) Received: (from willy@localhost) by mail.home.local (8.17.1/8.17.1/Submit) id 36A6URIR016678; Mon, 10 Jul 2023 08:30:27 +0200 Date: Mon, 10 Jul 2023 08:30:27 +0200 From: Willy Tarreau To: Zhangjin Wu Cc: arnd@arndb.de, linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org, thomas@t-8ch.de Subject: Re: [PATCH v1 4/5] selftests/nolibc: report: extrude the test status line Message-ID: References: <20230709085453.GB9321@1wt.eu> <20230709192652.97668-1-falcon@tinylab.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230709192652.97668-1-falcon@tinylab.org> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Zhangjin, On Mon, Jul 10, 2023 at 03:26:52AM +0800, Zhangjin Wu wrote: > > On Thu, Jul 06, 2023 at 05:11:17PM +0800, Zhangjin Wu wrote: > > > two newlines are added around the test summary line to extrude the test > > > status. > > > > But then we're back to making it annoying to check, having to figure > > if we need to grep -A or grep -B etc. With grep 'status:' we would get > > a synthetic status and the counters together. Why do you think it's > > not convenient ? Or am I the only one considering it useful to just > > run grep "status:" on all output files and figure a global status at > > once ? > > Sorry, Willy, my commit message may mislead you a little. > > The newlines are added around the whole test summary line (with the > status info), not only around the 'status info' ;-) Ah OK, thanks for clarifying this! > It is not for status grep, it is for developers to easily see the whole > summary line at a glance I understand but both work hand-in-hand, as every time you'll perform a slight change, you'll necessarily rerun the whole series on all archs to confirm, which is why I'm particularly annoying about the ability to grep! > And further, if not consider pure-text, the colors may be more helpful, > for example, red for failed/failure, yellow for skipped/warning, green > for passed/success, for example: > > $ echo | awk 'END{printf("138 test(s): \033[32m135\033[0m passed, \033[33m 2\033[0m skipped, \033[31m 1\033[0m failed => status: \033[31mfailure\033[0m\n");}' > 138 test(s): 135 passed, 2 skipped, 1 failed => status: failure > > But as we can see, the color control code is not readable and it may > break the simple "status: failure" grep, we should use something like > "status: .*failure" ;-) Colors may only be used when stdout is a terminal, and still, some might find it annonying (for example some distros use unreadably dark colors that were apparently never tested over a black background, forcing users to highlight the text by selecting it with the mouse to read it). Better not start to play with this IMO, that's not really needed and may be more annoying to some than helpful to most. Thanks, Willy