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 121bb04074 251: force: #87: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 9193d763a0 250: force: #85: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 088ea5bda8 249: force: #83: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 45eaf14290 248: force: #81: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 533e20f2e7 247: force: #79: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards ca45687a58 246: force: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 2db286a4b1 245: force: #75: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 322f12c510 244: force: #73: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 6b637d646a 243: force: #71: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 4a2781e573 242: force: #69: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards da225f88d2 241: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards a348df646c 240: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 01b4923a8f 239: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 5ff0cb9061 238: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 3b2d7dfedd 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 04bd6548c1 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards c0370bc755 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards fcfa0a8ce9 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards e78bf9eb31 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards dc2174b884 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 7e9f028a4d 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 14d53efc54 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards b38436e1bb 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards a3da0f3fc4 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards cacd3cf299 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 11686c4f6d 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 6789af3079 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 429ffbbdc4 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 38f5563729 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards b2ede97ec6 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 65f8c8ebc0 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 7bb51ba065 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards aa4bbd8e9b 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards e2a2769979 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards f8911e0bc3 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards e52ca14253 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 3de4fcfbd1 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 697d8a6060 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 4d68de5e2a 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards 517b2b78c1 212: force: #24: 1: Success after binutils: 2 commits discards 4de1ce33d6 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 8c8510e293 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards f1603cf52e 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards a36b26e49f 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 3b6255ac8f 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards df0656026d 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards dd502f9c5b 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 3586639927 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 632d88bef0 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 2c166391f4 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 6dcb0fa711 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 1f8d639c4c 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards a47e5714af 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 9c6e93e651 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 1a75582927 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 15001335a2 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 2fdaa3d9e7 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 89c8da731b 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 2e552353d3 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 19c6dcf8e9 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards c1a23bb3d9 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards b094acf6da 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] discards 507c6e8d8c 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] discards 90614a55c3 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] discards 23e1a16ed3 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] discards ffe7325c5e 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] discards 821c1988fe 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] discards 8d7dfc5547 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] discards f6a5cbc376 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits discards f596e3888e 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] discards 4b14153d76 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] discards 6f9b0a3f37 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] discards 107b96f5a0 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] discards 89a14ccfb2 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] discards b735b3240b 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] discards c135acf113 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] discards ffe1ab68f3 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] discards 3d9d3ab9d3 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] discards ad7a44c287 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] discards 0da22cc336 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] discards 41095f8dcc 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] discards aac904dc51 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] discards 33a8c82d1d 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] discards bd3b77cecb 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] discards c78a73331a 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] discards a2efe33827 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] discards 9e4bf4b049 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] discards 6594300836 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] discards c75540f262 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] discards ae9ee9c524 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] discards 45fa556e34 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] discards 18fe5dc190 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards c5fa1da392 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards 553f47cd15 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards 4bb82a541b 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards ea2eb113c0 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards 7587bb557f 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards f05fc837c4 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards f8561c0af3 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards 9b69ee814f 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards 707f7cf613 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new e969d98077 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new 031b224363 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new 3f7caac99c 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new 6647b7518e 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new 03915801ed 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new 90c778fc89 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new d1d117571a 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new 889f29f207 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 9a16c80e93 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new f173ab94dc 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new fa55091b33 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] new 89ace709bf 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] new fb93e52e31 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] new 821b902a0c 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] new 983100102d 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] new b7cf0562f2 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] new d81a01f0fa 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] new 8fec9fc34b 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] new 85b5f9b890 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] new f2bf653be9 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] new 7547cf47d4 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] new e4000e339a 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] new 1ca9feb739 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] new dc3d15ffc0 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] new f46798977f 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] new 5b94986be6 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] new 9ca961d2ae 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] new d70a593336 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] new c8cf191b29 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] new 6a4c695f81 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] new b8451cae4c 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] new d8c774e99c 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] new 16c182a520 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits new a9c0b7e594 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] new 3b5318a7d8 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] new 4d9f9841bd 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] new e54712704e 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] new ed9a04db59 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] new 8b2b707451 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] new a032eec958 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] new e86b94b010 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 3dd6ad1fc2 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new ae9bafd7a0 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 03985bc5ad 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new ced925e1cd 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 2076d3ec94 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 9ab1831d97 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 400a06f142 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 44bcf062db 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 76ef630983 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new aa2f3d25e4 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new b49b6e2402 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 214b8131b8 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new eca65e7bf2 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new ff4a357a81 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 6fd487d9eb 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 90fe7098db 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new df52fb0667 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 1f8d6fe7d4 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 3632a26bf4 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 1f55ed18bc 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 5b7f1a7519 212: force: #24: 1: Success after binutils: 2 commits new e1798985ff 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new 6715f5ad62 214: onsuccess: #26: 1: Success after binutils: 12 commits new 559b471695 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new f7a699b508 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 9251ea0b45 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 5976d7b94e 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new e80e750c5f 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 193e21bf57 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 2f8fb317c2 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new cdf6a47217 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 8958ed3227 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 9f1960825e 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 1160f582a3 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 54b59ee51a 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new c7fd2b6dce 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 670bd130a8 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 5cf3995c0f 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new c813297d66 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 8cc54bfc71 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new d30d4d5bc0 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new db661fc3b9 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 3a81e36eda 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 0d4e2eba9f 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new c7c7ad4205 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new d8e6cc218e 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 1f9944748d 238: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 2fdc4c8f52 239: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new fa5fb0417e 240: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new b53bd0f955 241: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 107266cc0f 242: force: #69: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new baac532242 243: force: #71: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 34ff0fe760 244: force: #73: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new cbc8ec45a2 245: force: #75: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new f036eb7065 246: force: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 3fde5e3616 247: force: #79: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 372e01a149 248: force: #81: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 5691ef1529 249: force: #83: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 7fd718601d 250: force: #85: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 5ca94b8b24 251: force: #87: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 494c02f2a4 252: force: #89: 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 (121bb04074) \ 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 2144 -> 2156 bytes 02-prepare_abe/console.log.xz | Bin 2440 -> 2416 bytes 03-build_abe-binutils/console.log.xz | Bin 35940 -> 35880 bytes 04-build_abe-gcc/console.log.xz | Bin 205232 -> 204500 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8776 -> 8728 bytes 07-build_abe-glibc/console.log.xz | Bin 241792 -> 241968 bytes 08-build_abe-gdb/console.log.xz | Bin 35688 -> 35004 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3872 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2740 -> 2744 bytes 11-check_regression/console.log.xz | Bin 1600 -> 1604 bytes 11-check_regression/results.compare | 8 ++-- 11-check_regression/results.regressions | 8 ++-- 11-check_regression/trigger-bisect | 4 +- 12-update_baseline/console.log | 72 ++++++++++++++--------------- git/gdb_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 8 ++-- mail/results.regressions | 8 ++-- manifest.sh | 12 ++--- results | 8 ++-- sumfiles/binutils.log.xz | Bin 62692 -> 62732 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150732 -> 150776 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 122604 -> 122640 bytes sumfiles/ld.sum | 2 +- 27 files changed, 70 insertions(+), 70 deletions(-)