Xumin
Xumin
Dear contributor, We're closing this issue as there hasn't been any update to it for a long time. If the issue is still relevant in the latest version, please feel...
Dear contributor, We're closing this issue as there hasn't been any update to it for a long time. If the issue is still relevant in the latest version, please feel...
@alerque The idea is that this context keeps its order even when we set `--sort-tests` or `--shuffle` to true, and persists in its behavior when `--keep-going` is true. After all,...
And no, it's not the same to use `--no-keep-going`. I want it to skip its siblings but not other subsequent tests.
@alerque No given what I read in the doc.
@Tieske It should be a user error I guess? Or simply make it skipped due to the dependency?
> @StarlightIbuki busted has been modeled after some other frameworks, how was this case handled there? That might give some pointers as to how to solve it. > > (this...
The behavior sounds expected to me. The health check status does not update immediately, and the passive health checker cannot predict if the next request will succeed. Could you elaborate?
@mhkarimi1383 Is the upstream failing in a predictable or manipulatable manner? So that you are sure that the status is not reflecting the fact?
@mhkarimi1383 Could you share the config that you are using?