Verification lemma crashes on test

[sjunnesson]

I have put together a Unity Lemma for a project we have here and is now trying to run some tests to verify that it works according to Noam standards using lemma_verification host.

My process is that I prepare to register for event "Echo" in my code, launch my code, it detects the MarcoPolo messages and connects to the TCP server but that crashes the host with below message. Is my process wrong?

ch-m-dsjunnesson:host dsjunnesson$ bundle exec bin/lemma_verification
[2014-10-15 16:46:17] [LemmaVerification ] [INFO] Join room lemma_verification to begin testing
/Users/dsjunnesson/.rvm/gems/ruby-2.1.0@noam/gems/eventmachine-1.0.3/lib/em/pure_ruby.rb:654:in connect_nonblock': Can't assign requested address - connect(2) for 127.0.0.1 (Errno::EADDRNOTAVAIL) from /Users/dsjunnesson/.rvm/gems/ruby-2.1.0@noam/gems/eventmachine-1.0.3/lib/em/pure_ruby.rb:654:inconnect'
from /Users/dsjunnesson/.rvm/gems/ruby-2.1.0@noam/gems/eventmachine-1.0.3/lib/em/pure_ruby.rb:81:in bind_connect_server' from /Users/dsjunnesson/.rvm/gems/ruby-2.1.0@noam/gems/eventmachine-1.0.3/lib/em/pure_ruby.rb:76:inconnect_server'
from /Users/dsjunnesson/.rvm/gems/ruby-2.1.0@noam/gems/eventmachine-1.0.3/lib/eventmachine.rb:664:in bind_connect' from /Users/dsjunnesson/.rvm/gems/ruby-2.1.0@noam/gems/eventmachine-1.0.3/lib/eventmachine.rb:640:inconnect'
from /Users/dsjunnesson/Documents/Github/noam/host/lib/noam_server/ear.rb:48:in make_new_outgoing_connection' from /Users/dsjunnesson/Documents/Github/noam/host/lib/noam_server/ear.rb:22:ininitialize'
from /Users/dsjunnesson/Documents/Github/noam/host/lemma_verification/test_tcp_message_handler.rb:30:in new' from /Users/dsjunnesson/Documents/Github/noam/host/lemma_verification/test_tcp_message_handler.rb:30:inregister_test_participant'
from /Users/dsjunnesson/Documents/Github/noam/host/lemma_verification/test_tcp_message_handler.rb:17:in message_received' from /Users/dsjunnesson/Documents/Github/noam/host/lemma_verification/test_tcp_server.rb:16:inblock in post_init'
from /Users/dsjunnesson/Documents/Github/noam/host/lib/noam/tcp_listener.rb:46:in call' from /Users/dsjunnesson/Documents/Github/noam/host/lib/noam/tcp_listener.rb:46:inmessage_complete'
from /Users/dsjunnesson/Documents/Github/noam/host/lib/noam/tcp_listener.rb:40:in read_payload' from /Users/dsjunnesson/Documents/Github/noam/host/lib/noam/tcp_listener.rb:19:inreceive_data'
from /Users/dsjunnesson/Documents/Github/noam/host/lemma_verification/test_tcp_server.rb:21:in receive_data' from /Users/dsjunnesson/.rvm/gems/ruby-2.1.0@noam/gems/eventmachine-1.0.3/lib/eventmachine.rb:1484:inevent_callback'
from /Users/dsjunnesson/.rvm/gems/ruby-2.1.0@noam/gems/eventmachine-1.0.3/lib/em/pure_ruby.rb:544:in block in eventable_read' from /Users/dsjunnesson/.rvm/gems/ruby-2.1.0@noam/gems/eventmachine-1.0.3/lib/em/pure_ruby.rb:542:intimes'
from /Users/dsjunnesson/.rvm/gems/ruby-2.1.0@noam/gems/eventmachine-1.0.3/lib/em/pure_ruby.rb:542:in eventable_read' from /Users/dsjunnesson/.rvm/gems/ruby-2.1.0@noam/gems/eventmachine-1.0.3/lib/em/pure_ruby.rb:369:inblock in crank_selectables'
from /Users/dsjunnesson/.rvm/gems/ruby-2.1.0@noam/gems/eventmachine-1.0.3/lib/em/pure_ruby.rb:369:in each' from /Users/dsjunnesson/.rvm/gems/ruby-2.1.0@noam/gems/eventmachine-1.0.3/lib/em/pure_ruby.rb:369:incrank_selectables'
from /Users/dsjunnesson/.rvm/gems/ruby-2.1.0@noam/gems/eventmachine-1.0.3/lib/em/pure_ruby.rb:324:in block in run' from /Users/dsjunnesson/.rvm/gems/ruby-2.1.0@noam/gems/eventmachine-1.0.3/lib/em/pure_ruby.rb:318:inloop'
from /Users/dsjunnesson/.rvm/gems/ruby-2.1.0@noam/gems/eventmachine-1.0.3/lib/em/pure_ruby.rb:318:in run' from /Users/dsjunnesson/.rvm/gems/ruby-2.1.0@noam/gems/eventmachine-1.0.3/lib/em/pure_ruby.rb:62:inrun_machine'
from /Users/dsjunnesson/.rvm/gems/ruby-2.1.0@noam/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in run' from /Users/dsjunnesson/Documents/Github/noam/host/lemma_verification/test_main.rb:14:instart'
from bin/lemma_verification:62:in `

'

[dougbradbury]

It looks like the Noam host throws an error when trying to make the reverse connection back to the Lemma's TCP server. I'm curious as to what port came back to the server in the polo message.

You might see this error if the port was '0' or possibly some other restricted port number.

At any rate, it would be nice to get better feedback while integrating than this exception.