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 a2416efdce 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 83146820fe 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 33d13097cd 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 1e82fb72e1 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards ed3519c389 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 84f6e2b5d7 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 0228b58b88 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 04f8735495 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 429d15ca85 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 0c7416bda5 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 530cec5df6 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards bc1241e64e 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 5378bb18d0 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards a210b8ad87 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 98fd4c2d9e 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 6aafc49cee 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 34b758362b 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards ab954c0582 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 3e4f2510e6 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 045feba4ba 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 08580462b0 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 0e82df301b 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 93746cb655 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards c0b51038c1 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 7fe2aa044a 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 35860a4be6 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 864c14ed06 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards d05662d6c2 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 2787e87c3d 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 42b4ded543 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 9052ce9f9f 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards fdd2cb3df5 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards ad8df0dc1f 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards a759fa2100 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards e52d0bf147 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 0c4078762a 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 8d56e14efc 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 0667cffffd 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards aa47cc2066 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards c471dabfdd 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards fa6a6b4a6e 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 14f443a9a1 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 94cafc8719 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 99791160f8 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards ec1365810c 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 3a2f2d59b9 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 73fbaf4912 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 099dd0888b 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 37db52cbd8 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 750b034ce5 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards dbce0243dc 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards b15555e429 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 181cf4adbe 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards f39f788c58 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 69e68c467a 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 32fc9a31af 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards f25a4c121d 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards ff17b1506c 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 7480aa631a 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 34e326f668 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 7bcb53a9b2 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 06281f10ae 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards c390c695c3 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 4de63d2c93 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards e1c2a5ea7a 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards f17eea228a 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards f71f00f289 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards d0de722139 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards d59ae51d07 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards de60366444 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 26c165e5bf 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards c6b980ac52 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards c024101b8c 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 5b7edba775 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 509a6cf7de 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards a274a6569b 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards a6ddd71b23 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 08e95d281f 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards e1baa682e6 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards d35fd5a19b 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards a629a3c71d 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 90156bcabe 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards fdf8b1e703 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards 703a2dd044 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 01b835a9d5 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards ef8622ba03 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 002b0a653f 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards 58c349a7a3 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 4cd75f9e6a 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 6f0f747740 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards d700b17f1b 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 8a1488623c 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards 5ec123f915 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 241ba3e1a6 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 479efa1a4f 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 4dbae9a0cf 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 4d09ae9c3c 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 86508b4e75 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 8ac5daceb5 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards 634dadd6f6 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards 26e67beb1c 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new 8fe562f1fa 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new 539aad3cfc 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 838a593f5c 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new 57c77e0ebe 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new b0a9c13678 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 32fb1af0eb 235: onsuccess: #2483: 1: Success after linux: 108 commits new e5a574594a 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 3f519f4557 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new 5c2fcb6613 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 926d66aaa0 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 1947ebc28a 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new ac29713c40 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 66f56f4926 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new aaf78b2dc1 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 8bec84f2fa 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new 9297b8c360 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new fd5b9dca67 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new e856fe449d 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new 113ea3f325 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new f6a839dc68 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 91b4e34e34 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 03300004d6 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 72e7df5800 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new c33d0f0d9f 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 41e851b256 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 96bed6ef30 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 3e8b7c0751 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 09faf9673f 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 979918d809 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 59f93a3c4b 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new ed890a0724 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 598ff0afeb 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 8d729fc990 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 1a00614d53 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 6d98939c8a 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new e47b230023 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 57b1489b90 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 869fb5581d 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new a12a9a9c70 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 943e8a0b34 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 695b875e54 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new ec08c4b39a 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new efe671b562 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 0c481f552e 273: onsuccess: #2521: 1: Success after gcc: 2 commits new a97e522347 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 587f052e27 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new ebde2eac77 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 23f05598f6 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new d9c8913350 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 721977fa41 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new a488bc08a9 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 369695ca19 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 3a3a588b92 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 386ce745ec 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new caff733522 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 122b21040f 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 00d1c859a0 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 3661f3ca7c 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 5a33469e50 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new c7fdcfe453 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 0890deb4d5 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 5a94abf07c 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 9d186bfcd4 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 7613e36436 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 0f5b059753 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new e7c5269cff 295: onsuccess: #2545: 1: Success after linux: 10 commits new e5f26b3d5f 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 692b34ae1d 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 4e75d489b2 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 51125f8419 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 4ac7519304 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 8e86f7eb14 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 4be5e82685 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 6af9297eef 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 9cc7fa0841 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new dc13e2309a 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 6c39dfa832 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new cff16636bc 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new d18800d881 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new cf720a3d5a 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new b573a8b69e 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 5de06dacfb 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 5a15daf038 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 67e13d1b10 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 472a201c3e 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new a8429f2fea 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 9a2ebea298 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 48b1448074 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 32a34f6487 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 6dc2677b7b 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new b7705b0cb5 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 7be8e1c439 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new c444f930a2 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 9ac356a1c6 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 15c9255879 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new cd8301ad37 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 072a4cf006 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new b14237fe36 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 28b8f03d15 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 07846d82e5 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new b633ac8ee5 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 4804468513 331: onsuccess: #2581: 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 (a2416efdce) \ 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 1824 -> 1848 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 32012 -> 31848 bytes 04-build_abe-stage1/console.log.xz | Bin 73000 -> 73304 bytes 06-build_abe-linux/console.log.xz | Bin 9416 -> 9456 bytes 07-build_abe-glibc/console.log.xz | Bin 245240 -> 245208 bytes 08-build_abe-stage2/console.log.xz | Bin 204316 -> 204288 bytes 09-build_abe-gdb/console.log.xz | Bin 39356 -> 39340 bytes 10-build_abe-qemu/console.log.xz | Bin 32520 -> 32028 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3928 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2748 -> 2956 bytes 13-check_regression/console.log.xz | Bin 5576 -> 7176 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 13 +- 13-check_regression/mail-body.txt | 67 +- 13-check_regression/results.compare | 51 +- 13-check_regression/results.compare2 | 77 +- 13-check_regression/results.regressions | 51 +- 14-update_baseline/console.log | 64 +- 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 | 69 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 51 +- sumfiles/g++.log.xz | Bin 3413788 -> 3418648 bytes sumfiles/g++.sum | 28 +- sumfiles/gcc.log.xz | Bin 3032036 -> 3039624 bytes sumfiles/gcc.sum | 4762 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1042324 -> 1041652 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214748 -> 214804 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429012 -> 429892 bytes sumfiles/libstdc++.sum | 12 +- 43 files changed, 2733 insertions(+), 2574 deletions(-)