-
Notifications
You must be signed in to change notification settings - Fork 50
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
Trainer fails when Scan fails #13
Comments
Are you sure this wasn't always the case? The only change that was recently applied was 002f5d6 |
Actually no, I'm not confident that this is recent. Looking through my Fastfile history I had broken trainer out into another lane previously that was actually being left before reaching it, so it's entirely possible the issue has been around for longer. This is a bug in trianer though, right? |
@KrauseFx I just wanted to bring this back up since it seems like a bug. I have the same problem with it failing and have to catch the exception in order for everything to work. I run the
My workaround in the meantime is to just do:
And everything actually works fine. |
We are also experiencing the same issue. It seems that even when
We are running |
We have the same issue with 2.108.0 and fail_build set to false
|
Lately, I'm only able to have
trainer
run successfully whenscan
succeeds and passes all tests. If even one test fails, I get the following error:Followed by the sad explosion icon next to
trainer
and thefastlane finished with errors
message.I wanted to look into this so I saw there was a commit 7 days ago, the only instance of the message I could find the following, from the trainer_action.rb file, lines 11-13:
I can provide any working examples you might need to reproduce this. I'm very stumped after an hour or so of searching for the solution. If my tests pass, trainer runs. If any tests fail, trainer kills the lane.
The text was updated successfully, but these errors were encountered: