"combineCoverage" logged in stdout, creating huge logs

Abierto
  • ¿Algo no está bien?
#652 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
cypress, docker, node.js, typescript
Área
testing-qa, tooling

Línea de trabajo

Comienza con el commit 8f6154a48ef9256e4d3b57a2387d59c046aba12 y sigue cómo se registra la tarea combineCoverage en cypress/logs y stdout. Reprodúcelo con Cypress 12.10.0, plugin 3.10.4 y la configuración de Docker de Debian; se considera terminado cuando las entradas grandes de combineCoverage ya no aparecen cuando la tarea usa log: false.

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

Descripción

E2E triaged type: enhancement

Logs and screenshots

Here's the end of the log for one of my tests (as stylized by Firefox):

Screenshot 2023-05-12 at 2 02 45 PM

Each of those "request combineCoverage" lines are huge.

Versions

  • What is this plugin's version? If this is NOT the latest released version can you try the latest version, please? 3.10.4
  • If the plugin worked before in version X, but stopped after upgrading to version Y, please try the released versions between X and Y to see where the breaking change was.
  • What is Cypress version? 12.10.0
  • What is your operating system? Debian, from Cypress Docker images
  • What is the shell? bash
  • What is the Node version? 16.17
  • What is the NPM version?
  • How do you instrument your application? Cypress does not instrument web application code, so you need to do it yourself. @cypress/instrument-cra
  • When running tests, if you open the web application in regular browser, and open DevTools, do you see window.__coverage__ object? Can you paste a screenshot?
  • Is there .nyc_output folder? Is there .nyc_output/out.json file. Is it empty? Can you paste at least part of it so we can see the keys and file paths?
  • Do you have any custom NYC settings in package.json (nyc object) or in other NYC config files 
      "nyc": {
"extends": "@istanbuljs/nyc-config-typescript",
"all": true,
"exclude": [
  "build/**",
  "coverage-cypress/**",
  "cypress/**",
  "**/__fixtures__/**",
  "**/__mocks__/**",
  "**/__tests__/**",
  "**/messages.{ts,js}",
  "**/*.story.*",
  "**/story.*",
  "**/*.d.ts"
],
"report-dir": "./coverage-cypress",
"temp-dir": "./coverage-cypress/.nyc_output",
"reporter": [
  "text-summary",
  "json",
  "html"
]
}
  • Do you run Cypress tests in a Docker container? Yes

Describe the bug

The combineCoverage task is logged (in both files saved to cypress/logs and to stdout), even though that task is run with { log: false} (see https://github.com/cypress-io/code-coverage/commit/8f6154a48ef9256e4d3b57a2387d59c046aba12e).

Link to the repo

Lenguaje dominante
TypeScript
Estrellas
440
Forks
114
Merge medio
42 min
PR fusionados (30 d)
19

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

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 cypress-io/code-coverage

Todos los issues de cypress-io/code-coverage

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.