All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eugeniu Rosca <roscaeugeniu@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/6] kconfig: re-sync with Linux 4.17-rc4
Date: Sat, 12 May 2018 21:17:05 +0200	[thread overview]
Message-ID: <20180512191705.GA23056@example.com> (raw)
In-Reply-To: <20180512182556.GA2025@x230>


Hello Petr,

On Sat, May 12, 2018 at 08:25:56PM +0200, Petr Vorel wrote:
> Hi Eugeniu,
> 
> > My testing was limited to:
> > - make defconfig all
> > - make ARCH=arm CROSS_COMPILE=aarch64-linux-gnu- r8a7795_ulcb_defconfig all
> > - comparing .config before and after the re-sync
> > - running the newly imported Kconfig unit tests as seen below:
> 
> I tested whole patch-set with the other options:
> make config
> make defconfig
> make menuconfig
> make xconfig
> make gconfig
> make oldconfig
> 
> > Reviewed-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> > Signed-off-by: Eugeniu Rosca <erosca@de.adit-jv.com>
> Tested-by: Petr Vorel <petr.vorel@gmail.com>

Many thanks for testing!

> 
> > $ make testconfig
> 
> > ============================= test session starts =============================
> > scripts/kconfig/tests/auto_submenu/__init__.py::test PASSED             [  7%]
> > scripts/kconfig/tests/choice/__init__.py::test_oldask0 PASSED           [ 14%]
> > scripts/kconfig/tests/choice/__init__.py::test_oldask1 PASSED           [ 21%]
> > scripts/kconfig/tests/choice/__init__.py::test_allyes PASSED            [ 28%]
> > scripts/kconfig/tests/choice/__init__.py::test_allmod PASSED            [ 35%]
> > scripts/kconfig/tests/choice/__init__.py::test_allno PASSED             [ 42%]
> > scripts/kconfig/tests/choice/__init__.py::test_alldef PASSED            [ 50%]
> > scripts/kconfig/tests/choice_value_with_m_dep/__init__.py::test PASSED  [ 57%]
> > scripts/kconfig/tests/err_recursive_inc/__init__.py::test PASSED        [ 64%]
> > scripts/kconfig/tests/inter_choice/__init__.py::test PASSED             [ 71%]
> > scripts/kconfig/tests/new_choice_with_dep/__init__.py::test PASSED      [ 78%]
> > scripts/kconfig/tests/no_write_if_dep_unmet/__init__.py::test PASSED    [ 85%]
> > scripts/kconfig/tests/rand_nested_choice/__init__.py::test PASSED       [ 92%]
> > scripts/kconfig/tests/warn_recursive_dep/__init__.py::test PASSED       [100%]
> > ========================== 14 passed in 0.34 seconds ==========================
> 
> When applied all 6 patches, I got several errors (see bellow).
> I tested in on 2 distros (Debian unstable and openSUSE Tumbleweed).
> The code I applied is here, did I make error when applying patches?
> https://github.com/pevik/u-boot/tree/eugeniu/kconfig.v2

I checked your branch and got some interesting conclusions.
Here is the diff between my and your version of commit ("kconfig:
re-sync with Linux 4.17-rc4"):

$ git diff <eugeniu> <petr>
 scripts/kconfig/tests/auto_submenu/expected_stdout        | 14 +++++++-------
 scripts/kconfig/tests/choice/oldask0_expected_stdout      | 14 +++++++-------
 scripts/kconfig/tests/choice/oldask1_expected_stdout      | 12 ++++++------
 scripts/kconfig/tests/new_choice_with_dep/expected_stdout |  4 ++--
 4 files changed, 22 insertions(+), 22 deletions(-)

Here is the same diff ignoring whitespace:

$ git diff -w <eugeniu> <petr>
 scripts/kconfig/tests/auto_submenu/expected_stdout        | 0
 scripts/kconfig/tests/choice/oldask0_expected_stdout      | 0
 scripts/kconfig/tests/choice/oldask1_expected_stdout      | 0
 scripts/kconfig/tests/new_choice_with_dep/expected_stdout | 0
 4 files changed, 0 insertions(+), 0 deletions(-)

So, it seems like all the trailing white-space from above files
disappeared on your branch, after applying the patches from the
email client (who did this?...).

I didn't expect that trailing white-space to be of any value for the
test results, but it turns out it is! With the whitespace removed, I can
also reproduce the failures of "make testconfig".

I am not familiar with pytest, but, based on what we see here, it looks
like every single character stored in *xpected_stdout files (including
whitespace at the end of lines) matters for the test to pass.

I wonder if Kconfig could avoid printing whitespace in command line
user dialogs. Then maybe those space characters could be removed from
the "*xpected_stdout" files.

Masahiro?

Thanks again!

Best regards,
Eugeniu.

  reply	other threads:[~2018-05-12 19:17 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-12 17:13 [U-Boot] [PATCH v2 1/6] kconfig: re-sync with Linux 4.17-rc4 Eugeniu Rosca
2018-05-12 17:13 ` [U-Boot] [PATCH v2 2/6] board: eets: pdu001: Fix wrong default value in Kconfig Eugeniu Rosca
2018-05-12 17:13 ` [U-Boot] [PATCH v2 3/6] scripts/dtc: Update to upstream version v1.4.5-6-gc1e55a5513e9 Eugeniu Rosca
2018-05-13 22:00   ` Simon Glass
2018-05-16  1:54   ` Masahiro Yamada
2018-05-16 11:51     ` Eugeniu Rosca
2018-05-12 17:13 ` [U-Boot] [PATCH v2 4/6] scripts/dtc: Update to upstream version v1.4.6-9-gaadd0b65c987 Eugeniu Rosca
2018-05-13 22:00   ` Simon Glass
2018-05-13 22:45     ` Eugeniu Rosca
2018-05-14 19:52       ` Simon Glass
2018-05-15 13:46         ` Eugeniu Rosca
2018-05-15 16:05           ` Simon Glass
2018-05-16  1:49   ` Masahiro Yamada
2018-05-12 17:13 ` [U-Boot] [PATCH v2 5/6] scripts/dtc: Re-sync with Linux 4.17-rc4 Eugeniu Rosca
2018-05-15 14:06   ` Eugeniu Rosca
2018-05-15 16:05     ` Simon Glass
2018-05-16  1:48     ` Masahiro Yamada
2018-05-12 17:13 ` [U-Boot] [PATCH v2 6/6] sandbox: dts: test: Fix wrong aliases property names Eugeniu Rosca
2018-05-13 22:00   ` Simon Glass
2018-05-12 18:25 ` [U-Boot] [PATCH v2 1/6] kconfig: re-sync with Linux 4.17-rc4 Petr Vorel
2018-05-12 19:17   ` Eugeniu Rosca [this message]
2018-05-12 19:31     ` Petr Vorel
2018-05-12 21:17       ` Eugeniu Rosca
2018-05-13 13:52     ` Masahiro Yamada
2018-05-13 20:43       ` Eugeniu Rosca
2018-05-14 19:35       ` Petr Vorel
2018-05-16  1:59 ` Masahiro Yamada
2018-05-16  5:09   ` Petr Vorel
2018-05-16  8:24     ` Eugeniu Rosca
2018-05-16 11:27       ` Eugeniu Rosca
2018-05-19 12:21         ` Eugeniu Rosca

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180512191705.GA23056@example.com \
    --to=roscaeugeniu@gmail.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.