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 abf948c894f 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 3c61e67be94 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 892dccfadcf 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 17298b18f40 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 87022a1fc48 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 33d2591dfad 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards a27cc4b206e 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 60309cf0a8e 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards ed31b49cbfc 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards a7defef1940 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards d1e68ffc15a 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 2eb7d3041f5 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 504cb77176e 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 7bf8b9cff59 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards e2d17f370c5 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards f94bca527cc 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards e7dfc4de2d5 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards ac55b21fccf 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards 97c81f6b05a 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 0dfdb4d2316 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards f0e1e10b0b4 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards 8e0644a077d 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 01d747247ea 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards 93fe62dd914 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards a238d839b50 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 3b7017b2c86 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards 7e44e49aee5 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards e7c14f9b49c 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 5a83640438a 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards 1c99dddec63 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards a06f6e25174 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards d8c5dce4795 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards 662568d55d2 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards 7bd5e585a13 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 2c2f3b9d6f4 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 5803bf513a7 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 4a6d5abafd3 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards 7978d3d93e8 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards 2bf4699ff6c 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards 81c5dc5d4f0 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 1cf54dadca5 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards dbf4a1be1b6 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards ef526c86dbf 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards c0165151958 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards c7e53d80de1 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 36b95c8961e 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 0dd4cd363c7 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards fb0440baf10 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards 178aaa94d0c 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards e7d1642c580 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards a664c60465a 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards dd00cfca9c3 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards d952e8ca9cc 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards c42e76ebff5 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards a03d59b0a42 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards 50513f54436 149: onsuccess: #684: 1: Success after linux: 10 commits discards 5adbd5f7f4d 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 2aa0f2988e8 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 5c16fdad601 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 9a4928d8e0d 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards cc6d7abdcc3 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 6137df244cb 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 2b510ab92b0 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 4a53e0580b8 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards 6751bc02ea6 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards 4bd6a7b6845 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards e57675b8615 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 7acca9b5209 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards 14b8fba74e9 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 06890226e22 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 49f38d21f8b 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards 407cfd47b11 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 710f8262706 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 1512b42fd42 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards d6bbced1a9b 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 5d0bd7a5f01 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards ac87eac5624 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 4c083754cdd 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards c3f6f9caac2 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards b8a0fdde606 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 66b3d573de5 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 252f297011a 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 0d75dad3c1e 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards ae50add537b 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards bc2e7ff5ef3 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 9c9135bce95 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards d759a126691 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards ee66f25d453 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 1c86f13d94c 116: onsuccess: #647: 1: Success after linux: 3 commits discards 4bac3e86630 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 99925446cba 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards c60c111b112 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards f34b4edf06c 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 53efac6de24 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 97a6f3fc002 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards e33974301c3 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 8131e55b794 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 25684c03f0c 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 931226ae88b 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards a0f66d8cdcd 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 29203bc4c90 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new a1c32a8c2fe 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 40f393f30d5 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 89921026e9e 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 1efa0a1db33 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 561801ed2e5 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new b69fbf636da 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 49e8171bce0 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 5575e6bade9 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 13813d6fb6d 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new e95db3ef702 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 14f238daf14 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new b5703ed9a42 115: onsuccess: #645: 1: Success after binutils: 27 commits new 262b509c139 116: onsuccess: #647: 1: Success after linux: 3 commits new 9fb1e4585e1 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new d58ce9edc57 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new d4ecd5936d3 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 82f86a04128 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 6ca52bce49d 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 3513127e63b 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new b238c59d254 123: onsuccess: #655: 1: Success after binutils: 22 commits new d226033fc20 124: onsuccess: #657: 1: Success after glibc: 2 commits new 34b2b3be3e9 125: onsuccess: #658: 1: Success after linux: 3224 commits new f26cf0a0355 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new dacb616c6b5 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new dab4941ac3b 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 6f2f191a319 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 3c5b6825ec2 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 8f9a2409114 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new f1167e9f72a 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new eeb21eca348 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 2e5296e054a 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 4709fbca387 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 34c326a06f5 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 878954341b0 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new 5ed85d38e18 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 54fa95742c4 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new 3c090746c77 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new 8d28dd84379 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new 1f9114014b5 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new e8d5cc8982b 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 94780a99c92 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 530c1531224 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new 7bd5d2778dc 146: onsuccess: #680: 1: Success after binutils: 20 commits new 970fcffe55b 147: onsuccess: #681: 1: Success after gcc: 6 commits new ee644eaf7a8 148: onsuccess: #683: 1: Success after glibc: 9 commits new 1b594616527 149: onsuccess: #684: 1: Success after linux: 10 commits new 835c0793cf1 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new 32f27e3f862 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 90cc732db38 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new 8f7f16f0ba4 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 9106f7504b6 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new 822d92da614 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new f93a9c93665 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new d5e043b843e 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new 5cab3de0194 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new ddc8e0fb657 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 0b5d18ed364 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 17c6b62a1ad 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new 4689bac0341 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new 181d4aaf563 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new 9498e1c95b8 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new 470b072e38b 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new a25f48ada59 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new d96ca741c86 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 7eb979c2825 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new cf8e033c481 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 48410f3630c 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new a56b16ec024 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new 2a968f05f8e 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new ffab036d186 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new ad2d716706b 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new 09ae5dac579 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 832c0ea576a 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new 7c52039ca36 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new 9bc03e7b776 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 11bc6534d85 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new 00538317498 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 522d4d82888 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new 5d1c4764aa7 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new 6f317fcd439 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new c19d3fe0c6f 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new a2b94344afe 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 88e3b2ad9bc 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new 6e05b57aba2 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new 45236acc77c 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new 6328b83cfdc 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new dce079ea734 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 450295f2f60 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 9e2b3bc4208 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new ef8f8f0b91b 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new aeab6fcad92 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 66e85e42b45 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 6958afc6c2f 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 2745a5e77c3 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new a0cb4952609 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 46e2fd037c2 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new f36df9409ea 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new bf334100a4b 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 1317d5bec69 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new dd87fa11aea 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 51f00d82292 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 0d0c8d039bf 205: onsuccess: #15: 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 (abf948c894f) \ 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 2764 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 38940 -> 39048 bytes 04-build_abe-gcc/console.log.xz | Bin 203116 -> 203548 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8520 -> 9584 bytes 07-build_abe-glibc/console.log.xz | Bin 243972 -> 244244 bytes 08-build_abe-gdb/console.log.xz | Bin 38704 -> 38632 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3760 -> 3752 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2284 -> 2260 bytes 11-check_regression/console.log.xz | Bin 6076 -> 5844 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 38 ++-- 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 | 34 +-- sumfiles/binutils.log.xz | Bin 62984 -> 63016 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83972 -> 83988 bytes sumfiles/gas.sum | 274 +++++++++++------------ sumfiles/ld.log.xz | Bin 123620 -> 123608 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 29 files changed, 391 insertions(+), 391 deletions(-)