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_gdb/master-aarch64 in repository toolchain/ci/base-artifacts.
discards cec58c3ce6 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] discards 1ea4a1a942 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits discards ae217ca56d 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards b0d3371c51 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards bdd01790de 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards dbed34b2f0 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 06acc769db 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards 34b3973cec 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 34d65e9b52 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards 6039b5ac3a 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards d19452aad4 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards c3f129c0dd 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards 4b946f81b5 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards 095d331b10 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards 7ecba2cbb6 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards f661646e67 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards e2f4d09ff8 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 3a1932c531 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards a9a7377b40 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards 91bc666c16 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 08c4d338a4 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards c98b3159d6 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards f7093a890c 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards 20fc8114a3 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards 7598ab38b5 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards fd4cd42457 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 60e595d3cd 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards 8377902b02 212: force: #45: 1: Success after gdb: 22 commits discards e6eb8ea36a 211: onsuccess: #44: 1: Success after linux: 26 commits discards e600cf964f 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards 85391c8a96 209: force: #37: 1: Success after baseline build: no new commits discards 3d15f4c824 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 063d488858 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards bbc913bf3b 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 5b8c7a72cc 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 7874c998ff 204: force: #26: : Failure after baseline build: no new commits discards 4d0f6a6fc3 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards ce7b91ce86 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards dcd199a28e 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 34b9ffc2a5 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 7a269bea32 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 25a7c71c88 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards d0312db196 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards ed143bdb15 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards d350a08bd9 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 5aa4d3c243 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards d7169dc67b 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards f58cc9aa0e 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 1c399e224d 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 8e14bd0a7f 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards be260e3295 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards d30b77af0b 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 69f869d47d 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards e30644558c 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 9defaaabaf 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 9b312803ef 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards 63ee84798a 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards 871b71e602 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards 78c57dc00a 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards dc6defd504 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards 9d2bccf64d 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards 00435cf868 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards 278daf2027 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards ead6374fe1 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards 8dc61b644b 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards 7c2370a7a3 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards 84686bb612 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards 1f274e4ea6 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards d2e3172ccf 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards 9c4e04bac2 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards e3877a5345 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards 1bc0cda031 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards 7e8d32e87f 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards 4285098682 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards 00d104b3f9 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards fd740b058e 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards f84fbd3d82 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards 719c4b898b 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards ac198c421a 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards 0a52e2b36f 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards 09ae881567 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards 0094dba69b 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 71cdf2d0f1 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards 076457fa47 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards 64efac5de3 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards 0866a1c47d 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards 6bbeab0466 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards 739bac322a 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards b6b55ee5d8 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards 1af12c4881 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards 1bd07dd46e 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards 74e9c546a2 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards da4c367f24 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards ddfdcf7119 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards 6beabfd194 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards 173f73ed88 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards 4bf4cc96f6 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards bb2535e10e 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards 425f72df38 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards f774d07d1c 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards 932cf3e21c 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new 70efde8c17 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new f5ed340a96 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new 6a1a02a797 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new fe27b941a2 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new 8528abc0b2 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new 2e039f6ea0 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new f742f99bae 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new 9f60fdc111 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new 144e98212a 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new 3813e186fb 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new cb13b2fa3d 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new 3b8e2d13a5 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new 1b0c8baf61 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new 48ce170cf0 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new fd6b046aeb 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new a24309b28d 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new fe3a60fd53 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new 0e2e16bebc 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new cbad330778 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new ad2d01651f 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 23cb026610 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new afdc171697 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new bb43ac82f1 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new cee38be3dd 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new f4c7e71d70 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new b112ba0b3c 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new 48be4138a2 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new b19588ef9b 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new 8dfd0b3cab 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new abc374549f 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new 8246e57ae0 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new 2b4db8214e 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new bea6f7f034 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new 0f4ee555b9 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new 1c8f946704 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new 3029fa6c61 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new f1b8488af0 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new 6e95b0ef4a 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new c22c42a6c5 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new ddfc19dd1e 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new fe34145386 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new 18644e67f5 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new 58b06bc048 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new e6eba68f47 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new f3df020db6 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new e019adc91d 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new 63d45b479d 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new d570695df3 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 7b9bfb066b 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 80006c0c21 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new bcc5423f9a 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 2d575f3559 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 7db05181e3 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 894b57e85d 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 0840c50c09 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new da6c3bdc1a 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new fe5bb1f0da 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 5f6c8eae7e 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 5402db83ae 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new c424f4881e 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 1f61bdc6e4 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 712e23bad0 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 27d5db3125 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 6b5e93735b 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 64956d05b3 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 7b437074ca 204: force: #26: : Failure after baseline build: no new commits new b5e1089b36 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 79f313bf45 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 0d32d6756c 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new fe1380ba80 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 1488888bd6 209: force: #37: 1: Success after baseline build: no new commits new 07f654e1b8 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new eed8b00321 211: onsuccess: #44: 1: Success after linux: 26 commits new bf2ef85f5a 212: force: #45: 1: Success after gdb: 22 commits new 645ac075c9 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new 97661feb68 214: onsuccess: #47: 1: Success after gdb: 21 commits new f97d0bcba4 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new 048b45b0f7 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new c9cb803c3f 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new e0aabc5cfe 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new c09de1065e 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new a4e5d635df 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new afddf5f741 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 36b4ca9cbb 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new 7e0d32c124 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new 6601e06ae2 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 226bbbd085 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new 3e76183513 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new ea23a510db 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new a9d97e8f43 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new 8621d77109 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new ad2aaf43bd 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new 81eccc3785 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new 7451f2362a 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new 3e8df3a4c3 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new 29e056215b 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 6b051e167c 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new 4a3c6d9234 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new 1e7a1d48f6 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new 8bc8ce8a59 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits new e3aa4d038e 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] new 3898eee693 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...]
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 (cec58c3ce6) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/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 2024 -> 2080 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2528 bytes 03-build_abe-binutils/console.log.xz | Bin 35476 -> 34952 bytes 04-build_abe-gcc/console.log.xz | Bin 203424 -> 203604 bytes 06-build_abe-linux/console.log.xz | Bin 9424 -> 8484 bytes 07-build_abe-glibc/console.log.xz | Bin 241344 -> 240648 bytes 08-build_abe-gdb/console.log.xz | Bin 35292 -> 34688 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3888 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3268 -> 2640 bytes 11-check_regression/console.log.xz | Bin 5788 -> 5132 bytes 11-check_regression/results.compare2 | 105 +++++++++++++++----------------- 12-update_baseline/console.log | 38 ++++++------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 51 +++++++--------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 36 ++++++----- manifest.sh | 32 +++++----- sumfiles/gdb.log.0.xz | Bin 1920276 -> 1988900 bytes sumfiles/gdb.log.1.xz | Bin 27728 -> 28456 bytes sumfiles/gdb.log.2.xz | Bin 14864 -> 0 bytes sumfiles/gdb.sum | 41 +++++++------ sumfiles/gdb.sum.0 | 37 +++++++----- sumfiles/gdb.sum.1 | 18 +++--- sumfiles/gdb.sum.2 | 110 ---------------------------------- 28 files changed, 181 insertions(+), 299 deletions(-) delete mode 100644 sumfiles/gdb.log.2.xz delete mode 100644 sumfiles/gdb.sum.2