qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adel Boutros <adelbout...@live.com>
Subject RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
Date Wed, 01 Jun 2016 13:22:04 GMT
Hello Justin,
I took a look at the appveyor link you sent and there 2 issues which I wanted to raise:In
your cmake, Proton is not found (Some of the tests are skipped or disabled)SWIG is not present
(I believe it is also used in the tests)
This is why you have only 12 total tests while I have 15 tests
The following tests FAILED:          4 - federation_tests (Failed)          5 - flow_control_tests
(Timeout)          8 - python_tests (Timeout)         13 - interlink_tests (Failed)      
  14 - interop_tests (Failed)         15 - windows_store_tests (Failed)
Regards,Adel
> Date: Tue, 31 May 2016 21:14:00 -0700
> Subject: Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> From: justin.ross@gmail.com
> To: users@qpid.apache.org
> 
> https://svn.apache.org/viewvc?view=revision&revision=1746375
> 
> I believe I've fixed the issues you've raised so far.  Now on to new ones.
> 
> In general, I won't have much time to work more on this in the near future,
> but I think we are closer to seeing real test failures as opposed to
> problems in the test scripting.
> 
> Latest results:
> https://ci.appveyor.com/project/ssorj/qpid-svn-reorg/build/hammerandtong.76
> 
> I had my test timeout set relatively low.  In other runs, the python_tests
> were also failing, not timing out.  I'm also now skipping the unit_tests
> because of the SSL issue I haven't been able to resolve.
> 
> The following tests FAILED:
>   4 - federation_tests (Failed)
>   5 - flow_control_tests (Timeout)
>   8 - python_tests (Timeout)
>   12 - windows_store_tests (Failed)
> Errors while running CTest
> 
> 4: run_federation_tests: Calling 'qpid-python-test --broker localhost:1760
> --time -m headers_federation -Dremote-port=1762'
> 4: headers_federation.HeadersFederationTests.test_dynamic_headers_unbind
> ... fail
> 4: Error during test: Traceback (most recent call last):
> 4: File "C:\projects\qpid-svn-reorg\build\python\bin\\qpid-python-test",
> line 340, in run
> 4: phase()
> 4: File
> "C:\projects\qpid-svn-reorg\build\cpp\src\tests\headers_federation.py",
> line 88, in test_dynamic_headers_unbind
> 4: self.verify_cleanup()
> 4: File
> "C:\projects\qpid-svn-reorg\build\cpp\src\tests\headers_federation.py",
> line 41, in verify_cleanup
> 4: self.fail("Bridges and links didn't clean up")
> 4: File "C:\Python27\lib\unittest\case.py", line 410, in fail
> 4: raise self.failureException(msg)
> 4: AssertionError: Bridges and links didn't clean up
> 4: Totals: 1 tests, 0 passed, 0 skipped, 0 ignored, 1 failed
> 
> 12: store.StoreTests.testDtxRecoverPrepared
> ................................. fail
> 12: Error during test: Traceback (most recent call last):
> 12: File "C:\projects\qpid-svn-reorg\build\python\bin\\qpid-python-test",
> line 340, in run
> 12: phase()
> 12: File "C:\projects\qpid-svn-reorg\build\cpp\src\tests\store.py", line
> 195, in testDtxRecoverPrepared
> 12: self.assert_(xid_matched)
> 12: File "C:\Python27\lib\unittest\case.py", line 422, in assertTrue
> 12: raise self.failureException(msg)
> 12: AssertionError: False is not true
> 
> On Tue, May 31, 2016 at 6:28 AM, Adel Boutros <adelboutros@live.com> wrote:
> 
> > Hello Justin,
> >
> >
> >
> > When do
> > you think you will have time to fix those issues?
> >
> >
> >
> > Regards,
> >
> > Adel
> > > From: adelboutros@live.com
> > > To: users@qpid.apache.org
> > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013
> > > Date: Fri, 27 May 2016 18:31:29 +0200
> > >
> > > In env.py.in, all libraries are ".so" extension which will not work on
> > Windows as you will need ".dll" instead
> > >
> > > _export_module("HA_LIB", join(BUILD_DIR, "src",
> > "ha.so"))_export_module("XML_LIB", join(BUILD_DIR, "src",
> > "xml.so"))_export_module("AMQP_LIB", join(BUILD_DIR, "src",
> > "amqp.so"))_export_module("TEST_STORE_LIB", join(BUILD_DIR, "src", "tests",
> > "test_store.so"))_export_module("STORE_LIB", join(BUILD_DIR, "src",
> > "linearstore.so"))
> > > > From: adelboutros@live.com
> > > > To: users@qpid.apache.org
> > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio
> > 2013
> > > > Date: Fri, 27 May 2016 17:49:46 +0200
> > > >
> > > > In qmf_tests, in brokertest.py, there is something wrong with the path
> > because the script cannot find "qpidd" executable. If you add the ".exe"
> > extension then it works.
> > > > I noticed that all other tests use "common.py" for qpidd. So why is
> > this test different?
> > > > Fixing the path makes the test pass and it fixes the same error in
> > other tests.
> > > > Error: AssertionError: executable not found: qpiddFix: qpidd_exec =
> > "qpidd.exe" (In brokertest.py)
> > > > Regards,Adel
> > > >
> > > > > Date: Fri, 27 May 2016 07:59:34 -0700
> > > > > Subject: Re: Qpid C++ 0.34 unit tests are failing with visual studio
> > 2013
> > > > > From: justin.ross@gmail.com
> > > > > To: users@qpid.apache.org
> > > > >
> > > > > Yeah, that's a simple bug on my end.  I'll get that fixed and report
> > back.
> > > > >
> > > > > On Fri, May 27, 2016 at 7:52 AM, Adel Boutros <adelboutros@live.com>
> > wrote:
> > > > >
> > > > > > Also, in env.ps1.in, there is a reference to "$builddir" but
it
> > never has
> > > > > > value so the tests needing PYTHON_DIR will always fail.
> > > > > > $PYTHON_DIR="$builddir\python" ---> is interpreted as "\python"
> > > > > > I think there is a missing link between "$builddir" and some
Cmake
> > > > > > variable.
> > > > > > > From: adelboutros@live.com
> > > > > > > To: users@qpid.apache.org
> > > > > > > Subject: RE: Qpid C++ 0.34 unit tests are failing with
visual
> > studio 2013
> > > > > > > Date: Fri, 27 May 2016 16:31:44 +0200
> > > > > > >
> > > > > > > Hello Justin,
> > > > > > > So I launched all the tests and I have 10 failing including
the
> > > > > > unit_tests (There is a disconnection error which I can also
see in
> > your
> > > > > > appveyor).
> > > > > > >
> > > > > > > The following tests FAILED:     4 - federation_tests (Failed)
> >  5 -
> > > > > > flow_control_tests (Timeout)        6 - ha_tests (Failed)  
9 -
> > > > > > python_tests (Failed)      11 - qmf_tests (Failed)         14
-
> > > > > > interlink_tests (Failed)   15 - interop_tests (Timeout)    16
-
> > store_tests
> > > > > > (Failed)       17 - store_tests_clfs (Failed)
> > > > > > > For the store_tests, powershell scripts in current directory
> > cannot be
> > > > > > launched as they are not trusted, so you should add ".\" prior
to
> > the
> > > > > > script name.
> > > > > > > C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
> > > > > > "run_store_tests.ps1" "MSSQL"The error message is helpful
> > > > > > actually:run_store_tests.ps1 : The term 'run_store_tests.ps1'
is
> > not
> > > > > > recognized as the name of a cmdlet, function... Suggestion
> > [3,General]: The
> > > > > > command run_store_tests.ps1 was not found, but does exist in
the
> > current
> > > > > > location. Windows PowerShell does not load commands from the
> > current
> > > > > > location by default. If you trust this command, instead type
> > > > > > ".\run_store_tests.ps1". See "get-help about_Command_Precedence"
> > for more
> > > > > > details.
> > > > > > > I am still debugging the other tests.
> > > > > > > Have you had a better luck than mine?
> > > > > > > I can send you the test logs if you like.
> > > > > > > PS: I am compiling with SASL/SSL disabled and valgrind
disabled
> > also
> > > > > > completely.
> > > > > > > Regards,Adel
> > > > > > > > From: adelboutros@live.com
> > > > > > > > To: users@qpid.apache.org
> > > > > > > > Subject: RE: Qpid C++ 0.34 unit tests are failing
with visual
> > studio
> > > > > > 2013
> > > > > > > > Date: Fri, 27 May 2016 12:02:40 +0200
> > > > > > > >
> > > > > > > > Please ignore my last email. There was a problem with
the PATH
> > > > > > environment variable.
> > > > > > > >
> > > > > > > > > From: adelboutros@live.com
> > > > > > > > > To: users@qpid.apache.org
> > > > > > > > > Subject: RE: Qpid C++ 0.34 unit tests are failing
with
> > visual studio
> > > > > > 2013
> > > > > > > > > Date: Fri, 27 May 2016 11:40:58 +0200
> > > > > > > > >
> > > > > > > > > Hello Justin,
> > > > > > > > > I updated to the head of the trunk and relaunched
> > everything. I
> > > > > > still have a problem with the qpid tools.I can see all the bat
> > files, but
> > > > > > the code still calls the original files for example:
> > > > > > > > > 1: run_acl_tests: Calling 'qpid-python-test --broker
> > localhost:63666
> > > > > > --time -m acl -Dport-i=63668 -Dport-u=63710 -Dport-q=63712
> > > > > >
> > -Dpolicy-file=D:\qpid-cpp-trunk.git\qpid\qpid\cpp\build-dir-RelWithDebInfo\src\tests\policy.acl'1:
> > > > > > 'qpid-python-test' is not recognized as an internal or external
> > command,
> > > > > > > > > All the .py files have not been updated to launch
> > > > > > qpid-python-test.bat when on windows:Example:
> > > > > > qpid/cpp/src/tests/run_interop_testscall("qpid-python-test -m
> > interop_tests
> > > > > > -DOUTDIR={0}", WORK_DIR)
> > > > > > > > > Regards,Adel
> > > > > > > > > > Date: Thu, 26 May 2016 15:02:59 -0700
> > > > > > > > > > Subject: Re: Qpid C++ 0.34 unit tests are
failing with
> > visual
> > > > > > studio 2013
> > > > > > > > > > From: justin.ross@gmail.com
> > > > > > > > > > To: users@qpid.apache.org
> > > > > > > > > >
> > > > > > > > > > An update.  I think I've fixed the python
and backslash
> > problems.
> > > > > > > > > >
> > > > > > > > > >   https://issues.apache.org/jira/browse/QPID-7281
> > > > > > > > > >
> > > > > > > > > > Here's what I get now in appveyor:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > >
> > https://ci.appveyor.com/project/ssorj/qpid-svn-reorg/build/hammerandtong.71
> > > > > > > > > >
> > > > > > > > > > The unit_test failure is one I've had for
a long time.
> > I've not
> > > > > > yet been
> > > > > > > > > > able to convince either appveyor to use
"localhost" for its
> > > > > > hostname or
> > > > > > > > > > unit_test to use "appveyor-vm" as its ssl
cert name.  So
> > it times
> > > > > > out.
> > > > > > > > > >
> > > > > > > > > > The other tests are running now, with some
failures.  Note
> > that up
> > > > > > to now
> > > > > > > > > > I've been liberal in enabling the cross-platform
tests
> > that can
> > > > > > > > > > hypothetically work in windows.  There may
be specific
> > instances
> > > > > > where I'm
> > > > > > > > > > wrong, and we'll need to adjust the target
platform for
> > the test.
> > > > > > > > > >
> > > > > > > > > > On Thu, May 26, 2016 at 9:45 AM, Andrew
Stitcher <
> > > > > > astitcher@redhat.com>
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > On Thu, 2016-05-26 at 09:38 -0700,
Justin Ross wrote:
> > > > > > > > > > > > I tried this approach first. 
I wasn't able to make
> > that
> > > > > > > > > > > > configuration
> > > > > > > > > > > > available in CTestCustom.cmake
when I tried last.
> > However, I
> > > > > > don't
> > > > > > > > > > > > think I
> > > > > > > > > > > > tried repeating the find_package
logic directly in the
> > > > > > custom.cmake
> > > > > > > > > > > > file,
> > > > > > > > > > > > which I will do.
> > > > > > > > > > >
> > > > > > > > > > > CMake is hierarchical so the find_package()
would need
> > to be in
> > > > > > a CMake
> > > > > > > > > > > file above the relevant one (and perhaps
in the sequence
> > before
> > > > > > the
> > > > > > > > > > > add_directory(..) or include(...) that
includes the file
> > you
> > > > > > want the
> > > > > > > > > > > definition in - I'm not too clear about
that point.
> > > > > > > > > > >
> > > > > > > > > > > Andrew
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > > > > > > To unsubscribe, e-mail:
> > users-unsubscribe@qpid.apache.org
> > > > > > > > > > > For additional commands, e-mail:
> > users-help@qpid.apache.org
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > >
> > >
> >
> >
 		 	   		  
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message