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

CI: fix the YAML syntax for the docs job, and thus properly surface any docbuild failures #1046

Merged
merged 6 commits into from
Aug 31, 2023
Merged

Conversation

DilumAluthge
Copy link
Member

@DilumAluthge DilumAluthge commented Aug 27, 2023

Fixes the "silent" part of #1045

Obviously doesn't actually fix the underlying doc failure.

@DilumAluthge DilumAluthge marked this pull request as draft August 27, 2023 23:08
@codecov-commenter
Copy link

codecov-commenter commented Aug 27, 2023

Codecov Report

Merging #1046 (07acd86) into dev (7c677a2) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #1046   +/-   ##
=======================================
  Coverage   60.97%   60.97%           
=======================================
  Files           2        2           
  Lines          41       41           
=======================================
  Hits           25       25           
  Misses         16       16           

@DilumAluthge DilumAluthge changed the title CI: fix the YAML syntax for the docs job CI: fix the YAML syntax for the docs job, and thus properly surface any docbuild failures Aug 28, 2023
@DilumAluthge DilumAluthge marked this pull request as ready for review August 28, 2023 07:09
@DilumAluthge
Copy link
Member Author

@ablaom This is now ready for review.

@ablaom
Copy link
Member

ablaom commented Aug 28, 2023

@OkonSamuel Can you please review this and follow up? I think we need a PR to master to test the current fail is detected.

@DilumAluthge
Copy link
Member Author

I can push a commit to this branch to demonstrate that it detects the failure.

@DilumAluthge
Copy link
Member Author

@ablaom As you can see on the test commit d66d829, we correctly detect the docs failure.

@ablaom
Copy link
Member

ablaom commented Aug 30, 2023

Thanks @DilumAluthge . I'm convinced. If you could kindly restore to previous state we can merge.

@OkonSamuel
Copy link
Member

@DilumAluthge But I don't see how the code differs from what was initially there. Any idea what was the reason for the silent failures?

@DilumAluthge
Copy link
Member Author

Yeah. The YAML wasn't getting parsed correctly. So while we had intended to write this:

@info "attempting to build the docs"
run(`julia --project=docs docs/make.jl`)

Where that would have been two separate lines, we instead wrote this:

@info "attempting to build the docs" run(`julia --project=docs docs/make.jl`)

Where it all became one line. So it was equivalent to writing the following in Julia:

@info "my message" f()

In Julia, if you write @info "my message" f(), and if f() throws an exception, the overall @info will NOT throw an exception; it will print a warning message, but it will not error.

@ablaom
Copy link
Member

ablaom commented Aug 31, 2023

Thanks for that @DilumAluthge . Can we please have a "restore" commit so that docs don't get generated on PR's to dev?

Copy link
Member

@ablaom ablaom left a comment

Choose a reason for hiding this comment

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

Good to go!

Thanks @DilumAluthge for jumping in here.

@ablaom ablaom merged commit 347a3ab into JuliaAI:dev Aug 31, 2023
3 checks passed
@DilumAluthge DilumAluthge deleted the patch-1 branch August 31, 2023 02:31
@DilumAluthge
Copy link
Member Author

@ablaom Can you make a PR to merge dev into master?

@ablaom
Copy link
Member

ablaom commented Aug 31, 2023

I was going to wait for a fix to the cause of the fail (tracking this at #1045). I haven't got around to that.

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.

None yet

4 participants