b84c4d7488
rather than the results telling you an individual file was a badf. why? i think the old behavior was too clever, and makes it harder to write a scheduler. * what should the call do when you pass it some badf and some not-badf? i don't think anything besides exiting early is the correct answer. * the results vector tells you something that the scheduler had to say about the file, not about your inputs. the errno of the function always says what the validity of the inputs was
This is the test-programs crate, which builds and runs whole programs
compiled to wasm32-wasi.
To actually run these tests, the test-programs feature must be enabled, e.g.:
cargo test --features test-programs/test_programs --package test-programs