Skip to content

[Enhancement] fix connector mem scan limit adjustment when no chunk source #113600

[Enhancement] fix connector mem scan limit adjustment when no chunk source

[Enhancement] fix connector mem scan limit adjustment when no chunk source #113600

GitHub Actions / FE UT Report failed Nov 22, 2024 in 0s

10448 tests run, 10392 passed, 54 skipped, 2 failed.

Annotations

Check failure on line 1251 in fe/fe-core/src/test/java/com/starrocks/analysis/RefreshMaterializedViewTest.java

See this annotation in the file changed.

@github-actions github-actions / FE UT Report

RefreshMaterializedViewTest.testTruncateTableInDiffDb

expected:<1> but was:<0>
Raw output
java.lang.AssertionError: expected:<1> but was:<0>
	at com.starrocks.analysis.RefreshMaterializedViewTest.testTruncateTableInDiffDb(RefreshMaterializedViewTest.java:1251)

Check failure on line 1 in fe/fe-core/src/test/java/com/starrocks/backup/RestoreJobTest.java

See this annotation in the file changed.

@github-actions github-actions / FE UT Report

RestoreJobTest.testSignature

Missing 1 invocation to:
com.starrocks.system.ComputeNode#isAlive()
   on mock instance: com.starrocks.system.Backend@2d5831da
Raw output
Missing 1 invocation to:
com.starrocks.system.ComputeNode#isAlive()
   on mock instance: com.starrocks.system.Backend@2d5831da
Caused by: Missing invocations
	at com.starrocks.system.ComputeNode.isAlive(ComputeNode.java)
	at com.starrocks.task.AgentBatchTask.run(AgentBatchTask.java:181)
	at java.base/java.lang.Thread.run(Thread.java:829)