|
1 | 1 | name: "~Sandbox"
|
2 | 2 |
|
3 | 3 | on:
|
4 |
| - workflow_dispatch: |
| 4 | + push: |
5 | 5 |
|
6 | 6 | jobs:
|
7 |
| - sandbox: |
8 |
| - runs-on: ubuntu-22.04 |
9 |
| - steps: |
10 |
| - - name: Login to GitHub Container Registry |
11 |
| - uses: docker/login-action@v3 |
12 |
| - with: |
13 |
| - registry: ghcr.io |
14 |
| - username: ${{ github.repository_owner }} |
15 |
| - password: ${{ secrets.GITHUB_TOKEN }} |
| 7 | + runner: |
| 8 | + uses: ./.github/workflows/_runner_ondemand_slurm.yaml |
| 9 | + with: |
| 10 | + NAME: "TEST" |
| 11 | + LABELS: "A100,${{ github.run_id }}" |
| 12 | + TIME: "01:00:00" |
| 13 | + secrets: inherit |
16 | 14 |
|
17 |
| - - name: Print usage |
18 |
| - run: | |
19 |
| - cat << EOF |
20 |
| - This is an empty workflow file located in the main branch of your |
21 |
| - repository. It serves as a testing ground for new GitHub Actions on |
22 |
| - development branches before merging them to the main branch. By |
23 |
| - defining and overloading this workflow on your development branch, |
24 |
| - you can test new actions without affecting your main branch, ensuring |
25 |
| - a smooth integration process once the changes are ready to be merged. |
| 15 | + jax-unit-test: |
| 16 | + strategy: |
| 17 | + fail-fast: false |
| 18 | + matrix: |
| 19 | + GPU_ARCH: [V100, A100] |
| 20 | + # ensures A100 job lands on dedicated runner for this particular job |
| 21 | + runs-on: |
| 22 | + - self-hosted |
| 23 | + - "${{ matrix.GPU_ARCH }}" |
| 24 | + - "${{ matrix.GPU_ARCH == 'A100' && github.run_id || '' }}" |
| 25 | + env: |
| 26 | + BADGE_FILENAME_FULL: ${{ inputs.BADGE_FILENAME }}-${{ matrix.GPU_ARCH }}.json |
| 27 | + steps: |
| 28 | + - name: Print environment variables |
| 29 | + run: env |
26 | 30 |
|
27 |
| - Usage: |
28 |
| - |
29 |
| - 1. In your development branch, modify the sandbox.yml workflow file |
30 |
| - to include the new actions you want to test. Make sure to commit |
31 |
| - the changes to the development branch. |
32 |
| - 2. Navigate to the 'Actions' tab in your repository, select the |
33 |
| - '~Sandbox' workflow, and choose your development branch from the |
34 |
| - branch dropdown menu. Click on 'Run workflow' to trigger the |
35 |
| - workflow on your development branch. |
36 |
| - 3. Once you have tested and verified the new actions in the Sandbox |
37 |
| - workflow, you can incorporate them into your main workflow(s) and |
38 |
| - merge the development branch into the main branch. Remember to |
39 |
| - revert the changes to the sandbox.yml file in the main branch to |
40 |
| - keep it empty for future testing. |
41 |
| - EOF |
| 31 | + - name: Print GPU information |
| 32 | + run: nvidia-smi |
0 commit comments