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 359c6146dc 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 58bd9f21c7 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards f5ff5bba5d 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 8b1b144b4e 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 3cc01721e0 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards d7fbf1f138 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards a838870107 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 6aa43c0a88 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards c4d09ab463 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 61eb9b2768 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 9459160877 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 44fecc566f 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards a83ee1e325 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 37e997af5b 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards c231b86011 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards ef82fb20b6 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards ef302514a6 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 35772caf52 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards b884be82a8 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 7e790a72ab 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 0f4d60046d 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards b1d7eb4511 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 9c0824222c 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards f20c2d5bd5 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 4a20cef8c7 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 96504a3c44 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 874fe4507a 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards f29e6e6b39 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards 8e6c2f5a0b 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards fc2adcf8e9 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards ec7c5ef760 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 0c18046492 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards 18893980d9 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards e5d33ffb09 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards a4fb23de91 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards cd85b7e6e6 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 12767a3070 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards 87adbdeab4 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 82fafdf4c5 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 44f49e825b 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards d5aa188000 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 7dc308a0cc 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 706c2a0ea3 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 348c14fa87 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards 130ab2f1f2 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards ea1fade389 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 54191c860f 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 9d501c743e 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards 87ad096c87 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards e2b2c15cd6 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards a510f07b54 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards b045d39572 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards 263e1dac00 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards 9e39186943 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards 7115343951 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards 2d044965a9 220: onsuccess: #2465: 1: Success after linux: 572 commits discards d4d0a27879 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards 291f0ef17c 218: onsuccess: #2461: 1: Success after linux: 916 commits discards cda0bc4c9d 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards f908ab8750 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards 825d607224 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards 75e840d4c9 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] discards 6cd1c533c9 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] discards 86edaa3d7f 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] discards dd07f91d3f 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards 92833bd095 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits discards 7685faac11 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] discards 9c0a54322d 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] discards 00c5758439 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] discards ee44d237b3 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] discards e35a39aa04 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] discards f0389a27ee 204: onsuccess: #2435: 1: Success after linux: 3 commits discards 406f207740 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards cd16c17509 202: onsuccess: #2431: 1: Success after linux: 944 commits discards e82a775dd5 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards f73b3b1152 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 25fda31fb6 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] discards c8591346c7 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] discards ada2a2fa19 197: onsuccess: #2348: 1: Success after linux: 190 commits discards 2089967683 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] discards a62193174f 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] discards 87e5c21fb0 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] discards 406db77431 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] discards e030c26b13 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] discards 236803ab5e 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards b41d64594a 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] discards d750ed7b7f 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] discards 6325034a05 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] discards ba13e3cce6 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] discards 910c0fb23c 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] discards 3fd81b365f 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] discards aaa4dd1420 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards 441c6ffbcb 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards 9cc5906dd2 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards 3f58a42775 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards c2a24c270a 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards 7dbdbb374c 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards 2395483958 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 8fc36d9650 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards d1335d71a0 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 0707d269b3 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new fef4837848 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 95dbae0250 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 5e8e44d4fa 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 7537fa01ba 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 0e5924c45f 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new 02f243e568 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new 3d474624fe 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new 7e14c91fa9 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new f5addcc593 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new cf982ca898 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new e44b0f3792 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] new 783e1b58f1 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] new 2773301970 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] new 9c3676b97e 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] new 74da20c1d8 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] new daa76a77b1 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] new 45c3d7c58d 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new ff85d51cdf 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] new 8f42fab1cd 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] new baaa211fe9 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] new 799e8bb716 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] new c26aaa3202 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] new b8b11ba7f4 197: onsuccess: #2348: 1: Success after linux: 190 commits new d6e1ab32a3 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] new f286c65ff6 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] new c2e22c0863 200: onsuccess: #2427: 1: Success after binutils: 274 commits new ca6ba5de45 201: onsuccess: #2430: 1: Success after glibc: 26 commits new 1e931c9452 202: onsuccess: #2431: 1: Success after linux: 944 commits new 20c92a1f3a 203: onsuccess: #2433: 1: Success after binutils: 27 commits new cf862b2c40 204: onsuccess: #2435: 1: Success after linux: 3 commits new fa432a14f4 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] new 827e0fd987 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] new c624e4843f 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] new d5b23176d5 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] new fa3f0cd00a 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] new 730646bf5f 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits new 1741407fc8 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new 59af4070b6 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] new 362a36d98f 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] new 7b43e3b141 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] new 39770dfbbd 215: onsuccess: #2455: 1: Success after binutils: 3 commits new 1cf66d6be6 216: onsuccess: #2457: 1: Success after linux: 1736 commits new 8eba0ee40f 217: onsuccess: #2459: 1: Success after binutils: 3 commits new 4a8ea56a15 218: onsuccess: #2461: 1: Success after linux: 916 commits new 8bb0529f8e 219: onsuccess: #2463: 1: Success after binutils: 3 commits new 02fea97f57 220: onsuccess: #2465: 1: Success after linux: 572 commits new af45468103 221: onsuccess: #2467: 1: Success after binutils: 3 commits new e8cb6e2859 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new dba91dd164 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new 863ef804b5 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new fe805d8a88 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 44dac248cc 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new 0ad22cd6e2 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 591732244c 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new d7f5861507 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new 60b70c2062 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new a94128f618 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 4665799689 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new b05f9d4b00 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new 76c640abc4 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 99e939d101 235: onsuccess: #2483: 1: Success after linux: 108 commits new b04843e90c 236: onsuccess: #2484: 1: Success after gcc: 2 commits new fcd130c7c1 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new ac8f8657e1 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 1dd4e97304 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 8535985826 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 6391b2722e 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 36aee202ff 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new c89e6c0dcb 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new b2a6204139 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new aeebd44bd7 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 445e32c142 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new e165c1d7df 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new d12b5e1664 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 54ad9b7f15 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 628710c6b3 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new fc417a245c 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new c39016aac5 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 82d0db90ac 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 707e7948a0 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 2d8010959c 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new d85b548b45 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 9110249a2e 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 991d35298f 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new cefeed3a5b 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new a6df7ac3df 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new e2f4abcc01 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 15788c8a34 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 8b15f7ee72 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 2e3eb1b82a 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 3e991a30fe 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 70ed6b679a 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new a3ee60647e 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 12f51e6703 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new ea8e9f022b 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 899b595e82 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 38cb7c02b0 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 6387613468 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new dc0f751870 273: onsuccess: #2521: 1: Success after gcc: 2 commits new aa61db9ef1 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 017e2207c8 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 6e3ea48272 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 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 (359c6146dc) \ 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 1760 -> 1824 bytes 02-prepare_abe/console.log.xz | Bin 2804 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 32404 -> 32396 bytes 04-build_abe-stage1/console.log.xz | Bin 73912 -> 73672 bytes 06-build_abe-linux/console.log.xz | Bin 8464 -> 8592 bytes 07-build_abe-glibc/console.log.xz | Bin 247208 -> 248096 bytes 08-build_abe-stage2/console.log.xz | Bin 208096 -> 205336 bytes 09-build_abe-gdb/console.log.xz | Bin 39876 -> 39696 bytes 10-build_abe-qemu/console.log.xz | Bin 32468 -> 32268 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3924 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2724 -> 2716 bytes 13-check_regression/console.log.xz | Bin 5620 -> 5548 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 10 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 9 +- 13-check_regression/results.compare2 | 44 +- 13-check_regression/results.regressions | 30 - 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 30 - sumfiles/g++.log.xz | Bin 3424504 -> 3402384 bytes sumfiles/g++.sum | 26 +- sumfiles/gcc.log.xz | Bin 3039004 -> 3034500 bytes sumfiles/gcc.sum | 5212 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1041908 -> 1042872 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214680 -> 214840 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438552 -> 430948 bytes sumfiles/libstdc++.sum | 2 +- 41 files changed, 2744 insertions(+), 2820 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions