Failure persistence file location for workspace member crates about proptest

[AltSysrq]

found that the source_path is relative to the workspace root, e.g. my_member_crate/src/lib.rs

Odd, what OS are you on? I thought file!() always gave an absolute path

[haraldmaida]

It all happens on Windows 10.
Tests are executed with Cargo test.
Rust itself is setup via rustup. Rust 1.22.1 stable

I thought I double check it and added a println("{:?}", file!()); to one of my tests in a member crate and it prints out: "member_crate\src\my_mod.rs".

[AltSysrq]

Thanks for the info! It looks like this problem also affected non-workspace projects as well.

This has been fixed in version 0.3.4, manually verified on Windows 10 with both non-workspace and workspace configurations. Anyone affected by this bug will need to manually move any persistence files to the correct location, for example by running in cmd or PS:

move my_member_crate\my_member_crate\somesource.proptest-regressions my_member_crate\proptest-regressions\somesource.txt

The exact location where the files were incorrectly placed was dependent on the working directory when the tests were run. This means that if you ran tests outside of cargo, it is theoretically possible to have multiple persistence files that belong in the same place. If this has happened, simply concatenating the respective files will merge them correctly.

[haraldmaida]

Unfortunately starting from proptest version 0.7 the exact same behavior as in the original issue is happening again. In version 0.5 and 0.6 everything works perfectly fine.

I'm on Windows 10. Rust 1.26.0 stable.

It makes no difference whether I call "cargo test" from the workspace directory or inside the directory of the member-crate.

If I can help somehow please let me know. Let me thank you for the great work on this crate. I really love to use proptest in my projects.

[AltSysrq]

Sorry about the regression, I'll take a look this weekend. I'll also see about adding some automated tests around it this time.

[AltSysrq]

This is fixed in 0.7.1, now including full-stack tests for both platforms.