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-aarch64 in repository toolchain/ci/base-artifacts.

discards 7b74b7ae85 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards f347580258 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards b0412039b9 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 463805f213 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards ccc70c0517 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 77006287c4 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards ab4898bc9f 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards fbfc02d972 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 6ac8b2a3e3 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards a50ce812ea 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 3984003b3c 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards a724291d75 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards feefc2554e 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 1dc87b8702 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 5335c1fa21 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 6c0fa20a52 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards a10c0df477 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 9572fe32d9 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 9d5e8daff4 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 4666e08daa 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 203ca8ad26 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 2f4fedb755 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 87aa64b063 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 22771b897f 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards e1064d2775 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 74a59d4f3a 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards bb2add98e4 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 2e97718b0f 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 6a5a5a77ee 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 0832c520e3 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards c229db0849 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 9b5b20be62 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards 4e4bec9f77 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards dd32be857a 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards f7987f2d70 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards df972b3aa5 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards b0b4f35430 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 25b5b054ca 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards e44a6a10ff 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 3555114b20 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards b37eec5373 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards aeae4c7fec 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 42f8041a4b 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 8149bfe4ae 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 3353fd7a23 235: onsuccess: #2483: 1: Success after linux: 108 commits discards ead9d6618b 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 05835d1859 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 41df656168 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards a89ace6586 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards 270d251c3f 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 6f217e8d41 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 59d4c83d5e 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards cc2d96cad1 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards c404c4c1c7 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards 653793fd98 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards cfa867350b 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards dea4625c24 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards b5f8042a06 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards 3f87c7af27 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards 5313a0b42f 220: onsuccess: #2465: 1: Success after linux: 572 commits discards 8fbdb728a9 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards 41fa3b1c4a 218: onsuccess: #2461: 1: Success after linux: 916 commits discards 9815de2759 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards 6efe9aeacf 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards e7cf022c94 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards dd612ce779 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] discards 028ec33411 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] discards 17072e5a05 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] discards 5764581f83 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards c375a5a2e0 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits discards f1f501f933 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] discards db5f7224b8 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] discards 95b6505374 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] discards 777cfcb253 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] discards 30c5379c68 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] discards 557f4c9d93 204: onsuccess: #2435: 1: Success after linux: 3 commits discards 266e9affda 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards ed9aa96a8d 202: onsuccess: #2431: 1: Success after linux: 944 commits discards 44aa7d499f 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards ab94ce0868 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards ace521c568 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] discards d09aaff11b 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] discards de38f1b95d 197: onsuccess: #2348: 1: Success after linux: 190 commits discards 9df71718be 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] discards d1b28a87d5 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] discards 9d5206b359 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] discards 4bb40d080a 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] discards 93994fbb4e 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] discards c0802b4646 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards c28d39d517 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] discards da85b1c7c3 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] discards 8d5c8f1fa7 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] discards 1b9f6e11ba 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] discards 1d6d64972a 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] discards 06544d2958 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] discards 3bfed1a7e9 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards 004ca716ad 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards b0de52760f 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards bc94076405 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards aedd4602ca 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards 1c99601b3d 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new 45a2164c1a 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new cb0ff09aac 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new 05712c8dde 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new 4329752af6 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new c678bf0acf 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new 8cf06257a5 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new af5c027832 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] new 4cb90cff86 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] new 15c2335139 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] new b7a827f63b 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] new 63c61a8f48 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] new 4e9f36a458 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] new 7e86595df7 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 22e35631f7 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] new 5a6182fe67 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] new e27cdf0cd4 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] new 4f9f720107 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] new 5a0a00820d 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] new 1c906df0f8 197: onsuccess: #2348: 1: Success after linux: 190 commits new 93dcea92ad 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] new 31cdd6661d 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] new f822266d4f 200: onsuccess: #2427: 1: Success after binutils: 274 commits new 4155064a24 201: onsuccess: #2430: 1: Success after glibc: 26 commits new 958537efd7 202: onsuccess: #2431: 1: Success after linux: 944 commits new a3e6222aa4 203: onsuccess: #2433: 1: Success after binutils: 27 commits new 9f0cfbf855 204: onsuccess: #2435: 1: Success after linux: 3 commits new de45a64d5a 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] new 764cbe039b 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] new 4c76808ef7 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] new a55c68ccd5 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] new de4b418c3f 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] new 6e65891599 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits new 8f5e69a697 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new 5ea73eeb6e 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] new 84f7df78cd 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] new ff97685745 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] new a7e5986efb 215: onsuccess: #2455: 1: Success after binutils: 3 commits new e2358af5ce 216: onsuccess: #2457: 1: Success after linux: 1736 commits new 0365fc073f 217: onsuccess: #2459: 1: Success after binutils: 3 commits new dd93ab9a21 218: onsuccess: #2461: 1: Success after linux: 916 commits new cb1d10234c 219: onsuccess: #2463: 1: Success after binutils: 3 commits new d93d1505be 220: onsuccess: #2465: 1: Success after linux: 572 commits new 2abe7cb5de 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 84be8811d2 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new 1e56dd447b 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new 4623f8491f 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new ff8010db08 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 05076bcd77 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new 512a3340eb 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 63df0298c1 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new a859e8fd8c 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new d037ff2fc3 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new d9f88f073e 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 13282419d0 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new c19020e4b0 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new ea0ca346a4 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 3c58a6b983 235: onsuccess: #2483: 1: Success after linux: 108 commits new 066ea1ed25 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 8454b0c757 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new c7b3469ebc 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new c6eff935b0 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 52e439710c 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new eba3ef5c1c 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new f8398d3d6f 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new c17e6fbbd7 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new ce60784a5b 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new d64c324acd 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 533efc819f 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new 3827cbc6b7 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new d90c84343b 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 60ce355dbe 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 0bcd2ecd20 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new c46315490b 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 62f11067df 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 9701a9da1d 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 12054e2836 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new be9a29fc69 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 15cbf8a30d 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 3432d84ab7 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 9fdf0d0387 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 96b0d8a878 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 1820d6ff28 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 4b0b6d98bd 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new fd1e5d7da4 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 9fefa4fae2 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 1eefeaacb6 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 6d6a652259 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 0f01d3d501 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 60e41f3389 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new c3116a0cdc 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new edb11d5e80 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new b73090d615 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 628a8df105 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new b9686060ba 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new e2d9a9cf3e 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 6a1abf0a6e 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new ab16ce92a8 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 70c21106a0 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new fcb497b285 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 1f98b522f0 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new c4688fb95a 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 2d30c920ec 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 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 (7b74b7ae85) \ 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 1816 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 32060 -> 32696 bytes 04-build_abe-stage1/console.log.xz | Bin 73520 -> 73800 bytes 06-build_abe-linux/console.log.xz | Bin 9228 -> 9252 bytes 07-build_abe-glibc/console.log.xz | Bin 245128 -> 245152 bytes 08-build_abe-stage2/console.log.xz | Bin 205160 -> 205096 bytes 09-build_abe-gdb/console.log.xz | Bin 39460 -> 39832 bytes 10-build_abe-qemu/console.log.xz | Bin 31588 -> 31972 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2856 -> 3216 bytes 13-check_regression/console.log.xz | Bin 5848 -> 5888 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 4 +- 13-check_regression/mail-body.txt | 71 +- 13-check_regression/results.compare | 35 +- 13-check_regression/results.compare2 | 46 +- 13-check_regression/results.regressions | 35 +- 14-update_baseline/console.log | 42 +- 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 | 73 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 35 +- sumfiles/g++.log.xz | Bin 3405256 -> 3409708 bytes sumfiles/g++.sum | 42 +- sumfiles/gcc.log.xz | Bin 3036900 -> 3031080 bytes sumfiles/gcc.sum | 5236 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1039860 -> 1040396 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214612 -> 214732 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2700 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434100 -> 431160 bytes sumfiles/libstdc++.sum | 10 +- 42 files changed, 2781 insertions(+), 2902 deletions(-)