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 6606a555c5b 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards eff65e3f610 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards b44113fc839 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gc [...] discards 656dd1a176e 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards 194ab4dcbf9 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards ca64d518fa4 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 3b949bc51e7 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gc [...] discards 35e4bd400e6 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gd [...] discards b9ffde472f1 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gd [...] discards cac97fcc347 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] discards a5547408285 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 280a75082eb 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] discards f3aa22dc42f 212: force: #45: 1: Success after gdb: 22 commits discards a489fb61436 211: onsuccess: #44: 1: Success after linux: 26 commits discards b6c36ad7792 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] discards 0cfb9596b82 209: force: #37: 1: Success after baseline build: no new commits discards c84c9fe6eed 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 1e1d0b3e39f 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards d4727d5b8e4 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 4ee8cfae04f 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 1af3329522b 204: force: #26: : Failure after baseline build: no new commits discards 2fecd0f3e0b 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 01c22d784f3 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards b98e06e5a98 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards bc45b7e5e45 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 1a9e5fb85d8 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards c852eee4b1f 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 513a62fecc0 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards addb7eae209 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 2ccd2f618f1 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 8ac3c5ea811 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 686cf61de61 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards b3ad9a8be5b 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards a5fd309f6eb 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 1d34d41f2f2 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 206af9626ee 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 17ef32bfb00 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 72ed0ae18e5 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 337922441a7 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 193576eab60 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 02c55604b59 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards f0ad0134b36 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards 6ab4edd3baa 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards 5eeb0c7973a 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards a80d370a975 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards d103bbf5d45 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards b4a9f74d594 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards b7e38c90736 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards 813703d2c88 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards fe3012bc317 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards cfb0771a892 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards fb29b4d4ae9 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards 4e7c4d34d7b 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards 3571bf2654e 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards 007a917304e 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards 0774fe7974b 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards f2730a497a9 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards 8faf53a6f94 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards fc22c65a979 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 848d807a3a2 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards 26786600f84 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards 643944e0dde 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards 8ff2d852700 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards ab2ebc8aae0 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards 7928865c771 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards 991276d5a18 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 3c87b295faa 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 073d8ff8444 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards 82bbc9a7ce2 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards 3983443aa2d 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards a53f386f17a 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards c2c913cd548 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 9593b24ca44 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 501fe02912f 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards be95e7833e0 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 509677183af 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 78bb1fe6b8b 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards faf3c15dfe6 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 7a99e2c6c49 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 8cbaab647ce 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 510e0432a6c 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards 5c31e397ac2 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 55084a26692 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards b8552253c0d 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 6c27d1af472 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 2732758323a 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards e3e7b6514d4 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards c8dd93a373f 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards 5307cc11336 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards e1c98383501 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 6438ce93586 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards 8d517581ca4 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 0a461a643c0 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 56c50e9b317 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 1c2de501d45 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards e203a3df43b 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards e1da4118602 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards 0a05930b298 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 99eb12e2d03 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards db1dff6ef81 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards c5531cbd080 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 9d2646cd375 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 872016116a4 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 04fb696c134 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new b3d4d2fbe2c 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 0702d5bffcf 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new 5573217e200 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 81b4f093bda 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 00b744fc3b6 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 45ca10f8be8 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 3e2631fbce9 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new c74dfadbf18 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new 15a3687ae2a 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 9fea11f8302 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 65d43bc4429 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new e6746237f1a 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new 766cea62aa8 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 6bc94ce5367 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 7b2535ec64f 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new e9811e7439a 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 80fad246731 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 94b5fb2f3ab 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new d7a854b3a36 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 1fe061c4a6f 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 80d5e884e8e 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 72f683d12c1 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 25375ffc84a 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new 0c2dd3146e7 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new cd8c39ce9f8 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new fda3b2354d2 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new ff15c777e45 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 05e0ccecce3 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new d83f1ed6cd9 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new bcf4fb3507f 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new 56fa1234d84 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new 98e75cd6ceb 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new a7a735e31ec 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new bd243d634f4 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new b3a5f661dc9 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new 9d98fee81e4 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new a58b83546de 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new f8f97712370 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new b77b996e64e 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new f26e2b9c6db 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new a2b181b2b2b 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new 48b3db342cc 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new 9591460ca11 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new 696f9957fa6 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new d69eb4ef20e 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new 9b9978f50df 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new ce22f1efc6f 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new a2046864bbe 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new 7a24a1fb31e 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new 78c57cf9246 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new ac408342b24 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new 41f390dacd4 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new e3be33a2878 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new 146be5647f1 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new 9b06a10ef4e 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new 38eb744b7f0 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new 5a9f1387683 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new 9fcaf3b3f21 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new d1b4fc29351 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new c71416b7b2f 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 9af23eeaf5d 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 5529fed6b2e 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 5b7177496ef 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new b8b4f103e8c 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new e95eea55319 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new bc55805ca19 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 6fdfd624e1b 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new b5ae5c8d890 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new ad6d2d5f25e 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new d9b361a7e2e 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 305fbf2b334 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new a0dc68b61f7 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new cedea6b5163 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new b780cab815f 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 4fffaada80e 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new b0e95dc5987 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 818b54e266d 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 93a3344b1d9 204: force: #26: : Failure after baseline build: no new commits new 3806469840e 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 293223ecac7 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new fc52621eda1 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 5141b07f613 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 8f05f68fd4f 209: force: #37: 1: Success after baseline build: no new commits new 70fed945f2a 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] new d8ccd4df8de 211: onsuccess: #44: 1: Success after linux: 26 commits new 2aea98f2ae4 212: force: #45: 1: Success after gdb: 22 commits new e0ec5697650 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] new 3045b69aac0 214: onsuccess: #47: 1: Success after gdb: 21 commits new bb231070e5b 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] new 5a569761bfc 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gd [...] new bb6ea7ae0c5 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gd [...] new 58ffff54d4e 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gc [...] new a2357dfe12f 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 56685f4c3e3 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new ae69cc8f6e8 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 17a44a6b83e 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gc [...] new 28436b48474 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new 00637862f4d 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 8560eb6d948 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 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 (6606a555c5b) \ 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 2000 -> 2024 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2536 bytes 03-build_abe-binutils/console.log.xz | Bin 36316 -> 35580 bytes 04-build_abe-gcc/console.log.xz | Bin 203836 -> 202388 bytes 06-build_abe-linux/console.log.xz | Bin 8624 -> 8652 bytes 07-build_abe-glibc/console.log.xz | Bin 241368 -> 240832 bytes 08-build_abe-gdb/console.log.xz | Bin 34764 -> 35172 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3800 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2712 -> 3148 bytes 11-check_regression/console.log.xz | Bin 3744 -> 3988 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 16 ----- 11-check_regression/results.compare | 19 +----- 11-check_regression/results.compare2 | 112 +++++++++++++++++++++++++++++++- 11-check_regression/results.regressions | 24 ------- 11-check_regression/trigger-bisect | 3 - 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 62 +++++++++--------- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- jenkins/notify.sh | 3 - mail/changes-list-long.txt | 11 ++-- mail/changes-list-short.txt | 2 +- mail/short-diag.txt | 2 +- manifest.sh | 22 +++---- results | 24 ------- sumfiles/gdb.log.0.xz | Bin 1992972 -> 2010260 bytes sumfiles/gdb.log.1.xz | Bin 30556 -> 31100 bytes sumfiles/gdb.log.2.xz | Bin 14680 -> 15928 bytes sumfiles/gdb.log.3.xz | Bin 15460 -> 0 bytes sumfiles/gdb.sum | 28 ++++---- sumfiles/gdb.sum.0 | 33 +++++----- sumfiles/gdb.sum.1 | 16 ++--- sumfiles/gdb.sum.2 | 18 ++--- sumfiles/gdb.sum.3 | 110 ------------------------------- 35 files changed, 210 insertions(+), 300 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions delete mode 100644 11-check_regression/trigger-bisect delete mode 100644 11-check_regression/trigger-notify delete mode 100755 jenkins/notify.sh delete mode 100644 sumfiles/gdb.log.3.xz delete mode 100644 sumfiles/gdb.sum.3