This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts.

discards ee81d54afe 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] discards 10cf22b324 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] discards 75a15cc1cb 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] discards 227a040e3a 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] discards 06a642f8e5 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] discards 2dfd054e87 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] discards 57ea255ec8 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards 4cff9baeba 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards 6598d243bf 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards 08bc901edd 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards 6dfaa68b2a 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards 7435b2f984 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards 7a33ef8db1 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 8414b2f438 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards 62fc7825e1 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards fd0910566d 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 4d5f62e9fd 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards 06371b5ee2 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 576ffb0c8c 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 0759ec97f4 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 4e20a3506b 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards a0bfe1a0f9 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards 8eec92d18e 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards 05d888e0c8 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards c66c7c06b0 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 640037f33b 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards e2fb7cfe4f 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards b2ffda3d6e 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards 67bc814896 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 62fcbd6fa4 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards d2255216f3 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 1abdc5f1d0 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 66535e5aef 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 9423a9dd74 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 4b0bf2ec7d 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 7f61049ca7 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 8964a98c00 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards bf07c7018b 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 79fe72baa4 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 9fce7d4511 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 2efbfa0585 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards d115b4f288 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 1498120782 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 0dde087b18 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 135dd18ae1 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 5ed9e65fa7 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards bf317140e6 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 212c141fee 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards ab57a2f57b 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 6729915eca 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 876ecea3b2 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 545cbd6cff 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 2b9b102b2e 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 066e014004 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 59745eaceb 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 6ab9512327 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 91aa68e5f7 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards dd3371973e 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards ecbb77b996 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 41af0bbeb0 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards dccc151844 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards cd4a60d17c 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards cc6a265015 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 4e68d7659c 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards e2b82d4a32 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 00ac031d2f 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 7a61719b97 124: onsuccess: #2159: 1: Success after linux: 23 commits discards fe1ef0d24a 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards a987aa42ff 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards f1996ec07e 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 3e5e7eb3f4 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 6cd22bd9d8 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 5d138bc52a 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards e8d3ec1e9d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 969832b4ca 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 353db4e010 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards b60a1d64b8 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 365c4fd531 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards e26e8977b5 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 18207dd598 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 14145d4c42 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 76ceb3f050 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 963270ecd4 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 324b139504 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards ab622f4fe3 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards a60cf077c8 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 1776c49211 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 424a15958d 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 07be614990 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 9bcadaf2ec 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 7357732f17 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 80ed8d6652 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 07c1739a77 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards e540203c11 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards ff71d64c4e 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 14dbd37793 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards a128029ecc 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards a14e2f38c7 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 3ec45ef027 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2d328660ad 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 672474f4c1 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 8cd8881f98 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 13d41246f0 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 05155c4ce1 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 757455da1d 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 9a49b24413 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 9d5f425a4a 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 9b3cee64c6 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 8b9eec6b93 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 81e844e3b6 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 33f120c7c4 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 951c7c6b04 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 8b5095ae3e 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 032eb55b56 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 4277e7b4e4 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new d0c8cf682d 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new dec126a493 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 43d16239b5 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 175abcb58e 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 9e894fea44 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 265c28ad66 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 3a948331e4 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new fc266178d9 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 366971d84b 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 4842dbc890 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 00c9f3fe8a 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 5df6f1117e 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new cb0a20d2a3 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 23d83320df 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 6a3d29ab75 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 3464b14b84 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 15b78750c4 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 4febb92915 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 7bac9bf0dd 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 83aa077db4 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 7e1a79abf2 124: onsuccess: #2159: 1: Success after linux: 23 commits new b3efce2103 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new e9a3c8dfff 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new e0009371f9 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 2db86f0e30 128: onsuccess: #2163: 1: Success after linux: 23 commits new 17907aedda 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 86d5802577 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 4df1f4eb21 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 0d9b3fa7bd 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 9ceeaff8a4 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 97d0b2980b 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new b57b6107f2 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 60e04f12b5 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new e4715aa402 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new fc2443d5eb 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 38f0315791 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 5aba8c1b98 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 020b8f2732 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new b664e2c1e6 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new f0db7935f9 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 28ece5952e 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 1678fe8fa7 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 629a5e31fc 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 4d33c4551f 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 595ff9c0c7 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new b4220f67e6 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 4464bea963 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 912a62e07c 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 0b1355c0be 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new c3bf09d270 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new e4a062c680 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 08c1d1a06d 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 4f2d9bdd52 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 42d89c351b 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 86e4b08187 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new e51fd21124 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 8d10f47458 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new aee7cbc74b 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new d1d8609c63 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new 1b6bf08fae 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new b71d1b3ccc 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new da8c4b55a7 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 1eec233534 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 43eb32e7bc 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new e3c1759a25 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new 02dc87f898 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new 0cf7534360 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new 48d902071b 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new a1f58d72d3 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 81a7fcd582 173: onsuccess: #2208: 1: Success after gcc: 10 commits new b4b8ae957a 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new 3c5bb7bbac 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new ac5c25573d 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 41954d3218 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 9f827d972e 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 3a4f506710 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new 293fbf0548 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new 38c9dff533 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new db82c7c135 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new ca5969c472 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new 6051634bd3 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new 10b648f802 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] new 26836351f2 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] new be27418f3e 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] new 22e9d92d07 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] new 2f3e2f3c8b 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] new d1da3d645c 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] new 15282c73f8 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits

This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:

* -- * -- B -- O -- O -- O (ee81d54afe) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]

You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.

Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.

The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.

Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1764 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30536 -> 30532 bytes 04-build_abe-stage1/console.log.xz | Bin 72692 -> 73488 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8616 -> 8624 bytes 07-build_abe-glibc/console.log.xz | Bin 244332 -> 244696 bytes 08-build_abe-stage2/console.log.xz | Bin 204304 -> 204024 bytes 09-build_abe-gdb/console.log.xz | Bin 37848 -> 37892 bytes 10-build_abe-qemu/console.log.xz | Bin 31548 -> 31932 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3928 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2864 -> 3496 bytes 13-check_regression/console.log.xz | Bin 41592 -> 20704 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 179 +- 13-check_regression/mail-body.txt | 210 +- 13-check_regression/results.compare | 125 +- 13-check_regression/results.compare2 | 9081 ++++++++----------------------- 13-check_regression/results.regressions | 64 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 212 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results | 64 +- sumfiles/g++.log.xz | Bin 3443696 -> 3433420 bytes sumfiles/g++.sum | 2852 +++++----- sumfiles/gcc.log.xz | Bin 3050808 -> 3044708 bytes sumfiles/gcc.sum | 6391 +++++++++++----------- sumfiles/gfortran.log.xz | Bin 1033840 -> 1042444 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213528 -> 213556 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 422980 -> 431656 bytes sumfiles/libstdc++.sum | 14 +- 42 files changed, 7217 insertions(+), 12151 deletions(-)