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 e10f8ff1868 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 52a98099d8c 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 52174616fa4 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 7db776d2096 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 994d58cb560 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards f9a376b341e 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 575bd77bd8e 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 35ff8571f00 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 6b262eada56 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 0982cca8d2f 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 4100b880516 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards a5d20ff98c9 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards f185faae621 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 91e61b543af 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 0160ef2eab5 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 4c3e086f16d 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards fc9ec55fd3c 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 9e7486edf59 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 5b86e20aff8 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards 019277b6298 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards 5826ad2e9d5 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards 5c463acfdfb 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards 1ea67267f96 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 83f6f5d4409 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards 24eebbebc2c 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards fd8642737d6 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 82c9bc5d6e5 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards e0725da3d64 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards ddb7ad522cd 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 7d67a5359ac 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards 4ffbf9f1777 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards 0cd69df1f39 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 126f8ac15c7 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards 547aec28713 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards fa5da74a72f 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards 6fbcc76badc 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards da711585b79 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards 15b52ae4275 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 4f05d041770 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards c2e16d523c2 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards b8c4bc60599 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards ad7680a1195 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards c1affd1e835 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards 210d8210db8 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 8860f6f514a 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards 2c6f58d6c03 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards b5eb9462576 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 50948fec34c 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards a65f7a4fb15 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 6391bd774c6 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards da5654e0d54 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 0129cc459a5 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards 27cc924c5dd 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards e765053fcb7 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards f0759c04b97 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards 690c018d936 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 90b41997756 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards 9d823c85f45 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 2857f233865 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards b73da87c597 149: onsuccess: #684: 1: Success after linux: 10 commits discards d4d75c87286 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 7fbb7b30d56 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 1aeaac5dc9f 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 79f5215ca41 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards ae09a89492d 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 7d18a7f0867 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards d3d4456a55f 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards a79f4dc52c2 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards 1728e496188 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards d773774fecb 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards 01c3cfb30dc 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 36e92d04807 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards bf9e1902806 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 5c3be21610b 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards c52b3a6c4b4 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards 306fd965e0c 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards e9bbea3e8ae 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 215459c3fac 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 6a88c997040 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards aee043a0ead 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 564ecb14ff2 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 4d2747d656c 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 87a4e32c8bb 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 5e442368f22 125: onsuccess: #658: 1: Success after linux: 3224 commits discards d406054d25a 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 0b856a42089 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 2a6361ae108 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 534d58b2829 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 915fe4f72fd 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards f122715a048 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards c0149f08cc5 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards ebed2cd09e9 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 3f7da9ab580 116: onsuccess: #647: 1: Success after linux: 3 commits discards 1f8ed6e118e 115: onsuccess: #645: 1: Success after binutils: 27 commits discards f8213ca93ba 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 1f802382b9d 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards e4b3fff9dd3 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 5196f25fb6e 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards f3397a3e92c 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 466d8568f7f 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 611291b48fa 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new f0a476d520d 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 8ff885aa967 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 9aa4510464f 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new a4b2fa7529b 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 96990d266b4 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new dc04f1c5cc4 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 08c439fc658 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new b4c86e17091 115: onsuccess: #645: 1: Success after binutils: 27 commits new 7dca430a2e6 116: onsuccess: #647: 1: Success after linux: 3 commits new d4ff572e381 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 6775ae9c417 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 2f9e0689cbe 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 774d1059f2b 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 58607a914e4 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new fd0081a4af2 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new ca1842d04ff 123: onsuccess: #655: 1: Success after binutils: 22 commits new 75e1a1ce51c 124: onsuccess: #657: 1: Success after glibc: 2 commits new bc5fdef5001 125: onsuccess: #658: 1: Success after linux: 3224 commits new 5358c79a7ac 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 6ae0eb5cb03 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 4bae8978ed2 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 36799515a10 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 95752f9e4ad 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new d12d3efd1b1 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new d0ecebaab97 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new f72d959600d 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new c7d6db7fdd4 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 6c289b4f26c 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 175cf7f8848 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 134e9c7f4fe 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new f27664af743 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 9f53c7701c2 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new e5c51f9f676 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new 9b1f4c85825 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new 83116881812 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new ac14422c464 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 3ba97d8bba5 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new ffc7398c874 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new cd0a9df1e62 146: onsuccess: #680: 1: Success after binutils: 20 commits new 99ef5a2f839 147: onsuccess: #681: 1: Success after gcc: 6 commits new 4a11af19fd5 148: onsuccess: #683: 1: Success after glibc: 9 commits new 7c4252a4d75 149: onsuccess: #684: 1: Success after linux: 10 commits new 4ef069beed7 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new aeb91ccfc06 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 0588b64d690 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new 0e2b69a62f3 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 4ea5e392b2c 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new 72a1f315ee7 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new dc5706e9c10 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new d8f92499c4e 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new 240222ddeff 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 33aa139441d 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 680c032451d 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 091ae60f7cf 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new ecbadcec1b1 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new 2b2eb83b4d0 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new c7c73be73a2 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new ef6c0ea4e19 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new 103aa1e547e 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new 4daa45c9bcf 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new dcd6707f409 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new b6586bd6c5b 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 0baaf7cffd9 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new 65775091d45 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new fc36d5c2a38 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new 8db3b2163e9 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new 5f0375e748f 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new 464aac3f9e1 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 41ae7da2b20 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new 4a24704ca5f 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new 4949c0c0533 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 3d8595c916e 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new 1ed6752cfd3 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 7f5302946cd 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new e39f6a7da3d 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new 29beb7fddbb 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new e975a2d24af 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 19e43330f85 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 75805201811 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new b178c8b3825 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new ce07fe9028c 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new a30fd7fae7e 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 8e628f317fc 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 518c12f1099 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 27d8d923cb4 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 2d62b3e4d72 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 903eebd1dae 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 9893872529e 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 2570ce5e5bf 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 90f8b7029cb 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 7365becd81b 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 46ebd4ed6ac 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 7f38deb443f 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new e281e216fce 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new e044f113530 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 0ef22e8227f 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new fb88acd9620 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 7d0aec42b78 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new c492868ed1f 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new bafe3629d39 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new a0ecedc8c54 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 5059b469655 209: onsuccess: #19: 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 (e10f8ff1868) \ 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 1752 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 38660 -> 38872 bytes 04-build_abe-gcc/console.log.xz | Bin 203552 -> 203768 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8228 -> 8552 bytes 07-build_abe-glibc/console.log.xz | Bin 244156 -> 244316 bytes 08-build_abe-gdb/console.log.xz | Bin 38348 -> 38440 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3768 -> 3816 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2028 -> 2184 bytes 11-check_regression/console.log.xz | Bin 5880 -> 6052 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 42 ++-- 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 62776 -> 62888 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83940 -> 83976 bytes sumfiles/gas.sum | 274 +++++++++++------------ sumfiles/ld.log.xz | Bin 122244 -> 122228 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 30 files changed, 396 insertions(+), 396 deletions(-)