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 64f653ba32 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards b46c72de36 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 74b88a07f8 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 1fb1c93367 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 377b3fc5b0 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 40d714cf63 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards d07b1f1e9b 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards b42aa0adc4 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 42023febe8 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards b2da0f531e 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 5a8fec779f 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 0b7b6e4f2b 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards b67d51587e 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 3e0bead87a 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 1e7ff02d3f 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards ae979ae617 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards a587b80eda 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 166cac51a7 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 32c92b5a1e 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 378b0a55de 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 3abba0de3e 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards c51a04db88 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards ccd6b2f812 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 55a1a52935 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards e30b3f9a2f 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 8d6f2d658b 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 1a2c93a355 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 1b51de3f50 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 7c52441f85 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 534e1e2b12 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 0ba0ea4968 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards d7beab5e8b 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 54dae509a0 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 9aed3f1161 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 14216c083d 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards d4532f4b3b 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards cc7d9e619b 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 9fc3d3006b 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 3b27e54307 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards f6a1697c54 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 92c092e0a4 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 27f86f07d8 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards a68bea66b7 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 16e59847c8 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 3798262f48 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 1082d1c7d1 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 3ce42bdb95 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 4e200cc3fd 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 1475d88d76 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 785b8c827c 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 6fb44efb81 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards a31d48b78c 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards b04f969372 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards f20b41ca0a 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 0933695ad0 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 20fbb4d313 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards c958c3ddfb 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 278790743f 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 03ce41d8f6 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 75fd38435c 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards a352f5229f 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards cf819ec50b 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 1f2d90517e 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 08834edcd9 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards eba55918df 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards b1e560bc0a 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards e50d002e7a 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 9000c258f5 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 4925cb96e9 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards e08d866660 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards d465b699f8 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 217ce941f8 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 67904a44b3 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 2a9aaa00c8 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 36b3ff489f 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 613b2e051d 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards da3b66c8ab 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards db94af1835 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 39446c52d6 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 86b108ec52 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 7c31e762ae 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 5fc99be82b 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 2cb1992805 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards d3db0289f8 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards bdc3bf8321 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards d01e813d42 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 08c2af825a 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards 70a2bbfbb4 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 11281b03ab 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards 936b75094a 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 4cddbc071f 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards cf897bc21f 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 8001702d71 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 635e852160 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards 6dd35866c4 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 86ff458d63 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards f6a4ba1385 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards efaf001260 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 2ffbfc4e2a 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 2642650403 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 0e93547853 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new b3cfa9978b 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new 34ba38bf00 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new 10f424efcc 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 14dbb5bcbd 235: onsuccess: #2483: 1: Success after linux: 108 commits new 0c8d3d6859 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 3a88df4d2b 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new e67baaa4e6 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new e77d2259a8 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new bc102ffe3b 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 5494d89690 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 27aa9c73d0 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new f4f51d4533 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new a5cc4e4908 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new aab9e16d6b 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 6df66727f2 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new 6648db39ed 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new b97d611465 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 58f944af90 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 5969ee956d 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new ee656daee6 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new d55b7e0bf8 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 2bbad0d8a9 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new d74f6ea96b 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new d98487e7d2 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 83fe58b36e 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 92426a3f1e 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 351d13507d 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 4a606d9524 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new e1dc8bd7c5 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new d9e5143a24 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new d2f86132bb 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new c38657f95b 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 535d431488 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new b665038891 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new c2c3c08a75 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 8f89a575b8 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 83bde9a47c 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 43a14d600e 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new dbda5fe72f 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new e3b89c93cc 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new cbc1e135c7 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new de7c423927 273: onsuccess: #2521: 1: Success after gcc: 2 commits new bc98f935f3 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 566f6b3cab 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new c63c4eb902 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new b7cd831d26 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new af6d1f2b85 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 88abd83237 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new e26ae5a043 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 5a4d687d24 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 45e4832e69 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new a2d3a2d90c 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new add3c7792c 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new c3430228b0 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new a3116252ee 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new af24f7ad0c 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new c7da0b74bf 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 0d55dd7e49 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 5c9fbbf79c 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new abc69c328c 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 6358bf58f9 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 5c913f70ad 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 71238dc799 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 294424807a 295: onsuccess: #2545: 1: Success after linux: 10 commits new 3870753d2c 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 17ee70cecb 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 116fdc3d9a 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 02a5106d5c 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new b15a72f559 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 621d2e3f32 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 447070ca9e 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 30239d9a7c 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 7cbeaa4738 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 492901f7ba 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 823166ae9b 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new f9f9f79444 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 0f2e9ecf96 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 7b478954da 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new ef3e1a8107 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 30cf6bd9a6 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 6ca4070cee 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 8ded91b54a 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 838df7ca20 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new beec01c689 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 62f8561227 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 74d9153268 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new e4973e2762 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new b7fa7b4535 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 588dda64f7 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 646362a365 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new cfd3fcb872 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new eb72a4e16a 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 58c8deaf96 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 460a2219e3 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 8fb6aeddfc 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new f9cce6a245 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 501024e375 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 7a4d5c0378 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 3103114af7 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 0a911938c1 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new c9103a168a 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new dfb5f04d04 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...]

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 (64f653ba32) \ 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 1812 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 31780 -> 31988 bytes 04-build_abe-stage1/console.log.xz | Bin 73748 -> 73720 bytes 06-build_abe-linux/console.log.xz | Bin 9168 -> 8784 bytes 07-build_abe-glibc/console.log.xz | Bin 245164 -> 246120 bytes 08-build_abe-stage2/console.log.xz | Bin 204808 -> 206220 bytes 09-build_abe-gdb/console.log.xz | Bin 39356 -> 39652 bytes 10-build_abe-qemu/console.log.xz | Bin 32364 -> 33156 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3960 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3420 -> 3132 bytes 13-check_regression/console.log.xz | Bin 7724 -> 7968 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 19 +- 13-check_regression/mail-body.txt | 124 +- 13-check_regression/results.compare | 59 +- 13-check_regression/results.compare2 | 195 +- 13-check_regression/results.regressions | 59 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 126 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 59 +- sumfiles/g++.log.xz | Bin 3403464 -> 3439276 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 3039552 -> 3032072 bytes sumfiles/gcc.sum | 4764 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1038152 -> 1044160 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214728 -> 214632 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2692 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435140 -> 431616 bytes sumfiles/libstdc++.sum | 19 +- 43 files changed, 2916 insertions(+), 2663 deletions(-)