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 494c02f2a4 252: force: #89: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 5ca94b8b24 251: force: #87: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 7fd718601d 250: force: #85: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 5691ef1529 249: force: #83: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 372e01a149 248: force: #81: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 3fde5e3616 247: force: #79: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards f036eb7065 246: force: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards cbc8ec45a2 245: force: #75: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 34ff0fe760 244: force: #73: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards baac532242 243: force: #71: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 107266cc0f 242: force: #69: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards b53bd0f955 241: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards fa5fb0417e 240: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 2fdc4c8f52 239: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 1f9944748d 238: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards d8e6cc218e 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards c7c7ad4205 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 0d4e2eba9f 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 3a81e36eda 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards db661fc3b9 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards d30d4d5bc0 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 8cc54bfc71 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards c813297d66 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 5cf3995c0f 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 670bd130a8 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards c7fd2b6dce 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 54b59ee51a 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 1160f582a3 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 9f1960825e 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 8958ed3227 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards cdf6a47217 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 2f8fb317c2 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 193e21bf57 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards e80e750c5f 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 5976d7b94e 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 9251ea0b45 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards f7a699b508 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 559b471695 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 6715f5ad62 214: onsuccess: #26: 1: Success after binutils: 12 commits discards e1798985ff 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards 5b7f1a7519 212: force: #24: 1: Success after binutils: 2 commits discards 1f55ed18bc 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 3632a26bf4 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 1f8d6fe7d4 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards df52fb0667 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 90fe7098db 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 6fd487d9eb 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards ff4a357a81 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards eca65e7bf2 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 214b8131b8 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards b49b6e2402 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards aa2f3d25e4 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 76ef630983 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 44bcf062db 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 400a06f142 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 9ab1831d97 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 2076d3ec94 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards ced925e1cd 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 03985bc5ad 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards ae9bafd7a0 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 3dd6ad1fc2 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards e86b94b010 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards a032eec958 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] discards 8b2b707451 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] discards ed9a04db59 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] discards e54712704e 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] discards 4d9f9841bd 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] discards 3b5318a7d8 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] discards a9c0b7e594 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] discards 16c182a520 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits discards d8c774e99c 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] discards b8451cae4c 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] discards 6a4c695f81 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] discards c8cf191b29 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] discards d70a593336 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] discards 9ca961d2ae 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] discards 5b94986be6 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] discards f46798977f 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] discards dc3d15ffc0 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] discards 1ca9feb739 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] discards e4000e339a 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] discards 7547cf47d4 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] discards f2bf653be9 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] discards 85b5f9b890 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] discards 8fec9fc34b 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] discards d81a01f0fa 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] discards b7cf0562f2 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] discards 983100102d 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] discards 821b902a0c 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] discards fb93e52e31 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] discards 89ace709bf 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] discards fa55091b33 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] discards f173ab94dc 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards 9a16c80e93 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards 889f29f207 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards d1d117571a 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards 90c778fc89 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards 03915801ed 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards 6647b7518e 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards 3f7caac99c 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards 031b224363 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new 2791d50143 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new 4190efe238 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new b9d68bbf08 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new d5a0af3c83 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new e5acfb4097 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new 520bfe41d6 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new 32054eac01 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new c6e8302939 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new db3d63ead2 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new 3a72f9069a 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] new 56d24e1b8b 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] new 8d37e8ae54 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] new 69b21d663e 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] new 2060ae8089 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] new 14ed456c65 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] new 88e1677c05 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] new 561eb50257 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] new bd6bb58ea5 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] new 46c7a8c53c 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] new 9e620642dd 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] new 39cfc3c10d 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] new dbdc9c00ba 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] new decb27a909 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] new 1ca1467740 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] new 33e8419c7d 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] new 039061ce49 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] new 706ba61643 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] new a3875aad08 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] new 6be84a49db 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] new 3d45b3b038 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] new 6dfc792b02 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] new 83979ca0f4 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits new 269d56257d 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] new 064583209a 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] new d24df5daae 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] new 6892dcd771 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] new ace928847a 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] new c3458fa058 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] new a4a82ce65f 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] new 6b9b92c7d1 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 0cc4d11d8d 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 00e89387a9 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 78739c1469 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new b4dfe0a3e1 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new fda5fb2569 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 61a9a3a229 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 293eb5ab4f 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 58db66457e 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 7540f2a038 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 5dc37f3fc4 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 4d6a059362 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new bab9e31a1c 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 18573a0a7c 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new d0f9a22d2d 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 71ec177d67 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 0fbef97544 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new b6403ba022 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 85b44049da 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new dca5bcdef5 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 6559b9f9c7 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new a842f3f7f9 212: force: #24: 1: Success after binutils: 2 commits new 02821d1fb2 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new daf0de817a 214: onsuccess: #26: 1: Success after binutils: 12 commits new 38c01429e4 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 4154bc27ed 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 39e96babf2 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 4f83fe4390 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new d613dc7e4e 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 590cede7d8 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 911dd36fbc 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new a2a87cba9c 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 4b1a06a6d6 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 8f800755bb 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new f5f20b5af1 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 1996f46d82 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new dd4913468a 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 6b8b87c776 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 6781af0fc5 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new ad22584094 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 00b8269c10 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 3083e198c0 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 137811a315 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 536588c6d9 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 11e8f71a8b 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new f95c3045a0 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 343473a4bd 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new d4747502e3 238: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new bca7f4a325 239: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new be9ab012bb 240: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new a88be1e483 241: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new cf7ce6dd08 242: force: #69: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new a048ddfa71 243: force: #71: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new caf5eec026 244: force: #73: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 3cd1e75667 245: force: #75: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 27801dd8e2 246: force: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 3c3e5cd6d1 247: force: #79: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 67fcd28574 248: force: #81: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 7b227432f3 249: force: #83: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new b0f4872da9 250: force: #85: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new e4cc40209d 251: force: #87: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 9aa0cc67e8 252: force: #89: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 7cc77a523a 253: force: #91: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...]
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 (494c02f2a4) \ 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 2156 -> 2188 bytes 02-prepare_abe/console.log.xz | Bin 2416 -> 2448 bytes 03-build_abe-binutils/console.log.xz | Bin 35880 -> 35640 bytes 04-build_abe-gcc/console.log.xz | Bin 204500 -> 204176 bytes 06-build_abe-linux/console.log.xz | Bin 8728 -> 8772 bytes 07-build_abe-glibc/console.log.xz | Bin 241968 -> 242764 bytes 08-build_abe-gdb/console.log.xz | Bin 35004 -> 35024 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3880 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2744 -> 2792 bytes 11-check_regression/console.log.xz | Bin 1604 -> 1596 bytes 11-check_regression/results.compare | 2 +- 11-check_regression/results.regressions | 2 +- 11-check_regression/trigger-bisect | 4 +- 12-update_baseline/console.log | 72 ++++++++++++++--------------- git/glibc_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 2 +- mail/results.regressions | 2 +- manifest.sh | 10 ++-- results | 2 +- sumfiles/binutils.log.xz | Bin 62732 -> 62716 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150776 -> 150788 bytes sumfiles/gas.sum | 2 +- sumfiles/ld.log.xz | Bin 122640 -> 122624 bytes sumfiles/ld.sum | 2 +- 26 files changed, 53 insertions(+), 53 deletions(-)