-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[receiver/chrony] generated lifecycle tests #31524
Conversation
10abaf0
to
df79f25
Compare
…alization of the chrony client to the start function
df79f25
to
e40fa3a
Compare
|
||
tests: | ||
config: | ||
skip_lifecycle: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this true
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you try to start the receiver, it fails looking for the chrony socket file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So why do we need to do the functional changes if the test fails anyway? That can be done separately right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The generated tests test two scenarios:
- lifecycle, meaning we start and stop the receiver with a configuration, and make sure it is able to run. This is skipped.
- shutdown: we create the receiver and call .Shutdown on it. We check the receiver doesn't panic on this unexpected call.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know. so the shutdown part is failing without functional changes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed, the current behavior of the chrony receiver is to create a chrony client before creating the receiver. This client immediately looks up a file on disk and fails. Moving the chrony client creation to start helps.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for clarifying 👍
**Description:** Add generated tests for chrony receiver; move initialization of the chrony client to the start function **Link to tracking Issue:** Relates to open-telemetry#27849
Description:
Add generated tests for chrony receiver; move initialization of the chrony client to the start function
Link to tracking Issue:
Relates to #27849