Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Console errors in the Storybook test-runner #30472

Open
DanDeLuca opened this issue Feb 5, 2025 · 1 comment
Open

[Bug]: Console errors in the Storybook test-runner #30472

DanDeLuca opened this issue Feb 5, 2025 · 1 comment

Comments

@DanDeLuca
Copy link

Describe the bug

Since upgrading to version 8.5.2 and subsequently 8.5.3 the test runner is outputting errors in the GitHub pipeline console:

PASS browser: chromium ../../../tmp/791c8e78dec52614e7407c37b81a8e7e/components-nptile.test.js (9.434 s)
  ● Console

    console.log
      An error occurred in the following story, most likely because of a navigation: "Components / NpTile/With Long Title". Retrying...

      at Object.log (../../../tmp/791c8e78dec52614e7407c37b81a8e7e/components-nptile.test.js:112:19)

    console.log
      An error occurred in the following story, most likely because of a navigation: "Components / NpTile/Disabled". Retrying...

      at Object.log (../../../tmp/791c8e78dec52614e7407c37b81a8e7e/components-nptile.test.js:172:19)

The tests do appear to be passing however, according to the report:

Test Suites: 52 passed, 52 total
Tests:       227 passed, 227 total
Snapshots:   0 total
Time:        84.877 s
Ran all test suites.
[test-storybook] Cleaning up /tmp/0a06b7ea4f9918e03ffedd164cc92a0c

Reproduction link

Unable to supply as this is a runner issue

Reproduction steps

No response

System

System:
    OS: Linux 5.4 Ubuntu 20.04.6 LTS (Focal Fossa)
    CPU: (4) x64 Intel Xeon Processor (Cascadelake)
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 18.20.6 - /usr/bin/node
    npm: 9.9.4 - /usr/bin/npm <----- active
  npmPackages:
    @storybook/addon-a11y: ^8.5.2 => 8.2.10 
    @storybook/addon-essentials: ^8.5.2 => 8.5.2 
    @storybook/addon-interactions: ^8.5.2 => 8.5.2 
    @storybook/addon-links: ^8.5.2 => 8.5.2 
    @storybook/blocks: ^8.5.2 => 8.5.2 
    @storybook/manager-api: ^8.5.2 => 8.5.2 
    @storybook/test: ^8.5.2 => 8.5.2 
    @storybook/test-runner: ^0.21.0 => 0.21.0 
    @storybook/theming: ^8.5.2 => 8.5.2 
    @storybook/vue3: ^8.5.2 => 8.5.2 
    @storybook/vue3-vite: ^8.5.2 => 8.5.2 
    eslint-plugin-storybook: ^0.11.2 => 0.11.2 
    storybook: ^8.5.2 => 8.5.2

Additional context

No response

Copy link
Contributor

greptile-apps bot commented Feb 5, 2025

** Disclaimer** This information might be inaccurate, due to it being generated automatically
This appears to be expected behavior from the test-runner when dealing with navigation events. The console logs are informational messages indicating that the test-runner detected a navigation during story rendering and automatically retried the test. Since all tests are passing, these messages can be safely ignored.

If you want to suppress these messages, you can add the following to your test-runner config:

js testRunner: { silent: true }

About Greptile

This response provides a starting point for your research, not a precise solution.

Help us improve! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

Edit Issue Bot Settings · Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant