Issues with broken code detection after updating ABCD tool to later version LabVIEW

[kchang408]

This was asked on another section but they cannot seem to solve it since it's more related to continues integration (https://forums.ni.com/t5/LabVIEW/Continuous-integration-w-gitLab-not-working-after-updating/m-p/4281...😞 

We have a CI/CD git runner setup working before.  It used to run on Labview 2019 and I have mass compiled it into Labview 2022 and now the broken code report looks odd, at the First Broken Commit column, it says that "This VI has the 'Separate compiled code from source file' setting disabled" instead of showing actually commit#.

This is what is like now after running the pipeline:

This is what it used to do on another project:

[அனிச்பிரபு_தி.]

Hi all,

       This is an internal tool that, I will be supporting the team.

Regards

Anish T.

[kchang408]

The vi broken code analyzer is working now but I am getting items that are supposedly warning items (not using high resolution polling wait vi instead of using wait (ms) vi) rather than actually broken vis in the broken code list now.  Are there any way to ignore these type of warnings?

[அனிச்பிரபு_தி.]

The VI Analyser is uses configuration (*.vian) file, looks like that file is modified. Open the file in VI Analyser and uncheck all items except for broken VI Test.

[kchang408]

Hi Anish, where is this VI analyzer you are talking about.  I was trying to find it but only could find a VI analyzer launcher and after running it I was able to see analyzer GUI.  Is that what you are talking about?  But I cannot find the option to open the .vlan file. 

[அனிச்பிரபு_தி.]

Yes, that is VI analyzer app. The configuration is openable from another app menu. All the test items must be deselected, and only Broken Vi test should be selected.

[kchang408]

My issue is that the config file only has Broken Code Vi selected, but in reality it's checking something else as well.