Output tests/debuginfo raw JSON data on failure in CI - #162002
Conversation
|
|
|
Thanks! Do you have a link to a job where this happened, so I can take a look at it? In general, this is a nice improvement, though not perfect by far (but that is for follow-up PRs). If this happens for multiple tests and/or OSes, it would be annoying to manually update all that. I wonder if we could generate a single git patch file that could then be updated as a GitHub Actions artifact, and after download you could just |
|
Should be this one: #161574 (comment) Though that run didnt have the "use this to bless" tip, just the raw json. |
|
Thanks. It is a bit non-trivial to copy, but better than nothing. Thanks! Let's land this as an initial implementation. @bors r+ rollup |
Output `tests/debuginfo` raw JSON data on failure in CI As discussed a few days ago, this change allows people to "manually bless" in cases where they do not have access to the target that caused the failure in CI. When run outside of CI, no json is dumped (since it's assumed you're running it locally and thus can just use `--bless`). It makes things a lot easier (for the user) to present this as minified, single-line json, but obviously we'd prefer if it's formatted after they copypaste it. Maybe a tidy pass to enforce that? I'm not sure if we have anything that currently handles JSON, but I can look into it. r? @Kobzol , @jieyouxu
Rollup of 5 pull requests Successful merges: - #161556 (document some rustc_dump attributes) - #161353 (Add test for parallel compiler reproducible build) - #161776 (Add a couple polonius tests and move universal region liveness generation) - #162002 (Output `tests/debuginfo` raw JSON data on failure in CI) - #162049 (Fix a compile error on the ESP-IDF target)
Output `tests/debuginfo` raw JSON data on failure in CI As discussed a few days ago, this change allows people to "manually bless" in cases where they do not have access to the target that caused the failure in CI. When run outside of CI, no json is dumped (since it's assumed you're running it locally and thus can just use `--bless`). It makes things a lot easier (for the user) to present this as minified, single-line json, but obviously we'd prefer if it's formatted after they copypaste it. Maybe a tidy pass to enforce that? I'm not sure if we have anything that currently handles JSON, but I can look into it. r? @Kobzol , @jieyouxu
…uwer Rollup of 6 pull requests Successful merges: - #162058 (Port 1.98.1 release notes into main) - #161556 (document some rustc_dump attributes) - #161776 (Add a couple polonius tests and move universal region liveness generation) - #162002 (Output `tests/debuginfo` raw JSON data on failure in CI) - #162049 (Fix a compile error on the ESP-IDF target) - #162054 (Refine InferCtxtInner docs)
…uwer Rollup of 6 pull requests Successful merges: - #162058 (Port 1.98.1 release notes into main) - #161556 (document some rustc_dump attributes) - #161776 (Add a couple polonius tests and move universal region liveness generation) - #162002 (Output `tests/debuginfo` raw JSON data on failure in CI) - #162049 (Fix a compile error on the ESP-IDF target) - #162054 (Refine InferCtxtInner docs)
…uwer Rollup of 6 pull requests Successful merges: - #162058 (Port 1.98.1 release notes into main) - #161556 (document some rustc_dump attributes) - #161776 (Add a couple polonius tests and move universal region liveness generation) - #162002 (Output `tests/debuginfo` raw JSON data on failure in CI) - #162049 (Fix a compile error on the ESP-IDF target) - #162054 (Refine InferCtxtInner docs)
Rollup merge of #162002 - Walnut356:json_dump, r=Kobzol Output `tests/debuginfo` raw JSON data on failure in CI As discussed a few days ago, this change allows people to "manually bless" in cases where they do not have access to the target that caused the failure in CI. When run outside of CI, no json is dumped (since it's assumed you're running it locally and thus can just use `--bless`). It makes things a lot easier (for the user) to present this as minified, single-line json, but obviously we'd prefer if it's formatted after they copypaste it. Maybe a tidy pass to enforce that? I'm not sure if we have anything that currently handles JSON, but I can look into it. r? @Kobzol , @jieyouxu
As discussed a few days ago, this change allows people to "manually bless" in cases where they do not have access to the target that caused the failure in CI. When run outside of CI, no json is dumped (since it's assumed you're running it locally and thus can just use
--bless).It makes things a lot easier (for the user) to present this as minified, single-line json, but obviously we'd prefer if it's formatted after they copypaste it. Maybe a tidy pass to enforce that? I'm not sure if we have anything that currently handles JSON, but I can look into it.
r? @Kobzol , @jieyouxu