Forum Discussion

diegoxro's avatar
diegoxro
New Contributor
7 years ago

Ready Api loadrunner.sh does not generate report ( any format )

When running test using the loadrunner scripts, Load is generated but report is not. It fails with error Unable to open Display.

 

OS: RHEL Server release 7.3 (Maipo)

Running: sh ../ReadyAPI-2.0.2/bin/loadtestrunner.sh "restapitest.xml" "-nLoadUI NG Test" "-EDefault environment" "-a127.0.0.1:1991=New Scenario" -r./test -FPDF

 

-----------------------------------------
TEST EXECUTION COMPLETED
FINAL RESULTS: Time: 00:00:10 Requests: 240 Failures: 0
-----------------------------------------
19:49:35,824 INFO [CanvasItemImpl] Generating a summary report for CanvasItem LoadUI NG Test.
19:49:35,826 DEBUG [ProjectSummaryCreatorBase] Creating a summary with start time Mon Aug 07 19:49:09 UTC 2017 and end time Mon Aug 07 19:49:34 UTC 2017.
[ERROR]: Unable to open DISPLAY
19:49:36,198 INFO [license] Ready! API 2.0.2 shutting down

 

5 Replies

Sort By
  • JamesLunan's avatar
    JamesLunan
    SmartBear Alumni (Retired)
    7 years ago

    Hello diegoxro,

     

    I don't have any reports of tests failing with the "Unable to open DISPLAY" error. However, there is a similar issue for versions previous to 2.1.0 where in some cases PDF reports would fail intermittently. Are you able to try out the latest version and see if that resolves your problem?

     

    Have you opened a support case to have someone look into the issue?

    • diegoxro's avatar
      diegoxro
      New Contributor
      7 years ago

      thanks for your reply!

       

      I get the same error and it is with ALL supported formats. 

    • diegoxro's avatar
      diegoxro
      New Contributor
      7 years ago

      case has been opened for a couple of days. no replies. 

      • JamesLunan's avatar
        JamesLunan
        SmartBear Alumni (Retired)
        7 years ago

        Can you private message me the case number?

  • JamesLunan's avatar
    JamesLunan
    SmartBear Alumni (Retired)
    7 years ago

    Circling back to this thread, as promised.

     

    It turns out we had some issues that started in ReadyAPI v2.1 with RHEL headless mode. The fix is now in the maintenance build and should be in the ReadyAPI v2.2 release.