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 50d527d5199 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards dba39fdb826 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 58de53d9774 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards d96378e29c7 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 480f646c8fa 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards f112e53e833 212: force: #24: 1: Success after binutils: 2 commits discards 7ff51e6703e 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards c36f4db8b89 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards c132efc54b8 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards e0c5be9f747 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards c755be5d2f2 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards a82fdd6eaf9 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 28021986832 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 6fd351aa5e1 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 6c0300a028a 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 3da70713184 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards e29bafaa814 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards eb455fd50b6 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards b08a9ac19c7 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards f21068e2d51 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 7e50db61040 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 8eeb695dcff 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 6fb733f849b 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards a11f3d05509 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 21fed43a5a5 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 55aaaa849b2 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 17db1c7d1e0 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards b836f1c9cf4 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards 4bf63f121ff 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards e92571a37e3 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards c45a2347da7 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards e537d4db67c 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 25aed00ec19 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards 3e3af519b5f 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards 46b49397f02 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 52d664fa071 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards 25f8d034fc4 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards 810884c6ef6 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 443e71bdb72 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards f7a79dcd125 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards e2fe21a22c4 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 8ad42dc07d6 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards b1b3a38321c 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards 7601c2f2176 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards f54f84e7a58 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards b2f42529ac4 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards 3c5e6176312 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 14ff0da6744 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 1e938b519d2 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 1743e2cc443 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards 4f083506b6d 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards 268ee384c06 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards 87a810fe608 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 72fc56fa006 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards a4c268c9f42 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards 93cbc78b6b1 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 31316713d13 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards 1c8f360c26b 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 2700d713e89 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 393985b1eed 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards c7401599a15 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards f43e9481e09 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards d50d4b5362a 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 1839e7aef78 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards 53aef1da200 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 3ba01d58221 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards 86c0bb03a9e 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 63956c691a3 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards 1585631af91 149: onsuccess: #684: 1: Success after linux: 10 commits discards a226781b670 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 3a173db8930 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 29add306075 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 940cfd06329 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards 0f6d4bbdf9c 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 66946f7634e 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 4b6337d39a4 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 26cea8c3c8b 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards 0486b8a2d74 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards 0c7480450a7 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards 827a55100c9 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards a88627d0897 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards 4c69af23a49 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 819c92be357 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 69437c375d1 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards ea35e0a1a4f 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 377fe0eabbc 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 3151c019f1a 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 2387e7ece9d 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards f87f48cc26d 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 6db6c793ecb 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards d5e6879e7ab 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards e3a2bcacd6f 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards af866fc37f5 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 52281e8c090 124: onsuccess: #657: 1: Success after glibc: 2 commits discards e65b2ce7ef4 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 7d012b71f8a 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards aee708bb663 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 01835fb520f 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 9915516ff11 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards b0f972d4e6d 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards ef96c8cf97d 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 3e7660e29c3 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 8f4fe08e694 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 4c123a726d6 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 346195e0b79 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 203186d94d6 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 56ebc96a925 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new c61356f161f 123: onsuccess: #655: 1: Success after binutils: 22 commits new a3a9cc8c7c6 124: onsuccess: #657: 1: Success after glibc: 2 commits new c2855d4c8ed 125: onsuccess: #658: 1: Success after linux: 3224 commits new e67f4318839 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new e88e7bd2523 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 64f22b80227 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 6252db7efee 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 38c94fece50 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 8f565646fb0 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 78bf2ebf887 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 1623678f8b5 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new d8b258543db 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new afc89332a7d 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 22385ec453d 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new c5637ea760b 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new ba703a6191c 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 2e1f917b76a 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new 479e697a3d1 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new 9972de91ecc 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new 52759a745e9 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 4725e9ad33e 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new b0c7e37b26c 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new bd19d26d271 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new 26ed271500c 146: onsuccess: #680: 1: Success after binutils: 20 commits new 59ecc2b9da5 147: onsuccess: #681: 1: Success after gcc: 6 commits new f0796fd7eeb 148: onsuccess: #683: 1: Success after glibc: 9 commits new b362726024f 149: onsuccess: #684: 1: Success after linux: 10 commits new 59988c67f91 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new ac7275ace9a 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 2c913f18501 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new eeddbccee01 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 873fa6feec4 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new 47e0ea2a856 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new ce597050f64 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new 9acc4375693 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new dcb3f104da1 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 7c2e0993986 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new b00d17d6fbf 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 57ce9578344 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new cd22e17241a 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new cb0cf3c2a16 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new cadad796dd1 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new d12545e8faa 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new bb75e05f08c 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new fe260035609 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 55b71e8a830 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 6052608dced 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new c8bdb969020 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new 9c4d7d145a4 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new e30c177741f 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new 2e689d3f72c 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new e7bedfb4c56 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new e44d75718a5 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new c47cd983595 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new aff3bd9230c 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new 5635356dee8 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 6237796f60a 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new 54168336773 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 6ec4c2fa980 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new e06cc71b5bd 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new b1d1408c004 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new edebfb21bce 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 815d79f6575 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 54110599d75 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new 53ac65108a6 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new 55adbdf32ce 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new a202c5fd696 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 70b2da3cf0b 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 2e88ae65906 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new caf6d0f8249 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new a73b2e3d85a 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 88150580b10 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 9d5c2d2a159 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 34745968269 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 373e07c43ae 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 794789d21e9 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 121a91851d0 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 0317379b294 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 3651b2c7281 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new dc837a5bbaa 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 7906b1dc03d 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 936c7b28a2d 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 1352a6270ff 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 291f20c78c8 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new c524bd299fd 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 20f8ea4d69e 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 75f555064e3 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 7a3b5a70ce8 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new c856b740850 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new ef413868a24 212: force: #24: 1: Success after binutils: 2 commits new 934c4e1dca7 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 55e1c6fef11 214: onsuccess: #26: 1: Success after binutils: 12 commits new 27ea28bde4b 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 258ae2c2458 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 56a6ba4d7d7 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 6c42d888502 218: onsuccess: #32: 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 (50d527d5199) \ 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 1792 -> 1932 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2548 bytes 03-build_abe-binutils/console.log.xz | Bin 34864 -> 35556 bytes 04-build_abe-gcc/console.log.xz | Bin 202864 -> 203944 bytes 06-build_abe-linux/console.log.xz | Bin 8392 -> 8340 bytes 07-build_abe-glibc/console.log.xz | Bin 241760 -> 241596 bytes 08-build_abe-gdb/console.log.xz | Bin 34492 -> 35296 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3780 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2096 -> 2680 bytes 11-check_regression/console.log.xz | Bin 4732 -> 4968 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 4 +- 12-update_baseline/console.log | 58 ++++++++++++++--------------- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++---------- sumfiles/binutils.log.xz | Bin 62964 -> 63020 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83984 -> 83988 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 122500 -> 122492 bytes sumfiles/ld.sum | 4 +- 29 files changed, 66 insertions(+), 66 deletions(-)