-
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
[mdatagen] add unsupported_platforms
support and enable several components
#30640
[mdatagen] add unsupported_platforms
support and enable several components
#30640
Conversation
2fbead0
to
78de2f0
Compare
supported_platforms
support and enable several components
Also I don't think we need to render |
Signed-off-by: Ziqi Zhao <zhaoziqi9146@gmail.com>
78de2f0
to
dc27578
Compare
supported_platforms
support and enable several componentsunsupported_platforms
support and enable several components
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 @fatsheep9146! This looks great, just one comment
@@ -52,6 +53,7 @@ func Test_composeEffectiveConfig(t *testing.T) { | |||
|
|||
expectedConfig, err := os.ReadFile("../testdata/collector/effective_config.yaml") | |||
require.NoError(t, err) | |||
expectedConfig = bytes.ReplaceAll(expectedConfig, []byte("\r\n"), []byte("\n")) |
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.
can this change be made in a separate PR? it seems unrelated to the change here
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.
No problem!
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.
#30690 is created @codeboten
My understanding is that we should be testing all components on all OSes giving that we expect proper error messages and the that the collector configuration can be parsed on different platforms. Not testing the lifecycle on such platforms as of recently risks crashes without proper error message and regressions in this regard, see: |
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 understand this as an emergency fix to the broken Windows CI, however, in the end the tests should keep loading the config and expecting a definite error when the platform is not supported.
Yes, so @dmitryax suggested:
I think we can improve this as you suggest in following prs. |
Co-authored-by: Dmitrii Anoshin <anoshindx@gmail.com>
Co-authored-by: Dmitrii Anoshin <anoshindx@gmail.com>
Signed-off-by: Ziqi Zhao <zhaoziqi9146@gmail.com>
|
Thanks @fatsheep9146 |
…ponents (open-telemetry#30640) **Description:** Add `supported_platforms` to enable components to describe which platforms are supported, meanwhile this configuration can also be used to generate the liftcycle test to skip windows when the component does not support windows. **Link to tracking Issue:** fix open-telemetry#30561 --------- Signed-off-by: Ziqi Zhao <zhaoziqi9146@gmail.com> Co-authored-by: Dmitrii Anoshin <anoshindx@gmail.com>
Description:
Add
supported_platforms
to enable components to describe which platforms are supported, meanwhile this configuration can also be used to generate the liftcycle test to skip windows when the component does not support windows.Link to tracking Issue:
fix #30561
Testing:
Documentation: