topic OneAPI 2024.0.0 modulefiles/vtune/{2024.0,latest} bug in Analyzers

OneAPI 2024.0.0 modulefiles/vtune/{2024.0,latest} bug

CFR — Sat, 02 Dec 2023 19:25:21 GMT

I think:

set scriptpath ""
set scriptpath "[file dirname [file normalize "/___"]]"

is supposed to be:

set scriptpath "${ModulesCurrentModulefile}"
set scriptpath "[file dirname [file normalize "$scriptpath/___"]]"

Re:OneAPI 2024.0.0 modulefiles/vtune/{2024.0,latest} bug

SreedeviK_Intel — Tue, 05 Dec 2023 06:26:06 GMT

Hi,

Thank you for posting in Intel communities.

We were able to reproduce the issue from our end on linux machine with latest version of VTune (2024.0).

We are checking on it internally and will get back to you with an update shortly.

Could you please share your OS and hardware details?

Regards,

Sreedevi

Re: Re:OneAPI 2024.0.0 modulefiles/vtune/{2024.0,latest} bug

CFR — Tue, 05 Dec 2023 15:35:33 GMT

The install was done on a CentOS 7.9, Xeon E5-2637 machine.

Re:OneAPI 2024.0.0 modulefiles/vtune/{2024.0,latest} bug

SreedeviK_Intel — Mon, 11 Dec 2023 05:56:09 GMT

Hi,

Thanks for reporting this issue.

We were able to reproduce it and we have informed the development team about it.

Regards,

Sreedevi

Re:OneAPI 2024.0.0 modulefiles/vtune/{2024.0,latest} bug

Jeffrey_R_Intel1 — Fri, 22 Dec 2023 15:15:39 GMT

Hello,

This bug is documented in the Intel(R) VTune(TM) Profiler release notes: https://www.intel.com/content/www/us/en/developer/articles/release-notes/vtune-profiler-release-notes.html#inpage-nav-4

and a workaround patch is available at https://www.intel.com/content/dam/developer/articles/release-notes/intel-oneapi-toolkit-release-notes/vtune-2024-fix.tcl

Re: Re:OneAPI 2024.0.0 modulefiles/vtune/{2024.0,latest} bug

nmnobre — Wed, 13 Mar 2024 11:34:49 GMT

Hi, both the current and patched modules have unbalanced curly braces in:

set modulefilever "[file tail "$scriptpath}"]"

Cheers,

Nuno

Re: Re:OneAPI 2024.0.0 modulefiles/vtune/{2024.0,latest} bug

Jeffrey_R_Intel1 — Mon, 22 Jul 2024 17:13:42 GMT

Thank you for reporting this. The Intel(R) VTune(TM) Profiler module file has been fixed in the 2024.2 release.

Re: Re:OneAPI 2024.0.0 modulefiles/vtune/{2024.0,latest} bug

CFR — Thu, 25 Jul 2024 18:19:00 GMT

Sadly it looks like 2024.02 is broke in a different way...

set script_path "[file normalize [exec readlink -f ${ModulesCurrentModulefile}]]"

...results is something like...

<installdir>/vtune/2024.2/etc/modulefiles/vtune/2024.2

and then...

set PRODUCT_INSTALL_DIR "[file dirname [file dirname $script_path]]"

... turns into ...

<installdir>/vtune/2024.2/etc/modulefiles

What's missing is something that takes off two more level of directories...

set PRODUCT_INSTALL_DIR "[file dirname [file dirname $PRODUCT_INSTALL_DIR]]"

... to get a PRODUCT_INSTALL_DIR to point at the right level...

<installdir>/vtune/2024.2

(At least that's what I had to do....)

Re: OneAPI 2024.0.0 modulefiles/vtune/{2024.0,latest} bug

yuzhang3_intel — Thu, 24 Oct 2024 03:03:34 GMT

This is one known issue, which will be fixed in a future release. Here is a workaround:

The target file is something like /opt/intel/oneapi/vtune/latest/etc/modulefiles/vtune/2024XX

set write permissions on the target file and edit the file

Old

set PRODUCT_INSTALL_DIR "[file dirname [file dirname $script_path]]"

New

set PRODUCT_INSTALL_DIR "[file dirname [file dirname [file dirname [file dirname $script_path]]]]"

Open a new shell and load the module again