[perl #58934] [CAGE] 'make fulltest' says PASS at the end, although some tests failed
# New Ticket Created by Moritz Lenz # Please include the string: [perl #58934] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=58934 'make fulltest' runs several chunks of tests, and does not show a final summary. So although some tests in some chunks fail, the last thing that the tester sees is something along these lines: ===( 35 )==All tests successful. Files=10, Tests=108, 29 wallclock secs ( 0.04 usr 0.02 sys + 19.55 cusr 1.44 csys = 21.05 CPU) Result: PASS make[1]: Leaving directory `/home/moritz/src/parrot' If only the last chunk succeeded. This is very misleading, and probably dangerous. At the very least it should say something like WARNING: not all tests were successful, scroll up to find out which failed. This could be done by collecting the return values from the various 'make test*' calls. Even better would be real summary at the end listing the failed tests. (Observed with perl-5.10.0 and Test::Harness 3.11, parrot as of shortly-before 0.7.1) Moritz -- Moritz Lenz http://moritz.faui2k3.org/ | http://perl-6.de/
Re: [perl #58934] [CAGE] 'make fulltest' says PASS at the end, although some tests failed
On Tue, Sep 16, 2008 at 12:27 PM, via RT Moritz Lenz [EMAIL PROTECTED] wrote: # New Ticket Created by Moritz Lenz # Please include the string: [perl #58934] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=58934 'make fulltest' runs several chunks of tests, and does not show a final summary. So although some tests in some chunks fail, the last thing that the tester sees is something along these lines: ===( 35 )==All tests successful. Files=10, Tests=108, 29 wallclock secs ( 0.04 usr 0.02 sys + 19.55 cusr 1.44 csys = 21.05 CPU) Result: PASS make[1]: Leaving directory `/home/moritz/src/parrot' If only the last chunk succeeded. This is very misleading, and probably dangerous. At the very least it should say something like WARNING: not all tests were successful, scroll up to find out which failed. This could be done by collecting the return values from the various 'make test*' calls. Even better would be real summary at the end listing the failed tests. (Observed with perl-5.10.0 and Test::Harness 3.11, parrot as of shortly-before 0.7.1) Moritz -- Moritz Lenz http://moritz.faui2k3.org/ | http://perl-6.de/ parrot's fulltest runs the harness multiple times without a very clear distinction. as i understand, this behavior can now be changed, as we require T::H 3. the fulltest target must be modified to report the results from each harness run together at the end, rather than seperately after each harness run. ~jerry
Re: C++ build succeeded, but with some tests failed
On Mon, Apr 14, 2008 at 4:00 PM, Senaka Fernando [EMAIL PROTECTED] wrote: Hi all, C++ build succeeded, but with some tests failed. There were two issues that I couldn't formally sorted, and thus I had to tweak it. I have opened tickets for all other build related issues which have a formal fix. The tweaks used along with the make test report are attached herewith. Thus, I believe that you should be able to get Parrot to build with g++ on Ubuntu Gutsy once my tickets are closed and the given diff of tweaks are applied. Regards, Senaka Please also attach a file with your invocation of Configure.pl and the output from that step. Thanks! -- Will Coke Coleda
Fwd: C++ build succeeded, but with some tests failed
Coke, These are not intended to be applied. But, I doubt whether it is something else. Here is the output of the Configure.pl, and a diff against the output I get when I use gcc. Also, here are some reasons to what might cause these errors. 1. these are either misuse of names 2. or due to __cplusplus define missing 3. or due to inline/readline 4. or may be my tweaks Regards, Senaka On Tue, Apr 15, 2008 at 1:45 AM, Will Coleda [EMAIL PROTECTED] wrote: On Mon, Apr 14, 2008 at 4:00 PM, Senaka Fernando [EMAIL PROTECTED] wrote: Hi all, C++ build succeeded, but with some tests failed. There were two issues that I couldn't formally sorted, and thus I had to tweak it. I have opened tickets for all other build related issues which have a formal fix. The tweaks used along with the make test report are attached herewith. Thus, I believe that you should be able to get Parrot to build with g++ on Ubuntu Gutsy once my tickets are closed and the given diff of tweaks are applied. Regards, Senaka Note that one of the failures is in t/codingstd/c_indent.pl - but this failure is a result of your local changes. (If someone applies this, please make sure the formatting is fixed.) Regards. -- Will Coke Coleda Checking MANIFEST.done. Setting up Configure's default values.done. Setting up installation paths.done. Tweaking settings for miniparrot...skipped. Loading platform and local hints filesdone. Finding header files distributed with Parrot..done. Determining what C compiler and linker to use.done. Determining whether make is installed..yes. Determining whether lex is installed...skipped. Determining whether yacc is installed..skipped. Determining if your C compiler is actually gcc.yes. Seeing if GNU libc is installedyes. Determining whether libc has the backtrace* functions (glibc only).yes. Determining Fink location on Darwinskipped. Determining Macports location on Darwinskipped. Determining if your C compiler is actually Visual C++...no. Detecting compiler attributes (-DHASATTRIBUTE_xxx)done. Detecting supported compiler warnings (-Wxxx)..set for gcc. Enabling optimization...no. Determining flags for building shared libraries..-fPIC. Determine if parrot should be linked against a shared library..yes. Determining what charset files should be compiled in..done. Determining what encoding files should be compiled in.done. Determining what types Parrot should use..done. Determining what opcode files should be compiled in...done. Determining what pmc files should be compiled in..done. Determining your minimum pointer alignment. 1 byte. Probing for C headers.done. Determining some sizesdone. Computing native byteorder for Parrot's wordsize.little-endian. Test the type of va_ptr (this test is likely to segfault)stack. Figuring out how to pack() Parrot's types.done. Figuring out what formats should be used for sprintf..done. Determining if your C library has a working S_ISREGyes. Determining CPU architecture and OS...done. Determining architecture, OS and JIT capability...done. Generating CPU specific stuff.done. Verifying that the compiler supports function pointer castsyes. Determining whether your compiler supports computed goto...yes. Determining if your compiler supports inlineno. Determining what allocator to use.done. Determining if your C library supports memalignyes. Determining some signal stuff.done. Determining whether there is socklen_t.yes. Determining if your C library has setenv / unsetenv...both. Determining if your platform supports AIO..yes. Determining if your platform supports GMP..yes. Determining if your platform supports readline..no. Determining if your platform supports gdbm..no. Determining if your
PGE update fails some tests under x86_64
On Fri, Mar 17, 2006 at 07:08:55PM -0600, Patrick R. Michaud wrote: I've just applied a change (r11921) to PGE that allows embedded closures in rules to designate a return value for a match (recently added to S05). [...] I neglected to mention in my previous post that this update seems to cause some PGE tests to fail when run in the x86_64 platform (and the failures seem inconsistent). They all pass when run 32-bit, however. Before committing this latest update I spent some time trying to resolve the x86_64 issues, but with little success. So, despite the failed tests, I decided to commit the update anyway so that others with more knowledge than me can track down the problem. Pm
[perl #29836] [PATCH] No need to skip some tests on Cygwin
All extend and thread tests have passed for me on trunk with normal build. timer seems to pass outside the harness, but isn't happy inside it. Signal seems to have a 'Signal 1' message in the output which breaks the test. I'm just going to repeat this to double check things. I'll add any updates if there are any. [Also trans has the problem with one of the trig tests (which has been mentioned a few times!), and dynclasses don't build yet] On p6i Nick reported success for the timer and signal tests on an updated Cygwin. For the failing trig test there is now ticket [perl #36835] and for the dynclasses problem there is not [perl #36836]. Thus this ticket can be resolved. Nick: Could you check the cygwin information in PLATFORMS? If you send a patch, I'll apply it. -- /* [EMAIL PROTECTED] */
[perl #29836] [PATCH] No need to skip some tests on Cygwin
Hi, I have applied a couple of old patches from Limbic~Region. These patches are enabling some tests for cygwin. Unfortunately I have no cygwin installed, so I can't tell whether the enabled tests are passing. But I think that right after a release is a good time for breaking things. Could one of the Cygwin users tell whether everything is OK? extend 12 previously hung on Cygwin: If configured with --intval=long and --opcode=long this is not the case This might still be problematic. threads were all being skipped on Cygwin: They all pass except the 2 that are being universally skipped The threads tests were already enabled for cygwin. timer were all being skipped on Cygwin: They all pass Timer tests are now enabled -- /* [EMAIL PROTECTED] */
Re: [perl #29836] [PATCH] No need to skip some tests on Cygwin
Bernhard Schmalhofer via RT wrote: Hi, I have applied a couple of old patches from Limbic~Region. These patches are enabling some tests for cygwin. Unfortunately I have no cygwin installed, so I can't tell whether the enabled tests are passing. But I think that right after a release is a good time for breaking things. Could one of the Cygwin users tell whether everything is OK? My pleasure. All extend and thread tests have passed for me on trunk with normal build. timer seems to pass outside the harness, but isn't happy inside it. Signal seems to have a 'Signal 1' message in the output which breaks the test. I'm just going to repeat this to double check things. I'll add any updates if there are any. [Also trans has the problem with one of the trig tests (which has been mentioned a few times!), and dynclasses don't build yet] Regards, Nick
Re: [perl #36385] Some Tests Failing on Win32 for 8443 revision
Craig (via RT) wrote: Downloaded revision 8443 of Parrot to Windows XP Pro using SVN. When using 'nmake' 7.10.3077, some of the test are failing. According to the gettingstarted.pod, none of the tests should fail. README.win32 is more specific - dynclasses are currently broken. Thanks, Craig Fjord.pasm 1 print He's pining for the fjords. \n 2 end Output from various attemts to excute fjord.pasm. Fjord.pasm - ASCII format E:\usr\local\parrot-0.2.1-devel\binparrot fjord.pasm error:imcc:syntax error, unexpected EOM, expecting '\n' in file 'fjord.pasm' line 2 Very linkely missing newline after end. Fjord.pasm - Unicode format E:\usr\local\parrot-0.2.1-devel\binparrot fjord.pasm error:imcc:syntax error, unexpected $end, expecting PARROT_OP in file 'fjord.pasm' line 1 Parrot doesn't support non-ascii source files. But you can specify e.g. unicode strings. t\dynclass\foo.t 8 2048 98 88.89% 1-5 7-9 t\dynclass\pybuiltin.t5 1280 65 83.33% 1-2 4-6 t\dynclass\pyclass.t 6 1536 66 100.00% 1-6 t\dynclass\pycomplex.t4 1024 44 100.00% 1-4 t\dynclass\pyfunc.t 4 1024 44 100.00% 1-4 t\dynclass\pyint.t 25 640026 25 96.15% 1-25 t\op\spawnw.t 3 768 63 50.00% 4-6 Yep leo
[perl #36385] Some Tests Failing on Win32 for 8443 revision
# New Ticket Created by Craig # Please include the string: [perl #36385] # in the subject line of all future correspondence about this issue. # URL: https://rt.perl.org/rt3/Ticket/Display.html?id=36385 Downloaded revision 8443 of Parrot to Windows XP Pro using SVN. When using 'nmake' 7.10.3077, some of the test are failing. According to the gettingstarted.pod, none of the tests should fail. Attached is myconfig and the output from 'nmake test' with STDERR at the end of the file. Please not this is my first attempt at using Parrot, so its most likely that I'm missing the obivous. Thanks, Craig Fjord.pasm 1 print He's pining for the fjords. \n 2 end Output from various attemts to excute fjord.pasm. Fjord.pasm - ASCII format E:\usr\local\parrot-0.2.1-devel\binparrot fjord.pasm error:imcc:syntax error, unexpected EOM, expecting '\n' in file 'fjord.pasm' line 2 Fjord.pasm - Unicode format E:\usr\local\parrot-0.2.1-devel\binparrot fjord.pasm error:imcc:syntax error, unexpected $end, expecting PARROT_OP in file 'fjord.pasm' line 1 Compiling with: xx.c cl -nologo -GF -W3 -MD -Zi -DNDEBUG -DWIN32 -D_CONSOLE -DNO_STRICT -DNO_HASH_SEED -Zi -I.\include -DHAS_JIT -DI386 -I. -Fo xx.obj -c xx.c E:\Perl\bin\perl.exe -e chdir shift @ARGV; system 'nmake', @ARGV; exit $? 8; docs E:\Perl\bin\perl.exe -e -d or mkdir $_,0777 or die foreach @ARGV ops E:\Perl\bin\perl.exe -e chdir shift @ARGV; system 'nmake', @ARGV; exit $? 8; dynclasses E:\Perl\bin\perl.exe -e chdir shift @ARGV; system 'nmake', @ARGV; exit $? 8; compilers\pge E:\Perl\bin\perl.exe t\harness --gc-debug --running-make-test t\library\*.t t\op\*.t t\pmc\*.t t\native_pbc\*.t imcc\t\*\*.t t\dynclass\*.t t\src\*.t t\perl\*.t t\library\dumper...ok t\library\getopt_long..ok t\library\md5..ok t\library\parrotlibok t\library\pcre.ok 1/1 skipped: no pcre-config t\library\pge..ok t\library\sort.ok t\library\streams..ok t\library\yaml_parser_syck.ok t\op\00ff-dos..ok t\op\00ff-unix.ok t\op\64bit.skipped all skipped: 64bit INTVAL platforms only t\op\arithmetics...ok t\op\basic.ok t\op\bitwise...ok t\op\calling...ok t\op\comp..ok t\op\conv..ok t\op\debuginfo.ok 3/8 skipped: getline/setline changes not finished t\op\gcok t\op\globals...ok t\op\hacks.ok 2/2 skipped: no universal SIGFPE handling t\op\ifunless..ok t\op\info..ok t\op\integer...ok t\op\interpok t\op\jit...ok t\op\jitn..ok t\op\lexicals..ok t\op\literal...ok t\op\macro.ok 1/18 skipped: Await exceptions t\op\numberok t\op\randomok t\op\rxok 1/23 skipped: Pending some sort of lowercasing op t\op\spawnwdubious Test returned status 3 (wstat 768, 0x300) DIED. FAILED tests 4-6 Failed 3/6 tests, 50.00% okay t\op\stacksok 3/56 skipped: no stack limit currently t\op\stringok 7/156 skipped: various reasons t\op\string_cclass.ok t\op\string_cs.ok t\op\stringu...ok t\op\time..ok t\op\trans.ok t\op\types.ok t\pmc\arrayok t\pmc\bigint...skipped all skipped: No BigInt Lib configured t\pmc\boolean..ok t\pmc\builtin..ok t\pmc\complex..ok t\pmc\config...ok t\pmc\coroutineok 2/13 skipped: various reasons t\pmc\delegate.ok t\pmc\env..ok t\pmc\eval.ok t\pmc\exceptionok t\pmc\fixedbooleanarrayok t\pmc\fixedfloatarray..ok t\pmc\fixedintegerarrayok t\pmc\fixedpmcarrayok t\pmc\fixedstringarray.ok t\pmc\floatok t\pmc\floatvalarrayok t\pmc\freeze...ok t\pmc\globals..ok t\pmc\hash.ok t\pmc\integer..ok t\pmc\intlist..ok t\pmc\io...ok 1/31 skipped: clone not finished yet t\pmc\iter.ok 1/41 skipped: N/Y: length of rest of array t\pmc\key..ok t\pmc\managedstructok t\pmc\mmd..ok t\pmc\multiarray...ok t\pmc\multisub.ok t\pmc\n_arithmeticsok t\pmc\namespaceok
[perl #29836] [PATCH] No need to skip some tests on Cygwin
# New Ticket Created by Joshua Gatcomb # Please include the string: [perl #29836] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=29836 extend 12 previously hung on Cygwin: If configured with --intval=long and --opcode=long this is not the case threads were all being skipped on Cygwin: They all pass except the 2 that are being universally skipped timer were all being skipped on Cygwin: They all pass Cheers Joshua Gatcomb a.k.a. Limbic~Region __ Do you Yahoo!? Yahoo! Domains Claim yours for only $14.70/year http://smallbusiness.promotions.yahoo.com/offer extend.patch Description: Binary data threads.patch Description: Binary data timer.patch Description: Binary data
[COMMIT] Re-enabled some tests.
Some tests were disabled because of recently-patched problems in the assembler. I'm contemplating simply removing the tests that require exceptions, because we're going to do much more with exceptions than these (probably already deprecated) tests cover. -- Jeff [EMAIL PROTECTED]
Some tests
The attached file contains tests for all Parrot integer ops. - Damien #! perl -w use Parrot::Test tests = 26; output_is(CODE, OUTPUT, set_i_ic); # XXX: Need a test for writing outside the set of available # registers. Parrot doesn't check for this at the moment. set I0, 0x12345678 print I0 print \\n set I31, 0x9abcdef1 print I31 print \\n set I1, 2147483647 print I1 print \\n set I2, -2147483648 print I2 print \\n set I3, 4294967295 print I3 print \\n CODE 305419896 -1698898191 2147483647 -2147483648 -1 OUTPUT output_is(CODE, OUTPUT, set_i); set I0, 0x77665544 set I1, I0 print I1 print \\n CODE 2003195204 OUTPUT output_is(CODE, OUTPUT, add_i); set I0, 0x11223344 add I1, I0, I0 print I1 print \\n add I2, I0, I1 print I2 print \\n add I2, I2, I2 print I2 print \\n set I3, 2147483647 set I4, 1 add I5, I3, I4 print I5 print \\n set I6, -1 add I7, I5, I6 print I7 print \\n CODE 574908040 862362060 1724724120 -2147483648 2147483647 OUTPUT output_is(CODE, OUTPUT, sub_i); set I0, 0x12345678 set I1, 0x01234567 sub I2, I0, I1 print I2 print \\n CODE 286331153 OUTPUT output_is(CODE, OUTPUT, mul_i); set I0, 7 set I1, 29 mul I2, I0, I1 print I2 print \\n CODE 203 OUTPUT output_is(CODE, OUTPUT, div_i); set I0, 0x set I1, 0x div I2, I0, I1 print I2 print \\n set I0, 11 set I1, 2 div I2, I0, I1 print I2 print \\n set I0, 9 set I1, -4 div I2, I0, I1 print I2 print \\n CODE 3 5 -2 OUTPUT output_is(CODE, OUTPUT, mod_i); set I0, 17 set I1, 5 mod I2, I0, I1 print I2 print \\n set I0, -57 set I1, 10 mod I2, I0, I1 print I2 print \\n CODE 2 -7 OUTPUT output_is(CODE, OUTPUT, eq_i_ic); set I0, 0x12345678 set I1, 0x12345678 set I2, 0x76543210 eq I0, I1, ONE, ERROR print bad\\n ONE: print ok 1\\n eq I1, I2, ERROR, TWO print bad\\n TWO: print ok 2\\n end ERROR: print bad\\n CODE ok 1 ok 2 OUTPUT output_is(CODE, OUTPUT, eq_ic_ic); set I0, -42 eq I0, 42, ERROR, ONE print bad\\n ONE: print ok 1\\n eq I0, -42, TWO, ERROR print bad\\n TWO: print ok 2\\n end ERROR: print bad\\n CODE ok 1 ok 2 OUTPUT output_is(CODE, OUTPUT, ne_i_ic); set I0, 0xa0b0c0d0 set I1, 0xa0b0c0d0 set I2, 0 ne I0, I2, ONE, ERROR print bad\\n ONE: print ok 1\\n ne I0, I1, ERROR, TWO print bad\\n TWO: print ok 2\\n end ERROR: print bad\\n CODE ok 1 ok 2 OUTPUT output_is(CODE, OUTPUT, ne_ic_ic); set I0, 427034409 ne I0, 427034409, ERROR, ONE print bad\\n ONE: print ok 1\\n ne I0, 427034408, TWO, ERROR print bad\\n TWO: print ok 2\\n end ERROR: print bad\\n CODE ok 1 ok 2 OUTPUT output_is(CODE, OUTPUT, lt_i_ic); set I0, 2147483647 set I1, -2147483648 set I2, 0 set I3, 0 lt I1, I0, ONE, ERROR print bad\\n ONE: print ok 1\\n lt I0, I1, ERROR, TWO print bad\\n TWO: print ok 2\\n lt I2, I3, ERROR, THREE print bad\\n THREE: print ok 3\\n end ERROR: print bad\\n CODE ok 1 ok 2 ok 3 OUTPUT output_is(CODE, OUTPUT, lt_ic_ic); set I0, 2147483647 set I1, -2147483648 set I2, 0 lt I0, -2147483648, ERROR, ONE print bad\\n ONE: print ok 1\\n lt I1, 2147483647, TWO, ERROR print bad\\n TWO: print ok 2\\n lt I0, 0, ERROR, THREE print bad\\n THREE: print ok 3\\n end ERROR: print bad\\n CODE ok 1 ok 2 ok 3 OUTPUT output_is(CODE, OUTPUT, le_i_ic); set I0, 2147483647 set I1, -2147483648 set I2, 0 set I3, 0 le I1, I0, ONE, ERROR print bad\\n ONE: print ok 1\\n le
Re: Some tests
On Tue, Sep 18, 2001 at 02:14:39PM -0700, Damien Neil wrote: The attached file contains tests for all Parrot integer ops. - Damien THANK YOU! (Applied) -- Calm down, it's *only* ones and zeroes.
