-
Notifications
You must be signed in to change notification settings - Fork 63
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
Analyze test case BREAKPOINT_002 for race conditions #43
Labels
Comments
lsf37
added a commit
that referenced
this issue
Aug 21, 2021
These are currently BREAKPOINT_002 and SCHED0021. The corresponding issues #43 and #42 remain open, and when resolved positively, these tests should be enabled again for simulation runs. Signed-off-by: Gerwin Klein <[email protected]>
lsf37
added a commit
that referenced
this issue
Aug 21, 2021
These are currently BREAKPOINT_002 and SCHED0021. The corresponding issues #43 and #42 remain open, and when resolved positively, these tests should be enabled again for simulation runs. Signed-off-by: Gerwin Klein <[email protected]>
lsf37
added a commit
that referenced
this issue
Aug 21, 2021
These are currently BREAKPOINT_002 and SCHED0021. The corresponding issues #43 and #42 remain open, and when resolved positively, these tests should be enabled again for simulation runs. Signed-off-by: Gerwin Klein <[email protected]>
lsf37
added a commit
that referenced
this issue
Aug 23, 2021
These are currently BREAKPOINT_002 and SCHED0021. The corresponding issues #43 and #42 remain open, and when resolved positively, these tests should be enabled again for simulation runs. Signed-off-by: Gerwin Klein <[email protected]>
lsf37
added a commit
that referenced
this issue
Aug 23, 2021
These are currently BREAKPOINT_002 and SCHED0021. The corresponding issues #43 and #42 remain open, and when resolved positively, these tests should be enabled again for simulation runs. Signed-off-by: Gerwin Klein <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
seL4/seL4#462 had a failure in
BREAKPOINT_002
that seems completely unrelated to the changes in the PR, especially sicne the changes affect ARM and RISC-V only, but the test failed forPC99_release_gcc_32
.Analysze
BREAKPOINT_002
for potential race conditions.The text was updated successfully, but these errors were encountered: