ShenandoahStrDedupStress.java test

[Aleksey Shipilev]

On 07/16/2018 04:04 PM, Zhengyu Gu wrote:
> What you observed is that, it takes longer than used to? or it simply takes too long?

It simply takes too long, and that must tell us something about Shenandoah itself. Can you profile
the test with perf and see if we verify something excessively? Or there is some other peculiarity
that makes the test too long? Optimizing tests does pay off with development productivity.


> BTW, I think we should probably move all stress tests to tier3, and make tier2 the criteria for
> pushing? and run tier3 for nightly test?

We should definitely move all stress tests to tier3. I am a bit worried about relaxing our push
criteria, because stress tests do catch a fair amount of bug, especially for non-trivial changes. I
think we are having our educated guesses about which tier to run for each change already.


-Aleksey