Closed sassy-asjp closed 1 month ago
I don't think there is any mechanism where the change could have possibly affected Linux opNav, so I think the CI failure was caused by some flaky test timing out.
@sassy-asjp , I agree that this looks like a time-out issue. For the life of me I can't figure out why some test runs stall at different places and then time out occasionally. This started happening when I added additional tests to be run. It isn't the same run that times out, and not always at the same place. For now I simply re-run the tests that time out. Not ideal, I agree.
I was able to test this on my macOS laptop and it worked. I added updated documentation and release notes.
Description
The fix described in #826 which guesses the correct RPATH (similar to how it works on Linux) was implemented.
Verification
Tested:
Documentation
None
Future work
None