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 d07f83b5375 220: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards 28c53a6005c 219: onsuccess: #24: 1: Success after binutils/gcc/linux/gd [...] discards a6563ea098f 218: onsuccess: #23: 1: Success after binutils/gcc/linux/gd [...] discards 8da1af145a8 217: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] discards 7a8be560e49 216: onsuccess: #21: 1: Success after binutils/gcc/linux/gd [...] discards 915b9ec2898 215: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 8653b286785 214: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards d2e10356c68 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 2b01540fba1 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 520d5b1fb66 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 2410982b935 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards a8b661fb93f 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards b32888d1125 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards c254b6855f2 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 8ee8d236c84 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards aab1de26507 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 0dfbfefe908 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 410aee7aabd 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards d2072814f1d 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 8ba1142a134 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 56fed07045c 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 2f8cd21b5bb 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 1348a699bad 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards f8c45550b0b 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 3df6ad6aff8 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 7a8d58adf43 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards ccec09439ee 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 97bc767c3b2 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards dca6f49eaa3 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 8b90dd77dac 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 18d93a4bcf1 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards a688e7911a0 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] discards 8bf18012bbe 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards b42168fa931 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 6a2d7493756 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] discards 04db2599b84 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] discards dd4f35926c0 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] discards 41fbc15fa73 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] discards cb9ac3f2915 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] discards db2ee1578ff 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] discards 3e849c84dfd 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 2a195c5cc51 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] discards 071723a959c 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 9a4096b336d 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards faec4e943ae 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 4d61fbfe866 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 2c953a972d6 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] discards 3764c5cc70d 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] discards 255a3df0f65 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] discards b1c51667865 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards feeea32aec2 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] discards 043d0fc5829 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 3e63200f50a 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 24c46ecdc0d 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 4f750cd4ea2 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 6db3306d46a 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards c534d23c7f0 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] discards 63e7899c911 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards d70626bacfb 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 8c15a1731c0 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards efe7d8a3f18 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 4b4b9db0ccd 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 3ee6fa377fd 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] discards 2e4de0e5a62 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] discards 091d4fe01b2 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] discards 8112893e5e6 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] discards ab1ddaf0b29 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] discards 76084cf4e91 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 3db4b8c2489 152: onsuccess: #903: 1: Success after linux: 22 commits discards 57f7c108f41 151: onsuccess: #902: 1: Success after glibc: 8 commits discards f2d8e500f39 150: onsuccess: #900: 1: Success after gcc: 11 commits discards 9d9ba331be8 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 7c89701ab19 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] discards e642ae9d2d5 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] discards fd5736e1955 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] discards 9a1c825ad9f 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 2d4278bb810 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] discards 071ccb46748 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] discards 815618c0dbc 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 40eba2dbc08 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] discards 1733f0b6fec 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 6b71fc38b05 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards df67c868a2f 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards e8776fa07ec 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 554fdc82040 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards df5e4558a72 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 7202c04b851 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] discards 3485c96cd09 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 520c903f951 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 11bcf37e7a9 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] discards 86337aed854 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] discards 1d252650d6a 129: onsuccess: #878: 1: Success after linux: 3008 commits discards f050d6da824 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 6048e86b4f2 127: onsuccess: #874: 1: Success after linux: 219 commits discards a51b1321aa7 126: onsuccess: #873: 1: Success after glibc: 2 commits discards e74f3968cb1 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 27380ca2db1 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards 2a5ea84cc6a 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards 9cded299a31 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards dbd990ec5ad 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards 53b0d6004c6 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new de877a121cd 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new 6172bc6c3f1 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new c6a3170e0e8 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new fb80a9628d1 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new dc47f2265cc 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new eaa92b91f9d 125: onsuccess: #871: 1: Success after binutils: 26 commits new 7b14ac24101 126: onsuccess: #873: 1: Success after glibc: 2 commits new a08ae69bc76 127: onsuccess: #874: 1: Success after linux: 219 commits new 26dd83d4e72 128: onsuccess: #876: 1: Success after binutils: 12 commits new 0124f322845 129: onsuccess: #878: 1: Success after linux: 3008 commits new 2128474ed0f 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] new 55462d75525 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] new 27a0afa2b6b 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 9f3cd9b3baf 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new c987ab6591a 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] new a2deb63fc21 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 66bce3f0b99 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 3ac198b7b68 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 300145f8298 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new e35612f581e 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 3fbdaa08786 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new fa0f3cc1f9d 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] new 966da900870 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new ca9e7741265 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] new a2afcad8742 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] new 728043c8032 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new ff7a4d61dea 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] new 4ad602b87e2 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] new f14798cf6f0 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] new c9661131a6a 149: onsuccess: #899: 1: Success after binutils: 15 commits new 0af76b5158d 150: onsuccess: #900: 1: Success after gcc: 11 commits new cfbdb179ecd 151: onsuccess: #902: 1: Success after glibc: 8 commits new 1af49c2b039 152: onsuccess: #903: 1: Success after linux: 22 commits new 75f0c284b8c 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 89dcc61c262 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] new 2d4593b1054 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] new 7f5c8cd4ff4 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] new 14209657f66 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] new f56bdaa3b76 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] new 20fdfe0ac1d 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new e983ae828d6 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 62e94dc51eb 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 07b04dfeed9 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 9a95dd8566e 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 75b0e51ff33 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] new 996870761db 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new c63443e0b0d 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new b7eb76941ba 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new c326e3a0d54 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 0f1b143eeb2 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new c360a13580e 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] new 7630a72f353 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 762605d4117 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] new d1e25404803 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] new b548745e970 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] new b5916c96f05 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 2d7879acdc7 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 1da51054f81 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new a45d263ed17 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 0f8b892f636 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] new cde143e8065 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 798b12b8780 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] new 0ba0960bce9 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] new d32041125b9 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] new b15ae4b5385 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] new 7488ac7a047 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] new 8b34ee358d9 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] new 4e885ee5a46 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 996080896ef 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 794a8ea63cc 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] new fc5cb6195af 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new dea358d7054 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 599cd3281d6 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new e9fe75b9b10 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 29fb7e86a2b 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 7967e1fee56 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 83c214caa94 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 7908edb24f8 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 1357a8c069c 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 7e5d1181231 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new bb7f82ff7bc 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 8db879fce89 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 3e7378c8694 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 3d136b99863 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new cb25f695740 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new c7363c9d2d9 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 4459016fb7a 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 7a0fa38ce40 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 214375f99ea 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 5cf4c75e369 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new bf56be1d858 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 915150336f6 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 69d370ae9d5 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new c329553de0d 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 67b08e61a08 214: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 9d16afee573 215: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 547d2aa8a33 216: onsuccess: #21: 1: Success after binutils/gcc/linux/gd [...] new b245d370e82 217: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] new dd3b8b3f778 218: onsuccess: #23: 1: Success after binutils/gcc/linux/gd [...] new d08385d41ac 219: onsuccess: #24: 1: Success after binutils/gcc/linux/gd [...] new 4ebea4489f3 220: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new 8cfa7eaaa20 221: onsuccess: #27: 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 (d07f83b5375) \ 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 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2548 -> 2548 bytes 03-build_abe-binutils/console.log.xz | Bin 35416 -> 35032 bytes 04-build_abe-gcc/console.log.xz | Bin 205068 -> 202948 bytes 06-build_abe-linux/console.log.xz | Bin 8400 -> 8472 bytes 07-build_abe-glibc/console.log.xz | Bin 242924 -> 243728 bytes 08-build_abe-gdb/console.log.xz | Bin 36084 -> 35316 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3792 bytes 10-build_abe-check_gcc/console.log.xz | Bin 10464 -> 10268 bytes 11-check_regression/console.log.xz | Bin 5580 -> 5476 bytes 11-check_regression/results.compare | 20 +- 11-check_regression/results.compare2 | 111 +- 12-update_baseline/console.log | 66 +- 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 72480 -> 65596 bytes sumfiles/g++.log.xz | Bin 3683212 -> 3723592 bytes sumfiles/g++.sum | 10 +- sumfiles/g++.sum.sep | 11504 ++++++++++++++------------------ sumfiles/gcc.log.sep.xz | Bin 75876 -> 52908 bytes sumfiles/gcc.log.xz | Bin 3235732 -> 3221964 bytes sumfiles/gcc.sum | 17 +- sumfiles/gcc.sum.sep | 8579 ++++++++++-------------- sumfiles/gfortran.log.sep.xz | Bin 25756 -> 30236 bytes sumfiles/gfortran.log.xz | Bin 1085108 -> 1086448 bytes sumfiles/gfortran.sum | 6 +- sumfiles/gfortran.sum.sep | 2218 +++--- sumfiles/libatomic.log.xz | Bin 2296 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 235364 -> 235636 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2688 -> 2684 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 32660 -> 34812 bytes sumfiles/libstdc++.log.xz | Bin 450800 -> 445052 bytes sumfiles/libstdc++.sum.sep | 363 +- 44 files changed, 9580 insertions(+), 13376 deletions(-)