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 7cfd3530183 211: onsuccess: #44: 1: Success after linux: 26 commits discards 085a5483af6 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] discards f06d8c11bcc 209: force: #37: 1: Success after baseline build: no new commits discards 1aa659feb90 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards af95faeeaec 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards ad206fd51dd 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards cb454f6a114 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 3262487ff22 204: force: #26: : Failure after baseline build: no new commits discards 3b08c5da363 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 2a8af9ecf07 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards f75f48b3177 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 7167d49d80b 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 2d1c0aefeb2 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards f036d3ca9dc 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards bbbb23788ba 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 3a21210ff0b 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 4a7a881e52a 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 8bdeadc876e 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 981bc6f28c0 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 081f2692a9a 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 21aa3629584 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards f87e3f6e27d 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 344b503ae06 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 5de87744b16 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 81864a10e31 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 9b5aae16ab7 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 4bd303a9100 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 47278fa197c 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards f10fe4e71f1 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards e8f3aeacbfd 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards b2e2f99499d 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards 466bf787a45 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards b0296b4f492 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards 34101086ae0 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards 909912d79fe 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards eadb8050a9d 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards 8f936c802fa 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards 601e570adc3 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards 32f4837fbd3 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards 63452f1e68e 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards 2b915e0b313 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards 6af5a1dc85e 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards 33347bfdf84 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 6c4dc4e63f0 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards 890bda69a91 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards b2b918eb245 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 023e6b1ed5e 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards a2d5f3e7cac 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards 1b1bbe75aea 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards a67046587de 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards 7f657c5458c 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards 369b769fd3b 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards c3ad3c9b144 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 06823285680 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 1d78c34607c 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards 6759f56bbe3 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards 5bc86f1f31f 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards f5395f2a0d0 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 24c7ebd9039 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards bca6780fed4 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 044d96b74c1 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 66232d1b03f 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 27b2ad5218e 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 86d7c8c2d86 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards db1038323d8 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards d073d032473 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 8f36e3b0c9a 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 8693882cc94 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards 4782d200ef9 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 9680e5eae02 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards f39c4144cdd 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 44aee06f691 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 5a2e5a19871 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 97364e9e6d5 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 4bff6a84405 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards c002790c611 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards 2a37c6018c0 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards a9ce896f1ee 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards ed294bcf519 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 32398fedf51 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards f749be2d729 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 6e7ad4ed09f 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 8f173a68b68 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards b2b18b3642f 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards 8e98f2bdcdb 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 776cf24b60a 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 96008ec24f4 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 7ba26ae4ebd 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 6ff185a5411 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 7b07b2c0be1 122: onsuccess: #909: 1: Success after linux: 2753 commits discards bf801c14cb8 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 9a715726e00 120: onsuccess: #906: 1: Success after binutils: 29 commits discards a68863caff1 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards b3bc2a33f98 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards ae2efaa4cd4 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 98ba0e9abd9 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards 383fbeac6f0 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards e73106d6cce 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards 2797787edcb 113: onsuccess: #898: 1: Success after linux: 3 commits discards f96cc0e88aa 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 0165f1d1b99 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 373eac1e0db 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 500b5e282c2 112: onsuccess: #896: 1: Success after binutils: 24 commits new 75cbc3cb307 113: onsuccess: #898: 1: Success after linux: 3 commits new b39a1bb9dbb 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 60dbf14e8c3 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new 80ba7ee9b8f 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new c9c555f7c4c 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new 13ed935b62b 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new f802a507552 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 0449b8de305 120: onsuccess: #906: 1: Success after binutils: 29 commits new 5d72b98caaa 121: onsuccess: #908: 1: Success after glibc: 2 commits new 807ed940c3b 122: onsuccess: #909: 1: Success after linux: 2753 commits new e4d426645e0 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new a0c2fddf821 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 7f90ffde1cb 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 80b2bc923e6 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 66226c13177 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 7fc7ffc19e2 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new 4305998d118 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 959abb10622 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new ed3ad75d69b 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 2715e75e3a4 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new be3ed7b72a0 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 244181822a5 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new 4fb767282f0 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new a1940ca2942 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 5d73d7726dc 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new 7840d3a6984 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new 8f0e40f40be 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new c0cca02826d 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new f487e972962 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new de35b02816f 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 353a3ccc04e 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new e89eb5c62da 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new 4a08e6f93e9 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 0634515cc7f 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 02624858365 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new a87b824deb3 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 7455638d24a 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new 258edd0aea9 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 3b115b5ba23 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 57a4381ec6a 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 13015aca80b 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 5b5d13017c6 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new b45f30fc047 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new eb4f1037866 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new 3df6107cc0f 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new 2a1af15e1b0 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 9bea2f16f42 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new 31fe5be9052 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new 2e8d1b67bc5 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new dc9d5bc6802 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new b2193ebd525 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new d20ad959ab7 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 4f7276baada 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new 786d81f1104 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new 0149c00c896 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new 64c7089c474 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new 57640561d70 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new d0adc7c0790 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new e6945c3e689 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new 7ab4910364e 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new 5fff4440790 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new b1d8a059f2e 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new 6cb63bc26c1 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new d6d3d2634f1 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new d0651bdc94c 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new eafdf68a088 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new 6efaae63a47 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new 266e11cf0a7 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new f8b3afadda7 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new ff7bc7d10fe 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new 0da40a0e5b5 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new b5a8a6abf59 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new 3f782da9147 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new b877cd7c2c0 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 2c277c6b22a 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new e49aede0325 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 2695c6342ad 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new ca897c1b2e1 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new b9f98184707 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new fa3bbabbd35 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 4455064d982 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 0afa6fca403 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new ece08b14a78 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 6db724946a2 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 4ddb9c0b43b 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 5c2efb669a7 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 65751224c7f 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new f6578f9cc5f 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new c3c48e632da 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 316b13ffd3d 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 0c09cd15c4c 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new e8814458e63 204: force: #26: : Failure after baseline build: no new commits new b7c2e59088e 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new f200421b5ac 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new fe522b9234c 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 20ab9d2d4b1 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new b0aec775768 209: force: #37: 1: Success after baseline build: no new commits new 0a621975aa2 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] new 671c22d495a 211: onsuccess: #44: 1: Success after linux: 26 commits new c10caf608e2 212: force: #45: 1: Success after gdb: 22 commits

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 (7cfd3530183) \ 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 2020 -> 1964 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2596 bytes 03-build_abe-binutils/console.log.xz | Bin 35384 -> 35288 bytes 04-build_abe-gcc/console.log.xz | Bin 203480 -> 203372 bytes 06-build_abe-linux/console.log.xz | Bin 8384 -> 8456 bytes 07-build_abe-glibc/console.log.xz | Bin 241852 -> 242376 bytes 08-build_abe-gdb/console.log.xz | Bin 34880 -> 34892 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3800 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2956 -> 2716 bytes 11-check_regression/console.log.xz | Bin 4000 -> 3408 bytes 11-check_regression/results.compare | 14 +++++++ 11-check_regression/results.compare2 | 74 +--------------------------------- 12-update_baseline/console.log | 40 +++++++++--------- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 ++++----- sumfiles/gdb.log.0.xz | Bin 1935336 -> 1949676 bytes sumfiles/gdb.log.1.xz | Bin 27008 -> 25288 bytes sumfiles/gdb.log.2.xz | Bin 5208 -> 5200 bytes sumfiles/gdb.log.3.xz | Bin 5420 -> 5420 bytes sumfiles/gdb.sum | 30 +++++++++----- sumfiles/gdb.sum.0 | 30 +++++++++----- sumfiles/gdb.sum.1 | 28 ++----------- sumfiles/gdb.sum.2 | 4 +- sumfiles/gdb.sum.3 | 4 +- 28 files changed, 99 insertions(+), 153 deletions(-)