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 884786236c 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 5c84c8e971 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 60a971f604 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 83e648c744 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 77f8c2c4f1 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards da02d95e95 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 4f1a1f11f1 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards c71161a045 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 3a7b60cb44 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 33c8106d08 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards cdcca11626 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 25010d59a8 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards e2d26ee213 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards c5db2b701c 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 53d78031f0 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards b8998743a8 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards fb218dc00a 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 409f98a122 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 4c91b9d5c4 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 68620e8dec 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 7584f18eae 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 8937932d03 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards e6efc1bbb3 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 5d481041d9 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 6994f08222 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards a1e90242d3 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 653718830e 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 813590df2e 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards c67aef9344 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 064c862206 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 247c81c267 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards d67c726bb7 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 004a9cad34 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards bdb626b15d 295: onsuccess: #2545: 1: Success after linux: 10 commits discards fb7b2dfde4 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 7f2d5806c3 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 3485dff056 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards a7cabd6bf9 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 7e62ca9fb8 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards d9ffc603f3 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards cac09cce97 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 89546c211a 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards cf4ec3bf03 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards c96e5b7d7b 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 18ce5d8457 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards c36116467f 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 9c7bb86520 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 5241af0f8d 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 384ee88043 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards b378d0d2a1 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards e3afd445f8 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 96eb7cad6d 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 0be81f856d 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards d53a3e916c 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 313e335104 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards c97895b9fc 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards b13ac0d40d 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 481d6f38dc 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 7b35516c20 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards efd4649cf3 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 6304f0e997 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 10a68a0259 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 3bacb0380a 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 9d7b65ab0e 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 79867531db 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards b4d603da7a 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 1b603928a2 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 937f8938dd 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 1603cbd577 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 836595d7e9 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards c3078077a7 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 6e0f121338 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 44c8d22845 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 59a8535165 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 92b0499d2e 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards bf0d16d52d 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 0dcd2be1e0 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards fd95ab4375 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards f861936704 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards b96d02580c 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards eec57070a5 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards f24fc67540 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 45ea7d258f 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards 05dee471bb 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 6aec3131f7 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards fb0cb4e063 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 3ba839e552 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards c4471e7b58 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 44450ed398 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 89a80442d4 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards 7079338564 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards d29ca30528 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 16ec8bbd2a 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards fd223bed6a 235: onsuccess: #2483: 1: Success after linux: 108 commits discards cd3ac70b31 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 27ae4f2f4e 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 4c857af2a5 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards 42f8d4261e 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards afc7d922c2 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 2d3ad36c66 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 207556b105 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new 64ef73f607 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new 8bc661eb86 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new 60db4b8c7e 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new f4fbdb1a15 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 256100420e 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new de579c2ec8 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new 718006f7f1 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 9cab6bd1c6 235: onsuccess: #2483: 1: Success after linux: 108 commits new 261b88cae5 236: onsuccess: #2484: 1: Success after gcc: 2 commits new b402c26093 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new efd2730c9f 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new b17c135682 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 2bcfa6d325 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new cde218ee00 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new ce7a101eb6 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new c72c83ab1a 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 80df272c97 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new bcda594e35 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new f358957e31 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new d5536659fe 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new 412de5eef0 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 71055f702d 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new f26f434ef1 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 656ac5349b 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 4c268e9d96 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new aa89419799 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new cefcb0dd67 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 1a014e61e2 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 97ebe94d99 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new f4bcb952de 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 67f485b086 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new a38f95644f 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 421c5b3cf6 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 69ab9b580d 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 4889a3fd87 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 39e578d796 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 5a2502b1fb 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 4b11df39f3 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new f38e46111e 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 940e82cb10 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 6ef25a3460 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 4e880107cf 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 961556973d 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new ff76d03c0b 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 2ef63c127b 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new ef7ce37a34 273: onsuccess: #2521: 1: Success after gcc: 2 commits new ae99b7fa01 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new aaed60b10a 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 9ac132f74c 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 360b6ea4d4 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new f8ce924775 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 3ab4c97558 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new f792c7b256 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 6cf925f686 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 0776103477 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 7f0a3d12fc 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 822bd5720b 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 8309e17294 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new e84470e0c4 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 00d7514a40 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new c2a2b9820d 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 51339b6f30 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new a51754963b 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new cbab43b2d9 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 43ec28ab8a 292: onsuccess: #2541: 1: Success after binutils: 13 commits new fb342c03eb 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 4e07c22b12 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 03dba8a975 295: onsuccess: #2545: 1: Success after linux: 10 commits new 7baea607d1 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new ac03b9ef50 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new c382ddb06b 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 392efc97bf 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 9782d42e0c 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 836f3fe114 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 295bf33a08 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 574db564e8 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 434fafd685 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new bfbd489015 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new ca74fafbae 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 2e6b76d055 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new f24dc67511 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new decd4758c3 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 284796af61 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new e97f8f040e 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 2fc843abd7 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 7a5ac7283b 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new ab6a22f4a4 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 846852e0b3 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 852c51ee55 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new d86d602b01 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 7842f88819 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 7aec6f98e7 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new c5500cb5b7 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 70d6e18455 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 7ecba8286c 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 57950b3435 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 185eb4aae7 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 10f75b3ccc 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new c4089754c3 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new b4ff9d0265 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 0b75de6eef 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 30184e5294 329: onsuccess: #2579: 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 (884786236c) \ 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 1836 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 32120 -> 31956 bytes 04-build_abe-stage1/console.log.xz | Bin 73528 -> 73412 bytes 06-build_abe-linux/console.log.xz | Bin 8740 -> 9408 bytes 07-build_abe-glibc/console.log.xz | Bin 245220 -> 244944 bytes 08-build_abe-stage2/console.log.xz | Bin 204764 -> 204584 bytes 09-build_abe-gdb/console.log.xz | Bin 39772 -> 39448 bytes 10-build_abe-qemu/console.log.xz | Bin 31984 -> 31984 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3936 -> 3948 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3276 -> 3012 bytes 13-check_regression/console.log.xz | Bin 7640 -> 6436 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 23 +- 13-check_regression/mail-body.txt | 172 +- 13-check_regression/results.compare | 44 +- 13-check_regression/results.compare2 | 85 +- 13-check_regression/results.regressions | 44 +- 14-update_baseline/console.log | 36 +- 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 | 174 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 44 +- sumfiles/g++.log.xz | Bin 3425416 -> 3420112 bytes sumfiles/g++.sum | 24 +- sumfiles/gcc.log.xz | Bin 3038464 -> 3041224 bytes sumfiles/gcc.sum | 4176 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1041200 -> 1039792 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2300 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214900 -> 214736 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 430540 -> 429820 bytes sumfiles/libstdc++.sum | 2 +- 43 files changed, 2335 insertions(+), 2557 deletions(-)