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 be13f2aa9866 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc [...] discards b9be8c349c3a 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...] discards a5c0d7a1f067 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] discards 034998545881 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] discards 54148bc5dc09 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] discards 441728d6c4a0 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards a181683218b7 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 535dd3558404 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] discards d8de88511f07 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] discards c351a9120130 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] discards 5f2a6aac5106 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] discards 025a6e8a015d 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] discards 2fe9ec9b2cb5 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] discards b673af039494 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] discards 955f7d139512 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] discards 942f774c4937 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] discards ab473055725b 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] discards bea06e2d4b23 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] discards e4338b3d9e7d 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] discards e2696a342886 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] discards b2de80d90a01 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] discards 7bee930dfb5f 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] discards 469b052efee7 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] discards 9355ec31a89c 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] discards b0f4bd4ec988 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] discards 6174f58f4a8b 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] discards 3ee454a94467 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 7a9a36c3e0cd 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 6c7cb4c1ad3a 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] discards 154bf4888b9e 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] discards 36155c1568d5 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] discards 8ec1bea3978a 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] discards 967b33037cf3 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] discards 99c8883710f7 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] discards a6c61694ae4b 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] discards 74eaa9fee734 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] discards 3927f6efd055 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] discards eda2be0082fe 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 7c0daa3fd839 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] discards fe4adff0130c 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] discards 82d58a9f9269 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 4519c9e75bb1 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] discards 9a899d7e031b 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] discards bcb21ad975f7 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] discards 5c21db3b32ca 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] discards 4f435973c7f0 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 7fcd2d386df6 212: onsuccess: #2022: 1: Success after linux: 3 commits discards a5cf8801b151 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 0c200bd26576 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards f9ed18389a03 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 415d902750e3 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 5e7f83ddc8fa 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 01cf95ca6db1 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 0e9217761a76 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards ef3d72fc08e5 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] discards cfc8df138a01 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] discards ee0e1972d736 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] discards 24182b270edb 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 1f9249ef7bf5 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] discards 96a99b9e88db 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards f423f96db3f0 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] discards 857767816d7b 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] discards 4374d6db0d9c 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] discards 8aee78f25145 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] discards 68b463337535 194: onsuccess: #1995: 1: Success after linux: 517 commits discards c75f6526e644 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 17e162ccb739 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] discards ab3261a100ce 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] discards 751aee728426 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] discards 1c66d5483cda 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] discards dfca55204459 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] discards 58e7978b4fec 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] discards 8997dd64a562 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] discards 7a6e49197988 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] discards f2d684f883b9 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] discards 48d81d659860 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] discards a54962c26825 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] discards a4525588ff3d 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] discards 4d95e1873cb6 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] discards c760ee2f1ee0 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] discards 1f03eebaa63a 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] discards 8e0b461d611d 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] discards e52ff5a40d9c 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] discards f85d51b7be04 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] discards 74a2f38afb8a 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] discards c4d6fcd741a6 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] discards 2bb7da1713d6 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] discards 70ac5c540f8d 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] discards 1b85a6d3401e 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] discards 07f95f11629a 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] discards 87aeb29cfbb4 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] discards 2f30cd7952f5 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] discards 3bcd2ddd2168 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] discards 782b0a861c57 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] discards 557aed00de7d 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] discards 8fe70621c913 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards f1caab26f946 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] discards fce60882ba06 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] discards 087e521abf37 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] discards 949297093f44 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] discards 13f8efdce9c3 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] new a9dd4ed84202 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] new 50abdef8b610 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] new 925598e5b0cc 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] new 89c88611a776 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] new a0b775abee50 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] new 661e9550128d 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 56806be7fadf 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] new d5d3a583cdc5 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] new ec2eca1db91a 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] new 2432845cf3a9 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] new 7750bc557dde 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] new ccff34bc4113 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] new 1c245d26aef9 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] new b36a51a7be75 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] new d9e1e5cd602c 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] new 59ea962a99ac 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] new 0343a68be702 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] new 9ca968367ac6 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] new 4203b64349c6 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] new 46a3b73a0b25 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] new 1ee287007077 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] new 811d9781bcdc 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] new a5327f367c51 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] new cee563e223bd 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] new b78301c6089b 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] new e1638bd62ec9 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] new 0fd180ac307c 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] new 9155d2e68441 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] new d519e36770cc 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] new 2da90d2cbbb6 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] new 257e6318f309 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] new 2ed4e3d6d383 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] new ad12d701423b 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] new a398ecaf17fc 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] new 0f963bec040f 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] new 3406e032c13e 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 55003b2a4b24 194: onsuccess: #1995: 1: Success after linux: 517 commits new c44dbf542d76 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] new abab124cba0c 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] new b94750a92a1c 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] new 08f8eeb843d8 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] new 98d176fea4d8 199: onsuccess: #2000: 1: Success after gcc: 5 commits new e7f1a35e112c 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] new d9f21da9bf83 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new a2f7fbd65375 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] new cd9faffc05e1 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] new 9701d4e6cb74 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] new 357683dea84a 205: onsuccess: #2006: 1: Success after gcc: 3 commits new ae951f1ffe1b 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 2d9fd9e35281 207: onsuccess: #2010: 1: Success after gcc: 4 commits new d4ec44fc8cfc 208: onsuccess: #2012: 1: Success after linux: 12 commits new b6d91da0d94f 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 019c44871c8b 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 4f923f59f79a 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 7bef72682981 212: onsuccess: #2022: 1: Success after linux: 3 commits new 1647f309a47d 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 1fd6eb87ff19 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] new ac3fbc0d92a8 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] new 560dd825c6ab 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] new f0b498d9f57f 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] new 1939bff4e140 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 4f864f668bbf 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] new 256e0ec25c60 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] new fb3e66a31bd5 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 637d5bb1f8c3 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] new 4a8dd1ca247c 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] new b13697bed9c6 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] new 01915941f1c4 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] new 7edd4b6f7747 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] new 4bf2e0a29324 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] new 752eebce39df 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] new 3480cfc75117 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] new cdacd23979a8 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] new 1e9bf349a003 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 73fc28cbb871 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 7c745c8d7e17 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] new 93ed29067ca1 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] new db244503737a 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] new 5358f667dbff 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] new c557435935af 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] new 874c93321800 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] new 7e37f47033f8 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] new bd8e8d8cb1b6 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] new 9d75e0ae3f74 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] new a722e288d49b 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] new ab8c7df5b724 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] new 856e94fe7779 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] new b04173afbefb 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] new 3e6133dedcde 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] new 4c887918c58f 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] new 5f6afb469207 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] new b856c117c280 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] new e72adad598ad 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] new 9eea6e775e2a 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] new 490b35b0e014 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 375c696b9f02 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 92f5218f843c 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] new cfd6ecccf7c6 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] new 949058c360f4 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] new 0454463ba832 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...] new 45de8557f27f 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc [...] new 2a10bca4282a 259: onsuccess: #2075: 1: Success after glibc: 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 (be13f2aa9866) \ 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 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31684 -> 31592 bytes 04-build_abe-stage1/console.log.xz | Bin 91740 -> 91344 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8608 -> 8624 bytes 07-build_abe-glibc/console.log.xz | Bin 235356 -> 235176 bytes 08-build_abe-stage2/console.log.xz | Bin 224640 -> 223572 bytes 09-build_abe-gdb/console.log.xz | Bin 39116 -> 39020 bytes 10-build_abe-qemu/console.log.xz | Bin 30700 -> 30624 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2500 -> 2496 bytes 13-check_regression/console.log.xz | Bin 5628 -> 5192 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 26 +- 13-check_regression/results.compare2 | 22 +- 14-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +- sumfiles/g++.log.xz | Bin 2682104 -> 2652856 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 2239132 -> 2271756 bytes sumfiles/gcc.sum | 2456 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 894480 -> 895224 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213912 -> 213848 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 429744 -> 427352 bytes sumfiles/libstdc++.sum | 10 +- 37 files changed, 1394 insertions(+), 1454 deletions(-)