Fix Mistral memory consumption with JAX and default dtype bug #4613
Triggered via pull request
February 23, 2024 05:46
tirthasheshpatel
Status
Success
Total duration
17m 59s
Artifacts
–
actions.yml
on: pull_request
Test the code with Keras 2
17m 48s
Check the code format
2m 24s
Matrix: Test the code with Keras 3
Annotations
5 warnings
|
Check the code format
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Test the code with Keras 3 (torch)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Test the code with Keras 3 (jax)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Test the code with Keras 3 (tensorflow)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Test the code with Keras 2
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|