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 656579522a 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards ffcdc55f42 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards db321182c3 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 73d91281dc 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards e62862509a 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 02976775bc 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 6817e1ae04 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards d5ba4a063d 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards b5b70158ca 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards acf281aa51 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 0339d2e6ee 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 7a711f7e05 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards bf983242f3 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards af77b0ceb8 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards f6c1782197 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards e441b6b0f7 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 29a92e1e4d 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards d4816d2739 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards b38b3ed692 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 6ea88888a8 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 4040127d4e 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 7e37a2e3ee 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 9074183782 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 032f8f845f 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 5e0e1d1eb9 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards aec561b119 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 2082311cac 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 881bcede1a 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 51f6ca4d02 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards f80f90fde0 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards c6d5b12d9c 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards e7b20fede2 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards e28d2ef77b 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards be0f7a0679 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 9cb446ffac 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards ea55cd1166 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards c9c9d73cd5 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 43ac218a20 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards f6f071df1d 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards ae127c8da5 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 321bb6ea45 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 316c8ea1d4 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 5adfbf584c 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards b6ca5f58d0 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 2f513d7e82 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 13325f5b0c 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 5b1c38840d 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 147f1e9e84 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 47f16b38a7 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 9770d013f4 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 7d44ed7c76 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards e088102e29 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards f024962414 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 2677276a5f 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 700b344921 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 141fc1a84b 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 7f5301717f 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 3ec7b3392d 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 81d9aced31 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards eef5fc3858 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards bf73761b01 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 2c66d70557 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards ecb786bd33 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards caa5e639b6 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 4a3b0b7298 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards da416c3ece 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards d18b57fa22 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 060f68293b 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards e6e1b97a13 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 57f7e5b30a 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards da5d447176 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards b95af0f531 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards f17c56ec90 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 47053c67ee 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 3b161b8d98 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 3772331b68 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 31ec9efc7c 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 3bc301922f 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 0246fcdae0 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 264aee863e 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 1eba186d8c 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 21875da94d 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards ea789f5e1c 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 8a0dbb9676 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 5bfad944f0 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards f52874079f 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 3d6e4b4260 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards cc2d74811a 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards bcc81bd4cd 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 1e1c0f6b7f 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 9ed8501df9 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards a9be3bf90f 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 9f206534b2 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards abe84fcca9 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards f4516b2410 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 25b8407141 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 22f342f788 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 9c9c114841 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 63dc118662 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards d86732ea96 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards 9b166e45a0 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new 997bbc76e6 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new 9a5b5c823b 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new ced7241416 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 785b4f3ff0 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 35db8a33dc 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 2a67e72589 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 0346d6e213 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 1cae8a2c8f 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 83e1ca85f2 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new ef9f11a3c7 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 00dbe83ea1 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 03426510a8 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new fbb10c90e5 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new e103d07c3d 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new b36a132cba 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new a6dc00dbaa 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 2cc73352d5 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 567dd9e520 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 1ba358b7c6 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new b963acffe6 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new c798446262 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 0669d6571a 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 5587594ebf 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 262d4912de 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 5e1d3ee09f 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 976f9e853e 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new ae101ec71e 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 5134dc1801 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 28eeed019d 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 13667414f9 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 68528b3794 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new a9d59fafc7 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 744600660d 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new f0f9deb0da 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 07461f782e 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 2ec8d01700 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 4057d9fb40 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 4a7b2676fc 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 396d1acb91 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 20479e6722 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new d39b8d8a4f 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 5ee2e0dd5e 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 6853cf652f 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 06b9d72b71 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 3c87eaed3e 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new e183150757 292: onsuccess: #2541: 1: Success after binutils: 13 commits new b61661e788 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 0f0d4b81fe 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 4247e441e6 295: onsuccess: #2545: 1: Success after linux: 10 commits new 27bddefd96 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new bd35008377 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 2773f2b8b5 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 53205bc4d9 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 67ec08ccfa 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 365db59402 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new b31814e0ec 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new b39ab5b5b7 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 6914d6593d 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 596af79616 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 29eb9b946b 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 481896cc3a 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 94f516ffa7 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new eefb0265db 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 83272779b7 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new cddc66b84c 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 2e7ccff60f 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 52270fcacd 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 3d1f1304f8 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 53917b1454 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new ab4ceef91b 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new be1bc46c6b 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 8d69b0b6e0 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 7057ded222 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 35b6ad4ee5 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new c17fd81fdb 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new e4e45389aa 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 8e15f43752 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 1d3a7ba038 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new cee5c99a7c 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 4123d36db1 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new fd3b2accbd 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 8314a6dd78 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 9ef182bb1e 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new ed15fe82ed 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 78e9e116a2 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 7be8c97573 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new b517565cbf 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 576b322622 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 7c1bb8ac8b 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 66341e9d21 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new d8bb90ed6e 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 3957a2922a 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 4fe8343272 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 4209a1f412 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new ded0c5cbf7 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 2040696060 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new dbff24b248 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 322cb9001f 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 17789458c8 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 316b65b9ca 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 65d935d12b 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new c45aa3e6a2 348: onsuccess: #2598: 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 (656579522a) \ 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 1832 -> 1828 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 31756 -> 32000 bytes 04-build_abe-stage1/console.log.xz | Bin 74212 -> 73884 bytes 06-build_abe-linux/console.log.xz | Bin 8476 -> 8780 bytes 07-build_abe-glibc/console.log.xz | Bin 247040 -> 245288 bytes 08-build_abe-stage2/console.log.xz | Bin 208288 -> 205132 bytes 09-build_abe-gdb/console.log.xz | Bin 39068 -> 39076 bytes 10-build_abe-qemu/console.log.xz | Bin 32112 -> 32276 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3924 -> 3964 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2796 -> 2664 bytes 13-check_regression/console.log.xz | Bin 7584 -> 7860 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 22 +- 13-check_regression/mail-body.txt | 96 +- 13-check_regression/results.compare | 35 +- 13-check_regression/results.compare2 | 141 +- 13-check_regression/results.regressions | 35 +- 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 | 98 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 35 +- sumfiles/g++.log.xz | Bin 3404800 -> 3424080 bytes sumfiles/g++.sum | 40 +- sumfiles/gcc.log.xz | Bin 3039424 -> 3035836 bytes sumfiles/gcc.sum | 4382 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1047072 -> 1039344 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214784 -> 214772 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435376 -> 437972 bytes sumfiles/libstdc++.sum | 146 +- 43 files changed, 2597 insertions(+), 2563 deletions(-)