-
Notifications
You must be signed in to change notification settings - Fork 2
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
Launches left IN_PROGRESS and break merge #53
Comments
It would also be good to be able to block publshing in the event of a failed merge. I don't ever want unmerged launches in my dashboards. |
Hi @owens-ben !
What do you expect, deletion of not finished launches from RP side? |
hi @AmsterGet thanks for replying. I tried increasing the interval to 30 seconds and still saw the issue again. It's intermittent so it's a little difficult to debug. As for the agent update I'm looking forward to that. I'm learning now about how to start a launch via the js client and save it for later. If you have it working on a branch I'd be happy to help test it |
Hi, I am just getting back from holiday, is there any update here? |
Fixed in version 5.1.0. |
Hi @AmsterGet, I'm facing the same issue, when i'm executing the test, if the test getting failed, so for that test -launch will continuosly shows as in-progress.. Adding the debug logs & Screenshots for the same.. [0-0] Start launch with tempId sktwi10i7lzctpv6r { |
I'm seeing an intermittent issue where merges are failing because one launch is apparently left open.
I tried adding an explicit wait in case there was a race condition and it was trying to merge before the API had closed the last launch, but that doesn't help.
Using the debugger, I'm unable to reproduce it.
The text was updated successfully, but these errors were encountered: