Skip to content

fix: init subclass docstring formatting for iterators #1754

fix: init subclass docstring formatting for iterators

fix: init subclass docstring formatting for iterators #1754

Triggered via pull request November 30, 2024 19:55
Status Failure
Total duration 4m 17s
Artifacts

pytest.yaml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

63 errors
test (windows-latest, 3.8)
Event loop is closed
test (windows-latest, 3.8)
Event loop is closed
test (windows-latest, 3.8)
Event loop is closed
test (windows-latest, 3.8)
Event loop is closed
test (windows-latest, 3.8)
Event loop is closed
test (windows-latest, 3.8)
Process completed with exit code 1.
test (windows-latest, 3.10)
Process completed with exit code 1.
test (ubuntu-latest, 3.10)
Process completed with exit code 134.
test (macos-latest, 3.10)
Process completed with exit code 134.
test (ubuntu-latest, 3.9)
Process completed with exit code 134.
test (ubuntu-latest, 3.8)
Event loop is closed
test (ubuntu-latest, 3.8)
Event loop is closed
test (ubuntu-latest, 3.8)
Event loop is closed
test (ubuntu-latest, 3.8)
Event loop is closed
test (ubuntu-latest, 3.8)
Event loop is closed
test (ubuntu-latest, 3.8)
Event loop is closed
test (ubuntu-latest, 3.8)
Event loop is closed
test (ubuntu-latest, 3.8)
Process completed with exit code 134.
test (ubuntu-latest, 3.12)
Event loop is closed
test (ubuntu-latest, 3.12)
Event loop is closed
test (ubuntu-latest, 3.12)
Event loop is closed
test (ubuntu-latest, 3.12)
Event loop is closed
test (ubuntu-latest, 3.12)
Event loop is closed
test (ubuntu-latest, 3.12)
Event loop is closed
test (ubuntu-latest, 3.12)
Event loop is closed
test (ubuntu-latest, 3.12)
Event loop is closed
test (ubuntu-latest, 3.12)
Event loop is closed
test (ubuntu-latest, 3.12)
Process completed with exit code 134.
test (ubuntu-latest, 3.11)
Event loop is closed
test (ubuntu-latest, 3.11)
Event loop is closed
test (ubuntu-latest, 3.11)
Event loop is closed
test (ubuntu-latest, 3.11)
Event loop is closed
test (ubuntu-latest, 3.11)
Event loop is closed
test (ubuntu-latest, 3.11)
Event loop is closed
test (ubuntu-latest, 3.11)
Event loop is closed
test (ubuntu-latest, 3.11)
Event loop is closed
test (ubuntu-latest, 3.11)
Event loop is closed
test (ubuntu-latest, 3.11)
Process completed with exit code 134.
test (windows-latest, 3.12)
Event loop is closed
test (windows-latest, 3.12)
Process completed with exit code 1.
test (windows-latest, 3.11)
Event loop is closed
test (windows-latest, 3.11)
Process completed with exit code 1.
test (macos-latest, 3.11)
Event loop is closed
test (macos-latest, 3.11)
Event loop is closed
test (macos-latest, 3.11)
Event loop is closed
test (macos-latest, 3.11)
Event loop is closed
test (macos-latest, 3.11)
Event loop is closed
test (macos-latest, 3.11)
Event loop is closed
test (macos-latest, 3.11)
Event loop is closed
test (macos-latest, 3.11)
Event loop is closed
test (macos-latest, 3.11)
Event loop is closed
test (macos-latest, 3.11)
Process completed with exit code 134.
test (macos-latest, 3.12)
Event loop is closed
test (macos-latest, 3.12)
Event loop is closed
test (macos-latest, 3.12)
Event loop is closed
test (macos-latest, 3.12)
Event loop is closed
test (macos-latest, 3.12)
Event loop is closed
test (macos-latest, 3.12)
Event loop is closed
test (macos-latest, 3.12)
Event loop is closed
test (macos-latest, 3.12)
Event loop is closed
test (macos-latest, 3.12)
Event loop is closed
test (macos-latest, 3.12)
Process completed with exit code 134.
test (windows-latest, 3.9)
Process completed with exit code 1.