-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: tests/apps/dial/preserve_top keeps failing #60
Labels
Comments
gtjoseph
added a commit
to gtjoseph/testsuite
that referenced
this issue
Jul 31, 2024
The middle sipp scenario fails often. See asterisk#60
I will look into it. |
maximilianfridrich
added a commit
to maximilianfridrich/testsuite
that referenced
this issue
Aug 1, 2024
The SIPP scenarios contained stream directions with initial answers containing audio=inactive for example which are known to trigger re-INVITEs in Asterisk. The timing of those re-INVITEs is hard to predict which can make the SIPP scenarios and tests flaky. Resolves: asterisk#60
maximilianfridrich
added a commit
to maximilianfridrich/testsuite
that referenced
this issue
Aug 1, 2024
The SIPP scenarios contained stream directions with initial answers containing audio=inactive for example which are known to trigger re-INVITEs in Asterisk. The timing of those re-INVITEs is hard to predict which can make the SIPP scenarios and tests flaky. Resolves: asterisk#60
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
Aug 2, 2024
The middle sipp scenario fails often. See #60
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
Aug 2, 2024
The middle sipp scenario fails often. See #60
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
Aug 2, 2024
The middle sipp scenario fails often. See #60
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
Aug 2, 2024
The middle sipp scenario fails often. See #60
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
Aug 2, 2024
The middle sipp scenario fails often. See #60
maximilianfridrich
added a commit
to maximilianfridrich/testsuite
that referenced
this issue
Aug 5, 2024
The SIPP scenarios contained stream directions with initial answers containing audio=inactive for example which are known to trigger re-INVITEs in Asterisk. The timing of those re-INVITEs is hard to predict which can make the SIPP scenarios and tests flaky. Resolves: asterisk#60
maximilianfridrich
added a commit
to maximilianfridrich/testsuite
that referenced
this issue
Aug 5, 2024
The SIPP scenarios contained stream directions with initial answers containing audio=inactive for example which are known to trigger re-INVITEs in Asterisk. The timing of those re-INVITEs is hard to predict which can make the SIPP scenarios and tests flaky. Resolves: asterisk#60
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
Aug 5, 2024
The SIPP scenarios contained stream directions with initial answers containing audio=inactive for example which are known to trigger re-INVITEs in Asterisk. The timing of those re-INVITEs is hard to predict which can make the SIPP scenarios and tests flaky. Resolves: #60
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
Aug 5, 2024
The SIPP scenarios contained stream directions with initial answers containing audio=inactive for example which are known to trigger re-INVITEs in Asterisk. The timing of those re-INVITEs is hard to predict which can make the SIPP scenarios and tests flaky. Resolves: #60
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
Aug 5, 2024
The SIPP scenarios contained stream directions with initial answers containing audio=inactive for example which are known to trigger re-INVITEs in Asterisk. The timing of those re-INVITEs is hard to predict which can make the SIPP scenarios and tests flaky. Resolves: #60
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
Aug 5, 2024
The SIPP scenarios contained stream directions with initial answers containing audio=inactive for example which are known to trigger re-INVITEs in Asterisk. The timing of those re-INVITEs is hard to predict which can make the SIPP scenarios and tests flaky. Resolves: #60
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
Aug 5, 2024
The SIPP scenarios contained stream directions with initial answers containing audio=inactive for example which are known to trigger re-INVITEs in Asterisk. The timing of those re-INVITEs is hard to predict which can make the SIPP scenarios and tests flaky. Resolves: #60
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Severity
Trivial
Versions
all
Components/Modules
tests/apps/dial/preserve_top
Operating Environment
rocky8
Frequency of Occurrence
Frequent
Issue Description
@maximilianfridrich Can you take a look at this test? It appears that the middle (I think) sipp scenario fails on a regular basis. It's most probably timing related so if you're going to test locally, I'd suggest doing it in a resource-constrained docker container.
I'm attaching the logs from the last run.
Nightly-apps_funcs-18.zip
Relevant log output
Asterisk Issue Guidelines
The text was updated successfully, but these errors were encountered: