Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
N/A
-
None
Description
The suspect (s) seem to be some failed database inserts on various BuildBot masters.
Error in async insert into database: [Failure instance: Traceback: <class 'MySQLdb.DataError'>: (1406, "Data too long for column 'failure_text' at row 1") |
|
As of now, the column is defined as TEXT.
MariaDB [buildbot]> describe test_failure;
|
+--------------+--------------+------+-----+---------+-------+
|
| Field | Type | Null | Key | Default | Extra |
|
+--------------+--------------+------+-----+---------+-------+
|
| test_run_id | int(11) | NO | PRI | NULL | | |
| test_name | varchar(100) | NO | PRI | NULL | | |
| test_variant | varchar(16) | NO | PRI | NULL | | |
| info_text | varchar(255) | YES | | NULL | | |
| failure_text | text | YES | | NULL | |
|
+--------------+--------------+------+-----+---------+-------+
|
The approach and the scope of this MDBF is to alter the failure_text column to LONGTEXT and set up monitoring to see if the problem is resolved.
Zulip discussion: https://mariadb.zulipchat.com/#narrow/channel/236699-Buildbot/topic/Missing.20test.20failures.20in.20cross-reference
