test: fix flaky test in linux CI/CD environments

[jessicatarra]

Description

This PR addresses the issue of flaky test results when executing the run command test (verifies that a melos script can call another script containing steps, and ensures all commands in those steps are executed successfully) in Linux CI/CD environments, as reported in issue #670.

Closes #670

Type of Change

• [ ] ✨ feat -- New feature (non-breaking change which adds functionality)
• [x] 🛠️ fix -- Bug fix (non-breaking change which fixes an issue)
• [ ] ❌ ! -- Breaking change (fix or feature that would cause existing functionality to change)
• [ ] 🧹 refactor -- Code refactor
• [ ] ✅ ci -- Build configuration change
• [ ] 📝 docs -- Documentation
• [ ] 🗑️ chore -- Chore

[CLAassistant]

All committers have signed the CLA.

[Salakar]

@jessicatarra off topic but we'd love to sponsor you through GitHub sponsors for all the good work you're doing, are you able (and interested) in setting up your GitHub sponsors profile? 😅

[spydon]

@jessicatarra is the failing linux test related? Or is that due to other type of flakiness? :sweat_smile:

[jessicatarra]

@spydon it's actually another one but a very similar issue. I'll investigate and consider applying a similar fix to resolve it. Also, I think it may be a good idea to run the CI/CD pipeline a couple times before merging this and see if the result is constant

[Salakar]

@spydon it's actually another one but a very similar issue. I'll investigate and consider applying a similar fix to resolve it. Also, I think it may be a good idea to run the CI/CD pipeline a couple times before merging this and see if the result is constant

I've triggered another CI run

[spydon]

I've triggered another CI run

Haha, we are sitting and triggering re-runs in parallel. :smile:

[Salakar]

I've triggered another CI run

Haha, we are sitting and triggering re-runs in parallel. 😄

Haha, woops! 😅

---

Seems to be a new failure:

[spydon]

Since it seems to be a different error I suggest that we merge this one and fix the other one as a follow-up, or what do you think @jessicatarra?

[jessicatarra]

@spydon Yes, I agree! it may require a much longer investigation and the root cause may be different from the issues mentioned here

[jessicatarra]

@jessicatarra off topic but we'd love to sponsor you through GitHub sponsors for all the good work you're doing, are you able (and interested) in setting up your GitHub sponsors profile? 😅

And before I forget @Salakar, I'm in the process of enabling GitHub Sponsors on my profile. I'll let you know when that happens. Thank you so much!

[jessicatarra]

@Salakar Happy to announce that my profile already has GitHub Sponsors enabled!