Skip to content

fix: MeshDoctor: ensure consistent node numbering between 2D element and 3D faces #942

fix: MeshDoctor: ensure consistent node numbering between 2D element and 3D faces

fix: MeshDoctor: ensure consistent node numbering between 2D element and 3D faces #942

Triggered via pull request February 3, 2026 18:03
Status Cancelled
Total duration 10m 46s
Artifacts

python-package.yml

on: pull_request
semantic_pull_request
5s
semantic_pull_request
check_draft
4s
check_draft
Matrix: build
check_integration_label
0s
check_integration_label
check_force_integration_label
0s
check_force_integration_label
Check GEOS Integration Required
0s
Check GEOS Integration Required
Dispatch cases of GEOS CI
0s
Dispatch cases of GEOS CI
GEOS Integration Test  /  Determine GEOS TPL Tag
GEOS Integration Test / Determine GEOS TPL Tag
GEOS Integration Test  /  Test geosPythonPackages Integration with GEOS
GEOS Integration Test / Test geosPythonPackages Integration with GEOS
GEOS Integration Test  /  GEOS Integration Test Summary
GEOS Integration Test / GEOS Integration Test Summary
Final CI Validation
3s
Final CI Validation
Fit to window
Zoom out
Zoom in

Annotations

8 errors
build (3.10, mesh-doctor)
Process completed with exit code 1.
build (3.11, hdf5-wrapper)
Canceling since a higher priority waiting request for geosPythonPackages CI-refs/pull/219/merge exists
build (3.11, hdf5-wrapper)
The operation was canceled.
build (3.11, mesh-doctor)
Canceling since a higher priority waiting request for geosPythonPackages CI-refs/pull/219/merge exists
build (3.11, mesh-doctor)
The operation was canceled.
build (3.11, geos-trame)
Canceling since a higher priority waiting request for geosPythonPackages CI-refs/pull/219/merge exists
build (3.11, geos-trame)
The operation was canceled.
geosPythonPackages CI
Canceling since a higher priority waiting request for geosPythonPackages CI-refs/pull/219/merge exists