about summary refs log tree commit homepage
path: root/t/test_isolate.rb
DateCommit message (Collapse)
2019-01-02t/test_isolate: various version updates
2017-04-02tests: update isolate deps for unicorn and raindrops
Newer versions were just released, so we should test with them to prevent mishaps like <https://bogomips.org/rainbows-public/9267B33C-D13C-47E1-8892-4777B96DDCD1@gmail.com/> from surfacing :x
2016-12-24Revert "t/t0044-autopush.sh: remove test"
Stuck between a rock and a hard place.. This reverts commit 5c911ab2470a2ca9c140b3a2e20ae810bf758590 and restores autopush support when using kgio 2.11.0+ Explanations on the kgio mailing list below: https://bogomips.org/kgio-public/20161216-kgio-2.11.0-released@fail/ https://bogomips.org/kgio-public/20161216000110.GA7366@untitled/T/#u We can drop kgio when we drop Ruby <= 2.2 support in a few years.
2016-11-17support rack 2.x
This requires updating to unicorn 5.1+ to relax the rack requirement. Unlike unicorn, Rainbows! is considerably larger and cannot function without rack installed. There were no code changes required to pass the test suite; but some other optional gems needed to be updated for testing. Support for async_sinatra is no longer tested as that is tied to rack 1.x; but the remaining EventMachine-dependent parts remain tested. Thanks to Julia López Aladro for reminding us on the mailing list: https://bogomips.org/rainbows-public/CAPhSs6OAU+motd+MF=WOSek9==StLjEQJsNwAO3-aRWCZzhs=g@mail.gmail.com/
2015-11-21bump to unicorn 5.0.1, use monotonic clock
The timeout (mis)feature in unicorn uses the monotonic clock if available. We must follow suit to avoid having our timeout functionality completely broken.
2015-09-14t/test_isolate.rb: updates for various gem versions
2014-10-08update dependencies for Ruby 2.2.0dev
This will allow me to test for unintentional breakage in 2.2.0. Part of the reason for putting this project on maintenance mode is because many of the libraries we depend on have not kept up with the latest changes to Ruby. So we will disable many tests for 2.2+ to ensure the core parts remain working.
2014-05-12documentation updates for Rubyforge death
We're migrating to a new public-inbox[1] + mailing list rainbows-public@bogomips.org [1] http://public-inbox.org/
2014-01-29update EventMachine tests
EM 1.0.3 got released and seems to work under Ruby 2.1, so re-enable EM and NeverBlock tests again.
2014-01-17unicorn 4.8 compatibility + test version bumps
Internal reworking of unicorn 4.8.0 completely broke us(!). This commit fixes things, but it means we no longer support unicorn <= 4.7. Sorry about that.
2013-04-24test_isolate: update raindrops to 0.11.0
raindrops 0.11.0 was released several days ago and contains minor improvements + fixes.
2013-02-26bump unicorn dependency to 4.6.2+ for Ruby 2.0.0
This ensures we're compatible with the latest stable Ruby version.
2013-02-11hijacking support for Rack 1.5.x users
This requires Rack 1.5.x and unicorn 4.6.0 for hijacking support. Older versions of Rack continue to work fine, but we must use unicorn 4.6.0 features to support this.
2013-02-01tests: bump version dependencies for Isolate
Most of these test dependencies may be safely bumped.
2012-12-05test_isolate: bump eventmachine and sinatra deps
Always ensuring we work with the latest versions.
2012-07-01test_isolate: bump raindrops dependency
As usual, test with the latest released version to avoid surprises.
2012-05-09test_isolate: update deps for EM tests
async_sinatra and rack-fiber_pool had new versions since we last updated.
2012-05-09test_isolate: bump unicorn and kgio versions for testing
Users will pull the latest upstream, ensure things keep working.
2012-05-08tests: require sleepy_penguin 3.1.0 or later
We'll be making the XEpollThreadPool users depend on this, too.
2012-02-23t/test_isolate: update test dependencies
At least for the gems I'm most familiar with...
2011-08-20bump unicorn dependency version
We want the stricter parser the error log filtering in unicorn 4.1.0
2011-08-19t/test_isolate: bump kgio test version
We always try to test with the latest and greatest.
2011-08-12test_isolate: bump cool.io test version
Everything appears to work as expected under cool.io 1.1.0
2011-06-27bump dependencies (kgio, unicorn, raindrops)
We now rely on Unicorn 4.0.0. We'll use the latest kgio and raindrops versions anyways.
2011-06-22t/test_isolate: remove unneeded comment
That's been around forever, and we think Rubinius supports that...
2011-06-22t/test_isolate: drop Unicorn test dependency for now
It's already a runtime dependency
2011-06-09update various RubyGem dependencies
Gotta keep using the latest and greatest.
2011-05-21use and recommend sleepy_penguin 3.0.1
It's better under 1.9.3 (sleepy_penguin 3.0.1 was bogus)
2011-05-21use and recommend sleepy_penguin 3.0.0
It's better under 1.9.3
2011-05-17doc: recommend io_splice 4.1.1 or later
io_splice 4.1.1 works around issues with socket buffers filling up pipe buffers on blocking splice. See http://lkml.org/lkml/2009/1/13/478 for a better explanation.
2011-05-16add "copy_stream" config directive
This allows using IO::Splice.copy_stream from the "io_splice" RubyGem on recent Linux systems. This also allows users to disable copy_stream usage entirely and use traditional response_body.each calls which are compatible with all Rack servers (to workaround bugs in IO.copy_stream under 1.9.2-p180).
2011-05-08require kgio 2.4.0
kgio 2.4.0 has some 1.9.3dev fixes which affect us
2011-05-06test_isolate: update to latest raindrops and unicorn
Newer versions should be better
2011-04-21bump dependency to Unicorn 3.6.0
Might as well use the latest and greatest.
2011-03-15bump Unicorn dependency to 3.5.0
Latest and greatest :D
2011-03-10test_isolate: bump dependencies
New sendfile gem will give us IO#trysendfile. We might as well use and test the latest and greatest versions of everything else since thats what users pull in by default.
2011-02-04test_isolate: use latest Unicorn
It supports IPv6 and pulls in a better Kgio. Since Unicorn defaults to ":tcp_nopush => true", we need to flip it back to false to be compatible with the types of apps Rainbows! is targetted as.
2011-02-04epoll: handle EINTR properly in Ruby-space
We can't work around it effectively in the C extension itself. This requires the latest sleepy_penguin gem.
2011-02-04test_isolate: only load sleepy_penguin under Linux
It's Linux-only, after all
2011-01-24initial XAcceptEpoll concurrency model
Edge-triggered epoll concurrency model with blocking accept() in a (hopefully) native thread. This is recommended over Epoll for Ruby 1.9 users as it can workaround accept()-scalability issues on multicore machines.
2011-01-21epoll: use newer sleepy_penguin
We can eliminate the State module to simplify our code since 1.3.x keeps better track of things.
2011-01-19initial edge-triggered epoll model
Coolio and EventMachine only use level-triggered epoll, but being Rainbows!, we live on the EDGE!
2011-01-14tests: bump rack-fiber_pool version to 0.9.1
We always try to track the latest and greatest. We've also updated the test to actually test concurrency since rack-fiber_pool reuses recent fibers now.
2011-01-07test_isolate: bump versions and simplify
We can't possibly keep track of all sub-dependencies, so only declare primary dependencies until we find a known problem with a sub-dependency.
2011-01-07test_isolate: prevent concurrent execution
I realize this lock overly covers different versions of Ruby, but it's simple and we don't need to invoke isolate too often (we hope).
2011-01-07tests: bump async_sinatra dependency to 0.4.0
It's out and it works, so why not.
2011-01-07bump dependency on Rack to 1.2.1
We need to split out Cramp tests to Isolate to a different path, which sucks, but oh well. Cramp hasn't had a release in a while...
2011-01-05Bump unicorn dependency to 3.3.0
This means we can remove Time.now.httpdate in the next commit
2010-12-27initial cool.io support
Cool.io is the new name for Rev. We'll continue to support Rev until Cool.io breaks backwards compatibility. Rev may not be supported if Cool.io is.
2010-12-26bump Unicorn dependency
Unicorn 3.2.1 gives us an improved HttpParser#next? that preserves state until the next HttpParser#parse call.