Pin ffi to < 1.13 #606
Merged
Pin ffi to < 1.13 #606
Conversation
This file contains 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
Our tests are failing on Windows: https://buildkite.com/chef-oss/inspec-train-master-verify/builds/395#18f8c2af-6501-4258-bdbf-0f8af87ce9e7 ``` rake aborted! SignalException: SIGSEGV ``` See ffi/ffi#784 - ffi 1.13 introduces segmentation faults. These are not ffi's fault directly, other gems that are not using ffi 100% correctly get away with it in ffi 1.12 but now crash with 1.13. Signed-off-by: James Stocks <[email protected]>
Schwad
approved these changes
Jun 5, 2020
There was a problem hiding this comment.
Looks great - thanks for digging into this @james-stocks! 👍
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Our tests are failing on Windows:
https://buildkite.com/chef-oss/inspec-train-master-verify/builds/395#18f8c2af-6501-4258-bdbf-0f8af87ce9e7
See ffi/ffi#784 - ffi 1.13 introduces segmentation faults. These are not ffi's fault directly, other gems that are not using ffi 100% correctly get away with it in ffi 1.12 but now crash with 1.13.
Signed-off-by: James Stocks [email protected]