search

tock / mirrorcheck

Periodically Check Mirrors of Tock-related Files
Apache License 2.0
0 stars 0 forks source link

`test-mirrors` has encountered an error #16

Closed github-actions[bot] closed 1 week ago

github-actions[bot] commented 1 month ago

Request Error for URL

Details:

Error message:

HTTPSConnectionPool(host='www.cs.virginia.edu', port=443): Max retries exceeded with url: /~bjc8c/archive/gcc-riscv64-unknown-elf-8.3.0-ubuntu.zip (Caused by SSLError(SSLError(1, '[SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1007)')))

Request Error for URL

Details:

Error message:

HTTPSConnectionPool(host='www.cs.virginia.edu', port=443): Max retries exceeded with url: /~bjc8c/archive/tock/libtock-libc++-10.5.0.zip (Caused by SSLError(SSLError(1, '[SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1007)')))

Request Error for URL

Details:

Error message:

HTTPSConnectionPool(host='www.cs.virginia.edu', port=443): Max retries exceeded with url: /~bjc8c/archive/tock/libtock-libc++-12.3.0.zip (Caused by SSLError(SSLError(1, '[SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1007)')))

Request Error for URL

Details:

Error message:

HTTPSConnectionPool(host='www.cs.virginia.edu', port=443): Max retries exceeded with url: /~bjc8c/archive/tock/libtock-libc++-13.2.0.zip (Caused by SSLError(SSLError(1, '[SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1007)')))

Request Error for URL

Details:

Error message:

HTTPSConnectionPool(host='www.cs.virginia.edu', port=443): Max retries exceeded with url: /~bjc8c/archive/tock/libtock-newlib-4.2.0.20211231.zip (Caused by SSLError(SSLError(1, '[SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1007)')))

Request Error for URL

Details:

Error message:

HTTPSConnectionPool(host='www.cs.virginia.edu', port=443): Max retries exceeded with url: /~bjc8c/archive/tock/libtock-newlib-4.3.0.20230120.zip (Caused by SSLError(SSLError(1, '[SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1007)')))
lschuermann commented 1 month ago

@bradjc I can confirm this issue on my local client.

lschuermann commented 1 week ago

Seems to be fixed now.