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-aarch64 in repository toolchain/ci/base-artifacts.
discards ca1bed22a6f 219: onsuccess: #24: 1: Success after binutils/gcc/linux/gd [...] discards 5958b4ec8fc 218: onsuccess: #23: 1: Success after binutils/gcc/linux/gd [...] discards 071505b8be0 217: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] discards dc447ce9709 216: onsuccess: #21: 1: Success after binutils/gcc/linux/gd [...] discards 45eb2007e13 215: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 206e21a9c26 214: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 9e95bf62eaf 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 01e18ea9aa1 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards b0953cd90b9 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 9d12ee3c36d 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 00b074859e5 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards b972a7541cf 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards b39afac7914 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 7075f9b530e 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards a91fedf6f25 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards b813304936e 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards c54f4b59aa2 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards f3b96e73d71 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 358fd0941d9 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards b21d72c09b5 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 594e84be877 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 5515c3a97d7 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 5d1080b8b9e 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards c844de8241e 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 7f9703931bd 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards dd39bce38fe 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 0d8d49f49c4 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 3f61f40d356 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards a49b8cb630d 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 204910dac45 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 3e0decd6248 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] discards 9a34d05e66c 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 0fa5bff66ea 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards e175d93bf70 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] discards bc5cd6a5e25 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] discards af8b96a0169 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] discards 8b7bb8cd6f5 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] discards d0c44621118 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] discards 1269b8a1407 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] discards 8eb32ce5fdd 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 405b9694401 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] discards cbfabb80c46 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 2c0ae8bd9b8 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards f64771a459a 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 28639750c7a 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 060d4b31358 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] discards 6c04a9be816 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] discards d3e9640f79d 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] discards 069e37a55ce 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 8c385f65bc4 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] discards 38bd1969ba2 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 69c12ba1f0a 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards e6578896338 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards e7ead5f559d 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 73f8e1af85f 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 0a12719c1a0 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] discards 99712b7af41 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards f7e28f083c0 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards e43501ff9df 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 66aefdd84d5 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 30c5d7aef27 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards ef95fcdbf69 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] discards 6b043b08420 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] discards a19155e7dd7 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] discards 4a5d4dd11c7 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] discards 2f5759da23a 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] discards 776b891e731 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 92b66463a0c 152: onsuccess: #903: 1: Success after linux: 22 commits discards bc3b54834fa 151: onsuccess: #902: 1: Success after glibc: 8 commits discards 366f44904b4 150: onsuccess: #900: 1: Success after gcc: 11 commits discards 1492244ebb7 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 3a66f4d3b03 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] discards f18a99a33e1 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] discards d1c2953a7bb 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] discards 09dd0044504 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards e737d44dcf3 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] discards 6bba981c456 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] discards ec00434d9f3 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 6cb90e79a20 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] discards d83fddfef98 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards db38101441b 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards a9db8e0f80c 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 4d73b52338b 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 668bee8628f 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 257b91fd8c9 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards cce1b3edac3 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] discards ca8b67bfab4 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 551cbad1117 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 49cb96d4e95 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] discards ce8fc777c3e 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] discards 591d221fc60 129: onsuccess: #878: 1: Success after linux: 3008 commits discards db1dd694dad 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 3bbaaf17d06 127: onsuccess: #874: 1: Success after linux: 219 commits discards 98c81278069 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 730fe9be685 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 87cc0d9946c 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards 5c48175b88e 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards e9197dba9d2 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards dc03c2fa9c0 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards 5ba38d83d4e 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards d3f90b2258b 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new d5aa5741dd7 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new 53b0d6004c6 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new dbd990ec5ad 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new 9cded299a31 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new 2a5ea84cc6a 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new 27380ca2db1 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new e74f3968cb1 125: onsuccess: #871: 1: Success after binutils: 26 commits new a51b1321aa7 126: onsuccess: #873: 1: Success after glibc: 2 commits new 6048e86b4f2 127: onsuccess: #874: 1: Success after linux: 219 commits new f050d6da824 128: onsuccess: #876: 1: Success after binutils: 12 commits new 1d252650d6a 129: onsuccess: #878: 1: Success after linux: 3008 commits new 86337aed854 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] new 11bcf37e7a9 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] new 520c903f951 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 3485c96cd09 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 7202c04b851 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] new df5e4558a72 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 554fdc82040 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new e8776fa07ec 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new df67c868a2f 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 6b71fc38b05 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 1733f0b6fec 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 40eba2dbc08 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] new 815618c0dbc 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 071ccb46748 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] new 2d4278bb810 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] new 9a1c825ad9f 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new fd5736e1955 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] new e642ae9d2d5 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] new 7c89701ab19 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] new 9d9ba331be8 149: onsuccess: #899: 1: Success after binutils: 15 commits new f2d8e500f39 150: onsuccess: #900: 1: Success after gcc: 11 commits new 57f7c108f41 151: onsuccess: #902: 1: Success after glibc: 8 commits new 3db4b8c2489 152: onsuccess: #903: 1: Success after linux: 22 commits new 76084cf4e91 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new ab1ddaf0b29 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] new 8112893e5e6 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] new 091d4fe01b2 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] new 2e4de0e5a62 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] new 3ee6fa377fd 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] new 4b4b9db0ccd 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new efe7d8a3f18 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 8c15a1731c0 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new d70626bacfb 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 63e7899c911 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new c534d23c7f0 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] new 6db3306d46a 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 4f750cd4ea2 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 24c46ecdc0d 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 3e63200f50a 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 043d0fc5829 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new feeea32aec2 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] new b1c51667865 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 255a3df0f65 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] new 3764c5cc70d 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] new 2c953a972d6 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] new 4d61fbfe866 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new faec4e943ae 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 9a4096b336d 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 071723a959c 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 2a195c5cc51 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] new 3e849c84dfd 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new db2ee1578ff 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] new cb9ac3f2915 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] new 41fbc15fa73 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] new dd4f35926c0 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] new 04db2599b84 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] new 6a2d7493756 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] new b42168fa931 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 8bf18012bbe 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new a688e7911a0 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] new 18d93a4bcf1 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 8b90dd77dac 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new dca6f49eaa3 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 97bc767c3b2 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new ccec09439ee 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 7a8d58adf43 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 3df6ad6aff8 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new f8c45550b0b 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 1348a699bad 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 2f8cd21b5bb 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 56fed07045c 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 8ba1142a134 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new d2072814f1d 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 410aee7aabd 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 0dfbfefe908 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new aab1de26507 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 8ee8d236c84 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new c254b6855f2 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new b32888d1125 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new a8b661fb93f 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 2410982b935 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 520d5b1fb66 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 2b01540fba1 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new d2e10356c68 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 8653b286785 214: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 915b9ec2898 215: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 7a8be560e49 216: onsuccess: #21: 1: Success after binutils/gcc/linux/gd [...] new 8da1af145a8 217: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] new a6563ea098f 218: onsuccess: #23: 1: Success after binutils/gcc/linux/gd [...] new 28c53a6005c 219: onsuccess: #24: 1: Success after binutils/gcc/linux/gd [...] new d07f83b5375 220: onsuccess: #26: 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 (ca1bed22a6f) \ 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 1772 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2548 bytes 03-build_abe-binutils/console.log.xz | Bin 35408 -> 35416 bytes 04-build_abe-gcc/console.log.xz | Bin 204648 -> 205068 bytes 06-build_abe-linux/console.log.xz | Bin 8940 -> 8400 bytes 07-build_abe-glibc/console.log.xz | Bin 243544 -> 242924 bytes 08-build_abe-gdb/console.log.xz | Bin 34952 -> 36084 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3792 -> 3880 bytes 10-build_abe-check_gcc/console.log.xz | Bin 10332 -> 10464 bytes 11-check_regression/console.log.xz | Bin 4892 -> 5580 bytes 11-check_regression/results.compare | 20 +- 11-check_regression/results.compare2 | 94 +- 12-update_baseline/console.log | 36 +- 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 61528 -> 72480 bytes sumfiles/g++.log.xz | Bin 3717628 -> 3683212 bytes sumfiles/g++.sum | 30 +- sumfiles/g++.sum.sep | 10833 ++++++++++++++++++-------------- sumfiles/gcc.log.sep.xz | Bin 75372 -> 75876 bytes sumfiles/gcc.log.xz | Bin 3208940 -> 3235732 bytes sumfiles/gcc.sum | 12 +- sumfiles/gcc.sum.sep | 8894 +++++++++++++++----------- sumfiles/gfortran.log.sep.xz | Bin 21348 -> 25756 bytes sumfiles/gfortran.log.xz | Bin 1086060 -> 1085108 bytes sumfiles/gfortran.sum | 31 +- sumfiles/gfortran.sum.sep | 2857 +++++---- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 235292 -> 235364 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2688 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 16836 -> 32660 bytes sumfiles/libstdc++.log.xz | Bin 447008 -> 450800 bytes sumfiles/libstdc++.sum.sep | 344 +- 43 files changed, 13410 insertions(+), 9797 deletions(-)