-
Notifications
You must be signed in to change notification settings - Fork 13
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
TTL validation #5
Comments
For reference, there's a test testing TTL issues by shifting time and testing presence of records in the answer, in |
CZNIC-GitLab
pushed a commit
that referenced
this issue
Aug 2, 2017
Thanks! I will check! |
CZNIC-GitLab
pushed a commit
that referenced
this issue
Nov 1, 2017
CZNIC-GitLab
pushed a commit
that referenced
this issue
Nov 1, 2017
CZNIC-GitLab
pushed a commit
that referenced
this issue
Nov 1, 2017
CZNIC-GitLab
pushed a commit
that referenced
this issue
Nov 1, 2017
CZNIC-GitLab
pushed a commit
that referenced
this issue
Dec 7, 2017
CZNIC-GitLab
pushed a commit
that referenced
this issue
Dec 22, 2017
CZNIC-GitLab
pushed a commit
that referenced
this issue
Dec 22, 2017
CZNIC-GitLab
pushed a commit
that referenced
this issue
Mar 5, 2018
CZNIC-GitLab
pushed a commit
that referenced
this issue
Mar 5, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello!
As I understand, by default deckard ignores TTL values in comparison code. But for our purposes, we need to check TTL values also.
Is it possible to enable/disable strict TTL validation for a particular test?
Thank you!
The text was updated successfully, but these errors were encountered: