Yea, I think that's the right way to do it, since the regression updates can
get very bulky and it would be hard to pick the actual code changes out of
the noise.
Steve
On Thu, Apr 9, 2009 at 9:36 PM, Korey Sewell wrote:
> Okay thanks, things are starting to look better.
>
> Also, when we make
Okay thanks, things are starting to look better.
Also, when we make changes that will affect regressions, do we typically
want to commit the change and the regression-updates in different
changesets?
On Thu, Apr 9, 2009 at 11:40 PM, Steve Reinhardt wrote:
> The right command to update the refer
The right command to update the reference outputs would be:
scons update_ref=y
build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/inorder.timing
Let me know if it doesn't work after you do that.
Also note that scons won't rerun the test if none of its dependencies (e.g.,
the m5 binary) has cha
OK, so I still have a few more questions on getting the regressions to work
me:
1. How do you enforce a particular test gets run?
===
--> M5 seems to recognize my regression but fails without actually running
the test. All I get is:
"scons: Building targets ...
* build/ALPHA_SE/tests/fast/quick
n/mJust took a little digging
If anyone wants to do this, you need to look in the m5/tests/SConscript file
and add your CPU-model to the script toward the bottom around line 265...
On Thu, Apr 9, 2009 at 12:54 PM, Korey Sewell wrote:
> If I would like to add a new regression test for th
If I would like to add a new regression test for the InOrder model what are
the steps? The WIKI entry I wrote is painfully outdated.
So far, I've collected the stats from m5.fast & placed them in the correct
folder (quick/hello/ref/inorder-timing).
What do I need to to get M5 to recognize this re
