Move more rustdoc-html tests using --test into the right folder - #162014
Move more rustdoc-html tests using --test into the right folder#162014GuillaumeGomez wants to merge 4 commits into
rustdoc-html tests using --test into the right folder#162014Conversation
| //@ compile-flags: --crate-type lib | ||
|
|
There was a problem hiding this comment.
| //@ compile-flags: --crate-type lib |
or remove it altogether since it's not really relevant (rustdoc doesn't look for main even if the crate type is bin)
There was a problem hiding this comment.
Yeah actually I need to remove it.
On it. ;)
|
bd5786a to
8374270
Compare
| @@ -1,5 +1,4 @@ | |||
| //@ check-pass | |||
| // compile-args: --cap-lints=warn -Fwarnings | |||
There was a problem hiding this comment.
Wait, this should be converted to //@ compile-flags like you did before. This test specifically intended to test the interaction between --cap-lints=warn and -Fwarnings as the paragraph states below.
Or did that lead to a failure? If so we might want to open a GH issue & investigate further.
There was a problem hiding this comment.
Accidental removal while trying to apply #162014 (comment) (there's still the corresp. *.stderr file)?.
This comment has been minimized.
This comment has been minimized.
8374270 to
fba1d54
Compare
This comment has been minimized.
This comment has been minimized.
fba1d54 to
815bbce
Compare
This comment has been minimized.
This comment has been minimized.
815bbce to
614d9ea
Compare
|
@bors r=fmease rollup |
614d9ea to
fa9cd5b
Compare
|
Some changes occurred in src/tools/compiletest cc @jieyouxu |
|
This pull request was unapproved. |
|
This pull request was unapproved. This PR was contained in a rollup (#162100), which was unapproved. |
|
@bors r=fmease rollup |
|
@bors r- |
|
This pull request was unapproved. |
92e4d2a to
5ba810f
Compare
|
Now it's good. @bors r=fmease rollup |
…ease Move more `rustdoc-html` tests using `--test` into the right folder Follow-up of rust-lang#161944. I double-checked if more `rustdoc-html` tests were in the wrong folder and... yeah. So fixing that too. I'll send a patch to prevent that in the future (in `compiletest` I guess, doesn't seem like a `tidy` thing). Oh also second commit is me realizing that some ui tests were using `compile-args` (which doesn't exist anymore) and without `@`. Anyway, fixed that too. r? @fmease
…ease Move more `rustdoc-html` tests using `--test` into the right folder Follow-up of rust-lang#161944. I double-checked if more `rustdoc-html` tests were in the wrong folder and... yeah. So fixing that too. I'll send a patch to prevent that in the future (in `compiletest` I guess, doesn't seem like a `tidy` thing). Oh also second commit is me realizing that some ui tests were using `compile-args` (which doesn't exist anymore) and without `@`. Anyway, fixed that too. r? @fmease
|
💔 I suspect this PR failed tests as part of a rollup After fixing the problem, consider running a try job for the failed job before re-approving. Link to failure: #162139 (comment) |
|
This pull request was unapproved. This PR was contained in a rollup (#162139), which was unapproved. |
|
Arf, a test stdout was only generated on mac. Talk about bad luck. :') @bors try jobs=aarch64-apple-1 |
This comment has been minimized.
This comment has been minimized.
Move more `rustdoc-html` tests using `--test` into the right folder try-job: aarch64-apple-1
View all comments
Follow-up of #161944.
I double-checked if more
rustdoc-htmltests were in the wrong folder and... yeah. So fixing that too. I'll send a patch to prevent that in the future (incompiletestI guess, doesn't seem like atidything).Oh also second commit is me realizing that some ui tests were using
compile-args(which doesn't exist anymore) and without@. Anyway, fixed that too.r? @fmease