Always ensure consistency of new MPI datatypes #1402
Triggered via pull request
September 13, 2024 10:31
giordano
Status
Success
Total duration
20m 0s
Artifacts
–
UnitTests.yml
on: pull_request
Matrix: test-default
Matrix: test-intel-linux
Matrix: test-mpitrampoline-jll
Matrix: test-mpitrampoline-oneapi-linux
Matrix: test-mpitrampoline-system-apt
Matrix: test-openmpi-jll
Matrix: test-spack-mvapich
Matrix: test-system-apt
Matrix: test-system-brew
Matrix: test-system-msmpi
Annotations
16 errors and 10 notices
|
test-default (ubuntu-latest, 1, x64)
Process completed with exit code 1.
|
|
test-default (ubuntu-latest, 1.6, x64)
Process completed with exit code 1.
|
|
test-default (macos-14, aarch64, 1)
Process completed with exit code 1.
|
|
test-default (ubuntu-latest, 1.6, x86)
Process completed with exit code 1.
|
|
test-default (ubuntu-latest, 1, x86)
Process completed with exit code 1.
|
|
test-default (macos-13, 1.6, x64)
Process completed with exit code 1.
|
|
test-default (windows-latest, 1, x64)
Process completed with exit code 1.
|
|
test-default (macos-13, 1, x64)
Process completed with exit code 1.
|
|
test-default (ubuntu-latest, nightly, x64)
Process completed with exit code 1.
|
|
test-default (windows-latest, 1, x86)
Process completed with exit code 1.
|
|
test-default (windows-latest, nightly, x64)
Process completed with exit code 1.
|
|
test-default (ubuntu-latest, nightly, x86)
Process completed with exit code 1.
|
|
test-default (macos-13, nightly, x64)
Process completed with exit code 1.
|
|
test-default (windows-latest, nightly, x86)
Process completed with exit code 1.
|
|
test-default (windows-latest, 1.6, x64)
Process completed with exit code 1.
|
|
test-default (windows-latest, 1.6, x86)
Process completed with exit code 1.
|
|
test-openmpi-jll (ubuntu-latest, 1.6, x64)
[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-default (ubuntu-latest, 1.6, x64)
[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-default (ubuntu-latest, 1.6, x86)
[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-openmpi-jll (macos-13, 1.6, x64)
[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-default (macos-13, 1.6, x64)
[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-mpitrampoline-jll (ubuntu-latest, mpitrampoline, 1.6, x86)
[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-mpitrampoline-jll (macos-13, mpitrampoline, 1.6, x64)
[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-mpitrampoline-jll (ubuntu-latest, mpitrampoline, 1.6, x64)
[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-default (windows-latest, 1.6, x64)
[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-default (windows-latest, 1.6, x86)
[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.
|