#50154 closed submission (fixed)
nqp, rakudo: new ports
Reported by: | mojca (Mojca Miklavec) | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | coke (Will Coleda), Ionic (Mihai Moldovan), mojca (Mojca Miklavec), dbevans (David B. Evans) | |
Port: | nqp rakudo |
Description (last modified by mojca (Mojca Miklavec))
Following #50153 here's a ticket to add nqp
and rakudo
.
See also:
Attachments (2)
Change History (8)
comment:1 Changed 9 years ago by mojca (Mojca Miklavec)
Changed 9 years ago by mojca (Mojca Miklavec)
Attachment: | nqp.Portfile added |
---|
Initial attempt for nqp
Changed 9 years ago by mojca (Mojca Miklavec)
Attachment: | rakudo.Portfile added |
---|
Initial attempt for rakudo
comment:2 Changed 9 years ago by mojca (Mojca Miklavec)
Description: | modified (diff) |
---|
comment:3 Changed 9 years ago by coke (Will Coleda)
The testing failure is likely due to getting the source from github; the make test target is part of the local repo; make spectest checks out another git repo - as part of the release, a specific version of this was cut and included with the tarball on the rakudo.org site; the default behavior is to get the latest version of the tests; so pulling the spec tests from github will soon be out of date compared the version in the portfile.
comment:4 Changed 9 years ago by mojca (Mojca Miklavec)
I committed r143947. Let us worry about the proper version of the test suite later.
comment:5 Changed 9 years ago by mojca (Mojca Miklavec)
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:6 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | mojca@… added; mojca@… removed |
---|
Note: See
TracTickets for help on using
tickets.
Just for testing purposes I have set
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:
I initially experienced another problem:
but running the test alone manually worked fine:
so I'm confused (and probably won't bother). Maybe it's just an interference with MacPorts' logging?