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

Sometimes SDL does not reset timeout for DiagnosticMessage response by receiving 2nd BC.OnResetTimeout' notification #3894

Open
VjKlepikov opened this issue Mar 30, 2022 · 0 comments
Labels

Comments

@VjKlepikov
Copy link

VjKlepikov commented Mar 30, 2022

Bug Report

Sometimes SDL does not reset timeout for DiagnosticMessage response by receiving 2nd BC.OnResetTimeout' notification

Occurrences: ~0.1%
Reproduction Steps
  1. Default SDL timeout is 10s (defined in .INI by 'DefaultTimeout' parameter)
  2. App is registered
  3. App sends DiagnosticMessage request
  4. SDL transfers this request to HMI
  5. HMI sends 1st 'BC.OnResetTimeout' notification to SDL right after receiving request with 'resetPeriod=15s'
  6. HMI sends 2nd 'BC.OnResetTimeout' notification to SDL after delay of 12s with 'resetPeriod=7s'
  7. HMI doesn't provide a response
Expected Behavior

SDL wait for the response from HMI within 'delay + 2nd resetPeriod' (19s)
respond with GENERIC_ERROR:false to Mobile app once this timeout expires

Observed Behavior

SDL does not reset timeout for DiagnosticMessage response by receiving 2nd BC.OnResetTimeout' notification
respond with GENERIC_ERROR:false to Mobile app once timeout expires (15s) after first request

OS & Version Information
Test Case, Sample Code, and / or Example App

./test_scripts/API/Restructuring_OnResetTimeout/005_BC_OnResetTimeout_HMI_sends_notification_twice.lua

Logs

Log.tar.gz

@VjKlepikov VjKlepikov changed the title Sometims SDL does not reset timeout for DiagnosticMessage response by receiving 2nd BC.OnResetTimeout' notification Sometimes SDL does not reset timeout for DiagnosticMessage response by receiving 2nd BC.OnResetTimeout' notification Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants