Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[DevOps] Merged HTML test report of a fork PR includes runner files named in its blob reports

Cerrado
#43,702 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@yury-s ya está trabajando en esto.

Desde el 27/10/2026.

  • #43693 de @yury-s — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
github-actions, playwright, typescript

Línea de trabajo

Read .github/workflows/create_test_report.yml and .github/workflows/merge.config.ts to trace how fork PR blob reports reach the HTML reporter, then inspect packages/playwright/src/reporters/html.ts, especially createSnippets and createErrorCodeframe. Reproduce with blob data whose location.file points outside the extracted blob folder. Done means the merged HTML report includes only blob report data and does not read runner files; linked PR #43693 is already open.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Version

main (1.65.0-next)

Steps to reproduce
  1. In a pull request from a fork, make the test run upload a blob report in which a test step or an error has a location.file outside the checkout, for example an absolute path on the runner.
  2. When tests 1 completes, the "Publish Test Results" workflow (.github/workflows/create_test_report.yml) downloads the blob reports, runs merge-reports with the html reporter (.github/workflows/merge.config.ts), and uploads playwright-report/index.html as an artifact.
Expected behavior

The published report contains only data from the blob reports.

Actual behavior

While it builds the report, the html reporter reads files on the runner at the locations from the blob: createSnippets for step locations and createErrorCodeframe for error locations (packages/playwright/src/reporters/html.ts). The text of those files goes into the uploaded report. A fork PR controls its blob reports, so it chooses which runner files are read.

Attachment paths are not affected: merge limits them to the extracted blob folder. The markdown report reads no files.

Lenguaje dominante
TypeScript
Estrellas
98.5k
Forks
6.7k
Merge medio
15 h 42 min
PR fusionados (30 d)
313

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/playwright

Todos los issues de microsoft/playwright

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.