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 281d28dfead 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 02fd1382745 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards fa0c36480c0 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] discards 4ea3d22989f 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] discards b921ef0bdef 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 7c60e5b21f8 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards a0fab6fa77a 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] discards 33b0cf1bfca 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards 6a4494f16eb 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards f89f3a7869a 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards a6d6e432762 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 226931e58cf 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards affcc0d8c02 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 862bf3d55b4 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 5f3949107fc 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards 82224aa9c8c 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 4a643caa416 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 7c265a61256 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 3c7ce95831e 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 11f83068384 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards a3903094b20 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards e168cc5e31d 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 6668e05a208 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 73722c18f63 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 2a3c931f753 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 208b85c1ff8 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 8dd515691bc 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 1704db54c07 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 21ba5a3399c 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 7ab84b6be81 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 447e4b0c6fe 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards a5b339e248d 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 6b002a5f2f7 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 9379b574b33 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards b482ef50b5a 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards d3c3684820b 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 0bde67e4d47 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 05dde24efdd 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards ebeb64f31e0 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 91fd72cc52e 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards ce4cb1d6828 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 22fcaa34916 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 3f5337e953c 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 66b7bf01629 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards 8fc6dc5b9fd 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards 4732786c400 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards e53f19a8983 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 6294557d98d 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards f1494577cca 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 0346ee56d52 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards e38ad16475a 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 42d35303cfe 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 6cdc3bbbf2f 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards cb777bf8df8 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards b041489db42 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards c2cf4551ed3 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards df27d2bc6f8 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 6cfe6d7f64c 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards 594da3f18e7 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 344f5bff566 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards ee5ad6b4f67 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 68094f837f3 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 35ae7b3c6f8 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 19f91029165 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 115ccda244a 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards 88dcf6bff94 162: onsuccess: #624: 1: Success after linux: 10 commits discards d8d6261b1dd 161: onsuccess: #623: 1: Success after glibc: 9 commits discards e2329eb68fe 160: onsuccess: #621: 1: Success after gcc: 11 commits discards dfee1d341e4 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 698b9cb8413 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 191512e205e 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 66dcb6224f3 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 51eb0e81d24 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 8caa5a4009a 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards f37103dc474 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards dc3f284013d 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards 19bf265f75b 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 5b40fab9898 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards f83b23e32d1 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 3451700a883 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 8b0d90f9c91 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards b8065bdf0a6 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 76102eb9e36 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 2bdbb55a333 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards 8f9706f39c7 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 0a0d4d6b36f 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 18899583b69 141: onsuccess: #601: 1: Success after linux: 794 commits discards 8c91d2784b9 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 11aa4c3808a 139: onsuccess: #599: 1: Success after binutils: 10 commits discards a0488bd0394 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 0ad05732b38 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 118f61f8a01 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards e5bc7131a42 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 1e7eada4def 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 9e1ffb3e1cb 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 3d4692e0dc7 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 208bb6ec2a2 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards d89143d8603 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 7b5923cd3f3 129: onsuccess: #588: 1: Success after linux: 4 commits discards f4b8ead6617 128: onsuccess: #586: 1: Success after binutils: 22 commits discards f620e2bd3f2 127: onsuccess: #584: 1: Success after linux: 21 commits new 90885c2de89 127: onsuccess: #584: 1: Success after linux: 21 commits new 54e16e8a9ee 128: onsuccess: #586: 1: Success after binutils: 22 commits new 116118980ba 129: onsuccess: #588: 1: Success after linux: 4 commits new 5d27225e2e0 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new d8d4d1944ce 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new d338cae2ade 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new ee2db3895ad 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 5f4b6f3ca70 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new a40b79b0388 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 2ce87284f4e 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 4d8d1a0c785 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new ed03b354ac2 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 5e03bca1c17 139: onsuccess: #599: 1: Success after binutils: 10 commits new a5b5483e110 140: onsuccess: #600: 1: Success after gcc: 23 commits new 9a12db58243 141: onsuccess: #601: 1: Success after linux: 794 commits new b3abb86dcfb 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 8caa2c689a8 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 5a5fa2023a7 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new 54df84ce860 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 56cf845a932 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 146bbb83014 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 76f45ae8b0b 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new a9ac3e631f8 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 6c3bae3164e 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 7f5ca61fa16 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new c965397e54f 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new c985d51ee8b 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new aebc19515d8 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new ea7812cfec7 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 25394ad1f23 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 273352ecccf 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new e58323db238 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new bea9c3f85d8 159: onsuccess: #620: 1: Success after binutils: 12 commits new 9a63000edd8 160: onsuccess: #621: 1: Success after gcc: 11 commits new 4d0170a317c 161: onsuccess: #623: 1: Success after glibc: 9 commits new 3ddeafa0263 162: onsuccess: #624: 1: Success after linux: 10 commits new 7697e2f025a 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new 59c419d0577 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 7078c59d2b2 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new c239b332ea0 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 183ac8b1fe9 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 3953af1c439 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 269cc897e9c 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 798a006ab7e 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new b1d3a168c64 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 8007764c5d7 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 52e05a22996 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 1d972328350 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 5b7faa16483 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new a2546e7b2ef 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 6f1bdb16e4f 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 8a37e6b9269 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 9112621b46c 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new a5210a8a3fe 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new bd890ba69ac 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 8324b5b8577 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new f5281fb95e3 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new 22e3330f06d 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new a343af4007e 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new e562c58c96f 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 00bd5ab59e2 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new f7e907af5ce 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 4f6c6247203 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 6ab2a981a14 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new f688530775f 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new dba59e01a9a 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new e1431874691 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new f459c97f759 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 9ee40c344a3 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 2e6b96a8c65 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 9c82d457f70 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 37692d29aaa 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 7f309b9a70a 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 8ac784be2cb 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 2350927f993 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 802005d0013 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new f6d3ff426dc 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 0803601c623 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new b926b71bc1d 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 8a99a8297cd 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 8dfa428d5d3 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new 44df691f6df 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 0f17d57cc72 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new a75a4d2182c 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 437765485a0 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 6e7db891263 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new e76413aeed6 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new a9fdf817641 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 4e0d7c2c19f 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new cb852f68d74 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 5adcff13a91 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 4cdd9e52362 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 43a01c2cf74 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 3b78c2e4d6a 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new a812ece8bd9 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] new 2736333baee 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 9621aaeb497 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 9567119fb60 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] new 3a04281a868 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] new dbf636b0283 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new df0e1d40ab2 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 609e86e4415 228: onsuccess: #28: 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 (281d28dfead) \ 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 1748 -> 2040 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2516 bytes 03-build_abe-binutils/console.log.xz | Bin 49216 -> 48968 bytes 04-build_abe-gcc/console.log.xz | Bin 236148 -> 237688 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8396 -> 8388 bytes 07-build_abe-glibc/console.log.xz | Bin 232532 -> 233788 bytes 08-build_abe-gdb/console.log.xz | Bin 46688 -> 47436 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3820 bytes 10-build_abe-check_gcc/console.log.xz | Bin 10936 -> 9304 bytes 11-check_regression/console.log.xz | Bin 5604 -> 5576 bytes 11-check_regression/results.compare | 26 +- 11-check_regression/results.compare2 | 121 +- 12-update_baseline/console.log | 68 +- 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/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/g++.log.sep.xz | Bin 101148 -> 63168 bytes sumfiles/g++.log.xz | Bin 2879124 -> 2904900 bytes sumfiles/g++.sum | 24 +- sumfiles/g++.sum.sep | 8125 ++++++++++++++++++++------------- sumfiles/gcc.log.sep.xz | Bin 70056 -> 20364 bytes sumfiles/gcc.log.xz | Bin 2509840 -> 2472676 bytes sumfiles/gcc.sum | 7 +- sumfiles/gcc.sum.sep | 5113 ++++----------------- sumfiles/gfortran.log.sep.xz | Bin 46512 -> 38528 bytes sumfiles/gfortran.log.xz | Bin 954884 -> 950104 bytes sumfiles/gfortran.sum | 6 +- sumfiles/gfortran.sum.sep | 3190 +++++++++---- sumfiles/libatomic.log.xz | Bin 2280 -> 2280 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 233812 -> 233884 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2688 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 6416 -> 9052 bytes sumfiles/libstdc++.log.xz | Bin 480148 -> 469848 bytes sumfiles/libstdc++.sum | 4 +- sumfiles/libstdc++.sum.sep | 388 +- 46 files changed, 8395 insertions(+), 8739 deletions(-)