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 1b138c455f6 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gc [...] discards 73a371bc4fd 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gd [...] discards bcb2d88fd67 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gd [...] discards 2c250184bfa 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] discards 448ef25f80f 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 379893d8911 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] discards 683faed3e69 212: force: #45: 1: Success after gdb: 22 commits discards 23f62bff4ab 211: onsuccess: #44: 1: Success after linux: 26 commits discards 84b74362c2d 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] discards 7ff69d025c2 209: force: #37: 1: Success after baseline build: no new commits discards 937d642b6f8 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 8fcfc46c04f 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 0749b94e903 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 404083cb2f8 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards b8795ff5174 204: force: #26: : Failure after baseline build: no new commits discards e6892d38611 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 0549715fd83 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards d112e2202be 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards a3d38c42309 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards a2c7ef38aa7 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards fbbcbee3b25 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 218ecff2db5 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 7d7c47dc1c9 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards a8c85989ac4 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards d02692f35ea 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 6ab8c4bef60 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 793e248ee5a 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 1e3f855b489 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 926806146d1 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 26698fe5cb4 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 1040c29ccdd 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards f40d64acca6 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 668f1a6d84b 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards fa488d8eb97 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 4556bd8e308 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards 8dec9c8b5ed 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards 6e3799f099a 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards 3c20e77ae13 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards 57141ac192e 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 69dbc286704 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards da34bb9c679 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards e4e7feaf459 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards 9d9316c0c21 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards 987b1bba258 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards fc7b420c410 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards e0299012d0b 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards b5a369a9070 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards 91b13e38727 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards 6d2b65e6648 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards cb306aef8c4 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 92c7197ac7d 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards daffe1771d9 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards 56a6eaca570 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 0df74b7f32c 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards c684320cd6e 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards 46b465f3cf0 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards c72d61a79cb 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards f378d22eb77 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards a765ff02fc9 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards 4158e49d87b 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards af4212c4320 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards e36203e7f60 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards a01df45256d 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards cc6c17b1466 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards c8ade9dc293 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards ee8e07a2af5 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 181293c9b43 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards fc4507c6b65 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 62db1643198 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 02801812426 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 426ff9286a2 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 564383a86cc 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 55e0da38d83 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards cb27545b7ef 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards d68254feea5 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards 931ad531a20 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 3307ae34405 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 203e862bcb5 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 45504080acc 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 7d729e35492 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards eced5f6bb05 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards c3f4996e242 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards bf4ff419603 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards c8e0c9fd9fd 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards fa767d6020f 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards 19cc003ca5e 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 04f5d109f10 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards f31cbfcc1db 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards fcb9b29e586 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards d50e9f86554 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards d6231318f68 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards 01fa9009df0 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards d47cdabdda6 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 2d952a9097f 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 910b0855d97 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 9a4f5a55f79 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 0f2096c8f9e 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 6a7aec44fa3 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 82e5d4c237a 120: onsuccess: #906: 1: Success after binutils: 29 commits discards a79c807cc1c 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 7537f50fbde 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new 5e5d7b23f3e 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new 192626d1687 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new e61080d775a 120: onsuccess: #906: 1: Success after binutils: 29 commits new 81e32b82fda 121: onsuccess: #908: 1: Success after glibc: 2 commits new c37fff1602e 122: onsuccess: #909: 1: Success after linux: 2753 commits new aaf9b4cc22f 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new a8f4e8ac802 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new ce27619ec1d 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 23d15655411 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 95e17bd52de 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 5a031ed412d 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new 11a5ad99a9f 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 43cd36dfb64 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new c5fb7d91091 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 626a27d3e79 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 4077730580b 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 36060b68e0a 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new 2a4ffffaa8b 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 2ffe17ca434 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 74fea35e337 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new 5d437af5857 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new a579fd4ddd7 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 401148fae3b 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 541167abb43 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 98c495f1a2e 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 21d4cc09a24 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 1ef3d2e25f0 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new 839b26551c9 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new a41d8a01cbb 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 9ec09bdee87 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 0a4e9a75717 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 05744a4c338 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new c59b599f015 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 56f62d50f4f 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 8d342a9e9ee 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 6860eac6807 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 316f3f6a69c 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 56163872a58 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new a4116bea665 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new cd6e0b64c72 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new 62021d83829 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new f579fa939a1 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new 538bcc9be05 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new 8b30ae1de91 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new 77f6f9871ec 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new 812ac746ee5 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new 35bf9fecfd0 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 9c87835ef8c 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new 413eb2a4733 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new 3eab06faff5 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new 3861c88152e 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new 7f5716d8286 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new f1ac2ab1707 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new afa02f3a23c 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new 364274487b2 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new 8d265ade25c 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new 02c925ce31f 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new a3321a9eb14 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new cc909f77fc7 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new d0a261dd2c0 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new 9f4e9791e04 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new 0298f0a7bee 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new a76838b0de1 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new 1e32132cac0 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new 6bd410fff44 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new 99691193428 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new 4dbc66d1d06 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new 6d6402f623e 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 16c4932f350 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new c655ea4754f 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 4847a146890 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 43b97da9923 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new eaac9083644 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 889cb16da20 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 4f6e3705842 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new f9c9a3f2cac 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 1feaec752e9 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 62e997c9651 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 857ce37abfc 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 8944ad8d166 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 9f3e9ebcee0 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 74240094c06 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new aa8de6bd727 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 9b474344e05 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 8cd9408cd98 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new a3b368ce873 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new baf31157b8c 204: force: #26: : Failure after baseline build: no new commits new 46376cd4153 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new b7caca5a96d 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new f855b3b9bf7 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new fd6b02747f4 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 1caa10ced7c 209: force: #37: 1: Success after baseline build: no new commits new 5d06170677e 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] new 3f14ab86cd0 211: onsuccess: #44: 1: Success after linux: 26 commits new 4ffd2b44258 212: force: #45: 1: Success after gdb: 22 commits new fd0cb722538 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] new e2afb2c3ec3 214: onsuccess: #47: 1: Success after gdb: 21 commits new 8209e747cdb 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] new b40f8c71944 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gd [...] new 4df4e73781e 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gd [...] new 09c44f04e6e 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gc [...] new 315d12afdd6 219: force: #64: 1: [TCWG CI] Success after gdb: 32 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 (1b138c455f6) \ 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 1984 -> 2204 bytes 02-prepare_abe/console.log.xz | Bin 2528 -> 2492 bytes 03-build_abe-binutils/console.log.xz | Bin 35188 -> 35188 bytes 04-build_abe-gcc/console.log.xz | Bin 203384 -> 206552 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8760 -> 8876 bytes 07-build_abe-glibc/console.log.xz | Bin 240500 -> 242328 bytes 08-build_abe-gdb/console.log.xz | Bin 34860 -> 34532 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3844 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2540 -> 2752 bytes 11-check_regression/console.log.xz | Bin 5604 -> 3120 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 117 +- 12-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- mail/changes-list-long.txt | 32 +- mail/changes-list-short.txt | 2 +- manifest.sh | 27 +- sumfiles/gdb.log.0.xz | Bin 2025572 -> 1966132 bytes sumfiles/gdb.log.1.xz | Bin 15344 -> 70144 bytes sumfiles/gdb.sum | 3656 +-------------- sumfiles/gdb.sum.0 | 3660 +-------------- sumfiles/gdb.sum.1 | 8192 ++++++++++++++++++++++++++++++++- 24 files changed, 8274 insertions(+), 7458 deletions(-)