All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
To: fuego@lists.linuxfoundation.org
Subject: [Fuego] A few fixes and a bug report
Date: Fri,  5 Oct 2018 10:30:52 +0900	[thread overview]
Message-ID: <1538703055-9252-1-git-send-email-daniel.sangorrin@toshiba.co.jp> (raw)

Hi Tim,

I did a few modifications and found a regression.

[PATCH 1/3] dynvars: add support for simple variable assignments
  -> this implements your proposal about using simple variable
     assignments for dynamic variables

[PATCH 2/3] run-test: use makedirs instead of mkdir
  -> I found cases where the "builds" folder had not been created
     so use os.makedirs instead to get an "mkdir -p" like functionality.

[PATCH 3/3] ovgen: remove test spec strip and generation code
  -> This removes some legacy code. If you want to keep the legacy code
     I am fine, you could leave a "this is deprecated" kind of message

About the regression. I already mentioned it once, but it seems that there
is a regression or at least some problem with the criteria handling code.
Benchmark.Dhrystone fails with these messages:
   Error: criteria missing reference value - returning SKIP
   ERROR: results did not satisfy the threshold

Thanks,
Daniel Sangorrin


             reply	other threads:[~2018-10-05  1:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-05  1:30 Daniel Sangorrin [this message]
2018-10-05  1:30 ` [Fuego] [PATCH 1/3] dynvars: add support for simple variable assignments Daniel Sangorrin
2018-10-06  1:17   ` Tim.Bird
2018-10-05  1:30 ` [Fuego] [PATCH 2/3] run-test: use makedirs instead of mkdir Daniel Sangorrin
2018-10-06  1:16   ` Tim.Bird
2018-10-05  1:30 ` [Fuego] [PATCH 3/3] ovgen: remove test spec strip and generation code Daniel Sangorrin
2018-10-06  1:15   ` Tim.Bird
2018-10-05  1:39 ` [Fuego] A few fixes and a bug report Tim.Bird

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=1538703055-9252-1-git-send-email-daniel.sangorrin@toshiba.co.jp \
    --to=daniel.sangorrin@toshiba.co.jp \
    --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.