Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
M
MariaDB
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
nexedi
MariaDB
Commits
9d687a69
Commit
9d687a69
authored
Jan 09, 2012
by
Vladislav Vaintroub
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
MDEV-63 - attempt to fix the warning exclusion
parent
f586a37c
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
mysql-test/include/mtr_warnings.sql
mysql-test/include/mtr_warnings.sql
+1
-1
No files found.
mysql-test/include/mtr_warnings.sql
View file @
9d687a69
...
@@ -159,7 +159,7 @@ INSERT INTO global_suppressions VALUES
...
@@ -159,7 +159,7 @@ INSERT INTO global_suppressions VALUES
/* innodb foreign key tests that fail in ALTER or RENAME produce this */
/* innodb foreign key tests that fail in ALTER or RENAME produce this */
(
"InnoDB: Error: in ALTER TABLE `test`.`t[123]`"
),
(
"InnoDB: Error: in ALTER TABLE `test`.`t[123]`"
),
(
"InnoDB: Error: in RENAME TABLE table `test`.`t1`"
),
(
"InnoDB: Error: in RENAME TABLE table `test`.`t1`"
),
(
"InnoDB: Error: table `test`.`t[123]` does not exist in the InnoDB internal"
),
(
"InnoDB: Error: table `test`.`t[123]`
.*
does not exist in the InnoDB internal"
),
/*
/*
BUG#32080 - Excessive warnings on Solaris: setrlimit could not
BUG#32080 - Excessive warnings on Solaris: setrlimit could not
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment