search for: test_work

Displaying 5 results from an estimated 5 matches for "test_work".

Did you mean: test_word
2006 Jun 15
5
Cannot invoke ActiveRecord subclass accessors in DRb worker
Hi there, I''m trying to create a worker to do some asynchronous web client work and update the data model with its results. It seems, however, that every call I make to an ActiveRecord subclass causes the whole thing to block. At least I think it''s blocked. Right now I''m just using debug log output. Is there a decent way to debug/test workers I can try? Is there any
2007 Jan 23
1
Getting results from a dead worker. example?
...#39;d be very grateful. My test worker: class TestWorker < BackgrounDRb::Worker::RailsBase def do_work(args) results[:done_with_do_work] = true self.delete end end TestWorker.register My rake task: task :tester => :environment do k=MiddleMan.new_worker( :class => :test_worker ) sleep 1 # the worker will die during this pause # next line gives a nil object error puts "done_with_do_work=#{MiddleMan.worker(k).results [:done_with_do_work]||"not available"}" end
2010 Mar 19
2
[LLVMdev] Use of blockadress() crashes llc in some cases
...m arguments: llc -f -o temp.s - 1. Running pass 'Optimize for code generation' on function '@reduce_graph' Segmentation fault I'm using the svn-version, revision 98581. Regards, Sebastian -------------- next part -------------- A non-text attachment was scrubbed... Name: test_working.ll Type: text/assembler-file Size: 422 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100319/997b1809/attachment.bin> -------------- next part -------------- A non-text attachment was scrubbed... Name: test_crash.ll Type: text/assembler-file Size: 42...
2008 Mar 20
2
can''t call any methods on workers
...config: :backgroundrb: :port: 11006 # port to start listen :ip: 0.0.0.0 # host to listen :environment: development # rails environment to load :log: foreground # foreground mode,print log messages on console And I can start my test worker. However, whenever I call any method on my test_worker, I get this error in backgroundrb_11006_debug.log: 00000004{:worker_method:process_batch: type: do_work worker_methodprocess_batchtypedo_work You have a nil object when you didn''t expect it! The error occurred...
2006 Mar 01
1
maddening intermittent failures in unit tests with "working" code
...ciated Zimp objects # Zimp and User are AR classes mapped to MySQL schema shown later below. count = 0 self.zimps.each { |x| count += x.reserved.to_i } count end A typical unit test for this function would be to create a User object and call the function, and check the return result def test_working @user=User.find(:first) assert_equal 2, @user.reservations end For the test data loaded from the fixtures below, two records should be returned, and the result should be 2. 90% of the time in testing this is what happens. But sometimes this will fail with a result of zero (no matching...