[Gluster-infra] [Bug 1758139] New: Modify logging at Gluster regression tests

bugzilla at redhat.com bugzilla at redhat.com
Thu Oct 3 11:42:19 UTC 2019


            Bug ID: 1758139
           Summary: Modify logging at Gluster regression tests
           Product: GlusterFS
           Version: 7
            Status: NEW
         Component: project-infrastructure
          Assignee: bugs at gluster.org
          Reporter: bsasonro at redhat.com
                CC: bugs at gluster.org, gluster-infra at 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:

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.

More information about the Gluster-infra mailing list