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 b3c6f7a250 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards 21ad25c1fb 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards 7b82da807a 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards 045a9af7a4 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards 8615f30f52 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards a38b0e918d 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards 6c170d879d 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards c76f9da26a 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards aaf887e8da 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards ecb5a713ab 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 25985def76 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards ce43c3c6f0 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 9f4b2d5aa9 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 514a29a88b 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 9056353ff3 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards 32aeba4dc8 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 086eee59e9 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards f9f485ad05 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards c518c05a4e 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards d6266e4e93 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards cb9ae4d781 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 116d6734e1 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 972ca9647a 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 2938970a04 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards b5a03d6106 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 0d9d998ccd 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 0f49b1605e 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards aaf46f8604 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 909c849b8e 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 9d00c5a535 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 6b58e332b6 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards ff3403ff9c 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards ff237f334c 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 774e64fe4f 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 4118054966 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 3b9a4b75e4 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 04c556b8c5 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards c0b85640d6 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards ca4f9379bc 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 1ee14a2c2b 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 70f9ce20ca 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards dae6cd06d4 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 095c594008 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards f91d19f688 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 19bc125b7f 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards a2a374c076 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 045819c660 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards ca12188fab 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 616d9c414f 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 22f401be12 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 8651d65a86 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 80ba2911b4 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 7ff42d8f31 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards d13bcd6841 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 7966bb3e11 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards ae4b6693f4 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 07e60e4ca5 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards b98571f28e 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards eda4f7c94e 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 4750c116eb 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards d0e5386bdc 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 25bc6daa75 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 617cb6c547 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards d2d1b95abd 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 79097e24d1 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 98e6331c85 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 9d85347dab 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards f9348fa766 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 256685bb7c 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 2c1dffc1ac 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards e624abb300 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards e8c56d728f 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 73c65a8365 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 07fcf67cdf 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 8a665b918d 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 7e72f129f8 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards ebcd75760d 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 3c47a13152 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards ea8d579db0 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 365b122f16 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 65173589fa 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards c4f548327f 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards efa6dd32c7 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 5bd9aa1b9d 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards e1fa2769eb 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 557af28f81 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 2f7f4111fe 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 408a1c2d24 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 211f79825e 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards e16efb2944 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards ec04998407 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards b17c778334 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 0e9d3c1e20 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards cc65814de1 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards df0c28cd4f 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards c554647044 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 0387c0b11a 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 6f42be2738 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards fcd25e6b4a 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 996cb7c8c4 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards ea6f07b691 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new d78eeaa8b3 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new a127743b01 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 6980d64545 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new b9f71e92e4 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new e7e83f0c46 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 3acee73eaf 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 556337e9d8 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 143491bbbc 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 64d7826576 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 196569131c 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 1b8bb819f9 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new e4cbd10bd6 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new a1fc20c277 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new d9dba2b9f9 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 5af2c22227 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new f59d3487fc 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 435e2585fd 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new fc294ba1e5 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new b7b38dffe7 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 5cc175f1d8 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 72470cfc5c 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new ffa045e57a 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 3f8cf08aab 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 4bafad248a 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 699ee21d45 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new b9643e180f 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 3d5245edc0 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 052eed4ef9 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new c28df838ed 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new ce2dd0de0c 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 390f1104f2 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 58b3217d2b 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 3b11e0d555 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 54106fd0f0 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 16141d88b1 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 620ec7bbf6 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 782ebe1770 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 3c015b27e2 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 33f435b639 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 3795c52057 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new a29245f798 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 766f541e23 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new c268f43607 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 9e5d6a945a 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new aef5f2fe3e 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new f7a7ef336f 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new c3ed7cd16b 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 25b36aeb6e 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 06d49d0fba 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new e15fb71e21 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new e9737216fc 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 72a06fa990 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 418652e45e 384: onsuccess: #2205: 1: Success after gcc: 2 commits new c6d24ad0f6 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new e18945528c 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 89e70b9720 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 1ac6cb95fa 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 2459e8eb76 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new ebfdc82cc2 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new d78906cd3e 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 5cbb79369f 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 711d8f7333 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new c3f275af3f 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 0643bea806 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new f13b177192 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 01eba9a4ca 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new e0194a1202 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 309502eb31 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new c3e1bb038c 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 995dbca54e 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 260e278e91 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 11115b101f 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 967fca8344 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 87265aa5ef 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 6098675c07 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new fecfc43ae1 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new ff0605d504 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 489b5ca49f 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 4050a8dd73 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 943b825d6a 411: onsuccess: #2232: 1: Success after gcc: 3 commits new b7cc56713c 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new abdc7f8cd8 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new e7c8d9a1ab 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new f26c5065b6 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 59beb6b9ba 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new 678965f44a 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 51110e8593 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new 97415f5cc2 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 2b08c68c2d 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 0ee726e313 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 61811ba83f 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new 0cd2fdfdca 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 2dbb0044b4 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 4a64de7b79 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new 324c649bc2 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new 40fab073ca 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new 21e6cd55cc 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new c7ffa47491 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new 32045a22db 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new 70f31ca0fd 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new b6535d06fa 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new 33947b5e3d 433: onsuccess: #2257: 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 (b3c6f7a250) \ 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 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31456 -> 31368 bytes 04-build_abe-stage1/console.log.xz | Bin 88860 -> 88520 bytes 06-build_abe-linux/console.log.xz | Bin 8520 -> 8528 bytes 07-build_abe-glibc/console.log.xz | Bin 235472 -> 235860 bytes 08-build_abe-stage2/console.log.xz | Bin 226244 -> 225744 bytes 09-build_abe-gdb/console.log.xz | Bin 39224 -> 38952 bytes 10-build_abe-qemu/console.log.xz | Bin 30700 -> 31216 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3800 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2784 -> 2676 bytes 13-check_regression/console.log.xz | Bin 5264 -> 6464 bytes 13-check_regression/results.compare | 16 ++++----- 13-check_regression/results.compare2 | 27 +++++++++++--- 14-update_baseline/console.log | 64 +++++++++++++++++----------------- 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 | 40 ++++++++++----------- sumfiles/g++.log.xz | Bin 2657580 -> 2639104 bytes sumfiles/gcc.log.xz | Bin 2204508 -> 2213392 bytes sumfiles/gcc.sum | 13 ++++++- sumfiles/gfortran.log.xz | Bin 892792 -> 891120 bytes sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217012 -> 217052 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 439700 -> 435976 bytes sumfiles/libstdc++.sum | 22 +++++------- 36 files changed, 115 insertions(+), 89 deletions(-)