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 18ef91f53b5 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] discards aa94305402a 214: onsuccess: #47: 1: Success after gdb: 21 commits discards a6323b68c7f 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] discards aa6ce71a295 212: force: #45: 1: Success after gdb: 22 commits discards 05891301e86 211: onsuccess: #44: 1: Success after linux: 26 commits discards ffaac2e42c1 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] discards c48c466fede 209: force: #37: 1: Success after baseline build: no new commits discards 39d4412a487 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards b6dafcaeccf 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 29b2264b6a2 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 2815545b670 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 8418e656d9b 204: force: #26: : Failure after baseline build: no new commits discards 6d57b0bf7f6 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 818e5235cf4 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 25a73719768 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 666ea3eb682 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 8b0c7566e8f 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards ee304813c8b 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards cebaff9bad7 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards cdd42bf3a92 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 94f4ab9e978 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 9e16e36e5f7 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 1f07544583b 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 5f43d80a534 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards f8d68639201 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 9f58d783712 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards b21c6c7a2e5 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards a222430b63e 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 27768347f89 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 7ab124697c5 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards b8f6d907682 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 56886d4b072 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards 0583ad73333 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards 9a3ded47ac0 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards b9cf47697e0 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards 1d9995defb2 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 3908c28994a 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards 4fe1d664ed8 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards ae5d2bf3b86 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards ceca8e4d095 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards 05e015db8a2 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards 107b68fa6bc 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards 34ccaf0c778 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards 793a7a33c57 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards 1e6a126f686 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards e57e17dc9c2 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards 36575bf5ec9 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 864111d0c08 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards 634b2ea739e 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards 62ec148ed59 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 82314b40f99 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards d4a7d1ad3c2 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards 9767f2f672f 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards 676b6f69f76 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards e63a80b59a7 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards ebf1bed6f87 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards b698ff1d522 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards f87e2cfc7e6 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 8ffb5614055 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards 2baebd3366b 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards 6670e1f7a12 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 739e2b3ebfc 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 440ca96b9eb 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 6dcbd252af5 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 9f78f5f97f5 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 2e9ba18105f 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 1401f628cfd 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 0bb3298d915 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 73fac70e821 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards d17eb3d9426 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards ae91f9bdb7d 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 2e2ebd917eb 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards d4b13c87f5d 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 7adcdce2a41 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 3c1c704fc5a 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards ed8f21b6fdb 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards fafe782c71c 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 6e84f35c0dc 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 690be2eb051 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards af7f7440a44 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards e19e90e1b58 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards eb8432b53ed 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards 61ad241c838 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 228577b307e 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 55a9b670fe6 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards a2f06de278f 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 5764bcbb781 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 2dc1de60b34 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards cd30544fd2c 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards ff48a6332a5 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 82169dde470 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 30f832da262 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 85ec7e4236e 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards abf49f44673 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 73b5da8069b 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 2ddb268ac6f 120: onsuccess: #906: 1: Success after binutils: 29 commits discards df902dcd6e2 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards a3e80ce3f49 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards afc01a5b01b 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 76355ca2b80 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards cade53577a7 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new f720c4701d8 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new 5ddd9f302c0 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new 0fde57e394b 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new 9c52823a026 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new 20b62c4a293 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 950e38d021a 120: onsuccess: #906: 1: Success after binutils: 29 commits new dc1ba19581c 121: onsuccess: #908: 1: Success after glibc: 2 commits new 41115f80cc9 122: onsuccess: #909: 1: Success after linux: 2753 commits new cb4792961f1 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 18d7714ef6f 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new b536ad9010e 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 426cf0ece46 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new ed5329caf29 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new cbe9cc77775 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new d278c97e179 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new cef5c31a820 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new e39f57d7b72 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new fc9542657dc 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new e516e0145dc 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new f46670953ec 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new 6ae0c202fda 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new a109367b21d 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 5615fff2a1c 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new 115fcd21e6a 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new f8838634bb3 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new b97c88afadf 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 066b8ddd78b 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new db119916624 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 3481f01e855 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 020661c46b1 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new 580b9e6bb90 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 3bccb8c4108 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 7aee29d2d00 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 8c3b188c79c 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 14f20e93c80 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new 7ccc6f6077a 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 87689d6c66b 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 8d1b03c083e 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new e2e4ef39faf 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 021ec51a676 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 37ebcce2f34 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 8aa86b90408 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new 39dea81a50a 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new a0c5d9260a5 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 3b72e0c2c36 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new acd02259ff5 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new ad2e41f6928 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new 42e9bc3c282 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new 7e0d6d08f54 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new ed86baaa878 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 76740243b9f 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new 3237f66360d 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new 59d8c05da10 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new 67b1d176d8a 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new 0679a6cc5cc 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new d12882b10d9 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new f6ad48c105e 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new bdaee88e99f 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new 9f6124b7dc8 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new 4166ae12fa0 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new aaabca8b678 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new 08f6ad175cd 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new 9f40c044ec4 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new 609d6f6f9fa 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new 77f21bee4c2 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new fd48869cac2 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new cfdf306b22c 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new 78f2efc438d 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new 8a8f6ad9e8e 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new f72afcbf39e 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new 08f9783f467 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 05e76ece383 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 059d08b8d09 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new b876595f57a 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 8c739aa1ee0 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new e69bdc5eb1c 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 70899ad3b2a 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 259d735bdd4 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new e7e9c4aa849 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new b2b4914f9d3 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 3fffacd4583 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new beb24826858 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 86ab0ad94c8 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 140f66e77bd 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 5ee484da63b 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 7c1578cd9fc 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new fb2ab948582 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 4071cd10144 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 495725e3581 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 24c2c6d9af0 204: force: #26: : Failure after baseline build: no new commits new dbb55406dcd 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new be25bb6fe77 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 8338c64bafb 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 1bb55025f82 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 3da951449c0 209: force: #37: 1: Success after baseline build: no new commits new 8bcaabc4722 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] new 4fffe8b4a27 211: onsuccess: #44: 1: Success after linux: 26 commits new f7826273620 212: force: #45: 1: Success after gdb: 22 commits new 36cef7e193a 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] new aecb3626a7a 214: onsuccess: #47: 1: Success after gdb: 21 commits new f8083c67c44 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] new 51b3bc4f256 216: onsuccess: #52: 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 (18ef91f53b5) \ 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 1964 -> 2088 bytes 02-prepare_abe/console.log.xz | Bin 2516 -> 2536 bytes 03-build_abe-binutils/console.log.xz | Bin 35124 -> 34924 bytes 04-build_abe-gcc/console.log.xz | Bin 203404 -> 203736 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8480 -> 8892 bytes 07-build_abe-glibc/console.log.xz | Bin 241456 -> 241260 bytes 08-build_abe-gdb/console.log.xz | Bin 34732 -> 34752 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3780 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2764 -> 2648 bytes 11-check_regression/console.log.xz | Bin 5216 -> 5180 bytes 11-check_regression/jira-body.txt | 1 - 11-check_regression/mail-body.txt | 2 +- 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 56 +++++++++--------- 12-update_baseline/console.log | 36 ++++++------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 1 - mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++------ sumfiles/gdb.log.0.xz | Bin 1954392 -> 1950016 bytes sumfiles/gdb.log.1.xz | Bin 20480 -> 33796 bytes sumfiles/gdb.log.2.xz | Bin 5412 -> 5424 bytes sumfiles/gdb.log.3.xz | Bin 5204 -> 5424 bytes sumfiles/gdb.sum | 15 +++-- sumfiles/gdb.sum.0 | 17 ++++-- sumfiles/gdb.sum.1 | 103 ++++++++++++++++++++++++++++++++-- sumfiles/gdb.sum.2 | 4 +- sumfiles/gdb.sum.3 | 4 +- 34 files changed, 194 insertions(+), 97 deletions(-) delete mode 100644 11-check_regression/jira-body.txt delete mode 100644 mail/jira-body.txt