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 51b3bc4f256 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gd [...] discards f8083c67c44 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] discards aecb3626a7a 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 36cef7e193a 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] discards f7826273620 212: force: #45: 1: Success after gdb: 22 commits discards 4fffe8b4a27 211: onsuccess: #44: 1: Success after linux: 26 commits discards 8bcaabc4722 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] discards 3da951449c0 209: force: #37: 1: Success after baseline build: no new commits discards 1bb55025f82 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 8338c64bafb 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards be25bb6fe77 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards dbb55406dcd 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 24c2c6d9af0 204: force: #26: : Failure after baseline build: no new commits discards 495725e3581 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 4071cd10144 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards fb2ab948582 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 7c1578cd9fc 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 5ee484da63b 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 140f66e77bd 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 86ab0ad94c8 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards beb24826858 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 3fffacd4583 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards b2b4914f9d3 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards e7e9c4aa849 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 259d735bdd4 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 70899ad3b2a 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards e69bdc5eb1c 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 8c739aa1ee0 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards b876595f57a 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 059d08b8d09 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 05e76ece383 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 08f9783f467 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards f72afcbf39e 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards 8a8f6ad9e8e 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards 78f2efc438d 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards cfdf306b22c 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards fd48869cac2 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 77f21bee4c2 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards 609d6f6f9fa 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards 9f40c044ec4 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards 08f6ad175cd 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards aaabca8b678 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards 4166ae12fa0 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards 9f6124b7dc8 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards bdaee88e99f 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards f6ad48c105e 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards d12882b10d9 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards 0679a6cc5cc 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 67b1d176d8a 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards 59d8c05da10 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards 3237f66360d 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 76740243b9f 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards ed86baaa878 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards 7e0d6d08f54 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards 42e9bc3c282 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards ad2e41f6928 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards acd02259ff5 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards 3b72e0c2c36 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards a0c5d9260a5 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 39dea81a50a 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards 8aa86b90408 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards 37ebcce2f34 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 021ec51a676 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards e2e4ef39faf 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 8d1b03c083e 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 87689d6c66b 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 7ccc6f6077a 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 14f20e93c80 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 8c3b188c79c 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 7aee29d2d00 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 3bccb8c4108 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 580b9e6bb90 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 020661c46b1 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards 3481f01e855 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards db119916624 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 066b8ddd78b 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards b97c88afadf 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards f8838634bb3 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 115fcd21e6a 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 5615fff2a1c 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards a109367b21d 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards 6ae0c202fda 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards f46670953ec 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards e516e0145dc 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards fc9542657dc 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards e39f57d7b72 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards cef5c31a820 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards d278c97e179 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards cbe9cc77775 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards ed5329caf29 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 426cf0ece46 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards b536ad9010e 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 18d7714ef6f 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards cb4792961f1 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 41115f80cc9 122: onsuccess: #909: 1: Success after linux: 2753 commits discards dc1ba19581c 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 950e38d021a 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 20b62c4a293 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 9c52823a026 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards 0fde57e394b 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 5ddd9f302c0 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new cdaadddb596 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new e3a4a3a0535 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new b0f70e7c3b7 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new 5b4b83fd006 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new a4dc7ac4453 120: onsuccess: #906: 1: Success after binutils: 29 commits new 50ac6c6e46f 121: onsuccess: #908: 1: Success after glibc: 2 commits new 1a0202fdf46 122: onsuccess: #909: 1: Success after linux: 2753 commits new ccd57654f6d 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 94721b0a27b 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 8d00739eab2 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 4900b4cdef1 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new f9ed16dc911 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new fea149f3ff2 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new 882d0d25664 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 30d41a7f397 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new a20f1015192 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 1f425776462 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new a5c21b0c6d1 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 9ddfbe06ae6 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new ea19baa57fe 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 65dc0f98648 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new afa4d2e08e2 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new 8d2ebaf3159 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new db8b398f1d4 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new d36a7711a33 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 39aa799f9e0 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 0f0995b384b 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 2e449860bd5 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 119fed2ddfa 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new 8b4fb8eb7d2 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 013e9cba704 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new cae4c63a686 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 7866c276518 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new efc2d60ded5 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new 11df1a2d5a6 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 1bec0612131 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 53d4cbfb43e 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new aee65f86088 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 49b0b2f51f8 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new f5da8b0b39a 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 614aff88f27 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new 91deb8bc925 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new ac30131dcc7 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new d692c64d985 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new ceb7fd9e12c 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new 798afb0c33c 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new 624d6b2c40b 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new 17f587e5cda 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new 4e7424115b5 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 5b4fdea19a3 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new a02938a9d98 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new b83650f7b6a 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new 99a55c78122 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new cf7c2ec4114 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new b96b7331d3c 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new faa485551b5 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new ecb26a19239 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new 9bb959a9cc2 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new 49a9eb1f475 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new 7974f6f7fe3 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new 63c726621a4 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new 167837889fb 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new 46d5fa8a1c7 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new c67d798bcf8 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new 29f90c94232 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new e6956c7e846 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new 17250a38577 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new bc42acdfee9 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new aecada3ca42 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new 0f2575620c7 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 780c7bf168f 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 1eafbf27106 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 64a39a36153 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 4310210ea71 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 8aa69a2fc3a 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 7017fc7ea61 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 9f276f7409d 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new c02b7f05bdd 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new b6ac3c0f016 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 3dc8c7814b7 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 50b758119a4 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 101288afa0c 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 3c6fc93a2a0 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new f8f54d504bb 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 61c40573b64 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new f923c9f32f5 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 2a86eda6bbf 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new d003490abe2 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 8252bb846b9 204: force: #26: : Failure after baseline build: no new commits new 322cd2612c8 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new bc89cf9b924 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 81d8807a6af 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 2701b615764 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 07a3d44bd50 209: force: #37: 1: Success after baseline build: no new commits new 81513c4808a 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] new 2c072b24841 211: onsuccess: #44: 1: Success after linux: 26 commits new 94791074ebf 212: force: #45: 1: Success after gdb: 22 commits new 6f79f8ae206 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] new e7f367ec52d 214: onsuccess: #47: 1: Success after gdb: 21 commits new be8cf1dc6b4 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] new 41f2d220a3e 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gd [...] new 7ec1cc1f8a1 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gd [...]

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 (51b3bc4f256) \ 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 2088 -> 2024 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 34924 -> 35116 bytes 04-build_abe-gcc/console.log.xz | Bin 203736 -> 203844 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8892 -> 8344 bytes 07-build_abe-glibc/console.log.xz | Bin 241260 -> 241032 bytes 08-build_abe-gdb/console.log.xz | Bin 34752 -> 34648 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3812 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2648 -> 2620 bytes 11-check_regression/console.log.xz | Bin 5180 -> 10244 bytes 11-check_regression/results.compare | 24 +- 11-check_regression/results.compare2 | 1026 +++++++++++++++++++- 12-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/gdb.log.0.xz | Bin 1950016 -> 1988720 bytes sumfiles/gdb.log.1.xz | Bin 33796 -> 28536 bytes sumfiles/gdb.log.2.xz | Bin 5424 -> 14828 bytes sumfiles/gdb.log.3.xz | Bin 5424 -> 15012 bytes sumfiles/gdb.sum | 1685 ++++++++++++++------------------- sumfiles/gdb.sum.0 | 1684 ++++++++++++++------------------ sumfiles/gdb.sum.1 | 267 +----- sumfiles/gdb.sum.2 | 268 ++---- sumfiles/gdb.sum.3 | 268 ++---- 31 files changed, 2675 insertions(+), 2661 deletions(-)