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-arm in repository toolchain/ci/base-artifacts.

discards bdf9cf31f910 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/ [...] discards 7e05b36246fc 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/ [...] discards 1120d8ddb457 239: force: #106: 1: [TCWG CI] Success after baseline buil [...] discards f47f46e59432 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branch [...] discards 0eb1a6395302 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits discards 7379844547b0 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: [...] discards 6659626304ac 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/g [...] discards 918126f9f196 234: force: #94: 1: [TCWG CI] Success after baseline build [...] discards 409fb0d15a84 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards 9386c8677ea5 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards ecdf624eca58 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards f71a5355d1ba 230: onsuccess: #78: 1: Success after gdb: 2 commits discards 0cd89aac18e0 229: force: #77: 1: Failure after gdb-13-branchpoint-1594- [...] discards 939122648653 228: force: #74: 1: Success after gdb: 53 commits discards fb9360f8a0cd 227: onsuccess: #72: 1: Success after binutils/gcc/linux/g [...] discards d46216979271 226: force: #70: 1: Success after baseline build: no new commits discards 53e6be9eb2ca 225: force: #68: 1: Failure after gdb-13-branchpoint-1540- [...] discards 28a16273918b 224: force: #65: 1: Success after gdb: 50 commits discards e19051052964 223: force: #63: 1: Failure after gdb-13-branchpoint-1489- [...] discards d16af11613c8 222: force: #60: 1: Success after gdb: 16 commits discards b0ae2720e3c8 221: force: #53: 1: Success after gdb-13-branchpoint-1472- [...] discards 705132cecf34 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02d [...] discards 2cda90ad379f 219: force: #50: 1: Failure after linux: 2520 commits discards d4a9f5f95a44 218: force: #48: 1: Success after gdb-13-branchpoint-1471- [...] discards 463823d7aa26 217: force: #45: 1: Success after linux: 1 commits discards 0f339d7146d7 216: force: #43: : Failure after baseline build: no new commits discards ae79e63d73df 215: force: #41: 1: Failure after gdb-13-branchpoint-1470- [...] discards 2bb6702f62cf 214: force: #39: 1: Failure after gdb-13-branchpoint-1470- [...] discards 1523fadece57 213: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 15256a61845d 212: force: #27: : Failure after baseline build: no new commits discards b5849c4c0d6c 211: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards a67ebd3836f6 210: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 3915c4b6d55b 209: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 7d39a40ccce6 208: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards a4fb5e11e30c 207: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards e8a00829e064 206: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 667212953d27 205: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards a09155b3083f 204: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards 6a0d8184ba5f 203: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards d3bd464d3d0e 202: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 74961351e988 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 180f76fd45d3 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 909a4442cb03 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards 0d82f8738643 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards 314db261da4f 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 4ef1752bd6a1 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards 3f07ec44fed3 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 92c753a3c909 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards 53173a60baac 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 81b068fae0fe 192: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] discards 5d2315640e1d 191: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] discards a89afad57c8f 190: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] discards a91355b2ceae 189: onsuccess: #683: 1: Success after binutils/gcc/linux/ [...] discards 50a6843be550 188: onsuccess: #682: 1: Success after binutils/gcc/linux/ [...] discards 5cb72c58086b 187: onsuccess: #681: 1: Success after binutils/gcc/linux/ [...] discards 7f1fc2fb9242 186: onsuccess: #680: 1: Success after binutils/gcc/linux/ [...] discards 01e65e6a6806 185: onsuccess: #679: 1: Success after binutils/gcc/linux/ [...] discards 5f2c700ed6bf 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/ [...] discards 535f559856c8 183: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] discards 88d3dbd0b28f 182: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] discards 462640e101c6 181: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] discards 6b67e7314026 180: onsuccess: #674: 1: Success after binutils/gcc/linux/ [...] discards f2ef6cc0722d 179: onsuccess: #673: 1: Success after binutils/gcc/linux/ [...] discards ef6a63a53276 178: onsuccess: #672: 1: Success after binutils/gcc/linux/ [...] discards f9737da90410 177: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] discards 2ffbff1ade03 176: onsuccess: #670: 1: Success after binutils/gcc/linux/ [...] discards d15e17ffecf3 175: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] discards e750424ac7da 174: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] discards f76eedc4294c 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 1 [...] discards c15166a51137 172: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] discards 77d71fdea3ef 171: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] discards 62d7008a0bbd 170: onsuccess: #664: 1: Success after binutils/gcc/linux/ [...] discards 2be2ce0ff3cf 169: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] discards 2d493c752e7c 168: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] discards 03b98bd11e5f 167: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] discards dc9d0545d9cc 166: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] discards c545853161e0 165: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] discards 9628006ff86c 164: onsuccess: #658: 1: Success after binutils/gcc/linux/ [...] discards 9e72d8541235 163: onsuccess: #657: 1: Success after binutils/gcc/linux/ [...] discards d825a4c1bd5e 162: onsuccess: #656: 1: Success after binutils/gcc/linux/ [...] discards c599f2983d26 161: onsuccess: #655: 1: Success after binutils/gcc/linux/ [...] discards b307c615ca3e 160: onsuccess: #654: 1: Success after binutils/gcc/linux/ [...] discards 2151cf38768e 159: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] discards edb7f921e2bd 158: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] discards acc480b5ee45 157: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] discards 18544d518ded 156: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] discards ffc7535cfbcc 155: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] discards 40ae465c8552 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/ [...] discards fe210c1094d0 153: onsuccess: #647: 1: Success after binutils/gcc/linux/ [...] discards 1368b242cd19 152: onsuccess: #645: 1: Success after binutils/gcc/linux/ [...] discards 00916d8b1cc3 151: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] discards f3b736cabe35 150: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] discards 248bc219924b 149: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] discards 81e6f50d2fcc 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 [...] discards 7b7dc7f76436 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 1 [...] discards f2790d4aa05c 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 3 [...] discards 62b306db9e8b 145: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] discards f3d73c9c9c56 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 4 [...] discards de1d8afd1d4d 143: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] discards 046393a65428 142: onsuccess: #634: 1: Success after binutils/gcc/linux/ [...] discards 67d72521a612 141: onsuccess: #633: 1: Success after binutils/gcc/linux/ [...] new 12edf291beb0 141: onsuccess: #633: 1: Success after binutils/gcc/linux/ [...] new f9dc01e562ed 142: onsuccess: #634: 1: Success after binutils/gcc/linux/ [...] new 6101b8892181 143: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] new 03ee6cadccd0 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 4 [...] new b214b58dc613 145: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] new ceb0f499e142 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 3 [...] new 7209c32b8ce5 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 1 [...] new 035fd196566a 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 [...] new dd823e63328c 149: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] new c2dddb7a09ca 150: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] new c34780c10be8 151: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] new 7e781695e32d 152: onsuccess: #645: 1: Success after binutils/gcc/linux/ [...] new 2683d254c76a 153: onsuccess: #647: 1: Success after binutils/gcc/linux/ [...] new 034373e80212 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/ [...] new ac10d04e73c1 155: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] new 27eb61fbb81f 156: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] new 966077bd9fc4 157: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] new 0cff5be1088a 158: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] new 9ce0744ece69 159: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] new 23789f793eef 160: onsuccess: #654: 1: Success after binutils/gcc/linux/ [...] new 5a28328d2ce3 161: onsuccess: #655: 1: Success after binutils/gcc/linux/ [...] new be3e33879036 162: onsuccess: #656: 1: Success after binutils/gcc/linux/ [...] new 0cbbad04c3ec 163: onsuccess: #657: 1: Success after binutils/gcc/linux/ [...] new f4e66f5a1c5f 164: onsuccess: #658: 1: Success after binutils/gcc/linux/ [...] new 6ab68ea966dc 165: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] new 2bcf767f34e0 166: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] new fddd08269c8a 167: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new 6e0d12498903 168: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new cde3356298ac 169: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] new 2033a2c22071 170: onsuccess: #664: 1: Success after binutils/gcc/linux/ [...] new 8a03b30a91d3 171: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] new 6633c7b2f3cb 172: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] new 2e79bd935211 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 1 [...] new 02d7733836be 174: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] new fd93f404413c 175: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] new 22fc13cbcd9b 176: onsuccess: #670: 1: Success after binutils/gcc/linux/ [...] new 6af8eb12434d 177: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] new d2c579eb9478 178: onsuccess: #672: 1: Success after binutils/gcc/linux/ [...] new decc90f652f4 179: onsuccess: #673: 1: Success after binutils/gcc/linux/ [...] new e9df17e45040 180: onsuccess: #674: 1: Success after binutils/gcc/linux/ [...] new 73fe50a22d52 181: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] new f17e6fbcb22a 182: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] new c81ab7b2bfb4 183: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] new 6e5c5ced3ccd 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/ [...] new 59f51417ec1b 185: onsuccess: #679: 1: Success after binutils/gcc/linux/ [...] new 94d6bff4c36f 186: onsuccess: #680: 1: Success after binutils/gcc/linux/ [...] new 03225de8e35c 187: onsuccess: #681: 1: Success after binutils/gcc/linux/ [...] new 6629bc86a068 188: onsuccess: #682: 1: Success after binutils/gcc/linux/ [...] new 52368f580a8c 189: onsuccess: #683: 1: Success after binutils/gcc/linux/ [...] new 23ce7b956b8b 190: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] new 3e598cf0e6de 191: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] new 0693265ef463 192: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] new 3366c3580327 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new ff97de47d642 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new e4dccbb18bcd 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 6a02496c692a 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new 4d998bba4e5f 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new d3bf6b9dde6e 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 4959762fbc4a 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 1c070d34c8f7 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 68a882c19b77 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 474eab177371 202: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 5419419fff2b 203: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new a66734b5c7f3 204: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new bfa26872f9d0 205: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new c625022c47c9 206: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new 7981b76d5abf 207: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 65b52c2075fc 208: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 33c6083022b0 209: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 081705736b6f 210: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new b51510cb9120 211: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new 4e41956df92a 212: force: #27: : Failure after baseline build: no new commits new 42eb435ad131 213: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 78b75526eb3a 214: force: #39: 1: Failure after gdb-13-branchpoint-1470- [...] new afd894fbc026 215: force: #41: 1: Failure after gdb-13-branchpoint-1470- [...] new 3549cc53f5d0 216: force: #43: : Failure after baseline build: no new commits new 296407dbb7c7 217: force: #45: 1: Success after linux: 1 commits new 79450f423f80 218: force: #48: 1: Success after gdb-13-branchpoint-1471- [...] new 2df93864cdeb 219: force: #50: 1: Failure after linux: 2520 commits new bda358b9c267 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02d [...] new 68deca96dcf6 221: force: #53: 1: Success after gdb-13-branchpoint-1472- [...] new a6a890df7546 222: force: #60: 1: Success after gdb: 16 commits new f0ee0afbfb6a 223: force: #63: 1: Failure after gdb-13-branchpoint-1489- [...] new 8481dc218b07 224: force: #65: 1: Success after gdb: 50 commits new 347c05a160de 225: force: #68: 1: Failure after gdb-13-branchpoint-1540- [...] new 3ab7f6009f98 226: force: #70: 1: Success after baseline build: no new commits new b1e4d68c22d2 227: onsuccess: #72: 1: Success after binutils/gcc/linux/g [...] new b47c1525b2b6 228: force: #74: 1: Success after gdb: 53 commits new 2fc4f364a248 229: force: #77: 1: Failure after gdb-13-branchpoint-1594- [...] new bb734003ea02 230: onsuccess: #78: 1: Success after gdb: 2 commits new bb75227f40e7 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new 399bfcc9639f 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchp [...] new 6eb992959f48 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchp [...] new eb475f03ec03 234: force: #94: 1: [TCWG CI] Success after baseline build [...] new 891e26e1eb68 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/g [...] new 8b472643ce96 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: [...] new 32dc3ce5e9aa 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits new d9a3a1613eb5 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branch [...] new 15ad98b97e5d 239: force: #106: 1: [TCWG CI] Success after baseline buil [...] new c0b6a3c5db92 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/ [...] new 1f21e82ec164 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/ [...] new 1280dad8b0f5 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 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 (bdf9cf31f910) \ 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 1976 -> 2008 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2492 bytes 03-build_abe-binutils/console.log.xz | Bin 49024 -> 49180 bytes 04-build_abe-gcc/console.log.xz | Bin 235276 -> 238512 bytes 06-build_abe-linux/console.log.xz | Bin 8608 -> 8712 bytes 07-build_abe-glibc/console.log.xz | Bin 232232 -> 233620 bytes 08-build_abe-gdb/console.log.xz | Bin 46520 -> 46396 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3820 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4256 -> 4356 bytes 11-check_regression/console.log.xz | Bin 11496 -> 4420 bytes 11-check_regression/results.compare2 | 3772 +-------------------------------- 12-update_baseline/console.log | 54 +- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- mail/changes-list-long.txt | 14 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 +- manifest.sh | 22 +- sumfiles/gdb.log.0.xz | Bin 2933800 -> 2946564 bytes sumfiles/gdb.log.1.xz | Bin 152260 -> 138656 bytes sumfiles/gdb.log.2.xz | Bin 16776 -> 11832 bytes sumfiles/gdb.log.3.xz | Bin 15276 -> 10088 bytes sumfiles/gdb.log.4.xz | Bin 14840 -> 10136 bytes sumfiles/gdb.log.5.xz | Bin 10032 -> 10240 bytes sumfiles/gdb.log.6.xz | Bin 0 -> 10300 bytes sumfiles/gdb.log.7.xz | Bin 0 -> 9996 bytes sumfiles/gdb.log.8.xz | Bin 0 -> 10076 bytes sumfiles/gdb.sum | 77 +- sumfiles/gdb.sum.0 | 96 +- sumfiles/gdb.sum.1 | 176 +- sumfiles/gdb.sum.2 | 240 +-- sumfiles/gdb.sum.3 | 214 +- sumfiles/gdb.sum.4 | 203 +- sumfiles/gdb.sum.5 | 78 +- sumfiles/{gdb.sum.5 => gdb.sum.6} | 48 +- sumfiles/{gdb.sum.5 => gdb.sum.7} | 14 +- sumfiles/{gdb.sum.5 => gdb.sum.8} | 28 +- 37 files changed, 565 insertions(+), 4509 deletions(-) create mode 100644 sumfiles/gdb.log.6.xz create mode 100644 sumfiles/gdb.log.7.xz create mode 100644 sumfiles/gdb.log.8.xz copy sumfiles/{gdb.sum.5 => gdb.sum.6} (98%) copy sumfiles/{gdb.sum.5 => gdb.sum.7} (99%) copy sumfiles/{gdb.sum.5 => gdb.sum.8} (99%)