https://bugzilla.redhat.com/show_bug.cgi?id=1758139
Bug ID: 1758139 Summary: Modify logging at Gluster regression tests Product: GlusterFS Version: 7 Status: NEW Component: project-infrastructure Assignee: b...@gluster.org Reporter: bsaso...@redhat.com CC: b...@gluster.org, gluster-infra@gluster.org Target Milestone: --- Classification: Community Description of problem: We're currently investigation the affect of Gluster logging on runtime. In an effort to reduce regression testing runtime, a suggestion came up to start the run with no logging (GF_LOG_NONE) and if a test fails, modify the logging level to debug (GF_LOG_DEBUG), retry the test and then lower the logging level again to no logging (GF_LOG_NONE). This requires changes to the Jenkins script that runs regression tests (by command "run full regression"). Version-Release number of selected component (if applicable): How reproducible: Run regression using "run full regression" command on gerrit Steps to Reproduce: 1. 2. 3. Actual results: Regression testing takes over 4 hours Expected results: Trying to reduce regression testing time Additional info: -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra