-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add rakudo build option to use local roast repo for spec tests #5412
Comments
From @tbrowderWhen working in a rakudo dev environment on a PR it would be very helpful to work on the associated tests at the same time. One way is to have a suitable build option to Configure.pl, e.g., + Use a suitably defined env var (say. ROAST_LOCAL_REPO_DIR): $ perl Configure.pl --gen-moar --gen-nqp --backends=moar \ or an explicit path: $ perl Configure.pl --gen-moar --gen-nqp --backends=moar \ and do the magic behind the scenes to generate make accordingly. A quick look at the rakudo/tools dir suggests that a new tools/build/Makefile-common-rules-local-roast.in could be a full replacement for "Makefile-common-rules.in", suitably modified, if the local roast option were used. |
From @cokeOn Sat Jul 02 05:50:21 2016, tom.browder@gmail.com wrote:
When I need to work on rakudo & spec tests simultaneously, I do a writable git clone of roast into t/spec inside the rakudo build dir. When you run "make stresstest" or "make spectest", it uses the version you already have checked out, instead of trying to grab a new copy. |
The RT System itself - Status changed from 'new' to 'open' |
From @zoffixznetClosing as per http://irclog.perlgeek.de/perl6/2016-07-08#i_12808727 |
@zoffixznet - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#128519 (status was 'resolved')
Searchable as RT128519$
The text was updated successfully, but these errors were encountered: