-
Notifications
You must be signed in to change notification settings - Fork 64
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
intermittent failing logger test on circleci #433
Comments
Likely related: winstonjs/winston#1504. Winston 2/3 historically has a ton of problems with answering the question "have all logs been flushed?" Relevant: https://github.com/winstonjs/winston#awaiting-logs-to-be-written-in-winston (doesn't actually work with the File transport). It seems like there is already test coverage for Winston file writes in |
well, there are other cases, where we want to test the log output. so maybe a string based transport for winston would help here. |
Seems like that would make more sense imho. I assume you'd want an upstream change in |
I added a string based test logger here: ce67700 I would disable the common log tests here and wait until winstonjs/winston#1504 is fixed.
exactly. I suggest that we remove the winston dependency from helix-cli and only rely on helix-shared. so maybe create a string transport when passing |
I created adobe/helix-shared#33 |
Description
happens only on circle ci...sometimes:
Expected behavior
no errors.
The text was updated successfully, but these errors were encountered: