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 0d0c8d039bf 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 51f00d82292 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards dd87fa11aea 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 1317d5bec69 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards bf334100a4b 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards f36df9409ea 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 46e2fd037c2 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards a0cb4952609 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 2745a5e77c3 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 6958afc6c2f 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 66e85e42b45 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards aeab6fcad92 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards ef8f8f0b91b 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 9e2b3bc4208 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 450295f2f60 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards dce079ea734 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards 6328b83cfdc 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards 45236acc77c 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards 6e05b57aba2 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards 88e3b2ad9bc 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards a2b94344afe 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards c19d3fe0c6f 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards 6f317fcd439 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 5d1c4764aa7 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards 522d4d82888 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards 00538317498 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 11bc6534d85 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards 9bc03e7b776 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards 7c52039ca36 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 832c0ea576a 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards 09ae5dac579 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards ad2d716706b 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards ffab036d186 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards 2a968f05f8e 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards a56b16ec024 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 48410f3630c 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards cf8e033c481 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 7eb979c2825 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards d96ca741c86 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards a25f48ada59 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards 470b072e38b 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 9498e1c95b8 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards 181d4aaf563 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards 4689bac0341 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 17c6b62a1ad 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards 0b5d18ed364 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards ddc8e0fb657 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 5cab3de0194 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards d5e043b843e 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards f93a9c93665 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards 822d92da614 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 9106f7504b6 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards 8f7f16f0ba4 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 90cc732db38 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards 32f27e3f862 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 835c0793cf1 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards 1b594616527 149: onsuccess: #684: 1: Success after linux: 10 commits discards ee644eaf7a8 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 970fcffe55b 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 7bd5d2778dc 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 530c1531224 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards 94780a99c92 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards e8d5cc8982b 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 1f9114014b5 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 8d28dd84379 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards 3c090746c77 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards 54fa95742c4 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards 5ed85d38e18 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 878954341b0 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards 34c326a06f5 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 4709fbca387 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 2e5296e054a 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards eeb21eca348 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards f1167e9f72a 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 8f9a2409114 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 3c5b6825ec2 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 6f2f191a319 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards dab4941ac3b 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards dacb616c6b5 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards f26cf0a0355 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 34b2b3be3e9 125: onsuccess: #658: 1: Success after linux: 3224 commits discards d226033fc20 124: onsuccess: #657: 1: Success after glibc: 2 commits discards b238c59d254 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 3513127e63b 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 6ca52bce49d 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 82f86a04128 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards d4ecd5936d3 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards d58ce9edc57 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 9fb1e4585e1 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 262b509c139 116: onsuccess: #647: 1: Success after linux: 3 commits discards b5703ed9a42 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 14f238daf14 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards e95db3ef702 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 13813d6fb6d 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 5575e6bade9 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 49e8171bce0 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards b69fbf636da 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 561801ed2e5 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 1efa0a1db33 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 89921026e9e 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 40f393f30d5 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 0fa1c74fd5c 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new a0d9e56bcad 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new aa12cdffe5d 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 16ff580e8d7 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new f5b6b5ef622 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new e7495153e29 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new fb2fc6ee161 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new fc047f66f0a 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 2aa7b6f23f9 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 2fd5054a11f 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 082a9e2e5b2 115: onsuccess: #645: 1: Success after binutils: 27 commits new 0378abf102d 116: onsuccess: #647: 1: Success after linux: 3 commits new 703e1547bca 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new d3f983d6a3c 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 63f8dc9e382 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 9277b05f59c 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new e9d985cdd68 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new f193201c375 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 6da7d83aace 123: onsuccess: #655: 1: Success after binutils: 22 commits new c4bfca49f65 124: onsuccess: #657: 1: Success after glibc: 2 commits new a7bb50eaecc 125: onsuccess: #658: 1: Success after linux: 3224 commits new a1614f86747 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 4b397374d80 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 4d9c6501f80 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new c7ec38cb15c 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 43b27d3701a 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new c584ef3f067 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new ec403b82ecf 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 3e585e17fde 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 7690e87abf4 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 8cb925d5502 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new c5624eeafcf 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 4c249b9403c 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new a03ecb52b0e 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new b74a22cace6 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new 3d21a0d904b 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new a1ad4f1c459 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new f0bc1105833 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 098ce181f94 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 5bb732d19ea 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 66a81c5a71d 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new bc8db45d33f 146: onsuccess: #680: 1: Success after binutils: 20 commits new c1cfb5ade8e 147: onsuccess: #681: 1: Success after gcc: 6 commits new 9251f829645 148: onsuccess: #683: 1: Success after glibc: 9 commits new 0bbdde0a29e 149: onsuccess: #684: 1: Success after linux: 10 commits new 4f7612e82f5 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new f6e7c223ff7 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 9da33fc6702 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new d4a37a1f09a 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new a6e865f526e 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new 7299aa4b8d3 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new 18b64e91d52 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new ec49a2b097e 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new 8ee642a6eea 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 043618db85a 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 3b2430b9954 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 2a290e0bee6 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new 2ecbbcd29a8 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new 966155896a3 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new 5abad737b43 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new e717bf9154e 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new e9d1c5ae1be 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new e7c232fcc10 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 70cefc7652f 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 8e59130e2b1 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 055a513cd68 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new b1dd5204ab8 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new 76b0f2f82a0 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new 77c4c774088 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new 536e1823d45 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new d687ea16f1c 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 72ff3af0f84 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new b6f7ca61514 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new 9ccdec260ad 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new bbb60640771 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new e71c7e88829 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 8373fd76670 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new 7dd7ea12454 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new db66e648757 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new 50f42d1ec1d 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 49823996089 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 7c7f40aa438 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new 3553ae9bbf9 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new ac89c73da00 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new c335ba99dc0 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new cd3e60656ef 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new f3c2268c2d5 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new a343ce70b17 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 630ab794bff 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 654df6d6235 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new c8d1ab33f9b 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 2ac88893d18 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 3393f4d0925 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 7b92ab16ac7 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 4ce772e19ec 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 40267386a04 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new a7a22e4c05d 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 7cf55c19455 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 562a635e73e 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 66998c5f584 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new d29c3174649 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 5b69c500cb5 206: onsuccess: #16: 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 (0d0c8d039bf) \ 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 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 39048 -> 38720 bytes 04-build_abe-gcc/console.log.xz | Bin 203548 -> 203584 bytes 06-build_abe-linux/console.log.xz | Bin 9584 -> 9096 bytes 07-build_abe-glibc/console.log.xz | Bin 244244 -> 244148 bytes 08-build_abe-gdb/console.log.xz | Bin 38632 -> 38472 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3752 -> 3756 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2260 -> 2016 bytes 11-check_regression/console.log.xz | Bin 5844 -> 6432 bytes 11-check_regression/results.compare2 | 34 ++++++++++++++++++++++---- 12-update_baseline/console.log | 38 ++++++++++++++--------------- 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 | 36 +++++++++++++-------------- sumfiles/binutils.log.xz | Bin 63016 -> 62952 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83988 -> 83968 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 123608 -> 122252 bytes sumfiles/ld.sum | 23 +++-------------- 28 files changed, 81 insertions(+), 74 deletions(-)