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 3da4adcab52 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] discards 0d94d8e6a2a 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards edf6aa9a1e3 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards 6dc20ccc631 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards 98bceb5a0e1 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards 996c32068ba 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards faa6293b5d1 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards b523b7d335e 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 54ab6c39a5e 214: onsuccess: #26: 1: Success after binutils: 12 commits discards b62f293f2a0 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards c40ca0c2b55 212: force: #24: 1: Success after binutils: 2 commits discards 2ba09d4a881 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards effc8ec0f75 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 713dfe7f517 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards bb80c5dfd3b 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards a038ffc12f1 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards b288ed9ea8f 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards c823353a2bc 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 192a8d2a0c0 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 039c9a078ca 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards ea9dede1e7f 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 67dd291584c 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 4b2c9e19509 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 1cd2730d504 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards df3dcba355a 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards c0faf349706 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards ce0552ca16d 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 8bc8ea72280 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 5b3f9903fe8 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 9fb102550c8 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 1c8189e8d1c 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 28011f6e09a 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 2a9ec992007 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards cfaa043e637 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards 5bffdff4c35 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards cdbf2af681c 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards 5019fdd3236 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 6d8917ee7b9 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards 9e9d3e95bf1 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards 91ef39f2cfd 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards f0113369d4b 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards 2f6a6a47565 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards 292f6b54cd5 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 9069a90e939 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards 01af38a1e0b 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards cfde8d602f1 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 65f110ea78a 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards 413824e18c2 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards d77b6a13946 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards 8e4552d04cd 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards 0a9c50af9af 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards 82354a06b96 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 1600b5e132a 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 868c5f89558 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards eb1afa15712 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards b7fbe7ed605 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards fa874254d15 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards db51176a767 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 703db0a225c 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards 2b1a1c5b95f 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards 5a647edfb99 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards d2658339427 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards b4ff12e437c 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 93e44f75aac 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 4a534108718 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards ba80d7ce826 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards b6ea428944e 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards 68bfcbd83e2 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 829666b1eab 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards 5f10df012cd 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 23b40fd7d60 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards 953c9cef35f 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 4967a1340e2 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards b0a803452bf 149: onsuccess: #684: 1: Success after linux: 10 commits discards 8ef70b66b87 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 14d06284f09 147: onsuccess: #681: 1: Success after gcc: 6 commits discards ed9c5787dd3 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 068a9962d53 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards 408b04c4b14 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards ccd9aa5116e 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 9ad2636230d 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards e398205ff04 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards 1097d04a990 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards ba3c5111e24 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards 498a0890f50 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 503e4edf1a8 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards eef4406ea24 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 1e40cf196d9 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards a8ed71f32d1 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards 5e057514811 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards d35dd9cf5eb 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 12f7acf0b07 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards a16fab2f27c 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards d9633133adf 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 380f1edf3c7 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards fe33cb079bf 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 142ed6aa719 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 6e6461ae5a3 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 6a121413d41 124: onsuccess: #657: 1: Success after glibc: 2 commits discards cd746593ff3 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 749744e782f 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 41200a18ea9 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 6d3176f3529 123: onsuccess: #655: 1: Success after binutils: 22 commits new 012f04484f2 124: onsuccess: #657: 1: Success after glibc: 2 commits new e8958a158f3 125: onsuccess: #658: 1: Success after linux: 3224 commits new 77f8c93bca8 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 5103aac4762 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new af0afc3a923 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 88fe92377a2 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new f809971da8b 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 9a968397ac2 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 57f9fdefbc6 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new a64e9229bb4 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 8dfd6941b91 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 8fe1cecab12 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new bbd6f983210 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new ac00e08ac24 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new c6fece24a39 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new b48a62a4a49 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new f36cb89854e 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new 82cb7a7b07f 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new 0d7f80c24b5 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new ae76367e7e0 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new ba72ee4ab56 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 99131fb743a 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new b85aa9ae533 146: onsuccess: #680: 1: Success after binutils: 20 commits new 37fec3247e4 147: onsuccess: #681: 1: Success after gcc: 6 commits new 2e3bce7cb59 148: onsuccess: #683: 1: Success after glibc: 9 commits new 448c33bf86a 149: onsuccess: #684: 1: Success after linux: 10 commits new f965faf0a08 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new ed0fdac1060 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 8c53cbce87e 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new 2b49191a597 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 88ea2c06d92 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new 3bc14dcd2d0 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new 0d85970c317 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new 7e4f8ca32ab 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new 480b53d72f6 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new b8982d4383b 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 06f296da415 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 78d6e662173 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new aa12660ad3a 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new da7bcea9077 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new 287484b2b2b 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new e399ecf923f 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new abc8e16f3cb 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new 679746e5ada 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 3552abd186d 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new eeab0c63239 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 07f08687078 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new 229b01a5574 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new 2e4f7c33b2e 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new d10238118f9 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new 034da0f0d44 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new 8a5c0ed037e 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new a427eb9b4a3 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new fbb804ddebc 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new 93b59f7c805 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 3b74d79165c 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new d3a326e27c1 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new d7017e02bbf 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new 6b2141a28a1 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new 4571d83ddfe 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new 80010a483be 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 676b0d6795d 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 8712b2199fc 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new 4e614fc3673 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new 84e372afb59 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new 83ed7efd5f3 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 6cac9e2e195 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 8ad222a486b 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new a57c9dc05e2 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 6cc9e169b54 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 4c1502dfa5c 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 3f63d5fa1f4 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 5986e8808bb 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new f9b7609bfd4 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 2147a03bf81 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new be9deb8db24 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new a03a696582a 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new fb21f90a38d 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 38861d54f9c 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 7b1496a4d76 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 4f32b01b49f 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 335e7d66686 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 351cddc0cf2 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new bf970344ce7 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new bd72f356a50 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new b37fdaf4fcf 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 8a25f8aafc1 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new fb9cfd6c773 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 219adbc1269 212: force: #24: 1: Success after binutils: 2 commits new 2e430e4242f 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new f8a4c1787e9 214: onsuccess: #26: 1: Success after binutils: 12 commits new d0f8fdf958a 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new c8041bd69a9 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 2f8286e05f1 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new f165cd513e6 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new 367a8bcba5c 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new 9eef6655014 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new cc9edfcee58 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new dad2d1dff07 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] new ac407681e3d 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gc [...]
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 (3da4adcab52) \ 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 2028 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2528 -> 2524 bytes 03-build_abe-binutils/console.log.xz | Bin 35136 -> 35128 bytes 04-build_abe-gcc/console.log.xz | Bin 203396 -> 202888 bytes 06-build_abe-linux/console.log.xz | Bin 8392 -> 8508 bytes 07-build_abe-glibc/console.log.xz | Bin 241460 -> 241600 bytes 08-build_abe-gdb/console.log.xz | Bin 34636 -> 34512 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3796 -> 3800 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2120 -> 2184 bytes 11-check_regression/console.log.xz | Bin 4196 -> 5232 bytes 11-check_regression/mail-body.txt | 35 ------------------------- 11-check_regression/mail-subject.txt | 1 - 11-check_regression/results.compare | 4 +-- 11-check_regression/results.compare2 | 4 +-- 12-update_baseline/console.log | 40 ++++++++++++++--------------- 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/changes-list-long.txt | 32 +++++++++++++++++++++++ mail/changes-list-short.txt | 1 + mail/mail-body.txt | 35 ------------------------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 38 +++++++++++++-------------- sumfiles/binutils.log.xz | Bin 62984 -> 63100 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83964 -> 83976 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122620 -> 122508 bytes sumfiles/ld.sum | 4 +-- 33 files changed, 88 insertions(+), 126 deletions(-) delete mode 100644 11-check_regression/mail-body.txt delete mode 100644 11-check_regression/mail-subject.txt create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt