[NDTensorsMetalExt] Trying to add GPU testing to M1 jenkins

[kmp5VT]

Description

In this PR I am making minimal changes to get Jenkins to run CI testing on the mac M1's with Metal backend. It looks like I just need to add it to Jenkins and Dylan added juliaup for us to use different versions of Julia. Currently Metal is not supported on Julia 1.6 so I am only testing with release (1.10)

Checklist:

• Jenkins runs NDTensors unittest on the M1 mac
• Metal Unittests pass on Jenkins

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 53.45%. Comparing base (25e2bc5) to head (ed95e15).
Report is 4 commits behind head on main.

❗ Current head ed95e15 differs from pull request most recent head b3676fc. Consider uploading reports for the commit b3676fc to get more accurate results

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #1359       +/-   ##
===========================================
- Coverage   84.36%   53.45%   -30.91%     
===========================================
  Files         100       99        -1     
  Lines        8505     8452       -53     
===========================================
- Hits         7175     4518     -2657     
- Misses       1330     3934     +2604     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mtfishman]

Nice to see this already up and running, I like how the Jenkins tests are now organized, the way the test results are displayed in Jenkins now is nicer.

The Metal tests appear to be failing because resize!(::MtlArray, ::Integer) can't be found. I added that in JuliaGPU/Metal.jl#279 but it hasn't been included in a registered version of Metal.jl yet. We could using Pkg.dev("Metal") as a temporary workaround.

[mtfishman]

@maleadt sorry to ping you, but could you register a new version of Metal.jl?

[mtfishman]

Note that some of the latest test failures were caused by issues introduced in #1356.