Thanks Nate, I didn't know about it. I will read about it.

On Mon, Oct 19, 2009 at 5:13 PM, nathan binkert <n...@binkert.org> wrote:

> Can I recommend the mercurial bisect extension?  It's totally designed
> for doing this exact thing.
>
>  Nate
>
> On Mon, Oct 19, 2009 at 3:10 PM, Polina Dudnik <pdud...@gmail.com> wrote:
> > OK, I will see if I checked in anything after MOESI patch on september
> 21st
> > and see if it breaks the tester.
> >
> > Polina
> >
> > On Mon, Oct 19, 2009 at 5:08 PM, Beckmann, Brad <brad.beckm...@amd.com>
> > wrote:
> >>
> >> No, I'm not sure Polina's checkin on 8/28 changed the stats.  I should
> >> have been more clear.  When I grep for "memtest-ruby passed" the last
> >> successful test I see is on 8/28.  However, for a few weeks afterwards
> there
> >> appeared to be many problems with the regression tester.  These
> regression
> >> tester problems existed until 9/21.  On 9/21, many tests succeeded but
> >> memtest-ruby still failed.
> >>
> >> I suppose we can conjecture that the checkin in question occurred
> sometime
> >> between 8/28 - 9/21.
> >>
> >> Brad
> >>
> >>
> >> -----Original Message-----
> >> From: m5-dev-boun...@m5sim.org [mailto:m5-dev-boun...@m5sim.org] On
> Behalf
> >> Of Derek Hower
> >> Sent: Monday, October 19, 2009 7:42 AM
> >> To: M5 Developer List
> >> Subject: Re: [m5-dev]
> >> Cron<m5t...@zizzer>/z/m5/regression/do-regression--scratch all
> >>
> >> So I haven't tried to reapply the Polina's changesets on 8/28, but
> >> just looking them over, I agree that they shouldn't be affecting the
> >> memtest stats.  One deals with DMA requests in MI, one with atomic
> >> requests for all protocols, and one with MOESI.  Since memtest uses MI
> >> and doesn't issue DMA or atomic requests, the stats should be
> >> unaffected.  Are we sure that it was one of those changes that altered
> >> the stats?
> >>
> >> -Derek
> >>
> >> On Sun, Oct 18, 2009 at 7:18 PM, Polina Dudnik <pdud...@gmail.com>
> wrote:
> >> > Nate,
> >> >
> >> > So my understanding is that mem-test is on MI_example. I pulled the
> >> > repository before my changes on August 28 and ran mem-test for MI,
> then
> >> > applied changes one by one and I can't see the test fail. I see it
> fail
> >> > for
> >> > MOESI, but that's because the stats are different for MOESI and MI.
> >> >
> >> > I don't think I changed the stats, and even if I did, the test then
> >> > would
> >> > have failed for when I haven't yet applied my changes.
> >> >
> >> > So,
> >> >
> >> > I can't say I know why the test fails, I don't.
> >> >
> >> > Polina
> >> >
> >> > On Sun, Oct 18, 2009 at 2:41 PM, Polina Dudnik <pdud...@gmail.com>
> >> > wrote:
> >> >>
> >> >> Right,
> >> >>
> >> >> I'm not sure if it does make sense, but I will check it.
> >> >>
> >> >> Polina
> >> >>
> >> >> On Sun, Oct 18, 2009 at 2:22 PM, nathan binkert <n...@binkert.org>
> >> >> wrote:
> >> >>>
> >> >>> I believe that the issue was that the checkin "wasn't supposed to
> >> >>> change stats", yet it did.  It's ok for stat values to change, but
> we
> >> >>> only want them to change when we actually change something that
> should
> >> >>> affect them.  She was going to verify that it made sense.
> >> >>>
> >> >>>  Nate
> >> >>>
> >> >>> On Sun, Oct 18, 2009 at 12:09 PM, Beckmann, Brad
> >> >>> <brad.beckm...@amd.com>
> >> >>> wrote:
> >> >>> > Actually, it looks like a reference miscorrelation error (see
> >> >>> > below).
> >> >>> > It
> >> >>> > appears this problem has existed since Polina's checkin on 8/28.
> >> >>> > The
> >> >>> > difference is rather minor, do we want to just go ahead and update
> >> >>> > the
> >> >>> > reference?
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> > Brad
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> > -Exiting @ tick 31749698 because maximum number of loads reached
> >> >>> >
> >> >>> > +Exiting @ tick 31693010 because maximum number of loads reached
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> > ===== Statistics differences =====
> >> >>> >
> >> >>> > Maximum error magnitude: +0.911268%
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> >                                   Reference  New Value   Abs Diff
> >> >>> > Pct
> >> >>> > Chg
> >> >>> >
> >> >>> > Key statistics:
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> >   host_mem_usage                    1507496    1522440      14944
> >> >>> > +0.99%
> >> >>> >
> >> >>> >   sim_ticks                        31749698   31693010     -56688
> >> >>> > -0.18%
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> > Largest 20 relative errors (> 0%):
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> >   sim_ticks                        31749698   31693010     -56688
> >> >>> > -0.18%
> >> >>> >
> >> >>> >   system.cpu0.num_reads               99565      99568          3
> >> >>> > +0.00%
> >> >>> >
> >> >>> >   system.cpu0.num_writes              53743      53636       -107
> >> >>> > -0.20%
> >> >>> >
> >> >>> >   system.cpu1.num_reads               99657      99545       -112
> >> >>> > -0.11%
> >> >>> >
> >> >>> >   system.cpu1.num_writes              53715      53439       -276
> >> >>> > -0.51%
> >> >>> >
> >> >>> >   system.cpu2.num_reads               99204      99287         83
> >> >>> > +0.08%
> >> >>> >
> >> >>> >   system.cpu2.num_writes              53874      53468       -406
> >> >>> > -0.75%
> >> >>> >
> >> >>> >   system.cpu3.num_writes              53515      53560         45
> >> >>> > +0.08%
> >> >>> >
> >> >>> >   system.cpu4.num_reads               99473      99582        109
> >> >>> > +0.11%
> >> >>> >
> >> >>> >   system.cpu4.num_writes              53442      53929        487
> >> >>> > +0.91%
> >> >>> >
> >> >>> >   system.cpu5.num_reads               99627      99543        -84
> >> >>> > -0.08%
> >> >>> >
> >> >>> >   system.cpu5.num_writes              53511      53703        192
> >> >>> > +0.36%
> >> >>> >
> >> >>> >   system.cpu6.num_reads               99662      99253       -409
> >> >>> > -0.41%
> >> >>> >
> >> >>> >   system.cpu6.num_writes              53565      53497        -68
> >> >>> > -0.13%
> >> >>> >
> >> >>> >   system.cpu7.num_reads               99533      99640        107
> >> >>> > +0.11%
> >> >>> >
> >> >>> >   system.cpu7.num_writes              53739      53676        -63
> >> >>> > -0.12%
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> > *****
> >> >>> >
> build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby
> >> >>> > FAILED!
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> > scons: done building targets.
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> > From: m5-dev-boun...@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-in, and I will fix it
> >> >>> > if
> >> >>> > it
> >> >>> > doesn't.
> >> >>> >
> >> >>> > Polina
> >> >>> >
> >> >>> > On Sun, Oct 18, 2009 at 1:07 PM, Beckmann, Brad
> >> >>> > <brad.beckm...@amd.com>
> >> >>> > wrote:
> >> >>> >
> >> >>> > I might be able to help with this, but I'm not sure exactly what
> the
> >> >>> > problem is.  It might be caused by a reference to the
> "libruby_file"
> >> >>> > variable in ruby_se.py.  I can't (or don't know how to) access
> >> >>> > /z/m5/regression/regress-2009-10-18-03:00:01 to confirm, but
> >> >>> > memtest-ruby is working for me 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--scratch all
> >> >>> >
> >> >>> > Polina or Derek.  Can one of you *please* take a look at what
> >> >>> > happened
> >> >>> > with this regression and fix it?  It really won't take that long.
> >> >>> >
> >> >>> >  Nate
> >> >>> >
> >> >>> > On Sun, Oct 18, 2009 at 4:44 AM, Cron Daemon
> >> >>> > <r...@zizzer.eecs.umich.edu> 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.
> >> >>> >> *****
> >> >>> >
> 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/ALPHA_SE/tests/fast/long/00.gzip/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/00.hello/alpha/linux/simple-atomic
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >
> >> >>> >
> build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >> build/ALPHA_SE/tests/fast/long/30.eon/alpha/tru64/simple-atomic
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >
> >> >>> >
> build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby
> >> >>> > passed.
> >> >>> >> *****
> >> >>> > build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/simple-atomic
> >> >>> > passed.
> >> >>> >> *****
> >> >>> > build/ALPHA_SE/tests/fast/long/50.vortex/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/long/00.gzip/alpha/tru64/simple-timing
> >> >>> > 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/00.hello/alpha/linux/o3-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >
> build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >> build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest
> >> >>> > passed.
> >> >>> >> *****
> >> >>> > build/ALPHA_SE/tests/fast/long/60.bzip2/alpha/tru64/simple-atomic
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >
> build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/inorder-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >> build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/o3-timing
> >> >>> > passed.
> >> >>> >> *****
> build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/o3-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >
> build/ALPHA_SE/tests/fast/long/40.perlbmk/alpha/tru64/simple-atomic
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >> build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/o3-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> > build/ALPHA_SE/tests/fast/long/60.bzip2/alpha/tru64/simple-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >
> build/ALPHA_SE/tests/fast/long/40.perlbmk/alpha/tru64/simple-timing
> >> >>> > 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-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >> build/ALPHA_SE/tests/fast/long/30.eon/alpha/tru64/simple-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >
> build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby
> >> >>> > FAILED!
> >> >>> >> *****
> >> >>> >
> build/ALPHA_FS/tests/fast/long/10.linux-boot/alpha/linux/tsunami-o3
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >
> build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/inorder-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >
> >> >>> >
> >> >>> >
> build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple
> >> >>> > -atomic passed.
> >> >>> >> *****
> >> >>> > build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/inorder-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >
> >> >>> >
> >> >>> >
> build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple
> >> >>> > -atomic-dual passed.
> >> >>> >> *****
> >> >>> >
> >> >>> >
> >> >>> >
> build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple
> >> >>> > -timing passed.
> >> >>> >> *****
> >> >>> >
> >> >>> >
> >> >>> >
> build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple
> >> >>> > -timing-dual passed.
> >> >>> >> *****
> >> >>> >
> >> >>> >
> >> >>> >
> build/ALPHA_FS/tests/fast/quick/80.netperf-stream/alpha/linux/twosys-tsu
> >> >>> > nami-simple-atomic passed.
> >> >>> >> *****
> >> >>> >
> >> >>> >
> >> >>> >
> build/ALPHA_FS/tests/fast/long/10.linux-boot/alpha/linux/tsunami-o3-dual
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >> build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/simple-atomic
> >> >>> > passed.
> >> >>> >> *****
> >> >>> > build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/inorder-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >
> >> >>> >
> build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/simple-atomic-ruby
> >> >>> > passed.
> >> >>> >> *****
> build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/o3-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >> build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/simple-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >
> >> >>> >
> build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/simple-timing-ruby
> >> >>> > passed.
> >> >>> >> ***** build/ALPHA_SE/tests/fast/long/30.eon/alpha/tru64/o3-timing
> >> >>> > passed.
> >> >>> >> *****
> build/ALPHA_SE/tests/fast/long/00.gzip/alpha/tru64/o3-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >
> >> >>> >
> build/SPARC_SE/tests/fast/quick/02.insttest/sparc/linux/simple-atomic
> >> >>> > passed.
> >> >>> >> *****
> >> >>> > build/SPARC_SE/tests/fast/quick/02.insttest/sparc/linux/o3-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >
> >> >>> >
> >> >>> >
> build/SPARC_SE/tests/fast/quick/40.m5threads-test-atomic/sparc/linux/sim
> >> >>> > ple-atomic-mp-ruby passed.
> >> >>> >> *****
> >> >>> >
> >> >>> >
> >> >>> >
> build/SPARC_SE/tests/fast/quick/40.m5threads-test-atomic/sparc/linux/o3-
> >> >>> > timing-mp passed.
> >> >>> >> *****
> >> >>> > build/SPARC_SE/tests/fast/long/50.vortex/sparc/linux/simple-atomic
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >
> >> >>> >
> build/SPARC_SE/tests/fast/quick/00.hello/sparc/linux/simple-atomic-ruby
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >
> >> >>> >
> build/SPARC_SE/tests/fast/quick/02.insttest/sparc/linux/simple-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> > build/SPARC_SE/tests/fast/quick/00.hello/sparc/linux/simple-atomic
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >
> >> >>> >
> >> >>> >
> build/SPARC_SE/tests/fast/quick/40.m5threads-test-atomic/sparc/linux/sim
> >> >>> > ple-timing-mp passed.
> >> >>> >> *****
> >> >>> > build/SPARC_SE/tests/fast/quick/00.hello/sparc/linux/simple-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >
> >> >>> >
> build/SPARC_SE/tests/fast/quick/00.hello/sparc/linux/simple-timing-ruby
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >> build/SPARC_SE/tests/fast/long/10.mcf/sparc/linux/simple-atomic
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >
> >> >>> >
> >> >>> >
> build/SPARC_SE/tests/fast/quick/40.m5threads-test-atomic/sparc/linux/sim
> >> >>> > ple-atomic-mp passed.
> >> >>> >> *****
> >> >>> > build/SPARC_SE/tests/fast/long/70.twolf/sparc/linux/simple-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> > build/SPARC_SE/tests/fast/long/70.twolf/sparc/linux/simple-atomic
> >> >>> > passed.
> >> >>> >> *****
> >> >>> > build/SPARC_SE/tests/fast/long/50.vortex/sparc/linux/simple-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >> build/SPARC_SE/tests/fast/long/10.mcf/sparc/linux/simple-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >> build/SPARC_SE/tests/fast/long/00.gzip/sparc/linux/simple-atomic
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >> build/SPARC_SE/tests/fast/long/00.gzip/sparc/linux/simple-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >> build/X86_SE/tests/fast/quick/00.hello/x86/linux/simple-atomic
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >> build/X86_SE/tests/fast/quick/00.hello/x86/linux/simple-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >
> build/X86_SE/tests/fast/quick/00.hello/x86/linux/simple-timing-ruby
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >
> >> >>> >
> >> >>> >
> build/SPARC_FS/tests/fast/long/80.solaris-boot/sparc/solaris/t1000-simpl
> >> >>> > e-atomic passed.
> >> >>> >> ***** build/X86_SE/tests/fast/long/10.mcf/x86/linux/simple-timing
> >> >>> > passed.
> >> >>> >> *****
> build/X86_SE/tests/fast/long/70.twolf/x86/linux/simple-atomic
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >> build/X86_SE/tests/fast/long/20.parser/x86/linux/simple-atomic
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >> build/X86_SE/tests/fast/long/20.parser/x86/linux/simple-timing
> >> >>> > passed.
> >> >>> >> *****
> build/X86_SE/tests/fast/long/00.gzip/x86/linux/simple-atomic
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >
> build/X86_SE/tests/fast/quick/00.hello/x86/linux/simple-atomic-ruby
> >> >>> > passed.
> >> >>> >> *****
> build/X86_SE/tests/fast/long/00.gzip/x86/linux/simple-timing
> >> >>> > passed.
> >> >>> >> *****
> build/X86_SE/tests/fast/long/70.twolf/x86/linux/simple-timing
> >> >>> > passed.
> >> >>> >> ***** build/X86_SE/tests/fast/long/10.mcf/x86/linux/simple-atomic
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >> build/ARM_SE/tests/fast/quick/00.hello/arm/linux/simple-atomic
> >> >>> > passed.
> >> >>> >> *****
> build/X86_SE/tests/fast/long/60.bzip2/x86/linux/simple-atomic
> >> >>> > passed.
> >> >>> >> *****
> build/X86_SE/tests/fast/long/60.bzip2/x86/linux/simple-timing
> >> >>> > passed.
> >> >>> >> *****
> >> >>> >> build/ALPHA_SE/tests/fast/long/40.perlbmk/alpha/tru64/o3-timing
> >> >>> > passed.
> >> >>> >> *****
> build/ALPHA_SE/tests/fast/long/60.bzip2/alpha/tru64/o3-timing
> >> >>> > passed.
> >> >>> >> *****
> build/SPARC_SE/tests/fast/long/00.gzip/sparc/linux/o3-timing
> >> >>> > passed.
> >> >>> >>
> >> >>> >> See /z/m5/regression/regress-2009-10-18-03:00:01 for details.
> >> >>> >>
> >> >>> >> _______________________________________________
> >> >>> >> m5-dev mailing list
> >> >>> >> m5-dev@m5sim.org
> >> >>> >> http://m5sim.org/mailman/listinfo/m5-dev
> >> >>> >>
> >> >>> >>
> >> >>> > _______________________________________________
> >> >>> > m5-dev mailing list
> >> >>> > m5-dev@m5sim.org
> >> >>> > http://m5sim.org/mailman/listinfo/m5-dev
> >> >>> >
> >> >>> >
> >> >>> > _______________________________________________
> >> >>> > m5-dev mailing list
> >> >>> > m5-dev@m5sim.org
> >> >>> > http://m5sim.org/mailman/listinfo/m5-dev
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> > _______________________________________________
> >> >>> > m5-dev mailing list
> >> >>> > m5-dev@m5sim.org
> >> >>> > http://m5sim.org/mailman/listinfo/m5-dev
> >> >>> >
> >> >>> >
> >> >>> _______________________________________________
> >> >>> m5-dev mailing list
> >> >>> m5-dev@m5sim.org
> >> >>> http://m5sim.org/mailman/listinfo/m5-dev
> >> >>
> >> >
> >> >
> >> > _______________________________________________
> >> > m5-dev mailing list
> >> > m5-dev@m5sim.org
> >> > http://m5sim.org/mailman/listinfo/m5-dev
> >> >
> >> >
> >> _______________________________________________
> >> m5-dev mailing list
> >> m5-dev@m5sim.org
> >> http://m5sim.org/mailman/listinfo/m5-dev
> >>
> >>
> >> _______________________________________________
> >> m5-dev mailing list
> >> m5-dev@m5sim.org
> >> http://m5sim.org/mailman/listinfo/m5-dev
> >
> >
> > _______________________________________________
> > m5-dev mailing list
> > m5-dev@m5sim.org
> > http://m5sim.org/mailman/listinfo/m5-dev
> >
> >
> _______________________________________________
> m5-dev mailing list
> m5-dev@m5sim.org
> http://m5sim.org/mailman/listinfo/m5-dev
>
_______________________________________________
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev

Reply via email to