Inline::Perl5 integration tests are no longer run

[lizmat]

It appears that since the relocatable build refactor, make spectest is no longer running the Inline::Perl5 integration tests, even though Inline::Perl5 is installed.

[lizmat]

I don't think this is a blocker. Hopefully, we'll fix this at the PTS

[coke]

I'm seeing what may be a related issue:

make spectest

...

Inline::Perl5 not installed: not running Perl 5 integration tests
You can install Inline::Perl5 into the build directory with

    zef --install-to=inst#/Volumes/BUKKIT/Users/coke/sandbox/rakudo/t/../gen/build_rakudo_home/site install Inline::Perl5

but if I run this zef command, it tells me all the candidates are currently installed, and then rerunning the spectest shows the same error.

[vendethiel]

it tells me all the candidates are currently installed

That's an issue with zef --install-to= I think, which doesn't use only that path to check if a module is installed. So if the module is installed somewhere else on your machine, zef --install-to= doesn't actually do something useful.

[coke]

FYI, added "--force-install" to that zef command, it installed... and then I got the same error from spectest, it's still not installed.

[ugexe]

@coke Can you try adding the --contained flag ala:
zef --contained --install-to=inst#/Volumes/BUKKIT/Users/coke/sandbox/rakudo/t/../gen/build_rakudo_home/site install Inline::Perl5?

--contained (BETA)      Install all transitive and direct dependencies regardless if they are already installed globally

Note that its BETA because it can have some issues installing to an existing repository (which it looks like you might be doing, but maybe it'll work).

EDIT: actually n/m... if you got it to force install then the above isn't going to get you any further.

[ugexe]

make spectest with Inline::Perl5 works if manually set the lib -- RAKULIB="inst#/Users/ugexe/repos/rakudo/t/../gen/build_rakudo_home/site" make spectest after using the zef install instructions. Something in make spectest should be setting that if it is going to tell users to install stuff to a specific location.

[vrurg]

All spectest targets in Makefile are using t/harnessN scripts. I think they're the best place for the fix.

[patrickbkr]

The original solution to this problem was to set the RAKUDO_HOME env var in the build runners in tools/templates/moar/rakudo-m-build.c.in. I'm wonder why that didn't have an effect (anymore?). Thus I'm not sure modifying the harness scripts is the correct fix...