search

bitrise-steplib / steps-virtual-device-testing-for-android

MIT License
22 stars 23 forks source link

Option to rerun a failing flaky test so if it runs successfully, the build does not fail #84

Closed salmanjawed7 closed 6 months ago

salmanjawed7 commented 1 year ago

Hi Team

I would like to report an issue. I use num_flaky_test_attempts in my workflow and it does not work as expected. The use case for me is that I want my build to succeed if a flaky test passes in the second time of running. Can you please check if we can support this?

Thanks

bitrise-coresteps-bot commented 1 year ago

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

salmanjawed7 commented 1 year ago

This is still active issue and still important to me

intiocean commented 1 year ago

+1 I would expect the build to pass and the status of the step to be "success" if all the tests pass on a re-run

This is also related to this auto closed issue: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues/63

salmanjawed7 commented 1 year ago

Lets try to keep this issue active. Maybe it can be fixed 😄

bitrise-coresteps-bot commented 1 year ago

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

salmanjawed7 commented 1 year ago

Any updates?

bitrise-coresteps-bot commented 10 months ago

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

intiocean commented 10 months ago

This issue is still frustrating!

bitrise-coresteps-bot commented 7 months ago

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

bitrise-coresteps-bot commented 6 months ago

I'll close this issue as it doesn't seem to be relevant anymore. We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.