On 02/06/25 16:56, Rahila Syed wrote:
>> I'm also attaching a second patch that has a TAP test case that
>> reproduce this issue, it has some hacks to move dynamic library files
>> around to exercice the problem so I'm not sure if it could be good to
>> also include these tests on the final patch.
>>
>
> The TAP test is useful in testing various paths of extension files.
> It will be cleaner if the dummy_index_am.so is deleted at the end of the
> tests from the $libdir.
>
I think that the problem is that some other tests may use this
extension, so deleting at the end may cause other tests that use it to
fail depending on the other that is executed? I actually delete the .so
in the middle of the test but I copy it back to $libdir at the end to
avoid this possible side effect.
> Currently, the tests seem to be failing as follows for windows:
>
> [19:07:13.107] # Failed test 'create extension from custom extension
> control path'[19:07:13.107] # at
> C:/cirrus/src/test/modules/test_extensions/t/002_strip_modulepathname.pl
> line 102.[19:07:13.107] # got: '2'[19:07:13.107] #
> expected: '0'[19:07:13.107] # Looks like you failed 1 test of
> 7.[19:07:13.107] [19:07:13.107] (test program exited with status code
> 1)
>
> Details here: Windows - Server 2019, VS 2019 - Meson & ninja - Cirrus CI
> <https://cirrus-ci.com/task/5241991606304768>
>
Thanks, I'll take a look
--
Matheus Alcantara
