Skip to content

Provide ignore message in the result of test#92714

Merged
bors merged 1 commit intorust-lang:masterfrom
yanganto:ignore-message
Feb 25, 2022
Merged

Provide ignore message in the result of test#92714
bors merged 1 commit intorust-lang:masterfrom
yanganto:ignore-message

Conversation

@yanganto
Copy link
Contributor

Provide ignore the message in the result of the test.

This PR does not need RFC, because it is about the presentation of the report of cargo test.

However, the following document listed here helps you to know about PR.

If there is something improper, please let me know.
Thanks.

@rust-highfive
Copy link
Contributor

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Mark-Simulacrum (or someone else) soon.

Please see the contribution instructions for more information.

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Jan 10, 2022
@rust-log-analyzer

This comment has been minimized.

@yanganto yanganto marked this pull request as draft January 10, 2022 09:50
@rust-log-analyzer

This comment has been minimized.

@rustbot rustbot added the T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. label Jan 10, 2022
@rust-log-analyzer

This comment has been minimized.

@rustbot rustbot added the T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. label Jan 10, 2022
@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@ehuss
Copy link
Contributor

ehuss commented Jan 10, 2022

I think it is tricky to change the definition of TestDesc because we want to be able to run the standard library tests with the beta compiler (which won't have the changes to TestDesc). The proc-macro expansion of the #[test] attribute generated by the beta compiler will have TestDesc without the new field, but it is being built with the new definition.

I think you will need to annotate the field (and everywhere it is used) with #[cfg(not(bootstrap))]. The bootstrap cfg is only set when building with the beta compiler. This will likely be very tricky, so I'm glossing over the details, but hopefully that can set you in the right direction.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@yanganto

This comment has been minimized.

@Mark-Simulacrum

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@Mark-Simulacrum Mark-Simulacrum added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Feb 17, 2022
@Mark-Simulacrum
Copy link
Member

@bors r+ rollup

Thank you for all the hard work here -- squashed the commits down and approving. You can keep an eye on progress in the bors queue -- https://bors.rust-lang.org/queue/rust

@bors
Copy link
Collaborator

bors commented Feb 18, 2022

📌 Commit 159e3795f33e83a19dcb0547cfbb513506409830 has been approved by Mark-Simulacrum

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Feb 18, 2022
@Mark-Simulacrum Mark-Simulacrum added the relnotes Marks issues that should be documented in the release notes of the next release. label Feb 18, 2022
@rust-log-analyzer

This comment has been minimized.

@Mark-Simulacrum
Copy link
Member

@bors r+

@bors
Copy link
Collaborator

bors commented Feb 18, 2022

📌 Commit 2f85ee3 has been approved by Mark-Simulacrum

@rust-log-analyzer

This comment has been minimized.

@yanganto
Copy link
Contributor Author

Hi @matthiaskrgr,
I hope the merge(679f4dd) will not mess up the rollup process, I uncarefully clicked the fetch-upstream button from the GitHub web page. And this PR was collected in #94120. If there is something I can do to fix this, please let me know thanks.

@yanganto
Copy link
Contributor Author

Hi @Mark-Simulacrum @matthiaskrgr, I hope this PR is good for rolling up, if there is something can do from my side please let me know. Thanks. 🙏

@yanganto
Copy link
Contributor Author

@bors retry

@bors
Copy link
Collaborator

bors commented Feb 24, 2022

@yanganto: 🔑 Insufficient privileges: not in try users

As an example:

    #[test]
    #[ignore = "not yet implemented"]
    fn test_ignored() {
        ...
    }

Will now render as:

    running 2 tests
    test tests::test_ignored ... ignored, not yet implemented

    test result: ok. 1 passed; 0 failed; 1 ignored; 0 measured; 0 filtered out; finished in 0.00s
@Mark-Simulacrum
Copy link
Member

We typically avoid merge commits, instead preferring to rebase -- I've done so now, @bors r+

@bors
Copy link
Collaborator

bors commented Feb 24, 2022

📌 Commit bb3b557 has been approved by Mark-Simulacrum

@rust-log-analyzer
Copy link
Collaborator

The job x86_64-gnu-tools failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)
  IMAGE: x86_64-gnu-tools
##[endgroup]
From https://github.com/rust-lang/rust
 * branch              master     -> FETCH_HEAD
