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 f3f2f3aa379 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards 79767a1a156 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards b8bc2ec1fe6 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards 616f3b736dd 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards 78bd8f9baea 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards a8eafbe23a8 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards f568e0f77e6 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 403a5256e42 214: onsuccess: #26: 1: Success after binutils: 12 commits discards f731721f66b 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards 20e68eb1065 212: force: #24: 1: Success after binutils: 2 commits discards 333622c042d 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 1174e76d353 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 955fec501ea 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 51618eff352 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 7fe2a5bd673 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 4927e758c81 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards cc1c48ae204 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 4f68489e8a9 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 4902316cb77 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 2be42943967 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards aac064cef3f 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards f4c10a4a35b 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 9f43c597711 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards a0533196bc2 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 06dc79ae0d0 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards d4122b9acde 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards d454169b0c5 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 86f49ac66a9 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards ed612d36ead 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards cd255cb9940 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 9c47b02b1fc 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 4a0d9388480 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards beeae4dc6a8 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards 17df9834517 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards 139aa136c56 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards d497cfd35c5 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 1977dd85627 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards 9c8c58e5c1a 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards d9d46f5ac9d 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 82ae35fc7d0 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards 81edb8fa092 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards 6a106e5236a 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 81662f34b02 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards d8af7096426 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards 51ff81e9409 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 3d2632b0c96 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards 56d5e41abb8 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards faf846c3992 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards 8ada91956c6 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards 019da3f76ef 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards c6743c61c1c 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 1c829ae9551 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 966888d63ab 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 11031e54b2b 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards 12488e8cf7f 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards 14d1beb814a 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards a26e98daee9 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 23f91382922 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards cf498eac1ac 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards c99d0cb7944 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards e3588dcaef9 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards 09e1cc55758 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards ee9aea17bfd 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 7c730c8741a 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards e0c48bdafb3 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards 92c6133735f 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards 94051a25f15 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards b7ca4b8236e 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards fa91920a935 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 331ed43525b 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards d0798f19a1d 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 409b671a1ea 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards 11727ba1560 149: onsuccess: #684: 1: Success after linux: 10 commits discards 49e993a5945 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 897a35ce4e5 147: onsuccess: #681: 1: Success after gcc: 6 commits discards a1e5af08920 146: onsuccess: #680: 1: Success after binutils: 20 commits discards cae94b84d41 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards b27db1acfd4 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards d69278851b6 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 3cbcd12be02 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 49eda5e29da 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards f4b4212efc1 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards 2d9d92fc21b 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards 443cf80686f 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 3ff2bae9933 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards 7f58674c332 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 59da88b1803 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 732c2ff61f8 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards 74c2de29dcf 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 07b01434c14 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 696e4b9d601 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards ad615d1da46 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 56189f5da52 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 879ec17e65b 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards ec3d80e4449 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 4d1e8c5a43a 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 537a2817e3b 125: onsuccess: #658: 1: Success after linux: 3224 commits discards cb5b967bc7b 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 70ae864e477 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 5d7e343d90c 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards c60d424776b 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 4bcfbc7490b 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 749744e782f 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new cd746593ff3 123: onsuccess: #655: 1: Success after binutils: 22 commits new 6a121413d41 124: onsuccess: #657: 1: Success after glibc: 2 commits new 6e6461ae5a3 125: onsuccess: #658: 1: Success after linux: 3224 commits new 142ed6aa719 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new fe33cb079bf 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 380f1edf3c7 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new d9633133adf 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new a16fab2f27c 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 12f7acf0b07 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new d35dd9cf5eb 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 5e057514811 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new a8ed71f32d1 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 1e40cf196d9 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new eef4406ea24 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 503e4edf1a8 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new 498a0890f50 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new ba3c5111e24 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new 1097d04a990 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new e398205ff04 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new 9ad2636230d 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new ccd9aa5116e 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 408b04c4b14 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 068a9962d53 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new ed9c5787dd3 146: onsuccess: #680: 1: Success after binutils: 20 commits new 14d06284f09 147: onsuccess: #681: 1: Success after gcc: 6 commits new 8ef70b66b87 148: onsuccess: #683: 1: Success after glibc: 9 commits new b0a803452bf 149: onsuccess: #684: 1: Success after linux: 10 commits new 4967a1340e2 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new 953c9cef35f 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 23b40fd7d60 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new 5f10df012cd 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 829666b1eab 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new 68bfcbd83e2 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new b6ea428944e 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new ba80d7ce826 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new 4a534108718 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 93e44f75aac 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new b4ff12e437c 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new d2658339427 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new 5a647edfb99 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new 2b1a1c5b95f 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new 703db0a225c 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new db51176a767 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new fa874254d15 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new b7fbe7ed605 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new eb1afa15712 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 868c5f89558 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 1600b5e132a 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new 82354a06b96 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new 0a9c50af9af 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new 8e4552d04cd 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new d77b6a13946 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new 413824e18c2 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 65f110ea78a 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new cfde8d602f1 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new 01af38a1e0b 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 9069a90e939 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new 292f6b54cd5 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 2f6a6a47565 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new f0113369d4b 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new 91ef39f2cfd 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new 9e9d3e95bf1 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 6d8917ee7b9 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 5019fdd3236 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new cdbf2af681c 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new 5bffdff4c35 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new cfaa043e637 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 2a9ec992007 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 28011f6e09a 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 1c8189e8d1c 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 9fb102550c8 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 5b3f9903fe8 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 8bc8ea72280 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new ce0552ca16d 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new c0faf349706 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new df3dcba355a 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 1cd2730d504 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 4b2c9e19509 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 67dd291584c 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new ea9dede1e7f 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 039c9a078ca 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 192a8d2a0c0 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new c823353a2bc 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new b288ed9ea8f 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new a038ffc12f1 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new bb80c5dfd3b 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 713dfe7f517 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new effc8ec0f75 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 2ba09d4a881 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new c40ca0c2b55 212: force: #24: 1: Success after binutils: 2 commits new b62f293f2a0 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 54ab6c39a5e 214: onsuccess: #26: 1: Success after binutils: 12 commits new b523b7d335e 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new faa6293b5d1 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 996c32068ba 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 98bceb5a0e1 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new 6dc20ccc631 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new edf6aa9a1e3 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new 0d94d8e6a2a 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new 3da4adcab52 222: onsuccess: #36: 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 (f3f2f3aa379) \ 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 2048 -> 2028 bytes 02-prepare_abe/console.log.xz | Bin 2572 -> 2528 bytes 03-build_abe-binutils/console.log.xz | Bin 34892 -> 35136 bytes 04-build_abe-gcc/console.log.xz | Bin 203564 -> 203396 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8872 -> 8392 bytes 07-build_abe-glibc/console.log.xz | Bin 241428 -> 241460 bytes 08-build_abe-gdb/console.log.xz | Bin 34396 -> 34636 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3796 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2092 -> 2120 bytes 11-check_regression/console.log.xz | Bin 4908 -> 4196 bytes 11-check_regression/results.compare | 10 ++++---- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 40 ++++++++++++++--------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 ++++++++++++------------ sumfiles/binutils.log.xz | Bin 62936 -> 62984 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 84000 -> 83964 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122584 -> 122620 bytes sumfiles/ld.sum | 4 +-- 28 files changed, 57 insertions(+), 57 deletions(-)