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 bfc519bc54 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 77a25891a5 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 194aa29784 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards e967e5de44 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards dac9366cb9 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 1b45fc3863 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 51eccb1fb0 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards a435814e7d 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards be7702ad87 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 8f9335549b 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 51a99248c2 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards fd011b177d 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards ef0e2a3d3c 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards bba2bc6d8c 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards d0b4f959e0 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards b4367fa0cc 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards e599c4c45d 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 831a8fbaed 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 2a44ec4aae 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards bdcfe8afbb 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 225afc7c42 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 00cb549d60 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards e4da5449c7 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 5144170cda 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 1ebf32e0b1 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards e25dbb1f41 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 3880462b31 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 4253691e51 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards ef91d4d887 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards b77fc4eb9d 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 36cde0a10b 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 371034fa7b 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards acbfd80a64 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 154febeb0d 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards f059b9d5dd 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 3a0236386a 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards b662a1ffa7 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards cbc4ce7d8c 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 73f1cecdbb 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 6e251e4301 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 110a963fa4 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards cbce6c6240 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 1e56d60a10 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 38e451b7c3 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards e4da4a24f1 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 1da4fd7691 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 784b350fea 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 40dcaa4f60 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 0b52b29f1a 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards a12cd7059c 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards fb90074526 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards b7bbb77b73 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards cd596d658d 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards a68d5ed779 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards aa311b203f 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 3110548b6a 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 738097a81b 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 424eca0e35 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 5e8eead0dc 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards eca8272e4e 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 491fecad82 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards a76f179f09 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 9d27f9bf2e 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 001ae886ce 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards f11218ba7e 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 0e55ace345 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 41a63afd49 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards a389f258fe 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards d1aa9ee7db 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 8ebb761f1e 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards a3b96e9e0e 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 323e00ca7a 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 721d85db1c 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 463a5c5928 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards 259f1254b2 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 06211f0725 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards 8d84093e26 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards e7fd791243 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards f6ce10f3f6 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 8ea185bbc9 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards faad2e4245 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 7099bed67e 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 3feaa893bd 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards b58f7247d4 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards a93172dce8 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 6a4a224b26 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 024e924ebc 235: onsuccess: #2483: 1: Success after linux: 108 commits discards c0490097e0 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards a5e00c49b1 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 5ba7979146 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards a10b555d0c 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards e09456187e 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 42d1e5a49a 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 14581e44a6 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards 94b92ca595 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards 176fa1c6ae 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards f9a31bc6c9 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 388e7d18d2 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards 957ed5e284 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards ce5a7956ca 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards ceafd904a1 221: onsuccess: #2467: 1: Success after binutils: 3 commits new a113ada316 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 4190bb362c 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new 87d940a0d0 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new d3ea036b9a 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new 314962501b 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new ad5fcd0fd2 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new 46d068e2ed 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 4720fec0b0 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new d44f4b77e4 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new 6b1ce7b6c7 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new 13ed46a702 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 3abd901072 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new ae531b2140 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new bdf0448e57 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 881ff76f6e 235: onsuccess: #2483: 1: Success after linux: 108 commits new 43b9575cbf 236: onsuccess: #2484: 1: Success after gcc: 2 commits new c2cc9aed95 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new 4afb4a6b19 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 31287f5d83 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 28d9cdbc88 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 8781944717 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 11941e12ae 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new 08011d4851 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 58c439a67c 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new dbdf4aea75 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new dc79f376ed 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new c6a8f23984 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new cac4e3b5e0 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new c7f83ab2a7 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 1c8616b363 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 9f59d010dc 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 46b90f6259 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new e1fc21bcd9 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 855b9e5276 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 957877fe6a 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new f54b8f18a0 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new d6039d7c87 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new ed7cc583ac 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 946df1da07 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 3bc1f224d1 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 24306fec00 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 8cb2028009 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 0a78a13ead 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 7011a127a3 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new ae64af45ef 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new bd36330a0d 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 9339433996 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 30ce984353 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new fc809d8da6 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 43521ff238 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 302da9091f 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 0958fab953 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 548967fd5a 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 7dc3b2684d 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new e07009944b 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 5a9891ed15 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new a6ac5127f3 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 181701f1e4 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 305dec7d49 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new b3164e921e 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 8edaee7e4d 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 2e32cb634a 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new b125d19d6f 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 1bb9d8f48f 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 7432986223 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 5c331abea2 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new da1190223c 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new b840f477c4 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 4349e62d40 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new dc857f37d1 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 2095545f00 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 12230ca5fb 292: onsuccess: #2541: 1: Success after binutils: 13 commits new fa701a9237 293: onsuccess: #2542: 1: Success after gcc: 5 commits new a2dac1d7e5 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 53d4f10281 295: onsuccess: #2545: 1: Success after linux: 10 commits new be98897b7f 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 3c98665b75 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 6ac8193f69 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new df10366359 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new f4a62e7618 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new e55f7c1f6f 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 5b44964faa 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 0d315f9eef 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 378016b59c 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 9500d2da2f 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 9d7c0f57fa 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 7d2b7c02a4 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new b33125b633 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 4bcd8e423b 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 73e27a3eea 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 89259e3e22 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 613fa0b47c 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 03c09b4079 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 3556b80707 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 4cadc90ea1 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 5070fb35de 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 4b0137c203 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 87d324d0a2 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new a4c23264c2 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new f7c109275f 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 8a3a191778 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 31246be472 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 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 (bfc519bc54) \ 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 1776 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31992 -> 31948 bytes 04-build_abe-stage1/console.log.xz | Bin 73264 -> 72964 bytes 06-build_abe-linux/console.log.xz | Bin 8584 -> 8596 bytes 07-build_abe-glibc/console.log.xz | Bin 244532 -> 244600 bytes 08-build_abe-stage2/console.log.xz | Bin 204480 -> 204688 bytes 09-build_abe-gdb/console.log.xz | Bin 39472 -> 39584 bytes 10-build_abe-qemu/console.log.xz | Bin 31780 -> 31900 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2624 -> 2764 bytes 13-check_regression/console.log.xz | Bin 6292 -> 5840 bytes 13-check_regression/fails.sum | 27 +- 13-check_regression/mail-body.txt | 83 +- 13-check_regression/results.compare | 35 +- 13-check_regression/results.compare2 | 60 +- 13-check_regression/results.regressions | 35 +- 14-update_baseline/console.log | 64 +- 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 | 85 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 35 +- sumfiles/g++.log.xz | Bin 3414232 -> 3435496 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 3036908 -> 3014568 bytes sumfiles/gcc.sum | 4712 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1043520 -> 1040752 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214760 -> 214652 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2704 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 428532 -> 423472 bytes sumfiles/libstdc++.sum | 2 +- 41 files changed, 2622 insertions(+), 2570 deletions(-)