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 71dce953a1 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...] discards d0fa11c62f 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 913fd70b67 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] discards 121a658acc 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits discards c40eb7c0be 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] discards 1c53b72eca 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] discards ef6351ddbe 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits discards ac2a3dfcf8 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] discards e938daeb78 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] discards de7382c03c 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits discards c8bb893b7b 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards afffca23ed 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards 8df3013bd6 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 37d72ab8e0 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 454ec2df48 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards 2cc306bddf 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 304e14c564 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards 9025365e97 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards 766d4ba558 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards 94501c6a53 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards 61cdc08743 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards 57e975e888 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards f8aec8734b 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards f9a0e2c643 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 843ddc877a 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 867f76587d 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards e6ccc2f06a 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards b7a2ffdd27 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards aedaed592a 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards d58d30878e 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards f1dd114bd0 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards e2fe78a287 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards 87b300546d 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards fe22a92347 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 914b83d553 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards 8d2d952151 212: force: #45: 1: Success after gdb: 22 commits discards cd99a44378 211: onsuccess: #44: 1: Success after linux: 26 commits discards bc2ca4eaa9 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards d8ef35c544 209: force: #37: 1: Success after baseline build: no new commits discards e7dd845da5 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 6f47c9fdf6 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards e01d122cd1 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 17e214a6ed 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 9dd4eff377 204: force: #26: : Failure after baseline build: no new commits discards d469c1d4c8 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 2da9e7c19e 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards be04207b1a 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards f2e4f34896 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 83d9f99334 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 3be61f3109 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards d5bab3208b 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards ea23fe3523 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 93acf8f14f 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 7e58c85c64 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards f0f489a7bc 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 2737de99ba 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 2a71618f97 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 1b844954e0 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 82ee2c61f6 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 6e45b1d258 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 06f8727f47 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 351bef0649 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards e77e5217e1 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 73a743d3a1 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards 86bb1108a0 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards 4c5f971385 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards 09e4ebab09 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards f2eca30c44 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards 3f86772dea 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards 1b447647bb 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards bb6373d8f4 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards 7ddab638d9 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards 325f9415a9 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards bc2bfc160d 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards 8d72b17dfc 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards 03779142f0 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards b6289274a2 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards 8df902743a 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards cf57201f6b 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards ae4305687e 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards bd702424aa 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards be698e8954 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards dff9fa21e8 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards d3bd158b14 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards 4bbc05dca6 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards 00107a9482 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards 2547da0637 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards fdd02ab0b6 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards 163cc9182f 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards 0ab616cbeb 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 46f74c707e 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards d684797635 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards f083a7c15f 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards 1d853451a6 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards 5ae3635671 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards 97af7b1de8 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards 79143a31c3 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards c4cbcfa190 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards 96a5dab84b 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards 45396470af 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards 6f0bd7ea36 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new e7ab8eb649 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new 7d42b979da 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new 7263a02746 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new 2db3b5320e 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new a3c4bbe738 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new 75dd9b92f1 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 7cb90b7e55 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new 4514492811 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 3a3af9d58e 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new 0ebdd9c642 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new 45fa885f18 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new 00b6e66ddc 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 0757d8ffec 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new ec9a1cbf97 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new 8050513ec2 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new 17b795517c 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new e5700fec50 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new a4faff61a6 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new 2438c9e615 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new f87c54f70c 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new 144ded2ad4 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new 95a206f2dc 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new 5b649e0235 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new 585df6bc7d 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new 6a74d72126 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new f8fe1e20e5 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new 0b6d7a5ae5 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new 3ddd32976a 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new c1f82637fe 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new c6f862fa4c 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new 5a61616896 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new ab504adf2e 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new e8db73d042 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new e194c8a13e 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new ef7016e515 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new 56d628c018 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new ad7b765bd3 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new 22dce6564d 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new f01dcfdb5f 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 49f26cdd19 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 49c4d84ac3 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new b8e336ed49 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 67a1d2743e 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 0e88cbdd4c 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new c09b77536e 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 49088e362e 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 76c46b3d67 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 1ebeb6bac1 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 11d2c57125 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new b7322112e6 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 82f6877925 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new f9b87308fc 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 1cb2408d59 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 315772aecf 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 636568f2ff 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 1fe4b30b05 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 9b2ee76912 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 0ddfb18165 204: force: #26: : Failure after baseline build: no new commits new f087968685 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new c5a12aade8 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new d493c00a1a 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 6761563119 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new ab6e4b7136 209: force: #37: 1: Success after baseline build: no new commits new 831e1256c3 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new e245c3be23 211: onsuccess: #44: 1: Success after linux: 26 commits new 2a943eac29 212: force: #45: 1: Success after gdb: 22 commits new 93fbaddbb0 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new 58c448154b 214: onsuccess: #47: 1: Success after gdb: 21 commits new 8d99932fa3 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new 65876d3d82 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new 841901459e 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new 89599d7498 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new 7d4d2cd5fd 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 52fc0926ff 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new dc9a2138cd 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new e4ecc7e76a 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new fd06c954fd 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new 4fd74b1e3f 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new ffae145758 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new 48f49c0dd8 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new ac67247ed2 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new 2410823a26 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new fed2349361 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new 972e0c2ad2 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new 20950c3cfe 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new a12132f1a7 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new 1d46dfda13 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new 3776c42d72 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 43eab87efb 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new d57da848f9 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new c899f45b6b 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new 984367cae7 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits new f7402faa34 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] new e3c851761a 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] new 9b4ab62035 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits new 47ae3312a9 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] new 0f03e2ae2e 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] new 0bef3524cf 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits new fa6f75cd5d 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] new 19b78bac13 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new 4298fb8f02 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...] new ce8d05910c 248: onsuccess: #123: 1: [TCWG CI] https://ci.linaro.org/job [...]
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 (71dce953a1) \ 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 -> 2252 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2600 bytes 03-build_abe-binutils/console.log.xz | Bin 34836 -> 35156 bytes 04-build_abe-gcc/console.log.xz | Bin 203144 -> 203064 bytes 06-build_abe-linux/console.log.xz | Bin 8580 -> 8600 bytes 07-build_abe-glibc/console.log.xz | Bin 240772 -> 240760 bytes 08-build_abe-gdb/console.log.xz | Bin 34672 -> 34884 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3848 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2748 -> 2856 bytes 11-check_regression/console.log.xz | Bin 2388 -> 1776 bytes 11-check_regression/results.compare2 | 59 ++++++++++++--------- 12-update_baseline/console.log | 48 ++++++++--------- dashboard/dashboard-generate.sh | 17 ------ dashboard/dashboard-push.sh | 7 --- .../squad-vs-first/score/results-functional.json | 1 - git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/dashboard-push.sh | 7 --- jenkins/notify.sh | 2 +- {11-check_regression => mail}/results.compare | 0 manifest.sh | 36 ++++++------- sumfiles/gdb.log.0.xz | Bin 1926688 -> 1936368 bytes sumfiles/gdb.log.1.xz | Bin 20320 -> 20316 bytes sumfiles/gdb.log.2.xz | Bin 5400 -> 5276 bytes sumfiles/gdb.log.3.xz | Bin 5248 -> 5400 bytes sumfiles/gdb.sum | 18 +++---- sumfiles/gdb.sum.0 | 10 ++-- sumfiles/gdb.sum.1 | 4 +- sumfiles/gdb.sum.2 | 25 +++------ sumfiles/gdb.sum.3 | 4 +- 33 files changed, 108 insertions(+), 140 deletions(-) delete mode 100755 dashboard/dashboard-generate.sh delete mode 100755 dashboard/dashboard-push.sh delete mode 100644 dashboard/squad-vs-first/score/results-functional.json delete mode 100755 jenkins/dashboard-push.sh copy {11-check_regression => mail}/results.compare (100%)