-
Notifications
You must be signed in to change notification settings - Fork 530
Fix ledvance unit tests #2918
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
Merged
+9
−2
Merged
Fix ledvance unit tests #2918
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Was this tested against 15? HC 0.59 is running lua-libs v17.
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 put it at 15 because that is when the disable_startup_messages was included in the test framework, so in theory it should work all the way back to version 15 if we ever include those earlier versions
Uh oh!
There was an error while loading. Please reload this page.
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.
Testing against 15 has unrelated failures due to stateless step capabilities in the driver. New capabilities in a driver are a separate issue that would need to be dealt with if we use those older api versions. Testing on 17 does pass since the capabilities are present
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 don't know if it makes sense to do backwards compat tests with the artificial limitation of capabilities not being generated, which is a UT only situation. To me, this should be worked around by the jenkins test framework rather than the devs, since new capabilities will continue to be made.
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 we ever include tests for lua libs <17 we will need to address that. I agree that a work around would be best done in jenkins when running the tests. For now I am opting for setting the min_api_version to what it should be, but I can change to 17 if people want.
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 think I'm wondering what will happen when we add statelessWindowStep (or whatever) in the next release and roll that out to the drivers. Will that cause everything to fail?
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.
Ill look into updating jenkins to be using the latest capabilities. IDRC if we do 15 or 17 as we likely aren't going to be adding 58 to our testing matrix in the future. The only way we'd go below 17 is if we wanted more support into the Cell hubs back on 52.
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 think we should support 58, right? We still have some tv hubs on 58, no? Calling this out since HQ caught a 58 bug in one of my PRs about a month ago.
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.
60 is almost fully released to TVs, so there is not much need to include it. 60 will be the lowest FW version out there (besides the ST Wifi hubs on 52).