[m5-dev] Cron m5t...@zizzer /z/m5/regression/do-regression quick

2010-02-22 Thread Cron Daemon
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/inorder-timing passed. * build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing passed. * build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp passed. *

[m5-dev] changeset in m5: BaseDynInst: Preserve the faults returned from ...

2010-02-22 Thread Timothy M. Jones
changeset 862a31349d43 in /z/repo/m5 details: http://repo.m5sim.org/m5?cmd=changeset;node=862a31349d43 description: BaseDynInst: Preserve the faults returned from read and write. When implementing timing address translations instead of atomic, I forgot to preserve the

Re: [m5-dev] changeset in m5: BaseDynInst: Preserve the faults returned from ...

2010-02-22 Thread Timothy M Jones
Hi everyone, First of all, sorry once again that this changeset was necessary. I thought all the regression tests passed for me before I pushed and I'm still not sure why I didn't pick this up. Second, I noticed when checking this patch that two other regresssions were failing: *

[m5-dev] Cron m5t...@zizzer /z/m5/regression/do-regression --scratch all

2010-02-22 Thread Cron Daemon
* 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. *

[m5-dev] Cron m5t...@zizzer /z/m5/regression/do-regression --scratch all

2010-02-22 Thread Cron Daemon
* 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. *

Re: [m5-dev] Cron /z/m5/regression/do-regression --scratch all

2010-02-22 Thread Ali Saidi
Looks like Alpha o3 boot is failing. Anyone know why? Ali On Mon, 22 Feb 2010 12:03:45 -0500, r...@zizzer.eecs.umich.edu (Cron Daemon) wrote: * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby passed. *

Re: [m5-dev] Cron /z/m5/regression/do-regression --scratch all

2010-02-22 Thread Steve Reinhardt
There's a more general problem here, which is that the 2/14 regression finished one minute after the 2/21 regression, 33 hours after the 2/21 regression started (and 9 hours after the 2/22 regression). I don't think scons likes having multiple builds going on simultaneously, so there may be some

Re: [m5-dev] Cron /z/m5/regression/do-regression --scratch all

2010-02-22 Thread Lisa Hsu
This is because of the push that I've been talking with Timothy Jones about, he just pushed a fix to it this morning. The bad changeset caused Alpha O3 boot to hang and go on indefinitely. It occurred to me last night that the runs would just still be going on zizzer, so I killed 2 instances this

Re: [m5-dev] Cron /z/m5/regression/do-regression --scratch all

2010-02-22 Thread Timothy M Jones
It could be that the long-running tests are my fault. Lisa emailed me about ALPHA_FS/test/fast/long/10.linux-boot tests hanging which could be part of this problem. I pushed a patch this morning which fixes those, so that may help with things. Tim On Mon, 22 Feb 2010 13:21:35 -0500,