Skip to content

Fixed potential crash when using uninitialized FEMappedValueMat3d. #186

Fixed potential crash when using uninitialized FEMappedValueMat3d.

Fixed potential crash when using uninitialized FEMappedValueMat3d. #186

Triggered via push September 20, 2024 16:41
Status Success
Total duration 15m 7s
Artifacts 5

linux-push.yml

on: push
call_workflow  /  Start self-hosted EC2 runner
3m 8s
call_workflow / Start self-hosted EC2 runner
call_workflow  /  Clone and build
3m 36s
call_workflow / Clone and build
call_workflow  /  Run test suite
4m 31s
call_workflow / Run test suite
call_workflow  /  Upload artifacts to repo
36s
call_workflow / Upload artifacts to repo
call_workflow  /  Publish to S3
38s
call_workflow / Publish to S3
call_workflow  /  Stop self-hosted EC2 runner
1m 46s
call_workflow / Stop self-hosted EC2 runner
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
call_workflow / Stop self-hosted EC2 runner
GitHub self-hosted runner removal error
call_workflow / Stop self-hosted EC2 runner
HttpError: Bad request - Runner "AWS-9067052738232559" is still running a job"

Artifacts

Produced during runtime
Name Size
FEBioChem-Linux-X64
119 KB
FEBioHeat-Linux-X64
53.3 KB
febio4-Linux-X64
47.8 MB
febio4-sdk-Linux-X64
50.2 MB
testsuite-Linux-X64-logs
11.2 MB