What is in the backlog?
I was testing on em64t dual core, and it failed there too.
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...
geir
On Jan 6, 2007, at 6:35 PM, Weldon Washburn wrote:
I have been hesitant to commit patches given that stress.Mix fails
on my
2-cpu rhel4 box. It looks like MegaSpawn.java (see Harmony-2803)
identifies
stress.Mix failure to be a problem with handling an exceedingly
high rate of
thread creation. stress.Mix has been causing "build test" failures
since
December 19. This is a long time. It does not seem a good path to
rollback
to a time when stress.Mix ran on SMP boxes.
Does anyone have a problem with the following? Put stress.Mix on the
exclude list for all platforms and resume committing. This would
unblock a
growing backlog of commits. Also we can analyze and fix stress.Mix
related
bugs without extra pressure to quickly hack something to get the
test to
pass.
--
Weldon Washburn
Intel Enterprise Solutions Software Division
