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 fcf1a296770 214: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 9f7600ccd95 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 55a4c8c3e47 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 85b16ad13e6 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 6dfcc63c26f 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards c22997cd398 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 596b06ef123 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards ada26b8395b 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 3f730efb8f6 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 322513110a0 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 6b6ef552a23 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 9d825aa5afe 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards c02df0c927c 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 7b13c0db49c 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards f462da67ab5 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards f9f583d95cd 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards dd2eb9db5c9 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 3149499b61f 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 184d20794f4 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 9e34557eb2f 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards cf0edca8336 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards e4276faf40f 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 290e314e6a2 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards e377e3c83d8 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 7f6a39a9788 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 86decdd61cf 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] discards 893f7554c10 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 248bdf46529 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards a5b0daf7d49 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] discards 9315ca5788b 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] discards d9f1f667e49 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] discards 4d9b720d873 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] discards c57ab226f8b 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] discards fb3eb3caab5 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] discards 17e72789e49 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 1b6f083d5f0 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] discards f62bbcab23e 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 5b3cb7bbb3e 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 97d433e1c99 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards b69a1a8eafe 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 39114d2770c 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] discards 1f2fb37d89c 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] discards ada69323f11 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] discards bcb3d97b9bd 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 0b851231f85 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] discards aac0e2ae1e6 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 6f40a0b4558 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards ff2684abf10 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 617d1dceba7 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 65036d0e9be 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 461022b3bde 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] discards 341666d346f 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards be6ec547e4e 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards fe81be58385 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards eee5aaf87c6 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards f3e62b7240f 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards ae96a494bc6 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] discards 6854c86e1f1 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] discards 787b00dbe98 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] discards b298ce87418 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] discards bbb1e2e5324 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] discards 57aaba16227 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards bc7a42576ca 152: onsuccess: #903: 1: Success after linux: 22 commits discards 1a3c496ebce 151: onsuccess: #902: 1: Success after glibc: 8 commits discards f051ef97259 150: onsuccess: #900: 1: Success after gcc: 11 commits discards ef46085611b 149: onsuccess: #899: 1: Success after binutils: 15 commits discards b050b951197 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] discards 9ebba35bc72 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] discards 3b7535cb088 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] discards 6b038dbc33b 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 95c141758fe 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] discards 8cbb635ae5b 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] discards 0a24b235f37 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards a6a3ce12bc3 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] discards 6d47bf9aca3 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards a51415e2718 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 7d2f24ffdea 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards cfc7d7165ca 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 83a54f2686e 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards a6aa7dcd0f6 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 78b53607491 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] discards fca95aed06f 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 1db1e8e1fc3 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards d50bb3e983b 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] discards 83a4405aa28 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] discards 5d9de271431 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 4926bde6db8 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 9868c32b04d 127: onsuccess: #874: 1: Success after linux: 219 commits discards 4625dcb381f 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 98d64dc8a62 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 4e6d94f47d1 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards 00a60895411 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards cd9818d0ca9 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards 9c89d1a0d8c 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards 6309e481687 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards adf8c7a01bc 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards 491146b19b2 118: onsuccess: #863: 1: Success after linux: 12 commits discards 101048976ea 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 39996376973 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards 942ff324f01 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards 637870efff1 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 0ba90d14589 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 2dcc8a81913 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 7451b8f7e28 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 77450ac8d3f 117: onsuccess: #861: 1: Success after binutils: 18 commits new 7727b186c8e 118: onsuccess: #863: 1: Success after linux: 12 commits new 2b254d6e5cf 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new edf9a351d8d 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new c378048b444 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new a591c7a1387 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new 9e021fbadc6 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new 6e5802904ec 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new ad9318fcc88 125: onsuccess: #871: 1: Success after binutils: 26 commits new 78cc015b72f 126: onsuccess: #873: 1: Success after glibc: 2 commits new d9583e73f54 127: onsuccess: #874: 1: Success after linux: 219 commits new ba6820d0f30 128: onsuccess: #876: 1: Success after binutils: 12 commits new 2013078e46a 129: onsuccess: #878: 1: Success after linux: 3008 commits new 7654cfddf95 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] new ddfc5f91eaa 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] new 7b45cde994a 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 2572a0675ed 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new af34fe5625f 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] new 6b3bf6c5850 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 451abf3e419 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 27621b9f849 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 9a9e2d34b70 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 001ccbc1264 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 196d8a9e6c7 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 1606f5dc671 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] new 004e5aa0815 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 3cd5fda920b 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] new 40b78cfba4c 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] new ae1b882fc87 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 7cc33050930 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] new ee8ea5a92e4 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] new 116e4ec9574 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] new 23b58c148a1 149: onsuccess: #899: 1: Success after binutils: 15 commits new 7c591933de9 150: onsuccess: #900: 1: Success after gcc: 11 commits new 37e33c093be 151: onsuccess: #902: 1: Success after glibc: 8 commits new 985d58dd5ea 152: onsuccess: #903: 1: Success after linux: 22 commits new 60f9e54f534 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new d28baf34705 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] new 3fb773c1580 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] new 5f0b84902b3 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] new 6585bda02c6 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] new d3014b625b9 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] new b027f4a7dfe 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 40cb708d69f 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new e8c6b0f66cd 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new a8b8b8258b6 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 2063b01016c 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new af9ad9d21fc 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] new 28a0e612f90 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new b1fdabfec6f 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 224e69b4082 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new decff2b3c6d 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 7541f593e6d 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 1e20aa82bd5 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] new 306966820d2 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 4874a4f94b9 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] new 4eb546dbf5e 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] new ceab685939c 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] new c4bc1727abc 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new d35e10638c0 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 4829544ba09 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 863b2c9ff39 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 8aa2db60ed6 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] new 51dcec1f28d 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 3c5b0e15138 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] new 3fe98e9a8fe 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] new 23fedb0b7c2 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] new ab024495d2e 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] new 66be085a5e4 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] new 409b123d1ac 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] new 04a9ae29ace 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new be98d420687 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 765942fed1e 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] new 0c5f33918cd 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 7fda361afab 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 44f75c3d6d1 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 535f1129d44 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 3d4c42f8815 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 8bcb5383a15 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new ac19828af38 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 71b001a35b8 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new e69f64d03d8 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new e361a323d3c 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new d26b80fe3b8 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 35a5fe732b9 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 113168c442d 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 9bc06512d4b 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new e7fa3afc7e0 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new e3f89edccd0 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 0c37d65c2a2 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new d8f8cf02098 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 547feecf2fc 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 71cd68996e6 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 21ea48d59fd 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new d6078f5c3e7 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 2f2b35bf7a7 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 7697e87f25e 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 9a9cc9e2998 214: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new eea3f522797 215: onsuccess: #20: 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 (fcf1a296770) \ 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 1768 -> 1832 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 39264 -> 38824 bytes 04-build_abe-gcc/console.log.xz | Bin 206260 -> 204900 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8696 -> 9064 bytes 07-build_abe-glibc/console.log.xz | Bin 245952 -> 245900 bytes 08-build_abe-gdb/console.log.xz | Bin 38916 -> 38388 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3752 -> 3836 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2812 -> 2692 bytes 11-check_regression/console.log.xz | Bin 6764 -> 7408 bytes 11-check_regression/results.compare | 32 ++- 11-check_regression/results.compare2 | 189 ++++++++++++------ 12-update_baseline/console.log | 50 ++--- 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 3695012 -> 3682944 bytes sumfiles/g++.sum | 167 +++++++++------- sumfiles/gcc.log.xz | Bin 3218848 -> 3229688 bytes sumfiles/gcc.sum | 358 +++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1082992 -> 1081712 bytes sumfiles/gfortran.sum | 38 ++-- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 235552 -> 235400 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2684 -> 2680 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 448820 -> 446320 bytes sumfiles/libstdc++.sum | 33 +++- 38 files changed, 548 insertions(+), 401 deletions(-)