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 6388e0c5aae 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards c999792675f 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gc [...] discards df32780e922 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards 88b72cb9aae 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 91ca8f2b51a 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 65de60968e9 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gc [...] discards 5578ad45a4d 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gd [...] discards e2708b26e9d 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gd [...] discards 6b54ce1a86d 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] discards e8d4d81a3c9 214: onsuccess: #47: 1: Success after gdb: 21 commits discards cb9c109599c 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] discards 2d838742c6b 212: force: #45: 1: Success after gdb: 22 commits discards 75d0829fc9e 211: onsuccess: #44: 1: Success after linux: 26 commits discards 1827794688c 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] discards 18ea8d1b585 209: force: #37: 1: Success after baseline build: no new commits discards 76cb9fb01cb 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 5404e4d4a09 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 014c1bd8187 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 2bb98b55976 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards da76051cd9b 204: force: #26: : Failure after baseline build: no new commits discards 3bae10b4700 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 30c452da42a 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 9ce1fba9c58 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards ef060d7ec15 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 68f9b1ff6d4 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 36ffce81149 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards c1b32b801c7 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 3afe416f1ea 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 2632b1085e2 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards e5c365f27d2 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards d76c884872b 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 51860b11339 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 26894c4338d 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards c180c6bbffa 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 536de598137 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 02058ee3109 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 96bf84c3df2 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 361713ebcfa 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 9dedf53f97f 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 5d49b39271f 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards c1dd5a7e8a8 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards 76381f31236 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards d608be08545 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards cd6a527034f 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 1865633703d 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards 1642c0525fc 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards 935dd44e741 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards 8071ccf0648 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards b4aa12c71b5 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards d46e656998e 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards cd2f5eba390 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards 5d322972060 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards 2d32a79d985 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards 59dee1f1414 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards dc7c438aff8 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 3db686c4c07 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards b60b11ffc5a 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards 6a656038ea7 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 77834eb7be2 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards 64372121e27 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards d6876f47944 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards 5828f782e98 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards b87372fedbc 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards a30a27718b4 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards 9363c90ce42 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards dd6d4254a46 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 990d2eb0557 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards 19602a3ee77 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards 7ab2bd7d991 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 2e99307c977 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 8e1d0180e1c 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 7a61a73e1fa 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards f815fef2f99 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards f873baa7efa 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards f3f21b4a294 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 4acb9eb139c 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 3fc396a3200 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 3ef0550c46b 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 2041998b24f 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 9e90be19fac 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards 4d3a6043ee0 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards a105a932acd 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 67eaad2d9f9 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 2dfa34c62e5 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards efd2143d3ab 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards ccba7224430 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards df51a4bad76 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards 41bd8be60a4 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards f3a80a3d47c 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards de893a1f8bf 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards b331eb386de 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 42012cc2a05 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards dbf685832c9 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 22b17bfe686 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 92ac5cea3ca 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards ab97caf08ac 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards 7e1b4cff0bb 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 63c3d883887 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 382511af343 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 88680d51b69 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards f65201139d5 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 304afdf8ceb 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new c5531cbd080 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new db1dff6ef81 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 99eb12e2d03 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 0a05930b298 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new e1da4118602 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new e203a3df43b 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 1c2de501d45 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 56c50e9b317 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 0a461a643c0 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 8d517581ca4 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 6438ce93586 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new e1c98383501 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 5307cc11336 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new c8dd93a373f 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new e3e7b6514d4 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new 2732758323a 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 6c27d1af472 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new b8552253c0d 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 55084a26692 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 5c31e397ac2 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 510e0432a6c 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new 8cbaab647ce 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 7a99e2c6c49 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new faf3c15dfe6 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 78bb1fe6b8b 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 509677183af 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new be95e7833e0 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 501fe02912f 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 9593b24ca44 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new c2c913cd548 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new a53f386f17a 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 3983443aa2d 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 82bbc9a7ce2 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new 073d8ff8444 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new 3c87b295faa 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 991276d5a18 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new 7928865c771 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new ab2ebc8aae0 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new 8ff2d852700 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new 643944e0dde 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new 26786600f84 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 848d807a3a2 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new fc22c65a979 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new 8faf53a6f94 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new f2730a497a9 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new 0774fe7974b 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new 007a917304e 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 3571bf2654e 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new 4e7c4d34d7b 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new fb29b4d4ae9 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new cfb0771a892 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new fe3012bc317 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new 813703d2c88 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new b7e38c90736 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new b4a9f74d594 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new d103bbf5d45 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new a80d370a975 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new 5eeb0c7973a 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new 6ab4edd3baa 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new f0ad0134b36 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new 02c55604b59 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new 193576eab60 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 337922441a7 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 72ed0ae18e5 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 17ef32bfb00 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 206af9626ee 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 1d34d41f2f2 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new a5fd309f6eb 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new b3ad9a8be5b 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 686cf61de61 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 8ac3c5ea811 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 2ccd2f618f1 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new addb7eae209 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 513a62fecc0 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new c852eee4b1f 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 1a9e5fb85d8 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new bc45b7e5e45 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new b98e06e5a98 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 01c22d784f3 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 2fecd0f3e0b 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 1af3329522b 204: force: #26: : Failure after baseline build: no new commits new 4ee8cfae04f 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new d4727d5b8e4 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 1e1d0b3e39f 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new c84c9fe6eed 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 0cfb9596b82 209: force: #37: 1: Success after baseline build: no new commits new b6c36ad7792 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] new a489fb61436 211: onsuccess: #44: 1: Success after linux: 26 commits new f3aa22dc42f 212: force: #45: 1: Success after gdb: 22 commits new 280a75082eb 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] new a5547408285 214: onsuccess: #47: 1: Success after gdb: 21 commits new cac97fcc347 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] new b9ffde472f1 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gd [...] new 35e4bd400e6 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gd [...] new 3b949bc51e7 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gc [...] new ca64d518fa4 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 194ab4dcbf9 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 656dd1a176e 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new b44113fc839 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gc [...] new eff65e3f610 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new 6606a555c5b 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpo [...]
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 (6388e0c5aae) \ 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 2052 -> 2000 bytes 02-prepare_abe/console.log.xz | Bin 2520 -> 2532 bytes 03-build_abe-binutils/console.log.xz | Bin 35736 -> 36316 bytes 04-build_abe-gcc/console.log.xz | Bin 203336 -> 203836 bytes 06-build_abe-linux/console.log.xz | Bin 8592 -> 8624 bytes 07-build_abe-glibc/console.log.xz | Bin 241532 -> 241368 bytes 08-build_abe-gdb/console.log.xz | Bin 34808 -> 34764 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3840 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2700 -> 2712 bytes 11-check_regression/console.log.xz | Bin 3140 -> 3744 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 16 +++++ 11-check_regression/results.compare | 19 +++++- 11-check_regression/results.regressions | 24 +++++++ 11-check_regression/trigger-bisect | 3 + 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 68 ++++++++++---------- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- jenkins/notify.sh | 3 + mail/changes-list-long.txt | 11 ++-- mail/changes-list-short.txt | 2 +- mail/short-diag.txt | 2 +- manifest.sh | 20 +++--- results | 24 +++++++ sumfiles/gdb.log.0.xz | Bin 2000712 -> 1992972 bytes sumfiles/gdb.log.1.xz | Bin 28568 -> 30556 bytes sumfiles/gdb.log.2.xz | Bin 0 -> 14680 bytes sumfiles/gdb.log.3.xz | Bin 0 -> 15460 bytes sumfiles/gdb.sum | 45 +++++++------ sumfiles/gdb.sum.0 | 49 +++++++------- sumfiles/gdb.sum.1 | 54 ++++++++++++---- sumfiles/gdb.sum.2 | 110 ++++++++++++++++++++++++++++++++ sumfiles/gdb.sum.3 | 110 ++++++++++++++++++++++++++++++++ 34 files changed, 450 insertions(+), 115 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions create mode 100644 11-check_regression/trigger-bisect create mode 100644 11-check_regression/trigger-notify create mode 100755 jenkins/notify.sh create mode 100644 sumfiles/gdb.log.2.xz create mode 100644 sumfiles/gdb.log.3.xz create mode 100644 sumfiles/gdb.sum.2 create mode 100644 sumfiles/gdb.sum.3