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 688a8a4bc72 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 9d6afde52e1 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards ab275027393 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 0196068e641 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gl [...] discards fcba062ef83 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 6b66651de2c 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards 270f123ee41 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] discards 7436bde0139 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] discards edbe153442a 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 6417e739ea2 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 1ba8a6df0b5 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] discards c2375de80fa 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards f7a0d6c59ec 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 55bef8a03f8 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 840ab06d727 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 52ae31a53df 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards e61312b2576 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 04315c6b854 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards c162da7beb0 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards ff386b020da 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 5193a204249 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards c9eb46a18d3 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards b5f22808f75 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 33a339ee147 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards b578f749cfb 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards 44831a94670 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 4b26c1b7ab7 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 317e0a6df7c 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 3f9fec8b322 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 4877fe59c94 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards e6e86018b5d 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards f67cc7eaf0e 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards cae251951eb 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards a0ad0dc4998 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards b0e62881704 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 5c05dad4168 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 99e31bb41ac 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards a3c692eebde 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 51bff15cc2a 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 5cb79abe4db 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 441b5ae0455 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 17be0b21676 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards ef4c1a8c9ea 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 091241f655b 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards a03bb077564 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 26a475824ca 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards cc58d781611 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 4b500f2b043 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards dba84ad322d 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards 928501200a5 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards b6ed909e3f0 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 789fec07d1e 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 9881f4c3b41 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 80597f133a3 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 2a450cfba57 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards f6b1b0b2b59 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 3159384290f 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 5b6e9f718e5 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 8b9964400d9 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 935d1a91639 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 378a82e3b7d 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 6e77b98b1f6 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards 3bae3b969c5 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 426b8bba5b0 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 427ffdc72c4 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 0257a5dcb62 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 883329ff91d 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 8a600f14822 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards c53706510a8 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards ba3409a1e34 162: onsuccess: #624: 1: Success after linux: 10 commits discards 78511ee0114 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 89da4e57bd6 160: onsuccess: #621: 1: Success after gcc: 11 commits discards 6bc8857d061 159: onsuccess: #620: 1: Success after binutils: 12 commits discards f473892353e 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 50ba4ee9ec5 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 480bd9319b5 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 00a248c6a9f 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 1bbd6af514f 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards 4223bcafe3d 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards d1a3016ee5a 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards a41df6cdb3d 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards ec19c0d7911 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 25fb4ceb87b 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards aa42bcad321 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 113488129a8 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards fbd07bc2fb1 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards e41fc0b491c 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 34354aea769 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards 839d13503f2 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 4dab32c5b38 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 71c5edc09a8 141: onsuccess: #601: 1: Success after linux: 794 commits discards 1455e624993 140: onsuccess: #600: 1: Success after gcc: 23 commits discards f64bc43d7ae 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 5f7e861eeb9 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards cf1dd0f4804 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards b34a5c07920 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards ea1cab3e3a1 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 06af771c72d 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 37f3f939bb0 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 5605b2d7e82 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 60da23db4df 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new ef4b294a0b3 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new f9fb652881b 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 389ab66b08c 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 2b9d36dd47b 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new dca42e17443 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 59fde2a6b81 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 58285c6674f 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 538a586d35d 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 7f4f985a74d 139: onsuccess: #599: 1: Success after binutils: 10 commits new 6001724bff2 140: onsuccess: #600: 1: Success after gcc: 23 commits new 31f367a7be3 141: onsuccess: #601: 1: Success after linux: 794 commits new 62248de7ce4 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new edc1505ca6b 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 88ca1afd8c5 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new c4464cf0eaa 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 2baf70be69b 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 239315a4fb4 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 70c3372339f 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 2260528e6d8 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 5f9333596d2 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new b96839d9dbf 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 8ecc69b5c27 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new cfe4bc04532 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new a76a2502ffd 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new 0bf00103cb8 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 2753396fcb5 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new d87ed2c1368 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 964e4dbf3a6 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 418af3d6e92 159: onsuccess: #620: 1: Success after binutils: 12 commits new 6a77f9bfd93 160: onsuccess: #621: 1: Success after gcc: 11 commits new c7e463c6c41 161: onsuccess: #623: 1: Success after glibc: 9 commits new 1d629ddade2 162: onsuccess: #624: 1: Success after linux: 10 commits new f89d6a1fb9c 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new 644930f8b05 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new c2b6c56c502 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 81288b36abf 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new df867b1f874 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 86e883c9b4c 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 91a7e759947 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 5560623183d 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new 3a2507abbba 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 1140fcefee2 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 16809b6b5a5 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new f250b5492a1 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 624278eac29 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new bd9feb8397e 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 996f697651b 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new ce65531a2a5 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 0d1a749ad2b 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 6ce8156d157 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 5d68cef8b15 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 015bfd31506 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new b77a5282568 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new fe311ed58a1 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new 0d4665e70ce 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 8e64d047f52 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 28764d7b257 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 5a8fe8cd6b8 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new ca8075cdb4e 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 28e0068aa1f 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 3486f56e541 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 506a3731a0a 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 8399344feab 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new aa528a7d455 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 4034a70b6ef 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new b750d29696f 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new abc365060de 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 4c2cdf2f864 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new d426a0135cf 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new c1f00113ae8 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new a104cd1fd66 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new c358dff2f68 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new a3958af5cb9 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 59efc369950 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 4d90a52af5b 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new fb9f4f8db0d 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 19318008900 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new ad3f6b39b1d 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 0c72c8034ab 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 1d760e24c13 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 0c1788a129d 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 10c023d0dc4 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new ea53126a411 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new fafc7fb7ab8 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new dfd4ac17a8f 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 6c41fcca33f 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 87e8d7e51dc 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 58eae4eaade 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 652fc17cae3 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new fd1a27dfbce 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new 1704156cf3b 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] new 41add5933e9 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new f7559731074 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new ee94ac9fa73 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] new 66c15f9f90d 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] new 38e6b467401 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new ac3a413b437 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new a583cd7badc 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gl [...] new a2388eb7e2e 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 1fd91ef65f6 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new f99d31b4e81 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 51a972b909e 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...]

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 (688a8a4bc72) \ 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 2032 -> 2032 bytes 02-prepare_abe/console.log.xz | Bin 2516 -> 2492 bytes 03-build_abe-binutils/console.log.xz | Bin 48776 -> 49508 bytes 04-build_abe-gcc/console.log.xz | Bin 237308 -> 235476 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8908 -> 9096 bytes 07-build_abe-glibc/console.log.xz | Bin 232884 -> 232456 bytes 08-build_abe-gdb/console.log.xz | Bin 47100 -> 47112 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3772 -> 3764 bytes 10-build_abe-check_gcc/console.log.xz | Bin 10488 -> 11160 bytes 11-check_regression/console.log.xz | Bin 5936 -> 4608 bytes 11-check_regression/results.compare | 26 +- 11-check_regression/results.compare2 | 264 +- 12-update_baseline/console.log | 48 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/g++.log.sep.xz | Bin 61144 -> 86148 bytes sumfiles/g++.log.xz | Bin 2867044 -> 2889652 bytes sumfiles/g++.sum | 2 +- sumfiles/g++.sum.sep | 7281 ++++++++++----------------------- sumfiles/gcc.log.sep.xz | Bin 88796 -> 87928 bytes sumfiles/gcc.log.xz | Bin 2512792 -> 2518088 bytes sumfiles/gcc.sum | 2 +- sumfiles/gcc.sum.sep | 6593 ++++++++++++++++++++++++----- sumfiles/gfortran.log.sep.xz | Bin 35760 -> 17384 bytes sumfiles/gfortran.log.xz | Bin 952424 -> 959236 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 3459 +++++----------- sumfiles/libatomic.log.xz | Bin 2284 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 234104 -> 233880 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 11904 -> 6140 bytes sumfiles/libstdc++.log.xz | Bin 469464 -> 481288 bytes sumfiles/libstdc++.sum.sep | 118 +- 44 files changed, 9087 insertions(+), 8768 deletions(-)