Skip to content

Conversation

@Wikunia
Copy link
Contributor

@Wikunia Wikunia commented Apr 2, 2020

Some things still missing:
The 3D torus image is missing as well as the corresponding jupyter notebook

git-tree-sha1 = "88bb0edb352b16608036faadcc071adda068582a"
uuid = "ffbed154-4ef7-542d-bbb7-c09d3a79fcae"
version = "0.7.0"
version = "0.8.1"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you sure that these are the minimum possible versions? E.g. 0.8.0 doesn't work? Probably this should just be 0.8

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think the Manifest.toml file should actually be included at all?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not completely sure about this:

  • I think the Manifest.toml is useful in the docs such that travis/GitHub Actions use the same version every time to generate the docs. Otherwise you need to provide upper bounds to be sure that it doesn't break when Documenter updates.
    Users of a package normally don't generate the docs locally. (At least I don't 😄 ) Therefore I think the versions used there are not breaking anything for the user.
    The root Manifest.toml shouldn't be included I think because there it should use the highest version possible if allowed by the specified [Compat] section and also a strict version shouldn't be forced as long as the package works the version for subpackages is often not important.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK thanks for the comments. Shall I just go ahead and merge this then? Or will the docs be built during this PR?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately I think you need to merge this to see the actual output.
I'm not sure why travis is not running for this package. Do you only run it on master?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like for the other PRs travis is running 😕

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I expect that's out of date too.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll just go ahead and merge.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe you get some useful information on travis.org?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dpsanders
Copy link
Member

Thanks a lot for this!

@dpsanders dpsanders merged commit 60385bb into JuliaIntervals:master Apr 2, 2020
@dpsanders
Copy link
Member

Travis ran but the docs look the same...

@Wikunia
Copy link
Contributor Author

Wikunia commented Apr 2, 2020

There are some errors: https://travis-ci.org/github/JuliaIntervals/IntervalConstraintProgramming.jl/jobs/670175738#L337-L342
Don't know why it still says that Documentation passed

@Wikunia
Copy link
Contributor Author

Wikunia commented Apr 2, 2020

Okay it seems to be running on PR and there it fails because it normally only deploys on master.
https://travis-ci.org/github/JuliaIntervals/IntervalConstraintProgramming.jl
There it doesn't run on master.

@Wikunia
Copy link
Contributor Author

Wikunia commented Apr 2, 2020

Btw you can use codecov: true to make it a little simpler. But don't know why it doesn't run on master.
lanl-ansi/Juniper.jl#154
Our script line looks a bit different as well:

 script:
        - julia --project=docs -e 'using Pkg; Pkg.instantiate(); Pkg.add(PackageSpec(path=pwd()))'
        - julia --project=docs --color=yes docs/make.jl

@dpsanders
Copy link
Member

dpsanders commented Apr 2, 2020 via email

@Wikunia
Copy link
Contributor Author

Wikunia commented Apr 3, 2020

Are you interested in using GitHub actions? Not sure why you need the sudo in the tests section. Otherwise I'm always getting help by @fredrikekre when I'm having problems with Documenter. Not sure where the problem lies with this one.

@fredrikekre
Copy link

df2c830 introduced an invalid config, you can see the warnings here: https://travis-ci.org/github/JuliaIntervals/IntervalConstraintProgramming.jl/builds/670193560/config?utm_medium=notification&utm_source=github_status

@dpsanders
Copy link
Member

Thanks, but the documentation was not running before that change.

@fredrikekre
Copy link

@Wikunia Wikunia deleted the bugfix-latex-docs branch April 4, 2020 12:59
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.

3 participants