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-arm in repository toolchain/ci/base-artifacts.
discards a6199e3b0eb 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 4c495910780 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards 0cc2ee1baa5 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards e87d1bdb10f 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards a2e2744b8fa 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards e92084862bf 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards f5602088301 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 25749b4d728 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards 5f75ebc5721 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards 0f38db5099c 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards 0299d6177b1 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards a62c722c5ac 194: onsuccess: #1995: 1: Success after linux: 517 commits discards d9c55935616 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards f83460f38c7 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards c2696205774 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards 91c21c745ca 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards 956042c36de 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards 598e173a5d7 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards 77a23577199 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards 442e16d9a7c 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards e0fe0ecddf2 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards e1845eeb010 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards a42501e5351 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards 0539bb852e0 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards 0fd9a527114 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards 954f542b87b 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards 354f22044c4 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards 0762879ab21 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards 5addbc3620d 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards 6c7b9804ebb 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards e223b346bfe 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards 21bb7e8dcec 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards f1a5770e2af 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards e933bb6a87f 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards 822ab65e0c8 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards 0e6dd9a57d0 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards c15afe65490 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards 664692e4ae3 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards a4294767c5a 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards f1e45e70cdf 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards 65a9940cc93 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards aecb5fb0318 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards 50386a15c4c 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 66d65292d24 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards 9541069843a 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards 2a022636507 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards b72b882c19f 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards 0712f787544 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards b796222fcd1 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards b023ebc96d4 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 59bb54d723c 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards daa945f696d 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 8237a25c5e2 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 194e2feedc8 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards 2f597d1c983 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards b7e49e94564 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards 4a50778a778 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards b33f245a5cb 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards 416fac0bdb4 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards 61ea76cbcff 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards 06a742dc2b5 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards 82e4d1aa8d4 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards bce59fd7791 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards fadb489a2fc 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards 950aad31a21 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards 4adcd620141 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards a43426d8808 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards 28b612743ec 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards 31f1ad2314c 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 30851602199 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards 3a8a16d5e67 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards f48ce9ce1c8 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards fb0b6a2ee76 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards 2c8c0859a9f 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] discards f1d8cbfed26 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] discards 0556e6888c0 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards b57afd2e65d 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] discards 392b73f410d 128: onsuccess: #1723: 1: Success after linux: 12 commits discards e850d19fbd0 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] discards 22831070a5a 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 185e94b8354 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] discards f09b988f96b 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 866041db85b 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] discards 0e21556e7f4 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] discards 94adff5ebcd 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] discards 0bd2115b3b6 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] discards d215436795f 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] discards a5fbf123d99 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] discards a1713e97623 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] discards f258aaf9dcf 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] discards ad3752b2572 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] discards 4f2d7c610a2 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 1472e198a41 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] discards 9572a4ad71f 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] discards 39fc3530a0c 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] discards 53bf5277fcd 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards b54854011b4 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 [...] discards d1e61369527 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 [...] discards 1da6e566b4a 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/ [...] discards 3adc14c5af4 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/ [...] discards a2938eda479 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38edde [...] new 3f9879b6e79 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38edde [...] new fc6ad1c2827 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/ [...] new a9d54348d23 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/ [...] new 797d93dfcda 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 [...] new 10ebece9e25 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 [...] new 80560c18353 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 1916a539526 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] new be042351a60 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] new 293f55dd097 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] new c01285b152e 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new df0e024d3f1 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] new f87c18e7f35 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] new e267fc3a1c3 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] new 1c51d419778 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] new b665504af52 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] new e260d468ffc 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] new 6eb4ca059a5 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] new 0a6c596f16a 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] new f3d8abd3e78 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] new ebd1405f107 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new dd8c0bca243 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] new a57a20f5e3f 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new a1f62f77ea3 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] new 8ecb68491cb 128: onsuccess: #1723: 1: Success after linux: 12 commits new 12e95a603da 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] new d14d7781bf8 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 32f7c567787 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new c2c6ca79040 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new 2df881c22ae 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new 5d83e07b4f4 134: onsuccess: #1730: 1: Success after binutils: 2 commits new af29062985d 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 0a02aacc5a0 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new ab317f72134 137: onsuccess: #1736: 1: Success after gcc: 5 commits new cbf10d472b4 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new 5ed1cbf2260 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new ed280d3cfb0 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new 137391ee91c 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new 3a9a67872ff 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new dedc846503d 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 778906bb6bf 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 422d57710fa 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new 35660647a20 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new 0bb7d5c13f6 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new cbe1d7a2c0f 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new fe1d4c14d8d 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new 3454ec0c9e4 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new 82b10b6ae19 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new 78f8896f5ad 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new be1a4fccc82 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 46d90509310 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 8a1b5d4568f 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new b3c9b2eb5b9 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 63e66e1fbb5 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new 78c9655542a 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new 699c2dca8fa 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new d6d51d15a2b 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new deb851d7cd7 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new ed3e3f50d6e 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new c2a2b36b28e 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 9170fbbf3fd 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new 0126e22b238 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new c6ad8af7a0b 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new 4c8294d8f01 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new 9632556870a 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new 6c56ae325e6 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new a19c0958dd5 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new 52516763861 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new cc91ba1869e 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new 8197145748c 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new dfd00286a6d 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new 52d91985210 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new de32ed5c803 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new dd6022e9d5e 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new edbc33835bd 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new 7fea8274971 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new c8a680496e3 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new b8ffd91fb99 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new 9058843fd4c 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new 7a8d2a09baa 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new 9b803965971 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new 3d56458f535 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new f99e31f5fa2 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new 65e1653094c 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new 169da2d84f6 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new cd1460d1e73 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new 8627c24a74d 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new 1fdf9757f26 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new ecec629462c 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new 697a3635dd3 193: onsuccess: #1992: 1: Success after binutils: 151 commits new abe30d28952 194: onsuccess: #1995: 1: Success after linux: 517 commits new 1f6884d7ef0 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new f702996c8d3 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new 4a571c5b9a0 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new ca67058717c 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new a036fd930e1 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 1fc0af9adb2 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new e6aadb22009 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new d6144d8ce00 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new ab393a23d93 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new 84246ebae5a 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new d0872b8b5c3 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 5b77c210ef9 206: onsuccess: #2007: 1: Success after gcc: 2 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 (a6199e3b0eb) \ 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 1780 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2812 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 32308 -> 31668 bytes 04-build_abe-stage1/console.log.xz | Bin 92468 -> 92916 bytes 06-build_abe-linux/console.log.xz | Bin 8724 -> 8760 bytes 07-build_abe-glibc/console.log.xz | Bin 237144 -> 238580 bytes 08-build_abe-stage2/console.log.xz | Bin 226908 -> 227828 bytes 09-build_abe-gdb/console.log.xz | Bin 39292 -> 38668 bytes 10-build_abe-qemu/console.log.xz | Bin 31496 -> 30300 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2696 -> 2840 bytes 13-check_regression/console.log.xz | Bin 6024 -> 5848 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 8 +- 13-check_regression/mail-body.txt | 74 +- 13-check_regression/results.compare | 32 +- 13-check_regression/results.compare2 | 77 +- 13-check_regression/results.regressions | 32 +- 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 76 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +- results | 32 +- sumfiles/g++.log.xz | Bin 2713740 -> 2713012 bytes sumfiles/g++.sum | 43 +- sumfiles/gcc.log.xz | Bin 2313092 -> 2307644 bytes sumfiles/gcc.sum | 2220 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 898692 -> 892524 bytes sumfiles/gfortran.sum | 70 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213180 -> 213108 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 440292 -> 429696 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 1442 insertions(+), 1338 deletions(-)