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 f840a528fa32 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 26c4989b2e04 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] discards fcad6616defd 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] discards f8838cfeabfc 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] discards b8f6a463f078 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] discards e52b57644e10 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] discards 29e746669f19 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] discards bf6832f02f9d 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] discards 6e3075945124 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] discards 683d914bc1be 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] discards 311abb663b41 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] discards b489863d65e9 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] discards 37050c199b4f 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] discards d90a6788ddd9 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] discards aadb0ae80b1e 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] discards cfdc85ad54a9 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] discards f10e5e8bef7c 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] discards d9e9f77d378f 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] discards 5e38ad174635 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] discards a8e5eb9d5164 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] discards 8801a8d4facc 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 6524a25c318b 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards e8dce1b77162 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] discards 44883dd9d1f9 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] discards e666c235b757 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] discards eff05c96a5ab 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] discards 9299e28e3500 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] discards 1bbb5609ac0b 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] discards 15f2a8915d7f 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] discards f957991ef869 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] discards e8fd22884bcd 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] discards 16eee2d5703a 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 95bd9a524aad 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] discards 7928fb134708 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] discards 6ecefdd5123c 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 1a2bf7be04c9 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] discards 0a19db511eba 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] discards 5f3eb0304257 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] discards bab0dfe0f1bf 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] discards 37b62891a7e8 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 7e0d2a8608ca 212: onsuccess: #2022: 1: Success after linux: 3 commits discards dc0aef085c0d 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 1a8906ff453b 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 4aa4992b6d83 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards c1d81de49ed6 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 5b99b2b715af 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards dec28a40197a 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards aa9d5cca3912 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 1388bdca6c14 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] discards 8c41bae8e439 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] discards de503396a72f 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] discards bf0ab222ed5d 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 5abdb3af6d2b 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] discards ce421ad064b3 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 9d2a8e36b560 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] discards aab7bd521201 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] discards d6868e7f3c93 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] discards a8e45411d150 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] discards 84012412be6f 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 71301cd2ed51 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 67913b210da9 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] discards 3f3867834569 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] discards a6fcd4da26ad 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] discards c44ef668a45b 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] discards b0c3a0c699eb 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] discards 83b9850e6220 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] discards 31cf82168abd 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] discards 3f7ad481f49e 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] discards 78f7717c4265 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] discards be29aba3f629 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] discards beb812d5afc7 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] discards 684089eccf38 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] discards 44c70c688d7e 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] discards 0d430d9f564c 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] discards 715836774602 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] discards 034bd10a2231 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] discards fffd73fced57 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] discards 3546426d4a7a 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] discards 3c6572b82358 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] discards d75a7df17d9a 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] discards 0cb8ee45d8c1 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] discards decf4d049479 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] discards abae20cd89a0 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] discards 2a3d863f12eb 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] discards 5119ff0e004a 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] discards 98626fb68c92 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] discards 859921c99eb8 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] discards 44aeffb47036 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] discards e33c89f54d3f 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] discards dd5e0f240d0d 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 704e05d3f839 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] discards 52584aad57ee 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] discards a7ed9a61b638 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] discards 582778c4ff7d 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] discards 18c9b043161d 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] discards 885c3b3448f3 157: onsuccess: #1758: 1: Success after binutils/gcc/linux [...] discards 73fea962bd36 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 4c447dddff49 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc [...] discards 99ac52e8f172 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards adf6561ca92b 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 1876211bed14 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gd [...] new aa51ae028c82 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gd [...] new 6c65e9a723cd 153: onsuccess: #1754: 1: Success after gcc: 2 commits new f29004dbcd84 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new bacf771f2814 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc [...] new 330cbf76158c 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 208afc47f418 157: onsuccess: #1758: 1: Success after binutils/gcc/linux [...] new 77f603456480 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] new 678d8b9459cc 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] new 0f81ce12a626 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] new 1e766bd2642a 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] new 6a4d46a935d4 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] new 15e2b147a636 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new a240176bcdca 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] new 6bc5062a60a3 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] new 33974e92b21e 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] new ed40133b2fe2 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] new 69e957a4fa50 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] new b682642e0f2e 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] new 716becf2f3b0 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] new 824443d1fe66 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] new 3e1ea3e53654 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] new 3ea09f035a7d 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] new b5f75b47ac38 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] new d249fc4c145b 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] new 8d2a84410afb 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] new 8c08414840ce 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] new ace8f0c0ab98 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] new 26fdd5fff464 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] new ba8e662d2273 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] new f0d025a63bd3 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] new 2d2a99aa1b16 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] new 543ca4f78032 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] new c845c0099ada 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] new fb319bdd598e 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] new e26a19959d47 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] new 9c2b985458ff 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] new 888146eb438a 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] new 21276550072f 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] new f4e8928ccef2 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] new c712b46b4db1 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] new 2483afd4d0bf 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] new a3f6ee86dabf 193: onsuccess: #1992: 1: Success after binutils: 151 commits new bcc0bb771a77 194: onsuccess: #1995: 1: Success after linux: 517 commits new d78d6cbc4a0b 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] new 7a67d7143a8b 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] new 9d8473b46862 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] new ed52fb2c4875 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] new 5ff8c86a0c3c 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 2cc63c740301 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] new 8215fef5e7aa 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 150c3888f763 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] new 2b33ef6fff4a 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] new 3f6862b9c732 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] new 73a74fd83ff2 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 8a484e746ab1 206: onsuccess: #2007: 1: Success after gcc: 2 commits new db9b19fed4a0 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 9596a9e6fa2c 208: onsuccess: #2012: 1: Success after linux: 12 commits new 7fdc696b4a51 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 185a65fcb2a5 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 016fae10e818 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 2b0e838e13cd 212: onsuccess: #2022: 1: Success after linux: 3 commits new 8bec4ba18d93 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 748a54491e62 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] new 0c88804be871 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] new 743174f7cf1a 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] new 7aa20fd80267 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] new 895ad9a90ebc 218: onsuccess: #2030: 1: Success after gcc: 5 commits new fa1b148d270b 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] new 5aa37b3ae15a 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] new b8b0e5dafd7e 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 2a33fa61725d 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] new c1d057c6bc9f 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] new 51fee33944c9 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] new ba8943ef2fe1 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] new 7bd6260db639 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] new 080e60c14d81 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] new 2826b0d99638 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] new 49392e00875e 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] new cbdc28f27a79 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] new 0e1139234b5f 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 0507f889671d 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 78cf9d505909 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] new e9e9571d025f 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] new 262c330b3362 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] new bc80da2e762d 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] new 298f4847faee 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] new 710a8c13e29a 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] new 5ec05c0d1daf 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] new 60b7c4d518c9 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] new b97cc3dbc1aa 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] new 78a2ba414027 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] new 4e2dee2c579c 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] new f162822aae55 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] new 7f639cdb371e 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] new 7b8168b0cd39 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] new 3da8d17dec44 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] new 4020745159dc 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] new 781376baff9a 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] new 04c242880981 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] new 27ce5776a03d 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] new febac8759620 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new dcf5658e28f9 253: onsuccess: #2069: 1: Success after gcc/linux: 109 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 (f840a528fa32) \ 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 1760 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 33040 -> 32500 bytes 04-build_abe-stage1/console.log.xz | Bin 92368 -> 92416 bytes 06-build_abe-linux/console.log.xz | Bin 8720 -> 8640 bytes 07-build_abe-glibc/console.log.xz | Bin 237064 -> 235908 bytes 08-build_abe-stage2/console.log.xz | Bin 226844 -> 226696 bytes 09-build_abe-gdb/console.log.xz | Bin 39636 -> 39608 bytes 10-build_abe-qemu/console.log.xz | Bin 32012 -> 31632 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3924 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2776 -> 3108 bytes 13-check_regression/console.log.xz | Bin 5572 -> 5800 bytes 13-check_regression/mail-body.txt | 27 - 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 59 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- sumfiles/g++.log.xz | Bin 2693360 -> 2658392 bytes sumfiles/g++.sum | 47 +- sumfiles/gcc.log.xz | Bin 2253092 -> 2246692 bytes sumfiles/gcc.sum | 1768 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 903352 -> 915388 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214072 -> 214012 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 439660 -> 440516 bytes sumfiles/libstdc++.sum | 8 +- 37 files changed, 1022 insertions(+), 1058 deletions(-)