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 70781df65cb 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards cf9a2fb59f3 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 2b059f73e3c 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 1e64efa359d 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards b72c1b37ccc 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 842ccc7a48d 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards a1058fb4e8e 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 264961c0cd0 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 622dbe2d1ba 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 9637e5b6bed 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 68b4044439e 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 3f83d0374dd 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 43deab1bd06 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards c81f3ead889 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 7f4a15b2e89 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 4be0cbe776c 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards f5f34a25a42 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 4811b7bc9ed 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 74ac3a041d3 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 35ccccca7e3 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 47ac288c7dd 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards b8db4f91c6b 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards fdd5a4d8192 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 61ab347457e 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards dd15214d915 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] discards 4e7304319d5 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 36e38e8c026 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards c0bc8db7560 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] discards a0cd5f6121e 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] discards 75390cb617d 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] discards efa49dd4cd0 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] discards 74c09ebba37 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] discards 8ae25e73132 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] discards 710785efc9c 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 4e076b5f8a9 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] discards 92b094cd559 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 779402d716a 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 102f6ffc78b 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 907c18db638 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 14b8f5e6cc2 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] discards 9d18c38170b 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] discards b207bcd8f6d 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] discards 96e9e8d75a3 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 3a290f3bc58 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] discards 3ea07e313e2 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards eb1070a685d 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards ad1430eb660 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 3f16ce080d1 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 6e6690355d5 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards fe37527c278 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] discards 70f6af29d63 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 204ecfdd3cd 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 5cd68221ebf 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards d2d48528e97 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 4b1fd0cc035 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards a7070616125 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] discards 281534dc939 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] discards 0c3ee0d3d13 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] discards 59e037633a5 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] discards 9636765f897 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] discards 8b9042a1508 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 3cd2e1e2ca7 152: onsuccess: #903: 1: Success after linux: 22 commits discards ca4312bd4e0 151: onsuccess: #902: 1: Success after glibc: 8 commits discards 7c55ebd4641 150: onsuccess: #900: 1: Success after gcc: 11 commits discards 9cbb7128ce7 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 6be2f712b85 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] discards f96ce5eaed1 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] discards ae8f6cbaab3 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] discards d2b1e2ae607 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 229153151ed 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] discards 64e814c3b82 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] discards 5fe54eaea19 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 1195af95812 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] discards 81c590c169e 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 1674abbf16a 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards b2ffcb933fd 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 21aebe44a32 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 535e488aab1 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 3e7cf5c867b 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards a1b4bf46428 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] discards 24bb3f64a73 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards aad3d947d63 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards f4812db7873 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] discards bb4b34a314f 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] discards ee4fc8bc9a8 129: onsuccess: #878: 1: Success after linux: 3008 commits discards f8ff47e9f98 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 97c4a2637a9 127: onsuccess: #874: 1: Success after linux: 219 commits discards c6869afb151 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 093c2300ac4 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 40c2b10d1c2 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards b01c7a278b4 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards 3480a705ab6 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards e0207d24413 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards 1c7523e47a6 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards 1714067fb27 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards ecd3e9235cf 118: onsuccess: #863: 1: Success after linux: 12 commits discards b3ae14f5912 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 026d1cd84f0 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards 63e2530fbfd 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards 3fe05536d70 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 53a4c69fc02 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new 692ba1dbcb8 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new 637870efff1 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 942ff324f01 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 39996376973 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 101048976ea 117: onsuccess: #861: 1: Success after binutils: 18 commits new 491146b19b2 118: onsuccess: #863: 1: Success after linux: 12 commits new adf8c7a01bc 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new 6309e481687 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new 9c89d1a0d8c 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new cd9818d0ca9 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new 00a60895411 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new 4e6d94f47d1 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new 98d64dc8a62 125: onsuccess: #871: 1: Success after binutils: 26 commits new 4625dcb381f 126: onsuccess: #873: 1: Success after glibc: 2 commits new 9868c32b04d 127: onsuccess: #874: 1: Success after linux: 219 commits new 4926bde6db8 128: onsuccess: #876: 1: Success after binutils: 12 commits new 5d9de271431 129: onsuccess: #878: 1: Success after linux: 3008 commits new 83a4405aa28 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] new d50bb3e983b 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] new 1db1e8e1fc3 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new fca95aed06f 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 78b53607491 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] new a6aa7dcd0f6 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 83a54f2686e 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new cfc7d7165ca 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 7d2f24ffdea 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new a51415e2718 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 6d47bf9aca3 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new a6a3ce12bc3 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] new 0a24b235f37 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 8cbb635ae5b 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] new 95c141758fe 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] new 6b038dbc33b 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 3b7535cb088 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] new 9ebba35bc72 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] new b050b951197 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] new ef46085611b 149: onsuccess: #899: 1: Success after binutils: 15 commits new f051ef97259 150: onsuccess: #900: 1: Success after gcc: 11 commits new 1a3c496ebce 151: onsuccess: #902: 1: Success after glibc: 8 commits new bc7a42576ca 152: onsuccess: #903: 1: Success after linux: 22 commits new 57aaba16227 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new bbb1e2e5324 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] new b298ce87418 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] new 787b00dbe98 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] new 6854c86e1f1 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] new ae96a494bc6 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] new f3e62b7240f 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new eee5aaf87c6 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new fe81be58385 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new be6ec547e4e 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 341666d346f 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 461022b3bde 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] new 65036d0e9be 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 617d1dceba7 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new ff2684abf10 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 6f40a0b4558 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new aac0e2ae1e6 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 0b851231f85 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] new bcb3d97b9bd 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new ada69323f11 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] new 1f2fb37d89c 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] new 39114d2770c 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] new b69a1a8eafe 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 97d433e1c99 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 5b3cb7bbb3e 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new f62bbcab23e 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 1b6f083d5f0 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] new 17e72789e49 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new fb3eb3caab5 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] new c57ab226f8b 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] new 4d9b720d873 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] new d9f1f667e49 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] new 9315ca5788b 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] new a5b0daf7d49 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] new 248bdf46529 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 893f7554c10 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 86decdd61cf 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] new 7f6a39a9788 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new e377e3c83d8 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 290e314e6a2 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new e4276faf40f 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new cf0edca8336 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 9e34557eb2f 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 184d20794f4 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 3149499b61f 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new dd2eb9db5c9 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new f9f583d95cd 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new f462da67ab5 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 7b13c0db49c 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new c02df0c927c 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 9d825aa5afe 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 6b6ef552a23 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 322513110a0 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 3f730efb8f6 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new ada26b8395b 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 596b06ef123 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new c22997cd398 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 6dfcc63c26f 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 85b16ad13e6 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 55a4c8c3e47 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 9f7600ccd95 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new fcf1a296770 214: onsuccess: #19: 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 (70781df65cb) \ 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 1756 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 39284 -> 39264 bytes 04-build_abe-gcc/console.log.xz | Bin 206056 -> 206260 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8368 -> 8696 bytes 07-build_abe-glibc/console.log.xz | Bin 246316 -> 245952 bytes 08-build_abe-gdb/console.log.xz | Bin 38848 -> 38916 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3764 -> 3752 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2736 -> 2812 bytes 11-check_regression/console.log.xz | Bin 7372 -> 6764 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 368 +++++++--------------------------- 12-update_baseline/console.log | 58 +++--- 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 3685956 -> 3695012 bytes sumfiles/g++.sum | 139 ++++++++----- sumfiles/gcc.log.xz | Bin 3243576 -> 3218848 bytes sumfiles/gcc.sum | 362 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1087680 -> 1082992 bytes sumfiles/gfortran.sum | 38 ++-- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 235548 -> 235552 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2684 -> 2684 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 448000 -> 448820 bytes sumfiles/libstdc++.sum | 8 +- 38 files changed, 441 insertions(+), 630 deletions(-)