Skip to content

Fix for launch_latency. - #2564

Merged
Lynd98 merged 3 commits into
aomp-devfrom
launchfix1
Sep 22, 2026
Merged

Lynd98 merged 3 commits into
aomp-devfrom
launchfix1

Conversation

@Lynd98

@Lynd98 Lynd98 commented Sep 18, 2026

Copy link
Copy Markdown
Collaborator

Motivation

In CI, the launch_latency report has error and warning messages represented as timings; needed to delete these messages.

Technical Details

Changed the launch_latency Makefile to send error and warning messages to /dev/null.

Test Plan

Reran launch_latency, checked for error and warning mesages.

Test Result

None

@mhalk mhalk left a comment •

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Does this need to be unblocked immediately?

IMHO we should keep that info for debugging purposes.
Ideas that come to mind:

  • redirect into another "error" log file (need to make sure this cannot become stale)
  • teach the CI extraction to ignore these warnings

@jplehr

jplehr commented Sep 21, 2026

Copy link
Copy Markdown
Collaborator

Does this need to be unblocked immediately?

IMHO we should keep that info for debugging purposes. Ideas that come to mind:

  • redirect into another "error" log file (need to make sure this cannot become stale)
  • teach the CI extraction to ignore these warnings

IMHO we should pipe it to another file. If we make the extract script to ignore the logs, we're just waiting for rocprofiler to change nad our tests to break again.

If we hit an error return code, the test should fail and output the log. Otherwise just overwrite it the next run / add it to make clean target.

@Lynd98 Lynd98 left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Changed /dev/null to ./rocprofv3.log. Because it is a *.log file, it is removed by "make clean".

@Lynd98
Lynd98 requested a review from mhalk September 21, 2026 15:39

@mhalk mhalk left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Looks good, thanks Lynd!
Please consider adding / trying my suggestion so we get output in case of an error.
Once that's taken care of, I think this is good to go :)

CC = $(OMP_BIN) $(VERBOSE)
RUNENV = ulimit -s unlimited;
RUNCMD = $(AOMPHIP)/bin/rocprofv3 --output-format csv --kernel-trace --stats -- ./$(TESTNAME) && python3 printLatency.py
RUNCMD = $(AOMPHIP)/bin/rocprofv3 --output-format csv --kernel-trace --stats -- ./$(TESTNAME) 2> ./rocprofv3.log && python3 printLatency.py

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Idea to accommodate JP's suggestion (please check): add sth. like || cat ./rocprofv3.log
Unsure if we want sth. "more sophisticated" like ReturnCode printing.

Style: I'd also try if we can improve readability by moving this into a new line like this:
(really just an idea, I did not test this)

Suggested change
RUNCMD = $(AOMPHIP)/bin/rocprofv3 --output-format csv --kernel-trace --stats -- ./$(TESTNAME) 2> ./rocprofv3.log && python3 printLatency.py
RUNCMD = $(AOMPHIP)/bin/rocprofv3 --output-format csv --kernel-trace --stats -- ./$(TESTNAME) 2> ./rocprofv3.log
RUNCMD += && python3 printLatency.py || cat ./rocprofv3.log

@mhalk mhalk left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

LGTM! :)

@Lynd98
Lynd98 requested a review from mhalk September 22, 2026 18:22
@Lynd98
Lynd98 merged commit ae6bb71 into aomp-dev Sep 22, 2026
1 check passed
@Lynd98
Lynd98 deleted the launchfix1 branch September 22, 2026 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants