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 31246be472 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 8a3a191778 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards f7c109275f 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards a4c23264c2 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 87d324d0a2 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 4b0137c203 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 5070fb35de 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 4cadc90ea1 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 3556b80707 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 03c09b4079 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 613fa0b47c 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 89259e3e22 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 73e27a3eea 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 4bcd8e423b 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards b33125b633 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 7d2b7c02a4 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 9d7c0f57fa 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 9500d2da2f 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 378016b59c 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 0d315f9eef 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 5b44964faa 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards e55f7c1f6f 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards f4a62e7618 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards df10366359 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 6ac8193f69 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 3c98665b75 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards be98897b7f 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 53d4f10281 295: onsuccess: #2545: 1: Success after linux: 10 commits discards a2dac1d7e5 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards fa701a9237 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 12230ca5fb 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 2095545f00 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards dc857f37d1 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 4349e62d40 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards b840f477c4 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards da1190223c 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 5c331abea2 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 7432986223 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 1bb9d8f48f 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards b125d19d6f 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 2e32cb634a 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 8edaee7e4d 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards b3164e921e 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 305dec7d49 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 181701f1e4 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards a6ac5127f3 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 5a9891ed15 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards e07009944b 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 7dc3b2684d 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 548967fd5a 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 0958fab953 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 302da9091f 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 43521ff238 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards fc809d8da6 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 30ce984353 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 9339433996 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards bd36330a0d 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards ae64af45ef 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 7011a127a3 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 0a78a13ead 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 8cb2028009 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 24306fec00 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 3bc1f224d1 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 946df1da07 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards ed7cc583ac 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards d6039d7c87 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards f54b8f18a0 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 957877fe6a 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 855b9e5276 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards e1fc21bcd9 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 46b90f6259 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 9f59d010dc 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 1c8616b363 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards c7f83ab2a7 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards cac4e3b5e0 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards c6a8f23984 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards dc79f376ed 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards dbdf4aea75 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 58c439a67c 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards 08011d4851 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 11941e12ae 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 8781944717 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 28d9cdbc88 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 31287f5d83 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards 4afb4a6b19 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards c2cc9aed95 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 43b9575cbf 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 881ff76f6e 235: onsuccess: #2483: 1: Success after linux: 108 commits discards bdf0448e57 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards ae531b2140 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 3abd901072 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards 13ed46a702 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards 6b1ce7b6c7 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards d44f4b77e4 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 4720fec0b0 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards 46d068e2ed 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards ad5fcd0fd2 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards 314962501b 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards d3ea036b9a 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards 87d940a0d0 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards 4190bb362c 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new cbfaaee986 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new 4925d8b9c5 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new b17da3b242 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new 1aa41d8610 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new e504375790 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new dadd1cb105 227: onsuccess: #2474: 1: Success after gcc: 2 commits new ad85f03478 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new f72e1e6404 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new 6011a96f83 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new 677436718d 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 092f8a9da5 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new df9b2f3fd3 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new c5e2e5c6f9 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 8c2f6a09ad 235: onsuccess: #2483: 1: Success after linux: 108 commits new 76d207843a 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 3564336f58 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new dca24ca93b 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 53f4acc4c4 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 40d9d3a485 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 9d63e12877 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 476d7e52c4 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new 955a100152 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 3d318afa0e 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new 0462913fd5 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 120ec0d1c1 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new 8825fa9ee1 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new d4e0bc403e 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 1bcd9d7dbf 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 2697938a3e 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 21b31fe9ec 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new d82298a21c 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 380f4c018e 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 1c835f2c2e 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 185a5faa2d 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new f1f33f4345 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new bd213dd85a 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 6d47798267 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new f82dde3bf4 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 9765b7e0f1 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new cef370d6be 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 80c08dca59 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 5520893e31 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 1bc06c4189 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new d0d850e554 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new dec095ca20 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new f57668126b 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new ad5718b9c9 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 77b6699779 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new d9c4b4f041 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 1a7afe17b1 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 768211c1c1 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new ad9019be19 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 5390b7a675 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 8c33d7c789 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new df59ff0db7 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 8509cf4ba0 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new c10807c182 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new af6ab3502c 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new bb9d01d901 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 26debdd568 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 274fb4199b 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new c1a1409892 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 01dad77714 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 9ee254cd8f 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 54fa09f0f3 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 672b063567 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 4efb200842 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 8e8cce4062 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new e0cf9be9c9 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new d75d387e50 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new e3472389e8 292: onsuccess: #2541: 1: Success after binutils: 13 commits new f5d9274997 293: onsuccess: #2542: 1: Success after gcc: 5 commits new d9a731e049 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new e878447f8c 295: onsuccess: #2545: 1: Success after linux: 10 commits new 90a9b36d7d 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 8c0308dc11 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 2c4e7954aa 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new f680b23d7b 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 372fa751ba 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 3786d228e6 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new c8974980bc 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new b3269808d5 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 0a54fa1e78 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 4dacc90547 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new d6183ff05f 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 1265bcd7e4 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new b4c2c3a6f9 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 8e43d2dbf6 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 06779f986c 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 499bcf47d7 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 82e56c0414 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new e49753ec31 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new a926efdcf3 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new a4010a0509 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 0020448acb 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new edac3dcf3d 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new a7a9ffe8f0 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new d460c1f169 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 152f8fe9fe 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 02b1622ae5 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 2e4c6efa44 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new eb02ef5408 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...]
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 (31246be472) \ 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 1764 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31948 -> 32212 bytes 04-build_abe-stage1/console.log.xz | Bin 72964 -> 73392 bytes 06-build_abe-linux/console.log.xz | Bin 8596 -> 8628 bytes 07-build_abe-glibc/console.log.xz | Bin 244600 -> 244688 bytes 08-build_abe-stage2/console.log.xz | Bin 204688 -> 204408 bytes 09-build_abe-gdb/console.log.xz | Bin 39584 -> 39372 bytes 10-build_abe-qemu/console.log.xz | Bin 31900 -> 31548 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2764 -> 2864 bytes 13-check_regression/console.log.xz | Bin 5840 -> 6824 bytes 13-check_regression/fails.sum | 8 +- 13-check_regression/mail-body.txt | 78 +- 13-check_regression/results.compare | 43 +- 13-check_regression/results.compare2 | 83 +- 13-check_regression/results.regressions | 43 +- 14-update_baseline/console.log | 58 +- 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 | 80 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 43 +- sumfiles/g++.log.xz | Bin 3435496 -> 3408308 bytes sumfiles/g++.sum | 30 +- sumfiles/gcc.log.xz | Bin 3014568 -> 3035844 bytes sumfiles/gcc.sum | 4528 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1040752 -> 1040360 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2284 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214652 -> 214676 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2704 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 423472 -> 432484 bytes sumfiles/libstdc++.sum | 8 +- 41 files changed, 2566 insertions(+), 2492 deletions(-)