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 2d4504a95ac 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 488577a333d 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 08262ba346c 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gc [...] discards ccb6c867c63 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gd [...] discards 4130945d9f6 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gd [...] discards f621495d1d5 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] discards 25bed252ef4 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 42ef6dae7f6 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] discards d3eff7a75c2 212: force: #45: 1: Success after gdb: 22 commits discards 6e87fc04c97 211: onsuccess: #44: 1: Success after linux: 26 commits discards 9f0f389d5b1 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] discards 91af2700105 209: force: #37: 1: Success after baseline build: no new commits discards 208200ca9ba 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards abfaa9b7c21 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards b6ce1592da8 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards db3a2a933fa 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 27ef9a9e204 204: force: #26: : Failure after baseline build: no new commits discards 1a3724e0664 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards b14dbd0410a 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 28d9bc090e2 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 8b860345329 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 7db63c3df75 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards cb351186e7e 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards eafb6fd02a4 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 591399f1433 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 9fb5ef8bf7d 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards b4d14f6efdf 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 4c2ad6a63ea 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards b0a6518a65f 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 3e0ad9fcba6 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 61e6bccf795 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 0f11a255f1d 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards e2532431e8d 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 9c92227b4a8 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 5f784bd2353 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 849570e8b73 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards e3bd187d4c2 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards 1fc2b8f6dae 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards 17d612ce84d 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards 04d00bd2ae8 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards dc05ce056b9 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards d8f8489cb3a 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards 980815729a6 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards 1efb01772bb 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards 8a975022466 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards 389ad1b099d 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards c2dd837b589 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards d33f8795c93 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards 9dd5e1a7048 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards 337220fa982 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards 8d571085253 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards ed3d70cd145 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards e2cf48c66d4 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards 5976aa7b1d9 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards aa4c7e2c28a 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 96b4c0460c8 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards ca37abc44fa 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards 428369abe8c 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards 0ae4690a938 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards a0daa035931 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards 7b1644aba97 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards 93c29dd21c0 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 11afd56271a 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards bc867be843a 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards 282a7e9754a 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards 70f900f45d4 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards a7fb8010d48 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards dfd6159e28e 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 4482ec07717 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 4e3b86d3072 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards d373994863a 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 499096342e8 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 791614f5f44 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 514c659ba82 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 71e4b66f588 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 0548d04d5e8 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards ed4ce363c58 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards fa3ecb94a33 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards c6b4dce66bc 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 6e85f5f2fbb 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards a130631c4de 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards fa5b803a7e8 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 069d7b3e27c 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 8456c620862 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards c1df253ca9c 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards a024921548e 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards f85772815c8 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards 56670330aa2 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 5ef1d856729 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 251e9ed9995 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards dbf1b0cadd8 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 7181b31847b 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards dcf12b7f75f 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards 7f62d832845 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 5d914e0f903 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards f74aa9ca171 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 522016d2592 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 407f11f75bd 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 62e65401217 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 70f7a3620b2 121: onsuccess: #908: 1: Success after glibc: 2 commits discards aeef4082401 120: onsuccess: #906: 1: Success after binutils: 29 commits new 56ebbf4081e 120: onsuccess: #906: 1: Success after binutils: 29 commits new a95dca712b8 121: onsuccess: #908: 1: Success after glibc: 2 commits new d6b2fd17e54 122: onsuccess: #909: 1: Success after linux: 2753 commits new 003e788654f 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 28aa58308ee 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new e8bd9e4e03d 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 29bd102fa3c 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new ada6218b2c9 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new f2471e34de9 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new 99be72c7cd2 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 5e6886f9950 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new e8da27bacf5 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 4fdcb9291a5 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 50566f68fbb 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 713fa3d4c81 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new 2492689ea5c 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 8e756043466 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 2b80bd077d8 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new d0c49ee87e2 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new 5ecd163bf2b 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 44d54229529 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new a07785ac0c0 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new bfd675a23cc 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 2e2897d5b2a 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 9ff10c4edf0 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new 0ff0f941589 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 7c9cf424e7e 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 02efbbdd985 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 96150f25e61 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new f8a7a46f7f8 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new 055ca3326c7 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new bfa9f57ba7a 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 1b73d2f6fcc 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 8d848ba9bdc 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 7a524aa3241 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 0ff60d4c234 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 27557a9c615 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new 5c594f6c4ed 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new 32c728b43bc 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 6398cae56be 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new 7dd89d3eb6e 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new 258afa83822 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new 1e329fa7ccd 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new 29023845b10 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new b31c7d9d152 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new c7503bd7b07 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new c92428a4bbf 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new af2b6707a4d 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new de60303642f 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new 5cc499b0cb5 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new 674ce4ef9a3 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 89179b05355 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new 90a924f6fc1 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new da4c034d559 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new 93069d90411 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new 5b81b9660d1 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new fabc52a31e8 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new d7405ed577a 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new f60c7c7a7b4 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new 2a4ebeb7d75 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new 17a1381c38d 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new ed69d3627e0 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new 5986ff8a2f8 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new 541c6bdf2a2 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new 8c14d932ff3 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new a4afa2b1ec9 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new c4be55c0a50 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 1a169b5ca4c 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 7f8f0a1c3fa 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 54e1e9c7a17 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 7c3f2f604bc 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 00a19c16162 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 89698251ab8 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 093c33d97e1 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new da532bad07d 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 0e0ffd8b29d 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 7e733a8e6d6 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 4f3e5f3eef7 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 3ae1519b9d4 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 27c70738761 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new c264b456526 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 78f1601fd77 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 12b2031d719 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 1fbb2211dc2 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new d5a2527a016 204: force: #26: : Failure after baseline build: no new commits new 0fbc77ac0d5 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new d5f5ab75b9e 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 88eda637be5 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 991e201b890 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new bddd52c35df 209: force: #37: 1: Success after baseline build: no new commits new 2eac9e0f723 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] new 581c9f25a32 211: onsuccess: #44: 1: Success after linux: 26 commits new 58b0ea4d3ba 212: force: #45: 1: Success after gdb: 22 commits new ecd322c76bd 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] new f0000d73dd7 214: onsuccess: #47: 1: Success after gdb: 21 commits new 4d47ceba027 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] new 6a9aea6a0d3 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gd [...] new 971a2fa4873 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gd [...] new 43aca899884 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gc [...] new b41e6ff1e80 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 4662a23de58 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new f31d5445f2c 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 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 (2d4504a95ac) \ 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 2032 -> 2012 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2516 bytes 03-build_abe-binutils/console.log.xz | Bin 35276 -> 35228 bytes 04-build_abe-gcc/console.log.xz | Bin 202768 -> 204064 bytes 06-build_abe-linux/console.log.xz | Bin 8820 -> 8896 bytes 07-build_abe-glibc/console.log.xz | Bin 241448 -> 240924 bytes 08-build_abe-gdb/console.log.xz | Bin 34716 -> 34964 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3784 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2692 -> 2824 bytes 11-check_regression/console.log.xz | Bin 3648 -> 4252 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 6 -- 11-check_regression/results.compare | 9 +- 11-check_regression/results.compare2 | 163 +++++++++++++++++++++++++++++++- 11-check_regression/results.regressions | 14 --- 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 | 14 --- sumfiles/gdb.log.0.xz | Bin 1932664 -> 1948932 bytes sumfiles/gdb.log.1.xz | Bin 20768 -> 34336 bytes sumfiles/gdb.log.2.xz | Bin 5552 -> 5508 bytes sumfiles/gdb.log.3.xz | Bin 5484 -> 5424 bytes sumfiles/gdb.sum | 57 +++++------ sumfiles/gdb.sum.0 | 60 ++++++------ sumfiles/gdb.sum.1 | 101 +++++++++++++++++++- sumfiles/gdb.sum.2 | 4 +- sumfiles/gdb.sum.3 | 4 +- 35 files changed, 378 insertions(+), 164 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