about summary refs log tree commit diff
path: root/src/liballoc_jemalloc
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2017-12-29 03:23:37 +0000
committerbors <bors@rust-lang.org>2017-12-29 03:23:37 +0000
commit966fdf15e2d2cb37fd565980b82f12c3859e48b6 (patch)
tree3b187107654b35ae5d330511537feec8ca11ef18 /src/liballoc_jemalloc
parentec9be91e4366f57dcb88169c78daaee049857af0 (diff)
parentdfbb94664915354eb512c66833ece422bd2b9214 (diff)
downloadrust-966fdf15e2d2cb37fd565980b82f12c3859e48b6.tar.gz
rust-966fdf15e2d2cb37fd565980b82f12c3859e48b6.zip
Auto merge of #46883 - QuietMisdreavus:faildown, r=GuillaumeGomez
rustdoc: add option to abort the process on markdown differences

In the efforts of keeping the std docs free of markdown warnings, this PR adds a stopgap measure to make sure the CI fails if it detects a markdown difference. It does this by adding a new unstable flag to rustdoc, `--deny-render-differences`, which bootstrap then passes to rustdoc when documenting std and friends.

The implementation is... probably not the cleanest option. It currently adds an extra branch after it prints the markdown warnings, which just prints a final line and calls `::std::process::abort(1)`. I did it like this because if it just panics regularly, it looks like an ICE, an even though `html::render::run` returns a Result, that Result is also just `expect`ed immediately, generating the same problem. This way bypasses the panic handler at the top of the thread and looks like a proper failure. Since i don't have a real error Handler there, this is the best i can do without pulling in a real error system for rustdoc.

This PR is blocked on https://github.com/rust-lang/rust/pull/46853, which will fix the rendering differences that were present on master when i started this branch.
Diffstat (limited to 'src/liballoc_jemalloc')
0 files changed, 0 insertions, 0 deletions