Do we need tesseract in the build?

[damies13]

The merge build for PR #378 failed for reporter windows because:

https://github.com/damies13/rfswarm/actions/runs/17959871604/job/51080591670

Run Invoke-WebRequest -Uri "https://digi.bib.uni-mannheim.de/tesseract/tesseract-ocr-w64-setup-5.3.1.20230401.exe" -OutFile "$($ENV:Temp)\tesseract-ocr-w64-setup-5.3.1.20230401.exe"
Invoke-WebRequest: D:\a\_temp\5840021e-6a67-44a9-a858-50de7803cd2d.ps1:2
Line |
   2 |  Invoke-WebRequest -Uri "https://digi.bib.uni-mannheim.de/tesseract/te …
     |  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | A connection attempt failed because the connected party did not properly respond after a period of time, or
     | established connection failed because connected host has failed to respond.
Error: Process completed with exit code 1.

I think this has happened before, and perhaps the download location is not that reliable (it's also very slow being a German Uni Infrastructure)

The question is did we end up using OCR and having it work? If not can we potentially remove this from the build?

Something to investigate: is this a dependency we actually need or is it something we can remove and make the builds a little quicker?

• Potentially Manager build could also be impacted by this?

[ArekKuczynski]

The Robot Framework OCRLibary which is using the tesseract module, is only being used by the Find Text keyword in the Tests/Common/GUI_Text.resource file. However, this keyword is not currently used anywhere and was only used before as one of the solution, idea for dynamic button manipulation in Reporter GUI tests.
Since we are not currently using it, because that keyword wasn't reliable enough, we are free to remove the tesseract installation from workflows for now if no other modules depend on it.