Skip to content

Issues: rust-lang/rust

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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
3 Open 1 Closed
3 Open 1 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

ICE with multiple attributes on a test function C-bug Category: This is a bug. F-custom_test_frameworks `#![feature(custom_test_frameworks)]` I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#100263 opened Aug 8, 2022 by HaimYosefHaim
1
2
custom_test_frameworks doesn't work with plain functions A-libtest Area: `#[test]` / the `test` library C-bug Category: This is a bug. F-custom_test_frameworks `#![feature(custom_test_frameworks)]` requires-nightly This issue requires a nightly compiler in some way.
#65210 opened Oct 8, 2019 by exFalso
2
Tracking issue for eRFC 2318, Custom test frameworks A-libtest Area: `#[test]` / the `test` library B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC F-custom_test_frameworks `#![feature(custom_test_frameworks)]` S-tracking-design-concerns Status: There are blocking design concerns. S-tracking-needs-summary Status: It's hard to tell what's been done and what hasn't! Someone should do some investigation. T-cargo Relevant to the cargo team, which will review and decide on the PR/issue. T-dev-tools Relevant to the dev-tools subteam, which will review and decide on the PR/issue. T-lang Relevant to the language team, which will review and decide on the PR/issue. T-testing-devex Relevant to the testing devex team (testing DX), which will review and decide on the PR/issue. WG-embedded Working group: Embedded systems
#50297 opened Apr 28, 2018 by Centril
10 tasks
106
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.