[GitHub] [geode] demery-pivotal opened a new pull request #7245: GEODE-9924: Avoid merging repeat test logs

[GitBox <gi...@apache.org>]

demery-pivotal opened a new pull request #7245:
URL: https://github.com/apache/geode/pull/7245


   PROBLEM
   
   Our repeat test tasks merge the output from all executions of a given
   test class, making it very difficult to diagnose failures in repeat
   tests.
   
   CAUSE
   
   In order to run tests repeatedly, our repeat test tasks override Gradle
   code to allow a test class to execute more than once. Gradle's test
   reporting code does not expect this. It directs the output from each
   test to a log associated with the test class name, not with the specific
   execution of the test class. This results in merging the outputs from
   different executions of the same class.
   
   SOLUTION
   
   Change Gradle to distinguish separate executions of a test class, and to
   log the output from each execution separately.
   
   Components:
   - New `InstanceNamingTestResultProcessor` class: Wraps a given test
     result processor to append an instance identifier (a simple counter)
     to the name of the test class when reporting results. Gradle
     associates the output with this instance-specific name instead of with
     class name.
   - New `InstanceNamingForkingTestClassProcessor` class: Wraps a
     `ForkingTestClassProcessor` to report via an
     `InstanceNamingTestResultProcessor`.
   - Change `RepeatTestExecuter` to use an
     `InstanceNamingForkingTestClassProcessor`.
   
   This commit also reverts GEODE-9912, which partially addressed the same
   problem by adding an execution ID to each log line from a DUnit ChildVM.
   The execution ID made it possible to identify the source of each merged
   log line. GEODE-9924 (this commit) makes the changes from GEODE-9912
   unnecessary.
   
   NOTES
   - Gradle now creates distinct XML and HTML report files for each
     execution of a given test class.
   - The test summary HTML page created by Gradle lists each test class
     execution separately. If a class named `FooTest` executes 50 times (as
     in a stress test run), the summary will list `FooTest-01`,
     `FooTest-02`, ..., `FooTest-50` as if they were separate test classes.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@geode.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [geode] demery-pivotal closed pull request #7245: GEODE-9924: Avoid merging repeat test logs

[GitBox <gi...@apache.org>]

demery-pivotal closed pull request #7245:
URL: https://github.com/apache/geode/pull/7245


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@geode.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [geode] demery-pivotal commented on pull request #7245: GEODE-9924: Avoid merging repeat test logs

[GitBox <gi...@apache.org>]

demery-pivotal commented on pull request #7245:
URL: https://github.com/apache/geode/pull/7245#issuecomment-1007066500


   I changed the names of the new classes after I wrote the commit message. Sorry about that.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@geode.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org