On 1/8/07, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
On Jan 8, 2007, at 1:20 PM, Weldon Washburn wrote: > On 1/8/07, Rana Dasgupta <[EMAIL PROTECTED]> wrote: >> >> On 1/7/07, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote: >> > >> > >What is in the backlog? >> > >> > >I was testing on em64t dual core, and it failed there too. >> >> >> Which one failed in 64 bit mode? The basic stress.Mix or Weldon's >> MegaSpawn? >> And did it hang, or run out of memory? Running out of memory on >> these 64 >> bit >> systems is not easy even under the conditions of this test. >> >> >I think we broke something basic. By just ignoring it and >> continuing >> > >with commits that are related, it seems like we're going going >> to get >> > >in deeper trouble... >> >> >> I am a little confused too. The stress.Mix test can randomly land >> up doing >> unbounded thread creation( as in Weldon's repro case )...and I >> would think >> that it is not unreasonable to fail in such a case. The RI fails >> too. But >> I >> don't understand how it never failed before. >> >> > I attempted to determine if there ever was an old svn revision that > would > pass stress.Mix test on my rhel 2-way SMP box. Unfortunately the > unified > classlib/vm build changed the how one gets an old revision from the > repository. I don't know if its worth trying to resurect an old svn > revision. I am hoping someone will confirm if stress.Mix ever ran > successfully on 2-way and 4-way boxes. This seems way easier than > trying to > reconstruct old build.xml files. Huh? Why do you think you need to reconstruct anything?
Its a moot point. Naveen got the answers for us already. geir
-- Weldon Washburn Intel Enterprise Solutions Software Division
