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_build/master-aarch64 in repository toolchain/ci/base-artifacts.
discards 3b16be8bd0 261: onsuccess: #49: 6: [TCWG CI] https://ci.linaro.org/job/ [...] discards 1a30d848e2 260: onsuccess: #48: 6: [TCWG CI] https://ci.linaro.org/job/ [...] discards 905a0b5953 259: onsuccess: #47: 6: [TCWG CI] Success after binutils/gcc [...] discards c2daaeb2b1 258: onsuccess: #46: 6: [TCWG CI] Success after binutils/gcc [...] discards 6ea933f48f 257: onsuccess: #45: 6: [TCWG CI] Success after binutils/gcc [...] discards 6f86b709b4 256: onsuccess: #44: 6: [TCWG CI] Success after binutils/gcc [...] discards d079bde67d 255: onsuccess: #42: 6: [TCWG CI] Success after binutils/gcc [...] discards e178f5cf88 254: onsuccess: #41: 6: [TCWG CI] Success after binutils/gcc [...] discards d0390d79dd 253: onsuccess: #40: 6: [TCWG CI] Success after binutils/gcc [...] discards 73de27d202 252: onsuccess: #39: 6: [TCWG CI] Success after binutils/gcc [...] discards c449a4298e 251: onsuccess: #38: 6: [TCWG CI] Success after binutils/gcc [...] discards 900789dbd5 250: onsuccess: #37: 6: [TCWG CI] Success after binutils/gcc [...] discards 61cbee0cb6 249: onsuccess: #36: 6: [TCWG CI] Success after binutils/gcc [...] discards 822ae7120c 248: onsuccess: #35: 6: [TCWG CI] Success after binutils/gcc [...] discards ebd3f3af5a 247: onsuccess: #34: 6: [TCWG CI] Success after binutils/gcc [...] discards 68c7a026a7 246: onsuccess: #32: 6: Success after binutils/gcc/linux/gli [...] discards 7a539e833e 245: onsuccess: #31: 6: Success after binutils/gcc/linux/gdb [...] discards cbf709eb9e 244: onsuccess: #30: 6: Success after binutils/gcc/linux/gdb [...] discards 0fa78a7957 243: onsuccess: #29: 6: Success after binutils/gcc/linux/gdb [...] discards e783c9a9f8 242: onsuccess: #28: 6: Success after binutils/gcc/linux/gdb [...] discards 2e2455d735 241: onsuccess: #27: 6: Success after binutils/gcc/linux/gli [...] discards d6c4ec1aec 240: onsuccess: #26: 6: Success after binutils/gcc/linux/gdb [...] discards 982ad192c7 239: onsuccess: #23: 6: Success after binutils/gcc/linux/gdb [...] discards 3c48bd286c 238: onsuccess: #22: 6: Success after binutils/gcc/linux/gdb [...] discards 3a5104fe35 237: onsuccess: #21: 6: Success after binutils/gcc/linux/gdb [...] discards abe2fae0c2 236: onsuccess: #20: 6: Success after binutils/gcc/linux/gli [...] discards 23ab7c6126 235: onsuccess: #19: 6: Success after binutils/gcc/linux/gli [...] discards ba7c504817 234: onsuccess: #18: 6: Success after binutils/gcc/linux/gli [...] discards 892db1b008 233: onsuccess: #17: 6: Success after binutils/gcc/linux/gdb [...] discards 9c7e26c3bf 232: onsuccess: #16: 6: Success after binutils/gcc/linux/gli [...] discards b2e9bcd438 231: onsuccess: #15: 6: Success after binutils/gcc/linux/gdb [...] discards 68dd347d00 230: onsuccess: #14: 6: Success after binutils/gcc/linux/gli [...] discards f3b76161f9 229: onsuccess: #13: 6: Success after binutils/gcc/linux/gli [...] discards dd97cc109c 228: onsuccess: #12: 6: Success after binutils/gcc/linux/gli [...] discards 2e3e28266a 227: onsuccess: #11: 6: Success after binutils/gcc/linux/gdb [...] discards d35d33ebc0 226: onsuccess: #10: 6: Success after binutils/gcc/linux/gdb [...] discards bdc60369b7 225: onsuccess: #9: 6: Success after binutils/gcc/linux/gdb: [...] discards 54bb149f91 224: onsuccess: #8: 6: Success after binutils/gcc/linux/glib [...] discards 1c3ca7a980 223: onsuccess: #7: 6: Success after binutils/gcc/linux/glib [...] discards 6a559b8b56 222: onsuccess: #6: 6: Success after binutils/gcc/linux/glib [...] discards b246116977 221: onsuccess: #5: 6: Success after binutils/gcc/linux/glib [...] discards f010e8787d 220: onsuccess: #4: 6: Success after binutils/gcc/linux/gdb: [...] discards 392c2472aa 219: onsuccess: #3: 6: Success after binutils/gcc/linux/glib [...] discards 98eb415424 218: onsuccess: #2: 6: Success after binutils/gcc/linux/gdb: [...] discards ce370795da 217: onsuccess: #1: 6: Success after binutils/gcc/glibc/gdb: [...] discards 6ab3e9d5d4 216: onsuccess: #642: 6: Success after binutils/gcc/linux/gl [...] discards a011d5a9c1 215: onsuccess: #641: 6: Success after binutils/gcc/linux/gl [...] discards 1870c79fa5 214: onsuccess: #640: 6: Success after binutils/gcc/linux/gl [...] discards bd1e9501a1 213: onsuccess: #639: 6: Success after binutils/gcc/linux/gl [...] discards 333ee3cd89 212: onsuccess: #638: 6: Success after binutils/gcc/linux/gd [...] discards 7d306dbd72 211: onsuccess: #637: 6: Success after binutils/gcc/linux/gl [...] discards aec082a95f 210: onsuccess: #636: 6: Success after binutils/gcc/linux/gl [...] discards 1c0197baa3 209: onsuccess: #635: 6: Success after binutils/gcc/gdb: 35 commits discards 4e98c22985 208: onsuccess: #634: 6: Success after binutils/gcc/linux/gl [...] discards ef99e8b163 207: onsuccess: #633: 6: Success after binutils/gcc/linux/gl [...] discards 66955b8d1c 206: onsuccess: #632: 6: Success after binutils/gcc/linux/gl [...] discards e8e28e2cd3 205: onsuccess: #631: 6: Success after binutils/gcc/linux/gl [...] discards 3124b6b4b1 204: onsuccess: #630: 6: Success after binutils/gcc/linux/gd [...] discards 35fa11be09 203: onsuccess: #629: 6: Success after binutils/gcc/linux/gl [...] discards d5b89a0471 202: onsuccess: #628: 6: Success after binutils/gcc/glibc/gd [...] discards 38e31bad72 201: onsuccess: #627: 6: Success after binutils/gcc/glibc/gd [...] discards a5355765cd 200: onsuccess: #626: 6: Success after binutils/gcc/linux/gl [...] discards 438a359c7d 199: onsuccess: #625: 6: Success after binutils/gcc/linux/gl [...] discards 66dcd26aa6 198: onsuccess: #624: 6: Success after binutils/gcc/linux/gl [...] discards 396c867ae5 197: onsuccess: #623: 6: Success after binutils/gcc/linux/gd [...] discards 7e93fcccd6 196: onsuccess: #622: 6: Success after binutils/gcc/linux/gl [...] discards f3c6d94d68 195: onsuccess: #621: 6: Success after binutils/gcc/linux/gl [...] discards 6cbbe7c798 194: onsuccess: #620: 6: Success after binutils/gcc/linux/gl [...] discards b9c513cac8 193: onsuccess: #619: 6: Success after binutils/gcc/linux/gl [...] discards a0fcc3254c 192: onsuccess: #618: 6: Success after binutils/gcc/linux/gl [...] discards 079d49d329 191: onsuccess: #617: 6: Success after binutils/gcc/linux/gd [...] discards 54db0dc622 190: onsuccess: #616: 6: Success after binutils/gcc/linux/gl [...] discards f0a03683e3 189: onsuccess: #615: 6: Success after binutils/gcc/gdb: 162 [...] discards 31ff1e0b0c 188: onsuccess: #614: 6: Success after binutils/gcc/linux/gd [...] discards 0598424e40 187: onsuccess: #613: 6: Success after binutils/gcc/linux/gl [...] discards 2e457065c4 186: onsuccess: #612: 6: Success after binutils/gcc/linux/gl [...] discards d8fd85f1dc 185: onsuccess: #611: 6: Success after binutils/gcc/linux/gd [...] discards bcbd414ebb 184: onsuccess: #610: 6: Success after binutils/gcc/linux/gd [...] discards 84f4c58d4b 183: onsuccess: #609: 6: Success after binutils/gcc/linux/gd [...] discards ee1d47225e 182: onsuccess: #608: 6: Success after binutils/gcc/linux/gl [...] discards 77ddc9e15b 181: onsuccess: #607: 6: Success after binutils/gcc/linux/gl [...] discards 6332c47fbf 180: onsuccess: #606: 6: Success after binutils/gcc/linux/gd [...] discards 39fa04324e 179: onsuccess: #605: 6: Success after binutils/gcc/linux/gl [...] discards 21276cd6ac 178: onsuccess: #604: 6: Success after binutils/gcc/linux/gl [...] discards cadd29f7c2 177: onsuccess: #603: 6: Success after binutils/gcc/linux/gl [...] discards 54bb032618 176: onsuccess: #601: 6: Success after binutils/gcc/linux/gd [...] discards e44167335c 175: onsuccess: #600: 6: Success after binutils/gcc/linux/gl [...] discards edfbddc63b 174: onsuccess: #599: 6: Success after binutils/gcc/linux/gl [...] discards 718674c1b6 173: onsuccess: #598: 6: Success after binutils/gcc/linux/gl [...] discards f47e78c9d6 172: onsuccess: #597: 6: Success after binutils/gcc/glibc/gd [...] discards 38ac489795 171: onsuccess: #596: 5: Success after gdb: 21 commits discards 80414a93cd 170: force: #595: 5: Failure after gdb-13-branchpoint-245-gd [...] discards 6d7f76c6e6 169: force: #594: 6: Success after gdb: 2 commits discards 89d4d9b63e 168: onsuccess: #593: 6: Success after linux: 10 commits discards 979b604c67 167: onsuccess: #592: 6: Success after glibc-2.36.9000-416-g [...] discards 77f2b013c9 166: onsuccess: #590: 6: Success after gcc: 23 commits discards b952d238b2 165: onsuccess: #589: 6: Success after binutils: 24 commits discards 129e588a6d 164: onsuccess: #587: 6: Success after binutils/gcc/linux/gl [...] discards 4066d5cbce 163: onsuccess: #586: 6: Success after binutils/gcc/linux/gd [...] discards ba9aaec55c 162: onsuccess: #585: 6: Success after binutils/gcc/linux/gd [...] discards 9e33422a92 161: onsuccess: #584: 6: Success after binutils/gcc/linux/gl [...] new 3eef4799a7 161: onsuccess: #584: 6: Success after binutils/gcc/linux/gl [...] new e91c4022d4 162: onsuccess: #585: 6: Success after binutils/gcc/linux/gd [...] new 167abe174f 163: onsuccess: #586: 6: Success after binutils/gcc/linux/gd [...] new aea6048fd6 164: onsuccess: #587: 6: Success after binutils/gcc/linux/gl [...] new c22b70c8ed 165: onsuccess: #589: 6: Success after binutils: 24 commits new 439b4b9373 166: onsuccess: #590: 6: Success after gcc: 23 commits new c362759d85 167: onsuccess: #592: 6: Success after glibc-2.36.9000-416-g [...] new 1fad5aa6a7 168: onsuccess: #593: 6: Success after linux: 10 commits new 3cd5bb2481 169: force: #594: 6: Success after gdb: 2 commits new be9fb640ef 170: force: #595: 5: Failure after gdb-13-branchpoint-245-gd [...] new c1d00ccbe7 171: onsuccess: #596: 5: Success after gdb: 21 commits new 27f938d128 172: onsuccess: #597: 6: Success after binutils/gcc/glibc/gd [...] new 6a8f409530 173: onsuccess: #598: 6: Success after binutils/gcc/linux/gl [...] new 49bd0c7d97 174: onsuccess: #599: 6: Success after binutils/gcc/linux/gl [...] new 32bddf1b43 175: onsuccess: #600: 6: Success after binutils/gcc/linux/gl [...] new 07239cde04 176: onsuccess: #601: 6: Success after binutils/gcc/linux/gd [...] new 7e9404a0a6 177: onsuccess: #603: 6: Success after binutils/gcc/linux/gl [...] new 4b00502181 178: onsuccess: #604: 6: Success after binutils/gcc/linux/gl [...] new bf9a67a908 179: onsuccess: #605: 6: Success after binutils/gcc/linux/gl [...] new 5e7eb9a78a 180: onsuccess: #606: 6: Success after binutils/gcc/linux/gd [...] new be71a60151 181: onsuccess: #607: 6: Success after binutils/gcc/linux/gl [...] new 803bb0f8e4 182: onsuccess: #608: 6: Success after binutils/gcc/linux/gl [...] new a4bcb0e9f2 183: onsuccess: #609: 6: Success after binutils/gcc/linux/gd [...] new f7c7f988f8 184: onsuccess: #610: 6: Success after binutils/gcc/linux/gd [...] new f1bbadd34d 185: onsuccess: #611: 6: Success after binutils/gcc/linux/gd [...] new 79567638ff 186: onsuccess: #612: 6: Success after binutils/gcc/linux/gl [...] new d9890e3246 187: onsuccess: #613: 6: Success after binutils/gcc/linux/gl [...] new 6b8589c98f 188: onsuccess: #614: 6: Success after binutils/gcc/linux/gd [...] new 1b07b5ee30 189: onsuccess: #615: 6: Success after binutils/gcc/gdb: 162 [...] new 11edc2b8ef 190: onsuccess: #616: 6: Success after binutils/gcc/linux/gl [...] new 41312b75d4 191: onsuccess: #617: 6: Success after binutils/gcc/linux/gd [...] new e7132fa4d6 192: onsuccess: #618: 6: Success after binutils/gcc/linux/gl [...] new c4c97cf0d8 193: onsuccess: #619: 6: Success after binutils/gcc/linux/gl [...] new 5b98110ad6 194: onsuccess: #620: 6: Success after binutils/gcc/linux/gl [...] new 17df95bed0 195: onsuccess: #621: 6: Success after binutils/gcc/linux/gl [...] new 2dee555fb6 196: onsuccess: #622: 6: Success after binutils/gcc/linux/gl [...] new 06d6438336 197: onsuccess: #623: 6: Success after binutils/gcc/linux/gd [...] new 64b389d37d 198: onsuccess: #624: 6: Success after binutils/gcc/linux/gl [...] new 1688d748c7 199: onsuccess: #625: 6: Success after binutils/gcc/linux/gl [...] new f765cbcddf 200: onsuccess: #626: 6: Success after binutils/gcc/linux/gl [...] new 4aadb7f719 201: onsuccess: #627: 6: Success after binutils/gcc/glibc/gd [...] new f7b98a7116 202: onsuccess: #628: 6: Success after binutils/gcc/glibc/gd [...] new c71fb02c18 203: onsuccess: #629: 6: Success after binutils/gcc/linux/gl [...] new 6c59bab141 204: onsuccess: #630: 6: Success after binutils/gcc/linux/gd [...] new 4c0e75d3ed 205: onsuccess: #631: 6: Success after binutils/gcc/linux/gl [...] new f43789c228 206: onsuccess: #632: 6: Success after binutils/gcc/linux/gl [...] new 352002bc42 207: onsuccess: #633: 6: Success after binutils/gcc/linux/gl [...] new 198bb01c20 208: onsuccess: #634: 6: Success after binutils/gcc/linux/gl [...] new 7637b05318 209: onsuccess: #635: 6: Success after binutils/gcc/gdb: 35 commits new b8cd1eaab6 210: onsuccess: #636: 6: Success after binutils/gcc/linux/gl [...] new 1c807851d1 211: onsuccess: #637: 6: Success after binutils/gcc/linux/gl [...] new 3a95347ef6 212: onsuccess: #638: 6: Success after binutils/gcc/linux/gd [...] new c5c4cf36f2 213: onsuccess: #639: 6: Success after binutils/gcc/linux/gl [...] new 29662699cd 214: onsuccess: #640: 6: Success after binutils/gcc/linux/gl [...] new 97bebba4d1 215: onsuccess: #641: 6: Success after binutils/gcc/linux/gl [...] new ae49589ad8 216: onsuccess: #642: 6: Success after binutils/gcc/linux/gl [...] new f160e0c592 217: onsuccess: #1: 6: Success after binutils/gcc/glibc/gdb: [...] new 4774962e4f 218: onsuccess: #2: 6: Success after binutils/gcc/linux/gdb: [...] new 0d22b261d2 219: onsuccess: #3: 6: Success after binutils/gcc/linux/glib [...] new 52c5417851 220: onsuccess: #4: 6: Success after binutils/gcc/linux/gdb: [...] new 924115387c 221: onsuccess: #5: 6: Success after binutils/gcc/linux/glib [...] new 7f620e96e2 222: onsuccess: #6: 6: Success after binutils/gcc/linux/glib [...] new c14dc7ff9e 223: onsuccess: #7: 6: Success after binutils/gcc/linux/glib [...] new e4b884d177 224: onsuccess: #8: 6: Success after binutils/gcc/linux/glib [...] new c5ae3776c3 225: onsuccess: #9: 6: Success after binutils/gcc/linux/gdb: [...] new 91eeb509cb 226: onsuccess: #10: 6: Success after binutils/gcc/linux/gdb [...] new bf94ac5a0b 227: onsuccess: #11: 6: Success after binutils/gcc/linux/gdb [...] new 35f74c29af 228: onsuccess: #12: 6: Success after binutils/gcc/linux/gli [...] new fbe0d66cca 229: onsuccess: #13: 6: Success after binutils/gcc/linux/gli [...] new c9836f1dea 230: onsuccess: #14: 6: Success after binutils/gcc/linux/gli [...] new c9e5b6512b 231: onsuccess: #15: 6: Success after binutils/gcc/linux/gdb [...] new 33b0c51d88 232: onsuccess: #16: 6: Success after binutils/gcc/linux/gli [...] new 794526a561 233: onsuccess: #17: 6: Success after binutils/gcc/linux/gdb [...] new 8fba562aea 234: onsuccess: #18: 6: Success after binutils/gcc/linux/gli [...] new f36df265c9 235: onsuccess: #19: 6: Success after binutils/gcc/linux/gli [...] new 7e594550f0 236: onsuccess: #20: 6: Success after binutils/gcc/linux/gli [...] new 24d743c9a4 237: onsuccess: #21: 6: Success after binutils/gcc/linux/gdb [...] new 814b5db5be 238: onsuccess: #22: 6: Success after binutils/gcc/linux/gdb [...] new 6063ba0a5c 239: onsuccess: #23: 6: Success after binutils/gcc/linux/gdb [...] new 4b04ded8cc 240: onsuccess: #26: 6: Success after binutils/gcc/linux/gdb [...] new eda1d78eff 241: onsuccess: #27: 6: Success after binutils/gcc/linux/gli [...] new 678088e3c7 242: onsuccess: #28: 6: Success after binutils/gcc/linux/gdb [...] new 69946abea7 243: onsuccess: #29: 6: Success after binutils/gcc/linux/gdb [...] new 2efee383c2 244: onsuccess: #30: 6: Success after binutils/gcc/linux/gdb [...] new d4ab7aab8a 245: onsuccess: #31: 6: Success after binutils/gcc/linux/gdb [...] new 7c48fe2a70 246: onsuccess: #32: 6: Success after binutils/gcc/linux/gli [...] new 40820c47f4 247: onsuccess: #34: 6: [TCWG CI] Success after binutils/gcc [...] new 10c454c176 248: onsuccess: #35: 6: [TCWG CI] Success after binutils/gcc [...] new a50cced3a5 249: onsuccess: #36: 6: [TCWG CI] Success after binutils/gcc [...] new 69ec191dae 250: onsuccess: #37: 6: [TCWG CI] Success after binutils/gcc [...] new 13b74d84d5 251: onsuccess: #38: 6: [TCWG CI] Success after binutils/gcc [...] new 05ad788408 252: onsuccess: #39: 6: [TCWG CI] Success after binutils/gcc [...] new 64ed33a816 253: onsuccess: #40: 6: [TCWG CI] Success after binutils/gcc [...] new b638a40111 254: onsuccess: #41: 6: [TCWG CI] Success after binutils/gcc [...] new 2d72857080 255: onsuccess: #42: 6: [TCWG CI] Success after binutils/gcc [...] new b5bce261f1 256: onsuccess: #44: 6: [TCWG CI] Success after binutils/gcc [...] new 239f5bdfce 257: onsuccess: #45: 6: [TCWG CI] Success after binutils/gcc [...] new 992f14b111 258: onsuccess: #46: 6: [TCWG CI] Success after binutils/gcc [...] new 14097dbf4d 259: onsuccess: #47: 6: [TCWG CI] Success after binutils/gcc [...] new d92e3499dd 260: onsuccess: #48: 6: [TCWG CI] https://ci.linaro.org/job/ [...] new 92d2f6338e 261: onsuccess: #49: 6: [TCWG CI] https://ci.linaro.org/job/ [...] new 5afd99339f 262: onsuccess: #50: 6: [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 (3b16be8bd0) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...]
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 2240 -> 2048 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2528 bytes 04-build_abe-binutils/console.log.xz | Bin 35424 -> 34992 bytes 05-build_abe-gcc/console.log.xz | Bin 204112 -> 203616 bytes 06-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 07-build_abe-linux/console.log.xz | Bin 8596 -> 8820 bytes 08-build_abe-glibc/console.log.xz | Bin 242504 -> 241272 bytes 09-build_abe-gdb/console.log.xz | Bin 35344 -> 34732 bytes 10-check_regression/console.log.xz | Bin 1292 -> 552 bytes 11-update_baseline/console.log | 40 ++++++++++----------- 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 +- manifest.sh | 36 +++++++++---------- 21 files changed, 43 insertions(+), 77 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