Displaying 5 results from an estimated 5 matches for "test_worker".
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
Hi!
In some cases the use of blockaddress() crashes llc.
I've attached two test-cases, one that crashes and for reference a slightly modified one (just 2 lines are commented) that works.
I compile the files with
# llvm-as test_crash.ll -o - | llc -f -o temp.s -
and get
0 llc 0x0000000000c6ab6f
1 llc 0x0000000000c6b38d
2 libpthread.so.0 0x00007feccd2270f0
3
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 wh...
2006 Mar 01
1
maddening intermittent failures in unit tests with "working" code
Hi all,
This testing problem has been a sink for time today, and is still unresolved.
Basically I have some unit tests that test simple functions (example below)
that depend on join operations in a habtm relationship, and I suspect I am
getting "false" failures, i.e ones that do not logically make any sense. I
need fresh sets of eyes to take a look and see if I''m mising