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 3898eee693 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] discards e3aa4d038e 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] discards 8bc8ce8a59 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits discards 1e7a1d48f6 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards 4a3c6d9234 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards 6b051e167c 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 29e056215b 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 3e8df3a4c3 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards 7451f2362a 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 81eccc3785 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards ad2aaf43bd 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards 8621d77109 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards a9d97e8f43 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards ea23a510db 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards 3e76183513 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards 226bbbd085 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards 6601e06ae2 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 7e0d32c124 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 36b4ca9cbb 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards afddf5f741 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards a4e5d635df 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards c09de1065e 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards e0aabc5cfe 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards c9cb803c3f 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards 048b45b0f7 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards f97d0bcba4 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards 97661feb68 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 645ac075c9 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards bf2ef85f5a 212: force: #45: 1: Success after gdb: 22 commits discards eed8b00321 211: onsuccess: #44: 1: Success after linux: 26 commits discards 07f654e1b8 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards 1488888bd6 209: force: #37: 1: Success after baseline build: no new commits discards fe1380ba80 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 0d32d6756c 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 79f313bf45 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards b5e1089b36 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 7b437074ca 204: force: #26: : Failure after baseline build: no new commits discards 64956d05b3 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 6b5e93735b 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 27d5db3125 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 712e23bad0 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 1f61bdc6e4 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards c424f4881e 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 5402db83ae 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 5f6c8eae7e 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards fe5bb1f0da 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards da6c3bdc1a 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 0840c50c09 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 894b57e85d 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 7db05181e3 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 2d575f3559 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards bcc5423f9a 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 80006c0c21 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 7b9bfb066b 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards d570695df3 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 63d45b479d 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards e019adc91d 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards f3df020db6 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards e6eba68f47 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards 58b06bc048 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards 18644e67f5 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards fe34145386 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards ddfc19dd1e 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards c22c42a6c5 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards 6e95b0ef4a 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards f1b8488af0 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards 3029fa6c61 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards 1c8f946704 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards 0f4ee555b9 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards bea6f7f034 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards 2b4db8214e 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards 8246e57ae0 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards abc374549f 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards 8dfd0b3cab 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards b19588ef9b 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards 48be4138a2 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards b112ba0b3c 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards f4c7e71d70 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards cee38be3dd 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards bb43ac82f1 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards afdc171697 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards 23cb026610 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards ad2d01651f 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards cbad330778 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards 0e2e16bebc 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards fe3a60fd53 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards a24309b28d 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards fd6b046aeb 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards 48ce170cf0 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards 1b0c8baf61 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards 3b8e2d13a5 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards cb13b2fa3d 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards 3813e186fb 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards 144e98212a 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards 9f60fdc111 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards f742f99bae 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards 2e039f6ea0 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards 8528abc0b2 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards fe27b941a2 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards 6a1a02a797 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards f5ed340a96 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new 447186866f 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new 4dac7c83b5 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new d350db195a 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new a1ffc5ad44 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new 0f0dca9b2d 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new 5791559dfa 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new e142bde3ae 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new 27eefcd125 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new 4d2b274b3e 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new edcf6822b4 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new 75a38af914 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new 3a90b97e0c 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new 4feed10e28 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new b8237f1345 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new b0d378a61b 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new faa3211ca4 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new 843046d22d 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new eeeb05bc60 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new a33becb746 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 73e4c0da52 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new d5c48f3e34 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new bbe3493b56 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new cf94419145 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new 42ddcc8452 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new 28566e64ab 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new 03102ddca3 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new 12251e6ee8 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new 480e69f608 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new 83bd4a036d 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new 7c53b94b76 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new f6d3166b68 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new 2331d4f262 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new a04ab63597 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new 7127d09e1c 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new 50e74b306e 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new 4163d6b13e 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new 19407e69d4 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new 5b7fa20b6b 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new 9768c338cb 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new 586e7d51dc 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new fb96ff87a9 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new b4d50aca83 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new 8c77bea947 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new f0585eb225 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new ca335f29cb 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new 6f384938ec 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 56930e59b2 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new ae624785d5 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 6ee797fe4c 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 6143c8a9d8 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 59f7e62287 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 220ca48365 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 75914bf466 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new b5f2c7a42a 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new c9be668f16 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 508f6f9534 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new f6c1608659 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new ab061da5fc 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 2e67f9f0e3 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 3bb131701f 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new c271f6501c 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new cfe3710b9d 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 487948fbed 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new f5dc578f32 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new f22f507cb9 204: force: #26: : Failure after baseline build: no new commits new 8c08609290 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new bfaeddc1c1 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new b444924074 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new ee0683754c 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 7018cb0ead 209: force: #37: 1: Success after baseline build: no new commits new caeb00033f 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new d439e08c47 211: onsuccess: #44: 1: Success after linux: 26 commits new f3f6e4647a 212: force: #45: 1: Success after gdb: 22 commits new 384ef89332 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new 27579603e0 214: onsuccess: #47: 1: Success after gdb: 21 commits new cf9acbb44c 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new 66700d037c 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new c8dddb8809 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new cc434bf8b7 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new 4a48e6ac6a 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 84eb0f91bd 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 94e0a61b51 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 89e8c43e7a 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new 95bf542f95 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new 67b90a02a3 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new f781f3c4bf 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new 92c6a9a2b1 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new 1fbabc78f8 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new 9e7720466e 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new 0219916bda 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new bbf4c3e305 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new cdfc078b62 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new a2757c3b1d 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new 180e03e6ad 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new b190a8db38 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new c3a4ecf6fb 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new 3611c9cc86 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new 8afa88d014 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new 03a4164f86 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits new 161da876b5 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] new 1a73660738 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] new 50019bdb29 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 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 (3898eee693) \ 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 2080 -> 2208 bytes 02-prepare_abe/console.log.xz | Bin 2528 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 34952 -> 35036 bytes 04-build_abe-gcc/console.log.xz | Bin 203604 -> 204088 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8484 -> 8652 bytes 07-build_abe-glibc/console.log.xz | Bin 240648 -> 241032 bytes 08-build_abe-gdb/console.log.xz | Bin 34688 -> 34752 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3884 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2640 -> 2620 bytes 11-check_regression/console.log.xz | Bin 5132 -> 4152 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 111 ++++++++++++++++------------------ 12-update_baseline/console.log | 42 ++++++------- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/changes-list-long.txt | 27 +++------ mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 +++++----- manifest.sh | 26 ++++---- sumfiles/gdb.log.0.xz | Bin 1988900 -> 1999124 bytes sumfiles/gdb.log.1.xz | Bin 28456 -> 15124 bytes sumfiles/gdb.sum | 26 ++++---- sumfiles/gdb.sum.0 | 29 +++++---- sumfiles/gdb.sum.1 | 103 ++----------------------------- 25 files changed, 145 insertions(+), 261 deletions(-)