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 d6a38b1095 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards ba0f186449 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards fe07e383af 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 2ea86b5004 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 4665963108 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 20594681ba 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards fec3e123a3 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 55306e4545 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 988e10fbe3 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 4bc493a332 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 571b204983 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 2a8aaa205e 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards e9265cb180 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 37f3411f02 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards cd7adf0923 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards e32ec8b8d4 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 8e38f98b5c 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 63b5ae71cf 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards df8a14532a 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 6208cd2966 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 7d0db7a6a5 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards faa8afdd22 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 94876688e9 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 6a085f8815 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 6d487dfe5e 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards f151be2909 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 5c891912b2 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 0792de1b20 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards cb47e39fb4 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards af8774aebd 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 33a400fb54 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards db1ec88764 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 9358e8e5b0 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 218e7bebc6 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards eb8e0b55a5 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 88362b6912 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 158bc3d904 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 580bc3a30b 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 97274c88c8 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 8a61609fb9 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 08680caad9 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 5c120a770a 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 0507b7a669 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 7dc3c25ad3 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards d04799f90b 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 3751aacc27 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards 48fa9279ae 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 038b5b4637 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards 7a6bc31863 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 5f68589f5e 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards 1b8cc855aa 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 066a0607eb 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 8777a3b616 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 2cfb7714a2 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 88a35893f1 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards db308e3f38 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 315e3b8f81 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 065127ceef 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 583e692f1d 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 289db1fbea 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 21c1ee27ca 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards c1a5b7f68e 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards 5c4f25a47b 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards e36192cfae 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 23feafb11c 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 3e0a3d8d90 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards 52596ba761 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards b9c595aab9 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards 57b70671b5 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards ac43cbf7e5 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards e6caad3b64 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards 65d92656f1 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards f24e8f0eef 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards b3b57a6703 220: onsuccess: #2465: 1: Success after linux: 572 commits discards 7012c92197 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards a9fe727a4b 218: onsuccess: #2461: 1: Success after linux: 916 commits discards 4376a17c0e 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards 2bd1b4ab3d 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards 357fa736c8 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards 025147b057 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] discards 3b3fad4e1f 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] discards 525bde2942 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] discards 252489f23d 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards cc4cf04798 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits discards d468748091 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] discards 8cbabe6baa 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] discards d9ea1d56f2 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] discards 5d44cb4752 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] discards 5b60def5e8 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] discards 37398713a8 204: onsuccess: #2435: 1: Success after linux: 3 commits discards 405a0d1b37 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards 50064bb763 202: onsuccess: #2431: 1: Success after linux: 944 commits discards 26bce951bb 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards 0399a05637 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards cb84ccac87 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] discards 19638492c3 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] discards 6bd9c96d82 197: onsuccess: #2348: 1: Success after linux: 190 commits discards 4d327698a9 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] discards 52b41d5d06 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] discards 8fe506075a 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] discards a51100c780 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] new 8eb341fae4 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] new 3b10a763fb 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] new 9a88eccac5 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] new 1e0b9fccc4 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] new 2cb259bfde 197: onsuccess: #2348: 1: Success after linux: 190 commits new 2a3e2430b0 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] new 50eb9c12bf 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] new 6c0efd4e30 200: onsuccess: #2427: 1: Success after binutils: 274 commits new 96cea56664 201: onsuccess: #2430: 1: Success after glibc: 26 commits new c2f670e79d 202: onsuccess: #2431: 1: Success after linux: 944 commits new 2ce7604c04 203: onsuccess: #2433: 1: Success after binutils: 27 commits new 1ce4025ad3 204: onsuccess: #2435: 1: Success after linux: 3 commits new e11e9ffb77 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] new 7c3de234a8 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] new a2aeec16aa 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] new 44eb035206 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] new 735bd82f42 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] new c6fb825f89 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits new 7f41964922 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new d72258da9a 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] new e2ee65419e 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] new 4068f77077 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] new 24b4995e8c 215: onsuccess: #2455: 1: Success after binutils: 3 commits new 945db6493b 216: onsuccess: #2457: 1: Success after linux: 1736 commits new d78b9d7312 217: onsuccess: #2459: 1: Success after binutils: 3 commits new 6bc876511b 218: onsuccess: #2461: 1: Success after linux: 916 commits new a505d4a0e5 219: onsuccess: #2463: 1: Success after binutils: 3 commits new 6d53b0075e 220: onsuccess: #2465: 1: Success after linux: 572 commits new 33e97009db 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 0923e0d695 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new bf995db356 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new e4c59c6ece 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new ace7d41f69 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new c391ef773e 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new 339e8fd133 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 3090cf21a2 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new 57276569c7 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new d6b2c745f3 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new afe61c301a 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 70f552a01f 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new 0f79512c40 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new 25d83f28fd 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 06d6835244 235: onsuccess: #2483: 1: Success after linux: 108 commits new 38238b6c13 236: onsuccess: #2484: 1: Success after gcc: 2 commits new c6cad313fe 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new db2d68fc55 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 1875ee814c 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 690ce2ecf9 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 35b06d73ed 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new c176e66dde 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new d0afc54536 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 05123e24a7 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new f891a2494e 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 0d888c3bae 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new 2ab3fc5b4d 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new 0a291cebf6 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 4df96f32d1 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 6b2c0f5a12 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 2dcfe88d5e 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new b16933d1c7 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 2f2af9a4d6 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 14ddf014c6 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 998e5f0ebd 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 43841e9f7d 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 323eee9113 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 9d8da0ef61 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 0e8c4a6107 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new bc9dd81c2a 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 77419770f9 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 33492c7d9c 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 2f35d1e81d 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 1a76e4f1c3 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new ca38f4f3b1 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 88fc5b2e7c 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 2d84cd53ff 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new e887f9e39d 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 96bc721ea0 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 9f2bfe6ad1 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 1dd2d0f261 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new ce9b823192 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 804faddbd2 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 9828fbfa33 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 0905292ab5 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new d982d1aa29 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 9b5e0fbe53 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 77da45a534 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 7fe7772625 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 93b33cb7c2 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 964b563b9c 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 9fc80c186f 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 30d00f7c01 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 21dd9d812e 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new b7804a54b3 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 2ca3c5cd2e 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 321b67a0a7 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new f0e979d612 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 7b1e0cd9ac 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 07fc2916cd 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 6242967adc 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 6b6f67a73a 292: onsuccess: #2541: 1: Success after binutils: 13 commits new d2228e31ce 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 29aece61f2 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...]
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 (d6a38b1095) \ 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 1792 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32152 -> 32348 bytes 04-build_abe-stage1/console.log.xz | Bin 73492 -> 73140 bytes 06-build_abe-linux/console.log.xz | Bin 8524 -> 8528 bytes 07-build_abe-glibc/console.log.xz | Bin 245536 -> 245524 bytes 08-build_abe-stage2/console.log.xz | Bin 204788 -> 204612 bytes 09-build_abe-gdb/console.log.xz | Bin 39564 -> 39456 bytes 10-build_abe-qemu/console.log.xz | Bin 32044 -> 32000 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2632 -> 2640 bytes 13-check_regression/console.log.xz | Bin 5312 -> 5512 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 6 +- 13-check_regression/mail-body.txt | 35 +- 13-check_regression/results.compare | 20 +- 13-check_regression/results.compare2 | 32 +- 13-check_regression/results.regressions | 20 +- 14-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 37 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 20 +- sumfiles/g++.log.xz | Bin 3410192 -> 3441804 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 3033544 -> 3028172 bytes sumfiles/gcc.sum | 4788 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1041288 -> 1044676 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214724 -> 214664 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 428244 -> 439444 bytes sumfiles/libstdc++.sum | 6 +- 40 files changed, 2570 insertions(+), 2494 deletions(-)