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 f31d5445f2c 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards 4662a23de58 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards b41e6ff1e80 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 43aca899884 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gc [...] discards 971a2fa4873 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gd [...] discards 6a9aea6a0d3 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gd [...] discards 4d47ceba027 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] discards f0000d73dd7 214: onsuccess: #47: 1: Success after gdb: 21 commits discards ecd322c76bd 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] discards 58b0ea4d3ba 212: force: #45: 1: Success after gdb: 22 commits discards 581c9f25a32 211: onsuccess: #44: 1: Success after linux: 26 commits discards 2eac9e0f723 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] discards bddd52c35df 209: force: #37: 1: Success after baseline build: no new commits discards 991e201b890 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 88eda637be5 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards d5f5ab75b9e 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 0fbc77ac0d5 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards d5a2527a016 204: force: #26: : Failure after baseline build: no new commits discards 1fbb2211dc2 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 12b2031d719 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 78f1601fd77 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards c264b456526 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 27c70738761 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 3ae1519b9d4 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 4f3e5f3eef7 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 7e733a8e6d6 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 0e0ffd8b29d 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards da532bad07d 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 093c33d97e1 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 89698251ab8 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 00a19c16162 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 7c3f2f604bc 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 54e1e9c7a17 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 7f8f0a1c3fa 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 1a169b5ca4c 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards c4be55c0a50 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards a4afa2b1ec9 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 8c14d932ff3 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards 541c6bdf2a2 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards 5986ff8a2f8 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards ed69d3627e0 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards 17a1381c38d 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 2a4ebeb7d75 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards f60c7c7a7b4 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards d7405ed577a 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards fabc52a31e8 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards 5b81b9660d1 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards 93069d90411 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards da4c034d559 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards 90a924f6fc1 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards 89179b05355 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards 674ce4ef9a3 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards 5cc499b0cb5 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards de60303642f 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards af2b6707a4d 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards c92428a4bbf 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards c7503bd7b07 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards b31c7d9d152 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards 29023845b10 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards 1e329fa7ccd 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards 258afa83822 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards 7dd89d3eb6e 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards 6398cae56be 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 32c728b43bc 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 5c594f6c4ed 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards 27557a9c615 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards 0ff60d4c234 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 7a524aa3241 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 8d848ba9bdc 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 1b73d2f6fcc 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards bfa9f57ba7a 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 055ca3326c7 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards f8a7a46f7f8 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 96150f25e61 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 02efbbdd985 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 7c9cf424e7e 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 0ff0f941589 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 9ff10c4edf0 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards 2e2897d5b2a 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards bfd675a23cc 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards a07785ac0c0 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 44d54229529 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 5ecd163bf2b 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards d0c49ee87e2 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 2b80bd077d8 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards 8e756043466 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards 2492689ea5c 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 713fa3d4c81 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards 50566f68fbb 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 4fdcb9291a5 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards e8da27bacf5 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 5e6886f9950 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 99be72c7cd2 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards f2471e34de9 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards ada6218b2c9 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 29bd102fa3c 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards e8bd9e4e03d 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 28aa58308ee 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 003e788654f 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards d6b2fd17e54 122: onsuccess: #909: 1: Success after linux: 2753 commits discards a95dca712b8 121: onsuccess: #908: 1: Success after glibc: 2 commits new 8dfb54dc4bb 121: onsuccess: #908: 1: Success after glibc: 2 commits new 55c8ba43555 122: onsuccess: #909: 1: Success after linux: 2753 commits new 29f233a312f 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new a7f9b66c44a 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 1a1e4bdb7ea 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 4e626d1fd4c 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 3d61aed3351 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 598b6980cbb 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new 8c3a7c43421 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 3b315ea9e23 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new f74506abfd9 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 8e8f4d10a6a 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 8b5ee489db6 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new bd32c245d55 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new d25fbddb6f1 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 0b6a6256d34 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 2177fb38a03 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new aa31cf11022 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new 03db579ee8a 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 1aec8c88a5e 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 0e2a544ccd7 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new ce74efeabe2 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new dc780c2656b 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 177cc3e4ea2 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new 6bf84a7fae2 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 819ec28b4de 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new e8cde38a554 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 470938e6864 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 3773302ff15 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new 7401beaf694 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 044fd68df91 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new ef0362cdc08 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 015d75c4b2f 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 95ea2f1fdb5 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new b328efdd5fd 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new b51fd99d38f 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new f2336333575 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new d328970ba3f 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new baa07c4080c 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new b9335b63f19 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new 063656c44f5 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new 2daddd715a3 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new eed5bc7c2b7 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new 936f1748f7d 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new b626e8e0365 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new 20630651afd 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new e63b8d344e6 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new 83a5f141005 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new 95996c4468a 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new 44d75b1971e 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 12e95e26276 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new 791fb1160ff 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new 4d06c4bb22f 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new ef7cfb58a34 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new a28d10fa1c3 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new ff0b62906fb 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new 405b6f01046 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new 963b94c9b4e 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new a1c28a4ed4e 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new 65c85a1cc62 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new 066d24a6173 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new cbb945ab6ea 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new abde4336be6 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new 4dac1492f4f 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new 5841c49ae2f 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 3780d2304c6 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new ed8d25e5ed5 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 6a9c0dd2652 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new fa53e20152b 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 9e384d89711 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new cc3d727de63 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 3d2f1f83195 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 0dc2905eff4 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 43aa209cec1 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 292ca3b1f36 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 96d84e44691 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new b0b2ff56b23 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new dd0e2f03da9 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 935656a3aec 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 979b435bf6d 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 316e463e1a4 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new df2b786dbcb 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new f514d878dda 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 5007da8a973 204: force: #26: : Failure after baseline build: no new commits new 8c45e27fc5a 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 4d31bb9e452 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 1045213f942 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new f8a9dbcf461 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 6f5d4bfe745 209: force: #37: 1: Success after baseline build: no new commits new f19ed91b537 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] new 9ea9a17985f 211: onsuccess: #44: 1: Success after linux: 26 commits new 9c492353713 212: force: #45: 1: Success after gdb: 22 commits new 30590bfcda2 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] new 4c7410ba098 214: onsuccess: #47: 1: Success after gdb: 21 commits new 3f5cdea79b0 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] new 4ed5325531a 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gd [...] new e5a3e45cd3d 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gd [...] new d5f1be19d9b 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gc [...] new 6bd8a6e9685 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 9c6ff29b27e 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 52632ccbb5b 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new cf82f294014 222: onsuccess: #68: 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 (f31d5445f2c) \ 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 2012 -> 2032 bytes 02-prepare_abe/console.log.xz | Bin 2516 -> 2520 bytes 03-build_abe-binutils/console.log.xz | Bin 35228 -> 35596 bytes 04-build_abe-gcc/console.log.xz | Bin 204064 -> 203448 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8896 -> 8504 bytes 07-build_abe-glibc/console.log.xz | Bin 240924 -> 240732 bytes 08-build_abe-gdb/console.log.xz | Bin 34964 -> 34996 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3784 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2824 -> 2704 bytes 11-check_regression/console.log.xz | Bin 4252 -> 10888 bytes 11-check_regression/results.compare | 24 +- 11-check_regression/results.compare2 | 1115 +++++++++++++++++++--- 12-update_baseline/console.log | 42 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 29 +- mail/changes-list-short.txt | 2 +- manifest.sh | 31 +- sumfiles/gdb.log.0.xz | Bin 1948932 -> 1991528 bytes sumfiles/gdb.log.1.xz | Bin 34336 -> 15552 bytes sumfiles/gdb.log.2.xz | Bin 5508 -> 0 bytes sumfiles/gdb.log.3.xz | Bin 5424 -> 0 bytes sumfiles/gdb.sum | 1685 ++++++++++++++------------------ sumfiles/gdb.sum.0 | 1686 ++++++++++++++------------------- sumfiles/gdb.sum.1 | 340 +------ sumfiles/gdb.sum.2 | 182 ---- sumfiles/gdb.sum.3 | 182 ---- 31 files changed, 2480 insertions(+), 2848 deletions(-) delete mode 100644 sumfiles/gdb.log.2.xz delete mode 100644 sumfiles/gdb.log.3.xz delete mode 100644 sumfiles/gdb.sum.2 delete mode 100644 sumfiles/gdb.sum.3