innodb_fake_changes fails to apply
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
High
|
Unassigned |
Bug Description
To reproduce:
bzr branch lp:percona-server
echo "innodb_
make all
failure is:
Applying patch innodb_
patching file storage/
Hunk #8 succeeded at 2094 (offset -1 lines).
Hunk #9 succeeded at 2209 (offset 4 lines).
Hunk #10 succeeded at 2359 (offset -1 lines).
Hunk #11 succeeded at 2454 (offset 4 lines).
Hunk #12 succeeded at 2490 with fuzz 1 (offset 3 lines).
Hunk #13 succeeded at 2852 (offset 58 lines).
Hunk #14 succeeded at 2939 (offset 3 lines).
patching file storage/
Hunk #2 succeeded at 1687 (offset -1 lines).
Hunk #3 succeeded at 3168 (offset -4 lines).
Hunk #4 succeeded at 7519 (offset -1 lines).
Hunk #5 succeeded at 7742 (offset -4 lines).
Hunk #6 succeeded at 7805 (offset -1 lines).
Hunk #7 succeeded at 7894 (offset -4 lines).
Hunk #8 succeeded at 8008 (offset -1 lines).
Hunk #9 succeeded at 10808 (offset -4 lines).
Hunk #10 succeeded at 12291 (offset -53 lines).
patching file storage/
patching file storage/
patching file storage/
patching file storage/
patching file storage/
patching file storage/
Hunk #2 succeeded at 2010 (offset 1 line).
Hunk #4 FAILED at 2124.
1 out of 4 hunks FAILED -- rejects in file storage/
patching file storage/
patching file storage/
Hunk #5 FAILED at 2026.
Hunk #6 succeeded at 2166 (offset 15 lines).
1 out of 6 hunks FAILED -- rejects in file storage/
patching file storage/
Patch innodb_
Related branches
- Stewart Smith (community): Approve
-
Diff: 1610 lines (+489/-184)14 files modifiedpatches/innodb_adaptive_hash_index_partitions.patch (+5/-5)
patches/innodb_buffer_pool_pages_i_s.patch (+1/-1)
patches/innodb_buffer_pool_shm.patch (+3/-3)
patches/innodb_deadlock_count.patch (+4/-4)
patches/innodb_fake_changes.patch (+214/-67)
patches/innodb_fast_checksum.patch (+6/-6)
patches/innodb_files_extend.patch (+6/-6)
patches/innodb_fix_misc.patch (+5/-5)
patches/innodb_kill_idle_transaction.patch (+189/-37)
patches/innodb_pass_corrupt_table.patch (+25/-25)
patches/innodb_separate_doublewrite.patch (+11/-11)
patches/innodb_show_status_extend.patch (+13/-13)
patches/mysql-test.diff (+5/-1)
patches/series (+2/-0)
Changed in percona-server: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Yasufumi Kinoshita (yasufumi-kinoshita) |
tags: | added: cr i15686 innodb-fake-changes |
Changed in percona-server: | |
milestone: | none → 5.5.16-22.0 |
Changed in percona-server: | |
status: | Triaged → Fix Released |
It is just you don't be along with the previous "series" file.
Almost no changes were needed. The patches are not wrong at all.
I revived kill_idle_ transaction. patch fake_changes. patch
innodb_
innodb_
and create lp:~percona-dev/percona-server/5.1-kill_idle_transaction-innodb_fake_changes
If you cannot treat the patches, you can use the branch for testing.