* build/ALPHA_SE/tests/opt/quick/20.eio-short/alpha/eio/simple-atomic
passed.
* build/ALPHA_SE/tests/opt/quick/00.hello/alpha/linux/simple-atomic passed.
* build/ALPHA_SE/tests/opt/quick/01.hello-2T-smt/alpha/linux/o3-timing
passed.
* build/ALPHA_SE/tests/opt/quick/00.hello/alpha/
* build/ALPHA_SE/tests/opt/quick/20.eio-short/alpha/eio/simple-atomic
passed.
* build/ALPHA_SE/tests/opt/quick/00.hello/alpha/tru64/simple-timing passed.
* build/ALPHA_SE/tests/opt/quick/00.hello/alpha/tru64/simple-atomic passed.
* build/ALPHA_SE/tests/opt/quick/00.hello/alpha/linu
* build/ALPHA_SE/tests/opt/quick/20.eio-short/alpha/eio/simple-timing
passed.
* build/ALPHA_SE/tests/opt/quick/00.hello/alpha/tru64/o3-timing passed.
* build/ALPHA_SE/tests/opt/quick/00.hello/alpha/linux/simple-timing passed.
* build/ALPHA_SE/tests/opt/quick/00.hello/alpha/tru64/si
* build/X86_SE/tests/opt/long/20.parser/x86/linux/o3-timing FAILED!
* build/ALPHA_SE/tests/opt/quick/30.eio-mp/alpha/eio/simple-atomic-mp
passed.
* build/ALPHA_SE/tests/opt/quick/00.hello/alpha/tru64/o3-timing passed.
* build/ALPHA_SE/tests/opt/quick/00.hello/alpha/linux/simple-tim
Argh. I guess different versions of python deal with this differently
too. I'll try to fix this tonight. Stupid demandimport.
Nate
> Deleting build didn't seem to do anything.
>
> Traceback (most recent call last):
> File "", line 1, in
> File "/z/m5/regression/zizzer/m5/src/python/import
Deleting build didn't seem to do anything.
Traceback (most recent call last):
File "", line 1, in
File "/z/m5/regression/zizzer/m5/src/python/importer.py", line 73, in
load_module
exec code in mod.__dict__
File "/z/m5/regression/zizzer/m5/src/python/m5/__init__.py", line 38,
in
int
* build/ALPHA_SE/tests/fast/long/00.gzip/alpha/tru64/inorder-timing FAILED!
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-atomic
FAILED!
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing FAILED!
* build/ALPHA_SE/tests/fast/quick/50.memtest/alpha
* 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/60.rubytest/alpha/linux/rubytest-ruby
passed.
* build/ALPHA_SE/tests/fast/long/50.vortex/a
Hey Gabe,
The change definitely could change the stats. If a block was ever dirty and
then instructions from that block we're ever executed (either because data and
inst were close or a misprediction) the dirty data could be lost. In this case
the cache would send the block to fetch in the owne
It looks like it was this change which was directly after the one I
pointed out before.
changeset: 8134:b01a51ff05fa
user:Ali Saidi
date:Thu Mar 17 19:20:19 2011 -0500
summary: Mem: Fix issue with dirty block being lost when entire
block transferred to non-cache.
Could you
Does anyone have any ideas about when X86_SE parser stopped working? The
last time it passed for sure was the end of February, but on March 16th
Ali updated the stats and so it was presumably working then too. I'm
running at that changeset right now to confirm that. There weren't any
X86 specific c
* build/X86_SE/tests/fast/long/20.parser/x86/linux/o3-timing FAILED!
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby
passed.
* build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/s
Traceback (most recent call last):
File "", line 1, in
File "/z/m5/regression/zizzer/m5/src/python/m5/main.py", line 348, in main
exec filecode in scope
File "tests/run.py", line 70, in
execfile(joinpath(tests_root, 'configs', test_filename + '.py'))
File "tests/configs/simple-tim
M5 exited with non-zero status*
build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby FAILED!
* build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby
FAILED!
* build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby
FAILED!
* build/AL
I had committed an error in one of the my recent patches. I have committed
a patch that should fix this error.
--
Nilay
On Sun, 20 Mar 2011, Cron Daemon wrote:
See /z/m5/regression/regress-2011-03-20-03:00:01 for details.
___
m5-dev mailing list
m
See /z/m5/regression/regress-2011-03-20-03:00:01 for details.
___
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
That makes sense. I've changed it.
Gabe
On 03/13/11 21:35, Ali Saidi wrote:
> I think we should just use /dist. The automounter is flaky.
>
> Ali
>
> On Mar 13, 2011, at 5:58 PM, Gabe Black wrote:
>
>> These failed because M5 looked for the disk image on /n/poolfs/... and
>> I'd only put it on /
I think we should just use /dist. The automounter is flaky.
Ali
On Mar 13, 2011, at 5:58 PM, Gabe Black wrote:
> These failed because M5 looked for the disk image on /n/poolfs/... and
> I'd only put it on /dist/... on zizzer. I copied it over so this should
> work next time, hopefully, and that
These failed because M5 looked for the disk image on /n/poolfs/... and
I'd only put it on /dist/... on zizzer. I copied it over so this should
work next time, hopefully, and that also means that when I explicitly
setting M5_PATH in the cron tab it actually worked.
The M5_PATH is now set to just us
* build/X86_FS/tests/fast/quick/10.linux-boot/x86/linux/pc-simple-timing
FAILED!
* build/X86_FS/tests/fast/quick/10.linux-boot/x86/linux/pc-simple-atomic
FAILED!
* build/X86_SE/tests/fast/long/00.gzip/x86/linux/o3-timing FAILED!
* build/X86_SE/tests/fast/long/20.parser/x86/linux/o
On Sat, Mar 5, 2011 at 8:54 PM, Gabe Black wrote:
> The problem was that the following directory belonged to root and
> couldn't be deleted to rebuild from scratch. If somebody went and ran
> this particular regression by hand (and as root) that could explain the
> problem.
>
When I updated this
The problem was that the following directory belonged to root and
couldn't be deleted to rebuild from scratch. If somebody went and ran
this particular regression by hand (and as root) that could explain the
problem.
build/ALPHA_SE/tests/fast/long/60.bzip2/alpha/tru64/inorder-timing/bzip2_m5out/
See /z/m5/regression/regress-2011-03-06-03:00:02 for details.
___
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
Sorry about that folks.
Looks like I committed the regression stats from some uncommitted patches.
Should be updated now.
On Sun, Feb 27, 2011 at 1:13 PM, Ali Saidi wrote:
> Korey,
>
> It doesn't look like anything committed between when you added your
> regression test and this failing could
Korey,
It doesn't look like anything committed between when you added your regression
test and this failing could have changed the inorder stats. Could you take a
look at it?
Thanks,
Ali
On Feb 27, 2011, at 10:33 AM, Cron Daemon wrote:
> * build/ALPHA_SE/tests/fast/long/60.bzip2/alpha/tru
* build/ALPHA_SE/tests/fast/long/60.bzip2/alpha/tru64/inorder-timing FAILED!
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alp
* 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/20.eio-short/alpha/
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/o3-timing passed.
* build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/s
Oops. I actually did test on zizzer, ran into this issue, fixed it re-ran the
regressions and then forgot to put the fix back in my patch queue. Sorry about
that. I fixed it by replacing NULL with 0, but your fix looks fine as well.
Ali
Sent from my ARM powered device
On Feb 13, 2011, at 5:17
Looks correct to me (though I'm not an ARM guy)
Nate
On Sun, Feb 13, 2011 at 3:17 AM, Gabe Black wrote:
> These are failing because of the following:
>
> cc1plus: warnings being treated as errors
> build/SPARC_SE/cpu/o3/inst_queue_impl.hh: In member function 'void
> InstructionQueue::scheduleR
These are failing because of the following:
cc1plus: warnings being treated as errors
build/SPARC_SE/cpu/o3/inst_queue_impl.hh: In member function 'void
InstructionQueue::scheduleReadyInsts() [with Impl = O3CPUImpl]':
build/SPARC_SE/cpu/o3/inst_queue.cc:35: instantiated from here
build/SPARC_SE/
scons: *** [build/ALPHA_SE/cpu/o3/inst_queue.fo] Error 1
scons: *** [build/ALPHA_SE_MOESI_hammer/cpu/o3/inst_queue.fo] Error 1
scons: *** [build/ALPHA_SE_MESI_CMP_directory/cpu/o3/inst_queue.fo] Error 1
scons: *** [build/ALPHA_SE_MOESI_CMP_directory/cpu/o3/inst_queue.fo] Error 1
scons: *** [build/A
* 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/00.hello/alpha/linux/simple-timing passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/s
* 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-timing passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing passed.
* build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing 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/linux/simple-timing passed.
* build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/inorder-timing
passed.
* build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby
passed.
* build/ALPHA_SE/tests/fast/long/00.gzip/alpha/t
* 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/00.hello/alpha/linux/simple-timing passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/s
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing 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-timing-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/20.eio-sh
* 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/01.hello-2T-smt/alpha/linux/o3-timing
passed.
* build/ALPHA_SE/tests/fast/quick/30.eio-m
* 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/00.hello/alpha
* 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/00.hello/alpha
* 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/00.hello/alpha
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/o3-timing passed.
* build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/simple-atomic passed.
* build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tr
* 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/tru64/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha
* 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-atomic-mp
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/60.rubytest/
* 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/tru64/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha
* 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/
* 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/20.eio-short/alpha/
* 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/20.eio-short/alpha/eio/simple-timing
passed.
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/
* 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/20.eio-short/alpha/
* 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/20.eio-short/alpha/
* build/ALPHA_SE/tests/fast/quick/00.hello/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/20.eio-short/a
It's likely then that this is the reason Joel is having issues too...
Ali
On Sep 19, 2010, at 7:37 PM, Gabe Black wrote:
> These two failed last night. The last week was when swig versions were
> causing trouble and the week before that worked, so something happened
> in the last 2 weeks. Lookin
These two failed last night. The last week was when swig versions were
causing trouble and the week before that worked, so something happened
in the last 2 weeks. Looking at my email for that period I think that
means this is either Nate's fault or mine, and judging by the changes
involved it's mor
* build/ALPHA_FS/tests/fast/long/10.linux-boot/alpha/linux/tsunami-o3-dual
FAILED!
* build/ALPHA_FS/tests/fast/long/10.linux-boot/alpha/linux/tsunami-o3
FAILED!
* build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing
passed.
* build/ALPHA_SE/tests/fast/quick/00.he
M5 exited with non-zero status 1*
build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/simple-atomic FAILED!
* build/ALPHA_SE/tests/fast/long/40.perlbmk/alpha/tru64/simple-timing
FAILED!
* build/ALPHA_SE/tests/fast/long/60.bzip2/alpha/tru64/simple-atomic FAILED!
* build/ALPHA_SE/t
* 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/01.hello-2T-smt/al
* 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/00.hello/alpha
* 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/
* 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/20.eio-shor
* 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/long/70.twolf/alp
* 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/long/70.twolf/alp
* 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/20.eio-short/alpha
* 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/20.eio-short/al
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/o3-timing FAILED!
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/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/linux/i
* 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/long/70.two
* 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/long/50.vor
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/00.h
* 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/long/70.two
* 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/long/70.two
* 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/long/70.two
* 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.
* build/ALPHA_SE/tests/fast/long/50.vor
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 o
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-timing-mp
FAILED!
* 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.
* build/ALPHA_SE/tests/fast/long/00.gzip/alp
> 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
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 wrote:
> It seems that /dist was out of commission.
>
> Nate
>
> On Sun, Apr 11, 2010 at 4:26 AM, Cron Daemon
> wrote:
>> * bui
It seems that /dist was out of commission.
Nate
On Sun, Apr 11, 2010 at 4:26 AM, Cron Daemon 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
> FAILED!
> * build/AL
* 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.
* build/ALPHA_SE/tests/fast/quick/00.hello/a
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 wrote:
> 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
> op
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 whe
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 even
* 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.
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alph
t;
> + // NumInternalProcRegs=74 and IPR_DTB_CM=58, yet an error is flagged
>
> + //
>
> mode_type mode =
>
> (mode_type)DTB_CM_CM(tc->readMiscRegNoEffect(IPR_DTB_CM));
>
>
>
>
>
>
>
> From: m5-dev-boun...@m5sim.org [mailto:m5-dev-b
or 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 /z/m5/regressi
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 th
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 differ
Actually they are run weekly, not monthly, though if something goes
wrong with a run you can miss a week or two.
And yes, if it's not giving consistent results on your machine vs.
zizzer then that's a problem. Is it consistent on each machine?
(I.e., your machine is consistent, and zizzer is cons
> 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 hittin
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 slightly
haven't we been having problems with inorder-timing for a while?
On Mon, Mar 29, 2010 at 12:19 AM, Steve Reinhardt wrote:
> Thanks for highlighting that. Looks like it's just a minor stats difference:
>
> = Statistics differences =
> Maximum error magnitude: +0.028348%
>
>
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
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.
> * build/ALPHA_SE/tests/fast/quick/00.hello/
* 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.
* build/ALPHA_SE/tests/fast/quick/20.eio-short/al
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
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 su
We're still getting those 'invalid IPR' errors...
On Sun, Mar 21, 2010 at 3:46 AM, Cron Daemon 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
> FAILED!
_
* 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.
* build/ALPHA_SE/tests/fast/quick/60.rubytest/
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 e
* 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.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha
iprs are accessed from palcode on alpha, so perhaps your palcode is
different from zizzer's.
Nate
On Tue, Mar 9, 2010 at 6:39 PM, Korey Sewell wrote:
>> 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
1 - 100 of 225 matches
Mail list logo
