You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run the tests from main on my local hardware (german lang), tests missing_manifest and patch_path_doesnt_exist fail.
missing_manifest
I don't know why this is failing.
2 2 │ Caused by:
3 3 │ `cargo metadata` exited with an error: error: failed to parse manifest at `[TEMPDIR]Cargo.toml`
4 4 │
5 5 │ Caused by:
6 │- virtual manifests must be configured with [workspace]
6 │+ manifest is missing either a `[package]` or a `[workspace]`
patch_path_doesnt_exist
OSERROR is printed in the user's configured OS lang.
0 0 │ error: Unable to run `cargo metadata`
1 1 │
2 2 │ Caused by:
3 │- 0: failed to start `cargo metadata`: [OSERROR]
4 │- 1: [OSERROR]
3 │+ 0: failed to start `cargo metadata`: Der Verzeichnisname ist ungültig.[OSERROR]
4 │+ 1: Der Verzeichnisname ist ungültig.[OSERROR]
The text was updated successfully, but these errors were encountered:
I think I've been overzealous with these snapshot tests. It's clearly not practical to assert on the OS errors.
I'd be happy to accept a PR that removes these assertions on cargo metadata failure messages, as long as we continue to assert on a failing status code.
When I run the tests from main on my local hardware (german lang), tests
missing_manifest
andpatch_path_doesnt_exist
fail.missing_manifest
I don't know why this is failing.
patch_path_doesnt_exist
OSERROR is printed in the user's configured OS lang.
The text was updated successfully, but these errors were encountered: