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

More specific logging configuration in test environment #4230

Open
RitaMAllenCA opened this issue Aug 23, 2023 · 1 comment
Open

More specific logging configuration in test environment #4230

RitaMAllenCA opened this issue Aug 23, 2023 · 1 comment
Assignees
Labels
casper-test release blocker PR to be merged before releasing

Comments

@RitaMAllenCA
Copy link

The testing environment currently produces slightly spammy logs, due to too many unrelated crates producing log messages (e.g. hyper and other third-party crates). This is likely due to logging being setup with a catchall setting like RUST_LOG=debug.
To remedy, the default configuration should be something like RUST_LOG=warn,casper_node_launcher=debug,casper_node=debug
Furthermore it would be good to include the log configuration in the dumps created after tests. Since these settings are likely set in the systemd unit file, it would make sense to include said unit file in the archive.

@RitaMAllenCA
Copy link
Author

@sacherjj @cspramit I logged this here so we don't lose track. Sai does not appear to have an account. Where should SRE work be logged? Can you send me a link to the JIRA instance being used to track the work? I can certainly put the work in there. Please advise.

@RitaMAllenCA RitaMAllenCA added the release blocker PR to be merged before releasing label Aug 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
casper-test release blocker PR to be merged before releasing
Projects
None yet
Development

No branches or pull requests

3 participants