Skip to content

Conversation

@martinholters
Copy link
Member

In case you're wondering: No 0.7(-lastest) and latest/nightly are not the same. The former is the latest 0.7 (pre-)release, i.e. 0.7-beta.0 at the moment, while the latter is, well, the latest nightly. (I think this would have exposed e.g. the problem with Statistics in #583, so it's probably worth doing both even though the difference is small.)

@fredrikekre
Copy link
Member

I think this would have exposed e.g. the problem with Statistics in #583

No, because Compat does not install itself from the registry, but I agree it is good to test on beta too!

@martinholters
Copy link
Member Author

At least locally, if I add an unknown dependency to the Project.toml, tests do fail:

(Compat) pkg> test
  Updating registry at `~/.julia/registries/Uncurated`
  Updating git-repo `https://github.com/JuliaRegistries/Uncurated.git`
 Resolving package versions...
ERROR: Unsatisfiable requirements detected for package Foo [abcdabcd]:

And isn't that the problem with Statistics, that is is unknown in beta.0? And shouldn't that then also cause CI to fail?

@fredrikekre
Copy link
Member

Ah, you are right, because Compat has a Project.toml file. For e.g. StaticArrays this was not found this way since you don't add them to the REQUIRE.

@martinholters martinholters merged commit af25a71 into master Jul 9, 2018
@martinholters martinholters deleted the mh/test0.7 branch July 9, 2018 06:49
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

Successfully merging this pull request may close these issues.

2 participants