[Q&A] Build failing during Test::MockModule installation

[dawsunnn]

Documentation & bug reporting acknowledgment

Yes, I read it

Describe your problem

Context:
I am facing an issue while building GLPI Agent on Windows. The build fails specifically during the installation of the Perl module Test::MockModule. The issue occurs both in the GitHub Actions workflow and when I replicate the steps locally.

Environment:

Operating System: Windows 10 22H2 (Build 19045.5371)
Perl Version: StrawberryPerl 5.32.1001 (x64)
Build Method: Replicated the GitHub Actions steps exactly without any modifications or additional parameters.
Relevant Logs:

To reproduce:
Clone the repository from GitHub.
Follow the documented steps for building GLPI Agent for Windows.
Run the script.
Observe the failure during the Test::MockModule installation step.
Actions Taken:

I verified that the steps I follow locally are identical to the GitHub Actions workflow.
I attempted manual installation of Test::MockModule, but the issue persists.
I have tried forcing installation (--force) and disabling tests, but it did not resolve the problem.

Expectation:
I would like assistance to understand:

Why Test::MockModule fails to install, even though its dependencies are being fetched correctly.
If there are any additional configuration steps or dependencies required for building on Windows.
Any recommendations to resolve this issue and complete the build successfully.
Thank you in advance for your help!

[g-bougard]

Hi @dawsunnn

the dates are funny in your log: 2025/00/23, this looks like a month output issue. I don't think anyway this is a problem.

Can you provide the link to the last action run ?

You should also be able to get the debug archive artifact and check the build log for that module.

Maybe this module had an update and we didn't see the problem for now on glpi-agent as the built perl is cached.

[dawsunnn]

Hi @g-bougard,

Thank you once again for your response. I have removed the GitHub Action mention from the "Steps to Reproduce" section.

I have been following both the GitHub Action YML file and the project Wiki instructions.

I was able to reproduce this issue on multiple instances of Windows 10 and 11. I noticed that the GitHub Action pipeline uses Windows Server 2022 for building. Could it be that this specific environment is required to successfully build the agent?

Here are the exact commands I use to attempt building the agent from source:
Build.ps1.txt

Thank you for the additional information; I’ll review those and see what I can find.

[g-bougard]

Well, I forgot I've written this doc 3 years ago. Thank you for the remembering.

I took a quick look at your PS script. It seems you didn't miss anything there. Indeed, there's one point... this is a PowerShell script ^^
I know sometime we expect the same comportment of script written in PS and in CMD/BAT but sometime this doesn't happen as expected. Also, you should know, Perl::Dist::Strawberry module will run CMD as subshell. I'm really not sure, but this may be an issue. And maybe this is related to the PATH handling. I know PATH is not handled the same way under PS and CMD.

Can you try to run all the step under a CMD environment to see if this is better ? Last time I tried to build myself on a windows vm few month ago, I did under a CMD environment.

[dawsunnn]

Hi @g-bougard,

As requested, I conducted new tests using CMD and Windows Server 2022. I encountered the same error at the same step.
build.bat.txt

Here is the new CMD SCRIPT script and the log file from the Test::MockModule installation: mod_install_Test_MockModule_FAIL_1737960358.log.txt

And as a reminder, here is the error encountered during the execution of the Perl script:

I am currently running tests with Cygwin and will keep you updated on the results.

[dawsunnn]

Using Cygwin resulted in the same error. All the prerequisites seem to be present on the machine I am using to compile the agent, yet I cannot identify the root cause of the issue.

[g-bougard]

Hi @dawsunnn

this time you have the error:

gmake: *** No rule to make target 'C:\Strawberry-perl-for-GLPI-Agent\perl\lib\CORE\libperl536.a'>> storing results via Storable to 'C:\Strawberry-perl-for-GLPI-Agent_build\debug\mod_install_Test_MockModule_1737960358.list.nstore.txt'

Here you can see libperl536.a is referencing a perl 5.36 installation, where the previous was on libperl538.a, so for perl v5.38.

This means to me you're not building the same project than before.

What kind of changes are you doing on the project you're trying to build ? Do you change something on the building process it self ?

[g-bougard]

Hi @dawsunnn

just wanted to tell you I just managed to run the build on a windows 11 environment without an issue:

• The windows was a WinDevEval from Microsoft running into a VirtualBox VM.
• I only had to install Perl Strawberry 5.40, Git and Wix Toolset 3.14 using winget tool.
• Then I just followed all the steps one by one from the GH Actions workflow (skipping GH Action cache related steps)
• As this time I tested from a PS console, I had to change the way to update PATH. I had to add the path to git.exe in the PATH as required by installation of development Perl::Dist::Strawberry module.

To be honest, I had an issue the first time on the Socket6 package. But looking at the "FAIL" related report in the debug archive, I found it was just a temporary issue while downloading the package. I restarted the build and I got the MSI generated.

[g-bougard]

Looking back to the wiki, I noticed the wiki tells to run cpanm --notest --verbose Perl::Dist::Strawberry to install Perl::Dist::Strawberry module. This is indeed wrong as actually I use the development version running:

glpi-agent/.github/workflows/glpi-agent-packaging.yml

Line 254 in c3fd510

cpanm --notest --verbose https://github.com/StrawberryPerl/Perl-Dist-Strawberry.git

This can be the reason why you have a failure.