From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752532AbbCZQ3g (ORCPT ); Thu, 26 Mar 2015 12:29:36 -0400 Received: from mail-ie0-f178.google.com ([209.85.223.178]:33960 "EHLO mail-ie0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751997AbbCZQ3e (ORCPT ); Thu, 26 Mar 2015 12:29:34 -0400 MIME-Version: 1.0 In-Reply-To: <5513EE03.1020507@redhat.com> References: <1427327073-19011-1-git-send-email-john.stultz@linaro.org> <5513EE03.1020507@redhat.com> Date: Thu, 26 Mar 2015 09:29:33 -0700 Message-ID: Subject: Re: [PATCH 1/2] kselftests: timers: Make set-timer-lat fail more gracefully for !CAP_WAKE_ALARM From: John Stultz To: Prarit Bhargava Cc: lkml , Shuah Khan , Thomas Gleixner , Richard Cochran , Tyler Baker Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 26, 2015 at 4:31 AM, Prarit Bhargava wrote: > On 03/25/2015 07:44 PM, John Stultz wrote: >> + printf("%-22s %s missing CAP_WAKE_ALARM? : [UNSUPPORTED]\n", >> + clockstring(clock_id), >> + flags ? "ABSTIME":"RELTIME"); > > Something to think about: Do you want to write these tests to be more human > readable or machine readable? In theory with awk I guess it doesn't matter too > much, however, it is something that we should think about moving forward. So this came up at ELC in a few discussions. Right now there isn't any established output format, but there's some nice and simple infrastructure for counting pass/fails. However, in talking to Tyler, I know he has started looking at how to integrate the selftests into our automated infrastructure and was interested in how we improve the output parsing for reports. So there is interest in improving this, and I'm open to whatever changes might be needed (adding extra arguments to the test to put them into "easy parse" mode or whatever). thanks -john