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 11b69f6a19 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards 7604afda5b 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards 7ec7fadd2d 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards 42d4817506 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards 289d0d238c 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards 1f84815235 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards ae63a21510 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 57aa625ec8 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards 52e4c947dd 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 27d68f331a 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards f1cb68759b 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards ace6656682 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards 6dde73b467 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 8c27d90051 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 13ce17e391 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 2f6b5e6c14 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards fb276c9c89 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 4477b2a552 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 6e8653d754 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 5cbd8b1461 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 9381ee9204 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 44db632fab 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 076ad94e72 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 4240f08b20 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 4ad8f672bd 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards f8b7616bca 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 060d8d1b8b 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards fcdf578a29 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 859a026acf 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards f8d90a4dcf 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 03a87029d1 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 2c07d109cf 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 1ded06039c 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 6b07ec372e 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 9fd40cb8a0 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards fb4997bb24 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 5102304b74 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards ee4260917c 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards b76536c67f 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards d284ec9977 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 59c54a702e 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 2dcc2c55dc 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards b508bc3331 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 3cee86c8d7 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards e1a2098c78 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards d32595b01a 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 908c26ad30 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 58df7280cb 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 3c0e542fb2 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards bdd2721405 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards e88389ba0c 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 6fcd91f143 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 66ddb0f1f3 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards ecbe6691dd 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards b7eaaab026 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards fb3fc81d3d 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards e52db4ec12 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 45a8c1b1ed 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 2e55f067ee 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 50e81a3355 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards ac9e9a7a3d 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards fc9efe59cb 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 80ddaa36ff 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 75007e3943 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards b9f7e5be07 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 17c6b856de 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 06c8b876cf 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 1aa4f46f78 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 9a071355b4 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards a3ace3acaa 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards acaeeb4134 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 45ac4625e9 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 27c40ff6d4 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 0766bbd912 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards d8aa083fa9 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 51005c1aa7 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 38ce7075e8 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 5f9017f4f0 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards f693716dd6 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards cc1218f433 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 43250b8efa 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 7f8cc87b11 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 8bb3350ce8 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards ce5d6d915c 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards b9257841af 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 5381a31d57 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 71fe91a322 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 4312a0d053 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 8cd5729942 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards fccc854437 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 76de231bb3 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 7c0091a1ae 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards f76ae54cfe 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 745bb9fc84 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards b2a722e8b8 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 90bba5c69c 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 00fc439e21 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 3ec13dd294 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards f0e92c6745 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards a0c2647c48 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 19b7a686d1 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 461c7a564f 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 709d2ca8dd 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new f418810369 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new eae41b8789 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new b4d0aba239 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 2e37881508 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new d69dcc0e79 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 7b6c8fd70b 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 8642db3f12 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 8f36481d52 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new cfb25ed8f8 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 482f7888d3 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 7ab27b4d52 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new a991f077bf 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 397c53d0bc 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new b4c3249697 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 5d90ae7dc0 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 6fe6d61c12 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new cbfb325748 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 6ccedec883 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new dd3c34889b 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 4fa6a10479 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 8106d8bf07 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 8e4567f9cc 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 99c65ead60 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 9ec02276d8 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new a8b2cd4e06 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 487c18be67 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new ef6c438ed7 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new a10a9a817f 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 44f1307493 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 3f3ca88194 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 068d3512aa 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 0dd775470f 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 38aefbcfe5 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 01599e5b4d 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 5edc3d2d67 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 330c7ba6e1 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 05e7a82a92 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 048b445d44 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 08723423ad 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 13105a0996 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new ae40464f77 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 05566765c7 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 8605e8c8f9 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new a2d51efbcb 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 5905a0a3a7 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 72988dee2e 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 8f37fd6261 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new e03034df85 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 760d539ca7 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new dfd95e865e 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 8c2960a220 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new c817198cc9 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 39dae4c4b0 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new b92377a22b 384: onsuccess: #2205: 1: Success after gcc: 2 commits new c456591c06 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new cb3556fa5a 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 609d3d8657 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 742da7a810 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 6f247b3126 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 0000e1fe0c 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 1a5d1aaab1 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new b0af8afd54 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 8cf2e14530 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 4e84e4bc7a 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new d76a590ec9 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 9951f70662 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new fb74f92484 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new da6c484fe5 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new b91797c55a 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 447d6751d7 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new dfc5effd06 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 742247cef3 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 1686871175 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 0c7d2ff8e0 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new f69b7f6ccd 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new bd406557fe 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 923b8bfce3 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 8c771af068 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 61f3a8e6bb 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 00c7ce7c67 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 58af123d19 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 9776b9fe06 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 68bd15df1f 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new d019a34580 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new d1dcb7dd9b 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new b3594e30fb 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new fa0ac8e678 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new c70368e52f 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new fb0291c963 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 1301559955 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new bd4c0da0a6 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 0760b0eedd 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new 0bb404759e 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 8048565d1b 424: onsuccess: #2248: 1: Success after gcc: 6 commits new fe3f7b2339 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new 5aef975b78 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new c5c6eebdcd 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new 44753fbffa 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new f83000a188 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new 0dc530c9a8 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...]
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 (11b69f6a19) \ 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 1752 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 30652 -> 30652 bytes 04-build_abe-stage1/console.log.xz | Bin 88872 -> 88924 bytes 06-build_abe-linux/console.log.xz | Bin 8316 -> 8860 bytes 07-build_abe-glibc/console.log.xz | Bin 235608 -> 235312 bytes 08-build_abe-stage2/console.log.xz | Bin 225532 -> 225508 bytes 09-build_abe-gdb/console.log.xz | Bin 38616 -> 38608 bytes 10-build_abe-qemu/console.log.xz | Bin 31964 -> 32000 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3792 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3080 -> 2964 bytes 13-check_regression/console.log.xz | Bin 7116 -> 7200 bytes 13-check_regression/results.compare | 16 ++++---- 13-check_regression/results.compare2 | 73 +++++++++++++++------------------- 14-update_baseline/console.log | 66 +++++++++++++++--------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +++++++++++----------- sumfiles/g++.log.xz | Bin 2653840 -> 2650332 bytes sumfiles/g++.sum | 12 +++++- sumfiles/gcc.log.xz | Bin 2216976 -> 2221464 bytes sumfiles/gcc.sum | 3 +- sumfiles/gfortran.log.xz | Bin 892560 -> 895304 bytes sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217072 -> 216956 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436008 -> 439764 bytes sumfiles/libstdc++.sum | 19 ++++----- 39 files changed, 133 insertions(+), 130 deletions(-)