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-lts-allmodconfig in repository toolchain/ci/base-artifacts.
discards f8a3fc6ac94 101: force: #39: : [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards ff314982163 100: force: #38: boot: [TCWG CI] https://ci.linaro.org/job/ [...] discards a53a969367e 99: onsuccess: #37: boot: [TCWG CI] https://ci.linaro.org/j [...] discards 42f954069db 98: onsuccess: #35: boot: [TCWG CI] https://ci.linaro.org/j [...] discards 4a2c148f2a5 97: onsuccess: #34: boot: [TCWG CI] https://ci.linaro.org/j [...] discards 707a18bf8d9 96: onsuccess: #31: boot: [TCWG CI] https://ci.linaro.org/j [...] discards 26cacc587d2 95: onsuccess: #30: boot: [TCWG CI] https://ci.linaro.org/j [...] discards c1f9a622951 94: onsuccess: #29: boot: [TCWG CI] https://ci.linaro.org/j [...] discards 9f179f7d7ee 93: onsuccess: #28: boot: [TCWG CI] https://ci.linaro.org/j [...] discards f30981d640b 92: onsuccess: #27: boot: [TCWG CI] https://ci.linaro.org/j [...] discards a3b332b94c8 91: onsuccess: #26: boot: [TCWG CI] https://ci.linaro.org/j [...] discards f1b1202cdad 90: onsuccess: #24: boot: [TCWG CI] https://ci.linaro.org/j [...] discards 948b3450eda 89: onsuccess: #23: boot: [TCWG CI] https://ci.linaro.org/j [...] discards ea2349bb890 88: onsuccess: #22: boot: [TCWG CI] https://ci.linaro.org/j [...] discards 92f3003c1da 87: onsuccess: #21: 22963: [TCWG CI] https://ci.linaro.org/ [...] discards c03f59185d0 86: force: #20: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 1613f3e9641 85: force: #19: boot: [TCWG CI] https://ci.linaro.org/job/t [...] discards 2dc4725e8b4 84: onsuccess: #18: boot: [TCWG CI] https://ci.linaro.org/j [...] discards ef0c4920209 83: onsuccess: #16: boot: [TCWG CI] Success after binutils: [...] discards eed772c24e7 82: onsuccess: #15: boot: [TCWG CI] Success after v6.1.23-4 [...] discards 4ec8619646f 81: onsuccess: #12: boot: [TCWG CI] Success after binutils/ [...] discards 7abca7896ef 80: onsuccess: #11: boot: [TCWG CI] Success after binutils/ [...] discards dec6964344f 79: onsuccess: #9: boot: Success after binutils/llvm/linux/ [...] discards ef32cddaded 78: onsuccess: #8: boot: Success after binutils/llvm/linux/ [...] discards 2948911d1da 77: onsuccess: #7: boot: Success after binutils/llvm/linux/ [...] discards f81f0980290 76: onsuccess: #6: 23008: Success after v6.1.16-44712-gb82a [...] discards bc2c54a040e 75: onsuccess: #5: 23010: Success after binutils/llvm/qemu: [...] discards 4b3144ac424 74: onsuccess: #3: 23010: Success after binutils/llvm/linux [...] discards 52acc39f243 73: onsuccess: #2: 23010: Success after binutils/llvm/qemu: [...] discards a09363f06a2 72: onsuccess: #1: 23010: Success after binutils/llvm/linux [...] discards 1f2c5efb4a7 71: onsuccess: #549: 23010: Success after binutils/llvm/qem [...] discards 1875267ec3f 70: onsuccess: #548: 23010: Success after binutils/llvm/lin [...] discards b4bf4412c95 69: onsuccess: #547: 23010: Success after linux: 142737 commits discards 8aeb6312325 68: force: #546: 20604: Failure after linux: 0 commits discards 34303b6dc4c 67: onsuccess: #544: all: Success after binutils/llvm/qemu: [...] discards 8394c247748 66: onsuccess: #542: all: Success after binutils/llvm/linux [...] discards 44d1f647fcd 65: onsuccess: #541: all: Success after binutils/llvm/qemu: [...] discards c59383841c9 64: onsuccess: #540: all: Success after binutils/llvm/linux [...] discards 6db5d5510d3 63: onsuccess: #539: all: Success after binutils/llvm/linux [...] discards 052bf2ad421 62: onsuccess: #538: all: Success after binutils/llvm/qemu: [...] discards 41bef31edf8 61: onsuccess: #537: all: Success after binutils/llvm/linux [...] discards 14d760a8f18 60: onsuccess: #536: 21439: Success after llvm: 147 commits discards e3f9a71f661 59: force: #535: 21439: Failure after working-10379-ge327b5 [...] discards 6f916c7b51f 58: force: #534: all: Success after llvm: 518 commits discards 22c3a64e937 57: onsuccess: #533: all: Success after qemu: 76 commits discards feb7ea4e62b 56: onsuccess: #531: all: Success after binutils: 194 commits discards 56107e7c41c 55: onsuccess: #530: all: Success after v5.15.87-30564-gee5 [...] discards cae2386ea67 54: onsuccess: #527: 21757: Success after binutils/llvm/qem [...] discards 5491843985e 53: onsuccess: #526: 21757: Success after binutils/llvm/qem [...] discards 94c9171ddbb 52: onsuccess: #525: 21757: Success after binutils/llvm/lin [...] discards 78476a90fc3 51: onsuccess: #524: 21757: Success after binutils/llvm: 35 [...] discards 69f28aecac9 50: onsuccess: #523: 21757: Success after binutils/llvm/lin [...] discards b82f8649a79 49: onsuccess: #522: 21757: Success after binutils/llvm/lin [...] discards 37ea03c8a5d 48: onsuccess: #521: 21757: Success after binutils/llvm/qem [...] discards 2e217af00cc 47: onsuccess: #520: 21757: Success after linux: 30601 commits discards c98ec1f33a4 46: force: #519: 21745: Failure after v5.15.81-80-gac2d7fa9 [...] discards 4a958676db7 45: force: #518: 21892: Success after linux: 284 commits discards 421bc31c4d3 44: onsuccess: #516: 21892: Success after binutils/llvm/qem [...] discards db358edd96d 43: onsuccess: #513: 21892: Success after binutils: 44 commits discards c46b4b33649 42: onsuccess: #511: 21892: Success after binutils/llvm/lin [...] discards 3dced6a8f3f 41: onsuccess: #510: 21892: Success after binutils/llvm/qem [...] discards cd62fcf8768 40: onsuccess: #509: 21892: Success after binutils/llvm/qem [...] discards 520f7ca8330 39: onsuccess: #508: 21892: Success after binutils/llvm/lin [...] discards eb13f839c27 38: onsuccess: #507: 21892: Success after binutils/llvm/lin [...] discards 7b5785eeb72 37: onsuccess: #506: 21892: Success after binutils/llvm/qem [...] discards b83b4e0d6e4 36: onsuccess: #505: 21892: Success after binutils/llvm/qem [...] discards 5626db89a04 35: onsuccess: #504: 21892: Success after binutils/llvm/lin [...] discards 93dc8668591 34: onsuccess: #503: 21892: Success after binutils/llvm/qem [...] discards 601c44d2e46 33: onsuccess: #502: 21892: Success after binutils/llvm/qem [...] discards 57c4b1fe228 32: onsuccess: #501: 21892: Success after binutils/llvm/lin [...] discards 8ed584cbd4c 31: onsuccess: #500: 21892: Success after binutils/llvm/qem [...] discards d5aca9870e3 30: onsuccess: #499: 21892: Success after binutils/llvm/qem [...] discards 1e4a2abeec0 29: onsuccess: #498: 21892: Success after binutils/llvm/lin [...] discards 2130027bc3b 28: onsuccess: #497: 37: Success after binutils/llvm/linux/ [...] discards 70bfaf20c99 27: onsuccess: #496: 37: Success after llvm: 48 commits discards a257a1dbf5a 26: force: #495: 37: Failure after llvmorg-16-init-5673-ge0 [...] discards b45a410ed58 25: force: #494: 21887: Success after llvm: 224 commits discards 7c884f0d460 24: onsuccess: #493: 21887: Success after qemu: 5 commits discards a346738f797 23: onsuccess: #491: 21887: Success after binutils: 43 commits discards d6b9e5ff3c5 22: onsuccess: #490: 21887: Success after v5.15.70-30549-g1 [...] discards 9d53c5cb500 21: onsuccess: #487: 21887: Success after binutils/llvm/lin [...] discards 1ab41a63116 20: onsuccess: #486: 21887: Success after binutils/llvm/lin [...] discards 1ead23d76fb 19: onsuccess: #485: 21885: Success after binutils/llvm: 33 [...] discards 1d8506e969a 18: onsuccess: #484: 21885: Success after binutils/llvm/lin [...] discards ea5bf5a252c 17: onsuccess: #483: 21885: Success after binutils/llvm/lin [...] discards 1af9dd29203 16: onsuccess: 21885: Success after binutils/llvm/linux/qem [...] discards 235d10ef6ad 15: onsuccess: 21885: Successful build after linux: 30642 commits discards c0618f1c234 14: force: 21885: Regression after linux: crypto: blake2s - [...] discards 671dada2105 13: force: 21889: Successful build after linux: 690 commits discards ce4f4a44415 12: onsuccess: 21889: Successful build after binutils/llvm/ [...] discards e30e398e633 11: onsuccess: 21889: Successful build after llvm: 488 commits discards ee028a9ccf5 10: force: 21889: Regression after llvm: Fix -Wbitfield-con [...] discards bc200eb76e4 9: force: 21891: Successful build after llvm: 258 commits discards c263ef6debc 8: onsuccess: 21891: Successful build after qemu: 10 commits discards 81860b0212d 7: onsuccess: binutils-8ad969a3fe9159c261092875def3b323acc5 [...] discards 1b7ec9bda70 6: onsuccess: linux-a81455654f70a9f3f2ebfc0708c105f16080b69 [...] discards 4ffd11882cc 5: onsuccess: qemu-61b6e67171c602cf6451e4928c9cdcc24c57a485: 21891 discards 71a88b8c829 4: onsuccess: binutils-31f6009538b75c22a4b3f99216846973283f [...] discards 7088bc7e8fc 3: onsuccess: linux-85829ea26ba91f8e98d5defc0ac8d20967b8eb4 [...] discards 024313a7c2f 2: update: binutils-llvm-linux-qemu: 21891 discards 3fa98c63881 1: reset: linux-4a2b285e7e103d4d6c6ed3e5052a0ff74a5d7f15: 21692 new f1596800dcd 1: reset: linux-4a2b285e7e103d4d6c6ed3e5052a0ff74a5d7f15: 21692 new 39285f1a5ba 2: update: binutils-llvm-linux-qemu: 21891 new 6d3e3e5b05a 3: onsuccess: linux-85829ea26ba91f8e98d5defc0ac8d20967b8eb4 [...] new 2c98172ed3f 4: onsuccess: binutils-31f6009538b75c22a4b3f99216846973283f [...] new 1ed651d52f7 5: onsuccess: qemu-61b6e67171c602cf6451e4928c9cdcc24c57a485: 21891 new a4231b93fbc 6: onsuccess: linux-a81455654f70a9f3f2ebfc0708c105f16080b69 [...] new c7039255d50 7: onsuccess: binutils-8ad969a3fe9159c261092875def3b323acc5 [...] new 7d8e2b71808 8: onsuccess: 21891: Successful build after qemu: 10 commits new 132bdac1396 9: force: 21891: Successful build after llvm: 258 commits new dacf32b8046 10: force: 21889: Regression after llvm: Fix -Wbitfield-con [...] new 85265127d32 11: onsuccess: 21889: Successful build after llvm: 488 commits new 90581fd797f 12: onsuccess: 21889: Successful build after binutils/llvm/ [...] new 8a00106d1d5 13: force: 21889: Successful build after linux: 690 commits new 1d641661151 14: force: 21885: Regression after linux: crypto: blake2s - [...] new 3708705ef02 15: onsuccess: 21885: Successful build after linux: 30642 commits new 5045dc52d60 16: onsuccess: 21885: Success after binutils/llvm/linux/qem [...] new c8099c6e699 17: onsuccess: #483: 21885: Success after binutils/llvm/lin [...] new 8d2e5b422c5 18: onsuccess: #484: 21885: Success after binutils/llvm/lin [...] new 56a08debf80 19: onsuccess: #485: 21885: Success after binutils/llvm: 33 [...] new 306e5321fb2 20: onsuccess: #486: 21887: Success after binutils/llvm/lin [...] new 007ed83c024 21: onsuccess: #487: 21887: Success after binutils/llvm/lin [...] new 285ffed0869 22: onsuccess: #490: 21887: Success after v5.15.70-30549-g1 [...] new 770962584ad 23: onsuccess: #491: 21887: Success after binutils: 43 commits new 06ff70d728b 24: onsuccess: #493: 21887: Success after qemu: 5 commits new 54c006b0b9d 25: force: #494: 21887: Success after llvm: 224 commits new bd254f5a1bc 26: force: #495: 37: Failure after llvmorg-16-init-5673-ge0 [...] new 373d80b35e8 27: onsuccess: #496: 37: Success after llvm: 48 commits new 86189cd6f5d 28: onsuccess: #497: 37: Success after binutils/llvm/linux/ [...] new cb6d60fd7a6 29: onsuccess: #498: 21892: Success after binutils/llvm/lin [...] new ea130a03240 30: onsuccess: #499: 21892: Success after binutils/llvm/qem [...] new b4ff44508e6 31: onsuccess: #500: 21892: Success after binutils/llvm/qem [...] new 36f6490c7f4 32: onsuccess: #501: 21892: Success after binutils/llvm/lin [...] new ef62e7e9bc6 33: onsuccess: #502: 21892: Success after binutils/llvm/qem [...] new b595e23a834 34: onsuccess: #503: 21892: Success after binutils/llvm/qem [...] new 321c1bd13a3 35: onsuccess: #504: 21892: Success after binutils/llvm/lin [...] new d3b3a0cf206 36: onsuccess: #505: 21892: Success after binutils/llvm/qem [...] new c92a5903337 37: onsuccess: #506: 21892: Success after binutils/llvm/qem [...] new 72faa4a1477 38: onsuccess: #507: 21892: Success after binutils/llvm/lin [...] new 1facad65d39 39: onsuccess: #508: 21892: Success after binutils/llvm/lin [...] new 67372ba98f4 40: onsuccess: #509: 21892: Success after binutils/llvm/qem [...] new 3926de82a16 41: onsuccess: #510: 21892: Success after binutils/llvm/qem [...] new 626d2f5eca0 42: onsuccess: #511: 21892: Success after binutils/llvm/lin [...] new 32973b17f3c 43: onsuccess: #513: 21892: Success after binutils: 44 commits new eb04d4d4afc 44: onsuccess: #516: 21892: Success after binutils/llvm/qem [...] new 68baadbdc73 45: force: #518: 21892: Success after linux: 284 commits new c6001f9c771 46: force: #519: 21745: Failure after v5.15.81-80-gac2d7fa9 [...] new 8a66b6d83e6 47: onsuccess: #520: 21757: Success after linux: 30601 commits new 01a66315a54 48: onsuccess: #521: 21757: Success after binutils/llvm/qem [...] new f1bb7a461fd 49: onsuccess: #522: 21757: Success after binutils/llvm/lin [...] new ba365511dfa 50: onsuccess: #523: 21757: Success after binutils/llvm/lin [...] new 38e91877721 51: onsuccess: #524: 21757: Success after binutils/llvm: 35 [...] new 1539cfb0a1e 52: onsuccess: #525: 21757: Success after binutils/llvm/lin [...] new 49d8164f364 53: onsuccess: #526: 21757: Success after binutils/llvm/qem [...] new 8f3c7cb2606 54: onsuccess: #527: 21757: Success after binutils/llvm/qem [...] new a534470fbee 55: onsuccess: #530: all: Success after v5.15.87-30564-gee5 [...] new c2d8e1337d4 56: onsuccess: #531: all: Success after binutils: 194 commits new eed708d1442 57: onsuccess: #533: all: Success after qemu: 76 commits new 635bb442c2d 58: force: #534: all: Success after llvm: 518 commits new 7b2a1319792 59: force: #535: 21439: Failure after working-10379-ge327b5 [...] new 84f59cb7565 60: onsuccess: #536: 21439: Success after llvm: 147 commits new 595c9d32755 61: onsuccess: #537: all: Success after binutils/llvm/linux [...] new c472527e9a3 62: onsuccess: #538: all: Success after binutils/llvm/qemu: [...] new 3387652a6f1 63: onsuccess: #539: all: Success after binutils/llvm/linux [...] new fc8a2e87a7a 64: onsuccess: #540: all: Success after binutils/llvm/linux [...] new d3b58c9c861 65: onsuccess: #541: all: Success after binutils/llvm/qemu: [...] new ae6e1ebe75a 66: onsuccess: #542: all: Success after binutils/llvm/linux [...] new f0a0d19dfd2 67: onsuccess: #544: all: Success after binutils/llvm/qemu: [...] new 6415c20b7b7 68: force: #546: 20604: Failure after linux: 0 commits new 755c3649cf3 69: onsuccess: #547: 23010: Success after linux: 142737 commits new cdc5e80947b 70: onsuccess: #548: 23010: Success after binutils/llvm/lin [...] new 3ef2ab892aa 71: onsuccess: #549: 23010: Success after binutils/llvm/qem [...] new 5928cd2a6e8 72: onsuccess: #1: 23010: Success after binutils/llvm/linux [...] new 5fa46f93a89 73: onsuccess: #2: 23010: Success after binutils/llvm/qemu: [...] new 39657ef1a44 74: onsuccess: #3: 23010: Success after binutils/llvm/linux [...] new 845320badc4 75: onsuccess: #5: 23010: Success after binutils/llvm/qemu: [...] new dbd58d168bc 76: onsuccess: #6: 23008: Success after v6.1.16-44712-gb82a [...] new eb6f69d6d3d 77: onsuccess: #7: boot: Success after binutils/llvm/linux/ [...] new 804a070aadb 78: onsuccess: #8: boot: Success after binutils/llvm/linux/ [...] new b8bb91489f2 79: onsuccess: #9: boot: Success after binutils/llvm/linux/ [...] new f7bef58c683 80: onsuccess: #11: boot: [TCWG CI] Success after binutils/ [...] new fb299865754 81: onsuccess: #12: boot: [TCWG CI] Success after binutils/ [...] new af6784c2a90 82: onsuccess: #15: boot: [TCWG CI] Success after v6.1.23-4 [...] new e732c3dd8df 83: onsuccess: #16: boot: [TCWG CI] Success after binutils: [...] new 7944603d0bb 84: onsuccess: #18: boot: [TCWG CI] https://ci.linaro.org/j [...] new 4f61bb9c234 85: force: #19: boot: [TCWG CI] https://ci.linaro.org/job/t [...] new 47b1b37498c 86: force: #20: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new f1171454fde 87: onsuccess: #21: 22963: [TCWG CI] https://ci.linaro.org/ [...] new f490f3c8176 88: onsuccess: #22: boot: [TCWG CI] https://ci.linaro.org/j [...] new 38580d4472a 89: onsuccess: #23: boot: [TCWG CI] https://ci.linaro.org/j [...] new 35e29f58d11 90: onsuccess: #24: boot: [TCWG CI] https://ci.linaro.org/j [...] new 20b4faba3fe 91: onsuccess: #26: boot: [TCWG CI] https://ci.linaro.org/j [...] new 815ca24e23a 92: onsuccess: #27: boot: [TCWG CI] https://ci.linaro.org/j [...] new 5b1624c94d6 93: onsuccess: #28: boot: [TCWG CI] https://ci.linaro.org/j [...] new d56ea26381a 94: onsuccess: #29: boot: [TCWG CI] https://ci.linaro.org/j [...] new 3635b4b93c4 95: onsuccess: #30: boot: [TCWG CI] https://ci.linaro.org/j [...] new e3bfdc6daae 96: onsuccess: #31: boot: [TCWG CI] https://ci.linaro.org/j [...] new e53c2065a5c 97: onsuccess: #34: boot: [TCWG CI] https://ci.linaro.org/j [...] new c440406eaea 98: onsuccess: #35: boot: [TCWG CI] https://ci.linaro.org/j [...] new 074654907f3 99: onsuccess: #37: boot: [TCWG CI] https://ci.linaro.org/j [...] new 9ea557b8f1b 100: force: #38: boot: [TCWG CI] https://ci.linaro.org/job/ [...] new 8d20747a0fc 101: force: #39: : [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 7cd2a14d249 102: onsuccess: #40: 36: [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 (f8a3fc6ac94) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-l [...]
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 2072 -> 2068 bytes 02-prepare_abe/console.log.xz | Bin 2488 -> 2488 bytes 03-build_abe-binutils/console.log.xz | Bin 27860 -> 27844 bytes 03-build_abe-binutils/make-binutils.log.xz | Bin 17772 -> 17744 bytes 04-build_kernel_llvm/console.log.xz | Bin 65880 -> 66376 bytes 05-build_abe-qemu/console.log.xz | Bin 33776 -> 34300 bytes 05-build_abe-qemu/make-qemu.log.xz | Bin 26388 -> 26844 bytes 06-build_linux/console.log.xz | Bin 3568 -> 3576 bytes 08-check_regression/console.log.xz | Bin 1388 -> 528 bytes 08-check_regression/results.regressions | 7 --- 08-check_regression/trigger-bisect | 2 - 09-update_baseline/console.log | 72 ++++++++++++++--------------- git/llvm_rev | 2 +- manifest.sh | 12 ++--- notify/check-regression-status.txt | 2 +- results | 7 --- 16 files changed, 44 insertions(+), 60 deletions(-) delete mode 100644 08-check_regression/results.regressions delete mode 100644 08-check_regression/trigger-bisect