tests

Enable support for cython 3 #228

Triggered via pull request September 23, 2023 12:17

chrhansk

opened #227

chrhansk:feature-cython3

Status Failure

Total duration 10m 29s

Artifacts –

This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

tests.yml

on: pull_request

Matrix: Build and run tests

Annotations

32 errors and 32 warnings

Build and run tests (ubuntu-latest, 3.9, 3.13)

Process completed with exit code 139.

Build and run tests (ubuntu-latest, 3.8, 3.14)

Process completed with exit code 139.

Build and run tests (ubuntu-latest, 3.10, 3.14)

Process completed with exit code 139.

Build and run tests (ubuntu-latest, 3.9, 3.14)

Process completed with exit code 139.

Build and run tests (ubuntu-latest, 3.10, 3.13)

Process completed with exit code 139.

Build and run tests (ubuntu-latest, 3.8, 3.13)

Process completed with exit code 139.

Build and run tests (ubuntu-latest, 3.11, 3.14)

Process completed with exit code 139.

Build and run tests (ubuntu-latest, 3.11, 3.13)

Process completed with exit code 139.

Build and run tests (ubuntu-latest, 3.11, 3.12)

Process completed with exit code 139.

Build and run tests (ubuntu-latest, 3.8, 3.12)

Process completed with exit code 135.

Build and run tests (ubuntu-latest, 3.10, 3.12)

Process completed with exit code 139.

Build and run tests (ubuntu-latest, 3.9, 3.12)

Process completed with exit code 139.

Build and run tests (macos-latest, 3.10, 3.13)

Process completed with exit code 139.

Build and run tests (macos-latest, 3.11, 3.14)

Process completed with exit code 139.

Build and run tests (macos-latest, 3.11, 3.12)

Process completed with exit code 139.

Build and run tests (macos-latest, 3.11, 3.13)

Process completed with exit code 139.

Build and run tests (macos-latest, 3.10, 3.12)

Process completed with exit code 139.

Build and run tests (windows-latest, 3.10, 3.13)

Process completed with exit code 139.

Build and run tests (macos-latest, 3.10, 3.14)

Process completed with exit code 139.

Build and run tests (windows-latest, 3.8, 3.13)

Process completed with exit code 139.

Build and run tests (macos-latest, 3.8, 3.13)

Process completed with exit code 139.

Build and run tests (windows-latest, 3.9, 3.13)

Process completed with exit code 139.

Build and run tests (macos-latest, 3.8, 3.12)

Process completed with exit code 139.

Build and run tests (windows-latest, 3.10, 3.14)

Process completed with exit code 139.

Build and run tests (windows-latest, 3.8, 3.14)

Process completed with exit code 139.

Build and run tests (windows-latest, 3.11, 3.14)

Process completed with exit code 139.

Build and run tests (macos-latest, 3.8, 3.14)

Process completed with exit code 139.

Build and run tests (windows-latest, 3.11, 3.13)

Process completed with exit code 139.

Build and run tests (macos-latest, 3.9, 3.12)

Process completed with exit code 139.

Build and run tests (windows-latest, 3.9, 3.14)

Process completed with exit code 139.

Build and run tests (macos-latest, 3.9, 3.14)

Process completed with exit code 139.

Build and run tests (macos-latest, 3.9, 3.13)

Process completed with exit code 139.

Build and run tests (ubuntu-latest, 3.9, 3.13)