I want to add some more tests to verify that refactoring doesnt completely tank RStan.
How can I fire off the unit tests in RStan? It looks like there's been some activity lately, so hopefully someone can guide me.
First, run 'make build' to make sure it can be built.
Second, run 'make check'
Third, there is an r script at folder call test.
All the above can be seen from the script on Jenkins
--
Jiqiang
I want to add some more tests to verify that refactoring doesnt completely tank RStan.
How can I fire off the unit tests in RStan? It looks like there's been some activity lately, so hopefully someone can guide me.
--
You received this message because you are subscribed to the Google Groups "stan development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to stan-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
git submodule init
git submodule update
cd stan
git fetch
git checkout origin/develop
cd ..
git submodule status
cd rstan
make clean
make install_pre_rpkg
make check && (cd tests & R -q -f runRunitTests.R --args ../rstan.Rcheck)
> R CMD Sweave rstan/vignettes/rstan_vignette.Rnw
...
Warning in file(fname, "rt") :
cannot open file 'schools.stan': No such file or directory
Error in file(fname, "rt") : cannot open the connection
Not sure what you are asking.
What output do you want to hide and why?
What true error message is hidden?
On Thu, Mar 6, 2014 at 12:00 PM, Jiqiang Guo <guo...@gmail.com> wrote:
Not sure what you are asking.Ok. From the rstan directory, this fails for me:
> R CMD Sweave rstan/vignettes/rstan_vignette.RnwI think once that works, I can get RStan to build end to end. That's what I'm trying to fix now.Does that work on your setup? I'm running of my Mac, R 3.0.2.
If I type:> cd rstan/vignettes && R CMD Sweave rstan_vignette.Rnwit works.
What output do you want to hide and why?You can ignore that. I was thinking about using a `setwd()` inside and not show it, but hopefully we don't need to.
Here's what happens when I type make build:
What true error message is hidden?
> make build
R --vanilla CMD build rstan --md5 # --no-build-vignettes --no-manual
On Thu, Mar 6, 2014 at 12:07 PM, Daniel Lee <bea...@alum.mit.edu> wrote:
On Thu, Mar 6, 2014 at 12:00 PM, Jiqiang Guo <guo...@gmail.com> wrote:
Not sure what you are asking.Ok. From the rstan directory, this fails for me:
> R CMD Sweave rstan/vignettes/rstan_vignette.RnwI think once that works, I can get RStan to build end to end. That's what I'm trying to fix now.Does that work on your setup? I'm running of my Mac, R 3.0.2.
I would go to folder rstan/vignettes to do that.
If I type:> cd rstan/vignettes && R CMD Sweave rstan_vignette.Rnwit works.It works based on the rstan that is installed on your system, not the one you are trying to build.
What output do you want to hide and why?You can ignore that. I was thinking about using a `setwd()` inside and not show it, but hopefully we don't need to.
Here's what happens when I type make build:
What true error message is hidden?
> make build
R --vanilla CMD build rstan --md5 # --no-build-vignettes --no-manualYou should remove above # so that vignettes would not be built. Then after you install the rstan you want to test, you can try to build the vignette or run other model to see what is the problem. It is a painful process, but I do not see a good way to avoid that. One thing you should do if you have not is to use ccache.
I think Jenkins always uses the develop branch against Stan's develop branch, so that is why it does not fail for now.
It works based on the rstan that is installed on your system, not the one you are trying to build.
Yeah, that's fine for now. I have one built and installed. The problem I'm having is that make check fails based on the makefile inside rstan.
I am not sure what is exactly failing now. If make build succeeds and make check fails, then it is not because of the vignette. But you also showed that make build failed.
You should remove above # so that vignettes would not be built. Then after you install the rstan you want to test, you can try to build the vignette or run other model to see what is the problem. It is a painful process, but I do not see a good way to avoid that. One thing you should do if you have not is to use ccache.
I see. So is there any reason why that comment isn't removed permanently?
Sometimes, I need it to be uncommented when building vignette fails so that I can try to build the vignette to see more error message.
Jiqiang
I think Jenkins always uses the develop branch against Stan's develop branch, so that is why it does not fail for now.It works based on the rstan that is installed on your system, not the one you are trying to build.
Yeah, that's fine for now. I have one built and installed. The problem I'm having is that make check fails based on the makefile inside rstan.
I am not sure what is exactly failing now. If
make buildsucceeds andmake checkfails, then it is not because of the vignette. But you also showed thatmake buildfailed.
You should remove above # so that vignettes would not be built. Then after you install the rstan you want to test, you can try to build the vignette or run other model to see what is the problem. It is a painful process, but I do not see a good way to avoid that. One thing you should do if you have not is to use ccache.
I see. So is there any reason why that comment isn't removed permanently?
Sometimes, I need it to be uncommented when building vignette fails so that I can try to build the vignette to see more error message.
Jiqiang
--
If make build fails, there is no package built. Then you should not even try make check since there is no package to check.
--
Jiqiang
I can still build by make build. Also I triggered travis-ci though it is still working on it. https://travis-ci.org/stan-dev/rstan/jobs/20229169
By the way, I had problems with the make you newly installed and could not figured out why if you are working on Windows.
--
Jiqiang