Skip to content
Pull Request Labeler

Fix different json representation in scheduling mechanism #16504

Sign in to view logs

Fix different json representation in scheduling mechanism

Fix different json representation in scheduling mechanism #16504

Triggered via pull request February 7, 2025 13:20
@mgoworkomgoworko
synchronize #7519
Status Success
Total duration 12s
Artifacts –

labeler.yml

on: pull_request_target
triage
3s
triage
Fit to window
Zoom out
Zoom in

Annotations

1 error
pl.touk.nussknacker.engine.flink.minicluster.scenariotesting.FlinkMiniClusterScenarioTestRunnerSpec ► A scenario run on Flink engine when IO monad interpreter is used should switch value should be equal to variable value: engine/flink/tests/src/test/scala/pl/touk/nussknacker/engine/flink/minicluster/scenariotesting/FlinkMiniClusterScenarioTestRunnerSpec.scala#L644
Failed test found in: engine/flink/tests/target/test-reports/TEST-pl.touk.nussknacker.engine.flink.minicluster.scenariotesting.FlinkMiniClusterScenarioTestRunnerSpec.xml Error: org.scalatest.concurrent.ScalaFutures$$anon$1$$anon$2: A timeout occurred waiting for a future to complete. Waited 5 seconds.