This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allyesconfig in repository toolchain/ci/base-artifacts.
discards 70c4db01af 102: force: #41: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards b360d7ab78 101: onsuccess: #39: all: [TCWG CI] https://ci.linaro.org/jo [...] discards 812086ad77 100: force: #35: all: [TCWG CI] https://ci.linaro.org/job/tc [...] discards 248f3ec3eb 99: force: #32: all: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 359b661836 98: force: #30: all: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 9f48ec8d35 97: force: #28: all: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 9f0fd83e81 96: onsuccess: #26: all: [TCWG CI] https://ci.linaro.org/job [...] discards 1d368a728f 95: onsuccess: #23: all: [TCWG CI] https://ci.linaro.org/job [...] discards e1ac720cfe 94: onsuccess: #21: all: [TCWG CI] https://ci.linaro.org/job [...] discards 2696a2093b 93: onsuccess: #20: all: [TCWG CI] Success after binutils/ll [...] discards a9a84d3a5e 92: onsuccess: #19: all: [TCWG CI] Success after binutils/ll [...] discards 83ff12ffe4 91: onsuccess: #18: 21079: [TCWG CI] Success after linux: 30 [...] discards d0758601d9 90: onsuccess: #17: 21132: [TCWG CI] Success after binutils/ [...] discards 08933cae53 89: onsuccess: #15: 21132: Success after binutils/llvm/linux [...] discards 89f1d950f6 88: onsuccess: #14: 21055: Success after binutils/llvm/linux [...] discards 1310a63b6e 87: onsuccess: #13: 21042: Success after binutils/llvm/linux [...] discards 9943ade5db 86: onsuccess: #12: 21023: Success after linux: 2636 commits discards 96576e0c7a 85: onsuccess: #11: 21059: Success after binutils/llvm/qemu: [...] discards a11dd025ee 84: force: #9: 21059: Failure after linux: 78 commits discards 78e5406d72 83: onsuccess: #7: all: Success after binutils/llvm/qemu: 66 [...] discards fe67063191 82: onsuccess: #5: all: Success after binutils/llvm/linux/qe [...] discards 2dee09fe9c 81: onsuccess: #4: 21058: Success after binutils/llvm/linux/ [...] discards 69ccb84619 80: onsuccess: #3: 21056: Success after linux: 449 commits discards e4b4da1c69 79: onsuccess: #2: 21057: Success after binutils/llvm/qemu: [...] discards ddd82008fa 78: onsuccess: #577: 21057: Success after binutils/llvm/linu [...] discards 33f1b590ca 77: onsuccess: #576: 21051: Success after binutils/llvm/linu [...] discards 794ae89b5a 76: onsuccess: #575: 21046: Success after binutils/llvm/linu [...] discards c6925c90c7 75: onsuccess: #574: 21014: Success after binutils/llvm/linu [...] discards ed4bc7497e 74: onsuccess: #573: 20726: Success after linux: 10368 commits discards b58efd8071 73: force: #572: 20707: Failure after v6.2-rc6-1149-g5b49da0 [...] discards 3a3131e78a 72: force: #571: 20992: Success after linux: 2668 commits discards ab9a2aa7fd 71: force: #568: 21005: Success after v6.2-rc1-1-gc476a78f19 [...] discards 3a5c3dec15 70: force: #567: 21030: Success after linux: 0 commits discards f030a43bef 69: force: #565: 21005: Failure after v6.2-rc1-1-gc476a78f19 [...] discards 1096093067 68: force: #564: 21030: Failure after linux: 14595 commits discards 103b4f0483 67: force: #560: all: Success after linux: 47576 commits discards 7cb18e40c1 66: force: #558: 21005: Failure after v6.2-rc1-1-gc476a78f19 [...] discards 90ea46e607 65: force: #557: 21030: Success after linux: 0 commits discards b38488c882 64: force: #554: 21023: Failure after v6.2-rc1-10-gc09846fc1 [...] discards c4a074cc68 63: force: #553: 21024: Failure after linux: 6 commits discards cecda767d0 62: onsuccess: #550: 21034: Success after binutils/llvm/qemu [...] discards 558b87ffc0 61: force: #547: 21034: Success after linux: 381 commits discards d7fd3b6ee4 60: onsuccess: #545: 21029: Success after binutils/llvm/qemu [...] discards 6d7cf58699 59: onsuccess: #543: 21029: Success after binutils/llvm/linu [...] discards c21bbc73d5 58: onsuccess: #542: 21025: Success after linux: 2956 commits discards 12ab222409 57: force: #541: 20998: Failure after v6.2-rc1-33-g520560c30 [...] discards b3678ce07c 56: force: #540: 21030: Failure after linux: 32 commits discards 1321489e45 55: force: #538: 21031: Success after baseline build: no new [...] discards fb6dc3eb23 54: force: #536: 21031: Success after baseline build: no new [...] discards 69278f6d04 53: force: #533: 21031: Success after baseline build: no new [...] discards b99ba49c2f 52: force: #531: 21031: Success after baseline build: no new [...] discards 5ffd24d821 51: force: #529: 21031: Success after baseline build: no new [...] discards b9f557d108 50: force: #527: 21031: Success after baseline build: no new [...] discards 41bb37c109 49: force: #525: 21031: Success after baseline build: no new [...] discards 5c19a526e6 48: force: #523: 21031: Success after baseline build: no new [...] discards fd720f59a8 47: force: #521: 21031: Success after baseline build: no new [...] discards 2569b40a45 46: force: #519: 21031: Success after baseline build: no new [...] discards dc5cd8e48d 45: force: #517: 21031: Failure after linux: 271 commits discards 1cd9582c5c 44: onsuccess: #515: 21035: Success after binutils/llvm: 165 [...] discards 1b462dbb3a 43: onsuccess: #513: 21035: Success after binutils/llvm/linu [...] discards a1f0e8928d 42: onsuccess: #512: 21034: Success after binutils/llvm/linu [...] discards ac551b0f14 41: onsuccess: #511: 21030: Success after binutils/llvm/linu [...] discards d531ab3f29 40: onsuccess: #510: 21008: Success after binutils/llvm/linu [...] discards df692c9955 39: force: #509: 20923: Failure after linux: 250 commits discards ebe3360fa6 38: onsuccess: #507: 21142: Success after binutils/llvm/qemu [...] discards 777e06a315 37: onsuccess: #504: 21142: Success after binutils: 113 commits discards 2c3fe114af 36: onsuccess: #502: 21142: Success after binutils/llvm/linu [...] discards a842b3e09f 35: onsuccess: #501: 21134: Success after binutils/llvm/linu [...] discards 04f1e6a39d 34: onsuccess: #500: 21127: Success after binutils/llvm/linu [...] discards ed14fd1e49 33: onsuccess: #499: 21113: Success after binutils/llvm/linu [...] discards e18f3a76bc 32: onsuccess: #498: 21104: Success after binutils/llvm/linu [...] discards a8ba74abf9 31: onsuccess: #497: 21059: Success after binutils/llvm/linu [...] discards 8974b4560b 30: onsuccess: #496: 21054: Success after binutils/llvm/linu [...] discards c9e3d8ecaf 29: onsuccess: #494: 21008: Success after binutils/llvm/linu [...] discards 448cab0ca6 28: onsuccess: #493: 21005: Success after binutils/llvm/linu [...] discards c008746bd1 27: force: #492: 20999: Success after linux: 384 commits discards 83b398c75a 26: force: #490: 20999: Success after baseline build: no new [...] discards 2b9f6455c0 25: force: #488: 20999: Success after linux: 225 commits discards 42d91c3585 24: onsuccess: #486: 20999: Success after binutils/llvm/qemu [...] discards 6cb859f0ec 23: onsuccess: #484: 20999: Success after binutils/llvm/linu [...] discards 3e0864ea97 22: onsuccess: #483: 20999: Success after binutils/llvm/linu [...] discards 81d0dc66d5 21: onsuccess: #482: 20983: Success after binutils/llvm/linu [...] discards ae6dcfc2c1 20: onsuccess: #481: 36: Success after llvm: 228 commits discards 28ec2bb1af 19: force: #480: 36: Failure after llvmorg-16-init-5673-ge07 [...] discards c3ab282b34 18: force: #479: 20954: Success after llvm: 30 commits discards 5a56011402 17: onsuccess: #478: 20954: Success after qemu: 118 commits discards 89b124881a 16: onsuccess: #476: 20954: Success after binutils: 24 commits discards ae511a57ed 15: onsuccess: #474: 20954: Success after binutils/llvm/linu [...] discards ffa0f47a3c 14: onsuccess: #473: 20924: Success after binutils/llvm/linu [...] discards 356452deee 13: onsuccess: #471: 20911: Success after binutils/llvm/linu [...] discards 6c20f7e198 12: onsuccess: #470: 20907: Success after binutils/llvm/linu [...] discards c305e83379 11: onsuccess: #469: 20893: Success after binutils/llvm/linu [...] discards 1ffd1d1f3f 10: onsuccess: 20873: Successful build after binutils/llvm/l [...] discards 5a07c70e9b 9: force: 20867: Regression after linux: 106 commits discards 0cc3359002 8: onsuccess: 20877: Successful build after binutils/llvm/qe [...] discards 58d5f390c2 7: onsuccess: 20877: Successful build after binutils/llvm/li [...] discards 03911ecf6c 6: onsuccess: binutils-llvm-linux-qemu: 20869 discards 1b300c2237 5: onsuccess: binutils-llvm-linux-qemu: 20866 discards d2e99148d0 4: update: binutils-llvm-linux-qemu: 20865 discards 81540bb769 3: reset: llvm-8f0c901c1a172313a32bc06a1fcface76cd1220f: 20629 discards 5245ff82a7 2: update: qemu-5288bee45fbd33203b61f8c76e41b15bb5913e6e: 20914 new 3d72e18f69 2: update: qemu-5288bee45fbd33203b61f8c76e41b15bb5913e6e: 20914 new 2895b2f3eb 3: reset: llvm-8f0c901c1a172313a32bc06a1fcface76cd1220f: 20629 new b9dd566291 4: update: binutils-llvm-linux-qemu: 20865 new 8d67f4d66b 5: onsuccess: binutils-llvm-linux-qemu: 20866 new 8fdd1219b2 6: onsuccess: binutils-llvm-linux-qemu: 20869 new 25f4714581 7: onsuccess: 20877: Successful build after binutils/llvm/li [...] new b007caf3b5 8: onsuccess: 20877: Successful build after binutils/llvm/qe [...] new 74026ab02f 9: force: 20867: Regression after linux: 106 commits new fcbd4e60e2 10: onsuccess: 20873: Successful build after binutils/llvm/l [...] new d95bdf6eb0 11: onsuccess: #469: 20893: Success after binutils/llvm/linu [...] new 80b6b3659c 12: onsuccess: #470: 20907: Success after binutils/llvm/linu [...] new 25ecdc35a6 13: onsuccess: #471: 20911: Success after binutils/llvm/linu [...] new 64a873624a 14: onsuccess: #473: 20924: Success after binutils/llvm/linu [...] new abea3f4151 15: onsuccess: #474: 20954: Success after binutils/llvm/linu [...] new 7355ee1f1b 16: onsuccess: #476: 20954: Success after binutils: 24 commits new c7df2da429 17: onsuccess: #478: 20954: Success after qemu: 118 commits new ba86b9c993 18: force: #479: 20954: Success after llvm: 30 commits new f5f92279fd 19: force: #480: 36: Failure after llvmorg-16-init-5673-ge07 [...] new 84dcd42df5 20: onsuccess: #481: 36: Success after llvm: 228 commits new 9a925e13b1 21: onsuccess: #482: 20983: Success after binutils/llvm/linu [...] new ab6b204509 22: onsuccess: #483: 20999: Success after binutils/llvm/linu [...] new b566a656f7 23: onsuccess: #484: 20999: Success after binutils/llvm/linu [...] new d045300156 24: onsuccess: #486: 20999: Success after binutils/llvm/qemu [...] new 83603f9ea0 25: force: #488: 20999: Success after linux: 225 commits new 3ea5253ceb 26: force: #490: 20999: Success after baseline build: no new [...] new 1f17dbe00f 27: force: #492: 20999: Success after linux: 384 commits new 2523b5903b 28: onsuccess: #493: 21005: Success after binutils/llvm/linu [...] new e6c25b40b2 29: onsuccess: #494: 21008: Success after binutils/llvm/linu [...] new 539a8b3e8f 30: onsuccess: #496: 21054: Success after binutils/llvm/linu [...] new ccdf2c0f05 31: onsuccess: #497: 21059: Success after binutils/llvm/linu [...] new 5c978c1efc 32: onsuccess: #498: 21104: Success after binutils/llvm/linu [...] new fef0797d52 33: onsuccess: #499: 21113: Success after binutils/llvm/linu [...] new 4ce145f782 34: onsuccess: #500: 21127: Success after binutils/llvm/linu [...] new f8b03d6170 35: onsuccess: #501: 21134: Success after binutils/llvm/linu [...] new f9478384ed 36: onsuccess: #502: 21142: Success after binutils/llvm/linu [...] new a2b64cb23c 37: onsuccess: #504: 21142: Success after binutils: 113 commits new 5af8d50ce6 38: onsuccess: #507: 21142: Success after binutils/llvm/qemu [...] new 3baa0dc63d 39: force: #509: 20923: Failure after linux: 250 commits new 3919aa3dab 40: onsuccess: #510: 21008: Success after binutils/llvm/linu [...] new b0f7f43dc4 41: onsuccess: #511: 21030: Success after binutils/llvm/linu [...] new 508147898e 42: onsuccess: #512: 21034: Success after binutils/llvm/linu [...] new 6bc2a2912d 43: onsuccess: #513: 21035: Success after binutils/llvm/linu [...] new dd81021929 44: onsuccess: #515: 21035: Success after binutils/llvm: 165 [...] new d5c7ce09e8 45: force: #517: 21031: Failure after linux: 271 commits new 3349ba17c2 46: force: #519: 21031: Success after baseline build: no new [...] new 3fb02fd3d3 47: force: #521: 21031: Success after baseline build: no new [...] new af42f00744 48: force: #523: 21031: Success after baseline build: no new [...] new 9e6d2418c6 49: force: #525: 21031: Success after baseline build: no new [...] new ed7faf60b4 50: force: #527: 21031: Success after baseline build: no new [...] new 38ee0ef2e6 51: force: #529: 21031: Success after baseline build: no new [...] new 6b7d1c980f 52: force: #531: 21031: Success after baseline build: no new [...] new af96eb6b61 53: force: #533: 21031: Success after baseline build: no new [...] new 843c7e8135 54: force: #536: 21031: Success after baseline build: no new [...] new 8d8568b606 55: force: #538: 21031: Success after baseline build: no new [...] new 57cbca2817 56: force: #540: 21030: Failure after linux: 32 commits new eec4a0d67e 57: force: #541: 20998: Failure after v6.2-rc1-33-g520560c30 [...] new a6d8ac452d 58: onsuccess: #542: 21025: Success after linux: 2956 commits new fa3c5c77b4 59: onsuccess: #543: 21029: Success after binutils/llvm/linu [...] new 12be5ea581 60: onsuccess: #545: 21029: Success after binutils/llvm/qemu [...] new 4a1238490b 61: force: #547: 21034: Success after linux: 381 commits new a25dcacaef 62: onsuccess: #550: 21034: Success after binutils/llvm/qemu [...] new 472d2a925c 63: force: #553: 21024: Failure after linux: 6 commits new 83fc6588e0 64: force: #554: 21023: Failure after v6.2-rc1-10-gc09846fc1 [...] new 51e286f0c0 65: force: #557: 21030: Success after linux: 0 commits new c432ef3948 66: force: #558: 21005: Failure after v6.2-rc1-1-gc476a78f19 [...] new bc4994aee8 67: force: #560: all: Success after linux: 47576 commits new 8ecae99dc5 68: force: #564: 21030: Failure after linux: 14595 commits new 8bd46f6418 69: force: #565: 21005: Failure after v6.2-rc1-1-gc476a78f19 [...] new 9326edee07 70: force: #567: 21030: Success after linux: 0 commits new c56b6504be 71: force: #568: 21005: Success after v6.2-rc1-1-gc476a78f19 [...] new 3c3e763cc9 72: force: #571: 20992: Success after linux: 2668 commits new 08288af26e 73: force: #572: 20707: Failure after v6.2-rc6-1149-g5b49da0 [...] new 55f9a9f8e2 74: onsuccess: #573: 20726: Success after linux: 10368 commits new 6d4b927478 75: onsuccess: #574: 21014: Success after binutils/llvm/linu [...] new af08aea511 76: onsuccess: #575: 21046: Success after binutils/llvm/linu [...] new 126f78769d 77: onsuccess: #576: 21051: Success after binutils/llvm/linu [...] new 13070d64ee 78: onsuccess: #577: 21057: Success after binutils/llvm/linu [...] new 54d17b2979 79: onsuccess: #2: 21057: Success after binutils/llvm/qemu: [...] new d770fd22f1 80: onsuccess: #3: 21056: Success after linux: 449 commits new 627b7de424 81: onsuccess: #4: 21058: Success after binutils/llvm/linux/ [...] new 9fe28eb269 82: onsuccess: #5: all: Success after binutils/llvm/linux/qe [...] new f3e1fba2e1 83: onsuccess: #7: all: Success after binutils/llvm/qemu: 66 [...] new f2d22d6d14 84: force: #9: 21059: Failure after linux: 78 commits new bbeb068de0 85: onsuccess: #11: 21059: Success after binutils/llvm/qemu: [...] new 83010d13eb 86: onsuccess: #12: 21023: Success after linux: 2636 commits new ad7398cdef 87: onsuccess: #13: 21042: Success after binutils/llvm/linux [...] new 149dd8c980 88: onsuccess: #14: 21055: Success after binutils/llvm/linux [...] new 302e309f4a 89: onsuccess: #15: 21132: Success after binutils/llvm/linux [...] new d63c16f095 90: onsuccess: #17: 21132: [TCWG CI] Success after binutils/ [...] new 971c440e21 91: onsuccess: #18: 21079: [TCWG CI] Success after linux: 30 [...] new 580c944d73 92: onsuccess: #19: all: [TCWG CI] Success after binutils/ll [...] new 085f66dac1 93: onsuccess: #20: all: [TCWG CI] Success after binutils/ll [...] new c5f3030de0 94: onsuccess: #21: all: [TCWG CI] https://ci.linaro.org/job [...] new 143b7aa992 95: onsuccess: #23: all: [TCWG CI] https://ci.linaro.org/job [...] new 0df72f4636 96: onsuccess: #26: all: [TCWG CI] https://ci.linaro.org/job [...] new 5c78987009 97: force: #28: all: [TCWG CI] https://ci.linaro.org/job/tcw [...] new e67f9c2cab 98: force: #30: all: [TCWG CI] https://ci.linaro.org/job/tcw [...] new cccfc2c15f 99: force: #32: all: [TCWG CI] https://ci.linaro.org/job/tcw [...] new 6f5617310b 100: force: #35: all: [TCWG CI] https://ci.linaro.org/job/tc [...] new c1c0f11969 101: onsuccess: #39: all: [TCWG CI] https://ci.linaro.org/jo [...] new 5e4f0e9c6f 102: force: #41: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 5538d38491 103: onsuccess: #42: 21165: [TCWG CI] https://ci.linaro.org/ [...]
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 (70c4db01af) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-n [...]
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 1988 -> 2192 bytes 02-prepare_abe/console.log.xz | Bin 2404 -> 2412 bytes 03-build_abe-binutils/console.log.xz | Bin 26660 -> 27008 bytes 04-build_kernel_llvm/console.log.xz | Bin 64952 -> 65048 bytes 05-build_abe-qemu/console.log.xz | Bin 30656 -> 32464 bytes 06-build_linux/console.log.xz | Bin 3464 -> 3572 bytes 08-check_regression/console.log.xz | Bin 1540 -> 524 bytes 08-check_regression/results.regressions | 12 -------- 08-check_regression/trigger-bisect | 2 -- 09-update_baseline/console.log | 48 ++++++++++++++++---------------- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- jenkins/notify.sh | 3 -- mail/check-regression-status.txt | 2 +- manifest.sh | 29 ++++++++++--------- results | 14 +--------- 18 files changed, 46 insertions(+), 72 deletions(-) delete mode 100644 08-check_regression/results.regressions delete mode 100644 08-check_regression/trigger-bisect delete mode 100755 jenkins/notify.sh