Searching for toolstate changes between 4b043faba34ccc053a4d0110634c323f6c03765e and 847a02cb48a90efa909d0511ed1cd978ca0e3d2d
Rustdoc was updated
##[group]Run src/ci/scripts/verify-channel.sh
src/ci/scripts/verify-channel.sh
shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
env:
---
thread '[compile-fail] compile-fail/validity/invalid_fnptr_uninit.rs' panicked at 'explicit panic', /cargo/registry/src/github.com-1ecc6299db9ec823/compiletest_rs-0.7.1/src/runtest.rs:1092:13
stack backtrace:
thread '[compile-fail] compile-fail/validity/fn_ptr_offset.rs' panicked at 'explicit panic', /cargo/registry/src/github.com-1ecc6299db9ec823/compiletest_rs-0.7.1/src/runtest.rs:1092:13
status: exit status: 1
command: "/checkout/obj/build/x86_64-unknown-linux-gnu/stage2-tools-bin/miri" "tests/compile-fail/validity/invalid_fnptr_uninit.rs" "-L" "/tmp/compiletestfTVevb" "--target=x86_64-unknown-linux-gnu" "--error-format" "json" "-C" "prefer-dynamic" "-o" "/tmp/compiletestfTVevb/validity/invalid_fnptr_uninit.stage-id" "-A" "unused" "--edition" "2018" "-Astable-features" "--sysroot" "/home/user/.cache/miri/HOST" "-L" "/tmp/compiletestfTVevb/validity/invalid_fnptr_uninit.stage-id.aux"
    Error {
        line_num: 9,
        kind: Some(
            Error,
---
stack backtrace:
   0: std::panicking::begin_panic::<&str>
   1: <compiletest_rs::runtest::TestCx>::run_cfail_test
   2: compiletest_rs::runtest::run
   3: <compiletest_rs::make_test_closure::{closurethread '#[compile-fail] compile-fail/validity/execute_memory.rs0}' panicked at ' as explicit paniccore', ::/cargo/registry/src/github.com-1ecc6299db9ec823/compiletest_rs-0.7.1/src/runtest.rsops:::1092function:::13FnOnce
    },
]

not found errors (from test file): [
---
error: tests/compile-fail/validity/fn_ptr_offset.rs:9: expected error not found: expected a function pointer

error: 1 unexpected errors found, 1 expected errors not found
status: exit status: 1
command: "/checkout/obj/build/x86_64-unknown-linux-gnu/stage2-tools-bin/miri" "tests/compile-fail/validity/fn_ptr_offset.rs" "-L" "/tmp/compiletestfTVevb" "--target=x86_64-unknown-linux-gnu" "--error-format" "json" "-C" "prefer-dynamic" "-o" "/tmp/compiletestfTVevb/validity/fn_ptr_offset.stage-id" "-A" "unused" "--edition" "2018" "-Astable-features" "--sysroot" "/home/user/.cache/miri/HOST" "-L" "/tmp/compiletestfTVevb/validity/fn_ptr_offset.stage-id.aux"
    Error {
        line_num: 9,
        kind: Some(
            Error,
---
error: tests/compile-fail/validity/execute_memory.rs:6: expected error not found: expected a function pointer

error: 0 unexpected errors found, 1 expected errors not found
status: exit status: 1
command: "/checkout/obj/build/x86_64-unknown-linux-gnu/stage2-tools-bin/miri" "tests/compile-fail/validity/execute_memory.rs" "-L" "/tmp/compiletestfTVevb" "--target=x86_64-unknown-linux-gnu" "--error-format" "json" "-C" "prefer-dynamic" "-o" "/tmp/compiletestfTVevb/validity/execute_memory.stage-id" "-A" "unused" "--edition" "2018" "-Astable-features" "--sysroot" "/home/user/.cache/miri/HOST" "-L" "/tmp/compiletestfTVevb/validity/execute_memory.stage-id.aux"
    Error {
        line_num: 6,
        kind: Some(
            Error,
---
.......... (50/60)
.......... (60/60)


/checkout/src/test/rustdoc-gui/search-result-go-to-first.goml An exception occured: Failed to launch the browser process!
Inconsistency detected by ld.so: dl-tls.c: 493: _dl_allocate_tls_init: Assertion `listp->slotinfo[cnt].gen <= GL(dl_tls_generation)' failed!


TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/master/docs/troubleshooting.md
== STACKTRACE ==
Error
Error
    at innerRunTestCode (/node-v14.4.0-linux-x64/lib/node_modules/browser-ui-test/src/index.js:468:16)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

@Mark-Simulacrum
Copy link
Member

Seems likely to be a spurious failure.

@yanganto
Copy link
Contributor Author

@Mark-Simulacrum Thanks for your help on this. 😄

@m-ou-se
Copy link
Member

m-ou-se commented Mar 3, 2022

This seems to have modified the output of --logfile rather than the output to the console. Was that intentional?

screenshot

Is there a test for the expected output?

@Mark-Simulacrum
Copy link
Member

Hm, no, that was not intentional (I had not realized we even had a logfile?).

@yanganto
Copy link
Contributor Author

yanganto commented Mar 3, 2022

@m-ou-se Thanks for this, I am fixing this. 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

relnotes Marks issues that should be documented in the release notes of the next release. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants