Hi-
I started looking at the same test failure on ppc64le. I found in my
logs:
"clustered database server has not yet joined cluster; trying another
server"
I found the same messsage in Lance's logs, so it could be the same
issue.
I made the following change to check that the cluster was up and running
before running the test.
diff --git a/tests/ovsdb-idl.at b/tests/ovsdb-idl.at
index cc38d69c1..5484fd4c5 100644
--- a/tests/ovsdb-idl.at
+++ b/tests/ovsdb-idl.at
@@ -1802,6 +1802,9 @@ m4_define([OVSDB_CHECK_IDL_LEADER_ONLY_PY],
PARSE_LISTENING_PORT([s2.log], [TCP_PORT_1])
PARSE_LISTENING_PORT([s3.log], [TCP_PORT_2])
PARSE_LISTENING_PORT([s1.log], [TCP_PORT_3])
+ OVS_WAIT_UNTIL([../../../ovsdb/ovsdb-tool check-cluster ./s1.db])
+ OVS_WAIT_UNTIL([../../../ovsdb/ovsdb-tool check-cluster ./s2.db])
+ OVS_WAIT_UNTIL([../../../ovsdb/ovsdb-tool check-cluster ./s3.db])
remotes=tcp:LPBK:$TCP_PORT_1,tcp:LPBK:$TCP_PORT_2,tcp:LPBK:$TCP_PORT_3
pids=$(cat s2.pid s3.pid s1.pid | tr '\n' ',')
echo $pids
This corrected the problem initially, however on Travis the problem
returned intermittently, so I did not submit until I could look further.
I hope this helps.
Regards
David Wilder
On 2019-11-21 17:51, Lance Yang (Arm Technology China) wrote:
Hi Ben,
Thanks for your reply.
I checked the original email I sent. I did attach the logs in my
previous email. However, as you said, they might be stripped
automatically.
At this time, I compress everything into a zip file. I am not sure
whether it would be stripped again. So I also attach a link where you
can find the related logs:
https://urldefense.proofpoint.com/v2/url?u=https-3A__1drv.ms_u_s-21Atj0ulDEFFyaj1ds2QyEmPMkRM9s-3Fe-3DIfr7l9&d=DwIFAg&c=jf_iaSHvJObTbx-siA1ZOg&r=7ndxyKjH9UrBD68Us2WP1wI4BwEBQbeAyz8i_vwCCaI&m=s9G46xQhkGSnSnZ64KeJqqxbxW8T4x8oC7cIXwZmm68&s=tWpvdvTFaHLkSQpOqJO8B0Qtj6runK-eQvnxwsAhz18&e=
.
For convenience, I also copied the original email content as below in
case that you did not receive the complete message:
I encountered an issue when I was running testsuite on Arm.
The system I tested on was an arm server running Ubuntu 18.04.3 LTS
(GNU/Linux 4.15.0-65-generic aarch64).
After I downloaded the up-to-date source code on master branch and
built ovs, I run the testsuite with TESTSUITEFLAGS="2105" (Unit case
name: Check Python IDL reconnects to leader) I run the unit case for
many times, most of the time I got the following failure:
make check TESTSUITEFLAGS="2105" RECHECK=yes
make check-recursive
make[1]: Entering directory '/home/lance/ovs'
Making check in datapath
make[2]: Entering directory '/home/lance/ovs/datapath'
make[3]: Entering directory '/home/lance/ovs/datapath'
make[3]: Leaving directory '/home/lance/ovs/datapath'
make[2]: Leaving directory '/home/lance/ovs/datapath'
make[2]: Entering directory '/home/lance/ovs'
make[3]: Entering directory '/home/lance/ovs/datapath'
make[3]: 'distfiles' is up to date.
make[3]: Leaving directory '/home/lance/ovs/datapath'
make utilities/ovs-appctl-bashcomp.bash
utilities/ovs-vsctl-bashcomp.bash tests/atlocal
make[3]: Entering directory '/home/lance/ovs'
make[3]: Nothing to be done for 'utilities/ovs-appctl-bashcomp.bash'.
make[3]: Nothing to be done for 'utilities/ovs-vsctl-bashcomp.bash'.
make[3]: 'tests/atlocal' is up to date.
make[3]: Leaving directory '/home/lance/ovs'
make check-local
make[3]: Entering directory '/home/lance/ovs'
set /bin/bash './tests/testsuite' -C tests
AUTOTEST_PATH=utilities:vswitchd:ovsdb:vtep:tests::; \
"$@" -j2 2104-2105 || (test X'' = Xyes && "$@" --recheck)
## ------------------------------- ##
## openvswitch 2.12.90 test suite. ##
## ------------------------------- ##
2105: Check Python IDL reconnects to leader - Python3 (leader only)
FAILED (ovsdb-idl.at:1816)
## ------------- ##
## Test results. ##
## ------------- ##
ERROR: All 1 test was run,
1 failed unexpectedly.
## -------------------------- ##
## testsuite.log was created. ##
## -------------------------- ##
Please send `tests/testsuite.log' and all information you think might
help:
To: <b...@openvswitch.org>
Subject: [openvswitch 2.12.90] testsuite: 2105 failed
You may investigate any problem if you feel able to do so, in which
case the test suite provides a good starting point. Its output may
be found below `tests/testsuite.dir'.
## ------------------------------- ##
2105: Check Python IDL reconnects to leader - Python3 (leader only)
FAILED (ovsdb-idl.at:1816)
## ------------- ##
## Test results. ##
## ------------- ##
ERROR: 1 test was run,
1 failed unexpectedly.
## -------------------------- ##
## testsuite.log was created. ##
## -------------------------- ##
Please send `tests/testsuite.log' and all information you think might
help:
To: <b...@openvswitch.org>
Subject: [openvswitch 2.12.90] testsuite: 2105 failed
You may investigate any problem if you feel able to do so, in which
case the test suite provides a good starting point. Its output may
be found below `tests/testsuite.dir'.
Makefile:6151: recipe for target 'check-local' failed
make[3]: *** [check-local] Error 1
make[3]: Leaving directory '/home/lance/ovs'
Makefile:5275: recipe for target 'check-am' failed
make[2]: *** [check-am] Error 2
make[2]: Leaving directory '/home/lance/ovs'
Makefile:4984: recipe for target 'check-recursive' failed
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory '/home/lance/ovs'
Makefile:5278: recipe for target 'check' failed
make: *** [check] Error 2
I attached the tests/testsuite.dir/testsuite.log to this email. I
also attached the logs for ovsdb. Any hints on what is wrong here?
Thank you so much.
Best regards,
Lance Yang
-----Original Message-----
From: Ben Pfaff <b...@ovn.org>
Sent: Friday, November 22, 2019 9:10 AM
To: Lance Yang (Arm Technology China) <lance.y...@arm.com>
Cc: b...@openvswitch.org; ovs-dev@openvswitch.org;
ted.elhour...@nutanix.com
Subject: Re: [ovs-dev] [bug-report] Check Python IDL reconnects to
leader unit case failed
on arm64
On Thu, Nov 21, 2019 at 07:54:09AM +0000, Lance Yang (Arm Technology
China) wrote:
> Hi,
> I encountered an issue when I was running testsuite on Arm.
> The system I tested on was an arm server running Ubuntu 18.04.3 LTS (GNU/Linux
4.15.0-65-generic aarch64).
> After I downloaded the up-to-date source code on master branch and built ovs,
I run the
testsuite with TESTSUITEFLAGS="2105" (Unit case name: Check Python IDL
reconnects to
leader) I run the unit case for many times, most of the time I got the
following failure:
Thanks for the report.
I don't see the attachment. Maybe you forgot to include it, or maybe
the stripped it.
Please try again?
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended
recipient, please notify the sender immediately and do not disclose
the contents to any other person, use it for any purpose, or store or
copy the information in any medium. Thank you.
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddiscuss&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=7ndxyKjH9UrBD68Us2WP1wI4BwEBQbeAyz8i_vwCCaI&m=s9G46xQhkGSnSnZ64KeJqqxbxW8T4x8oC7cIXwZmm68&s=OPwYR664vlglBddM-LBT-cBZMxtzTjQA0GI-blJZyFY&e=
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
