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

run_result being accessed before assignment. #781

Closed
Paul-Ferrell opened this issue Aug 2, 2024 · 2 comments · Fixed by #783
Closed

run_result being accessed before assignment. #781

Paul-Ferrell opened this issue Aug 2, 2024 · 2 comments · Fixed by #783
Assignees

Comments

@Paul-Ferrell
Copy link
Collaborator

We seem to be hitting an issue with result parsing in Pavilion. Seems like it's trying access run_result before assignment. Oddly, it's only happening on some tests. Maybe when the test application has completed output, but not returned a value and the pavilion timeout is hit. Results in a results.json with only 5 values in it. The results.log is empty. Running pav results -L -r <test_id> results in a full log that shows a full test result before adding result parsed entries, it parses the table as instructed, but then fails with the run_result issue and ends up with a very sparse results.json saved to disk.

@hwikle-lanl
Copy link
Collaborator

Can you provide me with one of the tests that's giving this behavior?

@hwikle-lanl
Copy link
Collaborator

Waiting on Nick to provide failing test.

@hwikle-lanl hwikle-lanl linked a pull request Aug 23, 2024 that will close this issue
7 tasks
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 a pull request may close this issue.

2 participants