test / unit + widget + golden + a11y (push) Failing after 32s
test / integration_test (xvfb) (push) Has been skipped
test / bundle smoke (xvfb 5s) (push) Has been skipped
test / daemon subprocess + web WASM smoke (push) Has been skipped
test / dart doc (lib API) (push) Failing after 36s
forkpty was replaced by posix_openpt + posix_spawn in T-96, but the test tag, ci/test.sh segregation, and dart_test.yaml comment kept the forkpty name. The segregation is still required — verified the PTY tests fail under the flutter-test runner (the master fd doesn't reliably deliver output there) but pass under dart test — only the name was wrong. Rename to `pty` and correct the rationale comment. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
13 lines
703 B
YAML
13 lines
703 B
YAML
# Declares tags used by inline `test('...', tags: [...], ...)` calls so
|
|
# that `flutter test --exclude-tags <name>` and `dart test --tags <name>`
|
|
# both honor them. Undeclared tags are ignored by the runners, which
|
|
# silently breaks selective excludes.
|
|
tags:
|
|
# Native-PTY tests (posix_openpt + posix_spawn via Dart FFI). Must run
|
|
# under `dart test`, not `flutter test`: the flutter-test runner hosts a
|
|
# multi-threaded engine in which the PTY master fd doesn't reliably
|
|
# deliver output, so these flake there (verified). They are reliable
|
|
# under `dart test`. (Tag was historically named `forkpty`, before
|
|
# T-96 replaced forkpty with posix_spawn.) See `test/pty/session_test.dart`.
|
|
pty:
|