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 e5be5c51f01 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] discards d346d052b22 226: force: #70: 1: Success after baseline build: no new commits discards 341f6271499 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] discards 30950bb6854 224: force: #65: 1: Success after gdb: 50 commits discards c0a3968925b 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] discards 6a27129b0e9 222: force: #60: 1: Success after gdb: 16 commits discards 210ca956980 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] discards c6d058c7bc2 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] discards 9dabe67e42d 219: force: #50: 1: Failure after linux: 2520 commits discards 53d2d76faa6 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] discards 8e6b997d3c7 217: force: #45: 1: Success after linux: 1 commits discards 5137ab170f4 216: force: #43: : Failure after baseline build: no new commits discards 7b81c36e834 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards d115b49ec20 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 8980b401b54 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 55794639a55 212: force: #27: : Failure after baseline build: no new commits discards bdd6f8750c6 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 72af0194629 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 3ed4663e4c7 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards c0af1626020 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 9fbe9f78106 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 49dbb1e9c7b 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards c944f9208db 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 9c3643cdf00 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 386a87b977e 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards d6c7787dfba 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards bce651a18cc 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 6d551de67cb 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards c7b32ac005e 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 5c00c50bc98 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 1c6d2a21c89 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 97773a24c25 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 459143fdd49 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards ca7b16de4b6 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards c9944970189 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 02cd84e7810 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards ac5d3791db9 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 0f85cb17624 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards b4445ba21b9 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards 6b7887041d7 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards c2b86dc0aad 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 73c0385842c 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 6c26a084fe1 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 222a4cf81b4 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards d5eb47c3de4 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards bf6c7ff8883 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 0ebddda3fab 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 93c23d56b66 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards a9164553dd6 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards ec2e83fdf8a 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 97c698c0a1a 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards a2df64a7c56 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards ad6f46cbe11 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards b9f24287aec 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 25f1b7075b9 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards e3f9e63ba73 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 9fabab7c36f 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 9f32362d5d9 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards f4d38a9d8d9 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 2165818a65b 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 5415d9f514a 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 740fd51ca96 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 35a67ccb722 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 1f8eaad8e1f 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 4a64ebd1eb1 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 1fd8f3ff105 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards fd3fb2a6370 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards de087933b9c 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 46f70764367 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards b0be52e5a36 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards ed1e575abec 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 3d8ee57d42b 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 25b74ccb3ef 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards dee39530a2f 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 2876f527a5d 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 0e59b151c01 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards d8ab2efffa6 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 87c1da0dcfc 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 8d429357910 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 8626e0c2685 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 6a0f4ddb8c4 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards ae384554af0 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards a25f0dda737 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 1e332e86ffb 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards b5b5ee6cafc 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 322229cbefa 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards b057e801766 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 2711e72b48b 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 2488e45e125 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 74e0a7ecbe3 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 56cefbef595 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards a60ab4962fa 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 0292cdfcd85 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 7113bcd38d6 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 583c02d619a 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards f24f3f4cec1 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 6b754c92dde 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards 770623e34f8 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards 88946c20e45 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 74fd315fdd7 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 55a845bcaa2 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 426dedfe4c5 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new eb32e3539c9 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new a2796237018 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 7af9f51dd29 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 6dc27933124 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 0ac3e3fbab4 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new d3c9b873ec0 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 099ad4843d7 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new f6ee60d6da2 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 1d9b6f6f102 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 2399840e5e4 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new a5092d5011e 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 5af4089c0c6 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 7a844d20c62 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new ecd32743538 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 79af9a39170 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new d02d6017903 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 734c217af52 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new a47d4e9582d 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new b541ebe0214 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 797fb18dc7b 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 6017d14c308 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 78d8999e8ad 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new d1f9b14adbe 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new aaa84dd6d17 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new a24d82d2f1a 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 5b67c2ec256 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 259f3b169f9 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new c7d0b5439eb 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 0e51306e2d2 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 0d5cf6fa4d7 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 6667490aeda 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new f2a4affd882 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new c5a6f565627 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new bfa52a5850a 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 8e544020f1f 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new d9608dd06be 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 16053fa00e0 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 3ff77c6e97f 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 0a9077d4d70 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new e077a93f2ba 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new e4409dffb28 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 43324f9e2a9 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new ddb287ff46c 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 6797442428d 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 51b2f9d6fca 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 0e888e55d64 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 76217b2129c 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 84bea89c5fe 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 0adfe8d0a3a 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new da3d3dce135 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new b762344fa43 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new f58c87fd7d5 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new dd760454619 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 361ac44e058 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new cc45cdb837a 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new c1db7ff880e 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 66f06bb1a8b 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new 2a600613b78 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new c9bc081765d 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new d982ca8cc9d 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 11555a0dbd9 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new 5b07c194808 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 0392de14094 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new d710c5afb87 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new da8136e061d 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 2b9da48938e 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new bd4188ffaeb 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 65856b7500a 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 515328ced7d 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 26c622e4127 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 5a72d2540f9 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new e77dfb31dc3 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new c1fc600ec48 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 42357b99380 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new bbf8424f748 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 0adb8a04779 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 1e4bbfe66e3 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 64662c25cb8 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 50d3a6b9de7 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 1b9fe54e157 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new a712fe962a5 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new d7c03c7cbc9 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new cf6cd869033 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new bc0416be805 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 6b0b0e33317 212: force: #27: : Failure after baseline build: no new commits new 04e13fdf075 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 817a70af9a1 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new 58658287009 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new 2b77931d061 216: force: #43: : Failure after baseline build: no new commits new 07d0d7f05cc 217: force: #45: 1: Success after linux: 1 commits new 2d06a1aa28d 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] new d18d4ee948b 219: force: #50: 1: Failure after linux: 2520 commits new 3ec9d639ba7 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] new 49a8d4fde8c 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] new d397ea1af78 222: force: #60: 1: Success after gdb: 16 commits new 3949f3feff9 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] new a999906778a 224: force: #65: 1: Success after gdb: 50 commits new 9a421a6b1f9 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] new b98bbcadd53 226: force: #70: 1: Success after baseline build: no new commits new dc2e5d2116a 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] new ab995fa736f 228: force: #74: 1: Success after gdb: 53 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 (e5be5c51f01) \ 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 2024 -> 2076 bytes 02-prepare_abe/console.log.xz | Bin 2524 -> 2536 bytes 03-build_abe-binutils/console.log.xz | Bin 48696 -> 49016 bytes 04-build_abe-gcc/console.log.xz | Bin 234820 -> 234700 bytes 06-build_abe-linux/console.log.xz | Bin 8356 -> 8432 bytes 07-build_abe-glibc/console.log.xz | Bin 233092 -> 233160 bytes 08-build_abe-gdb/console.log.xz | Bin 50116 -> 46932 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3768 -> 3816 bytes 10-build_abe-check_gdb/console.log.xz | Bin 7876 -> 4568 bytes 11-check_regression/console.log.xz | Bin 5340 -> 3796 bytes 11-check_regression/results.compare | 65 + 11-check_regression/results.compare2 | 110 +- 12-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 27 +- sumfiles/gdb.log.0.xz | Bin 2888000 -> 2879808 bytes sumfiles/gdb.log.1.xz | Bin 146580 -> 143376 bytes sumfiles/gdb.log.2.xz | Bin 15220 -> 20280 bytes sumfiles/gdb.log.3.xz | Bin 10328 -> 14912 bytes sumfiles/gdb.log.4.xz | Bin 10276 -> 14964 bytes sumfiles/gdb.log.5.xz | Bin 10332 -> 14844 bytes sumfiles/gdb.log.6.xz | Bin 10344 -> 6572 bytes sumfiles/gdb.log.7.xz | Bin 10224 -> 0 bytes sumfiles/gdb.log.8.xz | Bin 10096 -> 0 bytes sumfiles/gdb.sum | 152 +-- sumfiles/gdb.sum.0 | 163 +-- sumfiles/gdb.sum.1 | 230 +--- sumfiles/gdb.sum.2 | 238 +++- sumfiles/gdb.sum.3 | 204 ++- sumfiles/gdb.sum.4 | 256 +++- sumfiles/gdb.sum.5 | 207 ++- sumfiles/gdb.sum.6 | 2346 +++------------------------------ sumfiles/gdb.sum.7 | 2229 ------------------------------- sumfiles/gdb.sum.8 | 2161 ------------------------------ 37 files changed, 1206 insertions(+), 7236 deletions(-) delete mode 100644 sumfiles/gdb.log.7.xz delete mode 100644 sumfiles/gdb.log.8.xz delete mode 100644 sumfiles/gdb.sum.7 delete mode 100644 sumfiles/gdb.sum.8