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 d09c0d363c0 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards e8d7fb39fdd 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards e7b4dbb75cb 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards f16f14286a9 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 7019296bca3 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards e4c1abc69f0 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards c94754397f8 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 44a8db4e1a8 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 7a92d2413d5 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 234cfe98258 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 7cc6b4405a5 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 3c741310130 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 3d7ac1820bd 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards b4cdbbd5870 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 7738e265ff3 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 182c501f2ac 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 846568a5547 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 89e0e7dce41 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards 16661e6ef0f 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards ec9f07849e7 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 16216a020ed 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 5fcd9aa24e6 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 87a8d65fbdb 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 22adf59ec4d 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 810da6a3e06 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 79469866667 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 217d63a9a69 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 48fc4920bcc 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards e7574078207 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 390c3a3a63e 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards f2d598c4087 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards a5eed679d5c 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 49b3d12e890 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 6d71a10b42a 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 0f4ba5ec267 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 6be9ce4b7f5 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards ce4edb467b9 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 273c5dfe506 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 828222726af 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 22a197d2725 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 6893c17db7a 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards cac366e5041 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 0c1a1201313 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 0fcd79a3c0e 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 56570e19a46 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards dbf89d54903 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 784d497d20c 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 50bb3e21ad6 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 35b841f09ea 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 2f057410a60 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 36a6c59d3d2 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards e06e82a64a9 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 13abae13400 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards c4f6181bd11 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards f6a2f96834a 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 83e0b138a71 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards caf0903620f 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards e009fe6704c 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards f48268111a7 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards d64677642f0 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards 73ae6132a00 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards 17944145f6f 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards b563c7c1fd2 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards 874e7650b93 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 2559172e02d 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards c436b15fb22 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 8267b838cdc 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 5fe82307676 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 495319cf030 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards eff7db0551c 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 61fcd13505f 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards b55908754a8 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards ffe752ec454 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 749dcd77f6b 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 673b9a40048 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards f59ba415dde 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards a547e36e64d 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards ec96a1000c9 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 2b82c36e5b5 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards c9ab101fa17 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 92eab701219 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 5bcc1bf6049 125: onsuccess: #614: 1: Success after linux: 12 commits discards 3f0f321e09f 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 3233e0e986d 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 2683d5d25ed 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 64caa1223b6 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards fb480a53d9c 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 3c8ec3d4178 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 9efb8fe3311 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 19652db9ec1 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards 0de8d41a751 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 4d3f8368a1e 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 9ed6683fa66 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards bc1dbbe18ff 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 6b77acc3f26 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] discards e0b44dbd76c 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] discards 4f7fa839d55 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards fa272af261d 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 407a0f523ff 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards ce8d8179cdc 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 680e8136d1e 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new a448baaaa86 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 7d35c4cef95 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 874b3cad6c7 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 6e97164fba6 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new e2c5892de0c 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new ebae66bdf19 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new 3d3f27ba739 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new 8c56a694857 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 6e92aa2b162 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 4aa6b8c2a46 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new be4eb11c7c5 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 297207701ee 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new 4f5256f0a94 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new f81210a3a79 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 5b7f81bb8dd 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new f1a09245b8e 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 5eab0700de6 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 7a997fedc40 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new ce300219e41 124: onsuccess: #612: 1: Success after binutils: 18 commits new 98e05278e56 125: onsuccess: #614: 1: Success after linux: 12 commits new bb60e239fdf 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 233e082ea30 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new bae8c692fe1 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new e0ae92e3af6 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 217c16aeaad 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 33cf9f5e7e3 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 25545925c72 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 9aee4bbfcca 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 412e6960b23 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new e2529a59e9b 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new efd9f266b39 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 2bf548f19db 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new c0afe701b2c 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 17633ef05da 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new d0061e1a0c9 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new bb03d1bf13d 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 54324a63d10 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 45515359848 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 15bf6196037 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new 32c03ad121b 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 1b829632830 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 9a6e7da1cf0 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new d7e86e75d27 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 703e1a89cd8 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 2c4f8cdc97e 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 0cfdeb0e67a 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new b77eb4d84ad 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 64ba1250021 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new b2af3599b9e 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new a10e2cbab0a 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new a037e1bd767 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 105bdc46140 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 3215ae61dd1 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 40a78b9496a 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 837d3ab0b94 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 48eb36b04e2 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new e0698e90544 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 003c91cfa44 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 4a6610da9dd 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 4a6b3825c18 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 4043177b391 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 470a261d10e 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new d9d45ed26d2 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 15718d5a1d6 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new cbe2c20b1a7 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 9c2f1f0fd9b 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 33ec2805d18 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 9fff6badebd 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 8addae166d8 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 2e59b9b0a01 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new a4fa2bd8e1c 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 9766785e235 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 478466a0df4 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 8d31b01c5cc 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 783be11176a 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new b58673f5e86 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new b938e032cfd 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new e08dd0421d1 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 3344b21a0fe 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new 5887cf81682 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 3e0300dbfc8 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new 9a24ce7d4f9 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new ad04738bc38 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new 5fdfbc59224 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 72e4d814a85 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new ae092c06d24 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 813bfba93e4 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new ceee629840c 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 25609062db1 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new e325c0d0462 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 78b8e2b02f2 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 91acf1649a2 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new b18cecedad9 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new c89363c2293 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new dc64d320684 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new d30344b3ee1 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new c34c3580dab 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 801f25c2110 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 0c641c5392b 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new fbc7a9ab495 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 82449b99b6a 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 07a3670a33d 207: onsuccess: #16: 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 (d09c0d363c0) \ 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 1800 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 52708 -> 52948 bytes 04-build_abe-gcc/console.log.xz | Bin 236836 -> 236444 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9596 -> 8640 bytes 07-build_abe-glibc/console.log.xz | Bin 235664 -> 235580 bytes 08-build_abe-gdb/console.log.xz | Bin 51768 -> 51096 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3768 -> 3744 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2244 -> 2012 bytes 11-check_regression/console.log.xz | Bin 7808 -> 8492 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 22 +- 11-check_regression/mail-body.txt | 88 +- 11-check_regression/results.compare | 47 +- 11-check_regression/results.compare2 | 253 +- 11-check_regression/results.regressions | 47 +- 12-update_baseline/console.log | 66 +- 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/jira-body.txt | 2 +- mail/mail-body.txt | 90 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 47 +- sumfiles/gdb.log.xz | Bin 2931008 -> 2931760 bytes sumfiles/gdb.sum | 4641 +++++++++++++++---------------- 31 files changed, 2688 insertions(+), 2667 deletions(-)