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 7b255f7e49 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards c04868c68c 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 0301592aac 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 50a86bf897 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards a55a38df90 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 2004039a15 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards a8ba507bc8 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 6a9fe2d06c 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards e36dad6d2b 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 36c43a09e3 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards ab61398480 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 529e9efb58 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards c315a88445 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 6a9d9b26d0 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 8d06c30eca 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 3ca8ddd844 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 641ad2237f 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards f6ca78e8bb 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards aeb6f4fcd2 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards e8f2825433 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 7ee7a55fb9 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 07aacaa227 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards dc44d03275 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards a3deecde31 214: onsuccess: #26: 1: Success after binutils: 12 commits discards fc04355cf5 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards 4b34f7f971 212: force: #24: 1: Success after binutils: 2 commits discards 8d8a1d7a28 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 83c9fdffab 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards bef5fc07c1 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards f0667b322f 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards c5a6650567 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards b25cd886d4 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 2b10d4ab7f 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 96f9f116aa 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 51d28e781a 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards ec3c3df5ac 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 3eb9d01a68 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards a89264eebd 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 1ee8d9b4a5 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 6c5c7e219c 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards bcc2d6e981 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 7fd56c999b 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 9ddd511398 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 69c000f9b8 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 293adaf642 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 18437ddf22 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 2dbd87e9b3 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards dbe46556ca 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] discards e5edfff3c5 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] discards 4c2496fc4f 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] discards 420e50a5ba 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] discards 75b65b402f 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] discards 795e95c6e3 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] discards e5a70c8cc1 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] discards 4588b31493 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits discards fc26bd237a 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] discards 8e13ea9c37 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] discards f934b24eed 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] discards d007227315 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] discards 59a7bbeb18 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] discards 4c307114c8 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] discards b280853fc4 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] discards 1b791059d5 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] discards 46bf4abded 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] discards 43e4240afd 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] discards d1b225bc3c 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] discards 6133710ec6 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] discards 27de1f7264 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] discards 3d55ef9487 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] discards 653baa1696 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] discards 7b3b3a3583 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] discards 1297e55ac9 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] discards dd1a30cea1 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] discards 0dfe255d41 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] discards 7d927e6c47 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] discards 27a8786428 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] discards e3130af25d 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] discards 265919ca78 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards 3ea0de44bb 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards d692de8eb1 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards 147df9c1e1 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards 400f27cc2b 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards 00e9e153fb 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards 98e83ce646 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards 9b1cecda75 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards fd73865c90 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards f7d89a6181 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] discards 60be757728 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] discards bc1d4a3224 149: onsuccess: #684: 1: Success after linux: 10 commits discards f24b26e492 148: onsuccess: #683: 1: Success after glibc: 9 commits discards d3b3d55c8e 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 8167447ede 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 905b6d7ac0 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards 6042daa425 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards 3c9d8ba120 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards 87270439b4 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 24f2ee4a8a 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards ca86dca35e 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards fe014d3a5d 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits discards be1f12251c 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards 07563da0c1 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new e078c1fa16 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new 269ecb41c4 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new 473fa7a18c 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new b7689a5a8f 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new dd7a61f698 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new 2274f90981 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 4110bdaea3 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new 628ed674b3 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new 66a0e93b77 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new eb8581fdcd 146: onsuccess: #680: 1: Success after binutils: 20 commits new 3ab3f1030b 147: onsuccess: #681: 1: Success after gcc: 6 commits new a5e26a5c3b 148: onsuccess: #683: 1: Success after glibc: 9 commits new 24c2a0f1fe 149: onsuccess: #684: 1: Success after linux: 10 commits new 89807a0918 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] new ded6d7bdb8 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new 9d78542b4c 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new 6a220f59c2 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new b1b6b96e52 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new 2adea9569a 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new 6dd7f77d06 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new aa9548655b 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new 0f7082ca18 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new ecf3a365d4 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new 5f8ab177a9 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new 25b201dbb7 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] new 5f8428bafa 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] new f3776cac88 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] new 133ef91e53 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] new a002e81d64 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] new aa514a2ac7 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] new 8a4a6bcbfd 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] new 11a493e1de 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] new b12219e948 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] new afd08caa07 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] new 291380c3ba 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] new eb59c8c5c2 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] new 4cd4b4528f 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] new 3ee8fc0167 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] new 917b878635 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] new 721ce62f49 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] new 818db47945 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] new 6338a3caef 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] new b2794b914c 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] new 2c019ebe14 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] new af18931f1e 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] new e3e8700102 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] new eeccf744ea 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits new 83fe7883f4 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] new c2081ecd33 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] new 74878d05d8 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] new 64c4394a7a 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] new 58242b6369 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] new 4e9fbbd593 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] new 53fb198ab9 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] new 8f54b138a2 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new bfcf25f2a2 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new f324dd4bc0 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 4dab8cde34 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new b1edfa63a5 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 7945d16315 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new acdba97a20 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 05bcdd6b5f 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 8bf36a90f0 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 1bc2e45792 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 38b3c8d9c0 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 7b952122a1 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new c43691aeb0 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 3fb31344ce 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 920c0f2832 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 0581798fc8 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new cf9f3520cd 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 2846b8c7dd 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 8b191ab1d7 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new e44e1f0031 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new c6ffb36079 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 69aa214247 212: force: #24: 1: Success after binutils: 2 commits new d74f8af8df 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new ccb716707c 214: onsuccess: #26: 1: Success after binutils: 12 commits new cf83afac92 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 7d108f8890 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 64aac079a1 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 3fca9304c0 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new dccd08e1ae 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 7d4a38a6e3 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new e63ac78405 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 40ec49ecb6 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new d23ae55eeb 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 2d3a40caa5 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new b6b05b460f 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new c2a7658ee8 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new f3f6b0f04a 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 0a2f5ec9a4 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 7db112eccc 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new a213393dbb 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 236e1fab14 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new d29fa24ff9 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 105c9b291a 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 4290c2a278 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new af44b296e3 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 81a9ba9aec 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new df423d537a 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 01a90bdfe8 238: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...]
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 (7b255f7e49) \ 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 2020 -> 2048 bytes 02-prepare_abe/console.log.xz | Bin 2584 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 35052 -> 35076 bytes 04-build_abe-gcc/console.log.xz | Bin 203304 -> 203764 bytes 06-build_abe-linux/console.log.xz | Bin 8588 -> 8788 bytes 07-build_abe-glibc/console.log.xz | Bin 240716 -> 240980 bytes 08-build_abe-gdb/console.log.xz | Bin 34652 -> 34656 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3856 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2180 -> 2156 bytes 11-check_regression/console.log.xz | Bin 1320 -> 1320 bytes 11-check_regression/results.compare | 4 +-- 11-check_regression/results.compare2 | 4 +-- 12-update_baseline/console.log | 42 ++++++++++++++--------------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 4 +-- manifest.sh | 32 +++++++++++----------- sumfiles/binutils.log.xz | Bin 63144 -> 62676 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150608 -> 150684 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122620 -> 122584 bytes sumfiles/ld.sum | 4 +-- 27 files changed, 54 insertions(+), 54 deletions(-)