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 4543b178d1f 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 77ea312e7aa 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 4285dfc58c2 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 8a2e1cb9d7b 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards df1f8d043c9 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 356939595ce 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 1ee33c76230 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards fe4ed31b4b0 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 9967146e9fa 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards a87d053ed4e 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 2404e8d331f 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards fccfa465c73 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 954be0f00b3 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 1da50f2a94c 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards f2b81b9f9e0 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 1d4b045c7bc 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 48627094f4d 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 3d813f091c1 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 28f056da7b3 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 24232ce0ed6 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards ae0e2c848e8 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards bf98a4ade54 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards cc2a4a2875d 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards b9b03efb262 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 8b577e427af 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards c9ecd880791 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards b87e8d6bcbc 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards e8cb891c57b 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 6e1a0bb4d17 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 781ee026bc8 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards a35f02dfe74 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 920b9a3e89b 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 9bf8181d8b6 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 28032c41ffd 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards d9c61a3b210 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards e9e311023f8 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 74ecfc80aed 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards b1a73cb7da7 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards f0fb41dd162 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards ceb3b6d507c 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 9895d80aeae 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards c17208752d0 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 04ab04581e8 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 97f917cc3ae 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 1de83e96c13 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards c6b40c45a11 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards ecb5fc58ea8 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 5c647350247 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards bfb64237559 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards fc07d63b061 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards a3a52854bde 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 930b85e05ae 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 096c37eeba5 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards b1cdc6b12ee 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 3a1373dec82 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 723f789a266 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 5d11e880345 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards dcf93aca1a0 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards de024ca77fd 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards d93226d7931 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards b209591c51c 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 60314c57d3e 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards f6eeb2856ae 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards 8b6679ed5e7 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards df52a97a057 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards b0421932190 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 0af04b0a01e 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 80820bf6da0 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 1476c1c9d56 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 024a56dcd0d 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 61181c81739 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 0e2339d418b 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards d9a15228f23 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 2e8c4221eaa 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards d896f22e566 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 2ef97759053 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 44fbb815b10 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards c9619ab755c 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards 8e1f0d7d1d1 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards 3bb6905055d 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 528e9dd3589 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 0675857273c 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 0ed931039c2 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 971c5ea6359 125: onsuccess: #614: 1: Success after linux: 12 commits discards ce51de2e1db 124: onsuccess: #612: 1: Success after binutils: 18 commits discards eedf94bdf41 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 10f4d59a155 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 4c95b51b45a 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 9caf4336e1e 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 0fc26bf3107 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 8b005e1dc43 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 3b7598229f6 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards b27b01b5c6b 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards f2c87567c75 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 7745e4d4f0b 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 9fecc94004f 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards a051a59bbc2 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] discards 8f69040c10f 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] discards f7e33e1eabe 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards d63fe84c36c 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards b4111455959 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 1a3f8af77b0 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 645a5af1edb 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new f8d6f726fe3 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 81f6f35cc9b 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new 5a93c33f065 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new 37e8e3663b4 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new b6418235e34 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 0f0f700c6ed 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 4cb4612d15b 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new de324bc55c5 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new f91ab5739bc 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 009082bc885 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 3d3bf36501b 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new e5aa926f78f 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 171e1a1e13e 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new ee6d10d996c 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new d24c0f3bb0f 124: onsuccess: #612: 1: Success after binutils: 18 commits new d7498dceafc 125: onsuccess: #614: 1: Success after linux: 12 commits new 84da46d299f 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 410e7e86878 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 47e28ca4461 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new f4539b8dae1 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 6afebdb904e 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 11c0a5f0101 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 95ae81fa8e4 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 4fba228c61b 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new f5c8135c2e6 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 60c0d72fafe 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 4b4981cdacc 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new ef4faccaed7 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new a678a9c0ec5 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 647d4c6b4f0 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 4b689853286 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new f4830d400ab 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 380b46779c9 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new e1a6751e92c 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 737e76fa3b4 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new 8ca0e8a1f93 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new bb354348b77 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new c2daddf74c4 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 815afc3ca08 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new b08c10e45fd 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new b5be86edf4d 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 6b1fb13c16a 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new c3c72236b4c 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new c0aa3fbc62a 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new ea9b950f730 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 72e7251733e 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 8d5d3bd1b58 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 3a013a94170 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 989eb7ec4e9 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 84c956eb672 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 38ffb51e0a6 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 411879111fb 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 4cf1b4f74e5 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new e8dfb5b0286 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 0310b9d7f45 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new a7885f98b30 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 5be151b9d6e 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 92c21c1ce9f 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 8c318840f83 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new e2536ccb572 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 6cf40f9e0ed 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new a05fa658a78 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 05f74e351d7 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 4e68bd01056 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 72ed91c2e56 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 5ee6bcedef2 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 55cfa18838e 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new f088a94bd7f 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new d521e94ee61 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 86bc69bce24 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 89a5657294b 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 2552534de75 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 7b4bb8ab9fd 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 17750f98542 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new b11ed300fbd 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new 80537b6fa0d 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 01118ee48ae 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new c0364508599 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new d797c12765f 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new ee38660ad4c 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 1886130caee 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new b6fb4055127 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new e05f49addb9 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new cc59c9282fc 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 7f444169df5 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 40ab4749c9f 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new d99fb45f684 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 65ca1168547 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 11bdb1eedba 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 6138398974c 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new e05f1ee7935 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 22a6aae1cb7 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 4300f87f953 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new fad3effe4a6 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 2d25e775ad2 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new db469e122db 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 38791f22057 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 34c497e064a 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new de67044a1fc 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new d9f6e6864a0 209: onsuccess: #18: 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 (4543b178d1f) \ 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 1784 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 52388 -> 52192 bytes 04-build_abe-gcc/console.log.xz | Bin 236052 -> 236912 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8784 -> 8280 bytes 07-build_abe-glibc/console.log.xz | Bin 235496 -> 235992 bytes 08-build_abe-gdb/console.log.xz | Bin 50416 -> 50988 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3744 -> 3756 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2012 -> 2000 bytes 11-check_regression/console.log.xz | Bin 7304 -> 7516 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 19 +- 11-check_regression/mail-body.txt | 75 +- 11-check_regression/results.compare | 39 +- 11-check_regression/results.compare2 | 146 +- 11-check_regression/results.regressions | 39 +- 12-update_baseline/console.log | 36 +- 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 | 77 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 39 +- sumfiles/gdb.log.xz | Bin 2945332 -> 2929564 bytes sumfiles/gdb.sum | 4400 ++++++++++++++++--------------- 31 files changed, 2514 insertions(+), 2410 deletions(-)