Skip to content
This repository has been archived by the owner on Apr 14, 2021. It is now read-only.

Fix outdated regression from cc355865 #5176

Merged

Conversation

chrismo
Copy link
Contributor

@chrismo chrismo commented Nov 15, 2016

Refactoring of @lucasmazza fix w/ specs.

The only existing spec coverage was essentially integration level and
there was no way either @lucasmazza or myself could find a way to
simulate the bug context.

I extracted some of the code out of outdated into Definition and
SpecSet and added unit specs to those extracted bits.

Fixes #4979

The only existing spec coverage was essentially integration level and
there was no way either @lucasmazza or myself could find a way to
simulate the bug context.

I extracted some of the code out of outdated into Definition and
SpecSet and added unit specs to those extracted bits.
@chrismo chrismo force-pushed the fix_outdated_regression_from_cc355865 branch from 66d6b48 to b3ad170 Compare November 15, 2016 16:27
@chrismo
Copy link
Contributor Author

chrismo commented Nov 15, 2016

git commit --amend to force a different sha, since the homu check followed over here to this PR, based on the sha. This looks like maybe we'll be good. /me still learning and cluttering things up.

@chrismo
Copy link
Contributor Author

chrismo commented Nov 15, 2016

@bundlerbot r+

@bundlerbot
Copy link
Collaborator

📌 Commit b3ad170 has been approved by chrismo

@bundlerbot
Copy link
Collaborator

⚡ Test exempted - status

@bundlerbot bundlerbot merged commit b3ad170 into rubygems:master Nov 15, 2016
bundlerbot added a commit that referenced this pull request Nov 15, 2016
…r=chrismo

Fix outdated regression from cc35586

Refactoring of @lucasmazza fix w/ specs.

The only existing spec coverage was essentially integration level and
there was no way either @lucasmazza or myself could find a way to
simulate the bug context.

I extracted some of the code out of outdated into Definition and
SpecSet and added unit specs to those extracted bits.

Fixes #4979
@chrismo chrismo self-assigned this Nov 15, 2016
@indirect
Copy link
Member

indirect commented Nov 15, 2016

@chrismo 🎉 hooray finally r+ support

@chrismo
Copy link
Contributor Author

chrismo commented Nov 15, 2016

yeah! very cool - thx for the work :)

@chrismo chrismo deleted the fix_outdated_regression_from_cc355865 branch November 21, 2016 21:32
@kikonen
Copy link

kikonen commented Dec 1, 2016

Q: When release including this fix will be available?

@coilysiren
Copy link
Contributor

@kikonen if we release a patch, it'll be 1.13.7. Otherwise it'll be in 1.14.0

chrismo added a commit to chrismo/bundler that referenced this pull request Dec 23, 2016
This supersedes PR rubygems#4734, which fixed a bug but didn't have proper spec
coverage. Since that PR was submitted, a different commit (291a807 in
PR rubygems#5176) fixed a similar bug at the same time. That caused a merge
conflict in rubygems#4734. It was unknown if the same fix fixed both bugs,
since there were no successfully implemented specs. These specs show
that the bug was properly fixed.
chrismo added a commit to chrismo/bundler that referenced this pull request Dec 23, 2016
This supersedes PR rubygems#4734, which fixed a bug but didn't have proper spec
coverage. Since that PR was submitted, a different commit (291a807 in
PR rubygems#5176) fixed a similar bug at the same time. That caused a merge
conflict in rubygems#4734. It was unknown if the same fix fixed both bugs,
since there were no successfully implemented specs. These specs show
that the bug was properly fixed.

These specs were mostly already implemented by @b-ggs, just needed a
little additional guidance.
bundlerbot added a commit that referenced this pull request Dec 23, 2016
Specs for multiple platform bug fix in outdated.

This supersedes PR #4734, which fixed a bug but didn't have proper spec
coverage. Since that PR was submitted, a different commit (291a807 in
PR #5176) fixed a similar bug at the same time. That caused a merge
conflict in #4734. It was unknown if the same fix fixed both bugs,
since there were no successfully implemented specs. These specs show
that the bug was properly fixed.

These specs were mostly already implemented by @b-ggs, just needed a
little additional guidance.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bundle outdated (1.13.0) not listing all outdated gems
6 participants