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 315d12afdd6 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 09c44f04e6e 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gc [...] discards 4df4e73781e 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gd [...] discards b40f8c71944 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gd [...] discards 8209e747cdb 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] discards e2afb2c3ec3 214: onsuccess: #47: 1: Success after gdb: 21 commits discards fd0cb722538 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] discards 4ffd2b44258 212: force: #45: 1: Success after gdb: 22 commits discards 3f14ab86cd0 211: onsuccess: #44: 1: Success after linux: 26 commits discards 5d06170677e 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] discards 1caa10ced7c 209: force: #37: 1: Success after baseline build: no new commits discards fd6b02747f4 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards f855b3b9bf7 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards b7caca5a96d 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 46376cd4153 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards baf31157b8c 204: force: #26: : Failure after baseline build: no new commits discards a3b368ce873 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 8cd9408cd98 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 9b474344e05 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards aa8de6bd727 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 74240094c06 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 9f3e9ebcee0 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 8944ad8d166 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 857ce37abfc 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 62e997c9651 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 1feaec752e9 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards f9c9a3f2cac 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 4f6e3705842 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 889cb16da20 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards eaac9083644 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 43b97da9923 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 4847a146890 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards c655ea4754f 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 16c4932f350 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 6d6402f623e 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 4dbc66d1d06 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards 99691193428 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards 6bd410fff44 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards 1e32132cac0 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards a76838b0de1 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 0298f0a7bee 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards 9f4e9791e04 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards d0a261dd2c0 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards cc909f77fc7 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards a3321a9eb14 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards 02c925ce31f 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards 8d265ade25c 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards 364274487b2 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards afa02f3a23c 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards f1ac2ab1707 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards 7f5716d8286 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 3861c88152e 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards 3eab06faff5 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards 413eb2a4733 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 9c87835ef8c 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards 35bf9fecfd0 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards 812ac746ee5 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards 77f6f9871ec 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards 8b30ae1de91 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards 538bcc9be05 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards f579fa939a1 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 62021d83829 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards cd6e0b64c72 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards a4116bea665 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards 56163872a58 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 316f3f6a69c 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 6860eac6807 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 8d342a9e9ee 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 56f62d50f4f 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards c59b599f015 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 05744a4c338 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 0a4e9a75717 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 9ec09bdee87 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards a41d8a01cbb 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 839b26551c9 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 1ef3d2e25f0 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards 21d4cc09a24 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 98c495f1a2e 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 541167abb43 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 401148fae3b 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards a579fd4ddd7 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 5d437af5857 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 74fea35e337 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards 2ffe17ca434 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards 2a4ffffaa8b 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 36060b68e0a 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards 4077730580b 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 626a27d3e79 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards c5fb7d91091 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 43cd36dfb64 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 11a5ad99a9f 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 5a031ed412d 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards 95e17bd52de 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 23d15655411 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards ce27619ec1d 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards a8f4e8ac802 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards aaf9b4cc22f 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards c37fff1602e 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 81e32b82fda 121: onsuccess: #908: 1: Success after glibc: 2 commits discards e61080d775a 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 192626d1687 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new cb84854d4b5 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new aeef4082401 120: onsuccess: #906: 1: Success after binutils: 29 commits new 70f7a3620b2 121: onsuccess: #908: 1: Success after glibc: 2 commits new 62e65401217 122: onsuccess: #909: 1: Success after linux: 2753 commits new 407f11f75bd 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 522016d2592 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new f74aa9ca171 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 5d914e0f903 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 7f62d832845 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new dcf12b7f75f 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new 7181b31847b 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new dbf1b0cadd8 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 251e9ed9995 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 5ef1d856729 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 56670330aa2 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new f85772815c8 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new a024921548e 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new c1df253ca9c 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 8456c620862 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new 069d7b3e27c 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new fa5b803a7e8 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new a130631c4de 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 6e85f5f2fbb 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new c6b4dce66bc 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new fa3ecb94a33 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new ed4ce363c58 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new 0548d04d5e8 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 71e4b66f588 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 514c659ba82 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 791614f5f44 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 499096342e8 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new d373994863a 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 4e3b86d3072 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 4482ec07717 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new dfd6159e28e 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new a7fb8010d48 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 70f900f45d4 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 282a7e9754a 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new bc867be843a 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new 11afd56271a 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 93c29dd21c0 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new 7b1644aba97 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new a0daa035931 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new 0ae4690a938 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new 428369abe8c 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new ca37abc44fa 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 96b4c0460c8 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new aa4c7e2c28a 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new 5976aa7b1d9 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new e2cf48c66d4 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new ed3d70cd145 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new 8d571085253 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 337220fa982 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new 9dd5e1a7048 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new d33f8795c93 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new c2dd837b589 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new 389ad1b099d 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new 8a975022466 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new 1efb01772bb 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new 980815729a6 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new d8f8489cb3a 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new dc05ce056b9 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new 04d00bd2ae8 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new 17d612ce84d 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new 1fc2b8f6dae 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new e3bd187d4c2 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new 849570e8b73 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 5f784bd2353 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 9c92227b4a8 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new e2532431e8d 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 0f11a255f1d 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 61e6bccf795 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 3e0ad9fcba6 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new b0a6518a65f 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 4c2ad6a63ea 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new b4d14f6efdf 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 9fb5ef8bf7d 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 591399f1433 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new eafb6fd02a4 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new cb351186e7e 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 7db63c3df75 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 8b860345329 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 28d9bc090e2 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new b14dbd0410a 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 1a3724e0664 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 27ef9a9e204 204: force: #26: : Failure after baseline build: no new commits new db3a2a933fa 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new b6ce1592da8 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new abfaa9b7c21 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 208200ca9ba 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 91af2700105 209: force: #37: 1: Success after baseline build: no new commits new 9f0f389d5b1 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] new 6e87fc04c97 211: onsuccess: #44: 1: Success after linux: 26 commits new d3eff7a75c2 212: force: #45: 1: Success after gdb: 22 commits new 42ef6dae7f6 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] new 25bed252ef4 214: onsuccess: #47: 1: Success after gdb: 21 commits new f621495d1d5 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] new 4130945d9f6 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gd [...] new ccb6c867c63 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gd [...] new 08262ba346c 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gc [...] new 488577a333d 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 2d4504a95ac 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpo [...]
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 (315d12afdd6) \ 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 2204 -> 2032 bytes 02-prepare_abe/console.log.xz | Bin 2492 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 35188 -> 35276 bytes 04-build_abe-gcc/console.log.xz | Bin 206552 -> 202768 bytes 06-build_abe-linux/console.log.xz | Bin 8876 -> 8820 bytes 07-build_abe-glibc/console.log.xz | Bin 242328 -> 241448 bytes 08-build_abe-gdb/console.log.xz | Bin 34532 -> 34716 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3780 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2752 -> 2692 bytes 11-check_regression/console.log.xz | Bin 3120 -> 3648 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 6 + 11-check_regression/results.compare | 9 +- 11-check_regression/results.regressions | 14 + 11-check_regression/trigger-bisect | 3 + 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 40 +- 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 | 20 +- results | 14 + sumfiles/gdb.log.0.xz | Bin 1966132 -> 1932664 bytes sumfiles/gdb.log.1.xz | Bin 70144 -> 20768 bytes sumfiles/gdb.log.2.xz | Bin 0 -> 5552 bytes sumfiles/gdb.log.3.xz | Bin 0 -> 5484 bytes sumfiles/gdb.sum | 5304 ++++++++++++++++--- sumfiles/gdb.sum.0 | 5310 ++++++++++++++++--- sumfiles/gdb.sum.1 | 8445 +------------------------------ sumfiles/gdb.sum.2 | 182 + sumfiles/gdb.sum.3 | 182 + 34 files changed, 9929 insertions(+), 9623 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions create mode 100644 11-check_regression/trigger-bisect create mode 100644 11-check_regression/trigger-notify create mode 100755 jenkins/notify.sh create mode 100644 sumfiles/gdb.log.2.xz create mode 100644 sumfiles/gdb.log.3.xz create mode 100644 sumfiles/gdb.sum.2 create mode 100644 sumfiles/gdb.sum.3