[asterisk-bugs] [JIRA] (ASTERISK-25125) Testsuite: Investigate lock-up of tests/fastagi/record-file

[Corey Farrell (JIRA)]

Corey Farrell created ASTERISK-25125:
----------------------------------------

             Summary: Testsuite: Investigate lock-up of tests/fastagi/record-file
                 Key: ASTERISK-25125
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25125
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Tests/testsuite
            Reporter: Corey Farrell


Every time I run the full testsuite I come back 12 hours later to see progress frozen at tests/fastagi/record-file/.  No instances of Asterisk are running, {{tests/fastagi/record-file/run-test}} is left running.  I run the testsuite with {{./run-local run}}, unsure if that is relevant to this issue.  Marking as major since the full testsuite takes a VERY long time to run, any test that freezes the whole process is a major issue.

Strange thing is it doesn't look like the test ever attempted to start Asterisk.  After this failure there are no {{astroot/tmp/fastagi/record-file}} or {{logs/fastagi/record-file}} folders.  {{logs/messages.txt}} does not have any messages about the test, just a large gap in the timestamps:
{noformat}
[May 23 12:18:52] INFO[19292]: asterisk.test_case:158 __init__: Executing tests/fastagi/hangup
...
[May 23 12:19:19] INFO[19292]: twisted:443 emit: Main loop terminated.
[May 23 18:04:35] INFO[20491]: asterisk.test_case:158 __init__: Executing tests/fastagi/say-alpha
{noformat}

6PM being when I killed the process for {{python tests/fastagi/record-file/run-test}}.  There was a message on the screen about reactor timeout, but for some reason it didn't make it to a log and my screen has scrolled too far.  Once my system is available I will try running this test alone so I can get more information.



--
This message was sent by Atlassian JIRA
(v6.2#6252)