Closed rzbrk closed 3 years ago
Inserting a ls -al
before executing md5sum in testcase 07 reveals that the heuristic approach in this line to decide where to put the md5sum file and where to perform the md5sum verification can go wrong. This way, sometimes simply the wrong run_* folder is selected.
The following testcases are affected:
04transmission-30s.sh not affected, because different code. There, we do not have to deal with different run* folders.
In a couple of testcases md5sum is used to verify the correct output of the Calliope Mini after flashing with a dedicated hex.
Sometimes, the verification goes wrong with md5sum claiming, the files to verify are not in place:
Reason currently unknown ...
The
sync
andsleep 1
in all testcases after executing the Python script seems not to be sufficient.