Skip to content
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

Closed
1 task done
gtjoseph opened this issue Jul 31, 2024 · 1 comment · Fixed by #62
Closed
1 task done

[Bug]: tests/apps/dial/preserve_top keeps failing #60

gtjoseph opened this issue Jul 31, 2024 · 1 comment · Fixed by #62
Labels

Comments

@gtjoseph
Copy link
Member

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

Running tests/apps/dial/preserve_top ...
[Jul 31 02:28:57] WARNING[18493]: asterisk.sipp:572 processEnded: b"Resolving remote host '127.0.0.1'... Done.n"
[Jul 31 02:28:57] WARNING[18493]: asterisk.sipp:572 processEnded: b"2024-07-31t02:28:51.314321t1722392931.314321: Failed regexp match: looking in 'v=0rno=- 911699183 911699183 IN IP4 127.0.0.1rns=Asteriskrnc=IN IP4 127.0.0.1rnt=0 0rnm=audio 16940 RTP/AVP 9 0 8 101rna=rtpmap:9 G722/8000rna=rtpmap:0 PCMU/8000rna=rtpmap:8 PCMA/8000rna=rtpmap:101 telephone-event/8000rna=fmtp:101 0-16rna=ptime:20rna=maxptime:140rna=sendrecvrnm=video 15046 RTP/AVP 99 34rna=rtpmap:99 H264/90000rna=rtpmap:34 H263/90000rna=fmtprna=sendrecvrn', with regexp 'a=sendonly'n"
[Jul 31 02:28:57] WARNING[18493]: asterisk.sipp:675 __scenario_callback: SIPp Scenario carol2.xml Failed [1]
[Jul 31 02:28:57] WARNING[18493]: asterisk.sipp:231 _handle_scenario_finished: Scenario carol2.xml failed
[Jul 31 02:28:57] WARNING[18493]: asterisk.sipp:473 __execute_next: SIPp Scenario carol2.xml Failed
Test tests/apps/dial/preserve_top failed

Asterisk Issue Guidelines

  • Yes, I have read the Asterisk Issue Guidelines
gtjoseph added a commit to gtjoseph/testsuite that referenced this issue Jul 31, 2024
@maximilianfridrich
Copy link
Contributor

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
asterisk-org-access-app bot pushed a commit that referenced this issue Aug 2, 2024
asterisk-org-access-app bot pushed a commit that referenced this issue Aug 2, 2024
asterisk-org-access-app bot pushed a commit that referenced this issue Aug 2, 2024
asterisk-org-access-app bot pushed a commit that referenced this issue Aug 2, 2024
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
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants