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 5b69c500cb5 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards d29c3174649 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 66998c5f584 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 562a635e73e 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 7cf55c19455 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards a7a22e4c05d 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 40267386a04 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 4ce772e19ec 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 7b92ab16ac7 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 3393f4d0925 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 2ac88893d18 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards c8d1ab33f9b 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 654df6d6235 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 630ab794bff 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards a343ce70b17 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards f3c2268c2d5 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards cd3e60656ef 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards c335ba99dc0 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards ac89c73da00 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards 3553ae9bbf9 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards 7c7f40aa438 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 49823996089 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards 50f42d1ec1d 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards db66e648757 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 7dd7ea12454 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards 8373fd76670 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards e71c7e88829 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards bbb60640771 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards 9ccdec260ad 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards b6f7ca61514 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 72ff3af0f84 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards d687ea16f1c 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards 536e1823d45 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards 77c4c774088 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards 76b0f2f82a0 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards b1dd5204ab8 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 055a513cd68 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 8e59130e2b1 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 70cefc7652f 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards e7c232fcc10 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards e9d1c5ae1be 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards e717bf9154e 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 5abad737b43 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards 966155896a3 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards 2ecbbcd29a8 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 2a290e0bee6 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards 3b2430b9954 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 043618db85a 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 8ee642a6eea 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards ec49a2b097e 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards 18b64e91d52 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards 7299aa4b8d3 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards a6e865f526e 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards d4a37a1f09a 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 9da33fc6702 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards f6e7c223ff7 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 4f7612e82f5 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards 0bbdde0a29e 149: onsuccess: #684: 1: Success after linux: 10 commits discards 9251f829645 148: onsuccess: #683: 1: Success after glibc: 9 commits discards c1cfb5ade8e 147: onsuccess: #681: 1: Success after gcc: 6 commits discards bc8db45d33f 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 66a81c5a71d 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards 5bb732d19ea 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 098ce181f94 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards f0bc1105833 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards a1ad4f1c459 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards 3d21a0d904b 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards b74a22cace6 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards a03ecb52b0e 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 4c249b9403c 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards c5624eeafcf 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 8cb925d5502 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 7690e87abf4 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards 3e585e17fde 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards ec403b82ecf 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards c584ef3f067 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 43b27d3701a 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards c7ec38cb15c 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 4d9c6501f80 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 4b397374d80 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards a1614f86747 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards a7bb50eaecc 125: onsuccess: #658: 1: Success after linux: 3224 commits discards c4bfca49f65 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 6da7d83aace 123: onsuccess: #655: 1: Success after binutils: 22 commits discards f193201c375 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards e9d985cdd68 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 9277b05f59c 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 63f8dc9e382 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards d3f983d6a3c 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 703e1547bca 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 0378abf102d 116: onsuccess: #647: 1: Success after linux: 3 commits discards 082a9e2e5b2 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 2fd5054a11f 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 2aa7b6f23f9 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards fc047f66f0a 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards fb2fc6ee161 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards e7495153e29 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards f5b6b5ef622 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 16ff580e8d7 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards aa12cdffe5d 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards a0d9e56bcad 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 31e199b5c4a 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new d35d011d546 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 853c65f9952 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 90113ed583f 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 78b1a31fa6e 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 308cdc0ab0e 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new c1112999e83 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 1a3e156f37b 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 30680226388 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new bd5b82ed3af 115: onsuccess: #645: 1: Success after binutils: 27 commits new b44eea2d65b 116: onsuccess: #647: 1: Success after linux: 3 commits new f3d1bd78689 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 6999375d9b9 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new fa3d518873c 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new ffeec69d8be 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 043af4275a8 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 935a0db1e30 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 23b5fd0f983 123: onsuccess: #655: 1: Success after binutils: 22 commits new b2607178f52 124: onsuccess: #657: 1: Success after glibc: 2 commits new 633bfb81836 125: onsuccess: #658: 1: Success after linux: 3224 commits new b0c449207cf 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 3bb527dabac 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new edfe3b2f1f5 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new ee57d58b333 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 4634992d4e2 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new a6683d53d90 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new b59e74b0e82 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 9048c328eac 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 0c336812b6c 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 3f5a39f67e6 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 483d7290a3a 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 87600297d66 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new 9efda7da527 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 3a19bf86822 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new a70a7e5b8d3 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new e7ed53c0631 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new 480c757b765 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new b5e6fb24ac5 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new ad6a89d50b5 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new b7e270d1465 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new 3b8e5119221 146: onsuccess: #680: 1: Success after binutils: 20 commits new 08be507fbdb 147: onsuccess: #681: 1: Success after gcc: 6 commits new 1882cd84ac9 148: onsuccess: #683: 1: Success after glibc: 9 commits new 851f0654447 149: onsuccess: #684: 1: Success after linux: 10 commits new 321753a6bbb 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new 4996308895a 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new ac9401aedd3 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new a9e17486551 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 678f154f8b5 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new 7f5301d1e21 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new da2f9b1c8e4 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new 6a6887cbcab 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new 49047d8d493 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new d8c06223758 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 3b65f03dfcc 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 8122cd047c2 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new 091a565963b 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new a2f61fdc9f1 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new e3c5804b85a 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new e4a3ba4e07b 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new f937d41f4b4 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new 4be6e223384 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new d9935f4f281 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new e46d2397497 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new f282cb92073 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new a9af9a10957 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new c518ebc32ad 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new 5c75cd2833e 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new 13a45721489 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new 0f628e37c07 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new e7e53121eac 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new d67eb53d48c 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new a93c0412159 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 47b836e454f 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new 26bd381e44e 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 446cb4a9170 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new 7c455328ead 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new 603d022fb35 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new b67a6c62d58 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 09d1e8850ab 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 93478f4cbf0 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new 8d53324202c 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new 209c967fb3c 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new 4cac053f674 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 2e0a44ea326 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new b72675f69e0 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 0a1dbb64ffa 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 5d510f55c45 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 9d6abc13914 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 1ecf64dc557 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new f527aa9bd37 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 736b5e11289 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 2e9def60a69 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 4401043f144 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new a92d0474ec5 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new b323b635bae 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 59e3dd0eee1 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new a5370248c64 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new f80a0a0eb48 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 9016603c17a 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 209a736c382 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new f04a1b2242b 207: onsuccess: #17: 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 (5b69c500cb5) \ 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 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 38720 -> 38760 bytes 04-build_abe-gcc/console.log.xz | Bin 203584 -> 203688 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9096 -> 8784 bytes 07-build_abe-glibc/console.log.xz | Bin 244148 -> 244508 bytes 08-build_abe-gdb/console.log.xz | Bin 38472 -> 38460 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3756 -> 3756 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2016 -> 2036 bytes 11-check_regression/console.log.xz | Bin 6432 -> 5852 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 36 +-- 12-update_baseline/console.log | 36 +-- 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 | 32 +-- sumfiles/binutils.log.xz | Bin 62952 -> 63032 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83968 -> 83964 bytes sumfiles/gas.sum | 274 +++++++++++------------ sumfiles/ld.log.xz | Bin 122252 -> 122248 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 29 files changed, 392 insertions(+), 416 deletions(-)