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 33947b5e3d 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] discards b6535d06fa 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards 70f31ca0fd 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards 32045a22db 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards c7ffa47491 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards 21e6cd55cc 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards 40fab073ca 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards 324c649bc2 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards 4a64de7b79 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards 2dbb0044b4 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 0cd2fdfdca 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 61811ba83f 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards 0ee726e313 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 2b08c68c2d 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 97415f5cc2 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 51110e8593 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards 678965f44a 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 59beb6b9ba 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards f26c5065b6 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards e7c8d9a1ab 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards abdc7f8cd8 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards b7cc56713c 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 943b825d6a 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 4050a8dd73 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 489b5ca49f 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards ff0605d504 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards fecfc43ae1 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 6098675c07 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 87265aa5ef 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 967fca8344 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 11115b101f 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 260e278e91 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 995dbca54e 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards c3e1bb038c 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 309502eb31 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards e0194a1202 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 01eba9a4ca 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards f13b177192 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 0643bea806 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards c3f275af3f 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 711d8f7333 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 5cbb79369f 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards d78906cd3e 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards ebfdc82cc2 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 2459e8eb76 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 1ac6cb95fa 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 89e70b9720 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards e18945528c 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards c6d24ad0f6 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 418652e45e 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 72a06fa990 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards e9737216fc 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards e15fb71e21 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 06d49d0fba 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 25b36aeb6e 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards c3ed7cd16b 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards f7a7ef336f 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards aef5f2fe3e 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 9e5d6a945a 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards c268f43607 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 766f541e23 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards a29245f798 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 3795c52057 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 33f435b639 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 3c015b27e2 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 782ebe1770 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 620ec7bbf6 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 16141d88b1 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 54106fd0f0 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 3b11e0d555 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 58b3217d2b 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 390f1104f2 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards ce2dd0de0c 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards c28df838ed 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 052eed4ef9 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 3d5245edc0 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards b9643e180f 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 699ee21d45 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 4bafad248a 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 3f8cf08aab 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards ffa045e57a 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 72470cfc5c 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 5cc175f1d8 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards b7b38dffe7 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards fc294ba1e5 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 435e2585fd 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards f59d3487fc 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 5af2c22227 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards d9dba2b9f9 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards a1fc20c277 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards e4cbd10bd6 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 1b8bb819f9 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 196569131c 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 64d7826576 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 143491bbbc 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 556337e9d8 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 3acee73eaf 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards e7e83f0c46 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards b9f71e92e4 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 6980d64545 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards a127743b01 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new f73d850b73 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 3ce3562931 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new d79627d006 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 5fc7aef5dc 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new c84f79c6da 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 40274b87a9 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 906a7eff32 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 59c55a2cb3 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 37c249713e 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 9e8d71b5b6 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new ad9420f155 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 12b20c0130 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new bb2048691c 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new e225dde8ec 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 1af249f1e8 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new dc8246c1e0 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 30351c2d99 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new bb55c9fc3a 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 50140eb028 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 498f71735e 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 954ec5e112 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 186a5a64b1 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new fb28800cc8 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 6132283856 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 07e5e72506 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 2a49396961 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 3cc5d7e268 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 47896e6cc3 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 9cd7cbcc0b 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new f5482bd46b 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new c3ea946fa5 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 4a79a10f47 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 028ee0bfd7 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new aaf80579e1 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 02a4b684b0 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 5a5a9c8a51 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 5edc0956ff 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 8eb7649d64 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new bcfd14a2e4 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new fefe98c8e2 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 10419274d9 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 0998d9207b 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 4bdad6ccd0 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 85633ec0c4 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 4616bec857 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 9144aeefca 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new d12ce3b90c 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new f111e56e19 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 39479a504f 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new e9af489e4e 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 851c07c6fd 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 79b3050d86 384: onsuccess: #2205: 1: Success after gcc: 2 commits new eaf1800912 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 60d542b482 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 5cf84f71d3 387: onsuccess: #2208: 1: Success after gcc: 2 commits new fbd0d14e7b 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new da3a48ca8b 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 2f0ca9d3f9 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new ca6c48d0a6 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new e3ce94ba34 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new dddf5ffc8f 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 2a7da81828 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 57da896f3d 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new be56c13698 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new cfdde42a36 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 3c4018b6be 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new a5b7f39e0a 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new b9d58f7434 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new d0cb35f6ec 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 1aa48a438a 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new da8b179178 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 3d7a805b5a 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 5002b4af02 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new d7ab4b783f 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new d57e8b4867 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 4e1a82583d 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new b1f870405f 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 3ef1f202b8 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 5ebe8e03db 411: onsuccess: #2232: 1: Success after gcc: 3 commits new c5f150091d 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 25a6d8c75d 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 806974f932 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 3b3d9c42ac 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 8cd562d4c7 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new 6d4607e809 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new ed53f83ca9 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new 8a88da7a65 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 14c99a5e5a 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 6af9138e4c 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 078daf4d06 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new 69d22ee140 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new c3a18503ab 424: onsuccess: #2248: 1: Success after gcc: 6 commits new e3439dd638 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new 59d3b803d6 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new bcd0959892 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new c0480bd84f 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 78e496add6 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new 2b3205ea90 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new 56450a16de 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new ac8867c016 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new 8078d711b7 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] new 572212afc6 434: onsuccess: #2258: 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 (33947b5e3d) \ 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 1756 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31368 -> 30944 bytes 04-build_abe-stage1/console.log.xz | Bin 88520 -> 88796 bytes 06-build_abe-linux/console.log.xz | Bin 8528 -> 10536 bytes 07-build_abe-glibc/console.log.xz | Bin 235860 -> 236128 bytes 08-build_abe-stage2/console.log.xz | Bin 225744 -> 225716 bytes 09-build_abe-gdb/console.log.xz | Bin 38952 -> 38672 bytes 10-build_abe-qemu/console.log.xz | Bin 31216 -> 31308 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3808 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2676 -> 2708 bytes 13-check_regression/console.log.xz | Bin 6464 -> 5844 bytes 13-check_regression/results.compare | 16 ++++++------- 13-check_regression/results.compare2 | 43 ++++++++++++++++------------------ 14-update_baseline/console.log | 42 ++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_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 2639104 -> 2639536 bytes sumfiles/gcc.log.xz | Bin 2213392 -> 2198340 bytes sumfiles/gfortran.log.xz | Bin 891120 -> 891672 bytes sumfiles/gfortran.sum | 4 +++- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217052 -> 217016 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435976 -> 441356 bytes sumfiles/libstdc++.sum | 24 +++++++++---------- 36 files changed, 94 insertions(+), 95 deletions(-)