-
Notifications
You must be signed in to change notification settings - Fork 2
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
Remove: AIRAM generic resource and underlying reason #9
Remove: AIRAM generic resource and underlying reason #9
Conversation
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.
This is sufficient for the internal CI to trigger a build and push the 2.1.0 version inside the z43 docker repo.
Then in the images sync tool just add this version to the deployment you intend to use it and it will eventually be build.
Make sure that after this PR is merged the CI is green in the master branch of this repo. Only then then builder will pickup this version and automatically built it for you
@mrnicegyu11 I wonder why you don't have a CI run for this |
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.
trigger CI
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.
Go ahead and merge it. The CI should build it in master inside this REPO
when I recreated the PR it did not trigger the CI. I don't know why |
This PR
TF_FORCE_GPU_ALLOW_GROWTH=true
env-var in the dockerfile of Tensorflow stopping tensorflow from greedily allocating all GPU VRAM@GitHK can you advice if there is CI/CD or how this should be published to all ospars? thx!
CC @YuryHrytsuk When this gets in there will be no more AIRAM service.