From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg1-f195.google.com (mail-pg1-f195.google.com [209.85.215.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 5F4E02129F0EC for ; Wed, 26 Jun 2019 15:03:53 -0700 (PDT) Received: by mail-pg1-f195.google.com with SMTP id v9so46pgr.13 for ; Wed, 26 Jun 2019 15:03:53 -0700 (PDT) Date: Wed, 26 Jun 2019 22:03:50 +0000 From: Luis Chamberlain Subject: Re: [PATCH v5 13/18] kunit: tool: add Python wrappers for running KUnit tests Message-ID: <20190626220350.GA19023@42.do-not-panic.com> References: <20190617082613.109131-1-brendanhiggins@google.com> <20190617082613.109131-14-brendanhiggins@google.com> <20190626000150.GT19023@42.do-not-panic.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Brendan Higgins Cc: Petr Mladek , "open list:DOCUMENTATION" , Peter Zijlstra , Amir Goldstein , dri-devel , Sasha Levin , Masahiro Yamada , Michael Ellerman , "open list:KERNEL SELFTEST FRAMEWORK" , shuah , Rob Herring , linux-nvdimm , Frank Rowand , Knut Omang , Kieran Bingham , Felix Guo , wfg@linux.intel.com, Joel Stanley , David Rientjes , Jeff Dike , Dan Carpenter , devicetree , linux-kbuild , "Bird, Timothy , linux-um@lists.infradead.org, Steven Rostedt" , Julia Lawall , Josh Poimboeuf , kunit-dev@googlegroups.com, Theodore Ts'o , Richard Weinberger , Stephen Boyd , Greg KH , Randy Dunlap , Linux Kernel Mailing List , Daniel Vetter , Kees Cook , linux-fsdevel@vger.kernel.org, Kevin Hilman List-ID: On Wed, Jun 26, 2019 at 01:02:55AM -0700, Brendan Higgins wrote: > On Tue, Jun 25, 2019 at 5:01 PM Luis Chamberlain wrote: > > > > On Mon, Jun 17, 2019 at 01:26:08AM -0700, Brendan Higgins wrote: > > > create mode 100644 tools/testing/kunit/test_data/test_is_test_passed-all_passed.log > > > create mode 100644 tools/testing/kunit/test_data/test_is_test_passed-crash.log > > > create mode 100644 tools/testing/kunit/test_data/test_is_test_passed-failure.log > > > create mode 100644 tools/testing/kunit/test_data/test_is_test_passed-no_tests_run.log > > > create mode 100644 tools/testing/kunit/test_data/test_output_isolated_correctly.log > > > create mode 100644 tools/testing/kunit/test_data/test_read_from_file.kconfig > > > > Why are these being added upstream? The commit log does not explain > > this. > > Oh sorry, those are for testing purposes. I thought that was clear > from being in the test_data directory. I will reference it in the > commit log in the next revision. Still, I don't get it. They seem to be results from a prior run. Why do we need them for testing purposes? Luis _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm