-
Bug
-
Resolution: Unresolved
-
Major
-
Loadrunner - 12.55
MicroFocus Plugin version - 5.5
The standalone loadrunner scenario (Not integrated with ALM, PC etc) is executed properly and the results are collated in the controller machine/slave machine properly.
However when the results are a bit of huge size the "Complete Data" is not generated before the custom analysis template is applied, which results in a invalid/corrupted HTML report.
Is there anyway we can configure a timeout for the complete data generation, because waiting indefinitely for the complete data generation will become another issue.
So, I request the process to be,
1) Launch Analysis
2) Trigger Complete Data Generation (current default behavior)
3) wait for Complete data for less than the CDataGenerationTimeOut
3.1) if timeout, cancel the Complete Data Generation
4) Apply the default or custom template (if any)
5) Export the HTML Report to workspace
Extract from build.log
Scenario run has startedScenario run has startedScenario R:/Projects/my_project/Scenario/2018/my_project1x_2x_Scenario2018.lrs ended after 1:15:45.
============================================================================
Analyzing results...
closing ControllerError: The Controller is still running...
Controller closed
calling analysis report generator
executing Analysis launcher with arguments : "D:\jenkins\workspace\my_project\b6686a\LRR\LRR.lrr" "D:\jenkins\workspace\my_project\b6686a\LRA\LRA.lra" "D:\jenkins\workspace\my_project\b6686a\HTML\HTML.html" "C:\Program Files (x86)\HPE\LoadRunner\AnalysisTemplates\my_project_Template2\my_project_Template2.tem"
time for analysis: 00::03:00:00
starting analysis launcher
creating analysis COM object
creating analysis session
analysis session created
creating HTML reports
HTML reports created
[JENKINS-53801] Generate Complete Data before applying template
| Description |
Original:
The standalone loadrunner scenario (Not integrated with ALM, PC etc) is executed properly and the results are collated in the controller machine/slave machine properly. However when the results are a bit of huge size the "Complete Data" is not generated before the custom analysis template is applied, which results in a invalid/corrupted HTML report. Is there anyway we can configure a timeout for the complete data generation, because waiting indefinitely for the complete data generation will become another issue. So, I request the process to be, 1) Launch Analysis 2) Trigger Complete Data Generation (current default behavior) 3) wait for Complete data for less than the CDataGenerationTimeOut 3.1) if timeout, cancel the Complete Data Generation 4) Apply the default or custom template (if any) 5) Export the HTML Report to workspace Extract from build.log Scenario run has startedScenario run has startedScenario R:/Projects/my_project/Scenario/2018/my_project1x_2x_Scenario2018.lrs ended after 1:15:45.============================================================================Analyzing results...closing ControllerError: The Controller is still running...Controller closedcalling analysis report generatorexecuting Analysis launcher with arguments : "D:\jenkins\workspace\my_project\b6686a\LRR\LRR.lrr" "D:\jenkins\workspace\my_project\b6686a\LRA\LRA.lra" "D:\jenkins\workspace\my_project\b6686a\HTML\HTML.html" "C:\Program Files (x86)\HPE\LoadRunner\AnalysisTemplates\my_project_Template2\my_project_Template2.tem"time for analysis: 00::03:00:00starting analysis launchercreating analysis COM objectcreating analysis sessionanalysis session createdcreating HTML reportsHTML reports created |
New:
The standalone loadrunner scenario (Not integrated with ALM, PC etc) is executed properly and the results are collated in the controller machine/slave machine properly. However when the results are a bit of huge size the "Complete Data" is not generated before the custom analysis template is applied, which results in a invalid/corrupted HTML report. Is there anyway we can configure a timeout for the complete data generation, because waiting indefinitely for the complete data generation will become another issue. So, I request the process to be, 1) Launch Analysis 2) Trigger Complete Data Generation (current default behavior) 3) wait for Complete data for less than the CDataGenerationTimeOut 3.1) if timeout, cancel the Complete Data Generation 4) Apply the default or custom template (if any) 5) Export the HTML Report to workspace Extract from build.log Scenario run has startedScenario run has startedScenario R:/Projects/my_project/Scenario/2018/my_project1x_2x_Scenario2018.lrs ended after 1:15:45. ============================================================================ Analyzing results... closing ControllerError: The Controller is still running... Controller closed calling analysis report generatorexecuting Analysis launcher with arguments : "D:\jenkins\workspace\my_project\b6686a\LRR\LRR.lrr" "D:\jenkins\workspace\my_project\b6686a\LRA\LRA.lra" "D:\jenkins\workspace\my_project\b6686a\HTML\HTML.html" "C:\Program Files (x86)\HPE\LoadRunner\AnalysisTemplates\my_project_Template2\my_project_Template2.tem"time for analysis: 00::03:00:00starting analysis launchercreating analysis COM objectcreating analysis sessionanalysis session createdcreating HTML reportsHTML reports created |
| Description |
Original:
The standalone loadrunner scenario (Not integrated with ALM, PC etc) is executed properly and the results are collated in the controller machine/slave machine properly. However when the results are a bit of huge size the "Complete Data" is not generated before the custom analysis template is applied, which results in a invalid/corrupted HTML report. Is there anyway we can configure a timeout for the complete data generation, because waiting indefinitely for the complete data generation will become another issue. So, I request the process to be, 1) Launch Analysis 2) Trigger Complete Data Generation (current default behavior) 3) wait for Complete data for less than the CDataGenerationTimeOut 3.1) if timeout, cancel the Complete Data Generation 4) Apply the default or custom template (if any) 5) Export the HTML Report to workspace Extract from build.log Scenario run has startedScenario run has startedScenario R:/Projects/my_project/Scenario/2018/my_project1x_2x_Scenario2018.lrs ended after 1:15:45. ============================================================================ Analyzing results... closing ControllerError: The Controller is still running... Controller closed calling analysis report generatorexecuting Analysis launcher with arguments : "D:\jenkins\workspace\my_project\b6686a\LRR\LRR.lrr" "D:\jenkins\workspace\my_project\b6686a\LRA\LRA.lra" "D:\jenkins\workspace\my_project\b6686a\HTML\HTML.html" "C:\Program Files (x86)\HPE\LoadRunner\AnalysisTemplates\my_project_Template2\my_project_Template2.tem"time for analysis: 00::03:00:00starting analysis launchercreating analysis COM objectcreating analysis sessionanalysis session createdcreating HTML reportsHTML reports created |
New:
The standalone loadrunner scenario (Not integrated with ALM, PC etc) is executed properly and the results are collated in the controller machine/slave machine properly. However when the results are a bit of huge size the "Complete Data" is not generated before the custom analysis template is applied, which results in a invalid/corrupted HTML report. Is there anyway we can configure a timeout for the complete data generation, because waiting indefinitely for the complete data generation will become another issue. So, I request the process to be, 1) Launch Analysis 2) Trigger Complete Data Generation (current default behavior) 3) wait for Complete data for less than the CDataGenerationTimeOut 3.1) if timeout, cancel the Complete Data Generation 4) Apply the default or custom template (if any) 5) Export the HTML Report to workspace Extract from build.log Scenario run has startedScenario run has startedScenario R:/Projects/my_project/Scenario/2018/my_project1x_2x_Scenario2018.lrs ended after 1:15:45. ============================================================================ Analyzing results... closing ControllerError: The Controller is still running... Controller closed calling analysis report generator executing Analysis launcher with arguments : "D:\jenkins\workspace\my_project\b6686a\LRR\LRR.lrr" "D:\jenkins\workspace\my_project\b6686a\LRA\LRA.lra" "D:\jenkins\workspace\my_project\b6686a\HTML\HTML.html" "C:\Program Files (x86)\HPE\LoadRunner\AnalysisTemplates\my_project_Template2\my_project_Template2.tem" time for analysis: 00::03:00:00 starting analysis launcher creating analysis COM object creating analysis session analysis session created creating HTML reports HTML reports created |
| Assignee | Original: Daniel Gront [ gront ] | New: Rolando-Mihai Vlad [ rolandomihaivlad ] |
| Attachment | New: Rumba_Template2.zip [ 44611 ] | |
| Attachment | New: LRAnalysis80.ini [ 44612 ] |
1) The size of the LRR folder is - 2.8 GB (This usually goes up to 22 GB on longer test duration)
2) Template File - Attached
3) LRAnalysis80.ini - Attached
Note : The Ananlysis program's setting at Menu, Tools -> Options -> Results Collection -> "Display Summary while generating complete data" was enabled while the above issue was observed.
I've updated it to "Generate Summary Data Only" for the time being, and will post here if it work-around the corrupted HTML folder issue.
Thanks,
Anand
Rolando-Mihai Vlad
made changes -
| Attachment | New: LRAnalysis80.ini [ 44615 ] |
Rolando-Mihai Vlad
added a comment - Hello Ananda,
I attached a new LRAnalysis80.ini. Please backup your previous one before using this.
Regards,
Rolando
Rolando-Mihai Vlad
added a comment - Hello Ananda,
I attached a new LRAnalysis80.ini. Please backup your previous one before using this.
Regards,
Rolando Hello rolandomihaivlad,
I guess you updated the config to force the Analysis to "Generate Only Complete Data".
As I mentioned in the original problem statement, this will become another issue, if the complete data generation takes hours to complete.
So a configure-able timeout would be a ideal solution.
Hello Ananda,
Could you please explain what "a bit of huge size" means in your context. Also, please attach the .tem file and LRAnalysis80.ini.
Regards,
Rolando