Yeah, this is a bug in the testing suite not in your particular build. You can safely ignore those. Hopefully we can push fixed tests shortly.

I'm having some problems when testing my nox build. I downloaded it from the git repository, and configured --with python 2.5 and --with openflow When running the "nox_core tests" I get the exact same message as Brandon (quoted below):


(Quoting Brandon Heller's previous message: )

*********************************************************************************************************

"Hi,

I downloaded nox 0.4.0 on a Debian unstable system, and 4 of the assertions
and 4 of the tests don't pass.

I couldn't find any text on failed assertions.  Here are the tests that
fail:

Running 80 test cases...
*****************../../../../../src/nox/apps/tests/tests.cc(220): fatal
error in "nox.apps.tests.pyunittests.webservice_test.run_test": Traceback
(failure with no frames): <class
'twisted.internet.error.ConnectionRefusedError'>: Connection was refused by
other side: 111: Connection refused.

********************../../../../../src/nox/apps/tests/tests.cc(220): fatal
error in "nox.apps.tests.pyunittests.componentws_test.check_version":
Traceback (failure with no frames): <class
'twisted.internet.error.ConnectionRefusedError'>: Connection was refused by
other side: 111: Connection refused.

../../../../../src/nox/apps/tests/tests.cc(220): fatal error in
"nox.apps.tests.pyunittests.componentws_test.check_uptime": Traceback
(failure with no frames): <class
'twisted.internet.error.ConnectionRefusedError'>: Connection was refused by
other side: 111: Connection refused.

*../../../../../src/nox/apps/tests/tests.cc(220): fatal error in
"nox.apps.tests.pyunittests.componentws_test.check_components": Traceback
(failure with no frames): <class
'twisted.internet.error.ConnectionRefusedError'>: Connection was refused by
other side: 111: Connection refused.

******00466|topology|WARN:Add link to unknown datapath 2 - adding default
entry.
00467|topology|WARN:Add internal to unknown datapath 3 - adding default
entry.
00468|topology|WARN:Add link to unknown datapath 1 - adding default entry.
*******

Test suite "NOX" failed with:
  242 assertions out of 246 passed
  4 assertions out of 246 failed
  76 test cases out of 80 passed
  4 test cases out of 80 failed
  4 test cases out of 80 aborted


Any ideas?

-Brandon
"

*********************************************************************************************************
(/quote)


I'll post some additional info which is probably relevant and might help:

When I tried the next the next step of noxrepo.org/manual <http://noxrepo.org/manual> ( ./nox_core -v -i pgen:10 packetdump ) I got:

------------------------------------------------------------------------------------------
00001|packetgen|DBG:waiting for features request
00002|packetgen|DBG:waiting for features request
...
...   /(this went on for 5 secs)/
...
01599|packetgen|DBG:waiting for features request
01600|packetgen|DBG:waiting for features request
01601|packetgen|DBG:waiting for features request
01602|packetgen|DBG:waiting for features request
01603|packetgen|DBG:waiting for features request
01604|packetgen|DBG:waiting for features request
01605|nox|WARN:pgen:: closing connection due to timeout after 5 seconds in sending features request state
------------------------------------------------------------------------------------------


I moved on with the guide and tried to set up nox with openflow, setting up the switch looked ok:

-----------------------------------------------------------------------------------------
hda:/cdrom# ./dpctl addif nl:0 eth0
eth0: link up, 100Mbps, full-duplex, lpa 0x05E1
device eth0 entered promiscuous mode
send_openflow_skb: send failed: -3 <-------(I'm not sure if this is supposed to be here, i guess not)

hda:/cdrom# ./dpctl addif nl:0 eth1
eth1: link up, 100Mbps, full-duplex, lpa 0x05E1
device eth1 entered promiscuous mode
send_openflow_skb: send failed: -3                         <-------(same)

hda:/cdrom# ./dpctl show nl:0
features_reply (xid=36c3c26e):dp id:505400000003
tables: exact:131072, compressed:0, general:100
buffers: size:-1, number:256
features: capabilities:0x17, actions:0xff
0(eth0): addr:50:54:00:00:00:03, speed:100, flags:0, feat:0xf
1(eth1): addr:50:54:00:00:00:04, speed:100, flags:0, feat:0xf
LOCAL(of0): addr:3a:7e:bd:e6:fc:7a, speed:0, flags:0, feat:0
get_config_reply (xid=f93e7de): miss_send_len=128
hda:/cdrom#

------------------------------------------------------------------------------


and the same problem reflected when I tried to connect the controller with the switch :


[NOX screen]:
--------------------------------------------------------------------------------------
(initialization ommited but looked fine)
...
00028|openflow|DBG:Passive tcp interface bound to port 2525
00029|openflow|DBG:Passive tcp interface received connection
00030|nox|WARN:stream: closing connection due to timeout after 5 seconds in sending features request state
00031|openflow|DBG:Passive tcp interface received connection
00032|nox|WARN:stream: closing connection due to timeout after 5 seconds in sending features request state
00033|openflow|DBG:Passive tcp interface received connection
00034|nox|WARN:stream: closing connection due to timeout after 5 seconds in sending features request state
00035|openflow|DBG:Passive tcp interface received connection
00036|openflow|WARN:stream: connection closed by peer <---(this was when i sent Ctrl^C to the openflow switch (screen below)
00037|nox|WARN:Error sending features request: Unknown error 4294967295
--------------------------------------------------------------------------------------

[openflow switch screen]:
--------------------------------------------------------------------------------------
hda:/cdrom# ./secchan nl:0 tcp:10.0.2.2:2525 <http://10.0.2.2:2525>
00001|rconn|WARN:nl:0: connected
00002|rconn|WARN:tcp:10.0.2.2:2525 <http://10.0.2.2:2525>: connected
00003|rconn|WARN:tcp:10.0.2.2:2525 <http://10.0.2.2:2525>: connection closed
00004|rconn|WARN:tcp:10.0.2.2:2525 <http://10.0.2.2:2525>: connected
00005|rconn|WARN:tcp:10.0.2.2:2525 <http://10.0.2.2:2525>: connection closed
00006|rconn|WARN:tcp:10.0.2.2:2525 <http://10.0.2.2:2525>: connected
00007|rconn|WARN:tcp:10.0.2.2:2525 <http://10.0.2.2:2525>: connection closed
00008|rconn|WARN:tcp:10.0.2.2:2525 <http://10.0.2.2:2525>: connected
Ctrl^C
--------------------------------------------------------------------------------------


Has anyone come across any similar problem?
Any input appreciated

Regards,
Kyriakos


------------------------------------------------------------------------

_______________________________________________
nox-dev mailing list
[email protected]
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org


_______________________________________________
nox-dev mailing list
[email protected]
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org

Reply via email to