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

[1.2] TC-ACE-1.2 Fails if DUT negotiates a higher MaxInterval on subscription #28817

Closed
jrhees-cae opened this issue Aug 22, 2023 · 1 comment · Fixed by #28820
Closed

[1.2] TC-ACE-1.2 Fails if DUT negotiates a higher MaxInterval on subscription #28817

jrhees-cae opened this issue Aug 22, 2023 · 1 comment · Fixed by #28820
Labels
bug Something isn't working needs triage

Comments

@jrhees-cae
Copy link
Contributor

Reproduction steps

Python test TC-ACE-1.2 will fail on Step 8 if a DUT negotiates a higher MaxInterval than a few seconds (during subscription).

***** Test Step 8 : TH2 waits for subscription report for access control entry changed event

Possible remedies are:

  1. Modify the test to extend its wait time in step 8 to match the negotiated MaxInterval value from the subscription
  2. Set the isUrgent flag in the subscription request such that the AccessControlEntryChanged event arrived based on the minInterval time.

This is related to #28793

Bug prevalence

Consistent

GitHub hash of the SDK that was being used

main

Platform

python

Platform Version(s)

No response

Type

Test Improvement

Anything else?

No response

@cecille
Copy link
Contributor

cecille commented Aug 22, 2023

For now, I think the solution is to use IsUrgent - we don't have a good way to get back the negotiated time right now. We SHOULD implement that, but the chances of it landing and landing bug-free before friday are low.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs triage
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants