transformer-engine dependency fix#55
Open
xor2k wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
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.
Hi everybody,
I have a DGX Spark (
aarch64) at home and tried to getcosmos-predict2.5to run. I haven't tried so with x86, so I can't tell what's the situation there. However, three packages are not provided asaarch64versions:That's how I discovered this repo and I tried to build them myself.
When trying to build
transformer-engine, the build fails because in the build environment oftransformer-engineincludes a non-cuda version of PyTorch and the linein
bin/_build.shwill not actually install anything (especially,torchstays non-cuda).This is the build call (required for
cosmos-predict2.5as mentioned) that fails btw.The solution is to remove
torchfrom the build dependencies oftransformer-enginesince it will be installed in a specified version viabin/_build.shanyway. Since we want other package versions to stay locked in place until we provide an updated, working configuration, I've also removedtorchfrom theuv.lockoftransformer-engine. While usually, editing auv.lockmanually is not recommendable, in this particular case (removing a package) it stays identical if you runuv lockinpackages/transformer-engineand it's as clean as it gets I guess 😅Best, Michael