Fix timeout value set for pretty printer tests

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • 141
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      BF-30152 was triggered due to the 7 minute task execution timeout for the pretty printer tests getting hit. Pretty printer tests seem to historically be taking around 6 minutes and there is logic running to determine timeout based on the average historic execution duration.

      The issue is that the function to determine historic execution time is concluding that the average execution time is 3.8 seconds:

      [2023-10-05 17:58:58,460 - buildscripts.timeouts.timeout_service - INFO] 2023-10-05 17:58:58 [info     ] Getting historic runtime information build_variant=amazon-linux2-arm64-compile evg_project=mongodb-mongo-master task_name=run_pretty_printer_tests
      [2023-10-05 17:58:58,505 - buildscripts.timeouts.timeout_service - INFO] 2023-10-05 17:58:58 [info     ] Found historic runtime information evg_stats=[HistoricTestInfo(test_name='job1_fixture_setup_0', num_pass=267, avg_duration=0.0005430711610486891, hooks=[]), HistoricTestInfo(test_name='job1_fixture_abort_0', num_pass=1, avg_duration=0.001, hooks=[]), HistoricTestInfo(test_name='job1_fixture_teardown', num_pass=266, avg_duration=0.0004285714285714286, hooks=[]), HistoricTestInfo(test_name='job0_fixture_abort_0', num_pass=1, avg_duration=0.001, hooks=[]), HistoricTestInfo(test_name='build/install/dist-test/bin/pretty_printer_test_launcher_lock_gdb_test.py', num_pass=265, avg_duration=1.2803622641509433, hooks=[]), HistoricTestInfo(test_name='job0_fixture_setup_0', num_pass=267, avg_duration=0.0004981273408239701, hooks=[]), HistoricTestInfo(test_name='job2_fixture_setup_0', num_pass=267, avg_duration=0.0005393258426966293, hooks=[]), HistoricTestInfo(test_name='build/install/dist-test/bin/pretty_printer_test_launcher_optimizer_gdb_test.py', num_pass=265, avg_duration=1.2759698113207547, hooks=[]), HistoricTestInfo(test_name='job2_fixture_abort_0', num_pass=1, avg_duration=0.0, hooks=[]), HistoricTestInfo(test_name='job2_fixture_teardown', num_pass=266, avg_duration=0.0004135338345864661, hooks=[]), HistoricTestInfo(test_name='build/install/dist-test/bin/pretty_printer_test_launcher_pretty_printer_test.py', num_pass=265, avg_duration=1.2904075471698113, hooks=[]), HistoricTestInfo(test_name='job0_fixture_teardown', num_pass=266, avg_duration=0.0004511278195488722, hooks=[])]
      [2023-10-05 17:58:58,564 - buildscripts.timeouts.timeout - INFO] 2023-10-05 17:58:58 [info     ] expected_task_runtime: 3.8467396226415094
      [2023-10-05 17:58:58,564 - __main__ - INFO] 2023-10-05 17:58:58 [info     ] Getting historic based timeout exec_timeout_secs=420 idle_timeout_secs=300
      exec_timeout_secs: 420
      timeout_secs: 300
      

      Fix the BF with a manual override and then investigate why the automatic timeout logic is failing to generate a reasonable estimation.

            Assignee:
            Zack Winter
            Reporter:
            Zack Winter
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: