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 29d0a92f44 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards ebfd0b941f 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 356c0d6893 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards f3117d9dfc 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 4fe9fa8472 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 798ca2b1d9 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards d29af94752 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 7c117f1bd2 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards f9b025fd5f 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 7de1e4a17c 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 8bf8bbb8c5 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 0c5ea63496 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 4d9acd5922 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 87d9b685d1 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 16cfbc018f 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards f50c674c6d 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 14abef313a 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 5e55b1ad1a 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards d479617187 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 7f6f40ac04 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 826effc9de 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 066afe3807 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 42dca08beb 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards b9feec0a34 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards f777f21c4f 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 703b6cf0ed 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards e819fa7e8a 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 63275c61e0 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards bcbfdc6623 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards e0d4a587d5 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards ea9d753c47 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards e938e69e85 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 9107be7028 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards ad3c0ac206 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 7afdc88a96 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 05f105f3c5 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 9182f61408 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards c56edf6417 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards 3d5061f1b8 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards 5466af668a 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards 971edcef76 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards 2b3505f8d8 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards 67e0764675 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards fd046fc6b3 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards 4ceb3eb46f 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards cb9e599446 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards 4546b94780 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 060b63fa7b 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards d005b87781 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards 2d4a3ac586 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 2b1add5b74 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards 81d7c71e25 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards 75933781c2 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards 5e0a5436b1 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards 4d2981d246 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards df87ccf30f 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 6511e4f295 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 80fa7b4d6f 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards eee1f8b23d 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards e6a9cc15ba 208: onsuccess: #2012: 1: Success after linux: 12 commits discards b9997285c1 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards de9898d406 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards f0f253f447 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards c060b57c08 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] discards 3a56240856 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits discards b968ccddf3 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] discards 269036e19f 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 37e23f833d 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] discards 336f042f10 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards ad493b071a 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] discards e1b7212bd9 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] discards fac2bd3b62 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] discards f7714d9c64 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] discards a9d6c8993e 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 953e20fb8f 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards b3f81c1f56 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits discards 045ea8b830 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] discards 4cc9bce3ff 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] discards 66a7e7cb86 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] discards 4be36f4567 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits discards bef82e5995 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] discards 1b17c323f6 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] discards 03e7f88a25 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] discards 97f9fe93b4 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] discards c507fe7e8b 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] discards f6cbf06549 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] discards 31e0e6e932 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] discards f9676d8520 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] discards 7977406581 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] discards 41ee8bee4c 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] discards 30ca5daf4e 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] discards c60474b68f 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] discards ff33ca1cb1 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] discards b8b5a3a5d7 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards 9765cce09f 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards d8b13a68fb 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards be81b18790 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards bc345c449c 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards b87a9848ee 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards e5902245e6 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards a9516559fe 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new ed14bcd240 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new 61268492d3 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new d2e29553b5 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new 43ea89c0d9 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new 315bd74a5e 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new ebd4773253 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new b4d16a6fac 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new 89030368c9 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new 46dc7af2a2 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] new 18b6c065df 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] new 5dd390a19c 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] new 1a501b4126 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new 32b76d00e7 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] new 0754f30e80 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] new ad157fcc58 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] new 078e08cd98 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] new 6ee6196b4f 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] new d48311b3c1 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] new 511a60d413 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] new 5b65763aa9 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] new 25b1bcaf3c 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] new 5cba1174d0 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits new b7d6168710 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] new 96f47d15d0 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] new 4e17cefeda 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] new 595d4d36b3 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits new 6da6085e01 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 8f8b66a8c1 194: onsuccess: #1995: 1: Success after linux: 517 commits new 5475ae31ec 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] new f20d0bf9b5 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] new 534b8e65e8 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] new 33a82890a1 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] new 6ae83beb74 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 76ec1007a8 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] new de777f1c42 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new b58e28a666 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] new 553ccf9259 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits new 5507ea92bf 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] new 6f861eb43c 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 6129421cb9 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 92b282a3fd 207: onsuccess: #2010: 1: Success after gcc: 4 commits new c27b46e635 208: onsuccess: #2012: 1: Success after linux: 12 commits new 9d4b9d1bb9 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 8db4a3e14f 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 52dd87a67d 211: onsuccess: #2020: 1: Success after binutils: 10 commits new e966135998 212: onsuccess: #2022: 1: Success after linux: 3 commits new d241f7a417 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 1d91240260 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new 982c892d32 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new ba1e645aa3 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new 9077b65584 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new 4084bbcfdd 218: onsuccess: #2030: 1: Success after gcc: 5 commits new d235ac3918 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new 4ff35d9a5b 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new f32b692796 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 5fa344bcb5 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new e1f39deb08 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new a08f64f006 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new 804667b8e9 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new 0dd284562f 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new b75bde8c49 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new 85b7a4fde3 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new f69f66da44 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new b12006572b 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new 2674fab028 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 856e9cabfe 232: onsuccess: #2048: 1: Success after glibc: 2 commits new aef55033ff 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new a7b0529d60 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new f3dc0ac2b3 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new d0062216d0 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new 096c61fac5 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 6fe1283e48 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 3bda7b10f7 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new e50aa02288 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new e815003cfb 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new b8fd950266 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 16ab57da86 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new fce679e79f 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new e9110fcf43 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new b9b5c5cfa1 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new db4ec6f7aa 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 72770c0fa6 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 970b64c1e1 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 5434494c6f 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new e4074a8e8e 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new c942fac2ee 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 2f376fd5ed 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 89e3e5b3b6 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new d55187f806 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 489d8fdfd8 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 52962a4ee3 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 78a3728b96 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 078c79bb8a 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 24bff27411 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new d22c84847d 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 3815a41068 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 0c6e91d83e 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 368b700956 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new e2aafec6d6 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 7449cacdf7 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new d0f631ae4e 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 77777f5622 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...]
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 (29d0a92f44) \ 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 1808 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2804 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 32884 -> 32124 bytes 04-build_abe-stage1/console.log.xz | Bin 92876 -> 92096 bytes 06-build_abe-linux/console.log.xz | Bin 8560 -> 8572 bytes 07-build_abe-glibc/console.log.xz | Bin 237052 -> 237000 bytes 08-build_abe-stage2/console.log.xz | Bin 224952 -> 225836 bytes 09-build_abe-gdb/console.log.xz | Bin 39208 -> 39108 bytes 10-build_abe-qemu/console.log.xz | Bin 31524 -> 31720 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3900 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2608 -> 2660 bytes 13-check_regression/console.log.xz | Bin 6148 -> 6848 bytes 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 55 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/g++.log.xz | Bin 2659920 -> 2650864 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 2273828 -> 2271340 bytes sumfiles/gcc.sum | 2506 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 896768 -> 891836 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214032 -> 214028 bytes sumfiles/libgomp.sum | 6 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 442660 -> 438420 bytes sumfiles/libstdc++.sum | 8 +- 38 files changed, 1371 insertions(+), 1378 deletions(-)