You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
** 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.
Describe the bug
Since upgrading to version
8.5.2
and subsequently8.5.3
the test runner is outputting errors in the GitHub pipeline console:The tests do appear to be passing however, according to the report:
Reproduction link
Unable to supply as this is a runner issue
Reproduction steps
No response
System
Additional context
No response
The text was updated successfully, but these errors were encountered: