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 f16224650a6 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 1307f79a6a0 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 48e7cd5d77a 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 19317209603 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 0d5d5b57b28 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 9947fc91bf8 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 86481dc99ba 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards be0ce0bd339 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 6f0622c570f 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 301217f3cd0 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards ceaafad9f37 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 22495f6fb60 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 720886a531d 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards cea3b121a7e 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards b5177a8b970 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 5a7326135dd 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 901d0045a2a 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards e357a156157 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 043304aa4de 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards dda93e93976 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 01b829f4daa 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 597b1dc39f2 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 640919a0bb7 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 35c1e96d66d 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] discards 9348714f234 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards cd1d5f11da9 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 51df8e67135 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] discards b63d48bb8b6 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] discards 24d31b283b8 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] discards 5087c1916c4 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] discards dd7dbdad58c 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] discards d53cb1a3317 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] discards 5e0fe197943 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 342f26b0b67 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] discards 84dd9248b2d 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards b1773e38da9 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 2ebec8e9a2f 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 39addfe042e 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 819834ddb55 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] discards 8a04402235c 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] discards 37040ef1a31 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] discards c047f2657e9 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 03086cdb51d 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] discards 0452aeb30c1 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 602c97a52aa 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards b75979bbd5f 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 2c1be87a4b3 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards cea73aab284 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 455b1238513 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] discards cae4b82cf3b 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 25d196e86da 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 6382e382e62 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 2492d65f903 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards ce12168c973 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 61be27bf4df 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] discards 466ca1a607d 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] discards f6032c4fce1 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] discards d9de1a2175e 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] discards f591eeadc2d 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] discards e236959568a 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards a436e1c0d34 152: onsuccess: #903: 1: Success after linux: 22 commits discards 70e3e1fe17b 151: onsuccess: #902: 1: Success after glibc: 8 commits discards 2c965f3fa0c 150: onsuccess: #900: 1: Success after gcc: 11 commits discards 5e0d5708d48 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 6fde411e269 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] discards baa2f222437 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] discards f9f72368dc4 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] discards d05e1d6791c 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 253f7818e3a 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] discards eb24dab7d92 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] discards 5869ee0a94f 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 46ceed6840d 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] discards a13b786943b 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 97f234e28b2 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 44e85ab2a0e 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 80d4031f6c4 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards b8c46a25898 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 34dd294ee54 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards ccc106a1ae0 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] discards f0b65f41c5f 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards db8f48c119c 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards b6d9c36f2dc 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] discards 2d58ea26161 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] discards 9c0a06005d4 129: onsuccess: #878: 1: Success after linux: 3008 commits discards d46eb83c2a8 128: onsuccess: #876: 1: Success after binutils: 12 commits discards e63b134d8ac 127: onsuccess: #874: 1: Success after linux: 219 commits discards f2f395739dd 126: onsuccess: #873: 1: Success after glibc: 2 commits discards f855cd73637 125: onsuccess: #871: 1: Success after binutils: 26 commits discards c9931f064f2 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards 861c7619eb7 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards 98fac037c8a 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards ee35ae91239 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards dd2846991f9 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards 34dfe7b7a29 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards 8219f0e9a20 118: onsuccess: #863: 1: Success after linux: 12 commits discards 7cfb68534d1 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 67d5e4e6e4f 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards 91d44c322d6 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards b30f4c23dc6 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards e08bf424b7b 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 43fd4b35c79 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 2fe6686687d 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 53a4c69fc02 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new 3fe05536d70 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 63e2530fbfd 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 026d1cd84f0 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new b3ae14f5912 117: onsuccess: #861: 1: Success after binutils: 18 commits new ecd3e9235cf 118: onsuccess: #863: 1: Success after linux: 12 commits new 1714067fb27 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new 1c7523e47a6 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new e0207d24413 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new 3480a705ab6 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new b01c7a278b4 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new 40c2b10d1c2 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new 093c2300ac4 125: onsuccess: #871: 1: Success after binutils: 26 commits new c6869afb151 126: onsuccess: #873: 1: Success after glibc: 2 commits new 97c4a2637a9 127: onsuccess: #874: 1: Success after linux: 219 commits new f8ff47e9f98 128: onsuccess: #876: 1: Success after binutils: 12 commits new ee4fc8bc9a8 129: onsuccess: #878: 1: Success after linux: 3008 commits new bb4b34a314f 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] new f4812db7873 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] new aad3d947d63 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 24bb3f64a73 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new a1b4bf46428 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] new 3e7cf5c867b 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 535e488aab1 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 21aebe44a32 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new b2ffcb933fd 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 1674abbf16a 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 81c590c169e 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 1195af95812 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] new 5fe54eaea19 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 64e814c3b82 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] new 229153151ed 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] new d2b1e2ae607 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new ae8f6cbaab3 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] new f96ce5eaed1 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] new 6be2f712b85 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] new 9cbb7128ce7 149: onsuccess: #899: 1: Success after binutils: 15 commits new 7c55ebd4641 150: onsuccess: #900: 1: Success after gcc: 11 commits new ca4312bd4e0 151: onsuccess: #902: 1: Success after glibc: 8 commits new 3cd2e1e2ca7 152: onsuccess: #903: 1: Success after linux: 22 commits new 8b9042a1508 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 9636765f897 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] new 59e037633a5 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] new 0c3ee0d3d13 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] new 281534dc939 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] new a7070616125 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] new 4b1fd0cc035 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new d2d48528e97 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 5cd68221ebf 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 204ecfdd3cd 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 70f6af29d63 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new fe37527c278 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] new 6e6690355d5 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 3f16ce080d1 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new ad1430eb660 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new eb1070a685d 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 3ea07e313e2 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 3a290f3bc58 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] new 96e9e8d75a3 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new b207bcd8f6d 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] new 9d18c38170b 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] new 14b8f5e6cc2 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] new 907c18db638 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 102f6ffc78b 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 779402d716a 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 92b094cd559 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 4e076b5f8a9 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] new 710785efc9c 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 8ae25e73132 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] new 74c09ebba37 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] new efa49dd4cd0 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] new 75390cb617d 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] new a0cd5f6121e 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] new c0bc8db7560 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] new 36e38e8c026 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 4e7304319d5 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new dd15214d915 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] new 61ab347457e 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new fdd5a4d8192 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new b8db4f91c6b 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 47ac288c7dd 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 35ccccca7e3 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 74ac3a041d3 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 4811b7bc9ed 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new f5f34a25a42 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 4be0cbe776c 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 7f4a15b2e89 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new c81f3ead889 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 43deab1bd06 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 3f83d0374dd 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 68b4044439e 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 9637e5b6bed 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 622dbe2d1ba 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 264961c0cd0 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new a1058fb4e8e 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 842ccc7a48d 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new b72c1b37ccc 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 1e64efa359d 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 2b059f73e3c 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new cf9a2fb59f3 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 70781df65cb 213: onsuccess: #18: 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 (f16224650a6) \ 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 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 39092 -> 39284 bytes 04-build_abe-gcc/console.log.xz | Bin 204756 -> 206056 bytes 06-build_abe-linux/console.log.xz | Bin 8768 -> 8368 bytes 07-build_abe-glibc/console.log.xz | Bin 246824 -> 246316 bytes 08-build_abe-gdb/console.log.xz | Bin 38264 -> 38848 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3768 -> 3764 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2648 -> 2736 bytes 11-check_regression/console.log.xz | Bin 6240 -> 7372 bytes 11-check_regression/mail-body.txt | 28 --- 11-check_regression/results.compare2 | 313 ++++++++++++++++++++++++++++++++-- 12-update_baseline/console.log | 56 +++--- 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 | 30 +--- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++--- sumfiles/g++.log.xz | Bin 3676480 -> 3685956 bytes sumfiles/g++.sum | 6 +- sumfiles/gcc.log.xz | Bin 3251420 -> 3243576 bytes sumfiles/gcc.sum | 281 +++++++++--------------------- sumfiles/gfortran.log.xz | Bin 1078752 -> 1087680 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 235164 -> 235548 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2684 -> 2684 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 444112 -> 448000 bytes 36 files changed, 441 insertions(+), 335 deletions(-)