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 8fc752f4a7f 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 6e29ca0aacb 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards c4671904831 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards fe877fde434 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 389dd206062 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 4844673247c 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards af4a79973c9 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 4e16e917e1b 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards e43cfd5a8f1 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 816da92c5ad 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 71ef8715419 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 20db68e578a 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards bbd90fe1da4 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 7fc2377602e 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 69ec791e373 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards da8a8f64d1a 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards f226ba89553 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 11463fbca1f 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards d36ea1ea08f 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 2c08910eb84 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 483a126dcf2 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards cedffcb76ef 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards 26d7de5eee1 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards d5a4c481d36 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards 535d872abf5 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards 914107ba15e 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 336345dbee6 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards ec787a19098 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards 91eeabdc936 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 06823571ed6 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards e150e6a60d9 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards 73e550d7bb3 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards c4cc654f216 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards e4399ef1f27 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards bac75dba64b 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 1fdf69f746c 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards 9850111eb3e 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards ad5b8befc9d 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards 0e53beff629 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards 0c681492c18 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards e228d83656a 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards b81e68889e1 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 1b62a037602 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 46f3eba0a1a 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards cd65dac47da 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards 56f6a48e588 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards e0dfc9dc128 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 3401a7e39a7 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards ef21c1e1124 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards ef181f5049e 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 3b259478351 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards dbe9e257065 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards a9729f54ba8 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 2f3786b8451 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 0ddc4d6b50c 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards e1dba2bdd66 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards de788c83b09 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 839d55420dc 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards 0ad01e52d32 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 488dd1f84c7 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards cf8a827e66b 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 68e7599faa1 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards eecdfe721c8 149: onsuccess: #684: 1: Success after linux: 10 commits discards cea081b7c76 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 5a8e1f6afb1 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 78957721937 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 077fc89a5ce 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards 4a6b0422a7e 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 95d6b98eac0 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 19f60ebcdc9 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards d5836656c91 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards 52f68b2aa83 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards aa25579c0d5 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards 73f97305c78 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 1d60c1c86f4 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards 552b89547a3 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 2bf408ec596 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 63deda6d649 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards 99c60f3e158 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 62bf32abc62 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards cabaf79a1cf 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards bd8d0a8507e 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 1058829ca9d 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 6efd84e0d13 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards a663192d15f 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 5028611a72c 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards dd8e83f5343 125: onsuccess: #658: 1: Success after linux: 3224 commits discards fa455300ce1 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 43dca4c83ec 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 2c53acf8866 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 771c964a31d 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 0cd6b4485b4 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 6c31814f27f 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards d15dab9ac58 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 96c83646e18 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 2debe2f1360 116: onsuccess: #647: 1: Success after linux: 3 commits discards c720e550082 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 3968e2a12be 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards d00a674cb21 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 91a724754b1 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards df97b734f88 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 999ec8d79aa 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new dcbdab3a058 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 890843da2b2 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new af6f1a6c701 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new e71a85dc0eb 115: onsuccess: #645: 1: Success after binutils: 27 commits new 3d5c6e260d5 116: onsuccess: #647: 1: Success after linux: 3 commits new 4d7cf2ad040 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new a947f6736e5 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 7a75dea3d2b 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 4e7633f22af 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new da9214d5b3f 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new ce81bcc2498 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 67cf3e9f5f5 123: onsuccess: #655: 1: Success after binutils: 22 commits new fca17e32a2b 124: onsuccess: #657: 1: Success after glibc: 2 commits new 711180fb93d 125: onsuccess: #658: 1: Success after linux: 3224 commits new 7c735ce988f 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 80bb862f25a 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 9193b2345f0 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 8f93da18fdb 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 7cb72c85f73 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 1353807f14b 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new a71f458c3fa 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 4e5d027d446 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 7dd02395b17 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 0cd17dafed5 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 4fb63b715ca 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new bd69f3d7f9a 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new 738254df701 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 8e6ceb6d505 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new d97848c944a 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new c4f9983aa57 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new b37a6f3fa7e 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new fb9d574eb02 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 7d5d99cc8b3 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 1defbe9eb61 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new ec590be6ae6 146: onsuccess: #680: 1: Success after binutils: 20 commits new fd8995bd76d 147: onsuccess: #681: 1: Success after gcc: 6 commits new d5fd0c98213 148: onsuccess: #683: 1: Success after glibc: 9 commits new 4b85f6b8dd9 149: onsuccess: #684: 1: Success after linux: 10 commits new e0cdc06ceae 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new f411babb411 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 880ffacdc76 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new cc0cbf52192 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 64e8c9006c8 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new e6c56bf7dbf 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new d25f99a292f 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new 9c98c7c9d34 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new afe7988a0c9 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new be2fc8ad262 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new e929e7f5826 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 3a227ecc9b5 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new 8eac1321f28 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new 258bd3b63e6 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new 32cbf082a56 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new 3e58e1c8b81 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new 8f7de082f91 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new c5a637e41a3 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 36bf25527d2 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 25c0051a4e0 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new ca07a678831 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new d8ccc02ab41 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new e80882aa849 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new c822e673451 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new 49862106505 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new 4e77618cda6 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 841350e3f62 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new 6d7e17575a9 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new d9898c420f7 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 0d287d2e855 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new 894e8bbeff5 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 77d39ce378b 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new 1cd67853286 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new c442ed3cb4a 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new 8a15eb53173 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 1d006334e80 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new d0be0916d20 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new 571100967a2 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new f89b7876728 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new de633a93e5d 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 9e3a7868daf 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 4f44dd829be 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 032e8dc0616 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 0a75f26d30c 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 353096743a4 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new ded5d13d6f3 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 2387b97c180 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 849a6126ceb 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new e29e16536ab 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 88ecec7b88e 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 09e4d4601a1 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new e2053fe5cf9 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new dcb958ed0a6 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 1c82456e5ac 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new ba03dee73b4 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new b539d0bd059 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new dadfb86f0d4 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new e8635e71b05 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 46ba31c02aa 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new cc5da72c581 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 70ce1e38067 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 641d032472e 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new d23fc64eb8c 212: force: #24: 1: Success after binutils: 2 commits

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 (8fc752f4a7f) \ 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 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 3536 -> 3468 bytes 03-build_abe-binutils/console.log.xz | Bin 40156 -> 39052 bytes 04-build_abe-gcc/console.log.xz | Bin 204944 -> 204252 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8504 -> 8616 bytes 07-build_abe-glibc/console.log.xz | Bin 244268 -> 244500 bytes 08-build_abe-gdb/console.log.xz | Bin 38952 -> 39216 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3776 -> 3796 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2080 -> 2200 bytes 11-check_regression/console.log.xz | Bin 4416 -> 3060 bytes 11-check_regression/results.compare | 8 ++--- 11-check_regression/results.compare2 | 45 +--------------------------- 12-update_baseline/console.log | 46 ++++++++++++++--------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++------- sumfiles/binutils.log.xz | Bin 62928 -> 62956 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83992 -> 83944 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122228 -> 122252 bytes sumfiles/ld.sum | 2 +- 26 files changed, 46 insertions(+), 91 deletions(-)