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 61969173c5 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards bc87d7e5ea 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards c13472272f 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards cdcd3b3f5e 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards a03c1bc9e8 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 927600f1e9 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards b3110e0b84 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 778dc3093a 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards f6b7526ff9 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 45c581a310 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards b3235028aa 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 3311096707 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards f40e67ead4 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 08f4d230f5 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 9923b7ec81 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards afe57f730c 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards ac6235905d 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards d13eb172cd 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 54d16f507f 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 4f6c37dc62 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards c49cb565d5 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 417cd90fa7 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 6bea5123bf 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards da0ea0b9a6 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards b4b63d4d8a 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 99756dea51 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 3b41ffa7b2 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 723409b000 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 62ce7914be 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 7900493c8b 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 93b8bdab0a 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards ed1c30761e 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 69e015e7f0 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards a0aa112832 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards d38f88491a 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 9acbefae85 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards cfde84d079 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 962e7d3d63 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 7624df7d82 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards ba63a30018 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards cb71c1e61d 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 46619932d7 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards db76eb8568 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 7e56609238 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards ee51458f58 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards ba49c48077 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 9eb6645f8b 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards f1c0d0c51c 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 43cf8cf24c 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards f756cb5b29 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards c7ac39e93a 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 84750202d5 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards dbc2c3abe4 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards ec028de278 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 6b50dc40c9 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards a2e5184471 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 207626feae 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 5ffe3feb71 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards ca6c88f2cb 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards a675e5dd0c 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 1d624ba3fd 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 1f38a1f73f 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards f8a0352d2a 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 97f3785ec2 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards ee50c9aa1d 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 406449b1d2 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards b1ac837d2e 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 2e9e6d36f6 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards cacf5d5413 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 15f5275f17 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards a418326a26 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 0d0cb27d9e 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 13a9ff70ad 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 92e813f8f7 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards b13a9cea5e 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 1846c044e1 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards affcf1ab85 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 40f1a9ad47 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 506a48eaac 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 8b06c7f7d8 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 588ae86700 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 14dae69f54 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 78b790033e 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards a853052d4d 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 5784d1427b 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 63fea8f6fc 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 074b25c275 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 589c1fbea0 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 77ffa0a97a 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 8e3f4c48c2 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 49b0ec0d5c 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards f5a3d078a5 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 5442919c24 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 06aa74f3f6 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 0fb075aa7c 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards ca15d5a1b6 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 2f6e2c7044 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 2a527980b5 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards cbf9027b82 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 631f9efae8 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards f0bfb92e58 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 0d059d974a 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 66baff3d37 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 235750b10f 273: onsuccess: #2521: 1: Success after gcc: 2 commits new b02300d021 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 72fdfe45bf 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new d6df464898 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 219eaafbf6 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new c804f23424 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 4cb1a14f49 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new cd748203fb 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 3733e164dc 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 572b5b1403 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 26d0f33ead 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 071cfc5ede 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 0c949552e0 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new caf63e270f 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 3b39f965f7 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 78bd8944e6 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 413c613efe 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 311cf2fdf1 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 09cab7dfac 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new e7df4b5b53 292: onsuccess: #2541: 1: Success after binutils: 13 commits new e643b54392 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 42270d9399 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 9f08911a4a 295: onsuccess: #2545: 1: Success after linux: 10 commits new 412aad259e 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 7f2944e7d9 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 956d399481 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new b33713e0c1 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new afd8f22998 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 002a0ccc1b 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 1902b3a28e 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new ef41b565d5 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new de38e83bf6 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new a5c3407b4a 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 5a8fbf5b5c 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new facc4b1277 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 0397a1d225 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 4892e76057 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 12ce750630 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 9acd141616 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 0f152144c9 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 42ba63ad2c 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 714b1eeff9 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 7bfb077fd5 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new a5a01e9fd4 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 86cde69b28 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 38a1647ac4 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new a9d0d2624b 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 2851f61385 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 5165d682bd 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 8c07d320de 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 8f3c668ed3 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 90da92ce7b 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 23236e4aea 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 30b2c67e78 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new f3c123129f 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 38b8f0cbbb 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 4f360ce4cb 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 0d8edd78b5 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new d2ab3840bf 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 2e807a90df 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 56ec4854f2 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new ca92bcaf05 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new ca042c014e 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 4f1f87ac3c 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new fc2bff9123 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 6fb5c7da1d 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 4f9192b41a 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new bd8d1d63a7 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new ae85dc1a07 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new a6df74a005 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new c41135520b 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new d20007e9eb 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 5c409cce09 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 4663bf5343 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new f3268b9faa 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 482fdcf4b8 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 0374f80b22 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new a04206c5a6 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 6c02512a24 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new c42c9050a8 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 941830ecd1 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 26841beb7e 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 8c455b3e39 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new caa841b923 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 307294440f 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 98ab6c2e75 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 289d2305c0 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 2aaed5d5c3 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 0c26448b05 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 72cffd5888 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 7f57a2d27a 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 65acf01d01 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 225dbcb637 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 69d77a36f4 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new aa213fb3e0 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new bddabd8db8 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new e2e95d0373 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new bdcd33fa35 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 7fde74c3ae 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new d4ca7bf523 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/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 (61969173c5) \ 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 1776 -> 1832 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 31340 -> 31920 bytes 04-build_abe-stage1/console.log.xz | Bin 73708 -> 74364 bytes 06-build_abe-linux/console.log.xz | Bin 8988 -> 8924 bytes 07-build_abe-glibc/console.log.xz | Bin 247132 -> 245336 bytes 08-build_abe-stage2/console.log.xz | Bin 206896 -> 205376 bytes 09-build_abe-gdb/console.log.xz | Bin 38512 -> 38840 bytes 10-build_abe-qemu/console.log.xz | Bin 32244 -> 32056 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3916 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3440 -> 2984 bytes 13-check_regression/console.log.xz | Bin 7468 -> 7820 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 24 +- 13-check_regression/mail-body.txt | 79 +- 13-check_regression/results.compare | 38 +- 13-check_regression/results.compare2 | 146 +- 13-check_regression/results.regressions | 38 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 81 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 38 +- sumfiles/g++.log.xz | Bin 3407380 -> 3418724 bytes sumfiles/g++.sum | 31 +- sumfiles/gcc.log.xz | Bin 3029596 -> 3018628 bytes sumfiles/gcc.sum | 3881 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1042856 -> 1038936 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 215180 -> 215224 bytes sumfiles/libgomp.sum | 9 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437068 -> 438400 bytes sumfiles/libstdc++.sum | 277 +-- 43 files changed, 2323 insertions(+), 2445 deletions(-)