-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update exit code reporting #536
Conversation
Codecov Report
@@ Coverage Diff @@
## master #536 +/- ##
============================================
+ Coverage 79.29% 79.59% +0.29%
- Complexity 557 561 +4
============================================
Files 77 77
Lines 2106 2102 -4
Branches 279 276 -3
============================================
+ Hits 1670 1673 +3
+ Misses 267 265 -2
+ Partials 169 164 -5 |
Will it change the |
Hmm. FTL said the matrix status should be correct now. They pinged me yesterday. |
@gtroshin I tested flank master and I'm getting the correct exit code ( |
@bootstraponline Ok, thank you! Then I will update to 5.0.2 :) |
@bootstraponline little bit late response. For the one android project, we use v5.0.1 and it works as expected. When there is at list one Re-attempt passed it exit with 0 status code. But I just upgraded to the v6.2.2 for our iOS project - the result is it exit with 1 status code in case there are any failures in some matrices. |
It sounds like I should restore the hack of using all the XML files to calculate the exit code. Firebase's retry is defective by design. I'll work on this soon. |
This reverts commit bd6e444.
I reverted the commit here: |
I updated #552 The fix has been released in flank v6.2.3 |
No description provided.