Community
Participate
Working Groups
When changing junit5 test files and clicking the "run junit button" within 1-10 seconds, then the changes are not reflected. This means: eclipse runs the junit test file with the old revision. It's tedious to wait 10 seconds between each editing before running a new test. It has to do something with the refresh rate, but I don't know if the user can set this to a lower level. I already gave eclipse over 16GB RAM and my machine should be fast enough. So why does eclipse cannot use the newest file? The problem sometime also occur in the whole UI. When changing a file, the validation or compiling cycle is sooo slow that I have to wait until eclipse reflects the new changes to the UI.
The problem still exist in Version: 2021-12 (4.22.0): Steps to reproduce: - edit any junit test class and press save - the compilation step for this changed (and saved!) test class is made not immediately but after an undetermined waiting time (e.g. 10-60 seconds, mostly approx. 30 seconds). - because of this waiting time of the compilations step, the junit test case cannot be run after it was saved. Expected behaviour: When the user clicks the save button, then the (incremental) compilation should be done immediately.
I think, I found the reason for the build delay: https://bugs.eclipse.org/bugs/show_bug.cgi?id=570794 I use Mac OS and there seems problems with using native hooks..
