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_binutils/master-aarch64 in repository toolchain/ci/base-artifacts.

discards 6c42d888502 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards 56a6ba4d7d7 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 258ae2c2458 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 27ea28bde4b 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 55e1c6fef11 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 934c4e1dca7 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards ef413868a24 212: force: #24: 1: Success after binutils: 2 commits discards c856b740850 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 7a3b5a70ce8 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 75f555064e3 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 20f8ea4d69e 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards c524bd299fd 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 291f20c78c8 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 1352a6270ff 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 936c7b28a2d 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 7906b1dc03d 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards dc837a5bbaa 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 3651b2c7281 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 0317379b294 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 121a91851d0 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 794789d21e9 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 373e07c43ae 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 34745968269 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 9d5c2d2a159 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 88150580b10 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards a73b2e3d85a 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards caf6d0f8249 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 2e88ae65906 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 70b2da3cf0b 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards a202c5fd696 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards 55adbdf32ce 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards 53ac65108a6 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards 54110599d75 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 815d79f6575 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards edebfb21bce 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards b1d1408c004 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards e06cc71b5bd 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards 6ec4c2fa980 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards 54168336773 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 6237796f60a 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards 5635356dee8 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards aff3bd9230c 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards c47cd983595 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards e44d75718a5 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards e7bedfb4c56 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards 2e689d3f72c 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards e30c177741f 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards 9c4d7d145a4 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards c8bdb969020 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 6052608dced 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 55b71e8a830 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards fe260035609 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards bb75e05f08c 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards d12545e8faa 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards cadad796dd1 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards cb0cf3c2a16 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards cd22e17241a 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 57ce9578344 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards b00d17d6fbf 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 7c2e0993986 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards dcb3f104da1 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 9acc4375693 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards ce597050f64 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards 47e0ea2a856 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 873fa6feec4 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards eeddbccee01 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 2c913f18501 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards ac7275ace9a 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 59988c67f91 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards b362726024f 149: onsuccess: #684: 1: Success after linux: 10 commits discards f0796fd7eeb 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 59ecc2b9da5 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 26ed271500c 146: onsuccess: #680: 1: Success after binutils: 20 commits discards bd19d26d271 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards b0c7e37b26c 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 4725e9ad33e 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 52759a745e9 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 9972de91ecc 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards 479e697a3d1 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards 2e1f917b76a 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards ba703a6191c 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards c5637ea760b 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards 22385ec453d 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards afc89332a7d 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards d8b258543db 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards 1623678f8b5 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 78bf2ebf887 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 8f565646fb0 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 38c94fece50 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 6252db7efee 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 64f22b80227 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards e88e7bd2523 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards e67f4318839 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards c2855d4c8ed 125: onsuccess: #658: 1: Success after linux: 3224 commits discards a3a9cc8c7c6 124: onsuccess: #657: 1: Success after glibc: 2 commits discards c61356f161f 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 56ebc96a925 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 203186d94d6 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 346195e0b79 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 4c123a726d6 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 8f4fe08e694 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 77602d0a263 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 7945987ade7 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 5f9bb8890b6 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new b4e218a5b53 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new dfc9bf693ce 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new fad462aa1e0 123: onsuccess: #655: 1: Success after binutils: 22 commits new 468b1acc271 124: onsuccess: #657: 1: Success after glibc: 2 commits new 9320dc6bd46 125: onsuccess: #658: 1: Success after linux: 3224 commits new b15472cc84d 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 114a37e7f95 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 85620865420 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 2aa3307d2cd 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 4c0756d0e3e 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new ecf5c986132 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new a6012f325d6 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 2aa944ac43a 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 9f57336ff3d 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 65eecf01e7a 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 733f8b9369f 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 2d460c1b2db 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new 57c9d2d9ad9 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 192d34d1f49 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new b3a82348a13 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new 221cfbc6871 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new ec8be7d27ff 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new f9b8e006639 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new d4737196a26 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 16cf5e59e42 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new fcc92967bcc 146: onsuccess: #680: 1: Success after binutils: 20 commits new 0464a1d18fc 147: onsuccess: #681: 1: Success after gcc: 6 commits new 6c54fadff1f 148: onsuccess: #683: 1: Success after glibc: 9 commits new ee3101d0405 149: onsuccess: #684: 1: Success after linux: 10 commits new 07db6ce4ff8 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new 20941b1595b 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 7f56717f448 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new 70142f0f05d 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new e2abc45de4b 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new 8ce911a9a88 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new cb3c5fd47e3 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new 65f2b8635ea 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new 780ec62f143 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new cf11ec43503 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 1ce5b99ff95 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new c8945575f94 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new 576c80edaf7 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new 34b9d155f01 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new ad74c1ecf1f 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new 93e25be1955 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new 10c3d4fb9e4 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new 5997abe7e9d 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 297d6add00f 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 06226003f49 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 4d46d14a9fb 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new b13d256f684 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new 0ea23f9ab2a 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new 267769e9344 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new e3729cd46d3 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new c8ab2761ff6 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 7a2ce2ac90f 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new 01189b35cdb 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new 00b8ea72767 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new d29755c4cf0 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new 001b0e86793 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 185dbead15e 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new 1af260f55e7 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new d969ce189b0 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new 5e4c2813eb0 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new fa35fb1a835 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new c0838f576fc 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new ba19437c4f0 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new ae8c6c4b125 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new 853b82ee65c 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 56d3e3b57e9 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 17a8f82dd0b 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new ccc05c70147 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 605c8a02d0c 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new c7e0a1e0e3e 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new e8d02501f92 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new abfdc046896 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new d45dce8b138 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 1393a1d9805 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 9be88d6ffb7 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 4855c145b3f 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 45b24151c9c 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new ff1f4f76d8c 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new a6154af024f 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 0a8e8f7cd87 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new f8271819884 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 2a84697dd19 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new ce2090d6812 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 4947f0642a3 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 13757c3e7c8 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new de3dd601d22 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new ac6b8530b61 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 132ae37654b 212: force: #24: 1: Success after binutils: 2 commits new ef9fea6fd27 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 2085ebd7d23 214: onsuccess: #26: 1: Success after binutils: 12 commits new 7d430dec64c 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 5460f19a960 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 2db25954b79 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new e3a0c8ccd0d 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new 5df62f5376c 219: onsuccess: #33: 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 (6c42d888502) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...]

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 1932 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2548 -> 2532 bytes 03-build_abe-binutils/console.log.xz | Bin 35556 -> 35544 bytes 04-build_abe-gcc/console.log.xz | Bin 203944 -> 203708 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8340 -> 8356 bytes 07-build_abe-glibc/console.log.xz | Bin 241596 -> 240956 bytes 08-build_abe-gdb/console.log.xz | Bin 35296 -> 35308 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3820 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2680 -> 2704 bytes 11-check_regression/console.log.xz | Bin 4968 -> 4800 bytes 11-check_regression/results.compare | 8 +++--- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 40 ++++++++++++++--------------- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 ++++++++++++------------ sumfiles/binutils.log.xz | Bin 63020 -> 62576 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83988 -> 83960 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122492 -> 122476 bytes sumfiles/ld.sum | 4 +-- 29 files changed, 57 insertions(+), 57 deletions(-)