On Tue, May 07, 2013 at 09:01:34AM +0300, Gabor Szabo wrote:
> Do I first need to manually clone Rakudo and the modules from Gihub
> and then use the --force or is
> there something else I need to do?
> Do I understand correctly that in a real Rakudo * release you'd check out the
> labeled release of Rakudo and the latest versions of the modules and
> then start the build process?

The rakudo/star repository contains the tools needed to build a
Rakudo Star tarball.  The repo itself doesn't contain the compiler
and/or module sources directly.

You don't (and shouldn't) manually clone the Rakudo and module repos
from GitHub, there's a Makefile in the repo that does that for you.  
See the tools/star/release_guide.pod file for the steps needed to build
and test a Rakudo Star distribution.  I've already done most of the steps 
needed to build the 2013.04 distribution, my latest candidate is
downloadable from:

   http://pmichaud.com/sandbox/rakudo-star-2013.04-rc2.tar.gz

The "make modules-test" part is failing for me in this candidate,
the failures I'm seeing are:

    Testing modules/perl6-File-Tools...
    t/01-file-find.t ...... ok   
    t/02-shell-command.t .. 1/12 Failed to remove the file 
't/dir2/foodir/not_a_dir': unlink failed: No such file or directory
      in block  at src/gen/CORE.setting:8121
      in sub unlink at src/gen/CORE.setting:8117
      in block  at 
/home/pmichaud/p6/star/work/rakudo-star-2013.04/install/lib/parrot/5.2.0/languages/perl6/lib/Shell/Command.pm:34
      in method reify at src/gen/CORE.setting:5737
      in method reify at src/gen/CORE.setting:5632
      in method gimme at src/gen/CORE.setting:6053
      in method eager at src/gen/CORE.setting:6032
      in sub rm_rf at 
/home/pmichaud/p6/star/work/rakudo-star-2013.04/install/lib/parrot/5.2.0/languages/perl6/lib/Shell/Command.pm:26
      in block  at t/02-shell-command.t:28
    
    t/02-shell-command.t .. Dubious, test returned 1 (wstat 256, 0x100)
    Failed 7/12 subtests 
    
    Test Summary Report
    -------------------
    t/02-shell-command.t (Wstat: 256 Tests: 10 Failed: 5)
      Failed tests:  5-9
      Non-zero exit status: 1
      Parse errors: Bad plan.  You planned 12 tests but ran 10.
    Files=2, Tests=18,  2 wallclock secs ( 0.03 usr  0.01 sys +  2.01 cusr  
0.37 csys =  2.42 CPU)
    Result: FAIL
   
and

    Testing modules/perl6-lwp-simple...
    t/000-load-module.t ............. ok   
    t/basic-auth.t .................. ok   
    t/custom-headers-and-content.t .. Cannot call 'match'; none of these 
signatures match:
    :(Cool:D : $target, *%adverbs)
      in method match at src/gen/CORE.setting:2477
      in block  at t/custom-headers-and-content.t:12
    
    t/custom-headers-and-content.t .. Dubious, test returned 1 (wstat 256, 
0x100)
    No subtests run 
    t/get-binary-camelia.t .......... ok   
    t/get-chunked-6guts.t ........... ok   
    t/get-perl6-org.t ............... ok   
    t/get-unsized.t ................. Cannot call 'match'; none of these 
signatures match:
    :(Cool:D : $target, *%adverbs)
      in method match at src/gen/CORE.setting:2477
      in block  at t/get-unsized.t:10
    
    t/get-unsized.t ................. Dubious, test returned 1 (wstat 256, 
0x100)
    No subtests run 
    t/get-w3-latin1-utf8.t .......... ok   
    t/get-w3-redirect.t ............. ok   
    t/getstore.t .................... ok   
    t/parse-url.t ................... ok    
    t/socket-sanity.t ............... ok   
    t/stringify-headers.t ........... ok   
    
    Test Summary Report
    -------------------
    t/custom-headers-and-content.t (Wstat: 256 Tests: 0 Failed: 0)
      Non-zero exit status: 1
      Parse errors: No plan found in TAP output
    t/get-unsized.t               (Wstat: 256 Tests: 0 Failed: 0)
      Non-zero exit status: 1
      Parse errors: No plan found in TAP output
    Files=13, Tests=54, 94 wallclock secs ( 0.11 usr  0.02 sys + 86.86 cusr  
2.66 csys = 89.65 CPU)
    Result: FAIL

I suspect these failures aren't all that hard to find/fix; 
I just haven't had time to do it.

Pm

Reply via email to