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 46154928a4 100: force: #35: all: [TCWG CI] https://ci.linaro.org/job/tc [...] discards bf7506e780 99: force: #32: all: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 16340d76ad 98: force: #30: all: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 297296b45f 97: force: #28: all: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 7d5394111d 96: onsuccess: #26: all: [TCWG CI] https://ci.linaro.org/job [...] discards 10dd7ca89a 95: onsuccess: #23: all: [TCWG CI] https://ci.linaro.org/job [...] discards 044383af3b 94: onsuccess: #21: all: [TCWG CI] https://ci.linaro.org/job [...] discards 44b7922de0 93: onsuccess: #20: all: [TCWG CI] Success after binutils/ll [...] discards 0e5e06fdec 92: onsuccess: #19: all: [TCWG CI] Success after binutils/ll [...] discards 6c59cb0bce 91: onsuccess: #18: 21079: [TCWG CI] Success after linux: 30 [...] discards 2b317f8d85 90: onsuccess: #17: 21132: [TCWG CI] Success after binutils/ [...] discards 084b5f06cd 89: onsuccess: #15: 21132: Success after binutils/llvm/linux [...] discards beae1efdd0 88: onsuccess: #14: 21055: Success after binutils/llvm/linux [...] discards d7365c170d 87: onsuccess: #13: 21042: Success after binutils/llvm/linux [...] discards 86ef68eb15 86: onsuccess: #12: 21023: Success after linux: 2636 commits discards b3cbf57154 85: onsuccess: #11: 21059: Success after binutils/llvm/qemu: [...] discards b17ea2dec3 84: force: #9: 21059: Failure after linux: 78 commits discards 178f2bd2cf 83: onsuccess: #7: all: Success after binutils/llvm/qemu: 66 [...] discards 05dba62788 82: onsuccess: #5: all: Success after binutils/llvm/linux/qe [...] discards bffc0e7e4a 81: onsuccess: #4: 21058: Success after binutils/llvm/linux/ [...] discards 6f14d378ff 80: onsuccess: #3: 21056: Success after linux: 449 commits discards da099370d0 79: onsuccess: #2: 21057: Success after binutils/llvm/qemu: [...] discards 69aa4a070b 78: onsuccess: #577: 21057: Success after binutils/llvm/linu [...] discards dd0a8ec615 77: onsuccess: #576: 21051: Success after binutils/llvm/linu [...] discards 6607ddda67 76: onsuccess: #575: 21046: Success after binutils/llvm/linu [...] discards f381ef04ff 75: onsuccess: #574: 21014: Success after binutils/llvm/linu [...] discards 6e216c4499 74: onsuccess: #573: 20726: Success after linux: 10368 commits discards 57e6cd8058 73: force: #572: 20707: Failure after v6.2-rc6-1149-g5b49da0 [...] discards 2b92205ff0 72: force: #571: 20992: Success after linux: 2668 commits discards f2166102eb 71: force: #568: 21005: Success after v6.2-rc1-1-gc476a78f19 [...] discards 7d868591f1 70: force: #567: 21030: Success after linux: 0 commits discards 074aa8cdae 69: force: #565: 21005: Failure after v6.2-rc1-1-gc476a78f19 [...] discards 2492306c08 68: force: #564: 21030: Failure after linux: 14595 commits discards 53a823ce64 67: force: #560: all: Success after linux: 47576 commits discards 517d3ca29c 66: force: #558: 21005: Failure after v6.2-rc1-1-gc476a78f19 [...] discards 53ebd1f681 65: force: #557: 21030: Success after linux: 0 commits discards 8e21802bfd 64: force: #554: 21023: Failure after v6.2-rc1-10-gc09846fc1 [...] discards ad67445c81 63: force: #553: 21024: Failure after linux: 6 commits discards 833a061c18 62: onsuccess: #550: 21034: Success after binutils/llvm/qemu [...] discards 48ea87f416 61: force: #547: 21034: Success after linux: 381 commits discards a605a2185b 60: onsuccess: #545: 21029: Success after binutils/llvm/qemu [...] discards a3c5240c33 59: onsuccess: #543: 21029: Success after binutils/llvm/linu [...] discards db2e982830 58: onsuccess: #542: 21025: Success after linux: 2956 commits discards 6f7e7d457a 57: force: #541: 20998: Failure after v6.2-rc1-33-g520560c30 [...] discards 695609f95e 56: force: #540: 21030: Failure after linux: 32 commits discards 816a34f270 55: force: #538: 21031: Success after baseline build: no new [...] discards 05218ef2bc 54: force: #536: 21031: Success after baseline build: no new [...] discards 8588d61e60 53: force: #533: 21031: Success after baseline build: no new [...] discards 7d92db087b 52: force: #531: 21031: Success after baseline build: no new [...] discards 5e9bd37aac 51: force: #529: 21031: Success after baseline build: no new [...] discards 93f9d4fcac 50: force: #527: 21031: Success after baseline build: no new [...] discards 9c7ca59b67 49: force: #525: 21031: Success after baseline build: no new [...] discards bd711cc402 48: force: #523: 21031: Success after baseline build: no new [...] discards 8491ea7852 47: force: #521: 21031: Success after baseline build: no new [...] discards e5ae4283ea 46: force: #519: 21031: Success after baseline build: no new [...] discards ae8aae4c05 45: force: #517: 21031: Failure after linux: 271 commits discards 8cfaabca99 44: onsuccess: #515: 21035: Success after binutils/llvm: 165 [...] discards 1fcb270e1d 43: onsuccess: #513: 21035: Success after binutils/llvm/linu [...] discards b88d10c266 42: onsuccess: #512: 21034: Success after binutils/llvm/linu [...] discards 935097443e 41: onsuccess: #511: 21030: Success after binutils/llvm/linu [...] discards 20918b7cd2 40: onsuccess: #510: 21008: Success after binutils/llvm/linu [...] discards 210575a09a 39: force: #509: 20923: Failure after linux: 250 commits discards 5a363e1b48 38: onsuccess: #507: 21142: Success after binutils/llvm/qemu [...] discards c6617bc4ce 37: onsuccess: #504: 21142: Success after binutils: 113 commits discards b82757b25a 36: onsuccess: #502: 21142: Success after binutils/llvm/linu [...] discards aec65110de 35: onsuccess: #501: 21134: Success after binutils/llvm/linu [...] discards 0bcab01a68 34: onsuccess: #500: 21127: Success after binutils/llvm/linu [...] discards 11443c1d45 33: onsuccess: #499: 21113: Success after binutils/llvm/linu [...] discards 77721c8f8d 32: onsuccess: #498: 21104: Success after binutils/llvm/linu [...] discards b0b644f091 31: onsuccess: #497: 21059: Success after binutils/llvm/linu [...] discards 2fbad1aeb4 30: onsuccess: #496: 21054: Success after binutils/llvm/linu [...] discards 15c52d4aa4 29: onsuccess: #494: 21008: Success after binutils/llvm/linu [...] discards a47c519390 28: onsuccess: #493: 21005: Success after binutils/llvm/linu [...] discards 732224aa94 27: force: #492: 20999: Success after linux: 384 commits discards d599636515 26: force: #490: 20999: Success after baseline build: no new [...] discards c0658cdfc0 25: force: #488: 20999: Success after linux: 225 commits discards 86aebfa2ac 24: onsuccess: #486: 20999: Success after binutils/llvm/qemu [...] discards 8af6b1fdc9 23: onsuccess: #484: 20999: Success after binutils/llvm/linu [...] discards ba28e4f5ab 22: onsuccess: #483: 20999: Success after binutils/llvm/linu [...] discards fe89dbee31 21: onsuccess: #482: 20983: Success after binutils/llvm/linu [...] discards 68dbf9873a 20: onsuccess: #481: 36: Success after llvm: 228 commits discards 49d804a0a9 19: force: #480: 36: Failure after llvmorg-16-init-5673-ge07 [...] discards b75dc13dc8 18: force: #479: 20954: Success after llvm: 30 commits discards 0327e6e31c 17: onsuccess: #478: 20954: Success after qemu: 118 commits discards f26d3d6d42 16: onsuccess: #476: 20954: Success after binutils: 24 commits discards 3f4652101f 15: onsuccess: #474: 20954: Success after binutils/llvm/linu [...] discards e5ccd09916 14: onsuccess: #473: 20924: Success after binutils/llvm/linu [...] discards ca8baeffda 13: onsuccess: #471: 20911: Success after binutils/llvm/linu [...] discards 1fcc0f08a7 12: onsuccess: #470: 20907: Success after binutils/llvm/linu [...] discards e0f47fac18 11: onsuccess: #469: 20893: Success after binutils/llvm/linu [...] discards ad90b9c6b1 10: onsuccess: 20873: Successful build after binutils/llvm/l [...] discards b32eaa985f 9: force: 20867: Regression after linux: 106 commits discards 0a75259170 8: onsuccess: 20877: Successful build after binutils/llvm/qe [...] discards 2d38e6df4c 7: onsuccess: 20877: Successful build after binutils/llvm/li [...] discards 01012c1797 6: onsuccess: binutils-llvm-linux-qemu: 20869 discards 77dba18ae4 5: onsuccess: binutils-llvm-linux-qemu: 20866 discards 33bac2d655 4: update: binutils-llvm-linux-qemu: 20865 discards e53ae853c1 3: reset: llvm-8f0c901c1a172313a32bc06a1fcface76cd1220f: 20629 discards cd07c45fef 2: update: qemu-5288bee45fbd33203b61f8c76e41b15bb5913e6e: 20914 discards 0679b2b2bc 1: reset: linux-626bf91a292e2035af5b9d9cce35c5c138dfe06d: discards 190413b26e 0: update: binutils-llvm-qemu: all new 0e0df19cbd 0: update: binutils-llvm-qemu: all new c9a8468aea 1: reset: linux-626bf91a292e2035af5b9d9cce35c5c138dfe06d: new 606a12ac63 2: update: qemu-5288bee45fbd33203b61f8c76e41b15bb5913e6e: 20914 new c73330bdd2 3: reset: llvm-8f0c901c1a172313a32bc06a1fcface76cd1220f: 20629 new 346ba800a4 4: update: binutils-llvm-linux-qemu: 20865 new 49129dc790 5: onsuccess: binutils-llvm-linux-qemu: 20866 new 14dd49171e 6: onsuccess: binutils-llvm-linux-qemu: 20869 new 12f0f24b04 7: onsuccess: 20877: Successful build after binutils/llvm/li [...] new 5cf3005f25 8: onsuccess: 20877: Successful build after binutils/llvm/qe [...] new 3167c872c7 9: force: 20867: Regression after linux: 106 commits new 3684d6ac20 10: onsuccess: 20873: Successful build after binutils/llvm/l [...] new 2ccd81c6b7 11: onsuccess: #469: 20893: Success after binutils/llvm/linu [...] new e37f73ba06 12: onsuccess: #470: 20907: Success after binutils/llvm/linu [...] new 5fcba831de 13: onsuccess: #471: 20911: Success after binutils/llvm/linu [...] new 4dffa6204e 14: onsuccess: #473: 20924: Success after binutils/llvm/linu [...] new 12294d8c90 15: onsuccess: #474: 20954: Success after binutils/llvm/linu [...] new 92ab75723d 16: onsuccess: #476: 20954: Success after binutils: 24 commits new aaa5bb4a0c 17: onsuccess: #478: 20954: Success after qemu: 118 commits new 81dfa9565e 18: force: #479: 20954: Success after llvm: 30 commits new 65504695bc 19: force: #480: 36: Failure after llvmorg-16-init-5673-ge07 [...] new 86b1085c1a 20: onsuccess: #481: 36: Success after llvm: 228 commits new b494371219 21: onsuccess: #482: 20983: Success after binutils/llvm/linu [...] new c9d9634b18 22: onsuccess: #483: 20999: Success after binutils/llvm/linu [...] new 8e50ae0f7b 23: onsuccess: #484: 20999: Success after binutils/llvm/linu [...] new 42761e7935 24: onsuccess: #486: 20999: Success after binutils/llvm/qemu [...] new 3d4f2fc0c6 25: force: #488: 20999: Success after linux: 225 commits new 000b28fcba 26: force: #490: 20999: Success after baseline build: no new [...] new fbb886d586 27: force: #492: 20999: Success after linux: 384 commits new 16a4cdea2e 28: onsuccess: #493: 21005: Success after binutils/llvm/linu [...] new 8564d76403 29: onsuccess: #494: 21008: Success after binutils/llvm/linu [...] new f52e62ace0 30: onsuccess: #496: 21054: Success after binutils/llvm/linu [...] new b89054a419 31: onsuccess: #497: 21059: Success after binutils/llvm/linu [...] new e4b0c7bf94 32: onsuccess: #498: 21104: Success after binutils/llvm/linu [...] new 34f7993a8a 33: onsuccess: #499: 21113: Success after binutils/llvm/linu [...] new ac8cb1c2fa 34: onsuccess: #500: 21127: Success after binutils/llvm/linu [...] new 94ecf4166e 35: onsuccess: #501: 21134: Success after binutils/llvm/linu [...] new 314088a192 36: onsuccess: #502: 21142: Success after binutils/llvm/linu [...] new efe09715ee 37: onsuccess: #504: 21142: Success after binutils: 113 commits new 3019804dd7 38: onsuccess: #507: 21142: Success after binutils/llvm/qemu [...] new 04bf346c36 39: force: #509: 20923: Failure after linux: 250 commits new 99fe42fd33 40: onsuccess: #510: 21008: Success after binutils/llvm/linu [...] new 310579ab2a 41: onsuccess: #511: 21030: Success after binutils/llvm/linu [...] new aebcca0f7d 42: onsuccess: #512: 21034: Success after binutils/llvm/linu [...] new 617cea9a03 43: onsuccess: #513: 21035: Success after binutils/llvm/linu [...] new 0d7590da61 44: onsuccess: #515: 21035: Success after binutils/llvm: 165 [...] new 75f1d3364e 45: force: #517: 21031: Failure after linux: 271 commits new c9805b49aa 46: force: #519: 21031: Success after baseline build: no new [...] new 736e379d2d 47: force: #521: 21031: Success after baseline build: no new [...] new 900b6d1638 48: force: #523: 21031: Success after baseline build: no new [...] new e599f7846d 49: force: #525: 21031: Success after baseline build: no new [...] new 50be6f7d31 50: force: #527: 21031: Success after baseline build: no new [...] new 10bf71bb7d 51: force: #529: 21031: Success after baseline build: no new [...] new d89d1b3492 52: force: #531: 21031: Success after baseline build: no new [...] new 22a5fba9c8 53: force: #533: 21031: Success after baseline build: no new [...] new b725909fdc 54: force: #536: 21031: Success after baseline build: no new [...] new 2e47667ccb 55: force: #538: 21031: Success after baseline build: no new [...] new 884e7d0e36 56: force: #540: 21030: Failure after linux: 32 commits new aba4a85ed9 57: force: #541: 20998: Failure after v6.2-rc1-33-g520560c30 [...] new f10ee0824e 58: onsuccess: #542: 21025: Success after linux: 2956 commits new f84ab148b3 59: onsuccess: #543: 21029: Success after binutils/llvm/linu [...] new ddc64f4fec 60: onsuccess: #545: 21029: Success after binutils/llvm/qemu [...] new da2081fa25 61: force: #547: 21034: Success after linux: 381 commits new 49dcae9e57 62: onsuccess: #550: 21034: Success after binutils/llvm/qemu [...] new c72cb1be41 63: force: #553: 21024: Failure after linux: 6 commits new c0dea01683 64: force: #554: 21023: Failure after v6.2-rc1-10-gc09846fc1 [...] new a69c26fbbb 65: force: #557: 21030: Success after linux: 0 commits new f56a39245d 66: force: #558: 21005: Failure after v6.2-rc1-1-gc476a78f19 [...] new 7e74c5af15 67: force: #560: all: Success after linux: 47576 commits new e2eb92d3f8 68: force: #564: 21030: Failure after linux: 14595 commits new 6818fd4583 69: force: #565: 21005: Failure after v6.2-rc1-1-gc476a78f19 [...] new 6f5c01683d 70: force: #567: 21030: Success after linux: 0 commits new 39508edab1 71: force: #568: 21005: Success after v6.2-rc1-1-gc476a78f19 [...] new b7eff61d4b 72: force: #571: 20992: Success after linux: 2668 commits new 2a4fa9017c 73: force: #572: 20707: Failure after v6.2-rc6-1149-g5b49da0 [...] new fab07cd9e7 74: onsuccess: #573: 20726: Success after linux: 10368 commits new c251cf873e 75: onsuccess: #574: 21014: Success after binutils/llvm/linu [...] new 96553eac30 76: onsuccess: #575: 21046: Success after binutils/llvm/linu [...] new bc34cf27d7 77: onsuccess: #576: 21051: Success after binutils/llvm/linu [...] new 59e07d11f3 78: onsuccess: #577: 21057: Success after binutils/llvm/linu [...] new 2fd736b661 79: onsuccess: #2: 21057: Success after binutils/llvm/qemu: [...] new 8c0394cadb 80: onsuccess: #3: 21056: Success after linux: 449 commits new 6afec4cc7c 81: onsuccess: #4: 21058: Success after binutils/llvm/linux/ [...] new 21e0f171ed 82: onsuccess: #5: all: Success after binutils/llvm/linux/qe [...] new de31fdad0c 83: onsuccess: #7: all: Success after binutils/llvm/qemu: 66 [...] new 1f5c30f5d4 84: force: #9: 21059: Failure after linux: 78 commits new 434fb93440 85: onsuccess: #11: 21059: Success after binutils/llvm/qemu: [...] new 2a67e775a6 86: onsuccess: #12: 21023: Success after linux: 2636 commits new a89f396997 87: onsuccess: #13: 21042: Success after binutils/llvm/linux [...] new 04e76b6576 88: onsuccess: #14: 21055: Success after binutils/llvm/linux [...] new 66b324c7fc 89: onsuccess: #15: 21132: Success after binutils/llvm/linux [...] new 4699a11cf9 90: onsuccess: #17: 21132: [TCWG CI] Success after binutils/ [...] new cc3f5f3833 91: onsuccess: #18: 21079: [TCWG CI] Success after linux: 30 [...] new 3e07309bfd 92: onsuccess: #19: all: [TCWG CI] Success after binutils/ll [...] new 4a5a160e2b 93: onsuccess: #20: all: [TCWG CI] Success after binutils/ll [...] new e22258eb89 94: onsuccess: #21: all: [TCWG CI] https://ci.linaro.org/job [...] new 7c8b240aa5 95: onsuccess: #23: all: [TCWG CI] https://ci.linaro.org/job [...] new 80540a6b15 96: onsuccess: #26: all: [TCWG CI] https://ci.linaro.org/job [...] new 8c9814f37b 97: force: #28: all: [TCWG CI] https://ci.linaro.org/job/tcw [...] new 0c560624e7 98: force: #30: all: [TCWG CI] https://ci.linaro.org/job/tcw [...] new cf94879827 99: force: #32: all: [TCWG CI] https://ci.linaro.org/job/tcw [...] new b1212ab3c4 100: force: #35: all: [TCWG CI] https://ci.linaro.org/job/tc [...] new c57f50dcb0 101: onsuccess: #39: all: [TCWG CI] https://ci.linaro.org/jo [...]
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 (46154928a4) \ 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 1984 -> 1940 bytes 02-prepare_abe/console.log.xz | Bin 2452 -> 2420 bytes 03-build_abe-binutils/console.log.xz | Bin 27328 -> 26896 bytes 04-build_kernel_llvm/console.log.xz | Bin 65688 -> 64576 bytes 05-build_abe-qemu/console.log.xz | Bin 31368 -> 30768 bytes 06-build_linux/console.log.xz | Bin 3188 -> 3368 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 528 -> 524 bytes 09-update_baseline/console.log | 44 +++++++++++++++++++++++++++++++---- git/binutils_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 26 +++++++++++---------- 14 files changed, 57 insertions(+), 21 deletions(-)