Skip to content

Added velocity (and general) field orthogonal expansions to EXP and pyEXP [WIP] #190

Added velocity (and general) field orthogonal expansions to EXP and pyEXP [WIP]

Added velocity (and general) field orthogonal expansions to EXP and pyEXP [WIP] #190

Triggered via pull request December 29, 2023 15:00
Status Failure
Total duration 9s
Artifacts

build.yml

on: pull_request
Matrix: Test Full EXP Build
Matrix: Test pyEXP Build
Fit to window
Zoom out
Zoom in

Annotations

8 errors
Test Full EXP Build (macos-latest, gcc)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.
Test Full EXP Build (ubuntu-latest, gcc)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.
Test pyEXP Build (ubuntu-latest, gcc)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.
Test Full EXP Build (macos-latest, mpicc)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.
Test Full EXP Build (ubuntu-latest, mpicc)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.
Test pyEXP Build (macos-latest, gcc)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.
Test pyEXP Build (ubuntu-latest, mpicc)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.
Test pyEXP Build (macos-latest, mpicc)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.