Because the machines were busy, which meant that the jobs timed out. Ali
On Aug 24, 2008, at 12:45 PM, Gabe Black wrote: > We should also figure out why the "all" regressions failed completely > last night. > > Gabe Black wrote: >> I'm pretty sure that perlbmk bug is still there and we just got rid >> of >> the regression. It might have gone away on it's own, but I don't >> think >> anyone actively tried to fix it. >> >> Gabe >> >> Ali Saidi wrote: >> >>> From the release notes the following are still outstanding for a 2.0 >>> release. I don't really care about the Cygwin problems and I'm not >>> sure that anyone else does, so I move to strike those. Additionally, >>> we made the repository public so that one is gone. >>> >>> I think the three things that need to be fixed are: >>> O3 CPU -- SMT SE regression hits an assert; bug causing perlbmk to >>> fail (Gabe reported this in April 2007 and I don't know if it's >>> still >>> a problem http://www.m5sim.org/flyspray/task/221); NACKs/coherence >>> messages >>> >>> Statistics -- The CPU statistics are confusing. I think the idle >>> time >>> in the simple CPU can still be wrong after a CPU switch and it's at >>> least not clear to me which idles mean quiesced time or idle because >>> of other things (blocked in the O3 case, not switched out in the >>> simple case); The bus needs statistics; I don't know if the cache >>> statistics are reasonable. >>> >>> Testing -- I've at least done a fair amount of testing over the last >>> month or two, so I'm pretty happy with that. I think some validation >>> needs to be done on an statistics changes though. >>> >>> Ali >>> >>> >>> >>> 1. Fix O3 CPU bug in SE 40.perlbmk fails >>> 2. Fix O3 processing nacks/coherence messages >>> 3. Better statistics for the caches. >>> 4. FS mode doesn't work under Cygwin >>> 5. memtest regression crashes under Cygwin >>> 6. Make repository public >>> 7. Testing >>> 8. Validation >>> >>> >>> On Aug 24, 2008, at 9:55 AM, Ali Saidi wrote: >>> >>> >>> >>>> Everyone should hold off pushing patches to the dev tree for the >>>> next >>>> two weeks so we can create a new stable release. Please only push >>>> fixes to known problems and test the repository in the next two >>>> weeks. >>>> >>>> Thanks, >>>> Ali >>>> >>>> _______________________________________________ >>>> 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
