Skip to content

Merge remote-tracking branch 'origin/features/#618-create-interface-t… #2217

Merge remote-tracking branch 'origin/features/#618-create-interface-t…

Merge remote-tracking branch 'origin/features/#618-create-interface-t… #2217

Triggered via push April 20, 2026 16:57
Status Failure
Total duration 1h 9m 25s
Artifacts
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

4 errors, 6 warnings, and 3 notices
basic at py3.10 on windows-latest
The process 'C:\Users\runneradmin\miniconda3\condabin\conda.bat' failed with exit code 1
basic at py3.10 on ubuntu-latest
Process completed with exit code 1.
basic at py3.11 on ubuntu-latest
Process completed with exit code 1.
coverage at py3.12 on ubuntu-latest
Process completed with exit code 1.
basic at py3.10 on windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: conda-incubator/setup-miniconda@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
basic at py3.10 on windows-latest
CondaEnvException: Pip failed
basic at py3.10 on windows-latest
Pip subprocess error: ERROR: Exception: Traceback (most recent call last): File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\site-packages\pip\_vendor\urllib3\response.py", line 438, in _error_catcher yield File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\site-packages\pip\_vendor\urllib3\response.py", line 561, in read data = self._fp_read(amt) if not fp_closed else b"" File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\site-packages\pip\_vendor\urllib3\response.py", line 527, in _fp_read return self._fp.read(amt) if amt is not None else self._fp.read() File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\site-packages\pip\_vendor\cachecontrol\filewrapper.py", line 100, in read data: bytes = self.__fp.read(amt) File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\http\client.py", line 471, in read s = self.fp.read(amt) File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\socket.py", line 717, in readinto return self._sock.recv_into(b) File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\ssl.py", line 1307, in recv_into return self.read(nbytes, buffer) File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\ssl.py", line 1163, in read return self._sslobj.read(len, buffer) ssl.SSLError: [SSL] record layer failure (_ssl.c:2588) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\site-packages\pip\_internal\cli\base_command.py", line 107, in _run_wrapper status = _inner_run() File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\site-packages\pip\_internal\cli\base_command.py", line 98, in _inner_run return self.run(options, args) File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\site-packages\pip\_internal\cli\req_command.py", line 96, in wrapper return func(self, options, args) File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\site-packages\pip\_internal\commands\install.py", line 419, in run preparer.prepare_linked_requirements_more( File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\site-packages\pip\_internal\operations\prepare.py", line 569, in prepare_linked_requirements_more self._complete_partial_requirements( File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\site-packages\pip\_internal\operations\prepare.py", line 478, in _complete_partial_requirements for link, (filepath, _) in batch_download: File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\site-packages\pip\_internal\network\download.py", line 183, in batch filepath, content_type = self(link, location) File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\site-packages\pip\_internal\network\download.py", line 194, in __call__ self._process_response(download, resp) File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\site-packages\pip\_internal\network\download.py", line 211, in _process_response for chunk in chunks: File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\site-packages\pip\_internal\cli\progress_bars.py", line 69, in _rich_download_progress_bar for chunk in iterable: File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\site-packages\pip\_internal\network\utils.py", line 65, in response_chunks for chunk in response.raw.stream( File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\site-packages\pip\_vendor\urllib3\response.py", line 622, in stream data = self.read(amt=amt, decode_content=decode_content) File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\site-packages\pip\_vendor\urllib3\response.py", line 560, in read with self._error_catcher(): File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\contextlib.py", line 153, in __exit__ self.gen.throw(typ, value, traceback) File "C:\Users\runneradmin\miniconda3\envs\edisgo_env\lib\site-packages\pip\_vendor\urllib3\response.py", line 449,
basic at py3.10 on ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: julia-actions/setup-julia@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
basic at py3.11 on ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: julia-actions/setup-julia@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage at py3.12 on ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: julia-actions/setup-julia@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
basic at py3.10 on ubuntu-latest
[setup-julia] If you are testing 1.6 as a Long Term Support (lts) version, consider using the new "lts" version specifier instead of "1.6" explicitly, which will automatically resolve the current lts.
basic at py3.11 on ubuntu-latest
[setup-julia] If you are testing 1.6 as a Long Term Support (lts) version, consider using the new "lts" version specifier instead of "1.6" explicitly, which will automatically resolve the current lts.
coverage at py3.12 on ubuntu-latest
[setup-julia] If you are testing 1.6 as a Long Term Support (lts) version, consider using the new "lts" version specifier instead of "1.6" explicitly, which will automatically resolve the current lts.