[MacPorts] #50154: nqp, rakudo: new ports
MacPorts
noreply at macports.org
Mon Dec 28 09:00:57 PST 2015
#50154: nqp, rakudo: new ports
-------------------------+--------------------------------
Reporter: mojca@… | Owner: macports-tickets@…
Type: submission | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: nqp rakudo |
-------------------------+--------------------------------
Comment (by mojca@…):
Just for testing purposes I have set
{{{
test.target test spectest
}}}
in `rakudo`.
This is the only failing test where the upstream developers would need
some help from Mac devs as those tests are skipped on other platforms:
{{{
> sudo -u macports /opt/local/bin/perl5.22 t/harness --fudge --moar
--verbosity=9 --keep-exit-code t/spec/S17-supply/watch-path.t
t/spec/S17-supply/watch-path.t ..
WARNINGS for /path/to/rakudo/work/rakudo-373adc0/t/spec/S17-supply/watch-
path.t:
Useless use of constant string "only about our file" in sink context
(lines 28, 28)
1..2
ok 1 - make sure we don't have a file
1..22
Failed 1/2 subtests
Test Summary Report
-------------------
t/spec/S17-supply/watch-path.t (Wstat: 5 Tests: 1 Failed: 0)
Non-zero wait status: 5
Parse errors: Bad plan. You planned 2 tests but ran 1.
Files=1, Tests=1, 5 wallclock secs ( 0.03 usr 0.00 sys + 3.47 cusr
0.28 csys = 3.78 CPU)
Result: FAIL
}}}
I initially experienced another problem:
{{{
t/spec/S32-str/utf8-c8.t ......................................
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/31 subtests
...
t/spec/S32-str/utf8-c8.t (Wstat: 256
Tests: 31 Failed: 1)
Failed test: 31
Non-zero exit status: 1
}}}
but running the test alone manually worked fine:
{{{
ok 31 - Can run Perl 6 sourcefile with non-UTF-8 name
}}}
so I'm confused (and probably won't bother). Maybe it's just an
interference with MacPorts' logging?
--
Ticket URL: <https://trac.macports.org/ticket/50154#comment:1>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list