Skip to content
geosPythonPackages CI

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

Sign in to view logs

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

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

Triggered via pull request February 4, 2026 18:08
@bd713bd713
synchronize #219
fix/bd713/consistent2Delemm_3Dface
Status Cancelled
Total duration 48s
Artifacts –

python-package.yml

on: pull_request
semantic_pull_request
3s
semantic_pull_request
check_draft
3s
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
5s
Final CI Validation
Fit to window
Zoom out
Zoom in

Annotations

4 errors
build (3.10, geos-utils)
Canceling since a higher priority waiting request for geosPythonPackages CI-refs/pull/219/merge exists
build (3.10, geos-ats)
Canceling since a higher priority waiting request for geosPythonPackages CI-refs/pull/219/merge exists
build (3.10, geos-geomechanics)
Canceling since a higher priority waiting request for geosPythonPackages CI-refs/pull/219/merge exists
geosPythonPackages CI
Canceling since a higher priority waiting request for geosPythonPackages CI-refs/pull/219/merge exists