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 6bfdc0fa035 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards 37341ebb089 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] discards 3df1342bb95 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] discards d9921b748dc 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards b3417168928 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 2c4d32f0080 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] discards 0e45b3ec4d7 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards d4dfaa6f873 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 0ea633aa73f 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 29af1ed45de 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 530163b3557 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards cd654ffcc8a 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 02cbb00be59 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards e7f19a32158 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards d49e3342f5d 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 333703f8c0b 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 73e02da8ccd 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 78e7da62be0 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 9304ef8f1b9 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards f2d2a436ca0 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards ec5b7fff7c3 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 6b5ae5e5412 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards c302ab32510 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 1d9c3de02d3 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 89b5dbdecbf 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 8b297dd5117 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards ca9c8189fec 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 73d0ea0ef6e 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards b2170a04721 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards cd6d797450f 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards a2bcb97ecee 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 0974bb26de4 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 312b07fd08b 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 9ed4cf95022 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards bac422cd19b 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 772aaa80fe9 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards e7f6a085727 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 6449efa4f6b 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards c2b1f8ae782 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards aca9ba66c8d 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards e9df2dc89c8 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 7e2baf3272c 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards e55a0927d46 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards 2bca50d9496 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards ca2b96c9323 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards 9923b1397a6 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards bdfe519447e 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards a1f5bc746e4 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 150712fc26d 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 0dcd16e9ff4 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards ba6a32beb9f 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards b1d838d9285 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 6ce21a733a1 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards d92bb0119d7 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 5645230710a 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards a9cf07f7190 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 11112fb7ad3 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards aa04b13ab33 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 58f7ace8a16 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards dc05141445d 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 6d0c9c8cf9e 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 14864bf0caa 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 109a930ea8f 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 27c30c09506 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards 570868b731e 162: onsuccess: #624: 1: Success after linux: 10 commits discards 10cc91598e3 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 8821ad61315 160: onsuccess: #621: 1: Success after gcc: 11 commits discards a4f40a1667c 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 1bd9a1ab611 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 9b749aac43f 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 1839f7cff67 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 1967d49f34f 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 45b983dca67 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards c2f7bdd3bb0 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards fadd77aa849 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards 66af74e9256 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 0e802dbf4b3 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 75c4d8ea1e3 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards bcfcd4e2ab1 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 769f7b45797 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 69be4272fb3 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 5d1782d1dc9 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards d87610cd8ee 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards 56ff285420d 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 16f96990919 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 0558a587bc4 141: onsuccess: #601: 1: Success after linux: 794 commits discards 0e10215f7b1 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 2c3ddbc72ce 139: onsuccess: #599: 1: Success after binutils: 10 commits discards dd6f0e61661 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards b3fe0d5c638 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards eb47395f83b 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards a71233079c6 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards f707e708a92 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 581ba80f179 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 06c880d159a 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 75e9aa1ba1d 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 48b702b676e 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 2d5199f8cba 129: onsuccess: #588: 1: Success after linux: 4 commits discards a1483b686e0 128: onsuccess: #586: 1: Success after binutils: 22 commits discards f66eda167a7 127: onsuccess: #584: 1: Success after linux: 21 commits discards 275815e18a5 126: onsuccess: #582: 1: Success after gcc: 9 commits new e60629f3629 126: onsuccess: #582: 1: Success after gcc: 9 commits new f620e2bd3f2 127: onsuccess: #584: 1: Success after linux: 21 commits new f4b8ead6617 128: onsuccess: #586: 1: Success after binutils: 22 commits new 7b5923cd3f3 129: onsuccess: #588: 1: Success after linux: 4 commits new d89143d8603 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 208bb6ec2a2 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 3d4692e0dc7 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 9e1ffb3e1cb 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 1e7eada4def 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new e5bc7131a42 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 118f61f8a01 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 0ad05732b38 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new a0488bd0394 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 11aa4c3808a 139: onsuccess: #599: 1: Success after binutils: 10 commits new 8c91d2784b9 140: onsuccess: #600: 1: Success after gcc: 23 commits new 18899583b69 141: onsuccess: #601: 1: Success after linux: 794 commits new 0a0d4d6b36f 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 8f9706f39c7 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 2bdbb55a333 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new 76102eb9e36 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new b8065bdf0a6 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 8b0d90f9c91 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 3451700a883 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new f83b23e32d1 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 5b40fab9898 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 19bf265f75b 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new dc3f284013d 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new f37103dc474 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new 8caa5a4009a 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new 51eb0e81d24 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 66dcb6224f3 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 191512e205e 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 698b9cb8413 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new dfee1d341e4 159: onsuccess: #620: 1: Success after binutils: 12 commits new e2329eb68fe 160: onsuccess: #621: 1: Success after gcc: 11 commits new d8d6261b1dd 161: onsuccess: #623: 1: Success after glibc: 9 commits new 88dcf6bff94 162: onsuccess: #624: 1: Success after linux: 10 commits new 115ccda244a 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new 19f91029165 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 35ae7b3c6f8 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 68094f837f3 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new ee5ad6b4f67 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 344f5bff566 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 594da3f18e7 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 6cfe6d7f64c 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new df27d2bc6f8 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new c2cf4551ed3 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new b041489db42 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new cb777bf8df8 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 6cdc3bbbf2f 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 42d35303cfe 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new e38ad16475a 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 0346ee56d52 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new f1494577cca 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 6294557d98d 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new e53f19a8983 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 4732786c400 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new 8fc6dc5b9fd 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new 66b7bf01629 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new 3f5337e953c 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 22fcaa34916 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new ce4cb1d6828 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 91fd72cc52e 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new ebeb64f31e0 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 05dde24efdd 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 0bde67e4d47 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new d3c3684820b 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new b482ef50b5a 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 9379b574b33 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 6b002a5f2f7 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new a5b339e248d 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 447e4b0c6fe 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 7ab84b6be81 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 21ba5a3399c 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 1704db54c07 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 8dd515691bc 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 208b85c1ff8 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 2a3c931f753 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 73722c18f63 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 6668e05a208 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new e168cc5e31d 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new a3903094b20 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new 11f83068384 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 3c7ce95831e 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 7c265a61256 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 4a643caa416 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 82224aa9c8c 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 5f3949107fc 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new 862bf3d55b4 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new affcc0d8c02 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 226931e58cf 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new a6d6e432762 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new f89f3a7869a 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 6a4494f16eb 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 33b0cf1bfca 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new a0fab6fa77a 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] new 7c60e5b21f8 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new b921ef0bdef 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 4ea3d22989f 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] new fa0c36480c0 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] new 02fd1382745 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new 281d28dfead 227: onsuccess: #27: 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 (6bfdc0fa035) \ 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 1744 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 49060 -> 49216 bytes 04-build_abe-gcc/console.log.xz | Bin 235536 -> 236148 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8204 -> 8396 bytes 07-build_abe-glibc/console.log.xz | Bin 233148 -> 232532 bytes 08-build_abe-gdb/console.log.xz | Bin 46484 -> 46688 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3776 -> 3784 bytes 10-build_abe-check_gcc/console.log.xz | Bin 10732 -> 10936 bytes 11-check_regression/console.log.xz | Bin 5332 -> 5604 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 119 +- 12-update_baseline/console.log | 64 +- 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 48292 -> 101148 bytes sumfiles/g++.log.xz | Bin 2881268 -> 2879124 bytes sumfiles/g++.sum | 34 +- sumfiles/g++.sum.sep | 6689 +++++++++++++++---------------- sumfiles/gcc.log.sep.xz | Bin 51504 -> 70056 bytes sumfiles/gcc.log.xz | Bin 2516772 -> 2509840 bytes sumfiles/gcc.sum | 25 +- sumfiles/gcc.sum.sep | 6985 ++++++++++++++++++++------------- sumfiles/gfortran.log.sep.xz | Bin 44964 -> 46512 bytes sumfiles/gfortran.log.xz | Bin 962060 -> 954884 bytes sumfiles/gfortran.sum | 5 +- sumfiles/gfortran.sum.sep | 1435 ++++--- sumfiles/libatomic.log.xz | Bin 2284 -> 2280 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 233792 -> 233812 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2684 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 8724 -> 6416 bytes sumfiles/libstdc++.log.xz | Bin 479208 -> 480148 bytes sumfiles/libstdc++.sum.sep | 270 +- 44 files changed, 8696 insertions(+), 7002 deletions(-)