[Ignore] test use of ldar rather than ldapr #24031
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
severity: fips change
|
crud, yes. Let me re-run this |
|
after re-enabling the test, running 10 iterations of the macosx 14 ci job, the failure is still not observed. I believe prior findings hold here, making the single instruction change on the virtualized M1 core from ldapr to ldar makes the problem abate. I should also note the cpu info indicates that we have 3 physical cpus on this system, with 3 separate l1 caches and a shared l2 core |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please ignore - conducting a test of ldar vs ldapr in CI on a virtualized mac