CQ failure: MySQL Cannot execute statement |
|||
Issue descriptionLots of failures with: DatabaseError: (1665, 'Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED.') See an example log here: https://logs.chromium.org/v/?s=chromeos%2Fbb%2Fchromeos%2Fwizpig-paladin%2F1723%2F%2B%2Frecipes%2Fsteps%2FHWTest__bvt-inline_%2F0%2Fstdout From this CQ run: https://chromiumos-build-annotator.googleplex.com/build_annotations/edit_annotations/master-paladin/2108779/?
,
Dec 7 2017
Should be fixed now. We've pushed out a revert : https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/814914
,
Dec 7 2017
Issue 793070 has been merged into this issue. |
|||
►
Sign in to add a comment |
|||
Comment 1 by kerl@google.com
, Dec 7 2017FYI, I'm getting this error when trying to use `atest` from my workstation as well: $ atest label remove pool:hotrod -m chromeos1-row4-rack5-host3 Operation label_remove_hosts failed: DatabaseError: (1665, 'Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED.')