This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm in repository toolchain/ci/base-artifacts.
discards de5703d5064 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 9e5b542a1a4 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 9f5c9c3c793 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gl [...] discards 56bcb2678dc 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards a525d5d4045 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards d5834b95a86 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] discards cf7f1eb4a02 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] discards ae6f3729748 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 13e7058a3a9 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards f36b3751c90 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] discards 3cf0dc7582f 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards c73309c9372 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 9b12767ce62 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 720d2c51885 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 5a1c5d97400 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards b07ec9c4ef6 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 4f82be7f064 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 14a45f6097d 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards 5f4fb11dd88 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 777c0bcaab8 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 24365d5c281 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards f8134f8904a 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards dcb1cff0286 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards f1e3e790c3c 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards 8e73e722fab 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 5efec1478e7 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 3a195f0439f 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 33a363eebf2 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 5ea1b649b1b 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards a6db7ac5559 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards edb497ce2d9 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 03db5fc1de9 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 04a80b6feb1 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 681fa0d4adb 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 658774bb0a3 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 48f632c64d8 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 0247e36c3a9 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 14c62fb0e77 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 5eacc0feff2 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards baddeef55e3 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards ea6500f738c 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards bd58720d63b 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 8328fc5b4c8 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 23dc5c75daa 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 83dec5ec7f2 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 820c72f3b0b 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 04bca5efb38 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards 4ccefb689b0 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards 03eeb318693 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards 4375338b943 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 808ad48ad81 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards e240a28d4bd 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 391adfb4a36 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 046406c1630 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 937c96840e4 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 9cfca273bfd 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards bb3d63af66d 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 5353666c86c 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 337510b50dd 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 018afb09fec 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards ce44355f856 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards 8d76214155d 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 98d86ecdc1f 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards e17efe0d09e 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards fb7b44588fe 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 1a5bfe5c6d9 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 0b333cfab8e 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards c426fb8df3a 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards 67a0fff23d7 162: onsuccess: #624: 1: Success after linux: 10 commits discards 0dca71117e1 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 32f185d9c1f 160: onsuccess: #621: 1: Success after gcc: 11 commits discards c39e319f1c2 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 80fd45b1947 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards d8f587af580 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 8fb7a9ca5d8 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 57378156493 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 50bd316c51f 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards c3726fd77c7 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards 118d6e89967 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards 95f9c57e407 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 7840803ddb9 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 4eea8ac3388 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 61d06b064e7 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards f01866a975d 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 546386c9793 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards a4d12048f6d 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 0dbe369448a 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards 4c144c91dc8 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 9b1a69a881b 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards fedefb324c0 141: onsuccess: #601: 1: Success after linux: 794 commits discards 4dafde96d4b 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 432c0e4cfe3 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 9d429ce7565 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards c8ebdf51d19 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 82e98e3d340 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 9c75560e162 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards cd6bac438b9 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 84dd60f5109 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards ca6cf9c519e 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 92a74456dc2 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 1e18927a462 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 221f2175f9a 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 60da23db4df 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 5605b2d7e82 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 37f3f939bb0 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 06af771c72d 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new ea1cab3e3a1 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new b34a5c07920 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new cf1dd0f4804 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 5f7e861eeb9 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new f64bc43d7ae 139: onsuccess: #599: 1: Success after binutils: 10 commits new 1455e624993 140: onsuccess: #600: 1: Success after gcc: 23 commits new 71c5edc09a8 141: onsuccess: #601: 1: Success after linux: 794 commits new 4dab32c5b38 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 839d13503f2 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 34354aea769 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new e41fc0b491c 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new fbd07bc2fb1 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 113488129a8 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new aa42bcad321 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 25fb4ceb87b 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new ec19c0d7911 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new a41df6cdb3d 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new d1a3016ee5a 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new 4223bcafe3d 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new 1bbd6af514f 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new 00a248c6a9f 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 480bd9319b5 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 50ba4ee9ec5 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new f473892353e 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 6bc8857d061 159: onsuccess: #620: 1: Success after binutils: 12 commits new 89da4e57bd6 160: onsuccess: #621: 1: Success after gcc: 11 commits new 78511ee0114 161: onsuccess: #623: 1: Success after glibc: 9 commits new ba3409a1e34 162: onsuccess: #624: 1: Success after linux: 10 commits new c53706510a8 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new 8a600f14822 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 883329ff91d 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 0257a5dcb62 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 427ffdc72c4 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 426b8bba5b0 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 3bae3b969c5 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 6e77b98b1f6 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new 378a82e3b7d 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 935d1a91639 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 8b9964400d9 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 5b6e9f718e5 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 3159384290f 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new f6b1b0b2b59 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 2a450cfba57 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 80597f133a3 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 9881f4c3b41 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 789fec07d1e 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new b6ed909e3f0 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 928501200a5 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new dba84ad322d 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new 4b500f2b043 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new cc58d781611 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 26a475824ca 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new a03bb077564 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 091241f655b 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new ef4c1a8c9ea 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 17be0b21676 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 441b5ae0455 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 5cb79abe4db 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 51bff15cc2a 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new a3c692eebde 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 99e31bb41ac 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 5c05dad4168 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new b0e62881704 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new a0ad0dc4998 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new cae251951eb 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new f67cc7eaf0e 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new e6e86018b5d 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 4877fe59c94 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 3f9fec8b322 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 317e0a6df7c 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 4b26c1b7ab7 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 44831a94670 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new b578f749cfb 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new 33a339ee147 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new b5f22808f75 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new c9eb46a18d3 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 5193a204249 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new ff386b020da 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new c162da7beb0 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new 04315c6b854 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new e61312b2576 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 52ae31a53df 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 840ab06d727 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 55bef8a03f8 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new f7a0d6c59ec 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new c2375de80fa 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new 1ba8a6df0b5 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] new 6417e739ea2 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new edbe153442a 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 7436bde0139 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] new 270f123ee41 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] new 6b66651de2c 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new fcba062ef83 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 0196068e641 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gl [...] new ab275027393 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 9d6afde52e1 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 688a8a4bc72 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...]
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 (de5703d5064) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...]
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 2236 -> 2032 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2516 bytes 03-build_abe-binutils/console.log.xz | Bin 49052 -> 48776 bytes 04-build_abe-gcc/console.log.xz | Bin 238088 -> 237308 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8424 -> 8908 bytes 07-build_abe-glibc/console.log.xz | Bin 232588 -> 232884 bytes 08-build_abe-gdb/console.log.xz | Bin 47260 -> 47100 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3772 -> 3772 bytes 10-build_abe-check_gcc/console.log.xz | Bin 9644 -> 10488 bytes 11-check_regression/console.log.xz | Bin 9976 -> 5936 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 1864 +------ 12-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.sep.xz | Bin 76972 -> 61144 bytes sumfiles/g++.log.xz | Bin 2911672 -> 2867044 bytes sumfiles/g++.sum | 279 +- sumfiles/g++.sum.sep | 8651 +++++++++++++++++++-------------- sumfiles/gcc.log.sep.xz | Bin 63696 -> 88796 bytes sumfiles/gcc.log.xz | Bin 2484576 -> 2512792 bytes sumfiles/gcc.sum | 77 +- sumfiles/gcc.sum.sep | 1329 +++-- sumfiles/gfortran.log.sep.xz | Bin 29272 -> 35760 bytes sumfiles/gfortran.log.xz | Bin 953296 -> 952424 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 3794 +++++++++------ sumfiles/libatomic.log.xz | Bin 2280 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 233812 -> 234104 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 9900 -> 11904 bytes sumfiles/libstdc++.log.xz | Bin 469836 -> 469464 bytes sumfiles/libstdc++.sum.sep | 263 +- 43 files changed, 8700 insertions(+), 7691 deletions(-)