Skip to content

[PR] Integrating Juliet testsuite#148

Draft
elazaro-riverside wants to merge 26 commits intomainfrom
integrating-juliet-testsuite
Draft

[PR] Integrating Juliet testsuite#148
elazaro-riverside wants to merge 26 commits intomainfrom
integrating-juliet-testsuite

Conversation

@elazaro-riverside
Copy link
Collaborator

No description provided.

@elazaro-riverside elazaro-riverside self-assigned this Mar 16, 2026
@elazaro-riverside elazaro-riverside added CVEAssert Related to CVEAssert component remediation tracking Status of remediation coverage labels Mar 16, 2026
Ethan Lazaro added 2 commits March 17, 2026 14:37
…eld in the summary table that enumerates the number of cases that failed to build due to lack of C++ support.
root_dir = str(Path(__file__).parent)


# Data type packages testname, testnumber, and exitcode (pass, fail, or exception)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The comment explains exit code could be one of three things (pass, fail, or exception), but the type of exit code is "int" and the definition of Result does not explain the mapping of these three cases.

Maybe a comment above exit_code?
Even better would be encoding the three cases into the type system somehow... an outcome field with an enum type or subclasses of Result that add additional metadata for each case?

Comment on lines +226 to +227

else:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest the early exit pattern here.
Put "continue" at the end of the if, then remove the else and move the rest of the function back one level of indentation.

Once you get to the failed to compile state, there is nothing left to do in this iteration of the loop

Comment on lines +246 to +247
elif executed_binary.returncode == 0:
incorrect_exit_code += 1
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happens is the return code is something other than 0, 3, or -11? Shouldn't we account for that possibility as well?

Comment on lines +251 to +252
if use_cpp:
failed_to_compile_cpp_build += 1
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't you use this failed_to_compile_cpp counter if the compiler exits with a non-zero code?

elif executed_binary.returncode == 0:
incorrect_exit_code += 1

except Exception as e:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you used the check=True option on subprocess.run(compile_cmd...) then you could share this error handling code.

check=True turns process.returncode == 0 into an exception.

Ethan Lazaro added 2 commits March 20, 2026 14:24
…his function used to look for matches agains the specified pattern AND search the function for a function name.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CVEAssert Related to CVEAssert component remediation tracking Status of remediation coverage

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants