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 659f3e052b0 226: force: #70: 1: Success after baseline build: no new commits discards 62405cb0445 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] discards 0c6e5afc82c 224: force: #65: 1: Success after gdb: 50 commits discards 94dfbbd1229 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] discards f5f61d12651 222: force: #60: 1: Success after gdb: 16 commits discards bf344a90df7 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] discards 90516df3c33 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] discards d628904170b 219: force: #50: 1: Failure after linux: 2520 commits discards 2a336b7e2b3 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] discards ab62f56d199 217: force: #45: 1: Success after linux: 1 commits discards 3e28e47b3df 216: force: #43: : Failure after baseline build: no new commits discards ec70c3dac99 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 98752a10c41 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards df8b0f0260d 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 37b27b39293 212: force: #27: : Failure after baseline build: no new commits discards 158bc5098ec 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 3be50482997 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards b276c9039a0 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 070b3d2d32a 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards e513f41c3f3 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 4afc6d25b72 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 4a77dea95db 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 4f84fe56100 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 6b5a04eff25 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 0443390c621 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 0c58658bbc8 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards ec7c584c646 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 02d44776646 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards d70f98f39a5 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards ecf16f44964 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 23ba788ab5d 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards b272eb0ef3e 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 650c0c5a754 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 0d443980e17 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 26f2140554c 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 7c572064eb0 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards e217e3b86d6 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards e75e0afd0d3 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards 698f31bece0 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards bb092aa20ae 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards b5834482b5b 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards d3dd7b1837e 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 2f7ca58d158 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 0120be4d64a 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 34a0fdc800c 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 190807954f7 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards ff7470818f4 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards d989e54b68d 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 58875dcc0cd 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards eb0977bcbf1 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards dc568408e61 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards e20d54ae5bc 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards ea20919cc3f 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 94e963b618f 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 7a0871a05ec 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 466441485e0 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards b3fc5603240 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 7f179cb8f0e 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards f30e4cb0ee2 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 1fef85a2e4f 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 0b3464669e1 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 7845edc2317 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards b3cddb94c3e 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 5c1b2b713c6 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 85f5a725c48 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards c995f025ebe 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 264f6be5384 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards ce9e13440db 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 88ab4618935 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 39088fcd250 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 13ca79fb2fb 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 8a28a01f1ea 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards d9a579691ec 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards d35b2209de4 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards c21c6b9b946 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 7aa42cf9cef 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 8181a0385a8 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards fb36448b6be 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 6173a79524f 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards bd2d458ca5e 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards e5de2e0fc12 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards 73676157b9f 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards b4b5a99c578 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards dc5d6395b35 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards d5d4ba71dc5 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards ecb23953ddb 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 4f601f28746 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards dd1f104df68 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 40c6a35b15c 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards d62b83dea96 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards d48ae12d8ae 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards d6f6a7961df 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 4f993c7e31a 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 0c91d689103 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards f83afb080e0 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards bf335ceb744 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards fbe5833aaaf 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards db05500338e 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 9f7a3ee8cee 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 6044ea33321 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards efc19995102 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new d891f2cddd9 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 55a845bcaa2 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 74fd315fdd7 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 88946c20e45 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 770623e34f8 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 6b754c92dde 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new f24f3f4cec1 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 583c02d619a 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 7113bcd38d6 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 0292cdfcd85 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new a60ab4962fa 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 56cefbef595 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 74e0a7ecbe3 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 2488e45e125 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 2711e72b48b 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new b057e801766 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 322229cbefa 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new b5b5ee6cafc 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 1e332e86ffb 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new a25f0dda737 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new ae384554af0 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 6a0f4ddb8c4 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 8626e0c2685 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 8d429357910 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 87c1da0dcfc 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new d8ab2efffa6 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 0e59b151c01 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 2876f527a5d 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new dee39530a2f 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 25b74ccb3ef 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 3d8ee57d42b 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new ed1e575abec 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new b0be52e5a36 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 46f70764367 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new de087933b9c 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new fd3fb2a6370 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 1fd8f3ff105 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 4a64ebd1eb1 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 1f8eaad8e1f 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 35a67ccb722 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 740fd51ca96 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 5415d9f514a 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 2165818a65b 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new f4d38a9d8d9 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 9f32362d5d9 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 9fabab7c36f 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new e3f9e63ba73 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 25f1b7075b9 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new b9f24287aec 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new ad6f46cbe11 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new a2df64a7c56 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 97c698c0a1a 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new ec2e83fdf8a 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new a9164553dd6 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 93c23d56b66 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 0ebddda3fab 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new bf6c7ff8883 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new d5eb47c3de4 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 222a4cf81b4 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new 6c26a084fe1 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 73c0385842c 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new c2b86dc0aad 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 6b7887041d7 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new b4445ba21b9 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 0f85cb17624 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new ac5d3791db9 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 02cd84e7810 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new c9944970189 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new ca7b16de4b6 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 459143fdd49 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 97773a24c25 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 1c6d2a21c89 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 5c00c50bc98 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new c7b32ac005e 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 6d551de67cb 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new bce651a18cc 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new d6c7787dfba 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 386a87b977e 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 9c3643cdf00 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new c944f9208db 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 49dbb1e9c7b 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 9fbe9f78106 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new c0af1626020 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 3ed4663e4c7 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 72af0194629 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new bdd6f8750c6 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 55794639a55 212: force: #27: : Failure after baseline build: no new commits new 8980b401b54 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new d115b49ec20 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new 7b81c36e834 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new 5137ab170f4 216: force: #43: : Failure after baseline build: no new commits new 8e6b997d3c7 217: force: #45: 1: Success after linux: 1 commits new 53d2d76faa6 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] new 9dabe67e42d 219: force: #50: 1: Failure after linux: 2520 commits new c6d058c7bc2 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] new 210ca956980 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] new 6a27129b0e9 222: force: #60: 1: Success after gdb: 16 commits new c0a3968925b 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] new 30950bb6854 224: force: #65: 1: Success after gdb: 50 commits new 341f6271499 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] new d346d052b22 226: force: #70: 1: Success after baseline build: no new commits new e5be5c51f01 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...]
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 (659f3e052b0) \ 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 2092 -> 2024 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2524 bytes 03-build_abe-binutils/console.log.xz | Bin 49328 -> 48696 bytes 04-build_abe-gcc/console.log.xz | Bin 235344 -> 234820 bytes 06-build_abe-linux/console.log.xz | Bin 8580 -> 8356 bytes 07-build_abe-glibc/console.log.xz | Bin 233912 -> 233092 bytes 08-build_abe-gdb/console.log.xz | Bin 49900 -> 50116 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3760 -> 3768 bytes 10-build_abe-check_gdb/console.log.xz | Bin 7908 -> 7876 bytes 11-check_regression/console.log.xz | Bin 2528 -> 5340 bytes 11-check_regression/mail-body.txt | 14 --- 11-check_regression/results.compare2 | 110 +++++++++++++++++- 12-update_baseline/console.log | 46 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/mail-body.txt | 16 +-- mail/mail-subject.txt | 2 +- manifest.sh | 32 +++--- sumfiles/gdb.log.0.xz | Bin 2822600 -> 2888000 bytes sumfiles/gdb.log.1.xz | Bin 146940 -> 146580 bytes sumfiles/gdb.log.2.xz | Bin 20104 -> 15220 bytes sumfiles/gdb.log.3.xz | Bin 10072 -> 10328 bytes sumfiles/gdb.log.4.xz | Bin 10276 -> 10276 bytes sumfiles/gdb.log.5.xz | Bin 10332 -> 10332 bytes sumfiles/gdb.log.6.xz | Bin 10148 -> 10344 bytes sumfiles/gdb.log.7.xz | Bin 10168 -> 10224 bytes sumfiles/gdb.log.8.xz | Bin 0 -> 10096 bytes sumfiles/gdb.sum | 43 ++++--- sumfiles/gdb.sum.0 | 53 +++++---- sumfiles/gdb.sum.1 | 76 +++++++++---- sumfiles/gdb.sum.2 | 209 ++++++---------------------------- sumfiles/gdb.sum.3 | 40 +++++-- sumfiles/gdb.sum.4 | 69 +++++++++-- sumfiles/gdb.sum.5 | 81 ++----------- sumfiles/gdb.sum.6 | 23 ++-- sumfiles/gdb.sum.7 | 59 +++++++++- sumfiles/{gdb.sum.4 => gdb.sum.8} | 17 +-- 40 files changed, 482 insertions(+), 418 deletions(-) create mode 100644 sumfiles/gdb.log.8.xz copy sumfiles/{gdb.sum.4 => gdb.sum.8} (99%)