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 78ae2eff09 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards ba4c3c8cfa 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards a1b0105028 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards d32127812b 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards bf7743aeb9 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards dc5d3feda0 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards f7391351b1 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 574e54dcd3 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 513722c5e8 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards d91eb14564 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 663e6e6407 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards c9f3709828 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards ab7bd417c4 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 277d7b46f5 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 24f27c2c89 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards cac1caa261 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 9dd0848cbe 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 0c9c1e933f 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards c9589e5a5c 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards f706c97b09 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards e16dd1e228 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 9f5da206f3 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards d7b97ae2f9 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 059b6850e4 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 0584e0b1e9 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards ee82fdca43 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 90a4656b21 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards c73aa74ad4 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 26a613e4ec 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 2e3a3eba60 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 79d1c4df22 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 2925bd0bd8 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 20aaafe371 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards bfa2bd4699 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 8c68598791 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards c5a80539ce 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards dfc924a612 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 6de5dba534 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 9b6f42460b 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards ead40c5332 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 9aba929908 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 0db33d68fc 295: onsuccess: #2545: 1: Success after linux: 10 commits discards a4a4455796 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 17d1420638 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards ee7df058f5 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 740995a93c 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 7f80bffd89 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards f11e4bd850 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 77db83544e 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 8d0d2e9565 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards bffdbd4b70 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 0211ec041e 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 87eb233f5b 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 52263ac7fc 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards bd88715749 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 48233a0a54 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 72f2d8fc0b 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards e6acc3ffcc 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards a7cc87ac4d 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 63fae85da4 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards f95f060276 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 1f0c95360b 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 96abe7da29 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 11b987768f 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 29ea24b459 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 0c2943e2a4 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 063fd898b6 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 6087cf22d2 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 9bfe05733a 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards dd26013306 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 47fa4aa0ac 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 9383c4cfcb 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards b30b3a3c41 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 68d4ddda30 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards e15ee828c1 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 9596106cb3 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards c5c2c7066c 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards a5e58530af 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 16fe00ab38 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards b396d2dba7 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards a3f07465fd 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 76a276deb7 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 199163498b 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 2f6eca4523 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 0620c3a31c 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 8075e08de1 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 48ca287750 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 8ccaf322d2 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards d26e1e64ca 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards c784262ed8 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 1a35bc7569 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards c176390db9 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards b83104d2f7 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards d6887e48df 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 37abbe17b5 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 6d51db07b4 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 8e1bec74cb 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards cc33d6a555 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards b2c0fd7763 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 1f50b5f9ac 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards c99fdc63d7 236: onsuccess: #2484: 1: Success after gcc: 2 commits new bc932c8fd7 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 9028f7e360 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new 0df449ccdd 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 6a311518cf 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new aaf30ba5fb 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 0256c789bb 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new c68ea632f9 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new 0f6bfb5666 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 9aeab038ba 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new 2eda285396 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 167e925572 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new db49320755 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new 72a068fac1 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 71b39bb08e 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new dcaa174298 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 6ad7e3b8cd 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new e9396644d8 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new da3a571654 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 0064169ffe 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 23cb369445 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 666bd5a19c 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 2d4f401eb0 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 623853804c 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new aa250a9e49 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 7665c2008e 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 5c427550a5 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new ef93251299 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 8e27e95551 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new f6fcb82531 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new db578093f4 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 1d1d0c9ed5 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new be4da7ee47 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 2c9bbfa093 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new db9e26347f 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 9b24ce4d8b 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 6e76565a76 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 7811a8aa13 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new e1329c2637 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 883e1319c4 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 88e0050fdf 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 204ad9dbbd 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new ee42bd3111 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new ea8eac640e 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new d35ca24184 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 3512e93078 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 539169f31a 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 75d90abd0f 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 3aec3908ee 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 5a3fb2a580 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 0c782363d6 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 84233200cf 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new a14c05754c 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new c0c09d89f4 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 493b8f2eaf 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new ec056261fb 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 63eeff1ede 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new bb44803da3 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 97bca52a9c 293: onsuccess: #2542: 1: Success after gcc: 5 commits new f5c1fbe5ad 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 8c1cff074e 295: onsuccess: #2545: 1: Success after linux: 10 commits new ccbc56fab3 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 8bb15b5cfd 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 86ca7a4d78 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 75f0bc1158 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new b09f9263a6 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 9920e2bdcf 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 18d2219603 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 73fc4f8b21 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 6c941089a8 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 57c6f108f8 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 115cbc8fc8 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 452ca3e992 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new f7e73fcb09 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new adb4a78e98 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 23a5371bb8 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new e2a1fa9e42 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 4ee4bd64fe 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 7f0b1d6e48 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 0177f61f0a 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 02dc0b41a2 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new c0df59d6a0 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 63aebc8293 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 6c20283c34 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new dd98b60c7a 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new b1f46c90e7 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new e934c21682 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 9c280b8be4 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 0559ac3a72 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 3a935be05f 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 5e05070bd5 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 550d80647b 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 292b41f489 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 769410efc3 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 4f62bf872d 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new bca2449645 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new a55124605e 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 00d39cf276 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 635e57f814 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new c43cc55ac6 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new d1bce3a33b 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 87e11667ba 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new ce1c0e0076 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 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 (78ae2eff09) \ 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 1772 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 31756 -> 32508 bytes 04-build_abe-stage1/console.log.xz | Bin 73068 -> 74136 bytes 06-build_abe-linux/console.log.xz | Bin 8744 -> 8816 bytes 07-build_abe-glibc/console.log.xz | Bin 244968 -> 247112 bytes 08-build_abe-stage2/console.log.xz | Bin 204136 -> 208724 bytes 09-build_abe-gdb/console.log.xz | Bin 39060 -> 39428 bytes 10-build_abe-qemu/console.log.xz | Bin 32872 -> 32656 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3944 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2724 -> 2800 bytes 13-check_regression/console.log.xz | Bin 6184 -> 6048 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 10 +- 13-check_regression/mail-body.txt | 102 +- 13-check_regression/results.compare | 48 +- 13-check_regression/results.compare2 | 62 +- 13-check_regression/results.regressions | 48 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 104 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +- results | 48 +- sumfiles/g++.log.xz | Bin 3429556 -> 3414296 bytes sumfiles/g++.sum | 28 +- sumfiles/gcc.log.xz | Bin 3044636 -> 3046432 bytes sumfiles/gcc.sum | 4266 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1047844 -> 1045752 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214616 -> 214908 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2692 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437092 -> 437976 bytes sumfiles/libstdc++.sum | 8 +- 41 files changed, 2439 insertions(+), 2400 deletions(-)