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

Suppress a textual output (except for logging) in all the tests #31

Open
pgagarinov opened this issue Oct 15, 2015 · 1 comment
Open

Comments

@pgagarinov
Copy link
Member

Tests should run silently, yet some of them produce a lot of console output for no reason

dimamih added a commit that referenced this issue Feb 14, 2018
… output of evalc-function calls to logger.info
dimamih added a commit that referenced this issue Feb 16, 2018
… output of evalc-function calls to logger.info
irublev added a commit that referenced this issue Feb 23, 2018
Enhancement: tests checking demo snippets work now in a separate worker, the snippet with s_install is excluded from checking by tests
irublev pushed a commit that referenced this issue Feb 23, 2018
… output of evalc-function calls to logger.info
irublev pushed a commit that referenced this issue Feb 23, 2018
… output of evalc-function calls to logger.info
irublev added a commit that referenced this issue Feb 23, 2018
Enhancement: tests checking demo snippets work now in a separate worker, the snippet with s_install is excluded from checking by tests
irublev pushed a commit that referenced this issue Feb 24, 2018
…gger.info

issue #31: added patch to change default test configuration, directed output of evalc-function calls to logger.info

issue #31: fixed errors appeared after rebase

issue #31: added tests from mxberry-core, fixed appeared errors

issue #31: directed output of strucdisp-function calls to logger.info
irublev added a commit that referenced this issue Feb 24, 2018
Enhancement: tests checking demo snippets work now in a separate worker, the snippet with s_install is excluded from checking by tests
dimamih added a commit that referenced this issue Feb 24, 2018
BugFix: fixed files that caused fail in MCodeQualityUtilTC/testTouch
dimamih added a commit that referenced this issue Feb 25, 2018
Enhancement: directed output of feval-function call to logger.info
dimamih added a commit that referenced this issue Feb 26, 2018
Enhancement: directed output of picgen tests to logger.info
dimamih added a commit that referenced this issue Feb 26, 2018
Enhancement: part of configuration is not written both on console and in the log file
irublev pushed a commit that referenced this issue Feb 26, 2018
…gger.info

issue #31: added patch to change default test configuration, directed output of evalc-function calls to logger.info

issue #31: fixed errors appeared after rebase

issue #31: added tests from mxberry-core, fixed appeared errors

issue #31: directed output of strucdisp-function calls to logger.info
irublev added a commit that referenced this issue Feb 26, 2018
Enhancement: tests checking demo snippets work now in a separate worker, the snippet with s_install is excluded from checking by tests
irublev pushed a commit that referenced this issue Feb 26, 2018
BugFix: fixed files that caused fail in MCodeQualityUtilTC/testTouch
irublev pushed a commit that referenced this issue Feb 26, 2018
Enhancement: directed output of feval-function call to logger.info
irublev pushed a commit that referenced this issue Feb 26, 2018
Enhancement: directed output of picgen tests to logger.info
irublev pushed a commit that referenced this issue Feb 26, 2018
Enhancement: part of configuration is not written both on console and in the log file
@irublev
Copy link
Contributor

irublev commented Feb 27, 2018

What remains to do:

  1. to make gras.gen.ProgressCmdDisplayer to be silent in the test configuration (it may be done by calling log4j logger instead of fprintf, but it is necessary to investigate how to be with printing of \b backspace symbols)
  2. to perform a fine tuning of configuration to be sure that the info written in the log file is sufficient for understanding what passes in the tests, current test configuration gives logs not fully coinciding with the old logs, the main reason for this is that logs for demo snippets are launched now in a separate worker
  3. because parallel toolbox is necessary for checking demo snippets, it is necessary to include the framework to do this in the toolbox

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants