#1401: t/library/pcre.t:  Test #2 failing on MSWin32
---------------------+------------------------------------------------------
 Reporter:  jkeenan  |       Owner:       
     Type:  bug      |      Status:  new  
 Priority:  normal   |   Milestone:       
Component:  library  |     Version:  1.9.0
 Severity:  medium   |    Keywords:       
     Lang:           |       Patch:       
 Platform:  win32    |  
---------------------+------------------------------------------------------

Comment(by ronaldws):

 Replying to [comment:17 fperrad]:
 > Replying to [comment:16 ronaldws]:
 > > Replying to [comment:15 ronaldws]:
 > > > Replying to [comment:12 fperrad]:
 > > > > I obtain the following output :
 > > > > ...
 > > > > > gdb -args parrot.exe t/library/pcre_2.pir
 > > > > GNU gdb (GDB) 7.1
 > > > > (gdb) r
 > > > > ok 1
 > > > > ok 2
 > > > > ok 3
 > > > > not ok 4
 > > > > not ok 5
 > > > >
 > I obtain :
 >
 > {{{
 > > prove -v t\library\pcre.t
 > t\library\pcre.t ..
 > 1..2
 > ok 1 - libpcre loading
 >
 > not ok 2 - soup to nuts
 > #   Failed test 'soup to nuts'
 > #   at t\library\pcre.t line 104.
 > #          got: 'ok 1
 > # ok 2
 > # not ok 3
 > # ok value seems to be error code - value is: -2
 > # not ok 4
 > # not ok 5
 > # '
 > #     expected: 'ok 1
 > # ok 2
 > # ok 3
 > # ok 4
 > # ok 5
 > # '
 > # Looks like you failed 1 test of 2.
 > }}}
 >

 After looking through these results I noticed that on the new run of test
 2, step 3 failed which had not been the case with the earlier running of
 the test.  In theory it would seem that step 3 returns an error diagnostic
 string but, on testing that error return string I came accross a bug in
 retrieving it, documented and fixed by ticket #1795.  After that ticket
 gets accepted or it's patches are otherwise applied on your system and
 parrot is rebuilt, Mr. Perrad should be able to apply the latest debugging
 paches to /t/library/pcre.t and post the results here for further progress
 in tracking down why the pcre nci interface is having trouble on his
 system

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/1401#comment:18>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets

Reply via email to