Closed IainNZ closed 10 years ago
INFO: Installing Phylogenetics v0.0.1
INFO: Package database updated
WARNING: bitmix(x,y::Int) is deprecated, use hash(x,uint(y)) instead.
in bitmix at deprecated.jl:26
in hash at /home/idunning/pkgtest/.julia/v0.3/Phylogenetics/src/typedefs.jl:71
in anonymous at test.jl:62
in do_test at test.jl:37
in include at boot.jl:244 (repeats 2 times)
in include_from_node1 at loading.jl:128
WARNING: bitmix(x,y::Uint) is deprecated, use hash(x,y) instead.
in bitmix at deprecated.jl:26
in hash at /home/idunning/pkgtest/.julia/v0.3/Phylogenetics/src/typedefs.jl:71
in anonymous at test.jl:62
in do_test at test.jl:37
in include at boot.jl:244 (repeats 2 times)
in include_from_node1 at loading.jl:128
ERROR: test failed: parsedtree == Clado("",[5 1;5 2;5 6;6 3;6 4],2,["A","B","C","D"],["F","E"])
in error at error.jl:21
in default_handler at test.jl:19
in do_test at test.jl:39
in include at boot.jl:244 (repeats 2 times)
in include_from_node1 at loading.jl:128
while loading /home/idunning/pkgtest/.julia/v0.3/Phylogenetics/test/io.jl, in expression starting on line 5
while loading /home/idunning/pkgtest/.julia/v0.3/Phylogenetics/runtests.jl, in expression starting on line 5
INFO: Package database updated
Looks like #8 fixed this actually - maybe good to bump version in METADATA?
Bumping issue to remind you to bump METADATA
Hi, I did a Pkg.tag() so I hope it's ok now - it should be fine but it's the first time I've tried doing it that way.
I don't see the results of the tag pushed to METADATA?
Pkg.publish is needed to push it to METADATA
On Wed, Jul 2, 2014 at 9:09 PM, Ben J. Ward notifications@github.com wrote:
This is strange - doesn' t Pkg.tag() increment the version number of the package and send a PR to the julia METADATA repo?
— Reply to this email directly or view it on GitHub https://github.com/Ward9250/Phylogenetics.jl/issues/7#issuecomment-47856247 .
Iain Dunning PhD Candidate http://orc.scripts.mit.edu/people/student.php?name=idunning / MIT Operations Research Center http://web.mit.edu/orc/www/ http://iaindunning.com / http://juliaopt.org
I'm currently having issues with Pkg.publish(): ''' julia> Pkg.publish() INFO: Validating METADATA INFO: Pushing Phylogenetics permanent tags: v0.0.2 Permission denied (publickey). fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
ERROR: failed process: Process(git --work-tree=/Users/axolotlfan9250/.julia/v0.3/Phylogenetics --git-dir=/Users/axolotlfan9250/.julia/v0.3/Phylogenetics/.git push -q origin refs/tags/v0.0.2:refs/tags/v0.0.2
, ProcessExited(128)) [128]
in wait at ./task.jl:279
in wait at ./task.jl:189
in wait at task.jl:48
in sync_end at ./task.jl:306
in publish at pkg/entry.jl:314
in anonymous at pkg/dir.jl:28
in cd at file.jl:20
in cd at pkg/dir.jl:28
in publish at pkg.jl:57
'''
Yikes. I personally don't use Pkg.publish, I just fork and update METADATA manually. Do you have Github setup to access with your public SSH key?
When I first created Phylogenetics.jl I did it with the GitHub Mac app, which I guess did everything automatically - if I look on my GitHub profile I see some keys that say they are for this macbook and my office ubuntu machine and so on. But then if I look at the instructions here: https://help.github.com/articles/generating-ssh-keys, I don't have files id_rsa.pub or id_dsa.pub. I'll go through the SSH docs on the site and try and work out what's up.
I think I've solved it - successfully made a PR on Julia's METADATA
Merge with METADATA went through.
This issue is being filed by a script, but if you reply, I will see it.
PackageEvaluator.jl is a script that runs nightly. It attempts to load all Julia packages and run their test (if available) on both the stable version of Julia (0.2) and the nightly build of the unstable version (0.3).
The results of this script are used to generate a package listing enhanced with testing results.
The status of this package, Phylogenetics, on...
'No tests, but package loads.' can be due to their being no tests (you should write some if you can!) but can also be due to PackageEvaluator not being able to find your tests. Consider adding a
test/runtests.jl
file.'Package doesn't load.' is the worst-case scenario. Sometimes this arises because your package doesn't have BinDeps support, or needs something that can't be installed with BinDeps. If this is the case for your package, please file an issue and an exception can be made so your package will not be tested.
This automatically filed issue is a one-off message. Starting soon, issues will only be filed when the testing status of your package changes in a negative direction (gets worse). If you'd like to opt-out of these status-change messages, reply to this message.