Several Polyspace Code Prover Licenses consumed for a single analysis?

Hello, support team

I have few questions related on how the Polyspace Code Prover is consuming a license per analysis.

This is the scenario:

We using docker with azure pipelines to run polyspace analysis for different projects.

Once a pipeline is started, docker container is initialized with the polyspace image and connection to license server.

When analysis starts, I can see:

Checking license ...

License is OK

Which I translate as "Execution has taken a license", problem presents when in license server, we can see several times that the same container ID has taken two licenses at the same time(without releasing the first one taken).

That makes 1 single execution to consume 2 licenses, and our following executions for other projects to fail with:

Checking license ...

Error: License checkout failed.

| License Manager Error -87

So.. questions are as follow:

1. By normal sw design, can one single analysis consume more than one single license?
2. Is there any way we can force the analysis to only take one single license until analysis is finished?
3. -max-processes=4 (or any number >1) could cause different processes take more than 1 license ?

Of course any recomedantion or idea what could be happening is highly appreciated as well.

PD. Different projects can use different PS CP versions like R2024b.4, R2023a.4, R2022a.4 in case that matters, some projects use the same.

Thank you.

Answer 1

[Jesus]

After some testing, it seems that Polyspace R2022a.4 is causing the issue, whenever a project start analyzing under this version, I can see that after 2 hrs a second license is taken, no idea why.

For now I have updated the projects to use R2024 version and I have not seen the executions taking more than one license.