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.

Sign up for GitHub

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

Jump to bottom

Report precise locations in evaluator error messages #1135

Open
anton-trunov opened this issue Aug 4, 2022 · 2 comments
Open

Report precise locations in evaluator error messages #1135

anton-trunov opened this issue Aug 4, 2022 · 2 comments
Labels
evaluator Scilla evaluator usability
Milestone
Scilla 0.14.0

Comments

@anton-trunov
Copy link
Contributor

It can report the 0:0 location in a number of cases. See #1134 for example.
@anton-trunov anton-trunov added evaluator Scilla evaluator usability labels Aug 4, 2022
@anton-trunov anton-trunov mentioned this issue Aug 4, 2022
Merged
@anton-trunov anton-trunov added this to the Scilla 0.13.0 milestone Aug 18, 2022
@jubnzv
Copy link
Contributor

jubnzv commented Sep 13, 2022 •
edited
Loading

It was partially closed by #1133.

This PR describes other cases when we report 0:0 locations:

We should also find more cases when we report 0:0, including such messages from the evaluator.

Probably, the simplest way to do this is to process the expected output of tests (using jq queries for example) and deal with them on a case-by-case basis.

@jjcnn jjcnn modified the milestones: Scilla 0.13.0, Scilla 0.14.0 Oct 17, 2022
@jjcnn
Copy link
Contributor

jjcnn commented Oct 17, 2022

Moving to Scilla 0.14.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
evaluator Scilla evaluator usability
Projects
None yet
Milestone
Scilla 0.14.0
Development

No branches or pull requests
3 participants
@anton-trunov @jubnzv @jjcnn