discuss parameterization of lava-test test cases

Bug #691505 reported by Zygmunt Krynicki
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Obsolete LAVA Test
Invalid
Low
Paul Larson

Bug Description

<davidgiluk> asac/zyga: Is there a mech to pass flags in to tests or a file - e.g. if you have the same test but want to try it with a number of different options and see which one is best, or in my case try something like SPEC with a few different libcs
<asac> patrikryd: what is "mm" ?
 Daviey davidgiluk
 davidgiluk: not sure. but it clearly be supported ;)
<zyga> davidgiluk, yes and no
<asac> davidgiluk: should ;)
<zyga> so, not in abrek from the outside
 but from the inside you can and should make the test code run multiple times with all the combinations you care about
 and store that for analysis
<asac> ok
<zyga> if you want we could build an interface for specifying that externally
<asac> zyga: is there a page with ideas for abrek?
<zyga> asac, I hate pages, let's just make a bug report because wikis don't work for me :/
<asac> we should add: "discuss parameterization of abrek test cases"
<zyga> asac, I don't know also - abrek is pauls work mostly
<asac> zyga: ok. please open a bug report on that
<zyga> k
<asac> just with that title ;)
 and paste the discussion here there initially so we remember

Fathi Boudra (fboudra)
summary: - discuss parameterization of abrek test cases
+ discuss parameterization of lava-test test cases
Changed in lava-test:
importance: Undecided → Low
assignee: nobody → Paul Larson (pwlars)
status: New → Triaged
milestone: none → 2011.10
Revision history for this message
Paul Larson (pwlars) wrote :

Why is this a bug, do we want to discuss this further on a bug before going ahead with the blueprint for this that we already had opened and targeted to this month?

https://blueprints.launchpad.net/lava-test/+spec/linaro-platforms-o-override-test-options

Changed in lava-test:
status: Triaged → Incomplete
Revision history for this message
Fathi Boudra (fboudra) wrote :

It isn't a bug. It was opened initially to keep the discussion somewhere.
We should use the backlog for this kind of reminders.
closing as invalid.

Changed in lava-test:
status: Incomplete → Invalid
Fathi Boudra (fboudra)
Changed in lava-test:
milestone: 2011.10 → none
Revision history for this message
Dr. David Alan Gilbert (davidgil-uk) wrote : Re: [Bug 691505] Re: discuss parameterization of lava-test test cases

On 7 October 2011 04:00, Paul Larson <email address hidden> wrote:
> Why is this a bug, do we want to discuss this further on a bug before
> going ahead with the blueprint for this that we already had opened and
> targeted to this month?
>
> https://blueprints.launchpad.net/lava-test/+spec/linaro-platforms-o
> -override-test-options

(I don't know why it's a bug - but I thought I'd comment on that spec...)

From that spec; the last point is important and may need expanding - i.e.
once you've tagged a result as having been run with a different set of
parameters you have to be very careful when generating averaged/summaries
for sets of results not to include ones run with different parameters.

Dave

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.