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
In case my code panics in this common pattern, it is somewhat difficult to figure out which original file has caused the failure. Would it be possible for glob! to use catch_unwind and report the file being processed?
glob!("../tests/fixtures", "**/*.txt", |file| {// this panic is deep inside the code,// without any knowledge of the current file
panic!("something panicked");
});
Expected output
---- my_test stdout ----
while processing `some_path/my_input_file_discovered_by_glob.txt`:
thread 'my_test' panicked at <some_file>:
My error message
The text was updated successfully, but these errors were encountered:
Maybe there could be a flag that controls catching of panics. I think the issue is that the rust testing infrastructure is already pretty brittle as it stands and catching down panics might be a bit too magic?
In case my code panics in this common pattern, it is somewhat difficult to figure out which original file has caused the failure. Would it be possible for
glob!
to usecatch_unwind
and report the file being processed?Expected output
The text was updated successfully, but these errors were encountered: