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 eb3cdbbeb5b 218: onsuccess: #23: 1: Success after binutils/gcc/linux/gd [...] discards 1753f174d48 217: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] discards df8f930916e 216: onsuccess: #21: 1: Success after binutils/gcc/linux/gd [...] discards 3c4baa9e09c 215: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 82cb557fd8f 214: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 02c63696d34 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 9590fd5f7a2 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 9261f954b94 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 00eb09838f5 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 8a62e607dee 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 83c82d029ec 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards ec4c767f032 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 3df7026a0cb 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 7b73a81800d 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards ce3847d3e07 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards df812d11d53 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 88201aa3d82 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards ffd0f79c1ea 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards a3ecf0c0e14 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 1934f760376 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 72d5cc71f1f 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards a30b2ac8e6a 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards fa06eadb029 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 0230873d471 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 2fafa270d93 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards c1df6845581 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 907c77b7b83 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards b1bd425b3d4 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 5e0d1aaa6ad 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 10f8d068882 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] discards 0e9a9cfddec 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 09b3efdf25d 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 833abd64879 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] discards a7ff866aca1 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] discards 335731061d9 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] discards d48cc5f744e 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] discards b7d2f257eb3 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] discards c3f2e5bdc59 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] discards d8b3031fbb7 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 4ea5c5d8ea5 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] discards 68d45662535 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 4fdf9a1924d 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 9c8de1126ad 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 1f834bc9a37 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 11b81af4c28 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] discards 6df5711ab17 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] discards 406170c3e5f 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] discards b96cbff887e 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 46a88a22de9 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] discards 3556ff6e59e 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 93754d4b994 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards a2369d2e1c1 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 64e7aa3cbcd 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 6a5ac6700f3 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 84662dff131 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] discards a5d3d72754d 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 246d42fbb4c 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 11bdfeb3cc8 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards ed886b9c8ff 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 808beb9ec9d 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 1e463a53e7a 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] discards ea859b72261 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] discards 1570759ff17 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] discards 2520476ee15 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] discards 8da6dc8f8c3 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] discards f88907cd5e2 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards dce12925959 152: onsuccess: #903: 1: Success after linux: 22 commits discards 49cf4127b8d 151: onsuccess: #902: 1: Success after glibc: 8 commits discards b0fcfa0f13a 150: onsuccess: #900: 1: Success after gcc: 11 commits discards 14cd388306c 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 8336f282d31 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] discards 67d22ab3ae3 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] discards 2b47f25b822 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] discards d143c6318b4 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards cd2d15f0d43 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] discards a01280561f2 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] discards 49400d6ad6e 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 4e4dd09c562 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] discards 8608efe8599 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 3169c6c25fd 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards c19297ae581 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 74e2a72837a 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards aadfde6b0bc 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 877cd3d5a6e 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 1b5eaf007f0 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] discards 2205ea7894f 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards ffea63c5315 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 575cbab6f14 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] discards 6fc36c4dc63 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] discards ccb85833b15 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 6c95c633c72 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 54b35d3ed66 127: onsuccess: #874: 1: Success after linux: 219 commits discards 4a181168689 126: onsuccess: #873: 1: Success after glibc: 2 commits discards dded31a795f 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 72c9397c3ef 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards e338be34b69 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards d823c8dc370 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards ba9bdda2e7a 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards 9867fcef0d5 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards 6d5a98f05f5 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards 8ff566bcf94 118: onsuccess: #863: 1: Success after linux: 12 commits new c93ec7c4a76 118: onsuccess: #863: 1: Success after linux: 12 commits new d3f90b2258b 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new 5ba38d83d4e 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new dc03c2fa9c0 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new e9197dba9d2 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new 5c48175b88e 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new 87cc0d9946c 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new 730fe9be685 125: onsuccess: #871: 1: Success after binutils: 26 commits new 98c81278069 126: onsuccess: #873: 1: Success after glibc: 2 commits new 3bbaaf17d06 127: onsuccess: #874: 1: Success after linux: 219 commits new db1dd694dad 128: onsuccess: #876: 1: Success after binutils: 12 commits new 591d221fc60 129: onsuccess: #878: 1: Success after linux: 3008 commits new ce8fc777c3e 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] new 49cb96d4e95 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] new 551cbad1117 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new ca8b67bfab4 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new cce1b3edac3 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] new 257b91fd8c9 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 668bee8628f 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 4d73b52338b 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new a9db8e0f80c 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new db38101441b 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new d83fddfef98 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 6cb90e79a20 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] new ec00434d9f3 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 6bba981c456 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] new e737d44dcf3 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] new 09dd0044504 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new d1c2953a7bb 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] new f18a99a33e1 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] new 3a66f4d3b03 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] new 1492244ebb7 149: onsuccess: #899: 1: Success after binutils: 15 commits new 366f44904b4 150: onsuccess: #900: 1: Success after gcc: 11 commits new bc3b54834fa 151: onsuccess: #902: 1: Success after glibc: 8 commits new 92b66463a0c 152: onsuccess: #903: 1: Success after linux: 22 commits new 776b891e731 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 2f5759da23a 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] new 4a5d4dd11c7 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] new a19155e7dd7 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] new 6b043b08420 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] new ef95fcdbf69 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] new 30c5d7aef27 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 66aefdd84d5 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new e43501ff9df 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new f7e28f083c0 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 99712b7af41 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 0a12719c1a0 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] new 73f8e1af85f 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new e7ead5f559d 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new e6578896338 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 69c12ba1f0a 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 38bd1969ba2 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 8c385f65bc4 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] new 069e37a55ce 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new d3e9640f79d 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] new 6c04a9be816 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] new 060d4b31358 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] new 28639750c7a 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new f64771a459a 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 2c0ae8bd9b8 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new cbfabb80c46 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 405b9694401 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] new 8eb32ce5fdd 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 1269b8a1407 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] new d0c44621118 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] new 8b7bb8cd6f5 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] new af8b96a0169 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] new bc5cd6a5e25 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] new e175d93bf70 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] new 0fa5bff66ea 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 9a34d05e66c 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 3e0decd6248 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] new 204910dac45 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new a49b8cb630d 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 3f61f40d356 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 0d8d49f49c4 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new dd39bce38fe 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 7f9703931bd 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new c844de8241e 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 5d1080b8b9e 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 5515c3a97d7 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 594e84be877 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new b21d72c09b5 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 358fd0941d9 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new f3b96e73d71 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new c54f4b59aa2 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new b813304936e 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new a91fedf6f25 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 7075f9b530e 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new b39afac7914 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new b972a7541cf 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 00b074859e5 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 9d12ee3c36d 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new b0953cd90b9 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 01e18ea9aa1 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 9e95bf62eaf 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 206e21a9c26 214: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 45eb2007e13 215: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new dc447ce9709 216: onsuccess: #21: 1: Success after binutils/gcc/linux/gd [...] new 071505b8be0 217: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] new 5958b4ec8fc 218: onsuccess: #23: 1: Success after binutils/gcc/linux/gd [...] new ca1bed22a6f 219: onsuccess: #24: 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 (eb3cdbbeb5b) \ 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 1768 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2444 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 35440 -> 35408 bytes 04-build_abe-gcc/console.log.xz | Bin 205996 -> 204648 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9928 -> 8940 bytes 07-build_abe-glibc/console.log.xz | Bin 243500 -> 243544 bytes 08-build_abe-gdb/console.log.xz | Bin 35056 -> 34952 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3792 bytes 10-build_abe-check_gcc/console.log.xz | Bin 11664 -> 10332 bytes 11-check_regression/console.log.xz | Bin 7020 -> 4892 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 446 +- 12-update_baseline/console.log | 38 +- 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 | 32 +- sumfiles/g++.log.sep.xz | Bin 117820 -> 61528 bytes sumfiles/g++.log.xz | Bin 3702136 -> 3717628 bytes sumfiles/g++.sum | 2 +- sumfiles/g++.sum.sep | 10710 ++++++++++++++------------------ sumfiles/gcc.log.sep.xz | Bin 126960 -> 75372 bytes sumfiles/gcc.log.xz | Bin 3225508 -> 3208940 bytes sumfiles/gcc.sum | 5 +- sumfiles/gcc.sum.sep | 5621 +++++++++++------ sumfiles/gfortran.log.sep.xz | Bin 27640 -> 21348 bytes sumfiles/gfortran.log.xz | Bin 1083720 -> 1086060 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 2026 +++--- sumfiles/libatomic.log.xz | Bin 2296 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 235640 -> 235292 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2684 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 21412 -> 16836 bytes sumfiles/libstdc++.log.xz | Bin 447692 -> 447008 bytes sumfiles/libstdc++.sum.sep | 23 +- 44 files changed, 9474 insertions(+), 9469 deletions(-)