From: "Brüns, Stefan" <Stefan.Bruens@rwth-aachen.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] test/py: Fix exception, do not parametrize with empty set
Date: Mon, 17 Oct 2016 19:18:15 +0000 [thread overview]
Message-ID: <1546966.FbbolYLUvO@sbruens-linux> (raw)
In-Reply-To: <1b7d496b-5cf1-b122-44e8-f20b127053ca@wwwdotorg.org>
On Montag, 17. Oktober 2016 12:11:26 CEST Stephen Warren wrote:
> On 10/16/2016 12:17 PM, Stefan Br?ns wrote:
> > If the parameter set is empty, the pytest setup fails:
> > ---
> >
> > call: <CallInfo when='setup' exception: got empty parameter set
> > ['env__dfu_config'], function test_dfu at [...]test_dfu.py:107>
> >
> > ---
> >
> > This aborts pytest_runtest_makereport and later leads to an exception
> > during the report generation, as the call to log.start_section(...)
> > is never executed:
> > ---
> >
> > Exception: Block nesting mismatch:
> > "test_dfu[env__usb_dev_port0-env__dfu_config0]" ""
> >
> > ---
>
> How do you trigger this? I believe my test setup has many cases where
> the test you added would trigger, but without the issues you mention,
> but I'm not 100% sure since I don't know for sure what is causing this
> issue.
>
> Which pytest version do you have? I appear to have 2.5.1 (on Ubuntu Trusty)
1. You need "dfu_configs" to be empty
2. Maybe its pytest version dependent, IIRC I have 3.0.2
The first error above can be seen when running pytest with "--debug", it is
written to IIRC pytestdebug.log
Kind regards,
Stefan
next prev parent reply other threads:[~2016-10-17 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 18:17 [U-Boot] [PATCH] test/py: Fix exception, do not parametrize with empty set Stefan Brüns
2016-10-17 18:11 ` Stephen Warren
2016-10-17 19:18 ` Brüns, Stefan [this message]
2016-10-17 22:01 ` Stephen Warren
2016-10-17 22:21 ` Stephen Warren
2016-10-17 22:59 ` Stephen Warren
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=1546966.FbbolYLUvO@sbruens-linux \
--to=stefan.bruens@rwth-aachen.de \
--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.