Re^2: Unable to release modulino to CPAN

The second [problem] is how to test any solution on my machine.

If I understand you correctly, the thing you want to test is "if there is another perl earlier on the path than the one I am being built with, it has not been called". So mimic that scenario:

% cat t/perl
#!/bin/bash
echo "Wrong perl"
exit 1
% perl -E 'say "ok"'
ok
% PATH=`pwd`/t:$PATH \
    perl -E 'say "ok"'
Wrong perl
% PATH=`pwd`/t:$PATH \
    /usr/bin/perl -E 'say "ok"'
ok
%
[download]

You could also have the wrong-perl script touch a file, in case something invokes it and ignores both its output and its exit code.

Comment on Re^2: Unable to release modulino to CPAN - still struggling Download Code

Replies are listed 'Best First'.
Re^3: Unable to release modulino to CPAN - still struggling by davies (Monsignor) on Oct 31, 2022 at 20:09 UTC
I may not have explained my problem adequately. On my machine, everything works. It's on the testers' machines that I have a problem and I don't know if there is a simple way to mimic what they are doing that causes the test failures. My reading indicates that this could be done my setting up an entire virtual machine to act as a pre-release test environment, but even then I would have to set it up in such a way that it would generate the errors, and not all test runs return errors. It also seems like a very large yak to shave unless there is no option. I get it now. Apologies for my earlier stupidity - it's amazing what a night's sleep can do. I was misunderstanding the bash (I default to Windows) and getting a totally false impression. I have implemented a Windows version of your code & I think it does what I need. Regards, John Davies	[reply]
Re^4: Unable to release modulino to CPAN - still struggling by hv (Prior) on Oct 31, 2022 at 20:38 UTC
On my machine, everything works. It's on the testers' machines that I have a problem and I don't know if there is a simple way to mimic what they are doing that causes the test failures. My suggestion was aimed precisely at letting you mimic a situation similar to that on the testers' machines, at least for the scenario described in your excerpt. Did you try running the testsuite with the setup I suggested? You should at least be able to show that it would have highlighted the one problem you already found and fixed. If there are other failure modes you want to test for, you will first need to identify those.	[reply]