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 5059b469655 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards a0ecedc8c54 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards bafe3629d39 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards c492868ed1f 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 7d0aec42b78 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards fb88acd9620 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 0ef22e8227f 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards e044f113530 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards e281e216fce 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 7f38deb443f 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 46ebd4ed6ac 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 7365becd81b 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 90f8b7029cb 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 2570ce5e5bf 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 9893872529e 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 903eebd1dae 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 2d62b3e4d72 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 27d8d923cb4 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 518c12f1099 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 8e628f317fc 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards a30fd7fae7e 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards ce07fe9028c 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards b178c8b3825 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards 75805201811 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 19e43330f85 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards e975a2d24af 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards 29beb7fddbb 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards e39f6a7da3d 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards 7f5302946cd 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards 1ed6752cfd3 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 3d8595c916e 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards 4949c0c0533 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards 4a24704ca5f 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 41ae7da2b20 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards 464aac3f9e1 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards 5f0375e748f 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards 8db3b2163e9 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards fc36d5c2a38 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards 65775091d45 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 0baaf7cffd9 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards b6586bd6c5b 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards dcd6707f409 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards 4daa45c9bcf 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards 103aa1e547e 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards ef6c0ea4e19 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards c7c73be73a2 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards 2b2eb83b4d0 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards ecbadcec1b1 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 091ae60f7cf 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards 680c032451d 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 33aa139441d 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 240222ddeff 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards d8f92499c4e 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards dc5706e9c10 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards 72a1f315ee7 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 4ea5e392b2c 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards 0e2b69a62f3 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 0588b64d690 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards aeb91ccfc06 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 4ef069beed7 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards 7c4252a4d75 149: onsuccess: #684: 1: Success after linux: 10 commits discards 4a11af19fd5 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 99ef5a2f839 147: onsuccess: #681: 1: Success after gcc: 6 commits discards cd0a9df1e62 146: onsuccess: #680: 1: Success after binutils: 20 commits discards ffc7398c874 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards 3ba97d8bba5 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards ac14422c464 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 83116881812 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 9b1f4c85825 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards e5c51f9f676 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards 9f53c7701c2 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards f27664af743 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 134e9c7f4fe 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards 175cf7f8848 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 6c289b4f26c 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards c7d6db7fdd4 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards f72d959600d 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards d0ecebaab97 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards d12d3efd1b1 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 95752f9e4ad 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 36799515a10 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 4bae8978ed2 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 6ae0eb5cb03 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 5358c79a7ac 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards bc5fdef5001 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 75e1a1ce51c 124: onsuccess: #657: 1: Success after glibc: 2 commits discards ca1842d04ff 123: onsuccess: #655: 1: Success after binutils: 22 commits discards fd0081a4af2 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 58607a914e4 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 774d1059f2b 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 2f9e0689cbe 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 6775ae9c417 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards d4ff572e381 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 7dca430a2e6 116: onsuccess: #647: 1: Success after linux: 3 commits discards b4c86e17091 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 08c439fc658 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards dc04f1c5cc4 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 96990d266b4 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards a4b2fa7529b 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 9aa4510464f 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 8ff885aa967 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 2c8d857f338 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 072a25255d5 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 0c0e4a4e423 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 918149d312f 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 5d01ff8d53a 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new f499fe318d7 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new f4c96081a7b 115: onsuccess: #645: 1: Success after binutils: 27 commits new 89920b8c1a9 116: onsuccess: #647: 1: Success after linux: 3 commits new 344f4444481 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 8c78f8bb9d6 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 8884af864d7 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 788d3933257 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new ce8cb6e8741 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 8956f088a5f 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new c77f5e03e82 123: onsuccess: #655: 1: Success after binutils: 22 commits new 05c5ef0de9e 124: onsuccess: #657: 1: Success after glibc: 2 commits new 0ec595fb9b6 125: onsuccess: #658: 1: Success after linux: 3224 commits new 60e88c51bf4 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new bcfb5391492 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 5113e3357a1 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new ad0f1ff799c 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new b96e99c3a4e 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 1ded2462d01 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 77881cf5ac3 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 1cd610e6957 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 8c7c1847bfc 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 7f902e856ad 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new ceeec435886 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new b6b52c8b488 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new a4e5001ec88 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 7f580ccf03b 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new de128f19213 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new 0a521bd0f71 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new 8cbf20f132a 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 04427811d50 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 24158225a29 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 299eaa18f80 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new f77c0813449 146: onsuccess: #680: 1: Success after binutils: 20 commits new 3477c9f65c7 147: onsuccess: #681: 1: Success after gcc: 6 commits new 9e18ba165a5 148: onsuccess: #683: 1: Success after glibc: 9 commits new f38447e0e4c 149: onsuccess: #684: 1: Success after linux: 10 commits new 33a2977dce5 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new 2c3ed3f8a9e 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new ef9e68e567e 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new 6fceff57ea5 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 3ef649ee4a7 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new ba40d515d7c 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new a1cfcc51881 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new fe05424b9e7 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new 7c145db268f 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new db61cb18254 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 0373ffd1daf 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 93f0dacfe72 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new 864664ffb45 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new a74bd6b17b5 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new 2e5d91568d8 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new ccbdd103720 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new d43c33615b7 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new 9f6bd1ce358 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new c4577bb0204 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 4d7f81d3e6a 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 27fb33a82cc 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new 70a08c8d5e9 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new 00808566063 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new a8f86fde468 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new 4e3746814fe 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new ae8e486fe4a 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 0da2b72b906 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new d144662afd9 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new 626fa7bf7ac 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 02156e9981a 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new da0ca84fc27 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new cadc874bb99 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new 232254e1b9c 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new eab93e84c7e 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new b85afd672d3 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 97a71ab2946 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 1469c1f412a 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new 4582f372808 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new 20d4222e67a 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new 53ec4fa791d 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 52472aa85b5 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 3e6cabb0d67 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new a7703ab4c31 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 11284671d6a 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new e0a3b4c3d5b 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 4702ec374bf 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new bba6c46b029 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new bee8a9e5e68 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new e88d3ed36b2 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 9d59170997f 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new a547c6cc6fc 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 6b7b26f843f 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new e28a3fdbdaf 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new e11f241ce2b 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 1a1662d9dda 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 99245dff125 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new cf87caa7014 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 7d823a8ec07 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 7f4d0b05c64 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new e865eabb3f1 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new e2737c86e00 210: onsuccess: #20: 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 (5059b469655) \ 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 1744 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 38872 -> 38764 bytes 04-build_abe-gcc/console.log.xz | Bin 203768 -> 203564 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8552 -> 9028 bytes 07-build_abe-glibc/console.log.xz | Bin 244316 -> 246092 bytes 08-build_abe-gdb/console.log.xz | Bin 38440 -> 38308 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3780 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2184 -> 2020 bytes 11-check_regression/console.log.xz | Bin 6052 -> 6036 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 +- manifest.sh | 38 ++-- sumfiles/binutils.log.xz | Bin 62888 -> 63068 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83976 -> 83968 bytes sumfiles/gas.sum | 274 +++++++++++------------ sumfiles/ld.log.xz | Bin 122228 -> 122240 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 27 files changed, 393 insertions(+), 393 deletions(-)