Slow query performance observed for test case results processing when viewing Build result summary page for failed builds and takes long time to load data for Build result summary > tests

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • 12.0.0, 10.2.8, 11.0.5
    • Affects Version/s: 9.6.6
    • Component/s: Builds, Tests
    • None
    • 1
    • Severity 2 - Major
    • 10

      Issue Summary

      It takes a long time to process test cases when viewing build results, so the data for the build result summary> tests tab for failed builds takes a long time to render.

      Steps to Reproduce

      N/A

      Expected Results

      Build results > test case processing should be swift, and data rendering should be finished in very little time.

      Actual Results

      Threadumps show stuck at test case data processing at DB:

      • org.hibernate.query.internal.AbstractProducedQuery.list(AbstractProducedQuery.java:1617)
        com.atlassian.bamboo.resultsummary.tests.TestCaseResultHibernateDao$3.doInHibernate(TestCaseResultHibernateDao.java:109)
        com.atlassian.bamboo.resultsummary.tests.TestCaseResultHibernateDao$3.doInHibernate(TestCaseResultHibernateDao.java:92
        

      Slow query observed:

      • select testcasere0_.TEST_CASE_RESULT_ID as test_case_result_i1_116_, testcasere0_.DELTA_STATE as delta_state2_116_, testcasere0_.DURATION as duration3_116_, testcasere0_.FAILING_SINCE as failing_since4_116_, testcasere0_.QUARANTINED as quarantined5_116_, testcasere0_.TEST_STATE as test_state6_116_, testcasere0_.TEST_CASE_ID as test_case_id7_116_, testcasere0_.TEST_CLASS_RESULT_ID as test_class_result_8_116_ from TEST_CASE_RESULT testcasere0_ inner join TEST_CASE testcaseim1_ on testcasere0_.TEST_CASE_ID=testcaseim1_.TEST_CASE_ID inner join TEST_CLASS_RESULT testclassr2_ on testcasere0_.TEST_CLASS_RESULT_ID=testclassr2_.TEST_CLASS_RESULT_ID inner join TEST_CLASS testclassi3_ on testclassr2_.TEST_CLASS_ID=testclassi3_.TEST_CLASS_ID inner join BUILDRESULTSUMMARY buildresul4_ on testclassr2_.BUILDRESULTSUMMARY_ID=buildresul4_.BUILDRESULTSUMMARY_ID inner join BUILD abstractpl5_ on testclassi3_.PLAN_ID=abstractpl5_.BUILD_ID where buildresul4_.CHAIN_RESULT=:1 and (testcasere0_.DELTA_STATE in (:2 )) and testcasere0_.QUARANTINED=:3 order by testclassi3_.TEST_CLASS_NAME, abstractpl5_.TITLE fetch first :4 rows only
        

      The below found in the atlassian-bamboo.log file:

      2025-08-04 08:30:10,023 INFO [http-nio-8085-exec-6447 url: /browse/test123-1, /chain/result/viewChainResult.action; user: testuser] [FreemarkerContext] Web panel chainresult.summary com.atlassian.bamboo.plugin.system.webpanel:chainInterestingTests was being rendered for 30.40 s
      2025-08-04 08:34:23,240 INFO [http-nio-8085-exec-6518 url: /browse/test123-1, /chain/result/viewChainResult.action; user: testuser] [FreemarkerContext] Web panel chainresult.summary com.atlassian.bamboo.plugin.system.webpanel:chainInterestingTests was being rendered for 27.15 s
      2025-08-04 09:04:33,083 INFO [http-nio-8085-exec-6533 url: /browse/test123-1, /chain/result/viewChainResult.action; user: testuser] [FreemarkerContext] Web panel chainresult.summary com.atlassian.bamboo.plugin.system.webpanel:chainInterestingTests was being rendered for 1.193 min
      

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Mateusz Szmal
            Reporter:
            Jyothi Charupalli
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: