Skip to content

rocprofv3-avail minor scrip fix#172

Merged
bwelton merged 4 commits into
developfrom
import/develop/ROCm_rocprofiler-sdk/gobhardw_rocprofv3-avail-minor-fix
Sep 2, 2025
Merged

rocprofv3-avail minor scrip fix#172
bwelton merged 4 commits into
developfrom
import/develop/ROCm_rocprofiler-sdk/gobhardw_rocprofv3-avail-minor-fix

Conversation

@systems-assistant

@systems-assistant systems-assistant Bot commented Aug 7, 2025

Copy link
Copy Markdown
Contributor

PR Details

Associated Jira Ticket Number/Link

What type of PR is this? (check all applicable)

  • Refactor
  • Feature
  • Bug Fix
  • Optimization
  • Documentation Update
  • Continuous Integration

Technical details

While preparing for a presentation, I discovered rocprofv3-avail doesn't handle a condition where no arguments are provided to the script. With this patch, rocprofv3 and rocprofv3-avail displays help menu if no other arguments are provided.

Added/updated tests?

  • Yes
  • No, Does not apply to this PR.

Updated CHANGELOG?

  • Yes
  • No, Does not apply to this PR.

Added/Updated documentation?

  • Yes
  • No, Does not apply to this PR.

🔁 Imported from ROCm/rocprofiler-sdk#120
🧑‍💻 Originally authored by @rocm-devops

ammallya pushed a commit that referenced this pull request Aug 7, 2025
* adding codeql.yml

* update codeql

* update codeql

* excluding external repos

* filter external

* filter external  and build

* Apply suggestions from code review

* Removed experimental test line

* Adding config

* moving codeql config out of workflows

* Disable Cdash

* update codeql

* replacing run-ci with simple cmake build

* cmake fix

* removing codeql_config

* Adding rule for python and actions

---------

Co-authored-by: Madsen, Jonathan <Jonathan.Madsen@amd.com>

[ROCm/rocprofiler-sdk commit: 215875d]
ywang103-amd pushed a commit to ywang103-amd/rocm-systems that referenced this pull request Aug 7, 2025
[ROCm/rocprofiler-systems commit: f03dce5]
systems-assistant Bot pushed a commit that referenced this pull request Aug 10, 2025
* Update vector types test

* update MakeVector to be host+device function

* Add regression testing

* Add tests for subscript operator

Change-Id: Ifac85aaa6cd6d6bd96c4239414e38f284e2a2d54

* Fix unused vars

Change-Id: I6bc2da76dbf962db5d75ea5a84bf16b66f8ba6ba

---------

Co-authored-by: Aidan Belton <abeltons@amd.com>
jayhawk-commits pushed a commit that referenced this pull request Aug 18, 2025
* Update vector types test

* update MakeVector to be host+device function

* Add regression testing

* Add tests for subscript operator

Change-Id: Ifac85aaa6cd6d6bd96c4239414e38f284e2a2d54

* Fix unused vars

Change-Id: I6bc2da76dbf962db5d75ea5a84bf16b66f8ba6ba

---------

Co-authored-by: Aidan Belton <abeltons@amd.com>

[ROCm/hip-tests commit: ef6c95f]
Comment on lines +461 to +465
if argv is None or len(argv) == 0:
avail.fatal_error("No arguments provided")

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make it display help menu

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@bgopesh bgopesh force-pushed the import/develop/ROCm_rocprofiler-sdk/gobhardw_rocprofv3-avail-minor-fix branch from 971f87e to e6230d6 Compare September 1, 2025 13:44
@bgopesh bgopesh requested a review from jrmadsen September 1, 2025 14:01
@bwelton bwelton force-pushed the import/develop/ROCm_rocprofiler-sdk/gobhardw_rocprofv3-avail-minor-fix branch from e6230d6 to 063991a Compare September 2, 2025 15:43
@ammarwa

ammarwa commented Sep 2, 2025

Copy link
Copy Markdown
Collaborator

Code Coverage Report

Code Coverage Report

Tests Only

code coverage tests.png

Samples Only

code coverage samples.png

Tests + Samples

code coverage all.png

@bwelton bwelton merged commit 45e969f into develop Sep 2, 2025
32 of 37 checks passed
@bwelton bwelton deleted the import/develop/ROCm_rocprofiler-sdk/gobhardw_rocprofv3-avail-minor-fix branch September 2, 2025 16:49
systems-assistant Bot pushed a commit to ROCm/rocprofiler-sdk that referenced this pull request Sep 2, 2025
* rocprofv3-avail scrip fix

* addressing feedback

* formatting

* rocprofv3 and rocprofv3-avail to display help when no args are provided
[rocm-systems] ROCm/rocm-systems#172 (commit 45e969f)
ammallya pushed a commit that referenced this pull request Jan 30, 2026
ammallya pushed a commit that referenced this pull request Jan 30, 2026
ammallya pushed a commit that referenced this pull request Apr 9, 2026
…172)

## Motivation

The ROCm build process sets certain build variables in the environment
from a build orchestrator. These arguments are not strictly necessary
for packaging; however, they are used to set a unified filename
structure across all ROCm packages for a given release. These are not
required though for building. `rocm-cmake` will only accept them through
the environment and does not expose a way to provide them directly as a
CMake function parameter.

This PR also sets which version of ROCm we are building against rather
than just blindly using whatever the `/opt/rocm` symlink refers to.
Should neither the ROCm Version or ROCm Path be set at configure time,
we fallback to the `/opt/rocm` symlink and try to ascertain what version
of ROCm is present.

