You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a manifest is being processed, in a case where Builder unexpectedly fails and dies, Claudie does not detect this and continues to wait.
Expected Behavior:
When a manifest is being processed, in a case where Builder unexpectedly fails and dies, the Claudie should detect it and should terminate due to error.
Steps To Reproduce:
Run all services in any environment
Run the testing-framework
Intentionally stop Builder
The testing-framework will not stop and will continue waiting until the testing framework timeout
Anything else to note:
This might be happening with Scheduler as well since both of these services are implemented as clients. We need to find an optimal solution for checking if the client services are running or not.
The text was updated successfully, but these errors were encountered:
MiroslavRepka
changed the title
Bug: Testing-framework do not know if the Builder are working properly
Bug: Testing-framework does not know if the Builder are working properly
Feb 1, 2022
MiroslavRepka
changed the title
Bug: Testing-framework does not know if the Builder are working properly
Bug: Testing-framework does not know if the Builder is working properly
Feb 1, 2022
bernardhalas
changed the title
Bug: Testing-framework does not know if the Builder is working properly
Bug: Caller does not know if the Builder is working properly
May 27, 2022
Current Behavior:
When a manifest is being processed, in a case where Builder unexpectedly fails and dies, Claudie does not detect this and continues to wait.
Expected Behavior:
When a manifest is being processed, in a case where Builder unexpectedly fails and dies, the Claudie should detect it and should terminate due to error.
Steps To Reproduce:
testing-framework
testing-framework
will not stop and will continue waiting until the testing framework timeoutAnything else to note:
This might be happening with Scheduler as well since both of these services are implemented as clients. We need to find an optimal solution for checking if the client services are running or not.
The text was updated successfully, but these errors were encountered: