Skip to content
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

[PkgEval] CompilerOptions may have a testing issue on Julia 0.3 (2014-09-28) #1

Closed
IainNZ opened this issue Sep 28, 2014 · 4 comments
Closed

Comments

@IainNZ
Copy link

IainNZ commented Sep 28, 2014

PackageEvaluator.jl is a script that runs nightly. It attempts to load all Julia packages and run their tests (if available) on both the stable version of Julia (0.3) and the nightly build of the unstable version (0.4). The results of this script are used to generate a package listing enhanced with testing results.

On Julia 0.3

  • On 2014-09-28 the testing status was N/A - new package.
  • On 2014-09-28 the testing status changed to Tests fail, but package loads.

Tests fail, but package loads. means that PackageEvaluator found the tests for your package, executed them, and they didn't pass. However, trying to load your package with using worked.

This issue was filed because your testing status became worse. No additional issues will be filed if your package remains in this state, and no issue will be filed if it improves. If you'd like to opt-out of these status-change messages, reply to this message saying you'd like to and @IainNZ will add an exception. If you'd like to discuss PackageEvaluator.jl please file an issue at the repository. For example, your package may be untestable on the test machine due to a dependency - an exception can be added.

Test log:

>>> 'Pkg.add("CompilerOptions")' log
INFO: Cloning cache of CompilerOptions from git://github.com/sjkelly/CompilerOptions.jl.git
INFO: Installing CompilerOptions v0.0.1
INFO: Package database updated
INFO: METADATA is out-of-date a you may not have the latest version of CompilerOptions
INFO: Use `Pkg.update()` to get the latest versions of your packages

>>> 'using CompilerOptions' log
Julia Version 0.3.1
Commit c03f413* (2014-09-21 21:30 UTC)
Platform Info:
  System: Linux (x86_64-unknown-linux-gnu)
  CPU: Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz
  WORD_SIZE: 64
  BLAS: libopenblas (USE64BITINT DYNAMIC_ARCH NO_AFFINITY Sandybridge)
  LAPACK: libopenblas
  LIBM: libopenlibm
  LLVM: libLLVM-3.3

>>> test log
ERROR: test failed: code_coverage()
 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:245
 in include_from_node1 at loading.jl:128
 in process_options at ./client.jl:285
 in _start at ./client.jl:354
 in _start_3B_1712 at /home/idunning/julia03/usr/bin/../lib/julia/sys.so
while loading /home/idunning/pkgtest/.julia/v0.3/CompilerOptions/test/runtests.jl, in expression starting on line 5

INFO: Testing CompilerOptions
===========================[ ERROR: CompilerOptions ]===========================

failed process: Process(`/home/idunning/julia03/usr/bin/julia /home/idunning/pkgtest/.julia/v0.3/CompilerOptions/test/runtests.jl`, ProcessExited(1)) [1]

================================================================================
INFO: No packages to install, update or remove
ERROR: CompilerOptions had test errors
 in error at error.jl:21
 in test at pkg/entry.jl:715
 in anonymous at pkg/dir.jl:28
 in cd at ./file.jl:20
 in cd at pkg/dir.jl:28
 in test at pkg.jl:67
 in process_options at ./client.jl:213
 in _start at ./client.jl:354
 in _start_3B_1712 at /home/idunning/julia03/usr/bin/../lib/julia/sys.so


>>> end of log
@sjkelly
Copy link
Owner

sjkelly commented Oct 1, 2014

@IainNZ PkgEval is run without code-coverage?

@IainNZ
Copy link
Author

IainNZ commented Oct 1, 2014

Correct, I haven't got a use for the output (yet)

@sjkelly
Copy link
Owner

sjkelly commented Oct 1, 2014

Sounds like I should finish my PR to Coverage.jl!

@sjkelly
Copy link
Owner

sjkelly commented Jan 12, 2015

The testing process has change on master, so this shouldn't be an issue.

@sjkelly sjkelly closed this as completed Jan 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants