-
Notifications
You must be signed in to change notification settings - Fork 85
(PA-3526) Ruby 2.7.2 performance patches #414
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
(PA-3526) Ruby 2.7.2 performance patches #414
Conversation
d44cfdd to
d0c3180
Compare
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.
Successfully built an x64 MSI, installed on Windows 2019 just fine, and was able to create a project, run ruby-language tasks (facts), and run Puppet language plans.
d0c3180 to
4c70d16
Compare
4c70d16 to
d16928c
Compare
|
Puppet runtime builds for Puppet Agent 6.x for all the supported platforms are available here: http://builds.delivery.puppetlabs.net/puppet-runtime/d16928cda5c70f0548a97d7acdda6a10791dd5c4/ |
|
Puppet Agent runtime for main build passed on all the supported. Artifacts are available here: http://builds.delivery.puppetlabs.net/puppet-runtime/d16928cda5c70f0548a97d7acdda6a10791dd5c4/ |
|
tests passed on all platforms for Puppet 6.x: https://jenkins-master-prod-1.delivery.puppetlabs.net/view/Adhoc/job/platform_puppet-agent-extra_puppet-agent-integration-suite_adhoc-ad_hoc/940/ |
|
This is great news! I am working on getting a PDK build tested with these patches |
|
Tests passed on Puppet Agent main (7.x) with this change: https://jenkins-master-prod-1.delivery.puppetlabs.net/view/Adhoc/job/platform_puppet-agent-extra_puppet-agent-integration-suite_adhoc-ad_hoc/942/ |
|
Hmm, I'm trying to build PDK on Windows 2019 on this PR, and am running into a strange error: Anything I'm obviously doing wrong? |
|
🎉 🌮 🎉 Got a successful run for PDK!! |
|
Yay! Could you reference PA-3526 in the commits. We're definitely going to want to mention this in release notes |
|
@joshcooper will do! |
0ae0e4a to
87d67bf
Compare
9c89df2 to
d815fb3
Compare
|
Commit messages amended |
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.
@jpogran awesome thanks! Could you file a PA ticket so we remember to double check/revert commit 6a6886d when moving to ruby 2.7.3+ as it looks like that issue is fixed in upstream ruby (but not yet released): ruby/ruby@99b4f20
Did you run into issues with the ruby patch for https://bugs.ruby-lang.org/issues/15856? I found it to be somewhat helpful in puppet, but don't remember exact numbers.
|
Ticket https://tickets.puppetlabs.com/browse/PA-3691 created to track removing the patch when upstream ruby is merged into the released 2.7 |
I did find it to be helpful, but had trouble combining it with these patches in vanagon. I decided to first try to merge what was already in use in upstream ruby before attempting to reconcile the differences. |
|
\o/ Any other todo items left before we merge? It's fine if there are, I don't mean to pressure but happy to help get this across the line any way I can. |
|
I don't think there are any other open items. We have successfull runs in puppet-agent, bolt and pdk, I think this is ready for merge. 🚀 If everyone is ok with it, I'll self merge this The patch Josh is mentioning would be a separate PR. |
|
Holding off on merging this until Puppet 7.6.0 is released later this month. |
|
We had to bump to 2.7.3 for a ruby cve and I think commit 6a6886d can be dropped due to the issue being fixed upstream. |
This updates the list of platforms that don't have dtrace to include the new Windows 2019 platform, so that puppet-runtime can be built for Windows 2019.
d815fb3 to
a2ccf66
Compare
|
Commit 6a6886d removed, rebased and synced with master |
|
Is this ready to remove 'do not merge' label? |
|
|
Uh oh!
There was an error while loading. Please reload this page.