bowtie-json-schema/bowtie

Uncaught harness errors should cause non-zero exit statuses

Open

#809 opened on Feb 4, 2024

View on GitHub
 (19 comments) (0 reactions) (0 assignees)Python (76 forks)github user discovery
good first issue

Repository metrics

Stars
 (90 stars)
PR merge metrics
 (PR metrics pending)

Description

A bowtie suite or bowtie run execution treats test failures by still exiting with 0 exit code, as failures are part of Bowtie's "normal behavior" as a compliance checker.

However -- errors, particularly uncaught errors which should be being handled in the harness, are not, and should likely trigger nonzero exit status.

Note that as part of fixing this you may also need to check whether any existing harnesses have uncaught errors (and to catch them if so) -- otherwise Bowtie's own report generation will begin to fail.

Contributor guide

Research direction
Trace the exit code logic in bowtie suite and bowtie run commands to see where errors are not causing non zero exit codes. Also review harness code for potential uncaught errors.
Tech stack
python
Domain
clibackendtesting
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60