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 22762dab52e 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 6d3ef0d4725 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards ceb3d1d8b1d 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards dea97f38634 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 02f16bdf1a6 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 0d164ac32b9 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 105722290e8 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 024bb0c3964 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 86b00755ec4 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards c094471ddcf 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 2a998382223 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards a5104136dc0 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 5af05d014e8 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 3e3f59869f7 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards ca6226a25d2 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards e2ddfcf52f0 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 7b4af2b19b4 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards eceb8f915fa 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards c727a6b1720 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 8189d3a75ed 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] discards 1766db7404f 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 50328aa4990 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards a65e3dccc09 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] discards 7773af2a248 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] discards 3744f4531f5 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] discards 17d9d188938 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] discards 635333e98b1 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] discards 72ee714ccba 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] discards 51115a38097 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards f35d571fb0b 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] discards c5870300964 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards e5cf0a3023c 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards f899c2d0740 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards dc3a668d209 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 86d72b09dbe 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] discards f13abde05b7 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] discards ffef902c9d5 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] discards ead6c46fa7d 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards d75a2e08885 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] discards 05fb56155f1 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards cf872ad424f 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 88f7c2e34b8 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 3f681ffdf85 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 4bcae613c37 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 582bf73e748 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] discards 85dabde760e 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards cb51f3150bd 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards d55b71fd96f 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards bd0265e6f6e 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 1042b75bdf0 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 8e96538b249 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] discards 9e4fb0ea2ac 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] discards 4ba5f57d844 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] discards 8e24df7a239 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] discards 68e07f3199a 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] discards d02a7ca0373 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 9e11bc36a67 152: onsuccess: #903: 1: Success after linux: 22 commits discards 35cb4368848 151: onsuccess: #902: 1: Success after glibc: 8 commits discards 10d4308e145 150: onsuccess: #900: 1: Success after gcc: 11 commits discards 7f9c912428f 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 5e276b11aec 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] discards dc24e7e448c 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] discards 998badbbb5d 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] discards 673f78adaf4 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards d5095047e13 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] discards a976368e78f 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] discards 08ff2a3043d 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards bbada53be19 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] discards 6af5c9730af 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 86c10aeeb53 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards d3d528975f6 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 3cb2f4d537e 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards be4828fc2d9 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards b939c926eb3 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 29eb955344b 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] discards 70edb2c8775 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 70535d82cc6 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 4f4d67e856c 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] discards e2fdf4df728 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] discards c48422603c8 129: onsuccess: #878: 1: Success after linux: 3008 commits discards f421fdfde60 128: onsuccess: #876: 1: Success after binutils: 12 commits discards ac3b16d3946 127: onsuccess: #874: 1: Success after linux: 219 commits discards f7449ccc802 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 9ca88a00201 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 556a4db5026 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards 5e693a6575d 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards 94baa056ae1 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards 6e9e7b231fd 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards fbc1d7b3a4a 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards e60577ceca6 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards dcd832996d4 118: onsuccess: #863: 1: Success after linux: 12 commits discards 682dba515d0 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 2f119da0303 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards d8f19ef1f1a 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards a8bd582d858 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards c770cb5e41d 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards d9e9e4c1b66 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards a34590fb548 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 3cf76775669 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards b85e9d9b053 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 4ee708752f7 108: onsuccess: #850: 1: Success after gcc: 2 commits new dee6c0f2fc9 108: onsuccess: #850: 1: Success after gcc: 2 commits new 3d5801ef1c4 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new f5dfaacb6ef 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new e05e8bafa3f 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new 13f86b9bd7e 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new e6fb65ac91e 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new fd0e6dd5755 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new af923117931 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new f6078de0d26 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 0cee768df1d 117: onsuccess: #861: 1: Success after binutils: 18 commits new 1a3b9f67024 118: onsuccess: #863: 1: Success after linux: 12 commits new 86308554c7c 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new 8f176e217e2 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new 159b157bbc7 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new 97554f155ec 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new 4c0f3bc2ad0 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new 0bfa878fa89 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new 5a2c9f11894 125: onsuccess: #871: 1: Success after binutils: 26 commits new f98335dc7ab 126: onsuccess: #873: 1: Success after glibc: 2 commits new 8707db4f104 127: onsuccess: #874: 1: Success after linux: 219 commits new 90fb1e61f14 128: onsuccess: #876: 1: Success after binutils: 12 commits new ea495fb50a3 129: onsuccess: #878: 1: Success after linux: 3008 commits new 79783e95ae8 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] new 10895ce71b5 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] new 10b451b85bc 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new f8b383c3dce 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 5df1c3514ca 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] new 12a2dbdb3f0 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new e19520e9d10 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 91a0c235b8a 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new db9c3679e17 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 268e41e92df 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new dd9cfb5b36d 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 801de9189f3 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] new 88bf4d8746f 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 33fa6b7756c 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] new a5e49781ae5 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] new 42c64b35a0d 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 64dad78667b 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] new 2cda8447ed8 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] new 2c94e205f92 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] new fb2616e0f5d 149: onsuccess: #899: 1: Success after binutils: 15 commits new 87990f331a3 150: onsuccess: #900: 1: Success after gcc: 11 commits new 27dd3b162a9 151: onsuccess: #902: 1: Success after glibc: 8 commits new baa9c2f2950 152: onsuccess: #903: 1: Success after linux: 22 commits new e598a4e891a 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 54b105df9e3 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] new 9479a54bb54 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] new 75213819ede 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] new 53ef1159ee4 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] new 06a1347c0df 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] new 38cd5794e26 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 583ad65fcbc 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 8f853362947 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 5ff0e71fa8c 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 4fd5749441d 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 734aecd28c9 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] new 6c1f69e9e72 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new eaa5fd07eae 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 3cd8b0e1e35 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new ab5c37aacbc 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 576e075cf65 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new cc0d54d2a8a 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] new 0962fbdf489 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new a753e00151b 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] new 12672085a7c 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] new 1951fc901e9 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] new 5cb4eb3d2b9 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 45e60189dee 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new ca0893ecc59 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new c3685d05927 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 2107d65e19f 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] new b0bda69d969 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 42c8cbc568c 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] new baf7bcad90c 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] new 088a1ee02aa 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] new 0528ad89c45 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] new 0e011268a27 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] new bd63591d5a4 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] new a4bd33237aa 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 3022b856af4 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 06a963d54d9 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] new f76f7b9d2d7 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 645acf5b5c2 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new c11dc076733 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new f62ee55b8b8 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 3be871a4265 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new c5fd27ce3a9 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new eeeea898fe7 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 037e0204808 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 38f2dfbf1c6 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 920f34e2a6d 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new c31f6c07817 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 542ab926617 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 12938b0e891 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 4a40965110b 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new d8cc8097b0a 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new d982bc1fdcd 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 5bfe43a6d9f 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 402bf1b923a 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 3bdd5e9e2b8 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new e1f95718e55 209: onsuccess: #14: 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 (22762dab52e) \ 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 1764 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 38776 -> 39052 bytes 04-build_abe-gcc/console.log.xz | Bin 204500 -> 205264 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 10108 -> 8512 bytes 07-build_abe-glibc/console.log.xz | Bin 244148 -> 245972 bytes 08-build_abe-gdb/console.log.xz | Bin 38528 -> 38724 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3752 -> 3764 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3048 -> 3692 bytes 11-check_regression/console.log.xz | Bin 6360 -> 6664 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 108 ++++------ 12-update_baseline/console.log | 44 +++-- 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.xz | Bin 3705328 -> 3705604 bytes sumfiles/g++.sum | 106 +++++----- sumfiles/gcc.log.xz | Bin 3214652 -> 3214044 bytes sumfiles/gcc.sum | 360 ++++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1082940 -> 1081068 bytes sumfiles/gfortran.sum | 38 ++-- sumfiles/libatomic.log.xz | Bin 2296 -> 2296 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 235260 -> 235384 bytes sumfiles/libgomp.sum | 24 ++- sumfiles/libitm.log.xz | Bin 2684 -> 2684 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 445704 -> 444444 bytes sumfiles/libstdc++.sum | 8 +- 38 files changed, 378 insertions(+), 392 deletions(-)