stupid mistake #671
Annotations
21 errors and 15 warnings
build (ubuntu-latest, 3.11)
Process completed with exit code 1.
|
build (ubuntu-latest, 3.10)
Process completed with exit code 1.
|
build (ubuntu-latest, 3.9)
Process completed with exit code 1.
|
build (windows-latest, 3.11)
The job running on runner GitHub Actions 19 has exceeded the maximum execution time of 360 minutes.
|
build (windows-latest, 3.11)
The operation was canceled.
|
build (windows-latest, 3.10)
The job running on runner GitHub Actions 15 has exceeded the maximum execution time of 360 minutes.
|
build (windows-latest, 3.10)
The operation was canceled.
|
build (windows-latest, 3.9)
The job running on runner GitHub Actions 14 has exceeded the maximum execution time of 360 minutes.
|
build (windows-latest, 3.9)
The operation was canceled.
|
build (macos-13, 3.10)
The job running on runner GitHub Actions 9 has exceeded the maximum execution time of 360 minutes.
|
build (macos-13, 3.10)
The operation was canceled.
|
build (macos-latest, 3.11)
The job running on runner GitHub Actions 1 has exceeded the maximum execution time of 360 minutes.
|
build (macos-latest, 3.11)
The operation was canceled.
|
build (macos-13, 3.9)
The job running on runner GitHub Actions 8 has exceeded the maximum execution time of 360 minutes.
|
build (macos-13, 3.9)
The operation was canceled.
|
build (macos-latest, 3.10)
The job running on runner GitHub Actions 6 has exceeded the maximum execution time of 360 minutes.
|
build (macos-latest, 3.10)
The operation was canceled.
|
build (macos-13, 3.11)
The job running on runner GitHub Actions 16 has exceeded the maximum execution time of 360 minutes.
|
build (macos-13, 3.11)
The operation was canceled.
|
build (macos-latest, 3.9)
The job running on runner GitHub Actions 12 has exceeded the maximum execution time of 360 minutes.
|
build (macos-latest, 3.9)
The operation was canceled.
|
build (ubuntu-latest, 3.11)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
build (ubuntu-latest, 3.11)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
|
build (ubuntu-latest, 3.10)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
build (ubuntu-latest, 3.10)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
|
build (ubuntu-latest, 3.9)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
build (ubuntu-latest, 3.9)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
|
build (windows-latest, 3.11)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
|
build (windows-latest, 3.10)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
|
build (windows-latest, 3.9)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
|
build (macos-13, 3.10)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
|
build (macos-latest, 3.11)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
|
build (macos-13, 3.9)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
|
build (macos-latest, 3.10)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
|
build (macos-13, 3.11)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
|
build (macos-latest, 3.9)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
|