Accept string values for allow_experimental_analyzer/enable_analyzer

[azat]

All settings can be passed as strings except for this one, due to manual check in the code, which leads to "Bad get: has String, requested UInt64." before this patch.

Changelog category (leave one):

• Not for changelog (changelog entry is not required)

Fixes: azat/chdig#146

[clickhouse-gh]

Workflow [PR], commit [3351274]

Summary: ❌

job_name	test_name	status	info	comment
Stateless tests (amd_binary, old analyzer, s3 storage, DatabaseReplicated, parallel)		failure
	02443_detach_attach_partition	FAIL
Stateless tests (amd_debug, sequential)		failure
	01150_ddl_guard_rwr	FAIL

[azat]

https://s3.amazonaws.com/clickhouse-test-reports/json.html?PR=86109&sha=5f8dfe158d7f7b57b810b9f44a26b140b900de61&name_0=PR&name_1=Build%20%28amd_release%29

ERROR: AWS API Call Precondition Failed
  | awc error: An error occurred (PreconditionFailed) when calling the PutObject operation: At least one of the pre-conditions you specified did not hold

@maxknv what was the precondition? can you PTAL?

[maxknv]

https://s3.amazonaws.com/clickhouse-test-reports/json.html?PR=86109&sha=5f8dfe158d7f7b57b810b9f44a26b140b900de61&name_0=PR&name_1=Build%20%28amd_release%29

ERROR: AWS API Call Precondition Failed
  | awc error: An error occurred (PreconditionFailed) when calling the PutObject operation: At least one of the pre-conditions you specified did not hold

@maxknv what was the precondition? can you PTAL?

That's normal. Multiple jobs are updating the overall CI report concurrently.

[azat]

But it fails CI, let's add retries at least?

[azat]

CI issues are known

[maxknv]

https://s3.amazonaws.com/clickhouse-test-reports/json.html?PR=86109&sha=5f8dfe158d7f7b57b810b9f44a26b140b900de61&name_0=PR&name_1=Build%20%28amd_release%29

ERROR: AWS API Call Precondition Failed
  | awc error: An error occurred (PreconditionFailed) when calling the PutObject operation: At least one of the pre-conditions you specified did not hold

@maxknv what was the precondition? can you PTAL?

This is the reason for the job error:
Timeout exceeded [7200], send SIGTERM to [2583] and give a chance for graceful termination

I have an issue to fix the timeout handling to make this error visible #85444

[azat]

@maxknv thank you. Let's maybe increase timeout for LTO builds temporary (to i.e. 3h) ?