Skip to content

fix: Return exit code 1 when fe-driver2 encounters errors#1059

Closed
Turupawn wants to merge 1 commit intoargotorg:fe-v2from
Turupawn:check-v2
Closed

fix: Return exit code 1 when fe-driver2 encounters errors#1059
Turupawn wants to merge 1 commit intoargotorg:fe-v2from
Turupawn:check-v2

Conversation

@Turupawn
Copy link
Contributor

This PR ensures that fe-driver2 commands exits with code 1 when errors are detected, preventing silent failures.

This changes can help building CI automations like this one that I'm building now.

@sbillig
Copy link
Collaborator

sbillig commented Feb 18, 2025

@Turupawn The fe-v2 branch has been merged into master, and is now defunct (I should have deleted it when I merged it in). The change you made is good, but the underlying code has changed. There's a basic fe crate again (which just calls a driver function). The appropriate place to add your change is around here: https://github.com/ethereum/fe/blob/e0d627350f8607fe3247a6a070a4453f0857286d/crates/driver/src/lib.rs#L106
(we should exit with a code if there are core_diags or local_diags).

@Turupawn
Copy link
Contributor Author

Replaced by #1060

@Turupawn Turupawn closed this Feb 18, 2025
@Turupawn Turupawn deleted the check-v2 branch February 19, 2025 18:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants