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 7ec1cc1f8a1 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gd [...] discards 41f2d220a3e 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gd [...] discards be8cf1dc6b4 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] discards e7f367ec52d 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 6f79f8ae206 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] discards 94791074ebf 212: force: #45: 1: Success after gdb: 22 commits discards 2c072b24841 211: onsuccess: #44: 1: Success after linux: 26 commits discards 81513c4808a 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] discards 07a3d44bd50 209: force: #37: 1: Success after baseline build: no new commits discards 2701b615764 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 81d8807a6af 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards bc89cf9b924 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 322cd2612c8 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 8252bb846b9 204: force: #26: : Failure after baseline build: no new commits discards d003490abe2 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 2a86eda6bbf 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards f923c9f32f5 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 61c40573b64 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards f8f54d504bb 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 3c6fc93a2a0 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 101288afa0c 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 50b758119a4 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 3dc8c7814b7 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards b6ac3c0f016 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards c02b7f05bdd 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 9f276f7409d 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 7017fc7ea61 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 8aa69a2fc3a 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 4310210ea71 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 64a39a36153 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 1eafbf27106 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 780c7bf168f 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 0f2575620c7 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards aecada3ca42 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards bc42acdfee9 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards 17250a38577 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards e6956c7e846 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards 29f90c94232 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards c67d798bcf8 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards 46d5fa8a1c7 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards 167837889fb 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards 63c726621a4 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards 7974f6f7fe3 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards 49a9eb1f475 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards 9bb959a9cc2 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards ecb26a19239 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards faa485551b5 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards b96b7331d3c 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards cf7c2ec4114 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 99a55c78122 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards b83650f7b6a 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards a02938a9d98 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 5b4fdea19a3 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards 4e7424115b5 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards 17f587e5cda 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards 624d6b2c40b 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards 798afb0c33c 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards ceb7fd9e12c 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards d692c64d985 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards ac30131dcc7 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 91deb8bc925 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards 614aff88f27 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards f5da8b0b39a 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 49b0b2f51f8 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards aee65f86088 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 53d4cbfb43e 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 1bec0612131 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 11df1a2d5a6 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards efc2d60ded5 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 7866c276518 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards cae4c63a686 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 013e9cba704 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 8b4fb8eb7d2 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 119fed2ddfa 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards 2e449860bd5 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 0f0995b384b 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 39aa799f9e0 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards d36a7711a33 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards db8b398f1d4 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 8d2ebaf3159 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards afa4d2e08e2 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards 65dc0f98648 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards ea19baa57fe 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 9ddfbe06ae6 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards a5c21b0c6d1 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 1f425776462 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards a20f1015192 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 30d41a7f397 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 882d0d25664 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards fea149f3ff2 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards f9ed16dc911 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 4900b4cdef1 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 8d00739eab2 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 94721b0a27b 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards ccd57654f6d 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 1a0202fdf46 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 50ac6c6e46f 121: onsuccess: #908: 1: Success after glibc: 2 commits discards a4dc7ac4453 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 5b4b83fd006 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards b0f70e7c3b7 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards e3a4a3a0535 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new 8023fd91e65 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new 7537f50fbde 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new a79c807cc1c 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 82e5d4c237a 120: onsuccess: #906: 1: Success after binutils: 29 commits new 6a7aec44fa3 121: onsuccess: #908: 1: Success after glibc: 2 commits new 0f2096c8f9e 122: onsuccess: #909: 1: Success after linux: 2753 commits new 9a4f5a55f79 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 910b0855d97 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 2d952a9097f 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new d47cdabdda6 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 01fa9009df0 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new d6231318f68 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new d50e9f86554 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new fcb9b29e586 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new f31cbfcc1db 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 04f5d109f10 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 19cc003ca5e 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new fa767d6020f 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new c8e0c9fd9fd 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new bf4ff419603 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new c3f4996e242 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new eced5f6bb05 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new 7d729e35492 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 45504080acc 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 203e862bcb5 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 3307ae34405 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 931ad531a20 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new d68254feea5 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new cb27545b7ef 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 55e0da38d83 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 564383a86cc 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 426ff9286a2 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 02801812426 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new 62db1643198 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new fc4507c6b65 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 181293c9b43 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new ee8e07a2af5 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new c8ade9dc293 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new cc6c17b1466 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new a01df45256d 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new e36203e7f60 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new af4212c4320 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 4158e49d87b 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new a765ff02fc9 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new f378d22eb77 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new c72d61a79cb 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new 46b465f3cf0 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new c684320cd6e 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 0df74b7f32c 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new 56a6eaca570 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new daffe1771d9 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new 92c7197ac7d 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new cb306aef8c4 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new 6d2b65e6648 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 91b13e38727 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new b5a369a9070 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new e0299012d0b 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new fc7b420c410 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new 987b1bba258 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new 9d9316c0c21 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new e4e7feaf459 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new da34bb9c679 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new 69dbc286704 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new 57141ac192e 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new 3c20e77ae13 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new 6e3799f099a 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new 8dec9c8b5ed 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new 4556bd8e308 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new fa488d8eb97 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 668f1a6d84b 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new f40d64acca6 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 1040c29ccdd 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 26698fe5cb4 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 926806146d1 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 1e3f855b489 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 793e248ee5a 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 6ab8c4bef60 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new d02692f35ea 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new a8c85989ac4 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 7d7c47dc1c9 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 218ecff2db5 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new fbbcbee3b25 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new a2c7ef38aa7 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new a3d38c42309 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new d112e2202be 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 0549715fd83 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new e6892d38611 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new b8795ff5174 204: force: #26: : Failure after baseline build: no new commits new 404083cb2f8 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 0749b94e903 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 8fcfc46c04f 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 937d642b6f8 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 7ff69d025c2 209: force: #37: 1: Success after baseline build: no new commits new 84b74362c2d 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] new 23f62bff4ab 211: onsuccess: #44: 1: Success after linux: 26 commits new 683faed3e69 212: force: #45: 1: Success after gdb: 22 commits new 379893d8911 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] new 448ef25f80f 214: onsuccess: #47: 1: Success after gdb: 21 commits new 2c250184bfa 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] new bcb2d88fd67 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gd [...] new 73a371bc4fd 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gd [...] new 1b138c455f6 218: onsuccess: #62: 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 (7ec1cc1f8a1) \ 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 2024 -> 1984 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2528 bytes 03-build_abe-binutils/console.log.xz | Bin 35116 -> 35188 bytes 04-build_abe-gcc/console.log.xz | Bin 203844 -> 203384 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8344 -> 8760 bytes 07-build_abe-glibc/console.log.xz | Bin 241032 -> 240500 bytes 08-build_abe-gdb/console.log.xz | Bin 34648 -> 34860 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3784 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2620 -> 2540 bytes 11-check_regression/console.log.xz | Bin 10244 -> 5604 bytes 11-check_regression/mail-body.txt | 35 -- 11-check_regression/mail-subject.txt | 1 - 11-check_regression/results.compare | 24 +- 11-check_regression/results.compare2 | 1038 ++------------------------------- 12-update_baseline/console.log | 66 +-- 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 | 26 + mail/changes-list-short.txt | 1 + mail/mail-body.txt | 35 -- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 37 +- sumfiles/gdb.log.0.xz | Bin 1988720 -> 2025572 bytes sumfiles/gdb.log.1.xz | Bin 28536 -> 15344 bytes sumfiles/gdb.log.2.xz | Bin 14828 -> 0 bytes sumfiles/gdb.log.3.xz | Bin 15012 -> 0 bytes sumfiles/gdb.sum | 33 +- sumfiles/gdb.sum.0 | 34 +- sumfiles/gdb.sum.1 | 103 +--- sumfiles/gdb.sum.2 | 110 ---- sumfiles/gdb.sum.3 | 110 ---- 36 files changed, 182 insertions(+), 1483 deletions(-) delete mode 100644 11-check_regression/mail-body.txt delete mode 100644 11-check_regression/mail-subject.txt create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt 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