feat: add thread-safe progress meter #314
MarcMushAnnotations
24 errors, 8 warnings, and 6 notices
|
test (1.6, ubuntu-latest, x64, 1)
Process completed with exit code 1.
|
|
test (1.6, ubuntu-latest, x64, 2)
Process completed with exit code 1.
|
|
test (1, ubuntu-latest, x64, 1)
Process completed with exit code 1.
|
|
test (1, ubuntu-latest, x64, 2)
Process completed with exit code 1.
|
|
test (nightly, ubuntu-latest, x64, 1)
Process completed with exit code 1.
|
|
test (1.11-nightly, ubuntu-latest, x64, 2)
Process completed with exit code 1.
|
|
test (nightly, ubuntu-latest, x64, 2)
Process completed with exit code 1.
|
|
test (1.11-nightly, ubuntu-latest, x64, 1)
Process completed with exit code 1.
|
|
test (1.6, macOS-latest, x64, 2)
Process completed with exit code 1.
|
|
test (1.6, macOS-latest, x64, 1)
Process completed with exit code 1.
|
|
test (1, windows-latest, x64, 1)
Process completed with exit code 1.
|
|
test (1.11-nightly, windows-latest, x64, 1)
Process completed with exit code 1.
|
|
test (nightly, windows-latest, x64, 2)
Process completed with exit code 1.
|
|
test (1, windows-latest, x64, 2)
Process completed with exit code 1.
|
|
test (1.11-nightly, macOS-latest, x64, 1)
Process completed with exit code 1.
|
|
test (1.11-nightly, windows-latest, x64, 2)
Process completed with exit code 1.
|
|
test (1.11-nightly, macOS-latest, x64, 2)
Process completed with exit code 1.
|
|
test (1, macOS-latest, x64, 1)
Process completed with exit code 1.
|
|
test (nightly, windows-latest, x64, 1)
Process completed with exit code 1.
|
|
test (1, macOS-latest, x64, 2)
Process completed with exit code 1.
|
|
test (nightly, macOS-latest, x64, 1)
Process completed with exit code 1.
|
|
test (nightly, macOS-latest, x64, 2)
Process completed with exit code 1.
|
|
test (1.6, windows-latest, x64, 2)
Process completed with exit code 1.
|
|
test (1.6, windows-latest, x64, 1)
Process completed with exit code 1.
|
|
test (1.6, macOS-latest, x64, 2)
[setup-julia] x64 arch has been requested on a macOS runner that has an arm64 (Apple Silicon) architecture. You may have meant to use the "aarch64" arch instead (or left it unspecified for the correct default).
|
|
test (1.6, macOS-latest, x64, 1)
[setup-julia] x64 arch has been requested on a macOS runner that has an arm64 (Apple Silicon) architecture. You may have meant to use the "aarch64" arch instead (or left it unspecified for the correct default).
|
|
test (1.11-nightly, macOS-latest, x64, 1)
[setup-julia] x64 arch has been requested on a macOS runner that has an arm64 (Apple Silicon) architecture. You may have meant to use the "aarch64" arch instead (or left it unspecified for the correct default).
|
|
test (1.11-nightly, macOS-latest, x64, 2)
[setup-julia] x64 arch has been requested on a macOS runner that has an arm64 (Apple Silicon) architecture. You may have meant to use the "aarch64" arch instead (or left it unspecified for the correct default).
|
|
test (1, macOS-latest, x64, 1)
[setup-julia] x64 arch has been requested on a macOS runner that has an arm64 (Apple Silicon) architecture. You may have meant to use the "aarch64" arch instead (or left it unspecified for the correct default).
|
|
test (1, macOS-latest, x64, 2)
[setup-julia] x64 arch has been requested on a macOS runner that has an arm64 (Apple Silicon) architecture. You may have meant to use the "aarch64" arch instead (or left it unspecified for the correct default).
|
|
test (nightly, macOS-latest, x64, 1)
[setup-julia] x64 arch has been requested on a macOS runner that has an arm64 (Apple Silicon) architecture. You may have meant to use the "aarch64" arch instead (or left it unspecified for the correct default).
|
|
test (nightly, macOS-latest, x64, 2)
[setup-julia] x64 arch has been requested on a macOS runner that has an arm64 (Apple Silicon) architecture. You may have meant to use the "aarch64" arch instead (or left it unspecified for the correct default).
|
|
test (1.6, ubuntu-latest, x64, 1)
[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.
|
|
test (1.6, ubuntu-latest, x64, 2)
[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.
|
|
test (1.6, macOS-latest, x64, 2)
[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.
|
|
test (1.6, macOS-latest, x64, 1)
[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.
|
|
test (1.6, windows-latest, x64, 2)
[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.
|
|
test (1.6, windows-latest, x64, 1)
[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.
|