Skip to content
Back to pull request #14460

Support for MySQL MAX_EXECUTION_TIME as query timeout method #3107

Sign in to view logs

Support for MySQL MAX_EXECUTION_TIME as query timeout method

Support for MySQL MAX_EXECUTION_TIME as query timeout method #3107

Triggered via pull request March 23, 2024 00:44
@timvaillancourttimvaillancourt
synchronize #14460
timvaillancourt:max-execution-time-timeout
Status Failure
Total duration 4m 34s
Billable time 4m
Artifacts –

cluster_endtoend_vreplication_foreign_key_stress.yml

on: pull_request
Run endtoend tests on Cluster (vreplication_foreign_key_stress)
3m 10s
Run endtoend tests on Cluster (vreplication_foreign_key_stress)
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 1 warning
Run endtoend tests on Cluster (vreplication_foreign_key_stress): go/vt/vttablet/tabletserver/query_executor.go#L895
cannot use tsv.loadQueryTimeout() (value of type time.Duration) as int64 value in argument to strconv.FormatInt
Run endtoend tests on Cluster (vreplication_foreign_key_stress): go/vt/vttablet/tabletserver/query_executor.go#L900
undefined: optimizerHints
Run endtoend tests on Cluster (vreplication_foreign_key_stress): go/vt/vttablet/tabletserver/query_executor.go#L903
undefined: optimizerHints
Run endtoend tests on Cluster (vreplication_foreign_key_stress): go/vt/vttablet/tabletserver/query_executor.go#L929
undefined: mysql
Run endtoend tests on Cluster (vreplication_foreign_key_stress): go/vt/vttablet/tabletserver/tabletserver.go#L806
not enough return values
Run endtoend tests on Cluster (vreplication_foreign_key_stress)
Process completed with exit code 1.
Run endtoend tests on Cluster (vreplication_foreign_key_stress)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.