-
-
Notifications
You must be signed in to change notification settings - Fork 78
latest robotframework versions [6.2] #1041
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
base: 6.2
Are you sure you want to change the base?
Conversation
robotframework-lsp = 1.10.1 | ||
robotframework-lsp = 1.13.0 | ||
robotframework-pythonlibcore = 4.4.1 | ||
# core tests do not use selenium anymore -> remove? |
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.
For me it is fine to remove the selenium pins.
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.
There are some addons (especially easyform) which rely on selenium and buildout for testsetup ... I'd leave it for 6.2 ... maybe mark for removal in 7.0 ?
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.
Agreed.
cfc9b24
to
da324f8
Compare
latest plugin release promises to solve our problem with parsing endtime: https://plugins.jenkins.io/robot/releases/#version_6.2.0 ... @gforcada I've updated the plugin, but maybe we need to restart jenkins? |
Update to latest robotframework version
Update to latest robotframework version
d16cd29
to
6803c9f
Compare
6803c9f
to
cd8edc5
Compare
see #1002unfortunately after merging, there was an error with the jenkins robotframework plugin again when generating the reports. Do not merge until we know whats going on there or a plugin update is available.