* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/o3-timing passed.
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic passed.
*
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/o3-timing passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic passed.
*
* build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/o3-timing passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing passed.
*
* build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/o3-timing passed.
* build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing
passed.
*
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-atomic
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby
passed.
*
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-timing-mp
passed.
* build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing
passed.
*
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-timing-mp
passed.
* build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing
passed.
*
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-timing-mp
passed.
* build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing
passed.
*
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/o3-timing passed.
*
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing passed.
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-atomic
passed.
* build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/simple-atomic passed.
*
* build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp
passed.
*
* build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp
passed.
*
Seems that I some how managed to not update bzip2/o3/Alpha. I'm running it now
and will update when I'm done.
Ali
On May 16, 2010, at 6:58 AM, Cron Daemon wrote:
* build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby
passed.
*
* build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp
passed.
*
* build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp
passed.
*
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp
passed.
*
I think these all failed because of some problem with poolfs and
/dist. It seems that /dist is available right now, but I can't seem
to ssh into poolfs. It appears that the pool uses YP for passwords
and that the password database was updated a couple of days ago.
curiously, there used to be an
* build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp
FAILED!
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed.
*
It seems that /dist was out of commission.
Nate
On Sun, Apr 11, 2010 at 4:26 AM, Cron Daemon r...@zizzer.eecs.umich.edu wrote:
* build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp
yea, I just saw that. what's the cause of that happening somewhat randomly?
Should we just re-run scratch all?
On Sun, Apr 11, 2010 at 11:16 AM, nathan binkert n...@binkert.org wrote:
It seems that /dist was out of commission.
Nate
On Sun, Apr 11, 2010 at 4:26 AM, Cron Daemon
yea, I just saw that. what's the cause of that happening somewhat randomly?
No idea. Network blip?
Should we just re-run scratch all?
I'm doing that now.
Nate
___
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
I *should* have the fix for this posted tomorrow. I'm re-running all
the regressions now.
-Korey
On Tue, Apr 6, 2010 at 3:34 AM, Gabe Black gbl...@eecs.umich.edu wrote:
Without looking into it too deeply what you're saying seems plausible.
The best place for this sort of initialization in SE
Without looking into it too deeply what you're saying seems plausible.
The best place for this sort of initialization in SE mode is, in my
opinion, in the process initialization code. Conceptually it's sort of
like the OS constructing the process context. The situation sounds
similar to SPARC
Following up on this, it seems that Brad is correct about where the
uninitialized values originate. Specifically, this code snippet in
src/arch/alpha/tlb.cc is the culprit:
mode_type mode =
(mode_type)DTB_CM_CM(tc-readMiscRegNoEffect(IPR_DTB_CM));
That uninitialized value
* build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed.
*
));
From: m5-dev-boun...@m5sim.org [mailto:m5-dev-boun...@m5sim.org] On Behalf
Of Korey Sewell
Sent: Tuesday, March 30, 2010 7:41 PM
To: M5 Developer List
Subject: Re: [m5-dev] Cron m5t...@zizzer /z/m5/regression/do-regression
--scratch all
I ran this through valgrind and it looks like
is flagged
+//
mode_type mode =
(mode_type)DTB_CM_CM(tc-readMiscRegNoEffect(IPR_DTB_CM));
From: m5-dev-boun...@m5sim.org [mailto:m5-dev-boun...@m5sim.org] On Behalf Of
Korey Sewell
Sent: Tuesday, March 30, 2010 7:41 PM
To: M5 Developer List
Subject: Re: [m5-dev] Cron m5t...@zizzer /z
Those are good questions to answer because they point either to
non-determinism in the CPU or host state leaking into the simulation.
Another thing people suggested way back when when I was trying to fix
something similar was to use netcat with tracediff to compare execution
across two known
I ran this through valgrind and it looks like in ALPHA_SE there may be some
uninitialized values that weren't affecting the simulation output but
affecting timing somewhat (specifically with the TLB translations).
In the next go round of this, I should be able to track that down and verify
what
* build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing passed.
* build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/simple-atomic passed.
*
So it doesn't get missed in the pile, this one failed.
* build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/inorder-timing
FAILED!
Cron Daemon wrote:
* build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby
passed.
*
Thanks for highlighting that. Looks like it's just a minor stats difference:
= Statistics differences =
Maximum error magnitude: +0.028348%
Reference New Value Abs Diff Pct Chg
Key statistics:
host_inst_rate 49066 74587
haven't we been having problems with inorder-timing for a while?
On Mon, Mar 29, 2010 at 12:19 AM, Steve Reinhardt ste...@gmail.com wrote:
Thanks for highlighting that. Looks like it's just a minor stats difference:
= Statistics differences =
Maximum error magnitude: +0.028348%
I've been looking into this intermittently throughout the day (slow
zizzer!). I'm hesitant to just update the reference stats though since
again, the stats are different on my machine than on zizzer. But what
really makes me hesitant is that although the execution is correct, we're
seeing
haven't we been having problems with inorder-timing for a while?
I didnt notice that the test was failing for awhile since the tests only run
once-a-month on the weekend, and as Gabe noted, whether something fails or
not gets lost in the avalanche of messages there.
So yea, they've been hitting
We're still getting those 'invalid IPR' errors...
On Sun, Mar 21, 2010 at 3:46 AM, Cron Daemon r...@zizzer.eecs.umich.edu wrote:
* build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/inorder-timing
FAILED!
* build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/inorder-timing
Steve,
where are you finding the 'Invalid IPR' message?
This bug is kind of elusive since everything is working fine on my local
machine, but trying to run off zizzer is painfully slow when I ssh in. I was
speculating that this might be a case of me different versions of gcc or
maybe something
Lookat the simerr files in these directories on zizzer:
/z/m5/regression/zizzer/m5/build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/inorder-timing
/z/m5/regression/zizzer/m5/build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/inorder-timing
Steve
On Mon, Mar 22, 2010 at 9:32 PM, Korey Sewell
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing passed.
*
I've thought about these sorts of hard to reproduce failures before, and
thought maybe we should have the regressions periodically dump stats?
That way we could tell roughly when something diverged. I don't know if
that would actually tell us much, but it would tell us more and sounds
to my naive
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing passed.
* build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby
passed.
*
The two failures this time are both print the error message panic:
Tried to read from invalid ipr N where N is 296 for twolf and 307 for
vortex.
I was able to pull all the new changesets and run the regressions
successfully just now so I'm a little perplexed to what's going on here.
Maybe I
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed.
*
The pass/fail groupings are probably a good idea.
Not sure why those inorder tests are failing, but I should be able to take a
look tomorrow. I haven't been paying too close of attention to the
changesets so I'm not sure off-hand what could be the culprit.
On Sun, Mar 7, 2010 at 8:27 PM, Gabe
It's in the plans. Steve, any opinions on my last email about tests?
On Sunday, March 7, 2010, Korey Sewell ksew...@umich.edu wrote:
The pass/fail groupings are probably a good idea.
Not sure why those inorder tests are failing, but I should be able to take a
look tomorrow. I haven't been
Yea, I'd been thinking too that it would be nice to have an easier way
of seeing if any tests failed.
The two failures this time are both print the error message panic:
Tried to read from invalid ipr N where N is 296 for twolf and 307 for
vortex.
Thanks for the reminder about your test email,
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp
passed.
* build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/inorder-timing FAILED!
* build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/simple-atomic passed.
*
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing
passed.
*
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic passed.
*
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed.
*
, January 31, 2010 4:40 PM
To: M5 Developer List
Subject: Re: [m5-dev] Cron m5t...@zizzer
/z/m5/regression/do-regression--scratch all
OK, I believe it's a problem Brad was already worried about... see this:
diff -r a162a2b0b1f8 -r 5bd33f7c26ea tests/SConscript
--- a/tests/SConscript Fri Jan
: [m5-dev] Cron m5t...@zizzer
/z/m5/regression/do-regression--scratch all
OK, I believe it's a problem Brad was already worried about... see this:
diff -r a162a2b0b1f8 -r 5bd33f7c26ea tests/SConscript
--- a/tests/SConscript Fri Jan 29 20:29:34 2010 -0800
+++ b/tests/SConscript Fri Jan 29 20
-Original Message-
From: m5-dev-boun...@m5sim.org [mailto:m5-dev-boun...@m5sim.org] On Behalf Of
Steve Reinhardt
Sent: Monday, February 01, 2010 8:55 AM
To: M5 Developer List
Subject: Re: [m5-dev] Cron
m5t...@zizzer/z/m5/regression/do-regression--scratch all
Yes, it would... that would
-
From: m5-dev-boun...@m5sim.org [mailto:m5-dev-boun...@m5sim.org] On Behalf Of
Steve Reinhardt
Sent: Monday, February 01, 2010 8:55 AM
To: M5 Developer List
Subject: Re: [m5-dev] Cron
m5t...@zizzer/z/m5/regression/do-regression--scratch all
Yes, it would... that would be great. I
*
build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MOESI_CMP_directory
passed.
*
build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MOESI_CMP_directory
passed.
*
, 2010 2:21 AM
To: M5 Developer List
Subject: Re: [m5-dev] Cron m5t...@zizzer
/z/m5/regression/do-regression --scratch all
If --scratch means from scratch like I'm assuming it does, something
doesn't seem to be working right.
Gabe
Cron Daemon wrote:
*
build/ALPHA_SE/tests/fast/quick
OK, I believe it's a problem Brad was already worried about... see this:
diff -r a162a2b0b1f8 -r 5bd33f7c26ea tests/SConscript
--- a/tests/SConscript Fri Jan 29 20:29:34 2010 -0800
+++ b/tests/SConscript Fri Jan 29 20:29:40 2010 -0800
@@ -264,11 +264,23 @@
else:
configs +=
unless explicitly specified at the
command line.
Brad
-Original Message-
From: m5-dev-boun...@m5sim.org [mailto:m5-dev-boun...@m5sim.org] On Behalf Of
Steve Reinhardt
Sent: Sunday, January 31, 2010 4:40 PM
To: M5 Developer List
Subject: Re: [m5-dev] Cron m5t...@zizzer
/z/m5/regression/do
...@m5sim.org] On Behalf Of
Steve Reinhardt
Sent: Sunday, January 31, 2010 4:40 PM
To: M5 Developer List
Subject: Re: [m5-dev] Cron m5t...@zizzer
/z/m5/regression/do-regression--scratch all
OK, I believe it's a problem Brad was already worried about... see this:
diff -r a162a2b0b1f8 -r
* build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/simple-atomic passed.
* build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/simple-atomic passed.
* build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/simple-timing passed.
*
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-timing-mp
passed.
* build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/simple-atomic passed.
*
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp
passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-timing-mp
passed.
*
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp
passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-timing-mp
passed.
*
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-timing-mp
passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp
passed.
*
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-timing-mp
passed.
*
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp
passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-timing-mp
passed.
*
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-timing-mp
passed.
* build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/simple-atomic passed.
*
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/o3-timing passed.
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic passed.
*
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing
passed.
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-atomic
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing passed.
*
* build/X86_SE/tests/fast/long/70.twolf/x86/linux/simple-timing FAILED!
* build/X86_SE/tests/fast/long/00.gzip/x86/linux/simple-timing FAILED!
* build/X86_SE/tests/fast/long/10.mcf/x86/linux/simple-timing FAILED!
* build/X86_SE/tests/fast/long/20.parser/x86/linux/simple-timing
I'm looking at it. I think there were three x86 changes since these last
passed, X86: Hook up time syscall on X86, X86: Enable x86_64 vsyscall
support, and X86: Fix problem with movhps instruction. I figure out
which one, and look at the stats changes.
Gabe
nathan binkert wrote:
*
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic-ruby
passed.
* build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/simple-timing passed.
* build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/simple-timing passed.
*
with this small fix.
I'll check it in.
Brad
-Original Message-
From: m5-dev-boun...@m5sim.org [mailto:m5-dev-boun...@m5sim.org] On
Behalf Of nathan binkert
Sent: Sunday, October 18, 2009 8:30 AM
To: M5 Developer List
Subject: Re: [m5-dev] Cron m5t...@zizzer
/z/m5/regression/do-regression
...@m5sim.org] On
Behalf Of Polina Dudnik
Sent: Sunday, October 18, 2009 11:10 AM
To: M5 Developer List
Subject: Re: [m5-dev] Cron
m5t...@zizzer/z/m5/regression/do-regression--scratch all
Thanks Brad,
Nate, let's see if it works after this check-in, and I will fix it if it
doesn't.
Polina
On Sun
-boun...@m5sim.org [mailto:m5-dev-boun...@m5sim.org] On
Behalf Of nathan binkert
Sent: Sunday, October 18, 2009 8:30 AM
To: M5 Developer List
Subject: Re: [m5-dev] Cron m5t...@zizzer
/z/m5/regression/do-regression--scratch all
Polina or Derek. Can one of you *please* take a look at what happened
...@m5sim.org [mailto:m5-dev-boun...@m5sim.org] On
Behalf
Of Polina Dudnik
Sent: Sunday, October 18, 2009 11:10 AM
To: M5 Developer List
Subject: Re: [m5-dev] Cron
m5t...@zizzer/z/m5/regression/do-regression--scratch all
Thanks Brad,
Nate, let's see if it works after this check
...@m5sim.org] On
Behalf
Of Polina Dudnik
Sent: Sunday, October 18, 2009 11:10 AM
To: M5 Developer List
Subject: Re: [m5-dev] Cron
m5t...@zizzer/z/m5/regression/do-regression--scratch all
Thanks Brad,
Nate, let's see if it works after this check-in, and I will fix it if it
doesn't
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic-ruby
passed.
* build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/simple-timing passed.
* build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/simple-timing passed.
*
OK, it looks like changeset 6650 which fixed command line arguments
(argc/argv) in MIPS switches up the initiliazation path of the code which in
turn creates slightly different stats in instruction count and other things.
I think it's OK to update the regression references.
OK to update them all
OK, it looks like changeset 6650 which fixed command line arguments
(argc/argv) in MIPS switches up the initiliazation path of the code which in
turn creates slightly different stats in instruction count and other things.
I think it's OK to update the regression references.
OK to update them
Yup, I used 'hg bisect' to track down the changeset that made the test
start failing and the one you have that's currently at the tip is it.
Steve
On Mon, Sep 21, 2009 at 8:51 AM, Korey Sewell ksew...@umich.edu wrote:
I did edit some MIPS stuff to allow for command line arguments...Didnt think
I did a manual run just to kick things off, and it looks like there
are some small stats changes in MIPS_SE as well as the ruby problems.
Korey, did you do any commits that would change stats in MIPS?
Steve
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/o3-timing passed.
*
Ruby must be failing due to stats changes in MOESI since the recent patch.
On Sun, Sep 20, 2009 at 5:17 PM, Steve Reinhardt ste...@gmail.com wrote:
I did a manual run just to kick things off, and it looks like there
are some small stats changes in MIPS_SE as well as the ruby problems.
Korey,
scons: *** [build/ALPHA_SE/params/params_wrap.fo] Error 1
scons: *** [build/ALPHA_SE/python/swig/debug_wrap.fo] Error 1
scons: *** [build/ALPHA_SE/python/swig/event_wrap.fo] Error 1
scons: *** [build/ALPHA_SE/python/swig/core_wrap.fo] Error 1
scons: *** [build/ALPHA_SE/python/swig/random_wrap.fo]
scons: *** [build/ALPHA_SE/params/params_wrap.fo] Error 1
scons: *** [build/ALPHA_SE/python/swig/debug_wrap.fo] Error 1
scons: *** [build/ALPHA_SE/python/swig/event_wrap.fo] Error 1
scons: *** [build/ALPHA_SE/python/swig/core_wrap.fo] Error 1
scons: *** [build/ALPHA_SE/python/swig/random_wrap.fo]
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby
passed.
*
See /z/m5/regression/regress-2009-08-16-03:00:01 for details.
___
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing passed.
*
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic-ruby
passed.
*
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-timing-mp
passed.
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby
passed.
*
* do-regression: qsub timed out, retrying locally
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-atomic
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing passed.
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-atomic
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic-ruby
passed.
*
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/o3-timing passed.
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-atomic
passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-timing-mp
passed.
*
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/o3-timing passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed.
*
I know there's been a few minor changes recently so maybe one slightly
tweaked the stats. But as you said Nate, the changes are extremely
minimal and dont affect anything significant (IMO) like sim_insts so
it's probably OK just to update the stats.
On Sun, Jun 7, 2009 at 4:22 PM, nathan
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/inorder-timing
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing
passed.
*
scons: *** [build/ALPHA_SE/encumbered/eio/eio.fo] Error 1
scons: *** [build/ALPHA_SE/encumbered/eio/exolex.fo] Error 1
scons: *** [build/ALPHA_SE/encumbered/eio/libexo.fo] Error 1
*
build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-atomic-dual
passed.
*
* do-regression: qsub timed out, retrying locally
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic
* do-regression: qsub timed out, retrying locally
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing
See /z/m5/regression/regress-2009-04-26-03:00:01 for details.
___
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
1 - 100 of 124 matches
Mail list logo
