I am maintaining an automated test environment, which tests devices, which are using PEI as their serial interface.
One of the tests sends an AT-command to reboot the device and measures the time till it is ready for usage.
With nrjavaserial 5.2.1 on (X)Ubuntu 20.04 64-bit and Java 17 (Corretto 17.0.2.8.1) this test fails about every 100th time (it seems to be every 73, sometimes 74 time).
The problem is that in these cases NRSerialPort.connect() never returns, after the device was rebooted.
Because the behaviour did not occur on our older setup (Windows 7 32-bit and Java 7) with nrjavaserial 3.15.0, I downgraded the newer setup from 5.2.1 to 3.15.0.
This now looks better from 1200 reboot tests only one got stuck. (I will update the numbers after the weekend.)
Update:
I setup the same use case with nrjavaserial 5.2.1 on Windows 10 64-bit. About 370 reboot tests were successfully run. No failures, therefore I assume, that the issue is Linux-specific.
Update after weekend:
The Linux-3.15.0 setup and the Windows-5.2.1 setup both have above 4000 reboot-tests and no failures.
Hello,
I am maintaining an automated test environment, which tests devices, which are using PEI as their serial interface. One of the tests sends an AT-command to reboot the device and measures the time till it is ready for usage.
With nrjavaserial 5.2.1 on (X)Ubuntu 20.04 64-bit and Java 17 (Corretto 17.0.2.8.1) this test fails about every 100th time (it seems to be every 73, sometimes 74 time). The problem is that in these cases
NRSerialPort.connect()never returns, after the device was rebooted.Because the behaviour did not occur on our older setup (Windows 7 32-bit and Java 7) with nrjavaserial 3.15.0, I downgraded the newer setup from 5.2.1 to 3.15.0.
This now looks better from 1200 reboot tests only one got stuck. (I will update the numbers after the weekend.)
Update:
Update after weekend: