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 90dd4d8a0f 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits discards 190c4fcdba 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards 19bc4e5593 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards 27d57b649f 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards ecd6c25104 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 944cfaa307 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards a328a1fef1 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards c2524d6615 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards cc22bb38dc 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards 09fdae1908 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards 66ec1c200b 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards d5f0f8e60c 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards 19d22b87f3 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards fd6c54b5f7 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards 355b7f35ec 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards e65904114b 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 76a1c9f4e3 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards 6afa0a4758 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards 5facca9f29 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 955bb3d1f9 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 6bdbd3eb12 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards 5c1c8a229e 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards 201bfa19d3 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards f3e1bdda88 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards 4097a3e827 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 7827a62315 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards 3d919b884f 212: force: #45: 1: Success after gdb: 22 commits discards e67187eec7 211: onsuccess: #44: 1: Success after linux: 26 commits discards 4fb2860a79 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards 52e08173b5 209: force: #37: 1: Success after baseline build: no new commits discards fe5f4c9d0f 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 968c7d5011 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards c5e3496eb9 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 1afeac8908 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards b6098ce170 204: force: #26: : Failure after baseline build: no new commits discards 9161f1bd4c 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 2da610e251 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards b6a54aa490 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards b2e40b2cab 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards f254dd0d42 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 8c0c534b42 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards f0cca30f68 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards ce0d917d77 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 5f85297a41 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 4d6688f45d 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 2a71668f19 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards b2a48e8f11 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards ab48ef9e3a 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards d64cd70806 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 68a0b68dff 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 3e0267cd65 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 0efe95ae22 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards b44d630df2 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards adeed98b46 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 50c525f775 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards ef01219d55 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards 643a35afb5 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards ea7b9d5461 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards 4e277ab64c 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards 3283059b52 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards 0115e0b985 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards 5c19311a60 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards 7e1fd0d2f2 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards dd8b94cb65 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards fb0690f16a 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards 769a79086f 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards 590d9be5b6 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards b9194ff93b 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards d17ad3bd50 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards 48c8e6e6e4 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards 655ccd88db 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards b315efc786 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards 335d1448d0 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards fec9376373 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards db56c82d26 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards 1a0e437cda 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards 2fd10dc68a 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards 2db854c4f3 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards 1986e624b8 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards b3f1486c7b 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards 14e3deeec8 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 16ee7dce84 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards bcf6399eed 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards 6982379e33 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards 4cd20da155 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards e75431eb4d 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards 7271ab62af 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards 1956cb2aa2 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards 56ac12edab 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards 3ba07c232f 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards 3a8165c0fe 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards 7172d78386 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards a6dba53d49 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards 6e63138e82 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards cc12614154 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards 88bc15c2cf 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards 259f2d6d96 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards bdf7c89d6a 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards 75068346e5 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards 5e27a90085 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards ce08911873 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new 7396e74377 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new 932cf3e21c 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new f774d07d1c 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new 425f72df38 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new bb2535e10e 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new 4bf4cc96f6 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new 173f73ed88 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new 6beabfd194 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new ddfdcf7119 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new da4c367f24 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new 74e9c546a2 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new 1bd07dd46e 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new 1af12c4881 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new b6b55ee5d8 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new 739bac322a 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 6bbeab0466 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new 0866a1c47d 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 64efac5de3 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new 076457fa47 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new 71cdf2d0f1 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new 0094dba69b 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 09ae881567 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new 0a52e2b36f 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new ac198c421a 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new 719c4b898b 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new f84fbd3d82 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new fd740b058e 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new 00d104b3f9 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new 4285098682 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new 7e8d32e87f 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new 1bc0cda031 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new e3877a5345 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new 9c4e04bac2 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new d2e3172ccf 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new 1f274e4ea6 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new 84686bb612 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new 7c2370a7a3 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new 8dc61b644b 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new ead6374fe1 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new 278daf2027 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new 00435cf868 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new 9d2bccf64d 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new dc6defd504 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new 78c57dc00a 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new 871b71e602 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new 63ee84798a 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new 9b312803ef 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new 9defaaabaf 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new e30644558c 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 69f869d47d 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new d30b77af0b 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new be260e3295 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 8e14bd0a7f 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 1c399e224d 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new f58cc9aa0e 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new d7169dc67b 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 5aa4d3c243 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new d350a08bd9 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new ed143bdb15 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new d0312db196 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 25a7c71c88 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 7a269bea32 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 34b9ffc2a5 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new dcd199a28e 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new ce7b91ce86 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 4d0f6a6fc3 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 7874c998ff 204: force: #26: : Failure after baseline build: no new commits new 5b8c7a72cc 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new bbc913bf3b 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 063d488858 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 3d15f4c824 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 85391c8a96 209: force: #37: 1: Success after baseline build: no new commits new e600cf964f 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new e6eb8ea36a 211: onsuccess: #44: 1: Success after linux: 26 commits new 8377902b02 212: force: #45: 1: Success after gdb: 22 commits new 60e595d3cd 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new fd4cd42457 214: onsuccess: #47: 1: Success after gdb: 21 commits new 7598ab38b5 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new 20fc8114a3 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new f7093a890c 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new c98b3159d6 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new 08c4d338a4 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 91bc666c16 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new a9a7377b40 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 3a1932c531 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new e2f4d09ff8 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new f661646e67 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 7ecba2cbb6 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new 095d331b10 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new 4b946f81b5 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new c3f129c0dd 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new d19452aad4 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new 6039b5ac3a 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new 34d65e9b52 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new 34b3973cec 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new 06acc769db 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new dbed34b2f0 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new bdd01790de 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new b0d3371c51 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new ae217ca56d 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new 1ea4a1a942 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits new cec58c3ce6 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...]
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 (90dd4d8a0f) \ 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 2040 -> 2024 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 35204 -> 35476 bytes 04-build_abe-gcc/console.log.xz | Bin 203700 -> 203424 bytes 06-build_abe-linux/console.log.xz | Bin 8892 -> 9424 bytes 07-build_abe-glibc/console.log.xz | Bin 240900 -> 241344 bytes 08-build_abe-gdb/console.log.xz | Bin 34940 -> 35292 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3872 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3004 -> 3268 bytes 11-check_regression/console.log.xz | Bin 4356 -> 5788 bytes 11-check_regression/results.compare | 24 ------- 11-check_regression/results.compare2 | 127 ++++++++++++++++------------------ 12-update_baseline/console.log | 34 ++++----- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 38 ++++++++-- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 28 ++++---- manifest.sh | 36 +++++----- sumfiles/gdb.log.0.xz | Bin 2037736 -> 1920276 bytes sumfiles/gdb.log.1.xz | Bin 27580 -> 27728 bytes sumfiles/gdb.log.2.xz | Bin 0 -> 14864 bytes sumfiles/gdb.sum | 50 ++++++++----- sumfiles/gdb.sum.0 | 51 +++++++++----- sumfiles/gdb.sum.1 | 16 ++--- sumfiles/gdb.sum.2 | 110 +++++++++++++++++++++++++++++ 30 files changed, 330 insertions(+), 198 deletions(-) create mode 100644 sumfiles/gdb.log.2.xz create mode 100644 sumfiles/gdb.sum.2