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
Stick to bundler version < 2 on AppVeyor #2321
Conversation
1d3c98d
to
fd1116c
Compare
@iggant you're welcome to keep plugging at this! |
Travis issue with If we do that, new PRs will have at least 1 less problem to solve :) |
b1a3105
to
9a8460c
Compare
@iggant would you mind rebasing the PR on latest |
@wasifhossain yes will do this on Friday |
dd17f4c
to
25cccde
Compare
@wasifhossain rebased and squashed |
@@ -164,7 +164,7 @@ def test_expiring_of_cache_at_update_of_record | |||
|
|||
assert_equal 'Foo', author_json[:name] | |||
|
|||
author.update_attributes(name: 'Bar') | |||
author.update(name: 'Bar') |
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.
👍
@@ -202,10 +202,12 @@ def test_cache_expiration_in_collection_on_update_of_record | |||
end | |||
|
|||
bar = 'Bar' | |||
author.update!(name: bar) | |||
Timecop.travel(10.seconds.from_now) do |
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.
@iggant can you please elaborate the case why you need Timecop in this case?
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.
before this change there were random test failture
probably this is because cache version relay on updated_at column which doesn't contain millisecond part, so time to time it doesn't invalidate cache.
and with travel to 10 second ahead we eliminate this possibility
probably current check in the 172 line is also related, but I will thy to change that test in the next PR
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.
perfect reason 👌 can't wait to see you apply the same logic for the other test too on line 167. You can do it in your next PR. Then we may also be able to remove these weird checks
if ENV['APPVEYOR'] && actual != expected
skip('Cache expiration tests sometimes fail on Appveyor. FIXME :)')
@iggant thanks a lot for your effort. Appveyor became green again 🙌 |
@wasifhossain made requested changed |
Force AppVeyor to follow the bundler version constraint