mesonbuild/meson

TAP implementation issue

Open

#6,810 opened on Mar 20, 2020

View on GitHub
 (2 comments) (2 reactions) (0 assignees)Python (4,978 stars) (1,465 forks)batch import
buggood first issuetest targets

Description

Describe the bug

The TAP protocol states: Any output line that is not a version, a plan, a test line, a diagnostic or a bail out is considered an “unknown” line. A TAP parser is required to not consider an unknown line as an error

Yet, the meson TAP parser does: yield self.Error('unexpected input at line %d' % (lineno,))

Contributor guide

Tech stack
python
Domain
testing
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
PythonTAP protocol
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85
Research direction
Locate the TAP parser in the meson repository (likely in mesonbuild/mesonbuild/tap.py or similar). The line `yield self.Error('unexpected input at line %d' % (lineno,))` should be replaced with a warning or a skipped line to comply with the TAP specification. Check for existing tests related to TAP parsing to verify the change. Consider adding a test case for unknown lines to ensure correct behavior.