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 6f629834fe 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards e2f3454492 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 8ca65b601b 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 9a3437c20c 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 471877307c 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 2d9547134b 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 71dc9e2471 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 46db13624b 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 3ddd60fb5f 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 8907d71ce1 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards cfc9cd0a03 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards b16d9afded 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 8594c7f266 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards c3e379898a 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 65690d9c48 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 0d82c53eaa 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 6b233fb265 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 8e8febf81f 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 3f764e2a41 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 547dd6323c 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 980b7c2b99 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 607c04e9a3 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 64ae96ce91 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards c71e93c1e5 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 9550713da4 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 4b62b63188 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards b29de23bed 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 63380fa55f 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards a50e2b36c4 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards cc0edd5484 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards e40fed89e1 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards baa769ea1f 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 6c6f4e7398 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 2c1c1ea389 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards db2aa9d298 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 9ab341c9a6 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 717ab629ac 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 0e0e3aa507 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 333bcebe7b 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 273be05a50 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 27babdf080 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 699dd419a9 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 009716124a 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 5b23cc49af 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards f844ee9e4c 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 90fe0e9a60 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 99b671002a 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 6244234a02 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards de13d8374e 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 85a9906965 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 60168f6f7b 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards c6b5af2aed 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 955cbb6c60 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 2021795ba1 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 710ca800df 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 0f0a0aadbe 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards c69ba3e65c 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards c3842a8a61 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 338957461e 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 24ecdc78b7 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 7fe7a731d5 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 2309caac43 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 0d9f321dbe 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 431d095df0 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards cf8860fb25 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 737f785987 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards d09d6c3880 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards e91a1481be 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 186d1ae708 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards b1a6c9916e 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 7fdf4c0f11 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 4392d893e0 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 63127a6d5e 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards d16b1026c3 295: onsuccess: #2545: 1: Success after linux: 10 commits discards ac90e6614e 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 85a3b2ea8e 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 6d6421a2ec 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards d7c113b087 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 92c0ae3834 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards bdaa384fcb 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 818c19e133 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 9e1df0d334 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards df167ff6df 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards fce27e171d 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 9242130a2a 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards d09ea8c13e 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards b3cc646dde 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards cd21c5a54e 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards cb7833200d 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 844de7f97c 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 53c802b6b1 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards fc13d16ba0 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards de9dc1e066 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 4f52e281ac 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards ac01d1584f 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards e978683d27 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards f028bc5624 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 58c4da79b8 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards bfbde87326 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 4a5757e62c 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 2b57602293 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new f4788e424d 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new ff3ba10eeb 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 385ab3e570 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 12f8899009 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 0d1b515fcb 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 0a8b1e50f3 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 36953eb94e 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new c0dcbdce73 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 1c797b29ef 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 1b5deca06b 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 661fab085f 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 0ecba82fcb 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new e86841b43e 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 5961c77f43 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new d0cae7abd2 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new da052af5ef 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 713b493121 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 5aae42b024 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 2629080516 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 1e0841c99b 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new d1d3b7173a 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 051f81b5be 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 7936eab09b 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 0347ff903f 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 530308c54d 292: onsuccess: #2541: 1: Success after binutils: 13 commits new b9f00ca90e 293: onsuccess: #2542: 1: Success after gcc: 5 commits new ff27411661 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 61c76d63eb 295: onsuccess: #2545: 1: Success after linux: 10 commits new 5a867fddb5 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 1bbff376bb 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 3ee9229fbd 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new df6d7442e2 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 350f7af53d 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 5a008fda6c 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 9982b29128 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new a45cd1ac11 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new e7de97466c 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 5f3cb4ac2f 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 5d1789fe25 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new cb91938200 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 5a0e484dc7 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 453830314d 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 586bc67cf3 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new ca5e252dd4 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new e2cd800978 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 63b01b6a63 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 01ae26c5e9 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 6573b006b2 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 3875768d2e 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 375a6dd468 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 91ae3ed4e4 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new f4f18500d6 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 6834c0a04b 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new fab0a18188 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 49d2eb8fce 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new f82812170d 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 3481a2e360 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 242b0dfe62 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 26a57542d8 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 98c06ac453 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 1da78f7dc8 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new a8d242618a 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new e3d497a56d 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 123e107e05 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new f5cf068bdb 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 565d899c46 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 07ff51f539 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 3ee7786bf5 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 7ad5cf9526 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new edc8bd01cf 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 130833bea7 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 5b6958bc9b 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new eb80eddef6 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 76e2042b77 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new c33336fdb0 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 8459954488 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new e50b37e6f4 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 8e42b43e75 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 9cab9552d7 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 8d66656e40 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new d3ef8b1e63 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new f3ea8cfa8c 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new a82ca793f4 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new d7c72cf316 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 1ef4db6da8 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new b3df7f459b 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 0a3edec1ea 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new ad02b83a4f 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 424ba5978f 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 3fbe6e8282 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new eeb13b34e3 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 7a6b8ac233 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 1de8e4ab16 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new defc441f25 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new c9d28b35c9 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new e1fb6a7c71 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new d00bc22b31 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 7638364cad 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new a82a89735f 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 25d7f1d8e1 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new abc91b79de 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 9f9fd0c3b4 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...]

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 (6f629834fe) \ 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 1820 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 31404 -> 31572 bytes 04-build_abe-stage1/console.log.xz | Bin 74484 -> 73388 bytes 06-build_abe-linux/console.log.xz | Bin 8740 -> 8800 bytes 07-build_abe-glibc/console.log.xz | Bin 247580 -> 247584 bytes 08-build_abe-stage2/console.log.xz | Bin 206940 -> 208084 bytes 09-build_abe-gdb/console.log.xz | Bin 39272 -> 39152 bytes 10-build_abe-qemu/console.log.xz | Bin 31260 -> 32196 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3952 -> 3940 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3460 -> 3088 bytes 13-check_regression/console.log.xz | Bin 7504 -> 7408 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 20 +- 13-check_regression/mail-body.txt | 92 +- 13-check_regression/results.compare | 44 +- 13-check_regression/results.compare2 | 218 +- 13-check_regression/results.regressions | 44 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 94 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 44 +- sumfiles/g++.log.xz | Bin 3414424 -> 3402432 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 3018416 -> 3023416 bytes sumfiles/gcc.sum | 4381 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1037712 -> 1043224 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 215000 -> 215176 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2652 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435884 -> 439400 bytes sumfiles/libstdc++.sum | 173 +- 43 files changed, 2596 insertions(+), 2678 deletions(-)