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_gdb/master-aarch64 in repository toolchain/ci/base-artifacts.
discards cf82f294014 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gc [...] discards 52632ccbb5b 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards 9c6ff29b27e 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 6bd8a6e9685 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards d5f1be19d9b 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gc [...] discards e5a3e45cd3d 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gd [...] discards 4ed5325531a 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gd [...] discards 3f5cdea79b0 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] discards 4c7410ba098 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 30590bfcda2 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] discards 9c492353713 212: force: #45: 1: Success after gdb: 22 commits discards 9ea9a17985f 211: onsuccess: #44: 1: Success after linux: 26 commits discards f19ed91b537 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] discards 6f5d4bfe745 209: force: #37: 1: Success after baseline build: no new commits discards f8a9dbcf461 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 1045213f942 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 4d31bb9e452 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 8c45e27fc5a 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 5007da8a973 204: force: #26: : Failure after baseline build: no new commits discards f514d878dda 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards df2b786dbcb 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 316e463e1a4 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 979b435bf6d 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 935656a3aec 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards dd0e2f03da9 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards b0b2ff56b23 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 96d84e44691 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 292ca3b1f36 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 43aa209cec1 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 0dc2905eff4 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 3d2f1f83195 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards cc3d727de63 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 9e384d89711 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards fa53e20152b 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 6a9c0dd2652 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards ed8d25e5ed5 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 3780d2304c6 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 5841c49ae2f 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 4dac1492f4f 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards abde4336be6 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards cbb945ab6ea 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards 066d24a6173 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards 65c85a1cc62 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards a1c28a4ed4e 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards 963b94c9b4e 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards 405b6f01046 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards ff0b62906fb 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards a28d10fa1c3 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards ef7cfb58a34 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards 4d06c4bb22f 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards 791fb1160ff 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards 12e95e26276 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards 44d75b1971e 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards 95996c4468a 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 83a5f141005 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards e63b8d344e6 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards 20630651afd 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards b626e8e0365 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards 936f1748f7d 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards eed5bc7c2b7 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards 2daddd715a3 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards 063656c44f5 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards b9335b63f19 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards baa07c4080c 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards d328970ba3f 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards f2336333575 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards b51fd99d38f 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards b328efdd5fd 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 95ea2f1fdb5 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 015d75c4b2f 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards ef0362cdc08 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 044fd68df91 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 7401beaf694 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 3773302ff15 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 470938e6864 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards e8cde38a554 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 819ec28b4de 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 6bf84a7fae2 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 177cc3e4ea2 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards dc780c2656b 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards ce74efeabe2 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 0e2a544ccd7 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 1aec8c88a5e 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 03db579ee8a 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards aa31cf11022 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 2177fb38a03 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards 0b6a6256d34 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards d25fbddb6f1 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards bd32c245d55 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards 8b5ee489db6 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 8e8f4d10a6a 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards f74506abfd9 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 3b315ea9e23 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 8c3a7c43421 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 598b6980cbb 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards 3d61aed3351 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 4e626d1fd4c 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 1a1e4bdb7ea 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards a7f9b66c44a 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 29f233a312f 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 55c8ba43555 122: onsuccess: #909: 1: Success after linux: 2753 commits new b8e76de5f36 122: onsuccess: #909: 1: Success after linux: 2753 commits new f65201139d5 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 88680d51b69 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 382511af343 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 63c3d883887 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 7e1b4cff0bb 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new ab97caf08ac 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new 92ac5cea3ca 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 22b17bfe686 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new dbf685832c9 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 42012cc2a05 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new b331eb386de 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new de893a1f8bf 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new f3a80a3d47c 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 41bd8be60a4 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new df51a4bad76 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new ccba7224430 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new efd2143d3ab 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 2dfa34c62e5 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 67eaad2d9f9 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new a105a932acd 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 4d3a6043ee0 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 9e90be19fac 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new 2041998b24f 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 3ef0550c46b 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 3fc396a3200 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 4acb9eb139c 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new f3f21b4a294 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new f873baa7efa 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new f815fef2f99 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 7a61a73e1fa 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 8e1d0180e1c 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 2e99307c977 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 7ab2bd7d991 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 19602a3ee77 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new 990d2eb0557 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new dd6d4254a46 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 9363c90ce42 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new a30a27718b4 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new b87372fedbc 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new 5828f782e98 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new d6876f47944 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new 64372121e27 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 77834eb7be2 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new 6a656038ea7 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new b60b11ffc5a 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new 3db686c4c07 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new dc7c438aff8 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new 59dee1f1414 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 2d32a79d985 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new 5d322972060 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new cd2f5eba390 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new d46e656998e 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new b4aa12c71b5 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new 8071ccf0648 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new 935dd44e741 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new 1642c0525fc 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new 1865633703d 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new cd6a527034f 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new d608be08545 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new 76381f31236 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new c1dd5a7e8a8 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new 5d49b39271f 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new 9dedf53f97f 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 361713ebcfa 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 96bf84c3df2 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 02058ee3109 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 536de598137 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new c180c6bbffa 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 26894c4338d 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 51860b11339 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new d76c884872b 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new e5c365f27d2 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 2632b1085e2 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 3afe416f1ea 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new c1b32b801c7 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 36ffce81149 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 68f9b1ff6d4 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new ef060d7ec15 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 9ce1fba9c58 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 30c452da42a 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 3bae10b4700 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new da76051cd9b 204: force: #26: : Failure after baseline build: no new commits new 2bb98b55976 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 014c1bd8187 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 5404e4d4a09 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 76cb9fb01cb 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 18ea8d1b585 209: force: #37: 1: Success after baseline build: no new commits new 1827794688c 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] new 75d0829fc9e 211: onsuccess: #44: 1: Success after linux: 26 commits new 2d838742c6b 212: force: #45: 1: Success after gdb: 22 commits new cb9c109599c 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] new e8d4d81a3c9 214: onsuccess: #47: 1: Success after gdb: 21 commits new 6b54ce1a86d 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] new e2708b26e9d 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gd [...] new 5578ad45a4d 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gd [...] new 65de60968e9 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gc [...] new 91ca8f2b51a 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 88b72cb9aae 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new df32780e922 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new c999792675f 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gc [...] new 6388e0c5aae 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits
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 (cf82f294014) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...]
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 2032 -> 2052 bytes 02-prepare_abe/console.log.xz | Bin 2520 -> 2520 bytes 03-build_abe-binutils/console.log.xz | Bin 35596 -> 35736 bytes 04-build_abe-gcc/console.log.xz | Bin 203448 -> 203336 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8504 -> 8592 bytes 07-build_abe-glibc/console.log.xz | Bin 240732 -> 241532 bytes 08-build_abe-gdb/console.log.xz | Bin 34996 -> 34808 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3836 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2704 -> 2700 bytes 11-check_regression/console.log.xz | Bin 10888 -> 3140 bytes 11-check_regression/results.compare | 24 +- 11-check_regression/results.compare2 | 1046 +-------------------------------- 12-update_baseline/console.log | 68 +-- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- mail/changes-list-long.txt | 29 +- mail/changes-list-short.txt | 2 +- manifest.sh | 27 +- sumfiles/gdb.log.0.xz | Bin 1991528 -> 2000712 bytes sumfiles/gdb.log.1.xz | Bin 15552 -> 28568 bytes sumfiles/gdb.sum | 18 +- sumfiles/gdb.sum.0 | 22 +- sumfiles/gdb.sum.1 | 103 +++- 24 files changed, 177 insertions(+), 1166 deletions(-)