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 888161dd0f5 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards fafdc3a651a 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards a16d98a8cec 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 4d50fb1b3b6 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards ccd9f675029 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards bc78622a584 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 2e2ccdbe167 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards ca48664377d 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 8576aaf98cd 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 7a1ec0e2555 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 35b5e308ac6 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 798a364e85e 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 49491ba3f52 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 61eb7d6bfaf 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 0d9cd421160 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 67f6b6f1b97 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 7dd8f268c1e 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards e4fbc3c4482 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards 95a826e8852 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 42720cd079c 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards a859e3986be 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 9c8c16eb4b0 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 2324144cf2b 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 82947a6c5ed 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards dbdbfc2c9f4 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 353357154f8 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 803d4dce5c5 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 6abd5214fcc 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 34f824e3b2a 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 48f0d900246 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards ab0a9e5dde0 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards d818d322534 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards f07e4570432 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 225380f5023 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 6fa4e49ed90 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 82a0f8f2f1c 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 7b83349d8dc 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 23d2ff89cbb 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 22330c49425 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards cd79be3796c 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 65214ac32d1 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards a64d468b0bb 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards be94c6e1406 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 32dc48294d8 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 1178181b02c 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 32134f867e6 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards ec58c9a5943 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 7c635f295fa 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards dd14ed26e0c 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 42e1fa6496f 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 30aae4b30fa 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 385c201b529 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards aadae350937 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards b7fb589a45e 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 15f7ebc1a1a 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 36190add4f3 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards e1bc7ba9970 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 94e19fa00ca 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 78e07290ab5 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards eb9634f2e84 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards 7240af720e0 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards b9f68048942 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards 70d5a2a73e8 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards ad8102376d4 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards bf933db4032 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards acb433b90d5 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 53bfd2e48f8 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 2272142be17 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards fdf9f95673e 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 1ea4dfff72d 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 3b26d4424dc 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 42c0ef91aa0 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 2003cda7726 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 4af97a29873 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards d1201b05be7 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards 891973390e1 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards ccbdfffdd4f 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 413322d175e 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 49bd356b6a3 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 3b87c8dde98 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 375968e7da1 125: onsuccess: #614: 1: Success after linux: 12 commits discards 99f51169ab5 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 2240af1faab 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 8c920cb739f 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards fe2bbfb00b2 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards e7e9e3fedcd 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards ca419d89a5b 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards ccfb48ca5c0 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards d76c14491b7 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards 9afadb1a4ea 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 2a17fe37bad 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards d8541d1f3e3 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 4fb72f0b828 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards d03952b7210 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] discards d1e9ce70f4c 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] discards 4c7cec082e0 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards b48c648b1c1 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards e5518cf5036 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 55845ce3db8 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 23098f17a1a 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 96f99acd72f 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 0091c5f55cf 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 680e8136d1e 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new ce8d8179cdc 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 407a0f523ff 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new fa272af261d 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 4f7fa839d55 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new e0b44dbd76c 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new 6b77acc3f26 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new bc1dbbe18ff 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 9ed6683fa66 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 4d3f8368a1e 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 0de8d41a751 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 19652db9ec1 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new 9efb8fe3311 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 3c8ec3d4178 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new fb480a53d9c 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 64caa1223b6 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 2683d5d25ed 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 3233e0e986d 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 3f0f321e09f 124: onsuccess: #612: 1: Success after binutils: 18 commits new 5bcc1bf6049 125: onsuccess: #614: 1: Success after linux: 12 commits new 92eab701219 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new c9ab101fa17 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 2b82c36e5b5 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new ec96a1000c9 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new a547e36e64d 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new f59ba415dde 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 673b9a40048 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 749dcd77f6b 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new ffe752ec454 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new b55908754a8 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 61fcd13505f 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new eff7db0551c 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 495319cf030 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 5fe82307676 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 8267b838cdc 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new c436b15fb22 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 2559172e02d 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 874e7650b93 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new b563c7c1fd2 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new 17944145f6f 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 73ae6132a00 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new d64677642f0 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new f48268111a7 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new e009fe6704c 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new caf0903620f 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 83e0b138a71 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new f6a2f96834a 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new c4f6181bd11 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 13abae13400 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new e06e82a64a9 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 36a6c59d3d2 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 2f057410a60 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 35b841f09ea 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 50bb3e21ad6 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 784d497d20c 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new dbf89d54903 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 56570e19a46 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 0fcd79a3c0e 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 0c1a1201313 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new cac366e5041 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 6893c17db7a 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 22a197d2725 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 828222726af 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 273c5dfe506 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new ce4edb467b9 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 6be9ce4b7f5 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 0f4ba5ec267 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 6d71a10b42a 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 49b3d12e890 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new a5eed679d5c 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new f2d598c4087 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 390c3a3a63e 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new e7574078207 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 48fc4920bcc 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 217d63a9a69 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 79469866667 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 810da6a3e06 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 22adf59ec4d 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 87a8d65fbdb 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new 5fcd9aa24e6 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 16216a020ed 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new ec9f07849e7 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 16661e6ef0f 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new 89e0e7dce41 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 846568a5547 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 182c501f2ac 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 7738e265ff3 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new b4cdbbd5870 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 3d7ac1820bd 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 3c741310130 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 7cc6b4405a5 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 234cfe98258 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 7a92d2413d5 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 44a8db4e1a8 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new c94754397f8 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new e4c1abc69f0 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 7019296bca3 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new f16f14286a9 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new e7b4dbb75cb 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new e8d7fb39fdd 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new d09c0d363c0 206: onsuccess: #15: 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 (888161dd0f5) \ 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 1804 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 52600 -> 52708 bytes 04-build_abe-gcc/console.log.xz | Bin 236468 -> 236836 bytes 06-build_abe-linux/console.log.xz | Bin 8496 -> 9596 bytes 07-build_abe-glibc/console.log.xz | Bin 235904 -> 235664 bytes 08-build_abe-gdb/console.log.xz | Bin 51008 -> 51768 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3768 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2008 -> 2244 bytes 11-check_regression/console.log.xz | Bin 7620 -> 7808 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 19 +- 11-check_regression/mail-body.txt | 108 +++++------ 11-check_regression/results.compare | 41 +++-- 11-check_regression/results.compare2 | 289 ++++++++++++++++++++--------- 11-check_regression/results.regressions | 41 +++-- 12-update_baseline/console.log | 64 +++---- 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 | 110 +++++------- mail/mail-subject.txt | 2 +- manifest.sh | 34 ++-- results | 41 +++-- sumfiles/gdb.log.xz | Bin 2949580 -> 2931008 bytes sumfiles/gdb.sum | 309 +++++++++++++++++--------------- 29 files changed, 585 insertions(+), 487 deletions(-)