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 07a3670a33d 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 82449b99b6a 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards fbc7a9ab495 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 0c641c5392b 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 801f25c2110 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards c34c3580dab 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards d30344b3ee1 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards dc64d320684 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards c89363c2293 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards b18cecedad9 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 91acf1649a2 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 78b8e2b02f2 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards e325c0d0462 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 25609062db1 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards ceee629840c 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 813bfba93e4 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards ae092c06d24 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 72e4d814a85 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 5fdfbc59224 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards ad04738bc38 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards 9a24ce7d4f9 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 3e0300dbfc8 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 5887cf81682 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 3344b21a0fe 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards e08dd0421d1 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards b938e032cfd 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards b58673f5e86 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 783be11176a 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 8d31b01c5cc 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 478466a0df4 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 9766785e235 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards a4fa2bd8e1c 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 2e59b9b0a01 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 8addae166d8 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 9fff6badebd 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 33ec2805d18 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 9c2f1f0fd9b 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards cbe2c20b1a7 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 15718d5a1d6 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards d9d45ed26d2 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 470a261d10e 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 4043177b391 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 4a6b3825c18 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 4a6610da9dd 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 003c91cfa44 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards e0698e90544 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 48eb36b04e2 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 837d3ab0b94 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 40a78b9496a 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 3215ae61dd1 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 105bdc46140 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards a037e1bd767 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards a10e2cbab0a 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards b2af3599b9e 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 64ba1250021 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards b77eb4d84ad 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 0cfdeb0e67a 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 2c4f8cdc97e 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 703e1a89cd8 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards d7e86e75d27 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 9a6e7da1cf0 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards 1b829632830 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards 32c03ad121b 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 15bf6196037 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards 45515359848 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 54324a63d10 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards bb03d1bf13d 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards d0061e1a0c9 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 17633ef05da 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards c0afe701b2c 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 2bf548f19db 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards efd9f266b39 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards e2529a59e9b 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 412e6960b23 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 9aee4bbfcca 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 25545925c72 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 33cf9f5e7e3 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards 217c16aeaad 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards e0ae92e3af6 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards bae8c692fe1 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 233e082ea30 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards bb60e239fdf 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 98e05278e56 125: onsuccess: #614: 1: Success after linux: 12 commits discards ce300219e41 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 7a997fedc40 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 5eab0700de6 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards f1a09245b8e 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 5b7f81bb8dd 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards f81210a3a79 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 4f5256f0a94 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 297207701ee 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards be4eb11c7c5 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 4aa6b8c2a46 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 6e92aa2b162 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 8c56a694857 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 3d3f27ba739 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] discards ebae66bdf19 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] discards e2c5892de0c 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 6e97164fba6 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 874b3cad6c7 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 7d35c4cef95 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 2a0e2f34509 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new b4111455959 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new d63fe84c36c 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new f7e33e1eabe 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 8f69040c10f 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new a051a59bbc2 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new 9fecc94004f 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 7745e4d4f0b 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new f2c87567c75 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new b27b01b5c6b 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 3b7598229f6 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new 8b005e1dc43 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 0fc26bf3107 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 9caf4336e1e 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 4c95b51b45a 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 10f4d59a155 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new eedf94bdf41 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new ce51de2e1db 124: onsuccess: #612: 1: Success after binutils: 18 commits new 971c5ea6359 125: onsuccess: #614: 1: Success after linux: 12 commits new 0ed931039c2 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 0675857273c 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 528e9dd3589 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 3bb6905055d 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 8e1f0d7d1d1 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new c9619ab755c 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 44fbb815b10 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 2ef97759053 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new d896f22e566 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 2e8c4221eaa 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new d9a15228f23 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 0e2339d418b 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 61181c81739 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 024a56dcd0d 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 1476c1c9d56 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 80820bf6da0 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 0af04b0a01e 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new b0421932190 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new df52a97a057 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new 8b6679ed5e7 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new f6eeb2856ae 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 60314c57d3e 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new b209591c51c 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new d93226d7931 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new de024ca77fd 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new dcf93aca1a0 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 5d11e880345 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 723f789a266 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 3a1373dec82 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new b1cdc6b12ee 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 096c37eeba5 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 930b85e05ae 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new a3a52854bde 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new fc07d63b061 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new bfb64237559 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 5c647350247 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new ecb5fc58ea8 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new c6b40c45a11 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 1de83e96c13 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 97f917cc3ae 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 04ab04581e8 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new c17208752d0 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 9895d80aeae 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new ceb3b6d507c 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new f0fb41dd162 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new b1a73cb7da7 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 74ecfc80aed 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new e9e311023f8 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new d9c61a3b210 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 28032c41ffd 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 9bf8181d8b6 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 920b9a3e89b 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new a35f02dfe74 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 781ee026bc8 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 6e1a0bb4d17 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new e8cb891c57b 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new b87e8d6bcbc 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new c9ecd880791 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 8b577e427af 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new b9b03efb262 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new cc2a4a2875d 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new bf98a4ade54 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new ae0e2c848e8 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new 24232ce0ed6 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 28f056da7b3 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 3d813f091c1 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 48627094f4d 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 1d4b045c7bc 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new f2b81b9f9e0 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 1da50f2a94c 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 954be0f00b3 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new fccfa465c73 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 2404e8d331f 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new a87d053ed4e 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 9967146e9fa 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new fe4ed31b4b0 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 1ee33c76230 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 356939595ce 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new df1f8d043c9 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 8a2e1cb9d7b 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 4285dfc58c2 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 77ea312e7aa 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 4543b178d1f 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...]

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 (07a3670a33d) \ 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 1768 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 52948 -> 52388 bytes 04-build_abe-gcc/console.log.xz | Bin 236444 -> 236052 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8640 -> 8784 bytes 07-build_abe-glibc/console.log.xz | Bin 235580 -> 235496 bytes 08-build_abe-gdb/console.log.xz | Bin 51096 -> 50416 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3744 -> 3744 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2012 -> 2012 bytes 11-check_regression/console.log.xz | Bin 8492 -> 7304 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 18 +- 11-check_regression/mail-body.txt | 83 +- 11-check_regression/results.compare | 36 +- 11-check_regression/results.compare2 | 352 +-- 11-check_regression/results.regressions | 36 +- 12-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 85 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 36 +- sumfiles/gdb.log.xz | Bin 2931760 -> 2945332 bytes sumfiles/gdb.sum | 4394 +++++++++++++++---------------- 30 files changed, 2442 insertions(+), 2684 deletions(-)