Change default ckpt name
State: closed | Pull request: yes
Labels: name: bug

name: Run CICD

# What does this PR do ?

Add a one line overview of what this PR aims to accomplish.

**Collection**: [Note which collection this PR will affect]

# Changelog 
- Add specific line by line info of high level changes in this PR.

# Usage
* You can potentially add a usage example below

```python
# Add a code snippet demonstrating how to use this 
```

# GitHub Actions CI

The Jenkins CI system has been replaced by GitHub Actions self-hosted runners.

The GitHub Actions CI will run automatically when the "Run CICD" label is added to the PR.
To re-run CI remove and add the label again.
To run CI on an untrusted fork, a NeMo user with write access must first click "Approve and run".

# Before your PR is "Ready for review"
**Pre checks**:
- [ ] Make sure you read and followed [Contributor guidelines](https://github.com/NVIDIA/NeMo/blob/main/CONTRIBUTING.md)
- [ ] Did you write any new necessary tests?
- [ ] Did you add or update any necessary documentation?
- [ ] Does the PR affect components that are optional to install? (Ex: Numba, Pynini, Apex etc)
  - [ ] Reviewer: Does the PR have correct import guards for all optional libraries?
  
**PR Type**:
- [ ] New Feature
- [ ] Bugfix
- [ ] Documentation

If you haven't finished some of the above items you can still open "Draft" PR.


## Who can review?

Anyone in the community is free to review the PR once the checks have passed. 
[Contributor guidelines](https://github.com/NVIDIA/NeMo/blob/main/CONTRIBUTING.md) contains specific people who can review PRs to various areas.

# Additional Information
* Related to # (issue)


<!-- pylint-output-strict-mode-false -->

beep boop 🤖: 🙏 The following files have warnings. In case you are familiar with these, please try helping us to improve the code base.

---

Your code was analyzed with PyLint. The following annotations have been identified:

```
************* Module nemo.lightning.nemo_logger
nemo/lightning/nemo_logger.py:75:0: C0301: Line too long (125/119) (line-too-long)
nemo/lightning/nemo_logger.py:98:0: C0301: Line too long (120/119) (line-too-long)
nemo/lightning/nemo_logger.py:99:0: C0301: Line too long (123/119) (line-too-long)
nemo/lightning/nemo_logger.py:104:0: C0301: Line too long (127/119) (line-too-long)
nemo/lightning/nemo_logger.py:174:0: C0301: Line too long (125/119) (line-too-long)
nemo/lightning/nemo_logger.py:207:0: C0301: Line too long (128/119) (line-too-long)
nemo/lightning/nemo_logger.py:208:0: C0301: Line too long (124/119) (line-too-long)
nemo/lightning/nemo_logger.py:213:0: C0301: Line too long (124/119) (line-too-long)

-----------------------------------
Your code has been rated at 9.46/10
```

---

Thank you for improving NeMo's documentation!

<!-- pylint-output-strict-mode-false -->

beep boop 🤖: 🙏 The following files have warnings. In case you are familiar with these, please try helping us to improve the code base.

---

Your code was analyzed with PyLint. The following annotations have been identified:

```
************* Module nemo.lightning.nemo_logger
nemo/lightning/nemo_logger.py:75:0: C0301: Line too long (125/119) (line-too-long)
nemo/lightning/nemo_logger.py:98:0: C0301: Line too long (120/119) (line-too-long)
nemo/lightning/nemo_logger.py:99:0: C0301: Line too long (123/119) (line-too-long)
nemo/lightning/nemo_logger.py:104:0: C0301: Line too long (127/119) (line-too-long)
nemo/lightning/nemo_logger.py:174:0: C0301: Line too long (125/119) (line-too-long)
nemo/lightning/nemo_logger.py:207:0: C0301: Line too long (128/119) (line-too-long)
nemo/lightning/nemo_logger.py:208:0: C0301: Line too long (124/119) (line-too-long)
nemo/lightning/nemo_logger.py:213:0: C0301: Line too long (124/119) (line-too-long)

-----------------------------------
Your code has been rated at 9.46/10
```

---

Thank you for improving NeMo's documentation!

[🤖]: Hi @maanug-nv 👋,

We wanted to let you know that a [CICD pipeline](https://github.com/NVIDIA/NeMo/actions/runs/11831909480) for this PR just finished successfully

So it might be time to merge this PR or get some approvals

I'm just a bot so I'll leave it you what to do next.

//cc @pablo-garay @ko3n1g