Skip to content
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.

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

Add test case for #4167, marked as an expected failure. #4168

Merged
merged 1 commit into from
Sep 25, 2023

Conversation

jimblandy
Copy link
Member

@jimblandy jimblandy commented Sep 22, 2023

This adds a test case for #4167, marked as an expected failure with a comment referring to the issue.

Checklist

  • Run cargo clippy.
  • Run cargo clippy --target wasm32-unknown-unknown if applicable.
  • (not appropriate) Add change to CHANGELOG.md. See simple instructions inside file.

tests/tests/pipeline.rs Show resolved Hide resolved
@jimblandy
Copy link
Member Author

I think this is what you asked for??

Do we really have to skip every test that might panic on wasm?

@cwfitzgerald
Copy link
Member

Yeah we do - there's not a lot of good ways around this as we aren't using our own test harness on wasm.

@cwfitzgerald cwfitzgerald merged commit 3666f1a into gfx-rs:trunk Sep 25, 2023
20 checks passed
@jimblandy jimblandy deleted the issue-4167-test-case branch September 27, 2023 19:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants