All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Liu, Wenlong" <liuwl.fnst@cn.fujitsu.com>
To: "fuego@lists.linuxfoundation.org" <fuego@lists.linuxfoundation.org>
Subject: [Fuego] How to return test_processing result if multiple "log_compare" exist
Date: Mon, 4 Dec 2017 06:17:34 +0000	[thread overview]
Message-ID: <F40213214988A94A9DDBFC5F7146FC5E012C65B1FE@G08CNEXMBPEKD01.g08.fujitsu.local> (raw)

Hi

I've been doing the OpenSSL test recently and find some interesting log as below.
...
##### doing fuego phase: post_test ########
Teardown board link
##### doing fuego phase: processing ########
ERROR: log_compare: pattern 'passed|ok' found 169 times (expected greater or equal than 176)
log_compare: pattern 'skip' found 0 times (expected less or equal than 86)
running python with PATH=/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
WARNING: missing or faulty criteria.json file (/fuego-core/engine/tests/Functional.OpenSSL/criteria.json), looking for reference.log
WARNING: No reference.log found. Using default criteria.
No reference.json available
ref={'test_sets': [{'test_cases': [{'status': 'PASS', 'name': 'OpenSSL'}], 'name': 'default'}]}
Applying criterion {'max_fail': 0, 'tguid': 'default'}
Applying criterion {'max_fail': 0, 'tguid': 'Functional.OpenSSL'}
Writing run data to /fuego-rw/logs/Functional.OpenSSL/DB410c-dab2.default.7.7/run.json
...

So, if multiple "log_compare" exist, how should we return the final log processing result?

Best regards
Liu 




             reply	other threads:[~2017-12-04  6:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04  6:17 Liu, Wenlong [this message]
2017-12-04  6:24 ` [Fuego] How to return test_processing result if multiple "log_compare" exist Daniel Sangorrin
2017-12-04  6:31   ` Liu, Wenlong
2017-12-04  9:08   ` Bird, Timothy

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=F40213214988A94A9DDBFC5F7146FC5E012C65B1FE@G08CNEXMBPEKD01.g08.fujitsu.local \
    --to=liuwl.fnst@cn.fujitsu.com \
    --cc=fuego@lists.linuxfoundation.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 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.