[release/2.3] Fix miopenStatusInternalError caused in new ROCm6.0 CI docker images #126942
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.
Fixes MIOpen sqlite error observed when trying to open database file.
This was observed when recent changes to bump the triton commit triggered a rebuild of the CI base docker images. These errors were observed first during the ROCm 6.0 CI upgrade and a workaround was put in place.
However, it seems that workaround didn't work during the rebuild, so this PR attempts a (better?) workaround, essentially by trying to set
journal_mode
todelete
instead ofoff
. For some reason, this seems to work for the gfx90a and gfx908 kdbs which havejournal_mode
originally set towal
(write-ahead logging) - which needs write permissions for the user invoking MIOpen (ie. jenkins). This PR also introduces logic to check that the finaljournal_mode
is eitherdelete
oroff
, either of which should be sufficient to get around the permission error.cc @jeffdaily @sunway513 @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang