From: Alexandru Palalau <alexandrux.palalau@linux.intel.com>
To: Corneliu Stoicescu <corneliux.stoicescu@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] selftest/bbtests.py: Fixed regex and added bitbake output to test_warnings_errors
Date: Wed, 26 Mar 2014 18:33:52 +0200 [thread overview]
Message-ID: <53330170.1070906@linux.intel.com> (raw)
In-Reply-To: <1395852491-32086-1-git-send-email-corneliux.stoicescu@intel.com>
Hi,
On 3/26/2014 6:48 PM, Corneliu Stoicescu wrote:
> The test failed when more than 1 error or 1 warning is present.
> Also pasting the bitbake output when the test fails.
>
> Signed-off-by: Corneliu Stoicescu <corneliux.stoicescu@intel.com>
> ---
> meta/lib/oeqa/selftest/bbtests.py | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/meta/lib/oeqa/selftest/bbtests.py b/meta/lib/oeqa/selftest/bbtests.py
> index ee1f82a..d7dc127 100644
> --- a/meta/lib/oeqa/selftest/bbtests.py
> +++ b/meta/lib/oeqa/selftest/bbtests.py
> @@ -47,10 +47,10 @@ class BitbakeTests(oeSelfTest):
>
> def test_warnings_errors(self):
> result = bitbake('-b asdf', ignore_status=True)
> - find_warnings = re.search("Summary: There was [1-9][0-9]* WARNING message shown.", result.output)
> - find_errors = re.search("Summary: There was [1-9][0-9]* ERROR message shown.", result.output)
> - self.assertTrue(find_warnings)
> - self.assertTrue(find_errors)
> + find_warnings = re.search("Summary: There wa.{1,2}? [1-9][0-9]* WARNING messages* shown", result.output)
> + find_errors = re.search("Summary: There wa.{1,2}? [1-9][0-9]* ERROR messages* shown", result.output)
If more than one warning messages are encountered, the actual output is
"Summary: There were 2 WARNING messages shown." and the search above
doesn't match.
> + self.assertTrue(find_warnings, msg="Did not find the mumber of warnings at the end of the build:\n" + result.output)
> + self.assertTrue(find_errors, msg="Did not find the mumber of errors at the end of the build:\n" + result.output)
>
> def test_invalid_patch(self):
> self.write_recipeinc('man', 'SRC_URI += "file://man-1.5h1-make.patch"')
>
--
Alexandru Palalau
prev parent reply other threads:[~2014-03-26 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 16:48 [PATCH] selftest/bbtests.py: Fixed regex and added bitbake output to test_warnings_errors Corneliu Stoicescu
2014-03-26 16:33 ` Alexandru Palalau [this message]
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=53330170.1070906@linux.intel.com \
--to=alexandrux.palalau@linux.intel.com \
--cc=corneliux.stoicescu@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox