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

Print debug logs in CI #2903

Closed
ScottFreeCode opened this issue Jun 26, 2017 · 1 comment
Closed

Print debug logs in CI #2903

ScottFreeCode opened this issue Jun 26, 2017 · 1 comment
Labels
area: repository tooling concerning ease of contribution type: chore generally involving deps, tooling, configuration, etc.

Comments

@ScottFreeCode
Copy link
Contributor

In Node CI tests, we should consider setting DEBUG=mocha:* to get the debug logs, if it won't interfere too much with the reporter output (and if we can find a way to deactivate it for integration tests without breaking Node 0.10, see #2897).

In browser CI tests... I don't know, we are currently suppressing the debug module using the browsers entry in package.json; most likely we can't just stop doing that because debug might not support all the old browsers Mocha supports, but maybe we could selectively convince Browserify to not do it for the BUILDTMP build and activate mocha:* for debug logging in Karma?

Why is this worth looking into? I believe getting these logs in the browser runs will show us a message that is being suppressed about #2890.

@ScottFreeCode ScottFreeCode added type: chore generally involving deps, tooling, configuration, etc. status: accepting prs Mocha can use your help with this one! qa labels Jun 26, 2017
@ScottFreeCode ScottFreeCode changed the title Print debug in CI Print debug logs in CI Jun 26, 2017
@ScottFreeCode ScottFreeCode added the area: repository tooling concerning ease of contribution label Aug 25, 2017
@juergba juergba removed the status: accepting prs Mocha can use your help with this one! label May 6, 2021
@juergba
Copy link
Member

juergba commented May 6, 2021

This issue is inactive, oudated and IMO without any clear benefit, closing.

@juergba juergba closed this as completed May 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: repository tooling concerning ease of contribution type: chore generally involving deps, tooling, configuration, etc.
Projects
None yet
Development

No branches or pull requests

2 participants