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 6e3ea48272 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 017e2207c8 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards aa61db9ef1 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards dc0f751870 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 6387613468 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 38cb7c02b0 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 899b595e82 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards ea8e9f022b 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 12f51e6703 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards a3ee60647e 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 70ed6b679a 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 3e991a30fe 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 2e3eb1b82a 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 8b15f7ee72 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 15788c8a34 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards e2f4abcc01 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards a6df7ac3df 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards cefeed3a5b 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 991d35298f 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 9110249a2e 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards d85b548b45 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 2d8010959c 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 707e7948a0 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 82d0db90ac 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards c39016aac5 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards fc417a245c 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 628710c6b3 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 54ad9b7f15 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards d12b5e1664 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards e165c1d7df 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 445e32c142 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards aeebd44bd7 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards b2a6204139 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards c89e6c0dcb 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 36aee202ff 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 6391b2722e 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 8535985826 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 1dd4e97304 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards ac8f8657e1 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards fcd130c7c1 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards b04843e90c 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 99e939d101 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 76c640abc4 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards b05f9d4b00 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 4665799689 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards a94128f618 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards 60b70c2062 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards d7f5861507 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 591732244c 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards 0ad22cd6e2 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards 44dac248cc 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards fe805d8a88 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 863ef804b5 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards dba91dd164 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards e8cb6e2859 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards af45468103 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards 02fea97f57 220: onsuccess: #2465: 1: Success after linux: 572 commits discards 8bb0529f8e 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards 4a8ea56a15 218: onsuccess: #2461: 1: Success after linux: 916 commits discards 8eba0ee40f 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards 1cf66d6be6 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards 39770dfbbd 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards 7b43e3b141 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] discards 362a36d98f 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] discards 59af4070b6 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] discards 1741407fc8 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards 730646bf5f 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits discards fa3f0cd00a 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] discards d5b23176d5 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] discards c624e4843f 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] discards 827e0fd987 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] discards fa432a14f4 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] discards cf862b2c40 204: onsuccess: #2435: 1: Success after linux: 3 commits discards 20c92a1f3a 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards 1e931c9452 202: onsuccess: #2431: 1: Success after linux: 944 commits discards ca6ba5de45 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards c2e22c0863 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards f286c65ff6 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] discards d6e1ab32a3 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] discards b8b11ba7f4 197: onsuccess: #2348: 1: Success after linux: 190 commits discards c26aaa3202 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] discards 799e8bb716 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] discards baaa211fe9 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] discards 8f42fab1cd 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] discards ff85d51cdf 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] discards 45c3d7c58d 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards daa76a77b1 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] discards 74da20c1d8 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] discards 9c3676b97e 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] discards 2773301970 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] discards 783e1b58f1 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] discards e44b0f3792 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] discards cf982ca898 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards f5addcc593 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards 7e14c91fa9 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards 3d474624fe 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards 02f243e568 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards 0e5924c45f 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards 7537fa01ba 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 5e8e44d4fa 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards 95dbae0250 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 51dd14ccb6 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 68911799dc 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new f9594a2539 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 683fbc72b5 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new 799add21ad 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new 0f47de1adb 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new ed1fc1e0c5 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new a74ff32ec3 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new 8d99c61300 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new 752a5194c2 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] new 04c06f7c05 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] new 76773a2194 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] new ef4b80ab4e 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] new 79443e7a77 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] new 11035a294a 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] new 93b6d57708 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 4b2333895e 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] new c0038ad070 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] new b0905d9ec4 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] new 438d4d1fa5 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] new 3b5c0fc78a 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] new a7825320ea 197: onsuccess: #2348: 1: Success after linux: 190 commits new 68d4c6a2cb 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] new e81d108acd 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] new d27741f1bd 200: onsuccess: #2427: 1: Success after binutils: 274 commits new 644f10fab9 201: onsuccess: #2430: 1: Success after glibc: 26 commits new 3bf5ab7c6d 202: onsuccess: #2431: 1: Success after linux: 944 commits new 3b640bb685 203: onsuccess: #2433: 1: Success after binutils: 27 commits new 12e260a13c 204: onsuccess: #2435: 1: Success after linux: 3 commits new d11f25cc46 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] new dea0d75302 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] new 58744cdc36 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] new 190cdc44d8 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] new d7fa75434a 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] new 21f57a5e35 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits new 5f5c3e870b 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new e52aa52ea2 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] new f61a9dbe7e 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] new e0214a897f 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] new 46fc30bc16 215: onsuccess: #2455: 1: Success after binutils: 3 commits new 2e7f092f60 216: onsuccess: #2457: 1: Success after linux: 1736 commits new 82e235ca3f 217: onsuccess: #2459: 1: Success after binutils: 3 commits new 65583dc8d5 218: onsuccess: #2461: 1: Success after linux: 916 commits new 74e3ac7954 219: onsuccess: #2463: 1: Success after binutils: 3 commits new 5a93b8d464 220: onsuccess: #2465: 1: Success after linux: 572 commits new a65bdacb61 221: onsuccess: #2467: 1: Success after binutils: 3 commits new fddc5c3c2c 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new e4f922fde2 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new 4faf781fc0 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new f880d1bb04 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 66286a0ac7 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new 8b87f23b9b 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 676da7c71e 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new ee0d63d653 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new 802b4d0e80 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new 0a1fd6f965 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 3a26738e99 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new 632fb0e799 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new fbc8a66f79 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 4f144b5fa0 235: onsuccess: #2483: 1: Success after linux: 108 commits new 528582d783 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 6c33141ca4 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new 1513ef6d2c 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 4885f0820b 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new fe8eb8d5ce 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 93c012edc7 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 4e408a6392 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new bbfbbb1d55 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 2e07d3ee9d 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new 336d9a3e86 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new f421949cac 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new 8cb01b52b8 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new 0ff9eb9ebb 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 244919d6ac 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 97309e3077 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new b7993d7fad 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new a0e0727f8d 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 501d9548e1 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 197e885efa 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 6664f1127b 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new c43e5b4292 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new eb63db1e65 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new b88e2f45c0 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 5d4708b46e 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 8dfe3dffa7 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 6de114ac77 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new b257f99654 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 45c763a513 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new a73445ca04 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new a041b8d07f 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new e1b8dd53a9 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 70d5c93e2d 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 55e634177a 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 18a122a24c 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 305d4e1131 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 4cd7faeec5 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new b0c65724db 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new f3479e281b 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 1dfc286741 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new dc7539a85b 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new add9829b8b 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new a7858a2bb9 277: onsuccess: #2525: 1: Success after gcc/linux: 60 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 (6e3ea48272) \ 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 1824 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 32396 -> 32104 bytes 04-build_abe-stage1/console.log.xz | Bin 73672 -> 73504 bytes 06-build_abe-linux/console.log.xz | Bin 8592 -> 9224 bytes 07-build_abe-glibc/console.log.xz | Bin 248096 -> 245712 bytes 08-build_abe-stage2/console.log.xz | Bin 205336 -> 205360 bytes 09-build_abe-gdb/console.log.xz | Bin 39696 -> 39456 bytes 10-build_abe-qemu/console.log.xz | Bin 32268 -> 31400 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2716 -> 2864 bytes 13-check_regression/console.log.xz | Bin 5548 -> 6340 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 70 +- 13-check_regression/results.compare | 37 +- 13-check_regression/results.compare2 | 41 +- .../results.regressions | 83 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 72 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 40 + sumfiles/g++.log.xz | Bin 3402384 -> 3409720 bytes sumfiles/g++.sum | 26 +- sumfiles/gcc.log.xz | Bin 3034500 -> 3036028 bytes sumfiles/gcc.sum | 4548 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 1042872 -> 1040160 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214840 -> 214860 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 430948 -> 428692 bytes sumfiles/libstdc++.sum | 14 +- 41 files changed, 2547 insertions(+), 2503 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum copy mail/mail-body.txt => 13-check_regression/results.regressions (57%)