Closed etagwerker closed 2 years ago
@etagwerker We can add the Gemfile.lock
👍 I see rubysec added it too https://github.com/rubysec/bundler-audit/tree/master/spec/bundle/unpatched_gems I don't know if that would solve the Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
error though
@bronzdoc Sounds good. I went ahead and did that in my local environment and it seems to work fine. I'll push my changes to #45 as soon as GitHub starts working again... 😄
Before we start...:
Branch/Commit:
main
Expected behavior:
Test suite should pass.
Actual behavior:
Test suite does not pass.
Steps to reproduce:
Context and environment:
You can see this failure in GitHub Actions. It should be easy to replicate in a Mac OS X environment too (I did!)
Part of the problem is that every time we run the test suite we are creating a brand new Gemfile.lock inside the unpatched_gems directory: https://github.com/rubymem/bundler-leak/blob/main/Rakefile#L43-L47
I don't see why that is necessary, that particular Gemfile.lock could be checked in to the repository. The important part is to have the unpatched gem inside the Gemfile.lock file.
Logs
I will abide by the code of conduct