`New_ATS` fails to find `LabVIEWCLI.exe` for 64-bit LabVIEW

[bkeryan]

New_ATS tries to run a 64-bit version of LabVIEWCLI.exe and fails because it is not installed.

With LabVIEW 2019 (64-bit) and LabVIEW 2023 Q4 (64-bit) installed, my test machine only has the 32-bit version of LabVIEWCLI.exe.

PS X:\grpc-labview\tests\New_ATS> dir 'C:\Program Files (x86)\National Instruments\Shared\LabVIEW CLI'


    Directory: C:\Program Files (x86)\National Instruments\Shared\LabVIEW CLI


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d-----         7/22/2025   2:57 PM                Operations
-a----          7/6/2023   4:51 PM          92328 LabVIEWCLI.exe
-a----         7/25/2025   5:42 PM            402 LabVIEWCLI.ini
-a----          7/6/2023   4:51 PM         845496 nilvcli.dll
-a----          7/6/2023   4:50 PM          56504 nilvclipm.dll


PS X:\grpc-labview\tests\New_ATS> dir 'C:\Program Files\National Instruments\Shared\LabVIEW CLI'
dir : Cannot find path 'C:\Program Files\National Instruments\Shared\LabVIEW CLI' because it does not exist.
At line:1 char:1
+ dir 'C:\Program Files\National Instruments\Shared\LabVIEW CLI'
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (C:\Program File...red\LabVIEW CLI:String) [Get-ChildItem], ItemNotFound
   Exception
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand

Steps to reproduce

1. Set labview_bitness to 64 in tests/New_ATS/pylib/testlist.json:

PS C:\dev\grpc-labview\build> git diff
diff --git a/tests/New_ATS/pylib/testlist.json b/tests/New_ATS/pylib/testlist.json
index 87208fd..33a8c38 100644
--- a/tests/New_ATS/pylib/testlist.json
+++ b/tests/New_ATS/pylib/testlist.json
@@ -15,7 +15,7 @@
     ],
     "gen_type": "0",
     "labview_version": "2019",
-    "labview_bitness": "32",
+    "labview_bitness": "64",
     "clean_gen": true
   }
 ]

2. Cd to tests/New_ATS and run python pylib/testlist.json

Expected result

It runs the tests

Actual result

PS X:\grpc-labview\tests\New_ATS> python pylib\run_tests.py

Running test for "helloworld"...
Traceback (most recent call last):
  File "X:\grpc-labview\tests\New_ATS\pylib\run_tests.py", line 194, in <module>
    main()
  File "X:\grpc-labview\tests\New_ATS\pylib\run_tests.py", line 189, in main
    run_test(test_config)
  File "X:\grpc-labview\tests\New_ATS\pylib\run_tests.py", line 61, in run_test
    check_for_pre_requisites(test_config)
  File "X:\grpc-labview\tests\New_ATS\pylib\run_tests.py", line 30, in check_for_pre_requisites
    raise Exception(f'LabVIEW CLI is not installed at {test_config["lvcli_path"]}')
Exception: LabVIEW CLI is not installed at C:\Program Files\National Instruments\Shared\LabVIEW CLI\LabVIEWCLI.exe

AB#3218392

[jasonmreding]

@bkeryan IIRC there is not a 64 bit version of the LabVIEW CLI, and it only gets installed under the 32 bit directory hierarchy on Windows. However, I don't believe the automated testing scripts account for this. I'm pretty sure I ran into this before when trying to run tests locally against a version of LV that isn't 32 bit LV 2019. I wouldn't be surprised if this is the only issue that is not tolerant of different LV versions and bitness.

[bkeryan]

@jasonmreding @yash-ni The AutoTests version of run_tests.py calls subprocess.Popen(["LabVIEWCLI", ...) without trying to find the absolute path. It looks like installing LabVIEW adds C:\Program Files (x86)\National Instruments\Shared\LabVIEW CLI to the system PATH.

I think setting test_config["lvcli_path"] to "LabVIEWCLI.exe" and removing the existence check would probably work.