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 64e52e6482 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards a340ef4375 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 9838d09c2a 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 88366e0bd4 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 1cea275183 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 12f05d3937 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 52d5ca79fe 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 9b952680b4 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 67f78dd3ee 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards da12eb2a96 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 814ece578b 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 070ae1337e 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 26120cf094 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 687a7fc5a5 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 877a8585df 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 3c4a831787 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards f60bdffc7c 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards d4bd0f8b82 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards e38fc2890a 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards e0581285d2 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards b5525afae1 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 2b3992cb4a 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 096cf9a679 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 74839e3821 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 054e4f4fe6 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 6a47a3cc55 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 4de16cba36 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 3e8acd3842 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 0abf07a7ac 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 2bf4d63ac0 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards beba477af4 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 258b0ad99b 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 94eb3f240a 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards c842547108 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards aa4e1b990f 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 6c6dcc3b94 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 842b907aec 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 54df098fc9 301: onsuccess: #2118: 1: Success after linux: 16 commits discards bd13abde5f 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 94ac56ccfd 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards c743e1913c 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards e801bdc2dc 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards ae8964fcd5 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 905eea02ea 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards eb6af7e2d1 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards f435c8a134 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards d13c7b535f 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards e227485925 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 953a9e0bda 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards bb948e8679 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 06296e3200 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards aace657f0b 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards d3a853dc2f 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards f0d8874c08 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 1532cf60cc 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 86f0d9e4a6 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards a3e7fd9629 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 0846d21e0d 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 10c89669d3 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 5bf492a834 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards f5d617337d 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 8fea2e2478 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 11eba28624 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards efe71d53a8 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 6ee1229d8d 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards f0742b46c4 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 52a3470d4f 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 2133097903 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 5a99732ffa 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 224727fa77 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards d7560234cf 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards e55fab4778 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 589f3b661f 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 5d91a0b622 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 351a142748 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards c31bad6528 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 3185ce54eb 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 8651caa5b1 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards c28eee23df 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards b00f7c8b37 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 443c6a8d34 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 48c14e0036 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards f6feca5120 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 8f959e2ef9 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards d0653f51cd 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 2d405308ac 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 7310117341 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 90b86be02f 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards d25d330523 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards e13a91a07e 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 1a699288a5 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards d7439f15db 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 0e4760c67b 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 9e506d4e27 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 510e97cf9c 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 313b8e5d11 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards fb2e9c5371 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 5066d8428d 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 16dd521cd3 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards f87658c675 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards ec1a731fa4 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 401f9a60eb 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 7b850707e5 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 3f935a9a99 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 89c6cd8de5 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new a7d5a7d68f 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new b8f80e0fc6 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new ec8676d2f2 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 6d24c2a1d9 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new e2c8b9557e 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 1ad5142c1b 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new a8addfbad6 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 509ff5d40e 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new c676bde5aa 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 0c0d9aed54 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 0c8210bcb7 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 49faa48700 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new e967bde8c7 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new c9c6c1dd99 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 2880342d8b 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 1689779a9b 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 1cf2880338 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new b22dfb25b7 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 08e1971dd6 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 8d46811724 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 2b8f20971e 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new b90115ed27 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new e36bcc6fdc 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 876b6b5c84 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new ae67119433 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new b83857a9b2 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 21063cb952 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 00058f56a4 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new f3492ac6f7 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 65eae2a006 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 142f60deb0 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new e35b6427af 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 1914fd28cc 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 56f33dd94b 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 48b6ab0ac0 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 7571d41bde 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 08b668ecd4 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 3f8bc17dc4 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 014c407752 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 75097f0856 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 2e8ce3a743 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 487aa56654 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 059015e216 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new d86d1a26c2 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new b708ff5329 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 9e9601db00 287: onsuccess: #2103: 1: Success after gcc: 9 commits new e95b6b74cb 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 1ab474f2c9 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new c475910e2f 290: onsuccess: #2106: 1: Success after gcc: 2 commits new e9d981e501 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 4a1f9bd93f 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new cbd87e181c 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 062bee2dcb 294: onsuccess: #2110: 1: Success after gcc: 17 commits new dbed0ac7e8 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 1c00da0f8a 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 7bd665a5ba 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 8cdb896001 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 3709d4d381 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 98f1f417a1 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 4030888c70 301: onsuccess: #2118: 1: Success after linux: 16 commits new b559547472 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new cde93bbeca 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 447226fef7 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 313059d4eb 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new a9c8529374 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 26838f1feb 307: onsuccess: #2124: 1: Success after gcc: 2 commits new e0c4979690 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new d9aded48cd 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 1794ca6a06 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 1d12e38e3a 311: onsuccess: #2130: 1: Success after gcc: 4 commits new e82449c06e 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 574e643219 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 5291dcb8b6 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new fc09516b32 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new a27bcc5607 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 32809d4eb0 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new e965718bd8 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 884bebd4ba 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 7187e18786 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 27f2258719 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new d3a40d924a 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 0e3b5d32ab 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 505c3a68a6 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 8a910efdaa 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new eb2c859e54 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 8af3e80cf5 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new a26ad4fd07 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 1d1655d11e 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new fb508161f8 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 99d83fba01 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 759ae3a30a 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new c16129e305 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new aab2f0fa4d 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new b08605598f 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new a28db6f5e4 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 7ab5907257 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new e92516a580 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 26906d9048 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 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 (64e52e6482) \ 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 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2804 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 32252 -> 32420 bytes 04-build_abe-stage1/console.log.xz | Bin 93076 -> 92636 bytes 06-build_abe-linux/console.log.xz | Bin 8704 -> 8700 bytes 07-build_abe-glibc/console.log.xz | Bin 237964 -> 238272 bytes 08-build_abe-stage2/console.log.xz | Bin 231568 -> 231304 bytes 09-build_abe-gdb/console.log.xz | Bin 39648 -> 39692 bytes 10-build_abe-qemu/console.log.xz | Bin 31492 -> 31504 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3908 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2544 -> 2692 bytes 13-check_regression/console.log.xz | Bin 6304 -> 5592 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 20 +- 14-update_baseline/console.log | 78 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.xz | Bin 2689380 -> 2662812 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2258412 -> 2271064 bytes sumfiles/gcc.sum | 2460 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 898892 -> 895108 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214088 -> 214136 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 440428 -> 429432 bytes sumfiles/libstdc++.sum | 2 +- 38 files changed, 1335 insertions(+), 1365 deletions(-)