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 f4d2ee90ed 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards e32f490576 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 68f7345772 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards d04cc64018 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards fcc914b3cb 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards ba6a92911d 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards a65987f9f6 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 8ac37c3b23 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards b5189f6090 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 1c49012b42 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards fe0d124bdf 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards eca0583044 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 9385220a20 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 300ffd6e8f 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 7ce4a2d57c 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards b89734b71a 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 0771057159 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards f5cf46551b 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards dc9a59094d 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards ab3fe36705 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 8b358a390e 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 2b59ad00cc 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards e64d9d5836 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 70fb9ef907 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 45417defab 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards e45fdc2b51 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards fe2e608990 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 51617ffb31 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 1510f2fa7a 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 3ecd1534a5 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards e2d3c70d78 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards e798336b44 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 4546fd6369 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 20b85142b4 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 2a53b91030 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 5f8e536503 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards a188e2c361 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 854dd1b27b 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 01a944e684 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards ebcf8a2d39 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 482ce52fc5 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 8bbcc8d8cf 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 853912d552 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 64c01ab83c 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards db51db1b6d 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 23e7c1a1c0 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 3d3a0ae323 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 5ed5657672 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 3ac18f1f2c 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards b21a74a2ee 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 5fa7ebadfe 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards edc2232799 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards b1da0f0ac9 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 12614b0230 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 079d053194 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 7c8622420c 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 562b74eaf2 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 4dcb6418a9 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards ba5fb3b1f9 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards c71c6887cc 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards e01a75be8a 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards f26ff31b58 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 585392e399 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards fcc0d802bc 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 07645a577f 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 7c47ed20af 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards baa123c4dd 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 8722fb9e8e 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 7640f7003b 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 1260031f18 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 9976a13117 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 4843d92add 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards b1081289f7 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards d9ad4d23fe 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards bd667de9e3 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 555f51e08a 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 0745493f3c 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards b2d656330b 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards e443e09ef3 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 919021bfb6 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards de78142acc 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 4524b5a72d 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 8fff1cea7b 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards c391b00349 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 8a150fbf07 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 800d438018 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 14a680b2a0 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards c41f6f4d15 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards a937327f58 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 59a531fdb3 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 42e84f2228 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards d82dce9e89 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 9f4b59ce32 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 9812576cd3 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 8a05eab104 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards f5c4127112 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 7ebd17d087 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards e981099254 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards f0bc6f2cb7 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 880dd46a00 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 31628b7dd5 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new a9e1718f8f 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new f0bfb92e58 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 631f9efae8 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new cbf9027b82 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 2a527980b5 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 2f6e2c7044 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new ca15d5a1b6 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 0fb075aa7c 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 06aa74f3f6 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 5442919c24 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new f5a3d078a5 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 49b0ec0d5c 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 8e3f4c48c2 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 77ffa0a97a 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 589c1fbea0 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 074b25c275 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 63fea8f6fc 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 5784d1427b 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new a853052d4d 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 78b790033e 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 14dae69f54 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 588ae86700 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 8b06c7f7d8 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 506a48eaac 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 40f1a9ad47 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new affcf1ab85 295: onsuccess: #2545: 1: Success after linux: 10 commits new 1846c044e1 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new b13a9cea5e 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 92e813f8f7 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 13a9ff70ad 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 0d0cb27d9e 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new a418326a26 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 15f5275f17 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new cacf5d5413 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 2e9e6d36f6 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new b1ac837d2e 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 406449b1d2 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new ee50c9aa1d 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 97f3785ec2 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new f8a0352d2a 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 1f38a1f73f 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 1d624ba3fd 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new a675e5dd0c 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new ca6c88f2cb 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 5ffe3feb71 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 207626feae 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new a2e5184471 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 6b50dc40c9 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new ec028de278 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new dbc2c3abe4 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 84750202d5 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new c7ac39e93a 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new f756cb5b29 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 43cf8cf24c 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new f1c0d0c51c 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 9eb6645f8b 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new ba49c48077 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new ee51458f58 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 7e56609238 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new db76eb8568 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 46619932d7 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new cb71c1e61d 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new ba63a30018 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 7624df7d82 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 962e7d3d63 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new cfde84d079 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 9acbefae85 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new d38f88491a 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new a0aa112832 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 69e015e7f0 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new ed1c30761e 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 93b8bdab0a 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 7900493c8b 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 62ce7914be 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 723409b000 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 3b41ffa7b2 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 99756dea51 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new b4b63d4d8a 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new da0ea0b9a6 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 6bea5123bf 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 417cd90fa7 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new c49cb565d5 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 4f6c37dc62 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 54d16f507f 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new d13eb172cd 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new ac6235905d 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new afe57f730c 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 9923b7ec81 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 08f4d230f5 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new f40e67ead4 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 3311096707 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new b3235028aa 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 45c581a310 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new f6b7526ff9 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 778dc3093a 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new b3110e0b84 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 927600f1e9 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new a03c1bc9e8 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new cdcd3b3f5e 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new c13472272f 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new bc87d7e5ea 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 61969173c5 371: onsuccess: #2621: 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 (f4d2ee90ed) \ 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 1836 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 31936 -> 31340 bytes 04-build_abe-stage1/console.log.xz | Bin 73756 -> 73708 bytes 06-build_abe-linux/console.log.xz | Bin 8772 -> 8988 bytes 07-build_abe-glibc/console.log.xz | Bin 246036 -> 247132 bytes 08-build_abe-stage2/console.log.xz | Bin 205272 -> 206896 bytes 09-build_abe-gdb/console.log.xz | Bin 38748 -> 38512 bytes 10-build_abe-qemu/console.log.xz | Bin 32172 -> 32244 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2828 -> 3440 bytes 13-check_regression/console.log.xz | Bin 7024 -> 7468 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 24 +- 13-check_regression/mail-body.txt | 66 +- 13-check_regression/results.compare | 41 +- 13-check_regression/results.compare2 | 150 ++- 13-check_regression/results.regressions | 41 +- 14-update_baseline/console.log | 70 +- 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 | 68 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 41 +- sumfiles/g++.log.xz | Bin 3398328 -> 3407380 bytes sumfiles/g++.sum | 24 +- sumfiles/gcc.log.xz | Bin 3023904 -> 3029596 bytes sumfiles/gcc.sum | 2154 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1038236 -> 1042856 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 215100 -> 215180 bytes sumfiles/libgomp.sum | 9 +- sumfiles/libitm.log.xz | Bin 2660 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435944 -> 437068 bytes sumfiles/libstdc++.sum | 354 +++-- 43 files changed, 1720 insertions(+), 1384 deletions(-)