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 c10caf608e2 212: force: #45: 1: Success after gdb: 22 commits discards 671c22d495a 211: onsuccess: #44: 1: Success after linux: 26 commits discards 0a621975aa2 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] discards b0aec775768 209: force: #37: 1: Success after baseline build: no new commits discards 20ab9d2d4b1 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards fe522b9234c 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards f200421b5ac 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards b7c2e59088e 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards e8814458e63 204: force: #26: : Failure after baseline build: no new commits discards 0c09cd15c4c 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 316b13ffd3d 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards c3c48e632da 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards f6578f9cc5f 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 65751224c7f 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 5c2efb669a7 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 4ddb9c0b43b 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 6db724946a2 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards ece08b14a78 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 0afa6fca403 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 4455064d982 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards fa3bbabbd35 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards b9f98184707 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards ca897c1b2e1 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 2695c6342ad 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards e49aede0325 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 2c277c6b22a 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards b877cd7c2c0 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 3f782da9147 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards b5a8a6abf59 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards 0da40a0e5b5 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards ff7bc7d10fe 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards f8b3afadda7 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards 266e11cf0a7 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 6efaae63a47 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards eafdf68a088 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards d0651bdc94c 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards d6d3d2634f1 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards 6cb63bc26c1 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards b1d8a059f2e 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards 5fff4440790 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards 7ab4910364e 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards e6945c3e689 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards d0adc7c0790 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards 57640561d70 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 64c7089c474 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards 0149c00c896 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards 786d81f1104 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 4f7276baada 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards d20ad959ab7 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards b2193ebd525 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards dc9d5bc6802 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards 2e8d1b67bc5 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards 31fe5be9052 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards 9bea2f16f42 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 2a1af15e1b0 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 3df6107cc0f 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards eb4f1037866 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards b45f30fc047 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 5b5d13017c6 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 13015aca80b 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 57a4381ec6a 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 3b115b5ba23 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 258edd0aea9 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 7455638d24a 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards a87b824deb3 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 02624858365 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 0634515cc7f 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 4a08e6f93e9 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards e89eb5c62da 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards 353a3ccc04e 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards de35b02816f 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards f487e972962 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards c0cca02826d 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 8f0e40f40be 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 7840d3a6984 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 5d73d7726dc 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards a1940ca2942 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards 4fb767282f0 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 244181822a5 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards be3ed7b72a0 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 2715e75e3a4 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards ed3ad75d69b 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 959abb10622 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 4305998d118 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 7fc7ffc19e2 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards 66226c13177 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 80b2bc923e6 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 7f90ffde1cb 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards a0c2fddf821 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards e4d426645e0 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 807ed940c3b 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 5d72b98caaa 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 0449b8de305 120: onsuccess: #906: 1: Success after binutils: 29 commits discards f802a507552 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 13ed935b62b 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards c9c555f7c4c 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 80ba7ee9b8f 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards 60dbf14e8c3 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards b39a1bb9dbb 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards 75cbc3cb307 113: onsuccess: #898: 1: Success after linux: 3 commits discards 500b5e282c2 112: onsuccess: #896: 1: Success after binutils: 24 commits new f8a531d238f 112: onsuccess: #896: 1: Success after binutils: 24 commits new 748c3e40c82 113: onsuccess: #898: 1: Success after linux: 3 commits new b4dc6b81f2e 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 809564829b1 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new 43df5d1cdc7 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new d34ae3a039d 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new 6eae1cedcb2 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new 585c6002f06 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 7762b129ae7 120: onsuccess: #906: 1: Success after binutils: 29 commits new a7eefa4fd45 121: onsuccess: #908: 1: Success after glibc: 2 commits new 19bbcb285ca 122: onsuccess: #909: 1: Success after linux: 2753 commits new 256fafec951 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 571862398bf 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 47c52bc6b91 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 7f03f374dc9 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 580fda299e7 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new bdfdad5db34 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new 94d7d2dc0ac 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new c883400d928 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 6f9d1482d55 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new e6475d546a8 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 46d9298ef3e 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new f673c4d0653 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new 60e7291aa64 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 4507c013a1a 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 0e5d737c878 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new 522c9b5c6c0 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new e3fb1ac0bee 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 38bf28fd398 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new d758021033e 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 2b06475c36a 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new b822ea73963 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 826e6e2c7a1 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new f57c6578fab 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 634d717b446 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 39d3862daea 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 91a01282c78 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new bb1123679f5 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new 8abd35a9d7d 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 11b15f7b847 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new ff429a861d0 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 23d8944bdef 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 3fc474b2656 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new dbd05306ff5 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 31b91904e13 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new 5037db2e97c 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new 155c8647dae 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new f653051962f 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new 1e64e7380c6 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new 1fa7afb8994 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new a1e18d53bfe 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new d2ed598f347 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new 09fb6a4cef8 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new ba00f41df80 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new a5a051e76a3 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new 12ed260f714 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new ba0af039e1b 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new 1d1b5162480 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new 2bb92bb00e6 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 2ef3b29caac 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new cb4e3c5a7b8 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new 22d49a7da5f 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new 00baf16a4dc 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new 0ed3d68d64b 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new 7ec203e7dc4 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new 76a9409d7c4 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new b3e82d8c852 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new 3f37dc8c2ec 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new d9c50fd1c8f 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new cddf244cf16 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new fc9759600a3 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new 6c66a848189 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new 1fd18f13fd9 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new 93d6e8bcfc3 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 8c8c7ab89e0 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 34985f333f4 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 26b57efd98e 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 1a9e72d08cd 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 62a432d88f8 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 7a467e2bc5b 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 1de2d1ffb42 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 40fab490442 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new ef9698e21ec 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 45c578b320c 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 2b36dd67c1f 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 1362e518391 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 4410098315a 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new f03f1b33f3b 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 9ac1adbc5e7 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 716eca7f7aa 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 3acff44fd78 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 7475a2e9c58 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 7bd7d1b51b6 204: force: #26: : Failure after baseline build: no new commits new ee8112c6c38 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new a3a817bc542 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 2f4a5b6b447 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new d17f0713e2f 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 1cb48d12dcc 209: force: #37: 1: Success after baseline build: no new commits new 96a39158866 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] new 2759eaded92 211: onsuccess: #44: 1: Success after linux: 26 commits new a3e8a6f471e 212: force: #45: 1: Success after gdb: 22 commits new a2f3bd40905 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...]
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 (c10caf608e2) \ 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 1964 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2596 -> 2516 bytes 03-build_abe-binutils/console.log.xz | Bin 35288 -> 35248 bytes 04-build_abe-gcc/console.log.xz | Bin 203372 -> 203300 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8456 -> 8460 bytes 07-build_abe-glibc/console.log.xz | Bin 242376 -> 242420 bytes 08-build_abe-gdb/console.log.xz | Bin 34892 -> 34728 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3780 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2716 -> 2720 bytes 11-check_regression/console.log.xz | Bin 3408 -> 3048 bytes 11-check_regression/results.compare | 18 ++---------- 12-update_baseline/console.log | 50 +++++++++++++++++----------------- 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 | 14 +++++----- sumfiles/gdb.log.0.xz | Bin 1949676 -> 1952768 bytes sumfiles/gdb.log.1.xz | Bin 25288 -> 25384 bytes sumfiles/gdb.log.2.xz | Bin 5200 -> 5204 bytes sumfiles/gdb.log.3.xz | Bin 5420 -> 5428 bytes sumfiles/gdb.sum | 2 +- sumfiles/gdb.sum.0 | 2 +- sumfiles/gdb.sum.1 | 4 +-- sumfiles/gdb.sum.2 | 4 +-- sumfiles/gdb.sum.3 | 4 +-- 28 files changed, 47 insertions(+), 61 deletions(-)