search

jurplel / install-qt-action

Install Qt on your Github Actions workflows with just one simple action
MIT License
446 stars 78 forks source link

"HTTPSConnectionPool: Read timed out" happening frequently on Win and Mac on v3.3.0 #203

Closed brunoalr closed 10 months ago

brunoalr commented 11 months ago

Hi there! Thanks a lot for this amazing project :)

I noticed that using install-qt-action with all default options started to give similar timeout errors to the one below very often when running on Windows and Mac:

Download of 5.15.2-0-202011130602qttools-Windows-Windows_10-MSVC2019-Windows-Windows_10-X86_64.7z has error: HTTPSConnectionPool(host='qt.mirror.constant.com', port=443): Read timed out.

More examples here: https://github.com/OpenImageDebugger/OpenImageDebugger/actions/runs/5835997834/job/15828667473?pr=94 Workflow: https://github.com/OpenImageDebugger/OpenImageDebugger/blob/bdec4347a075e9fd33fe6b0ce61a69286b4ce567/.github/workflows/build.yml#L44

This also happened in the test pipeline of v3.3.0 hosted in this very repo: https://github.com/jurplel/install-qt-action/actions/runs/5767308400/job/15636781547#step:6:625

I mitigated the issue by enabling caching and re-running my builds until the installation succeeded.

Is this a known issue?

stuart-auterion commented 11 months ago

I am experiencing the same issue. We run our builds on Linux, but the error message is the same. I am also able to mitigate it by simply re-running the build.

pzhlkj6612 commented 11 months ago

Hello. I guess there is something wrong with Qt's HTTP server. Specifying --base <mirror_server_url> in the extra: field of this action might be helpful.

I didn't test it, though.

Available mirror servers list: https://download.qt.io/static/mirrorlist/

jurplel commented 10 months ago

Closed, feel free to reopen

dkfellows commented 4 months ago

Switching which mirror was being used (away from the default, which was always Constant Hosting for my workflows) solved the problem for me (with Qt v6.6.1; it doesn't appear to be version-dependent). Or at least made it go away. Thank you, @pzhlkj6612!