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
t/04-nativecall/11-cpp.t failure #4806
Comments
From @lucsIt fails when rakudo has not yet been installed. Perhaps the makefile |
From ungrim97@hotmail.comI have picked this up. But don't currently have RT permissions |
From ungrim97@hotmail.comOn Wed Dec 02 05:22:19 2015, scullucs wrote:
Was able to replicate once but no cannot..... |
From @lucsGah! I meant t/16-rt125408.t, sorry about that (but the issue |
From ungrim97@hotmail.comI have been completely unable to replicate any issues with make test on a fresh vm. Steps: git clone http://github.com/rakudo/rakudo /data0/www/adcourier.broadbean/perl5/perlbrew/perls/perl-5.18.2/bin/perl t/harness --moar t/01-sanity t/04-nativecall |
The RT System itself - Status changed from 'new' to 'open' |
From @lucsAfter checking out and cleanly building all rakudo commits going back to one that I'm certain precedes the one where I got the error, it turns out that only t/04-nativecall/11-cpp.t fails (in the past), and never t/16-rt125408.t (I think that explains my error in the ticket title: I copypasted the wrong file name from the screen where I had seen the failure.) Yet I'm quite certain that the fail was occuring on t/16-rt125408.t, during a "make test" run. At the moment it occurred, I was nuking my whole rakudo directory and starting from scratch at each build (to get a feel for things I guess). Now that I look more closely, I understand that such builds from scratch check out fresh copies of nqp and MoarVM. The latter had a few commits done around the time I was building, so maybe its an unfortunate combination of rakudo+nqp+MoarVM that caused the now irreproducible error. I won't be trying out different combinations of rakudo+nqp+MoarVM commits, so I'm closing the ticket, and it will remain a mystery to me as to why it ever happened. In conclusion, I'll try to remember that a bit of patience on my part would probably have sufficed to avoid the false alarm. Thanks for looking into it! |
@lucs - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#126785 (status was 'resolved')
Searchable as RT126785$
The text was updated successfully, but these errors were encountered: