Trigger build with CRON, READCONTRACT, & KVSTORE standard capability binaries

[justinkaseman]

Not for review. Triggering a CI/CD build.

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[github-actions]

Below is an analysis created by an LLM. Be mindful of hallucinations and verify accuracy.

WF: CI Core#7a40750

Error 1: Test Failures and Exit Code 1

Source of Error:

Core Tests (go_core_tests)	Run tests	2024-10-08T00:03:22.4272984Z Encountered test failures.
Core Tests (go_core_tests)	Run tests	2024-10-08T00:03:22.4278764Z go_core_tests exiting with code 1
Core Tests (go_core_tests)	Run tests	2024-10-08T00:03:22.4293652Z ##[error]Process completed with exit code 1.

Why:
The error indicates that the test suite encountered failures during execution, which caused the process to exit with a non-zero status (exit code 1). This typically happens when one or more tests fail to pass their assertions or meet expected conditions.

Suggested fix:
Review the test cases and the assertions that failed. Modify the tests or the underlying code to ensure that all conditions are met and all assertions pass. Running the tests locally before pushing changes can help catch such errors early.

Error 2: Mock Method Call Exceeded Expected Times

Source of Error:

Core Tests (go_core_tests)	Print Filtered Test Results	2024-10-08T00:03:22.7364435Z assert: mock: The method has been called over 1 times.
Core Tests (go_core_tests)	Print Filtered Test Results	2024-10-08T00:03:22.7365912Z 	Either do one more Mock.On("HeadByNumber").Return(...), or remove extra call.
Core Tests (go_core_tests)	Print Filtered Test Results	2024-10-08T00:03:22.7367089Z 	This call was unexpected:
Core Tests (go_core_tests)	Print Filtered Test Results	2024-10-08T00:03:22.7368027Z 		HeadByNumber(*context.timerCtx,*big.Int)

Why:
This error is thrown by the mocking framework used in the tests. It indicates that a mocked method (HeadByNumber) was called more times than it was set up to expect. This can occur if the test logic has changed but the mock setup was not updated accordingly.

Suggested fix:
Update the mock configuration to align with the current test logic. This could involve adjusting the number of expected calls to the method or modifying the test to reduce the number of calls. Ensure that the mock setups accurately reflect the intended use of the mocked methods.

[justinkaseman]

Built