This project is archived and is in readonly mode.
Thread Scheduling Problem in FragmentCachingTest#test_fragment_for_logging
Reported by Matthias Hennemeyer | December 1st, 2009 @ 04:48 PM
In actionpack/test/controller/caching_test.rb:633
Using Ruby 1.9.1p243, this test fails on the last assertion, because when testing the local events array to contain the triggered events, the queue thread (see activesupport/lib/active_support/notifications/fanout.rb:85) that pushes the events to the local events array hasn't yet been scheduled.
Draining the Notifications Queue by sending #wait to the current notifier object (through ActiveSupport::Notifications.notifier.wait) fixes this problem.
Comments and changes to this ticket
-
Matthias Hennemeyer December 1st, 2009 @ 05:01 PM
- Tag changed from notifications, patch, testing to edge, notifications, patch, testing
-
Rohit Arondekar October 6th, 2010 @ 06:27 AM
- Importance changed from to
Marking ticket as stale. If this is still an issue please make a comment with suggested changes, creating a patch with tests, or rebasing an existing patch or just confirming the issue on latest releases/master.
-
Rohit Arondekar October 6th, 2010 @ 06:27 AM
- State changed from new to stale
-
Matthias Hennemeyer October 6th, 2010 @ 07:43 AM
- Assigned user set to Rohit Arondekar
Just trash it. The test has been changed and the assertion
that was failing for the specific Ruby version has been removed....And the specific Ruby version will not be supported (I wasn't aware of that fact in late 2009).
-
Rohit Arondekar October 6th, 2010 @ 08:28 AM
It's as good as closed since it's already marked as stale. Thank you for replying though! :)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>