Closed nvervelle closed 8 months ago
In fact, I checked the code, and I think I found the problem :
on()
calls Executables.toChainBuilder()
(without s
)ChainBuilder
(which is an Executable
) and not a List<ChainBuilder>
on(@NonNull List<ChainBuilder> choices)
, it calls itself on(@NonNull Executable executable, @NonNull Executable... executables)
resulting in a infinite loop and StackOverflowError
The problem seems to come from this commit by @slandelle . I think the problem is present on other classes (at least on UniformRandomSwitch
)
Thanks for reporting.
The same issue happens with UniformRandomSwitch
.
Gatling 3.10.1 is up.
Thanks @slandelle
I can now start the simulation with gatling 3.10.1.
It seems I have another problem though : I replaced calls CoreDsl.exitBlockOnFail(...)
by CoreDsl.exitBlockOnFail().on(...)
to take into account the breaking change in gatling DSL, but now errors fail to exit the simulation, the simulation seems to be stucked instead of finishing
I see logs stating that a request has failed, but nothing more happens to the simulation :
11:37:09.847 [DEBUG] i.g.h.e.r.DefaultStatsProcessor - Request 'applicant-submit-challenge' failed for user 2: status.find.is(200), but actually found 415
Any idea what can be causing such problem ?
@nvervelle Could you please open a distinct ticket?
Hello,
I just tried to upgrade to gatling 3.10.0 from gatling 3.9.5.6, and I get
StackOverflowError
when running gatling (it seems to fail when building the simulation). I just have this log, I can try to make a reproducible example but not sure I will success.