Strange results in Ubuntu

[yukiech]

The tester seems to "work" on Ubuntu with a "so:" rule with "-nostartfiles" but some result are strange.

I even tested to git clone other people libft and had about the same results. Others testers compile thoses just fine and results are OK.

Anyone had this kind of issues ?

EDIT: A friend on an iMac tested my libft and thoses functions where OK.

[alexrowe99]

Have you got it working on Ubuntu?

[yukiech]

Never managed to make thoses 3 work. (isalnum, toupper and tolower) Looks like all the others are working tho.

(confirmed by sending my libft to someone on Mac who ran it for me, everything came back as OK, even isalnum/toupper/tolower)

[DCAndrei]

Hello, i am new to this, but i have the same issue. On a mac with m1, ft_strrchr(test 7) and ft_memmove(test 9) give a crash, and ft_calloc a timeout on the first test, on Windows10 with ubutu wls, they are fine, but the ft_isalnum, ft_toupper and ft_tolower fail all. This is my experince, otherwise super tests. Thank you!

[yukiech]

For ft_isalnum, ft_toupper and ft_tolower, the tester gives false errors. What i mean is: your function should pass the moulinette even if it says "Failed" on WSL2. Overall, i can add that no libft tester can be 100% trusted. The moulinette does some additionnal tests. (Often, split, substr or strchr is OK on some testers but fails against the Moulinette)

[github-actions[bot]]

Hello! Thanks for contributing to the libft unit test.

Note that this repository is not maintained by the owner anymore, instead there is a bot that will automatically merge any reviewed pull requests. If you feel like it, here are some links that can help you submiting a change in the code base::

• Create a pull request from a fork
• List of people that can review your pull request
• Automatically closing an issue with a pull request