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 20d76ba3f8 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards a7d683fedc 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards f966944d49 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 04474854ad 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 417d20d9cc 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards a98e1d41c8 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards fd2176a8f9 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards a6d1643df1 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 1a7929c3b5 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 535c9adcea 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 872480bd2f 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards f560580368 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 55c7d8b8f9 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 9cfb2e8e37 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 285df86f44 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 7a61c42b91 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 786401a727 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 65995b1b54 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 5f499d1a70 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards c8cb704f5c 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards e36e67b94b 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 7b997169b7 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 93f2923f18 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 1fd88243c7 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards f1eba7e327 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards b1ee6d5608 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards fa0df10c19 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards dbcc4ace74 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 5ded4d2528 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards d7a00464a5 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 1edb592498 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 432f350bb8 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 3c90f5e8af 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 57bfcf7dfb 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 9589a00c31 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards eadb72503d 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards a8aae2fb02 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 7f81349a67 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards f31b6c1a79 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 03a652974c 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 22d6651bf6 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 9306245d0b 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 5095dd92a7 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 5bb93b77ba 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards eb549702ad 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 81b5233ebe 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 6e224965d6 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards b8abf31f0a 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 5101d7850d 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards dca0665df0 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards bcf31706d5 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 5114b6f754 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 52cc56b10c 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards f3fb91cacc 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 3c6e956a5c 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 3b20a3fc9e 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards a7bd416270 295: onsuccess: #2545: 1: Success after linux: 10 commits discards fff805ddef 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 22c834d466 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 45d4bc4d08 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 8a26ef175f 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 88d33189f9 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 6467057013 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards db069737c7 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 6d0cd45328 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 366f6b14e0 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards d6b18ec2ad 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards a5e2d7e411 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 0b94e20b2e 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 3fafb0c6bd 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards ee1d56e079 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 8735c0d080 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 0997819d77 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards dc81ec32ad 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 9aff2f9a97 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards d436986042 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards af94251a9a 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards f3f467624e 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 6aec412b3d 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 7e535dc497 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards efcfaf1689 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 56ed2e47c8 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 7b83ea5ade 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 8c03cd43f3 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards f991ae8b06 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards c8b5fc93f8 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 03c6a622a9 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 0e9b0bdae7 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 9411cc2db4 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 1c1ff13762 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 8946efc2b1 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 29a64d4443 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards d3c24a9f06 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards fe964ffa65 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 856963efa5 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards a23fe35794 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 217a92605f 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 32dc11fed8 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards f6529c545b 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 800076c187 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 42d83b60db 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 03681a273d 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new e12c6c796e 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new bf10407f8c 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new b13814db93 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 72494d5428 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new c0f969a1e3 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 6cc57232c8 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new a87b74f1c4 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new bd386fcc74 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 4711ffc0e7 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 4811e710bf 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new e255433428 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 295d277ae1 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new e90262b75e 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 39620725aa 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new dfea561210 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new abcae22f10 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 148b888094 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 732e2810a2 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new a65dc9b2b3 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 32160a7555 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 16f5750ce9 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new fd8c033e69 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 2b8d73cd7b 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 46b170a144 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new c597aac9af 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new bfd520cd07 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new eba72401cb 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 925f71773a 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 4495d4b51b 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 7032b4a1ab 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new cb8675782f 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 95809c9345 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new d6845f8b51 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new e58fe9f358 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 2b9ded8002 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 4fb9ca1cde 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 7891c5a379 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 275afc7be5 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 145bc9352a 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 9d5137a181 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 7f0959d3ee 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 3707e57b74 293: onsuccess: #2542: 1: Success after gcc: 5 commits new c020c887bc 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new d3143e6edf 295: onsuccess: #2545: 1: Success after linux: 10 commits new bec9a76a8d 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new e9b735e5e4 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 1e68c5d083 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 4ddb56a0b4 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 9f35178550 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 495b8edac9 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 1443a0de3d 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 5efd869994 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 03823c29e5 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 1d615c2e12 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new f446160e7a 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 6b8e80b7c3 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new dfbab32cc3 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new cca42df9f3 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 7302d2b9e9 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new acc811a0b4 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 9a443b0873 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 5712af4399 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 576d3d9347 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 3dacf4340e 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 66ad06a2da 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new cb4a02c161 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new f179042df7 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new cab2833ccb 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 027006a1fa 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new a8b83e7b3f 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 6551aba402 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new b23e761471 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 7306de64ed 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 986199c881 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 3198f291fd 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new dcfb9157a7 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new d0b0fd7a6b 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 591e9cfaaa 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new a141b52cf9 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 35e2eb3726 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 000931545a 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 65c7891bbb 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 0917cbf99d 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 4ff0effee2 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 273e0344f3 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 4649a61e50 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 6297c8f119 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new e924f364a8 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 1cb80c7823 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new a12f968c60 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 4254daa50f 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 639a599205 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 6f70320796 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 13275291f7 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 0c47a9c1f4 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new c34f771b2f 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new fa89a7d132 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new dfd9b39c5c 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 3b8766eda8 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 96c08aab31 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 886d621b71 352: onsuccess: #2602: 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 (20d76ba3f8) \ 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 1764 -> 1820 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 31552 -> 32012 bytes 04-build_abe-stage1/console.log.xz | Bin 73720 -> 74300 bytes 06-build_abe-linux/console.log.xz | Bin 8924 -> 8592 bytes 07-build_abe-glibc/console.log.xz | Bin 245984 -> 246456 bytes 08-build_abe-stage2/console.log.xz | Bin 206280 -> 206928 bytes 09-build_abe-gdb/console.log.xz | Bin 38904 -> 39184 bytes 10-build_abe-qemu/console.log.xz | Bin 31800 -> 31972 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3952 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2812 -> 2732 bytes 13-check_regression/console.log.xz | Bin 10432 -> 10352 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 12 +- 13-check_regression/mail-body.txt | 207 +- 13-check_regression/results.compare | 125 +- 13-check_regression/results.compare2 | 390 +-- 13-check_regression/results.regressions | 120 +- 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 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 209 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 120 +- sumfiles/g++.log.xz | Bin 3403384 -> 3407012 bytes sumfiles/g++.sum | 33 +- sumfiles/gcc.log.xz | Bin 3005192 -> 3000836 bytes sumfiles/gcc.sum | 4771 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1036432 -> 1041944 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214752 -> 214780 bytes sumfiles/libgomp.sum | 8 +- sumfiles/libitm.log.xz | Bin 2656 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 432780 -> 431788 bytes sumfiles/libstdc++.sum | 47 +- 44 files changed, 3149 insertions(+), 3027 deletions(-)