I am developing a package on my laptop. But I actually need it to run a server. So what I do is to test the code locally until it’s ready, and then rsync the package folder to the server.
It works when I first tried it yesterday. But now I made some new changes, synchronized the code again, and the modification does not work on the sever. It always runs the code from yesterday on the sever, even if I have checked the source code has been correctly synchronized.
I tried to delete .julia/complied/v1.1/mypackge. I tried to remove my own package from default environment and add it again. Nothing seems to work.
What can be the reason for such bizarre problem? I guess I must have messed up package system somehow.
I also see this line when I run update in package mode
Yes, I pkg> add the package (that has nothing to do with registration).
Basically my workflow is this: make sure it works on my laptop (tests pass, results with toy dataset look satisfactory, estimation converges for simulated data). Then I push to the repo (a private one on Gitlab), and just do a
pkg> up
on the server and I am ready to run the computation.
I e-mail myself (using a bash script calling mailx) when done and retrieve the results (also via git, in a separate repository, just a bunch of CSV files).
Thanks. Now I see what’s wrong in my original attempt.
It’s not enough to have the code of the package updated on the remote server. Since the package has been added to the default environment, I need to run
pkg> up
Otherwise in the default environment, julia will run the old code.