fix(entrypoint): tests fail on program crates #1687
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cargo test
usually creates a new "fn main" to be the entry point for running testswhen we use
!#[no_main]
the test harness has unexpected behavior and just calls our main functionyou cant just not have a main symbol because rustc will complain
compilation is currently broken in the template repo, and was fixed here 1c1f84d
if were not targeting the zkvm, we return an empty main function that has return values that the harness will expect
todo: ux? We should add a log somewhere if a user does try to make tests in the program crate
Originally from #1661