Skip to content

Add 'retail' to allowed use cases in sector validation #1726

Add 'retail' to allowed use cases in sector validation

Add 'retail' to allowed use cases in sector validation #1726

Triggered via push April 24, 2025 11:33
Status Cancelled
Total duration 29s
Artifacts
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 3 notices
basic at py3.9 on windows-latest
The operation was canceled.
basic at py3.9 on windows-latest
The run was canceled by @joda9.
basic at py3.10 on ubuntu-latest
The operation was canceled.
basic at py3.10 on ubuntu-latest
The run was canceled by @joda9.
coverage at py3.9 on ubuntu-latest
The operation was canceled.
coverage at py3.9 on ubuntu-latest
The run was canceled by @joda9.
basic at py3.11 on ubuntu-latest
The operation was canceled.
basic at py3.11 on ubuntu-latest
The run was canceled by @joda9.
Tests & Coverage
The run was canceled by @joda9.
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.
coverage at py3.9 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.