astral-sh/uv

Show tracing output on test failure

Open

#8,351 opened on Oct 18, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (3,111 forks)batch import
help wantedinternaltesting

Repository metrics

Stars
 (84,934 stars)
PR merge metrics
 (Avg merge 6d 16h) (222 merged PRs in 30d)

Description

In the vein of https://github.com/astral-sh/uv/pull/8349, it's nice to have more information from the child process when a test fails. Right now, if you turn tracing on it ends up in the snapshot and breaks the test. We should have tracing on by default, but exclude it from the snapshots and display it on failure. This could be implemented with something like a UV_LOG_FILE option we pass to the child process then read from on failure.

Contributor guide

Research direction
Examine the linked PR #8349 for a similar approach. Investigate how tracing is currently configured in uv's tests, particularly the test runner and snapshot handling. Look for existing environment variables like UV LOG FILE or similar patterns in the codebase. The implementation would involve modifying the test harness to enable tracing with a separate output channel (e.g., log file) and displaying its contents on failure without affecting snapshots.
Tech stack
rustpython
Domain
testingdeveloper experience
Issue type
Feature
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.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Rusttracing crateuv test infrastructure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60