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 609e86e4415 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gl [...] discards df0e1d40ab2 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards dbf636b0283 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards 3a04281a868 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] discards 9567119fb60 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] discards 9621aaeb497 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 2736333baee 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards a812ece8bd9 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] discards 3b78c2e4d6a 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards 43a01c2cf74 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 4cdd9e52362 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 5adcff13a91 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards cb852f68d74 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 4e0d7c2c19f 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards a9fdf817641 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards e76413aeed6 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards 6e7db891263 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 437765485a0 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards a75a4d2182c 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 0f17d57cc72 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 44df691f6df 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 8dfa428d5d3 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards 8a99a8297cd 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards b926b71bc1d 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 0803601c623 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards f6d3ff426dc 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 802005d0013 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 2350927f993 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 8ac784be2cb 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 7f309b9a70a 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 37692d29aaa 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 9c82d457f70 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 2e6b96a8c65 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 9ee40c344a3 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards f459c97f759 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards e1431874691 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards dba59e01a9a 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards f688530775f 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 6ab2a981a14 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 4f6c6247203 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards f7e907af5ce 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 00bd5ab59e2 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards e562c58c96f 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards a343af4007e 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 22e3330f06d 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards f5281fb95e3 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards 8324b5b8577 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards bd890ba69ac 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards a5210a8a3fe 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 9112621b46c 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 8a37e6b9269 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 6f1bdb16e4f 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards a2546e7b2ef 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 5b7faa16483 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 1d972328350 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 52e05a22996 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 8007764c5d7 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards b1d3a168c64 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 798a006ab7e 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards 269cc897e9c 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 3953af1c439 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 183ac8b1fe9 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards c239b332ea0 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 7078c59d2b2 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 59c419d0577 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 7697e2f025a 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards 3ddeafa0263 162: onsuccess: #624: 1: Success after linux: 10 commits discards 4d0170a317c 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 9a63000edd8 160: onsuccess: #621: 1: Success after gcc: 11 commits discards bea9c3f85d8 159: onsuccess: #620: 1: Success after binutils: 12 commits discards e58323db238 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 273352ecccf 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 25394ad1f23 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards ea7812cfec7 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards aebc19515d8 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards c985d51ee8b 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards c965397e54f 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards 7f5ca61fa16 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 6c3bae3164e 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards a9ac3e631f8 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 76f45ae8b0b 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 146bbb83014 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 56cf845a932 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 54df84ce860 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 5a5fa2023a7 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards 8caa2c689a8 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards b3abb86dcfb 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 9a12db58243 141: onsuccess: #601: 1: Success after linux: 794 commits discards a5b5483e110 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 5e03bca1c17 139: onsuccess: #599: 1: Success after binutils: 10 commits discards ed03b354ac2 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 4d8d1a0c785 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 2ce87284f4e 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards a40b79b0388 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 5f4b6f3ca70 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards ee2db3895ad 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards d338cae2ade 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards d8d4d1944ce 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 5d27225e2e0 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 116118980ba 129: onsuccess: #588: 1: Success after linux: 4 commits discards 54e16e8a9ee 128: onsuccess: #586: 1: Success after binutils: 22 commits new 078a4634d98 128: onsuccess: #586: 1: Success after binutils: 22 commits new 0d1c82f4d90 129: onsuccess: #588: 1: Success after linux: 4 commits new 06186164915 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 730871843a0 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new edea18e5a43 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new cb54ec526d7 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new ff11815c8a6 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 9ba91237d2a 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 7bbfe2d5df7 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new d969226b849 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 89d16d72651 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new affab5c5011 139: onsuccess: #599: 1: Success after binutils: 10 commits new 8a7afc2fc74 140: onsuccess: #600: 1: Success after gcc: 23 commits new b7961e51cf9 141: onsuccess: #601: 1: Success after linux: 794 commits new 4ef0f317cb4 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 6ae39aea05f 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new afe6f7f0375 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new 0178a129764 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 15ecc97e8fc 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 401ff94ab05 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 05ab5f875d7 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new ea1f9215488 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 33c1fb06f7a 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new eac171ea4f0 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 829b7a75a39 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new 14a77e975a4 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new 307b0fcccaa 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new dbe625a62ff 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 148d840f502 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new e223015a672 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 3c0ad7d2805 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 50fcf233b0c 159: onsuccess: #620: 1: Success after binutils: 12 commits new e173f91de0d 160: onsuccess: #621: 1: Success after gcc: 11 commits new b832dd99d80 161: onsuccess: #623: 1: Success after glibc: 9 commits new 425abda21b2 162: onsuccess: #624: 1: Success after linux: 10 commits new 3ae3b0687ae 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new 7e31d433a88 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new f65db080f8f 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new d0271d6d5f8 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 64a57758b4d 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 50fd60d03a7 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 35a47537397 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 9c57f0729da 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new 888d13581f6 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new c48e50d77c1 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new b290977c26c 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new be5b8ff271d 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new af074126e72 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 48ff78d8478 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 8ab3484c058 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 87a5575ee7a 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new f5b11163316 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new f00ff652c04 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 2f0168f6ef9 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 71a88cd0bf5 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new aae70307ab0 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new fcd9cb51d64 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new ac85a8974bc 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 588c4a8c72b 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new ba65777eae6 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 78807c04eab 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new c9da7953de4 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 7f2559ac2a7 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 557d15b826c 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new b8115337e1f 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 2cc4d480aeb 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new f86eb5e8793 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 03948748a97 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new e49652208d0 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 14ebbb39908 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 3373d2d3969 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new d6ab3232367 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new b1e43f03c47 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new b654152b067 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new b56b1f1a58b 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new a6f245a6c25 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 3463ae5841d 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new f925e27f78b 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 52c35787263 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 6e5823b5c1f 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new 0caf893d34a 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new ae85dab48a6 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new abacfc6a4ea 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 0380557ee21 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 327d5524db8 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 4aaad9a14cb 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new 45bec1d35fe 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 4cca520342a 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 286d3307987 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new e93d547af62 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 7946d2cb643 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 59572290413 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 0e04ee8cb78 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new 1d4fa109769 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] new 58876eb0efb 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new e79942c5377 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new be2ee92923e 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] new 66d2bbbecac 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] new c348bcd096c 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new e48a64fe758 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new f87ee3c2d75 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gl [...] new 9c1597d9e6d 229: onsuccess: #29: 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 (609e86e4415) \ 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 2040 -> 2028 bytes 02-prepare_abe/console.log.xz | Bin 2516 -> 2564 bytes 03-build_abe-binutils/console.log.xz | Bin 48968 -> 49012 bytes 04-build_abe-gcc/console.log.xz | Bin 237688 -> 236856 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8388 -> 8396 bytes 07-build_abe-glibc/console.log.xz | Bin 233788 -> 232940 bytes 08-build_abe-gdb/console.log.xz | Bin 47436 -> 47500 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3792 bytes 10-build_abe-check_gcc/console.log.xz | Bin 9304 -> 9116 bytes 11-check_regression/console.log.xz | Bin 5576 -> 5716 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 122 +- 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/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.sep.xz | Bin 63168 -> 81208 bytes sumfiles/g++.log.xz | Bin 2904900 -> 2912268 bytes sumfiles/g++.sum | 57 +- sumfiles/g++.sum.sep | 11625 +++++++++++++++++++------------- sumfiles/gcc.log.sep.xz | Bin 20364 -> 67068 bytes sumfiles/gcc.log.xz | Bin 2472676 -> 2469108 bytes sumfiles/gcc.sum | 6 +- sumfiles/gcc.sum.sep | 905 +-- sumfiles/gfortran.log.sep.xz | Bin 38528 -> 36364 bytes sumfiles/gfortran.log.xz | Bin 950104 -> 949244 bytes sumfiles/gfortran.sum | 6 +- sumfiles/gfortran.sum.sep | 4258 ++++++------ sumfiles/libatomic.log.xz | Bin 2280 -> 2280 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 233884 -> 233936 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 9052 -> 10152 bytes sumfiles/libstdc++.log.xz | Bin 469848 -> 469128 bytes sumfiles/libstdc++.sum.sep | 479 +- 44 files changed, 9356 insertions(+), 8236 deletions(-)