Closed nschlia closed 1 year ago
These are actually two problems:
In both cases, the read action waits until time out, no image is returned.
Problem still comes up:
$ ./test_frameset_bmp
Checking number of files is 250
Number of files OK
Checking access with full name
>> Checking 000204.bmp
'/tmp/tmp.KQRERvDGfk/frame_test_pal.mp4/000204.bmp' -> '/dev/null'
>> Checking 000004.bmp
'/tmp/tmp.KQRERvDGfk/frame_test_pal.mp4/000004.bmp' -> '/dev/null'
cp: error reading '/tmp/tmp.KQRERvDGfk/frame_test_pal.mp4/000004.bmp': Connection timed out
Return code: 1
Looks good after the last change.
Several new builds, did not happen any more, seems to be fixed!
FAIL: test_frameset_bmp
Still happening...
It hasn't appeared since May. Oh how I hate these kinds of bugs. Is it now fixed or is it not?!?
Closed. May be re-opened if happening again.
Still happens
One of frameset tests (test_frameset_bmp, test_frameset_jpg, test_frameset_png) occasionally fails. Next build it succeeds, or another fails. Seems to be a thread synchonisation/timing problem.
Example:
FAIL: test_frameset_bmp
Log has some explanation:
2022-01-05 20:30:45 ERROR : [srcdir/frame_test_pal.mp4] Reading image frame no. 4: (11) Resource temporarily unavailable
The error code EAGAIN (Resource temporarily unavailable) is returned when a frame is not returned within 30 seconds. Quite unlikely...