Some CI jobs (GitHub Actions) are failing
amitdo opened this issue · comments
Current Behavior
They complain about nodejs 16.
https://github.com/tesseract-ocr/tesseract/actions
Expected Behavior
No response
Suggested Fix
No response
tesseract -v
No response
Operating System
No response
Other Operating System
No response
uname -a
No response
Compiler
No response
CPU
No response
Virtualization / Containers
No response
Other Information
No response
The solution: update all actions to use actions/checkout@v4.
I updated all checkout actions now, but I am afraid that was not the reason for the failing CI jobs.
You are right.
msys2:
https://packages.msys2.org/base/mingw-w64-leptonica
Repo(s):
clang64, clangarm64, mingw64, ucrt64
msys2/MINGW-packages@d0bed5dd8f14c0
With this commit, they removed 32-bit support for leptonica.
unittest-disablelegacy:
https://github.com/tesseract-ocr/tesseract/actions/runs/8129379770/job/22216419083
The reason for the failure is unclear.
cmake, ubuntu 22.04 clang-14:
https://github.com/tesseract-ocr/tesseract/actions/runs/8133022714/job/22224110737
autotools, ubuntu 22.04 clang-14
https://github.com/tesseract-ocr/tesseract/actions/runs/8132678362/job/22223385796
A simple solution is to remove clang-14 from the yml files.
Note that clang-14 on macOS and clang-15 on Linux have no issues.
The reason for the failure is unclear.
Timeout? It looks like the time for the test jumped from less than 20 minutes to more than 6 hours about 4 months ago. I have no idea why that happened.
About msys2. Turns out that mingw-w64 started to remove 32-bit support for many packages a while ago.
So let's remove the mingw-w64 i686 job.
I fixed cmake, autotools and msys2 actions. Still trying to fix the unittest-disablelegacy action.
I fixed the unittest-disablelegacy action as well.