-
Notifications
You must be signed in to change notification settings - Fork 241
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
Add fin as a submodule #1588
Add fin as a submodule #1588
Conversation
In draft state until I verify behavior of Jenkins with git submodules. |
Why is fin developed independently? If it needs to be then why doesn't MIOpen use fin with Or is fin more tightly coupled with MIOpen that it needs to build with MIOpen? If so, then why is this in a separate repo? |
@JehandadKhan "Tuna Fin Build Test" stage has failed, and I guess that's expected? |
Completed work with converting Fin to a submodule. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@JehandadKhan it seems to be no functional changes except impacts from Jenkins file on CI?
@junliume This removes the Fin code copy from MIOpen, and instead it is tracked as a submodule. This change would remove the diffs we see in MIOpen when we change Fin. MIOpen changes here are for how the Jenkinsfile interacts with and builds the Fin repo. |
def no_cache = conf.get("no_cache", false) | ||
def dockerArgs = "--build-arg BUILDKIT_INLINE_CACHE=1 --build-arg PREFIX=${prefixpath} --build-arg GPU_ARCH='${gpu_arch}' --build-arg MIOTENSILE_VER='${miotensile_version}' --build-arg USE_TARGETID='${target_id}' --build-arg USE_MLIR='${mlir_build}' --build-arg USE_FIN='${build_fin}' " | ||
def dockerArgs = "--build-arg BUILDKIT_INLINE_CACHE=1 --build-arg PREFIX=${prefixpath} --build-arg GPU_ARCH='${gpu_arch}' --build-arg MIOTENSILE_VER='${miotensile_version}' --build-arg USE_TARGETID='${target_id}' --build-arg USE_MLIR='${mlir_build}' " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove USE_FIN from Dockerfile.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cderb Let's remove unused code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@JehandadKhan oops
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@atamazov should USE_FIN
be removed from everywhere in the repo? I may need to update dockerfile too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@junliume I do not know. But removal of USE_FIN='${build_fin}'
at this line in Jenkinsfile makes USE_FIN unused in the Dockerfile, so it should be removed.
This PR removes the old fin code which was added verbatim and replaces it with a git submodule. This allows better tracking with the upstream repo which is developed independently.