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 e1f95718e55 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 3bdd5e9e2b8 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 402bf1b923a 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 5bfe43a6d9f 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards d982bc1fdcd 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards d8cc8097b0a 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 4a40965110b 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 12938b0e891 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 542ab926617 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards c31f6c07817 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 920f34e2a6d 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 38f2dfbf1c6 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 037e0204808 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards eeeea898fe7 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards c5fd27ce3a9 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 3be871a4265 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards f62ee55b8b8 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards c11dc076733 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 645acf5b5c2 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards f76f7b9d2d7 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 06a963d54d9 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] discards 3022b856af4 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards a4bd33237aa 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards bd63591d5a4 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] discards 0e011268a27 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] discards 0528ad89c45 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] discards 088a1ee02aa 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] discards baf7bcad90c 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] discards 42c8cbc568c 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] discards b0bda69d969 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 2107d65e19f 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] discards c3685d05927 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards ca0893ecc59 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 45e60189dee 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 5cb4eb3d2b9 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 1951fc901e9 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] discards 12672085a7c 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] discards a753e00151b 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] discards 0962fbdf489 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards cc0d54d2a8a 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] discards 576e075cf65 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards ab5c37aacbc 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 3cd8b0e1e35 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards eaa5fd07eae 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 6c1f69e9e72 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 734aecd28c9 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] discards 4fd5749441d 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 5ff0e71fa8c 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 8f853362947 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 583ad65fcbc 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 38cd5794e26 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 06a1347c0df 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] discards 53ef1159ee4 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] discards 75213819ede 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] discards 9479a54bb54 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] discards 54b105df9e3 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] discards e598a4e891a 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards baa9c2f2950 152: onsuccess: #903: 1: Success after linux: 22 commits discards 27dd3b162a9 151: onsuccess: #902: 1: Success after glibc: 8 commits discards 87990f331a3 150: onsuccess: #900: 1: Success after gcc: 11 commits discards fb2616e0f5d 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 2c94e205f92 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] discards 2cda8447ed8 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] discards 64dad78667b 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] discards 42c64b35a0d 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards a5e49781ae5 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] discards 33fa6b7756c 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] discards 88bf4d8746f 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 801de9189f3 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] discards dd9cfb5b36d 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 268e41e92df 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards db9c3679e17 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 91a0c235b8a 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards e19520e9d10 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 12a2dbdb3f0 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 5df1c3514ca 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] discards f8b383c3dce 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 10b451b85bc 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 10895ce71b5 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] discards 79783e95ae8 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] discards ea495fb50a3 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 90fb1e61f14 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 8707db4f104 127: onsuccess: #874: 1: Success after linux: 219 commits discards f98335dc7ab 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 5a2c9f11894 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 0bfa878fa89 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards 4c0f3bc2ad0 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards 97554f155ec 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards 159b157bbc7 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards 8f176e217e2 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards 86308554c7c 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards 1a3b9f67024 118: onsuccess: #863: 1: Success after linux: 12 commits discards 0cee768df1d 117: onsuccess: #861: 1: Success after binutils: 18 commits discards f6078de0d26 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards af923117931 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards fd0e6dd5755 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards e6fb65ac91e 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 13f86b9bd7e 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards e05e8bafa3f 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards f5dfaacb6ef 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 3d5801ef1c4 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 242eec40c1c 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new b7572abbb8b 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new dbd56133254 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new 61e47ba32e6 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 0edfab3138b 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new f762959ab02 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new ccae0987ee3 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new ebc034d8ac1 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 22cf1a57fb5 117: onsuccess: #861: 1: Success after binutils: 18 commits new 1b7556f5050 118: onsuccess: #863: 1: Success after linux: 12 commits new f5895333be2 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new 0dd2c60ed3b 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new a5fae5b2b20 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new fe517d49da2 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new 24914f1b733 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new a7eca1b2bc0 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new d6359e15eed 125: onsuccess: #871: 1: Success after binutils: 26 commits new b9aed14f295 126: onsuccess: #873: 1: Success after glibc: 2 commits new 0f88d510af3 127: onsuccess: #874: 1: Success after linux: 219 commits new df6f4c3f584 128: onsuccess: #876: 1: Success after binutils: 12 commits new b2e42d5544e 129: onsuccess: #878: 1: Success after linux: 3008 commits new 3ddd8788d38 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] new 793c521d111 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] new 52cab16e047 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 04afdf4c4a2 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 89fab4dbae4 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] new c34f0459a54 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 8003caaafdd 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 155ce446137 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new fbe46a2d3d5 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 5133c9957ab 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 7f67d5f86a7 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 34c5ca53878 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] new 379d57dbfdd 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 6d67bb214fb 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] new 94e51fb9321 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] new dd09e099ae2 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new b52a3b5fb34 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] new d7853145cff 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] new 93e5e4b82a0 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] new b18804750d7 149: onsuccess: #899: 1: Success after binutils: 15 commits new 6d6ce7bd048 150: onsuccess: #900: 1: Success after gcc: 11 commits new bef793a95b5 151: onsuccess: #902: 1: Success after glibc: 8 commits new 95f971f86f1 152: onsuccess: #903: 1: Success after linux: 22 commits new 4a93a4dd38f 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 6f27b100006 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] new 2b273d28911 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] new 04f37392192 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] new 0b78bef6fd7 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] new 9547056e2aa 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] new a2fb86a7965 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 3441615eda1 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 28fed67ed63 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 8dca494790a 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 5d3a4070c7a 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new ee8db28cd9b 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] new a5ef0f57551 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new b090c004b41 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 9fa22068e6b 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new e3822d6ee61 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 62d45f5ff65 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new d5dbb7432e0 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] new 2a82010b10d 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 590c2fb3a1c 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] new f888f46497e 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] new e6683904ae4 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] new d702b755882 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new a6cd6e7adea 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 0cb3c2c9b54 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 1d700e3ff46 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 4ba045611ff 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] new 048d1220fd8 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new e0e7a8145db 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] new 8a6b02b67e5 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] new a5917158442 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] new 0b8898b31c7 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] new 0f02e9dc524 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] new 06ff36b79e5 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] new 6dd2ba7521c 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 2a6da2905aa 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 4eedd886f5a 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] new 10bcc264e09 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 1c37b78a235 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new d602a011441 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 61525af08e4 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 9ad0e0a391b 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new db75282f4de 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 5ae9f07caff 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 432889a3cb6 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 57391874701 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 14c8b8c9157 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 7c4eef0de58 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new f3f00347288 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 8e285d2b40e 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new f0c5bd0cebc 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new fd6255a3816 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new b401fa6fd54 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new eebaf00fce5 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 4e10de0f3e9 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 39aa92e7841 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new af7701cb79b 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 2b5c8e647c4 210: onsuccess: #15: 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 (e1f95718e55) \ 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 1760 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 39052 -> 39300 bytes 04-build_abe-gcc/console.log.xz | Bin 205264 -> 205408 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8512 -> 9728 bytes 07-build_abe-glibc/console.log.xz | Bin 245972 -> 246288 bytes 08-build_abe-gdb/console.log.xz | Bin 38724 -> 39072 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3764 -> 3760 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3692 -> 2828 bytes 11-check_regression/console.log.xz | Bin 6664 -> 7100 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 166 ++++++++++++--- 12-update_baseline/console.log | 52 ++--- 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.xz | Bin 3705604 -> 3709808 bytes sumfiles/g++.sum | 167 ++++++++++----- sumfiles/gcc.log.xz | Bin 3214044 -> 3206204 bytes sumfiles/gcc.sum | 387 +++++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1081068 -> 1082984 bytes sumfiles/gfortran.sum | 38 ++-- sumfiles/libatomic.log.xz | Bin 2296 -> 2296 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 235384 -> 235672 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2684 -> 2684 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 444444 -> 447296 bytes sumfiles/libstdc++.sum | 8 +- 37 files changed, 548 insertions(+), 362 deletions(-)