Aleksey Shipilëv
Aleksey Shipilëv
> > I can run the jcstress test. I will run fastdebug build with `java -jar jcstress-latest.jar -tb 24h` Is it the correct command > > Yes, I think so....
> Thanks for testing. I'm running jcstress on a neoverse-n2 instance. I got some "soft errs" in console output. Are they real error? Soft errors are API inconsistencies that jcstress...
GH says the branch has conflicts that must be resolved. Merging from master is advisable anyway to avoid merge surprises. Let's do that before integrating.
> I'll run this through our correctness and performance testing and report back once it passed. How was it, Tobias? Any surprises?
> Sorry for the delay, I had to re-run a subset of the benchmarks due to high variance. All green now. Great, thanks for testing. I think we are ready...
This thing: ``` Stack: [0x0000733a11cfe000,0x0000733a11dfe000], sp=0x0000733a11dfc990, free space=1018k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) V [libjvm.so+0x823129] G1ParScanThreadState::trim_queue_to_threshold(unsigned int)+0x209 V [libjvm.so+0x839fd3] G1ScanHRForRegionClosure::scan_heap_roots(HeapRegion*)+0x903 V [libjvm.so+0x837188] G1RemSet::scan_heap_roots(G1ParScanThreadState*, unsigned int,...
I think what @earthling-amzn said above makes sense. It would be interesting to see if we catch any asserts with fastdebug builds. We have already backported a few things to...
Can you please attach the `hs_err` file? There are no direct hits in bugtrackers for this particular error, so the full stack trace and reproducer would be handy to understand...
OK, I think _most_ of the tests are passing. There are some Windows failures, but I don't think they are regression from this PR, and they do not block us....