Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Emit error from k frontend when kore-exec fails #2862

Merged
merged 7 commits into from
Sep 14, 2022
Merged

Conversation

SchmErik
Copy link
Contributor

@SchmErik SchmErik commented Sep 7, 2022

kore-exec output can take up a lot of screen space. This change adds a
error message to claify that the call to kore-exec either resulted in a
stuck state or a crash when kore-exec returns a non-successful status.
closes: #2576

Erik Kaneda added 2 commits September 7, 2022 15:34
kore-exec output can take up a lot of screen space. This change adds a
error message to claify that the call to kore-exec either resulted in a
stuck state or a crash when kore-exec returns a non-successful status.
@SchmErik SchmErik requested review from radumereuta and removed request for radumereuta September 7, 2022 22:40
@SchmErik SchmErik marked this pull request as draft September 7, 2022 22:41
@radumereuta
Copy link
Contributor

Do not use the word stuck since it has a different meaning in ML.
stuck = no rules from the semantics can apply
Could say - the backend stopped and can't continue. (see output for more info).

@SchmErik SchmErik marked this pull request as ready for review September 13, 2022 18:17
@rv-jenkins rv-jenkins merged commit 16b3dc1 into master Sep 14, 2022
@rv-jenkins rv-jenkins deleted the kprove-errors branch September 14, 2022 14:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Better distinction between stuck backend and crashed backend
3 participants