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 676a2dfa36d 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 33718ff48c5 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] discards 721070651a2 212: force: #45: 1: Success after gdb: 22 commits discards 539c73cb306 211: onsuccess: #44: 1: Success after linux: 26 commits discards 6962c12b82c 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] discards 701f90ab597 209: force: #37: 1: Success after baseline build: no new commits discards 7be32c24106 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 22e65d17e09 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards cbea1943e07 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 7fff02c3986 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards e499f7417dd 204: force: #26: : Failure after baseline build: no new commits discards f3745e43e27 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 9e71045f64c 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 019b521e02b 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 946278acd1d 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 694230570eb 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards f056c7f47e1 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 84d926d61ec 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 79ab5101e64 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 476188ef4de 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 74c053a8bee 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 2dbd39bb04f 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 0a4a8bc03fd 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 26902ec3a71 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 6e3daaf7b70 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards fcd8a4b2917 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 262cc6b7eec 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 1f68f408ab1 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards ad17c45f65c 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 30dbb9aee64 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards f0da3e7328f 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards 47b1992225a 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards 43ee6fcc89e 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards ee67736bb8d 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards 29f71c22964 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 5ce72244020 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards 3d87b2db340 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards 2505dafe883 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards c1d69851206 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards 5b65896b44e 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards 64015d0dc2a 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards cbb43d36cfa 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards 22614ee11e7 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards ce75b2a183b 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards 051dd5e3a36 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards fce3267068d 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards a6219a56b74 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards ab52fe32c5e 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards 8b2b81cd674 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 06dc1fcc481 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards 2663595e16e 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards e07c3bc2bfb 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards 4906ae6a340 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards 6b6fa44af0b 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards 0aa2fb7ad9d 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards d44eb24f557 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards bc619a20956 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 5433fdc61e7 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards b76c8ad9732 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards 8f520848f10 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 78caa6228e8 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 8ebde80cf0e 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 349bd004bdf 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 54c8ba01985 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 19cd02866e4 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards a35b84a61e7 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 0c805a08450 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 444fbf48a89 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards e45b83f170f 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 860fe65dd60 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 60a558aea3d 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards a05f6cf5610 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 896aed9bbda 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 549309d4458 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards e74be90e5a5 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards e23bdc726a3 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards aec2af564ca 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 11ca4c3b4c7 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards a8c4c13884f 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards 56ff421ad70 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 3a44f0161ae 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards d3a603811aa 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 5e4f3ef0c73 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 6f43486b1f3 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 95099a9eb09 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 118459a6189 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 63903513700 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards bb768091813 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 6cc0d0095b7 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards a36e6ad46af 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 689d47bfbd5 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 8753f8c778a 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 615701c2141 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 5671b5e5d74 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 661e772f3ae 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 205a8838338 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 25106cb60fa 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards 32e437c5cf3 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 51a85d3aed1 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards d2da3e0b462 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards 83de2595818 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 22a47d12cd4 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new cade53577a7 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new 76355ca2b80 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new afc01a5b01b 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new a3e80ce3f49 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new df902dcd6e2 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 2ddb268ac6f 120: onsuccess: #906: 1: Success after binutils: 29 commits new 73b5da8069b 121: onsuccess: #908: 1: Success after glibc: 2 commits new abf49f44673 122: onsuccess: #909: 1: Success after linux: 2753 commits new 85ec7e4236e 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 30f832da262 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 82169dde470 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new ff48a6332a5 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new cd30544fd2c 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 2dc1de60b34 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new 5764bcbb781 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new a2f06de278f 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 55a9b670fe6 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 228577b307e 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 61ad241c838 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new eb8432b53ed 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new e19e90e1b58 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new af7f7440a44 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 690be2eb051 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new 6e84f35c0dc 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new fafe782c71c 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new ed8f21b6fdb 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 3c1c704fc5a 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 7adcdce2a41 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new d4b13c87f5d 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 2e2ebd917eb 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new ae91f9bdb7d 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new d17eb3d9426 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 73fac70e821 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 0bb3298d915 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 1401f628cfd 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new 2e9ba18105f 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 9f78f5f97f5 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 6dcbd252af5 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 440ca96b9eb 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 739e2b3ebfc 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 6670e1f7a12 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 2baebd3366b 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new 8ffb5614055 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new f87e2cfc7e6 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new b698ff1d522 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new ebf1bed6f87 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new e63a80b59a7 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new 676b6f69f76 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new 9767f2f672f 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new d4a7d1ad3c2 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 82314b40f99 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new 62ec148ed59 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new 634b2ea739e 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new 864111d0c08 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new 36575bf5ec9 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new e57e17dc9c2 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 1e6a126f686 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new 793a7a33c57 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new 34ccaf0c778 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new 107b68fa6bc 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new 05e015db8a2 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new ceca8e4d095 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new ae5d2bf3b86 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new 4fe1d664ed8 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new 3908c28994a 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new 1d9995defb2 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new b9cf47697e0 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new 9a3ded47ac0 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new 0583ad73333 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new 56886d4b072 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new b8f6d907682 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 7ab124697c5 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 27768347f89 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new a222430b63e 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new b21c6c7a2e5 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 9f58d783712 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new f8d68639201 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 5f43d80a534 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 1f07544583b 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 9e16e36e5f7 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 94f4ab9e978 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new cdd42bf3a92 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new cebaff9bad7 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new ee304813c8b 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 8b0c7566e8f 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 666ea3eb682 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 25a73719768 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 818e5235cf4 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 6d57b0bf7f6 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 8418e656d9b 204: force: #26: : Failure after baseline build: no new commits new 2815545b670 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 29b2264b6a2 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new b6dafcaeccf 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 39d4412a487 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new c48c466fede 209: force: #37: 1: Success after baseline build: no new commits new ffaac2e42c1 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] new 05891301e86 211: onsuccess: #44: 1: Success after linux: 26 commits new aa6ce71a295 212: force: #45: 1: Success after gdb: 22 commits new a6323b68c7f 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] new aa94305402a 214: onsuccess: #47: 1: Success after gdb: 21 commits new 18ef91f53b5 215: onsuccess: #48: 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 (676a2dfa36d) \ 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 -> 1964 bytes 02-prepare_abe/console.log.xz | Bin 2488 -> 2516 bytes 03-build_abe-binutils/console.log.xz | Bin 35468 -> 35124 bytes 04-build_abe-gcc/console.log.xz | Bin 203728 -> 203404 bytes 06-build_abe-linux/console.log.xz | Bin 8460 -> 8480 bytes 07-build_abe-glibc/console.log.xz | Bin 242400 -> 241456 bytes 08-build_abe-gdb/console.log.xz | Bin 35048 -> 34732 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3780 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3088 -> 2764 bytes 11-check_regression/console.log.xz | Bin 5072 -> 5216 bytes 11-check_regression/results.compare | 75 -------------------- 11-check_regression/results.compare2 | 129 ++++++---------------------------- 12-update_baseline/console.log | 42 +++++------ 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 | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 ++++---- sumfiles/gdb.log.0.xz | Bin 1949228 -> 1954392 bytes sumfiles/gdb.log.1.xz | Bin 21000 -> 20480 bytes sumfiles/gdb.log.2.xz | Bin 5420 -> 5412 bytes sumfiles/gdb.log.3.xz | Bin 5408 -> 5204 bytes sumfiles/gdb.sum | 16 ++--- sumfiles/gdb.sum.0 | 12 ++-- sumfiles/gdb.sum.1 | 25 ++++--- sumfiles/gdb.sum.2 | 4 +- sumfiles/gdb.sum.3 | 4 +- 31 files changed, 104 insertions(+), 249 deletions(-)