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.

Sign up for GitHub

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

Jump to bottom

tests: log level change on python 3.7 breaks log capture #1269

Closed
ghost opened this issue Jul 10, 2018 · 3 comments
Closed

tests: log level change on python 3.7 breaks log capture #1269

ghost opened this issue Jul 10, 2018 · 3 comments
Labels
bug Indicates an unexpected problem or unintended behavior component: core
Milestone
1.1.1

Comments

@ghost
Copy link

ghost commented Jul 10, 2018

In the test which sets the log level to DEBUG the actual (captured) logs only contain the level INFO.

See also the failed test result on Fedora Rawhide:
https://build.opensuse.org/package/live_build_log/home:sebix:intelmq:unstable/intelmq/Fedora_Rawhide/x86_64
@ghost ghost added bug Indicates an unexpected problem or unintended behavior component: core labels Jul 10, 2018
@ghost ghost added this to the 1.1.0 milestone Jul 10, 2018
@ghost ghost modified the milestones: 1.1.0, 1.1.1 Sep 5, 2018
@ghost
Copy link
Author

ghost commented Oct 3, 2018

Also happens on Debian testing now

@ghost
Copy link
Author

ghost commented Oct 15, 2018

Probably a problem of unittest.mock and then only a problem for the tests.

@ghost
Copy link
Author

ghost commented Oct 16, 2018

Seems to be a problem when creating copies of the logger -> in the tests only. So skipping the test for now.

@ghost ghost changed the title debug log level on python 3.7 not applied tests: log level change on python 3.7 breaks log capture Oct 16, 2018
@ghost ghost closed this as completed in 3381eb3 Oct 16, 2018
@ghost ghost mentioned this issue Jun 6, 2019
Closed
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Indicates an unexpected problem or unintended behavior component: core
Projects
None yet
Milestone
1.1.1
Development

No branches or pull requests
0 participants