Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.0.15
-
None
Description
CURRENT_TEST: main.partition_innodb --- /mnt/buildbot/build/mariadb-10.0.15/mysql-test/r/partition_innodb.result 2014-11-25 12:12:48.000000000 +0200 +++ /mnt/buildbot/build/mariadb-10.0.15/mysql-test/r/partition_innodb.reject 2014-11-26 02:28:43.000000000 +0200 @@ -541,6 +541,7 @@ PARTITION BY list(a) (PARTITION p1 VALUES IN (1)); CREATE INDEX i1 ON t1 (a); DROP TABLE t1; +db.opt # # Bug#54783: optimize table crashes with invalid timestamp default value and NO_ZERO_DATE # mysqltest: Result length mismatch
|
Jan, looks like this was introduced with this commit of yours:
revno: 4513
|
revision-id: jplindst@mariadb.org-20141125093801-nrsv7259uxzlu4ub
|
parent: jplindst@mariadb.org-20141125063103-r7q5vxxw0mfpc55p
|
committer: Jan Lindström <jplindst@mariadb.org>
|
branch nick: 10.0-bugs
|
timestamp: Tue 2014-11-25 11:38:01 +0200
|
message:
|
MDEV-7046: MySQL#74480 - Failing assertion: os_file_status(newpath, &exists, &type)
|
after Operating system error number 36 in a file operation.
|
Apparently the new testcase leaves stuff around that breaks following tests.
You can see this, if you run the test like this:
./mtr --mem innodb.innodb-mdev7046 main.partition_innodb
|
|
|
innodb.innodb-mdev7046 'innodb_plugin' [ pass ] 141
|
main.partition_innodb 'innodb_plugin' [ fail ]
|
Test ended at 2014-11-26 11:20:15
|
|
|
CURRENT_TEST: main.partition_innodb
|
--- /home/knielsen/my/10.0/work-10.0/mysql-test/r/partition_innodb.result 2014-10-16 15:19:35.500341000 +0200
|
+++ /home/knielsen/my/10.0/work-10.0/mysql-test/r/partition_innodb.reject 2014-11-26 11:20:15.083007691 +0100
|
@@ -541,6 +541,7 @@
|
PARTITION BY list(a) (PARTITION p1 VALUES IN (1));
|
CREATE INDEX i1 ON t1 (a);
|
DROP TABLE t1;
|
+db.opt
|
#
|
# Bug#54783: optimize table crashes with invalid timestamp default value and NO_ZERO_DATE
|
#
|
|
|
mysqltest: Result length mismatch
|
The main.partition_innodb fails. But if you run it like this:
./mtr --mem main.partition_innodb)
|
|
|
main.partition_innodb 'innodb_plugin' [ pass ] 5918
|
main.partition_innodb 'xtradb' [ pass ] 6275
|
it passes.
So the test failures depends on the order in which tests are run. It only
occurs if innodb.innodb-mdev7046 is run before main.partition_innodb (with no
server restarts in-between).
Attachments
Issue Links
- relates to
-
MDEV-7069 Fix buildbot failures in main server trees
-
- Stalled
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Jan Lindström [ jplindst ] | |
| Description |
http://buildbot.askmonty.org/buildbot/reports/cross_reference#branch=&revision=&platform=&dt=&bbnum=&typ=&info=&fail_name=main.partition_innodb&fail_variant=&fail_info_short=&fail_info_full=db.opt&limit=100 {noformat} CURRENT_TEST: main.partition_innodb --- /mnt/buildbot/build/mariadb-10.0.15/mysql-test/r/partition_innodb.result 2014-11-25 12:12:48.000000000 +0200 +++ /mnt/buildbot/build/mariadb-10.0.15/mysql-test/r/partition_innodb.reject 2014-11-26 02:28:43.000000000 +0200 @@ -541,6 +541,7 @@ PARTITION BY list(a) (PARTITION p1 VALUES IN (1)); CREATE INDEX i1 ON t1 (a); DROP TABLE t1; +db.opt # # Bug#54783: optimize table crashes with invalid timestamp default value and NO_ZERO_DATE # mysqltest: Result length mismatch {noformat} |
http://buildbot.askmonty.org/buildbot/reports/cross_reference#branch=&revision=&platform=&dt=&bbnum=&typ=&info=&fail_name=main.partition_innodb&fail_variant=&fail_info_short=&fail_info_full=db.opt&limit=100 {noformat} CURRENT_TEST: main.partition_innodb --- /mnt/buildbot/build/mariadb-10.0.15/mysql-test/r/partition_innodb.result 2014-11-25 12:12:48.000000000 +0200 +++ /mnt/buildbot/build/mariadb-10.0.15/mysql-test/r/partition_innodb.reject 2014-11-26 02:28:43.000000000 +0200 @@ -541,6 +541,7 @@ PARTITION BY list(a) (PARTITION p1 VALUES IN (1)); CREATE INDEX i1 ON t1 (a); DROP TABLE t1; +db.opt # # Bug#54783: optimize table crashes with invalid timestamp default value and NO_ZERO_DATE # mysqltest: Result length mismatch {noformat} Jan, looks like this was introduced with this commit of yours: {noformat} revno: 4513 revision-id: jplindst@mariadb.org-20141125093801-nrsv7259uxzlu4ub parent: jplindst@mariadb.org-20141125063103-r7q5vxxw0mfpc55p committer: Jan Lindström <jplindst@mariadb.org> branch nick: 10.0-bugs timestamp: Tue 2014-11-25 11:38:01 +0200 message: after Operating system error number 36 in a file operation. {noformat} Apparently the new testcase leaves stuff around that breaks following tests. You can see this, if you run the test like this: {noformat} ./mtr --mem innodb.innodb-mdev7046 main.partition_innodb innodb.innodb-mdev7046 'innodb_plugin' [ pass ] 141 main.partition_innodb 'innodb_plugin' [ fail ] Test ended at 2014-11-26 11:20:15 CURRENT_TEST: main.partition_innodb --- /home/knielsen/my/10.0/work-10.0/mysql-test/r/partition_innodb.result 2014-10-16 15:19:35.500341000 +0200 +++ /home/knielsen/my/10.0/work-10.0/mysql-test/r/partition_innodb.reject 2014-11-26 11:20:15.083007691 +0100 @@ -541,6 +541,7 @@ PARTITION BY list(a) (PARTITION p1 VALUES IN (1)); CREATE INDEX i1 ON t1 (a); DROP TABLE t1; +db.opt # # Bug#54783: optimize table crashes with invalid timestamp default value and NO_ZERO_DATE # mysqltest: Result length mismatch {noformat} The main.partition_innodb fails. But if you run it like this: {noformat} ./mtr --mem main.partition_innodb) main.partition_innodb 'innodb_plugin' [ pass ] 5918 main.partition_innodb 'xtradb' [ pass ] 6275 {noformat} it passes. |
| Description |
http://buildbot.askmonty.org/buildbot/reports/cross_reference#branch=&revision=&platform=&dt=&bbnum=&typ=&info=&fail_name=main.partition_innodb&fail_variant=&fail_info_short=&fail_info_full=db.opt&limit=100 {noformat} CURRENT_TEST: main.partition_innodb --- /mnt/buildbot/build/mariadb-10.0.15/mysql-test/r/partition_innodb.result 2014-11-25 12:12:48.000000000 +0200 +++ /mnt/buildbot/build/mariadb-10.0.15/mysql-test/r/partition_innodb.reject 2014-11-26 02:28:43.000000000 +0200 @@ -541,6 +541,7 @@ PARTITION BY list(a) (PARTITION p1 VALUES IN (1)); CREATE INDEX i1 ON t1 (a); DROP TABLE t1; +db.opt # # Bug#54783: optimize table crashes with invalid timestamp default value and NO_ZERO_DATE # mysqltest: Result length mismatch {noformat} Jan, looks like this was introduced with this commit of yours: {noformat} revno: 4513 revision-id: jplindst@mariadb.org-20141125093801-nrsv7259uxzlu4ub parent: jplindst@mariadb.org-20141125063103-r7q5vxxw0mfpc55p committer: Jan Lindström <jplindst@mariadb.org> branch nick: 10.0-bugs timestamp: Tue 2014-11-25 11:38:01 +0200 message: after Operating system error number 36 in a file operation. {noformat} Apparently the new testcase leaves stuff around that breaks following tests. You can see this, if you run the test like this: {noformat} ./mtr --mem innodb.innodb-mdev7046 main.partition_innodb innodb.innodb-mdev7046 'innodb_plugin' [ pass ] 141 main.partition_innodb 'innodb_plugin' [ fail ] Test ended at 2014-11-26 11:20:15 CURRENT_TEST: main.partition_innodb --- /home/knielsen/my/10.0/work-10.0/mysql-test/r/partition_innodb.result 2014-10-16 15:19:35.500341000 +0200 +++ /home/knielsen/my/10.0/work-10.0/mysql-test/r/partition_innodb.reject 2014-11-26 11:20:15.083007691 +0100 @@ -541,6 +541,7 @@ PARTITION BY list(a) (PARTITION p1 VALUES IN (1)); CREATE INDEX i1 ON t1 (a); DROP TABLE t1; +db.opt # # Bug#54783: optimize table crashes with invalid timestamp default value and NO_ZERO_DATE # mysqltest: Result length mismatch {noformat} The main.partition_innodb fails. But if you run it like this: {noformat} ./mtr --mem main.partition_innodb) main.partition_innodb 'innodb_plugin' [ pass ] 5918 main.partition_innodb 'xtradb' [ pass ] 6275 {noformat} it passes. |
http://buildbot.askmonty.org/buildbot/reports/cross_reference#branch=&revision=&platform=&dt=&bbnum=&typ=&info=&fail_name=main.partition_innodb&fail_variant=&fail_info_short=&fail_info_full=db.opt&limit=100 {noformat} CURRENT_TEST: main.partition_innodb --- /mnt/buildbot/build/mariadb-10.0.15/mysql-test/r/partition_innodb.result 2014-11-25 12:12:48.000000000 +0200 +++ /mnt/buildbot/build/mariadb-10.0.15/mysql-test/r/partition_innodb.reject 2014-11-26 02:28:43.000000000 +0200 @@ -541,6 +541,7 @@ PARTITION BY list(a) (PARTITION p1 VALUES IN (1)); CREATE INDEX i1 ON t1 (a); DROP TABLE t1; +db.opt # # Bug#54783: optimize table crashes with invalid timestamp default value and NO_ZERO_DATE # mysqltest: Result length mismatch {noformat} Jan, looks like this was introduced with this commit of yours: {noformat} revno: 4513 revision-id: jplindst@mariadb.org-20141125093801-nrsv7259uxzlu4ub parent: jplindst@mariadb.org-20141125063103-r7q5vxxw0mfpc55p committer: Jan Lindström <jplindst@mariadb.org> branch nick: 10.0-bugs timestamp: Tue 2014-11-25 11:38:01 +0200 message: after Operating system error number 36 in a file operation. {noformat} Apparently the new testcase leaves stuff around that breaks following tests. You can see this, if you run the test like this: {noformat} ./mtr --mem innodb.innodb-mdev7046 main.partition_innodb innodb.innodb-mdev7046 'innodb_plugin' [ pass ] 141 main.partition_innodb 'innodb_plugin' [ fail ] Test ended at 2014-11-26 11:20:15 CURRENT_TEST: main.partition_innodb --- /home/knielsen/my/10.0/work-10.0/mysql-test/r/partition_innodb.result 2014-10-16 15:19:35.500341000 +0200 +++ /home/knielsen/my/10.0/work-10.0/mysql-test/r/partition_innodb.reject 2014-11-26 11:20:15.083007691 +0100 @@ -541,6 +541,7 @@ PARTITION BY list(a) (PARTITION p1 VALUES IN (1)); CREATE INDEX i1 ON t1 (a); DROP TABLE t1; +db.opt # # Bug#54783: optimize table crashes with invalid timestamp default value and NO_ZERO_DATE # mysqltest: Result length mismatch {noformat} The main.partition_innodb fails. But if you run it like this: {noformat} ./mtr --mem main.partition_innodb) main.partition_innodb 'innodb_plugin' [ pass ] 5918 main.partition_innodb 'xtradb' [ pass ] 6275 {noformat} it passes. So the test failures depends on the order in which tests are run. It only occurs if innodb.innodb-mdev7046 is run before main.partition_innodb (with no server restarts in-between). |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Component/s | Tests [ 10800 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
| Workflow | MariaDB v2 [ 58734 ] | MariaDB v3 [ 65274 ] |
| Workflow | MariaDB v3 [ 65274 ] | MariaDB v4 [ 148550 ] |
revno: 4517
committer: Jan Lindström <jplindst@mariadb.org>
branch nick: 10.0-bugs
timestamp: Wed 2014-11-26 14:33:55 +0200
message:
MDEV-7214: Test failure in main.partition_innodbProblem is on test it tried to verify that no files were left
on test database.
Fix: There's no need to list other file types, it can only
list *.par files