We can then take this a step further by letting the CI control what
version of ROCm we want to target, which gets passed into the DOCKERFILE
to construct a CI image for a given platform with the target ROCm
version installed. A default ROCm version is still specified in the
DOCKERFILE's for convenience if someone is trying to build locally.

## Technical Details

Investigating other project's CMakeLists.txt and setupenv.sh in
rocm-build.

## Test Plan

Does CI pass? Does the hipFile build artifacts filename structure now
match what ROCm releases?
Does hipFile still build locally without specifying any of the new
arguments/environment variables?

## Submission Checklist

- [ ] Look over the contributing guidelines at
https://github.com/ROCm/ROCm/blob/develop/CONTRIBUTING.md#pull-requests.

AIHIPFILE-97
ammallya pushed a commit that referenced this pull request Apr 9, 2026
## Motivation

Enable the hipFile CI to run in a forked GitHub repository by default
without needing to manually patch the workflow to use a different GHCR
URL.

## Technical Details

This changes the GHCR URL that is used to pull the CI images. Originally
it was fixed to the main hipFile repository. Now, the URL will set
itself to the GHCR registry space of the repository the workflow is
being operated on.

Please note, that forked PRs targeting ROCm/hipFile will use the
ROCm/hipFile image registry. As such, even with this change, forked PRs
modifying the DOCKERFILE's are not supported.

## Test Plan

Verify there is no impact to CI in the hipFile repo.
Check that non-PR triggered workflows in the forked repo work as
expected.
CI workflows on forked repo's that run on GitHub hosted runners should
pass as expected. Workflows requiring self-hosted machines should not
expect to be started (unless a forked repo has setup an appropriate
self-hosted runner).

## Test Result

Run on personal fork:
https://github.com/riley-dixon/hipFile-test/actions/runs/21407607892?pr=16
(Note: The run did include other changes in #172)
Update CI images success:
https://github.com/riley-dixon/hipFile-test/actions/runs/21412596990
Manually triggered nightly release:
https://github.com/riley-dixon/hipFile-test/actions/runs/21414023786
Scheduled release job:
https://github.com/riley-dixon/hipFile-test/actions/runs/21414357640

## Submission Checklist

- [ ] Look over the contributing guidelines at
https://github.com/ROCm/ROCm/blob/develop/CONTRIBUTING.md#pull-requests.
ammallya pushed a commit that referenced this pull request Apr 9, 2026
…172)

## Motivation

The ROCm build process sets certain build variables in the environment
from a build orchestrator. These arguments are not strictly necessary
for packaging; however, they are used to set a unified filename
structure across all ROCm packages for a given release. These are not
required though for building. `rocm-cmake` will only accept them through
the environment and does not expose a way to provide them directly as a
CMake function parameter.

This PR also sets which version of ROCm we are building against rather
than just blindly using whatever the `/opt/rocm` symlink refers to.
Should neither the ROCm Version or ROCm Path be set at configure time,
we fallback to the `/opt/rocm` symlink and try to ascertain what version
of ROCm is present.

We can then take this a step further by letting the CI control what
version of ROCm we want to target, which gets passed into the DOCKERFILE
to construct a CI image for a given platform with the target ROCm
version installed. A default ROCm version is still specified in the
DOCKERFILE's for convenience if someone is trying to build locally.

## Technical Details

Investigating other project's CMakeLists.txt and setupenv.sh in
rocm-build.

## Test Plan

Does CI pass? Does the hipFile build artifacts filename structure now
match what ROCm releases?
Does hipFile still build locally without specifying any of the new
arguments/environment variables?

## Submission Checklist

- [ ] Look over the contributing guidelines at
https://github.com/ROCm/ROCm/blob/develop/CONTRIBUTING.md#pull-requests.

AIHIPFILE-97

[ROCm/hipFile commit: f954027]
ammallya pushed a commit that referenced this pull request Apr 9, 2026
## Motivation

Enable the hipFile CI to run in a forked GitHub repository by default
without needing to manually patch the workflow to use a different GHCR
URL.

## Technical Details

This changes the GHCR URL that is used to pull the CI images. Originally
it was fixed to the main hipFile repository. Now, the URL will set
itself to the GHCR registry space of the repository the workflow is
being operated on.

Please note, that forked PRs targeting ROCm/hipFile will use the
ROCm/hipFile image registry. As such, even with this change, forked PRs
modifying the DOCKERFILE's are not supported.

## Test Plan

Verify there is no impact to CI in the hipFile repo.
Check that non-PR triggered workflows in the forked repo work as
expected.
CI workflows on forked repo's that run on GitHub hosted runners should
pass as expected. Workflows requiring self-hosted machines should not
expect to be started (unless a forked repo has setup an appropriate
self-hosted runner).

## Test Result

Run on personal fork:
https://github.com/riley-dixon/hipFile-test/actions/runs/21407607892?pr=16
(Note: The run did include other changes in #172)
Update CI images success:
https://github.com/riley-dixon/hipFile-test/actions/runs/21412596990
Manually triggered nightly release:
https://github.com/riley-dixon/hipFile-test/actions/runs/21414023786
Scheduled release job:
https://github.com/riley-dixon/hipFile-test/actions/runs/21414357640

## Submission Checklist

- [ ] Look over the contributing guidelines at
https://github.com/ROCm/ROCm/blob/develop/CONTRIBUTING.md#pull-requests.

[ROCm/hipFile commit: 5ba2f18]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants