topic Run multiple LabVIEW CLI command in the same time in Continuous Integration

Run multiple LabVIEW CLI command in the same time

Olivier-JOURDAN — Thu, 12 Mar 2020 16:40:09 GMT

Hi there,

When I try to run 2 commands in 2 separate PowerShell windows I get the following error:

Error code : -350052
Error message : LabVIEW CLI: (Hex 0xFFFAA89C) You cannot initialize the logger multiple times.

I tried to set -LogToConsole flag to FALSE, but it didn't work.

As far as "RunOperation" vis are set to reentrant execution I was pretty sure I could do that.

Any idea on what's going wrong here ?

(Note: I'm LV2019 64-bit)

Thanks in advance for your help.

Re: Run multiple LabVIEW CLI command in the same time

Nathan-M — Tue, 17 Mar 2020 19:29:57 GMT

By default, the LabVIEW application itself cannot be opened multiple times, so it seems reasonable that you shouldn't be able to do two CLI Operations simultaneously as well.

What are you trying to accomplish, maybe you can write a custom operation that does multiple things.

Edited to add the "By Default" disclaimer after being corrected. 😉

Re: Run multiple LabVIEW CLI command in the same time

RkTrey — Tue, 17 Mar 2020 19:25:20 GMT

It is possible to open multiple application instances simultaneously:

https://labviewwiki.org/wiki/Multiple_Instances_of_LabVIEW

Re: Run multiple LabVIEW CLI command in the same time

Nathan-M — Tue, 17 Mar 2020 19:28:57 GMT

@RkTrey wrote:

It is possible to open multiple application instances simultaneously:

https://labviewwiki.org/wiki/Multiple_Instances_of_LabVIEW

Thanks for correcting me! Maybe this can solve OPs problem.

Re: Run multiple LabVIEW CLI command in the same time

Olivier-JOURDAN — Wed, 18 Mar 2020 13:49:34 GMT

Thanks for your inputs.

Just a bit of context. I've been setting up a CI configuration with Gitlab, where mutiple pipelines can be triggered in the same time. The problem here is that I need to be certain that a pipeline starts only if no others are running. This need to be done to prevent different pipelines (running on the same runner/build server) to override the context (in this case a specific vipc applyed during the first job of the pipeline) of the running pipeline.

My goal is to have a custom operation checking current pipelines status and waiting for no pipeline were running to start to let the it execute. The custom operation is working but I can't run it multiple time.

Activating AllowMultipleInstances key doesn't work.

Re: Run multiple LabVIEW CLI command in the same time

Olivier-JOURDAN — Wed, 18 Mar 2020 13:51:56 GMT

@Olivier-JOURDAN a écrit :

Error code : -350052
Error message : LabVIEW CLI: (Hex 0xFFFAA89C) You cannot initialize the logger multiple times.

I'd really like to know what "logger" is referring to in this error message?

Re: Run multiple LabVIEW CLI command in the same time

James_McN — Wed, 18 Mar 2020 14:42:19 GMT

Hi Olivier,

Could this be handled by the agent configuration instead? This article mentions the relevant settings: https://stackoverflow.com/questions/51828805/configure-runner-to-run-multiple-jobs-at-the-same-time

(This is what I do under Jenkins to avoid this issue)

Cheers,

James

Re: Run multiple LabVIEW CLI command in the same time

Olivier-JOURDAN — Fri, 20 Mar 2020 13:17:31 GMT

Hi James,

Actually, these settings only affect jobs execution not pipelines (pipelines can contain multiple jobs). As far as can read here --> https://gitlab.com/gitlab-org/gitlab-foss/-/issues/41560 there's no way, so far, to configure this kind of behavior.

My plan at this point isto try G-CLI to run concurrent "wait for no pipeline running" actions in order to wait the pipeline execution. If it doesn't work, I will have to do this in shell script 😞

I'll keep you post with the result of my tests as soon as possible!

Have a good day.

Re: Run multiple LabVIEW CLI command in the same time

Olivier-JOURDAN — Fri, 27 Mar 2020 18:03:46 GMT

State of the art:

G-CLI can run 2 (or more?) command in parallel 👍

G-CLI cannot run the same command in parallel. Not surprise cause James was quite sure of that.

So I have the solution to duplicate the vi and adapt the command each time I need to run it. Good. A better way to that would have been to be able to run a vit instead of a vi, but it's not supported by G-CLI.

Anyway, I'm going to be able to do what I want with G-CLI. Thank you for this tool James 🙂

James, I opened an issue for vit execution on the G-CLI project --> https://github.com/JamesMc86/G-CLI/issues/88

Re: Run multiple LabVIEW CLI command in the same time

James_McN — Fri, 27 Mar 2020 19:54:06 GMT

Hi Olivier,

Thats a great idea for a workaround. I'll have to do some tests and see if there is an easy way to get LabVIEW to open as a new instance (or what it does in any case!)

Cheers,

James

Re: Run multiple LabVIEW CLI command in the same time

Olivier-JOURDAN — Sat, 28 Mar 2020 13:49:22 GMT

@James_McN a écrit :
Thats a great idea for a workaround.

To be fair this is Fab’s idea 😇

Re: Run multiple LabVIEW CLI command in the same time

spf — Thu, 22 Oct 2020 02:17:55 GMT

I ran into similar problem too. And my solution is to set my node's "# of executors" property to 1. So jobs will execute one by one.

Re: Run multiple LabVIEW CLI command in the same time

pawhan11 — Sat, 30 Jan 2021 15:42:01 GMT

I am digging in to the same issue now, it seems that error comes from logging LV class in labviewCLI:

Located in:

C:\Program Files (x86)\National Instruments\Shared\LabVIEW CLI\Operations\Utilities\Logger

I am trying to run multiple builds in parallel, will keep You updated if make some progress...

Re: Run multiple LabVIEW CLI command in the same time

pawhan11 — Sat, 30 Jan 2021 21:46:52 GMT

Attached working proof of concept with LabVIEW CLI, To make it work:

Disable Error message on logger instance (FGV in C:\Program Files (x86)\National Instruments\Shared\LabVIEW CLI\Operations\Utilities\Logger)
Enable multiple instances of LabVIEW
Spawn few labview processes that will run Builder.vi and pass instance parameter eg \..\..\Labview.exe \..\..\Builder.vi -- 1
Copy ExecuteBuildSpecAsync_class folder to C:\Program Files (x86)\National Instruments\Shared\LabVIEW CLI\Operations
Start it the same way from labview CLI but use ExecuteBuildSpecAsync insstead of ExecuteBuildSpec, should compile on free running builder or throw exception

It seems that LabVIEW CLi opens 1 new instance and always connects to it (just my observation so far)