Guys,
I am still don't know why i am not having test(s) running correctly!!!, the
whole soln builds nicely, i have Qt for VS2008 and the VS addin as well, but
i am still getting this when running the tests
------ Build started: Project: RUN_TESTS, Configuration: Debug Win32 ------
Performing Post-Build Event...
Test project C:/PySide/apiextractor
Start 1: testabstractmetaclass
1/17 Test #1: testabstractmetaclass ............***Exception: SegFault
0.01 sec
Start 2: testabstractmetatype
2/17 Test #2: testabstractmetatype .............***Exception: SegFault
0.01 sec
Start 3: testaddfunction
3/17 Test #3: testaddfunction ..................***
Exception: SegFault 0.01 sec
Start 4: testcodeinjection
4/17 Test #4: testcodeinjection ................***Exception: SegFault
0.01 sec
Start 5: testconversionoperator
5/17 Test #5: testconversionoperator ...........***Exception: SegFault
0.01 sec
Start 6: testconversionruletag
6/17 Test #6: testconversionruletag ............***Exception: SegFault
0.01 sec
Start 7: testdtorinformation
7/17 Test #7: testdtorinformation ..............***Exception: SegFault
0.01 sec
Start 8: testenum
8/17 Test #8: testenum .........................***Exception: SegFault
0.01 sec
Start 9: testimplicitconversions
9/17 Test #9: testimplicitconversions ..........***Exception: SegFault
0.01 sec
Start 10: testmodifydocumentation
10/17 Test #10: testmodifydocumentation ..........***Exception: SegFault
0.01 sec
Start 11: testmodifyfunction
11/17 Test #11: testmodifyfunction ...............***Exception: SegFault
0.01 sec
Start 12: testmultipleinheritance
12/17 Test #12: testmultipleinheritance ..........***Exception: SegFault
0.01 sec
Start 13: testrefcounttag
13/17 Test #13: testrefcounttag ..................***Exception: SegFault
0.01 sec
Start 14: testreferencetopointer
14/17 Test #14: testreferencetopointer ...........***Exception: SegFault
0.01 sec
Start 15: testremoveimplconv
15/17 Test #15: testremoveimplconv ...............***Exception: SegFault
0.01 sec
Start 16: testreverseoperators
16/17 Test #16: testreverseoperators .............***Exception: SegFault
0.01 sec
Start 17: testtoposort
17/17 Test #17: testtoposort .....................***Exception: SegFault
0.01 sec
0% tests passed, 17 tests failed out of 17
Total Test time (real) = 0.19 sec
The following tests FAILED:
1 - testabstractmetaclass (SEGFAULT)
2 - testabstractmetatype (SEGFAULT)
3 - testaddfunction (SEGFAULT)
4 - testcodeinjection (SEGFAULT)
5 - testconversionoperator (SEGFAULT)
6 - testconversionruletag (SEGFAULT)
7 - testdtorinformation (SEGFAULT)
8 - testenum (SEGFAULT)
9 - testimplicitconversions (SEGFAULT)
10 - testmodifydocumentation (SEGFAULT)
11 - testmodifyfunction (SEGFAULT)
12 - testmultipleinheritance (SEGFAULT)
13 - testrefcounttag (SEGFAULT)
14 - testreferencetopointer (SEGFAULT)
15 - testremoveimplconv (SEGFAULT)
16 - testreverseoperators (SEGFAULT)
17 - testtoposort (SEGFAULT)
Errors while running CTest
Project : error PRJ0019: A tool returned an error code from "Performing
Post-Build Event..."
Build log was saved at
"file://c:\PySide\apiextractor\RUN_TESTS.dir\Debug\BuildLog.htm"
RUN_TESTS - 1 error(s), 0 warning(s)
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
also when trying to run any single test in Debug mode, (Debug win32), i get
a message saying that i don't have Qtxxxd.dll --means no Qt built for
debgugging--
i am not sure if there's any thing i am missing???
On Tue, Mar 30, 2010 at 7:01 PM, Hugo Parente Lima
<[email protected]>wrote:
> On Tuesday 30 March 2010 12:07:30 Catalin Iacob wrote:
> > On Tue, Mar 30, 2010 at 4:36 PM, Hugo Parente Lima
> >
> > <[email protected]> wrote:
> > > On Tuesday 30 March 2010 07:43:21 Abdullah Abouzekry wrote:
> > >> I have followed the steps you defined, and successfully installed
> > >> everything and got a VS2008 Project which when built in debug/release
> > >> mode everything is fine, but it looks like i need Qt built for
> > >> debugging to be able to run the tests in debug mode?
> >
> > Qt for Visual Studio comes with Debug dlls: QtCored.dll for Debug
> > versus QtCore.dll for Release etc. CMake correctly picks the correct
> > one for your current configuration.
> >
> > If you have a working build you should try running the tests and
> > report what you get.
> >
> > >> am i doing smth wrong?
> > >
> > > I think not, any other test failed? or just the one reported by you in
> > > previous email?
> >
> > We're two different persons :). Abdullah asked on the list what he
> > should do to port PySide to Windows, you replied, I saw your reply,
> > compiled it and then I reported the tests failing.
>
> Oops, memory fail, sorry =]
>
> > Catalin
> > _______________________________________________
> > PySide mailing list
> > [email protected]
> > http://lists.openbossa.org/listinfo/pyside
>
> --
> Hugo Parente Lima
> INdT - Instituto Nokia de Tecnologia
>
> _______________________________________________
> PySide mailing list
> [email protected]
> http://lists.openbossa.org/listinfo/pyside
>
>
--
Abdullah Abouzekry
_______________________________________________
PySide mailing list
[email protected]
http://lists.openbossa.org/listinfo/pyside
