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 a2f3bd40905 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] discards a3e8a6f471e 212: force: #45: 1: Success after gdb: 22 commits discards 2759eaded92 211: onsuccess: #44: 1: Success after linux: 26 commits discards 96a39158866 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] discards 1cb48d12dcc 209: force: #37: 1: Success after baseline build: no new commits discards d17f0713e2f 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 2f4a5b6b447 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards a3a817bc542 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards ee8112c6c38 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 7bd7d1b51b6 204: force: #26: : Failure after baseline build: no new commits discards 7475a2e9c58 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 3acff44fd78 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 716eca7f7aa 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 9ac1adbc5e7 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards f03f1b33f3b 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 4410098315a 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 1362e518391 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 2b36dd67c1f 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 45c578b320c 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards ef9698e21ec 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 40fab490442 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 1de2d1ffb42 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 7a467e2bc5b 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 62a432d88f8 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 1a9e72d08cd 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 26b57efd98e 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 34985f333f4 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 8c8c7ab89e0 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 93d6e8bcfc3 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 1fd18f13fd9 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards 6c66a848189 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards fc9759600a3 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards cddf244cf16 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards d9c50fd1c8f 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 3f37dc8c2ec 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards b3e82d8c852 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards 76a9409d7c4 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards 7ec203e7dc4 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards 0ed3d68d64b 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards 00baf16a4dc 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards 22d49a7da5f 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards cb4e3c5a7b8 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards 2ef3b29caac 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards 2bb92bb00e6 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards 1d1b5162480 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards ba0af039e1b 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards 12ed260f714 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards a5a051e76a3 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards ba00f41df80 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards 09fb6a4cef8 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards d2ed598f347 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards a1e18d53bfe 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards 1fa7afb8994 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards 1e64e7380c6 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards f653051962f 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 155c8647dae 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 5037db2e97c 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards 31b91904e13 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards dbd05306ff5 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 3fc474b2656 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 23d8944bdef 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards ff429a861d0 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 11b15f7b847 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 8abd35a9d7d 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards bb1123679f5 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 91a01282c78 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 39d3862daea 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 634d717b446 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards f57c6578fab 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 826e6e2c7a1 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards b822ea73963 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 2b06475c36a 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards d758021033e 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 38bf28fd398 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards e3fb1ac0bee 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 522c9b5c6c0 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 0e5d737c878 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards 4507c013a1a 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards 60e7291aa64 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards f673c4d0653 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards 46d9298ef3e 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards e6475d546a8 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 6f9d1482d55 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards c883400d928 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 94d7d2dc0ac 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards bdfdad5db34 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards 580fda299e7 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 7f03f374dc9 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 47c52bc6b91 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 571862398bf 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 256fafec951 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 19bbcb285ca 122: onsuccess: #909: 1: Success after linux: 2753 commits discards a7eefa4fd45 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 7762b129ae7 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 585c6002f06 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 6eae1cedcb2 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards d34ae3a039d 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 43df5d1cdc7 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards 809564829b1 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards b4dc6b81f2e 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards 748c3e40c82 113: onsuccess: #898: 1: Success after linux: 3 commits new 4792edeed1f 113: onsuccess: #898: 1: Success after linux: 3 commits new 83de2595818 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new d2da3e0b462 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new 51a85d3aed1 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new 32e437c5cf3 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new 25106cb60fa 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new 205a8838338 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 661e772f3ae 120: onsuccess: #906: 1: Success after binutils: 29 commits new 5671b5e5d74 121: onsuccess: #908: 1: Success after glibc: 2 commits new 615701c2141 122: onsuccess: #909: 1: Success after linux: 2753 commits new 8753f8c778a 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 689d47bfbd5 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new a36e6ad46af 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 6cc0d0095b7 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new bb768091813 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 63903513700 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new 118459a6189 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 95099a9eb09 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 6f43486b1f3 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 5e4f3ef0c73 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new d3a603811aa 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 3a44f0161ae 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new 56ff421ad70 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new a8c4c13884f 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 11ca4c3b4c7 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new aec2af564ca 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new e23bdc726a3 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new e74be90e5a5 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 549309d4458 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 896aed9bbda 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new a05f6cf5610 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 60a558aea3d 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new 860fe65dd60 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new e45b83f170f 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 444fbf48a89 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 0c805a08450 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new a35b84a61e7 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new 19cd02866e4 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 54c8ba01985 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 349bd004bdf 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 8ebde80cf0e 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 78caa6228e8 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 8f520848f10 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new b76c8ad9732 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new 5433fdc61e7 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new bc619a20956 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new d44eb24f557 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new 0aa2fb7ad9d 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new 6b6fa44af0b 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new 4906ae6a340 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new e07c3bc2bfb 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new 2663595e16e 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 06dc1fcc481 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new 8b2b81cd674 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new ab52fe32c5e 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new a6219a56b74 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new fce3267068d 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new 051dd5e3a36 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new ce75b2a183b 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new 22614ee11e7 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new cbb43d36cfa 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new 64015d0dc2a 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new 5b65896b44e 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new c1d69851206 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new 2505dafe883 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new 3d87b2db340 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new 5ce72244020 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new 29f71c22964 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new ee67736bb8d 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new 43ee6fcc89e 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new 47b1992225a 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new f0da3e7328f 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new 30dbb9aee64 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new ad17c45f65c 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 1f68f408ab1 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 262cc6b7eec 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new fcd8a4b2917 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 6e3daaf7b70 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 26902ec3a71 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 0a4a8bc03fd 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 2dbd39bb04f 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 74c053a8bee 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 476188ef4de 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 79ab5101e64 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 84d926d61ec 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new f056c7f47e1 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 694230570eb 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 946278acd1d 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 019b521e02b 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 9e71045f64c 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new f3745e43e27 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new e499f7417dd 204: force: #26: : Failure after baseline build: no new commits new 7fff02c3986 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new cbea1943e07 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 22e65d17e09 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 7be32c24106 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 701f90ab597 209: force: #37: 1: Success after baseline build: no new commits new 6962c12b82c 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] new 539c73cb306 211: onsuccess: #44: 1: Success after linux: 26 commits new 721070651a2 212: force: #45: 1: Success after gdb: 22 commits new 33718ff48c5 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] new 676a2dfa36d 214: onsuccess: #47: 1: Success after gdb: 21 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 (a2f3bd40905) \ 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 2072 -> 2088 bytes 02-prepare_abe/console.log.xz | Bin 2516 -> 2488 bytes 03-build_abe-binutils/console.log.xz | Bin 35248 -> 35468 bytes 04-build_abe-gcc/console.log.xz | Bin 203300 -> 203728 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8460 -> 8460 bytes 07-build_abe-glibc/console.log.xz | Bin 242420 -> 242400 bytes 08-build_abe-gdb/console.log.xz | Bin 34728 -> 35048 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3784 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2720 -> 3088 bytes 11-check_regression/console.log.xz | Bin 3048 -> 5072 bytes 11-check_regression/results.compare | 79 +++++++++++++- 11-check_regression/results.compare2 | 158 +++++++++++++++++++++++++++- 12-update_baseline/console.log | 40 ++++---- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +-- sumfiles/gdb.log.0.xz | Bin 1952768 -> 1949228 bytes sumfiles/gdb.log.1.xz | Bin 25384 -> 21000 bytes sumfiles/gdb.log.2.xz | Bin 5204 -> 5420 bytes sumfiles/gdb.log.3.xz | Bin 5428 -> 5408 bytes sumfiles/gdb.sum | 122 +++++++++++----------- sumfiles/gdb.sum.0 | 116 ++++++++++----------- sumfiles/gdb.sum.1 | 187 ++-------------------------------- sumfiles/gdb.sum.2 | 4 +- sumfiles/gdb.sum.3 | 4 +- 29 files changed, 399 insertions(+), 337 deletions(-)