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 19049c4023 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 119bd55530 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards d2c93af8c5 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 4b7dbc71d2 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 11636e8931 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards e712715538 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 034d04409b 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards c0d418bc93 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 37190e758f 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards 4e77c34fd7 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 9253b866a1 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards 0fc1bd7e8b 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards e0727ef4da 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards c780d08b8b 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 41b6f09ccf 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards c08ff18811 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 9682848b8c 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards a395a92d0a 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards 3fb7ec7218 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 25deefb1a3 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 43ba377293 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards caba3b5533 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 52a6cc3969 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards e0c608eb1e 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards e507fcc05b 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards 94af8df5bf 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards 44e9eb84e6 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards d0c49e6362 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 6637e76427 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards 7c8e1339d1 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards 1b1f9832ce 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards a109245529 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 91fba80bc1 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards 19d2f1f856 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards 762e68bc7a 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards d397515b59 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards 508f5366c5 220: onsuccess: #2465: 1: Success after linux: 572 commits discards c4a793c186 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards a2cf5b16c2 218: onsuccess: #2461: 1: Success after linux: 916 commits discards c867d16a28 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards 8ece9031e0 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards 646efae83f 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards fcd042e2cc 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] discards 75861c554f 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] discards a052b81863 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] discards 6c61ba7a1b 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards 28fc308bcb 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits discards 7b569ef9bd 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] discards 6917e943ea 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] discards 6d7f687f70 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] discards ac0a9c8f66 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] discards 8f85e49839 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] discards e203633bd3 204: onsuccess: #2435: 1: Success after linux: 3 commits discards 84886b9eb3 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards d46df6e452 202: onsuccess: #2431: 1: Success after linux: 944 commits discards 3dd99401ea 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards 25d35b190b 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 8d6f477e13 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] discards 30a6f2a241 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] discards 96c71f82f1 197: onsuccess: #2348: 1: Success after linux: 190 commits discards a98cadabcd 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] discards 6244c436a5 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] discards 6bf6f56c0f 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] discards b2af1bf823 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] discards 4eb4c14f81 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] discards 79542b2d4f 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 075b003ba4 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] discards cd312f240f 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] discards 54965caac7 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] discards 8f80d03dbf 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] discards 0635dba5a7 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] discards d3374df043 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] discards 6d45a2545b 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards 262b1d97fe 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards 967783187e 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards 60fbbdfdcf 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards 1529f020ec 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards 5555659925 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards b9765ee6b8 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards fc59f778f8 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards 401b940dd0 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 9652972910 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards a8dcfff671 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards 300d4a9e9f 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 7ac717397a 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards dfd357c8dd 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 6331c522c0 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards 697ab77d63 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards f69368a8f4 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards e1878ff946 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards af40318776 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 00f55e5d5d 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 2cc67a51d4 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards cd7b8db4f8 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards ea49d79aa6 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards efb5201ea4 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards fd7d31c1ba 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 5156381f74 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 442ba5e0a0 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards c7546785bf 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards cad4421b55 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new c1210e84c0 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 95b941e3e9 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 7d7aca64ac 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new bb97b2ab9f 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 47bde71ad3 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 3ad3819ebe 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 97c0d9eda8 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new 3870a5da36 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new b746ef0deb 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new 64a08f741b 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 3ffb6dda7c 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 91eb5d5da1 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new 3fe3301a34 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new c99be5a6ea 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new 85eb21f8a0 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new dc6cc16cf7 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 41944fce10 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new dd203c522e 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 1593dd0436 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new 8e909ac5d6 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 9ea5052770 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new e2bdbc8861 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 2743ddbd8c 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 5a0995cb66 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new b71d3ee0e6 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new 6acb35ea7b 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new 527531918f 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new bd4d873f79 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new 227b2b05da 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new 6f4f3e9e5e 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] new 1c355c7db0 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] new eed68c677b 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] new b177c83a6b 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] new b78127b9c0 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] new 94a59598b8 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] new fd91f7412a 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new ad6a86138f 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] new b42de736b2 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] new 40a3801879 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] new 504e7bebec 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] new 57be19e536 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] new 284b907b16 197: onsuccess: #2348: 1: Success after linux: 190 commits new b35edeaf03 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] new 2d4ed916ee 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] new 299b4fdd58 200: onsuccess: #2427: 1: Success after binutils: 274 commits new 4ffcac9584 201: onsuccess: #2430: 1: Success after glibc: 26 commits new 974e751cbb 202: onsuccess: #2431: 1: Success after linux: 944 commits new c753204540 203: onsuccess: #2433: 1: Success after binutils: 27 commits new 471413d723 204: onsuccess: #2435: 1: Success after linux: 3 commits new 7860e5a585 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] new e231d03abb 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] new d9f0afd5d9 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] new a1b809a716 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] new 6fb8569fe7 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] new 3116d312f2 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits new 6877597091 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new 331e62c0e2 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] new b7a4a5c335 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] new 7ab1fc0c01 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] new ca9923f78c 215: onsuccess: #2455: 1: Success after binutils: 3 commits new d265431036 216: onsuccess: #2457: 1: Success after linux: 1736 commits new 0df19d485e 217: onsuccess: #2459: 1: Success after binutils: 3 commits new 3d1f75d9b1 218: onsuccess: #2461: 1: Success after linux: 916 commits new 7c0ac5ebc0 219: onsuccess: #2463: 1: Success after binutils: 3 commits new 1f04685215 220: onsuccess: #2465: 1: Success after linux: 572 commits new eb9998360e 221: onsuccess: #2467: 1: Success after binutils: 3 commits new eb859c5319 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new f1530656a5 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new c7f91cede4 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new 78a586a942 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 8dfb36b3f9 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new e2a6b01f4d 227: onsuccess: #2474: 1: Success after gcc: 2 commits new f5e0783940 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new eeed96f399 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new 463ad93d4f 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new a7b078be4c 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 357a560dcf 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new a60c7f064a 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new e9b67b99bc 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new ef8af4cc3f 235: onsuccess: #2483: 1: Success after linux: 108 commits new 325287aa66 236: onsuccess: #2484: 1: Success after gcc: 2 commits new bdd80c965d 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new 505eae0381 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new e6a05544eb 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new b6c5575c25 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 2fedcd818d 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new bbb17f6ac1 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new 12773013db 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new a758b192c6 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new e3ee909477 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new dce4e1793c 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new 1fcddf8f3d 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new 31f357dd6c 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 6d7084ba32 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new db100e2aca 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 9c278ad4c8 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new d70e73ef46 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 5506620121 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 9bf6e8e6e4 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new b98c632431 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new c51282a977 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 0bb6b34862 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...]
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 (19049c4023) \ 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 1768 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 32428 -> 32140 bytes 04-build_abe-stage1/console.log.xz | Bin 74144 -> 74012 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8824 -> 8812 bytes 07-build_abe-glibc/console.log.xz | Bin 247272 -> 245508 bytes 08-build_abe-stage2/console.log.xz | Bin 207516 -> 205112 bytes 09-build_abe-gdb/console.log.xz | Bin 39696 -> 39452 bytes 10-build_abe-qemu/console.log.xz | Bin 31728 -> 31484 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3928 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2844 -> 3356 bytes 13-check_regression/console.log.xz | Bin 7268 -> 7072 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 10 +- 13-check_regression/mail-body.txt | 108 +- 13-check_regression/results.compare | 66 +- 13-check_regression/results.compare2 | 130 +- 13-check_regression/results.regressions | 66 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 110 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 66 +- sumfiles/g++.log.xz | Bin 3408756 -> 3406004 bytes sumfiles/g++.sum | 128 +- sumfiles/gcc.log.xz | Bin 3039500 -> 3040560 bytes sumfiles/gcc.sum | 5686 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1039212 -> 1037492 bytes sumfiles/gfortran.sum | 104 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 214504 -> 214596 bytes sumfiles/libgomp.sum | 21 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 438172 -> 431384 bytes sumfiles/libstdc++.sum | 69 +- 43 files changed, 3495 insertions(+), 3193 deletions(-)