Continuous Integration

Highlighted

VI Analyzer Tests Failing in CI

Hi everyone,

 

Recently I've started using CI with a LabVIEW Project.

 

One of the steps is running a VI Analyzer Test Suite. Apparently, the tests pass in my machine (or two of my machines), but some of them fail when running on CI.

 

Does anyone have a clue what is going on?

 

I didn't know if I should post here or in the VI Analyzer Enthusiasts Group, but here I felt that it would be the best place.

 

I am using Gitlab CI and Docker with LabVIEW 20.0f1.

 

Here is an example of the failing tests.

 

code quality.PNG

 

For now, I consider these tests as low ranking, then they do not interfere with my pipeline. But it is a workaround and not a solution.

 

Thanks.

Felipe Pinheiro Silva


Follow my blog for LV content!


0 Kudos
Message 1 of 4
(101 Views)
3 REPLIES 3
Highlighted

Re: VI Analyzer Tests Failing in CI

Fonts. 

 

You probably have different fonts on your build/test machine than your development machine.

 

Try setting the default font in the LV ini on both sides to the same font (and make sure that font is on both machines).

Sam Taggart
CLA, CPI, CTD, LabVIEW Champion
DQMH Trusted Advisor
automatedenver.com
GCentral
0 Kudos
Message 2 of 4
(89 Views)
Highlighted

Re: VI Analyzer Tests Failing in CI

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019UgESAU&l=en-US

 

Here is how you can change on your dev machine using the dialog boxes. See what keys that adds to your ini file and then copy them over to your test/build machine. Again they both need to have the same font installed.

Sam Taggart
CLA, CPI, CTD, LabVIEW Champion
DQMH Trusted Advisor
automatedenver.com
GCentral
Message 3 of 4
(86 Views)
Highlighted

Re: VI Analyzer Tests Failing in CI


@Taggart  escreveu:

Fonts. 

 

You probably have different fonts on your build/test machine than your development machine.

 

Try setting the default font in the LV ini on both sides to the same font (and make sure that font is on both machines).


That is probably the right answer, but I couldn't confirm this yet.

 

It turns out that I used a base image from windows docker that had no fonts installed in it, which is probably causing this.

 

I my installations, I always use default font in both ini files, so it is not a configuration issue.

 

I found out that the base font for LabVIEW is listed here (Segoi UI) https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P8q6SAC&l

 

But after installing this font in the image, it didn't solve, then I tried to install all the fonts in my PC, and again, not a change.

 

I will keep digging. 

 

Felipe Pinheiro Silva


Follow my blog for LV content!


0 Kudos
Message 4 of 4
(75 Views)
Reply
This is an open group. Sign in and click the "Join Group" button to become a group member and start posting.