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 29083c1810d 217: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] discards ebe6e532d70 216: onsuccess: #21: 1: Success after binutils/gcc/linux/gd [...] discards 0dfbbcb2a59 215: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards ffd63558fce 214: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 0f2924b75f0 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 9ee2e6d355e 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 6cd7d7f2e2f 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 3c495bdab7c 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 98cd24da694 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 2a599865a60 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 291811ee914 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 9d4db0a8952 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 387f4c84a3a 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 5d28eef5708 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards a1925757d05 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 10693dba76f 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards f033481b54b 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards f7f6a298a90 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 91cf4dbd71f 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 423c8190c31 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards a13b1dc0d6f 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 12ecfcbb653 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 5b9c26b0d6b 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards b6730b04c83 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 0c38546e327 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 1bddda13fdc 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 75dac2f8d29 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards ff055f181f1 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 93e52502e3f 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] discards c5eb6941032 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards e6831c2e6c9 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 012393dd4e9 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] discards 9b010da1b7e 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] discards dc31dceefa7 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] discards 2417a409e96 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] discards 98f1b97b858 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] discards d1978591ab9 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] discards 563b6909cab 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 286b6c19dd0 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] discards 3b95095739e 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards c4d073bcc4d 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 01b64eee1b6 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards eb1718e0ae4 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 38bbd879da9 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] discards 69dda0663f1 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] discards dc806860238 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] discards a41c73da526 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 1b4a91e5805 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] discards 97098cfb98f 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards c1559781aa3 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 4a6507a26cd 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 48d3ecde3b0 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards e5c92cf47a5 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 827b2001463 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] discards 6ab628de2bd 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards fc9b5c60d08 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards c653d420a7f 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 02ba42856f3 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards f4c2bcc85e1 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards de6b77be860 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] discards 597be74ebbc 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] discards 8af4e763767 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] discards 53bb1212170 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] discards a4ee98b8a35 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] discards 9c721d6e82b 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards e818c859931 152: onsuccess: #903: 1: Success after linux: 22 commits discards 1b903196928 151: onsuccess: #902: 1: Success after glibc: 8 commits discards df7bde75281 150: onsuccess: #900: 1: Success after gcc: 11 commits discards 71abfaf707d 149: onsuccess: #899: 1: Success after binutils: 15 commits discards d67c0df7e89 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] discards eb91382204c 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] discards 69d16fcc334 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] discards 004379dae22 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 05fee0c474c 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] discards dbe23f1ddc9 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] discards ff79216d0db 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards d0a83df708f 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] discards 2910dfd40e8 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards f9d3908a89d 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards f260f5880a1 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards cd6b4e1db6c 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 943cf01ba00 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards d0a85546c22 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 5eddae7c0e0 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] discards bb8ea5a73aa 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 4da108c5048 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 2a55bb145a2 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] discards c92b8c9487c 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] discards d21ddb240ed 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 14e4096389c 128: onsuccess: #876: 1: Success after binutils: 12 commits discards fdef2a41fd6 127: onsuccess: #874: 1: Success after linux: 219 commits discards ae1411e9d32 126: onsuccess: #873: 1: Success after glibc: 2 commits discards d1fba6d05a6 125: onsuccess: #871: 1: Success after binutils: 26 commits discards f9f1e60f12a 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards ffb09ba5e36 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards 0e32ac8d0dd 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards dcb06c2d879 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards 7ab02d6f344 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards 117846bc1a6 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards 5649990f2f6 118: onsuccess: #863: 1: Success after linux: 12 commits discards 765988e0c00 117: onsuccess: #861: 1: Success after binutils: 18 commits new 27c5de11329 117: onsuccess: #861: 1: Success after binutils: 18 commits new 8ff566bcf94 118: onsuccess: #863: 1: Success after linux: 12 commits new 6d5a98f05f5 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new 9867fcef0d5 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new ba9bdda2e7a 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new d823c8dc370 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new e338be34b69 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new 72c9397c3ef 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new dded31a795f 125: onsuccess: #871: 1: Success after binutils: 26 commits new 4a181168689 126: onsuccess: #873: 1: Success after glibc: 2 commits new 54b35d3ed66 127: onsuccess: #874: 1: Success after linux: 219 commits new 6c95c633c72 128: onsuccess: #876: 1: Success after binutils: 12 commits new ccb85833b15 129: onsuccess: #878: 1: Success after linux: 3008 commits new 6fc36c4dc63 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] new 575cbab6f14 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] new ffea63c5315 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 2205ea7894f 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 1b5eaf007f0 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] new 877cd3d5a6e 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new aadfde6b0bc 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 74e2a72837a 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new c19297ae581 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 3169c6c25fd 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 8608efe8599 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 4e4dd09c562 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] new 49400d6ad6e 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new a01280561f2 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] new cd2d15f0d43 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] new d143c6318b4 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 2b47f25b822 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] new 67d22ab3ae3 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] new 8336f282d31 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] new 14cd388306c 149: onsuccess: #899: 1: Success after binutils: 15 commits new b0fcfa0f13a 150: onsuccess: #900: 1: Success after gcc: 11 commits new 49cf4127b8d 151: onsuccess: #902: 1: Success after glibc: 8 commits new dce12925959 152: onsuccess: #903: 1: Success after linux: 22 commits new f88907cd5e2 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 8da6dc8f8c3 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] new 2520476ee15 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] new 1570759ff17 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] new ea859b72261 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] new 1e463a53e7a 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] new 808beb9ec9d 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new ed886b9c8ff 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 11bdfeb3cc8 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 246d42fbb4c 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new a5d3d72754d 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 84662dff131 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] new 6a5ac6700f3 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 64e7aa3cbcd 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new a2369d2e1c1 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 93754d4b994 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 3556ff6e59e 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 46a88a22de9 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] new b96cbff887e 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 406170c3e5f 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] new 6df5711ab17 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] new 11b81af4c28 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] new 1f834bc9a37 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 9c8de1126ad 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 4fdf9a1924d 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 68d45662535 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 4ea5c5d8ea5 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] new d8b3031fbb7 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new c3f2e5bdc59 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] new b7d2f257eb3 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] new d48cc5f744e 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] new 335731061d9 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] new a7ff866aca1 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] new 833abd64879 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] new 09b3efdf25d 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 0e9a9cfddec 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 10f8d068882 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] new 5e0d1aaa6ad 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new b1bd425b3d4 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 907c77b7b83 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new c1df6845581 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 2fafa270d93 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 0230873d471 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new fa06eadb029 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new a30b2ac8e6a 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 72d5cc71f1f 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 1934f760376 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new a3ecf0c0e14 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new ffd0f79c1ea 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 88201aa3d82 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new df812d11d53 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new ce3847d3e07 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 7b73a81800d 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 3df7026a0cb 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new ec4c767f032 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 83c82d029ec 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 8a62e607dee 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 00eb09838f5 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 9261f954b94 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 9590fd5f7a2 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 02c63696d34 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 82cb557fd8f 214: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 3c4baa9e09c 215: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new df8f930916e 216: onsuccess: #21: 1: Success after binutils/gcc/linux/gd [...] new 1753f174d48 217: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] new eb3cdbbeb5b 218: onsuccess: #23: 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 (29083c1810d) \ 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 1812 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2476 -> 2444 bytes 03-build_abe-binutils/console.log.xz | Bin 35460 -> 35440 bytes 04-build_abe-gcc/console.log.xz | Bin 203444 -> 205996 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8564 -> 9928 bytes 07-build_abe-glibc/console.log.xz | Bin 241712 -> 243500 bytes 08-build_abe-gdb/console.log.xz | Bin 34944 -> 35056 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3792 -> 3800 bytes 10-build_abe-check_gcc/console.log.xz | Bin 9144 -> 11664 bytes 11-check_regression/console.log.xz | Bin 5416 -> 7020 bytes 11-check_regression/results.compare | 26 +- 11-check_regression/results.compare2 | 480 +- 12-update_baseline/console.log | 42 +- 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 88156 -> 117820 bytes sumfiles/g++.log.xz | Bin 3689380 -> 3702136 bytes sumfiles/g++.sum | 34 +- sumfiles/g++.sum.sep | 13515 ++++++++++++++------------------ sumfiles/gcc.log.sep.xz | Bin 64488 -> 126960 bytes sumfiles/gcc.log.xz | Bin 3257984 -> 3225508 bytes sumfiles/gcc.sum | 163 +- sumfiles/gcc.sum.sep | 5574 ++++--------- sumfiles/gfortran.log.sep.xz | Bin 173784 -> 27640 bytes sumfiles/gfortran.log.xz | Bin 1074456 -> 1083720 bytes sumfiles/gfortran.sum | 212 +- sumfiles/gfortran.sum.sep | 4415 ++++------- sumfiles/libatomic.log.xz | Bin 2296 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 235400 -> 235640 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2688 -> 2684 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 13108 -> 21412 bytes sumfiles/libstdc++.log.xz | Bin 453548 -> 447692 bytes sumfiles/libstdc++.sum | 4 +- sumfiles/libstdc++.sum.sep | 242 +- 45 files changed, 9938 insertions(+), 14825 deletions(-)