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 886d621b71 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 96c08aab31 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 3b8766eda8 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards dfd9b39c5c 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards fa89a7d132 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards c34f771b2f 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 0c47a9c1f4 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 13275291f7 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 6f70320796 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 639a599205 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 4254daa50f 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards a12f968c60 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 1cb80c7823 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards e924f364a8 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 6297c8f119 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 4649a61e50 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 273e0344f3 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 4ff0effee2 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 0917cbf99d 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 65c7891bbb 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 000931545a 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 35e2eb3726 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards a141b52cf9 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 591e9cfaaa 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards d0b0fd7a6b 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards dcfb9157a7 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 3198f291fd 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 986199c881 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 7306de64ed 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards b23e761471 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 6551aba402 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards a8b83e7b3f 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 027006a1fa 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards cab2833ccb 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards f179042df7 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards cb4a02c161 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 66ad06a2da 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 3dacf4340e 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 576d3d9347 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 5712af4399 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 9a443b0873 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards acc811a0b4 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 7302d2b9e9 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards cca42df9f3 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards dfbab32cc3 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 6b8e80b7c3 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards f446160e7a 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 1d615c2e12 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 03823c29e5 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 5efd869994 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 1443a0de3d 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 495b8edac9 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 9f35178550 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 4ddb56a0b4 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 1e68c5d083 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards e9b735e5e4 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards bec9a76a8d 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards d3143e6edf 295: onsuccess: #2545: 1: Success after linux: 10 commits discards c020c887bc 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 3707e57b74 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 7f0959d3ee 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 9d5137a181 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 145bc9352a 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 275afc7be5 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 7891c5a379 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 4fb9ca1cde 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 2b9ded8002 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards e58fe9f358 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards d6845f8b51 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 95809c9345 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards cb8675782f 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 7032b4a1ab 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 4495d4b51b 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 925f71773a 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards eba72401cb 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards bfd520cd07 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards c597aac9af 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 46b170a144 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 2b8d73cd7b 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards fd8c033e69 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 16f5750ce9 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 32160a7555 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards a65dc9b2b3 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 732e2810a2 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 148b888094 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards abcae22f10 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards dfea561210 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 39620725aa 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards e90262b75e 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 295d277ae1 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards e255433428 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 4811e710bf 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 4711ffc0e7 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards bd386fcc74 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards a87b74f1c4 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 6cc57232c8 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards c0f969a1e3 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 72494d5428 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards b13814db93 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards bf10407f8c 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards e12c6c796e 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new e9e0628efe 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new ee3ee0a4b7 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new d0d6b3a22c 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new d8f8da7b95 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 15316818da 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 4b93915a64 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new f1290f5944 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new efa7c6a846 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 3f2aae78b3 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 44564187f0 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 322f419cc7 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 85c831ae51 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 1600f63979 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new f49bc2cf54 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 7717ba1916 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new a7569d08cd 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 128edd0253 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 2bac45ef13 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new b42a3f99a9 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new b96f37307e 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 2714453cfe 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 20f8ef2a00 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 21b63c4c2b 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new a3e4b0f24f 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 990f6108ba 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new bc291c9c6b 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 08279f8a64 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 41c306369d 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 73727e3900 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 71fd96d9ab 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 761b87db63 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new ca5b497fc8 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new c2705e9b60 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new f848c5601f 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 5c67f2246f 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 038c33fbf3 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 1dd1d44ce8 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 715e53af6f 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 3f2d8e97de 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 0a6b6678f6 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 898de3762c 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 0873ce9866 293: onsuccess: #2542: 1: Success after gcc: 5 commits new cc7167e572 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new c2619fc799 295: onsuccess: #2545: 1: Success after linux: 10 commits new b4043b873b 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new adc77d9663 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new affc11f856 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 48fc522954 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new d764046acb 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 9de840cdf4 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 8878548354 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 354711dc7d 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 74049879d0 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 4818cd2e23 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 2c2828970f 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 066661015e 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new ea4e772927 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 4266b84c93 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 0da54f5605 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 247279558e 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 2fbbd2e31a 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 05ec79d59e 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 0f96783a08 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new cfd577cdf3 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 795e835d10 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 3cdb219416 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new a93bbdce56 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 7904e8336e 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new d7ccd53aab 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 21bfa7f584 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new a9a982bc5e 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 82e94a8c21 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 2c8a044103 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new bc8adbc66a 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 1e6e19ce27 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new bd2d25ea90 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new a0e7bc9781 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 0b69fd0ebb 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 1087ac40f2 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 898348043b 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 42e77f9a5f 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 988dc44145 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new c423dbf74b 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 8d0bcbcd7c 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 68ffbaffc0 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 3c0aac5cec 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 512fd8caa8 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 4a6823adcb 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new d433078261 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new b2c8a544e7 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 7e83da9b58 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 4aa2898827 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 677eccd05a 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new ce087c803f 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new d5c584c54d 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new f086219c0c 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 4dae6541ff 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new c7e58eef75 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 12530e5c5e 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 52efad5e10 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new a35b1ff8a2 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new ca608a9f1a 353: onsuccess: #2603: 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 (886d621b71) \ 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 1820 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 32012 -> 32044 bytes 04-build_abe-stage1/console.log.xz | Bin 74300 -> 74292 bytes 06-build_abe-linux/console.log.xz | Bin 8592 -> 8364 bytes 07-build_abe-glibc/console.log.xz | Bin 246456 -> 246984 bytes 08-build_abe-stage2/console.log.xz | Bin 206928 -> 206584 bytes 09-build_abe-gdb/console.log.xz | Bin 39184 -> 39076 bytes 10-build_abe-qemu/console.log.xz | Bin 31972 -> 31960 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3952 -> 3924 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2732 -> 2784 bytes 13-check_regression/console.log.xz | Bin 10352 -> 7652 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 16 +- 13-check_regression/mail-body.txt | 197 +- 13-check_regression/results.compare | 93 +- 13-check_regression/results.compare2 | 431 +--- 13-check_regression/results.regressions | 93 +- 14-update_baseline/console.log | 68 +- 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 | 199 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 93 +- sumfiles/g++.log.xz | Bin 3407012 -> 3401032 bytes sumfiles/g++.sum | 4 +- sumfiles/gcc.log.xz | Bin 3000836 -> 3019184 bytes sumfiles/gcc.sum | 3940 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1041944 -> 1037840 bytes sumfiles/gfortran.sum | 22 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214780 -> 214776 bytes sumfiles/libgomp.sum | 8 +- sumfiles/libitm.log.xz | Bin 2664 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 431788 -> 435368 bytes sumfiles/libstdc++.sum | 191 +- 43 files changed, 2542 insertions(+), 2871 deletions(-)