Update build-test-lin.yml #381
Merged
Conversation
This file contains 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
Test Results Linux 1 files ±0 1 suites ±0 10m 7s ⏱️ -5s For more details on these failures, see this check. Results for commit 4c3331e. ± Comparison against base commit c2c4810. ♻️ This comment has been updated with latest results. |
Test Results Linux-CudaT 1 files ±0 1 suites ±0 11m 55s ⏱️ + 1m 39s For more details on these failures, see this check. Results for commit 4c3331e. ± Comparison against base commit c2c4810. |
joiskash
approved these changes
Aug 6, 2024
Vinayak-YB
pushed a commit
that referenced
this pull request
Aug 7, 2024
* Update build-test-lin.yml * Update build-test-lin.yml
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.
IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).
Fixes #[Issue]
Description
Disabled Git lfs install for arm cloud build
Alternative(s) considered
Have you considered any alternatives? And if so, why have you chosen the approach in this PR?
Type
Type Choose one: (Bug fix | Feature | Documentation | Testing | Other)
Screenshots (if applicable)
Checklist