Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap updated (98d7e017f -> 3ccf33733)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap in repository toolchain/ci/base-artifacts. discards 98d7e017f 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 2e5d162b6 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards 61fd26186 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards 4f08c6bc2 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards cac917733 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards 757561b1d 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards a8874b2be 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 3ce1ce489 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards 6928af192 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 5ba518eb0 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 5cd751643 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards 5f819adce 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 475efe8a7 94: onsuccess: #1476: 2: Success after baseline build: no new [...] discards 8d2885afb 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-2393 [...] discards ca9e599f1 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 05cd5a63d 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 9a16f7f28 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards db2b9f452 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 5126568cc 88: onsuccess: 1: Success after gcc: 20 commits discards 1570b10f9 87: force: 1: Failure after gcc: Fix up dump_printf_loc forma [...] discards 76a8117df 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 w [...] discards d985f5574 85: onsuccess: 2: Success after binutils: 4 commits discards 08cc4fde5 84: onsuccess: 2: Success after gcc: 9 commits discards b8cb1613d 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards c9d3d2416 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 5617d0761 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 59d4cbecd 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 864541a66 79: onsuccess: 1: Successful build after gcc: 3 commits discards 27fb2fc78 78: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] discards 883a16051 77: force: 2: Successful build after gcc: 32 commits discards 8d078eff0 76: onsuccess: 2: Successful build after binutils: 10 commits discards 93a50bc5d 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 94af51c05 74: onsuccess: 2: Successful build after gcc: 13 commits discards bed0acba3 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 4f39680a8 72: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] discards 7cfc216de 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 004ab8b83 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards a45f2fa93 69: onsuccess: 2: Successful build after baseline build: no n [...] discards 6b4ba0b65 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 6e23c83ad 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 2f6761248 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 60f141079 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 4c0b2d648 64: onsuccess: 2: Successful build after gcc: 7 commits discards 8fed58f43 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards f13f97d3a 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 93c71ab06 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 33810c866 60: onsuccess: 1: Successful build after gcc: 15 commits discards 5e6d81205 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] discards 0cad5c619 58: force: 2: Successful build after gcc: tree.cc: Fix optimi [...] discards 965a52556 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 37cf8475f 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards c71618087 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 3a2793a81 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards cea39bf46 53: onsuccess: 2: Successful build after gcc: 5 commits discards 750efea99 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 2be8e151e 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 7d6f7cc55 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 9941c3861 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards f99997c60 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 6d3f4bb97 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 5acbb8cad 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards f420bf728 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards 1f43cd120 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards a10a4e239 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] discards f4255d291 42: onsuccess: 2: Successful build after gcc: 2 commits discards f7cd01118 41: onsuccess: 2: Successful build after baseline build: no n [...] discards 0c317c82f 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards c93041290 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 82848da6c 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards be7a18abe 37: onsuccess: 2: Successful build after gcc: 2 commits discards 0b07143ec 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 0880cbdcb 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 36454cbef 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 21d10ae19 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 74d46935e 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards f6ea0022b 31: onsuccess: 2: Successful build after gcc: 8 commits discards 39b268b70 30: onsuccess: 2: Successful build after gcc: 7 commits discards 43dc5dc8e 29: onsuccess: 2: Successful build after binutils: 5 commits discards c94efd3b2 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 49c1994d6 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards de0e1fe92 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits discards 6af2760ca 25: onsuccess: binutils-gcc: 2 discards 393032a82 24: onsuccess: binutils-gcc: 2 discards c8696f08a 23: onsuccess: binutils-gcc: 2 discards 29f5c9d74 22: onsuccess: binutils-gcc: 2 discards c0e5fd878 21: onsuccess: binutils-gcc: 2 discards 1630e4724 20: onsuccess: binutils-gcc: 2 discards 4b1f03772 19: onsuccess: binutils-gcc: 2 discards d0a01aaff 18: onsuccess: binutils-gcc: 2 discards 2b894bd96 17: onsuccess: binutils-gcc: 2 discards 45bd1bfd6 16: onsuccess: binutils-gcc: 2 discards 8b9d40086 15: onsuccess: binutils-gcc: 2 discards ba8f9563f 14: onsuccess: binutils-gcc: 2 discards 92bb8f20f 13: onsuccess: binutils-gcc: 2 discards 1e77ce33c 12: onsuccess: binutils-gcc: 2 discards 84c43766e 11: onsuccess: binutils-gcc: 2 discards 8ee327f6b 10: onsuccess: binutils-gcc: 2 discards b7994087b 9: onsuccess: binutils-gcc: 2 discards c249f0800 8: onsuccess: binutils-gcc: 2 discards 86ce73d6f 7: onsuccess: binutils-gcc: 2 discards 2812c62ea 6: onsuccess: binutils-gcc: 2 new 9180c9f07 6: onsuccess: binutils-gcc: 2 new 800c22150 7: onsuccess: binutils-gcc: 2 new 3dde5237a 8: onsuccess: binutils-gcc: 2 new 5f44f80e3 9: onsuccess: binutils-gcc: 2 new f9fc1a9b0 10: onsuccess: binutils-gcc: 2 new bf620d214 11: onsuccess: binutils-gcc: 2 new cf9c85158 12: onsuccess: binutils-gcc: 2 new 3046404ff 13: onsuccess: binutils-gcc: 2 new 9ad06b471 14: onsuccess: binutils-gcc: 2 new 8a54f9ce8 15: onsuccess: binutils-gcc: 2 new 40cdcf1ab 16: onsuccess: binutils-gcc: 2 new f3f1bf47a 17: onsuccess: binutils-gcc: 2 new 6920282bc 18: onsuccess: binutils-gcc: 2 new a2fdde07f 19: onsuccess: binutils-gcc: 2 new 4d0df3b9f 20: onsuccess: binutils-gcc: 2 new d90b195ff 21: onsuccess: binutils-gcc: 2 new 5468308b9 22: onsuccess: binutils-gcc: 2 new fa72ef69b 23: onsuccess: binutils-gcc: 2 new 1ab12ea05 24: onsuccess: binutils-gcc: 2 new 4858261b7 25: onsuccess: binutils-gcc: 2 new 1c8de9458 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits new 16c300b8e 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits new cf3c17691 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 798e41f1b 29: onsuccess: 2: Successful build after binutils: 5 commits new e84a7e37b 30: onsuccess: 2: Successful build after gcc: 7 commits new e44abbdc5 31: onsuccess: 2: Successful build after gcc: 8 commits new 4bd6f8d91 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 01a910837 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits new eb560b448 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits new aead6920e 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 11d7af3d3 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 7a3dea6e3 37: onsuccess: 2: Successful build after gcc: 2 commits new 1c054df7a 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 65d4fb00e 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 238a689ec 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 6dbf33477 41: onsuccess: 2: Successful build after baseline build: no n [...] new ac75bd382 42: onsuccess: 2: Successful build after gcc: 2 commits new 64ba4683a 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] new 668d22c10 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 84eb2df09 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 704fb903a 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 18ee0e090 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 816b34d8c 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 9371bf0f5 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 89b73c56f 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new d5fe22270 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 3f0045c8a 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new e1822e941 53: onsuccess: 2: Successful build after gcc: 5 commits new 8457c7072 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 7a9dd01a5 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 8ab9517ae 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 2718e5b1b 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new af836b7ed 58: force: 2: Successful build after gcc: tree.cc: Fix optimi [...] new ce3972b40 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] new 37e89b7c6 60: onsuccess: 1: Successful build after gcc: 15 commits new 4131ddbd0 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new ccd7e5633 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new fc5563e6b 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new a228ef80e 64: onsuccess: 2: Successful build after gcc: 7 commits new 2a2d6814c 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 2d4509501 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new f45787b55 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 98d6fbb0a 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 24b3c50ef 69: onsuccess: 2: Successful build after baseline build: no n [...] new ec7a1a47e 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 754e6912b 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new c0186ce25 72: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] new 67181053b 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new e339831e7 74: onsuccess: 2: Successful build after gcc: 13 commits new e0dfcf600 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new d3677e0dd 76: onsuccess: 2: Successful build after binutils: 10 commits new 3321e2e87 77: force: 2: Successful build after gcc: 32 commits new e89ffd949 78: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] new fd2051ead 79: onsuccess: 1: Successful build after gcc: 3 commits new 06356e57b 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 33c2bbc66 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 169798014 82: onsuccess: 2: Success after binutils/gcc: 26 commits new d7bbb39d7 83: onsuccess: 2: Success after binutils/gcc: 7 commits new f25b824aa 84: onsuccess: 2: Success after gcc: 9 commits new f13053698 85: onsuccess: 2: Success after binutils: 4 commits new 28d299597 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 w [...] new ee7690422 87: force: 1: Failure after gcc: Fix up dump_printf_loc forma [...] new 070183299 88: onsuccess: 1: Success after gcc: 20 commits new 478490633 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 64b4f4a73 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 02babee96 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 97f41414b 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 89c853945 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-2393 [...] new 0be260ff5 94: onsuccess: #1476: 2: Success after baseline build: no new [...] new 542489305 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 7f7e0efa7 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new bb6d3858a 97: onsuccess: #1481: 2: Success after gcc: 8 commits new cc3f70f2f 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 6975ba201 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 63eff09d1 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new 0ede80f5a 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new 297a3d697 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new cecec8ef8 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 1e492adfa 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new e67313b41 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 60659b05b 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 3ccf33733 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits 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 (98d7e017f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] 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 1700 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2712 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 37600 -> 38364 bytes 05-build_abe-bootstrap/console.log.xz | Bin 269760 -> 272620 bytes 06-check_regression/console.log.xz | Bin 1792 -> 1868 bytes 07-update_baseline/console.log | 58 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +++++----- 13 files changed, 43 insertions(+), 43 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (f0a9d2fbe -> 68c6bc796)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards f0a9d2fbe 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] discards d9acabf6d 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 6f5f644f9 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards 656f9a8b7 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards 4e1dc7e41 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 28845bfe0 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards efdd1ba21 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards 38193003d 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards 8954a6670 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 334c1d440 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 3d7f7c73f 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards 911863623 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards 4147303ca 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards be905656a 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards 22f50b40f 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 9fae71028 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 6fbbad08c 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards b6ea361a3 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 6eea6d8cd 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 7f58407c5 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 9a523cace 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 4d74dd15b 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards ec6bf14ec 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 169f751b0 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 3b0df8fb5 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards ada22226c 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards f7aeb4bcd 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 7c77c41e4 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards f9189ea2b 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5c2a5d0a0 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards 883a04577 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e713ea4f3 74: onsuccess: 1: Successful build after linux: 44 commits discards 26850f782 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 6956e0c7c 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 0698d8a49 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards e7061b86a 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards aeb037162 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 8a66b7e41 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2ca9d87fc 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2b7ac22a3 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 983b8704e 65: onsuccess: 1: Successful build after gcc: 4 commits discards ceb020f6a 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 8438c9efe 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 516d6f989 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards d434f299f 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards f2e221c2f 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 5a04a3e13 59: onsuccess: 1: Successful build after glibc: 2 commits discards d4a318a89 58: onsuccess: 1: Successful build after binutils: 2 commits discards 8814ce850 57: onsuccess: 1: Successful build after gcc: 7 commits discards 38d62408c 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7a16d6512 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a659d827a 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 4494a3329 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards e8a34802f 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards cc44e400d 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 142c74349 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5a9c33c33 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 989a4c0d5 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards f7a9705b4 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 106028cbe 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 49ca90bac 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a5a8d439e 44: onsuccess: 1: Successful build after linux: 34 commits discards 2efb1cb0d 43: onsuccess: 1: Successful build after gcc: 2 commits discards 80c2b8b9c 42: onsuccess: 1: Successful build after baseline build: no n [...] discards 3c2b7164f 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 0872edfe6 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 76b1a8268 39: onsuccess: 1: Successful build after gcc: 2 commits discards 71284b1ca 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1067f8d56 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 5bef3afe2 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7320212a0 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 55f85a64a 34: onsuccess: 1: Successful build after gcc: 3 commits discards 66adcbc76 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards bc9c3f88d 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards ca117810d 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards abaa879c5 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards 12086263c 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 04922eac4 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards db8599848 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 694d6e641 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d960e69e7 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2859946ac 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5567efeb5 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b6b166250 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ec5dd3bc4 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards af4ca2170 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 90e9fb4ef 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 654a578d9 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3ee584018 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7b533289f 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1d7c069fd 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards fe1af4737 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 71fba10be 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9058d8534 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 4bb73973f 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5d2fb5adc 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards fc830521f 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 10060cc80 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e2f900861 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards bc1fc1ff8 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 38ce50aba 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f5db6037f 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7465676c3 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c5875a60d 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 818201c92 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 0f67fca95 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8b76c7fde 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6cc7c1a22 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1026504c7 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a29c18aac 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new eda44fe66 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2712d7b6a 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 01e6e3938 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5193ed429 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a6064e2f6 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 32c74b0b0 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2236cb17e 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8c5700423 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5e86024a6 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 25a73d5f8 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e7063eb68 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 52bb4dd59 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ae8f3d59b 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 59aff2dcf 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new db008e5e2 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new c9420d769 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cb96c2bf4 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 7255ea3cc 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new b650ad00d 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 4397ffc73 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 45d7a55a6 34: onsuccess: 1: Successful build after gcc: 3 commits new 4fe49d9a5 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 25a28f43b 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 818e90bd9 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new de03bf3b2 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c145675fa 39: onsuccess: 1: Successful build after gcc: 2 commits new c9e1f3ad6 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 43f4c842e 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 0b44c1923 42: onsuccess: 1: Successful build after baseline build: no n [...] new 42ece4c6e 43: onsuccess: 1: Successful build after gcc: 2 commits new 5a0e42385 44: onsuccess: 1: Successful build after linux: 34 commits new 4c49f08f6 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c9607f5f1 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new a60c1a758 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f8bbe16bc 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 826750db4 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 05d990cd5 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 40e8a6746 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 192559c1b 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 9150dce74 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new c2930cbfb 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new d6a22debc 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 43597fc91 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b9a18d488 57: onsuccess: 1: Successful build after gcc: 7 commits new 2f3793e59 58: onsuccess: 1: Successful build after binutils: 2 commits new 26eb1864b 59: onsuccess: 1: Successful build after glibc: 2 commits new 948aea648 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 9fae3404e 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new b0da992dd 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new 92aabb69d 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new fb1c0c38d 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 8023dfd51 65: onsuccess: 1: Successful build after gcc: 4 commits new a3c0d849e 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 6b91e4f9f 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 553f6e8f9 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b53781fcf 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new d4ebaa0de 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new ad25a1aeb 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new 0177a41f9 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b3bab9d06 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 24f18710d 74: onsuccess: 1: Successful build after linux: 44 commits new 9ed5bd9cc 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new be113203e 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new 3700eb112 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 21b0b4874 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 5deb93c8c 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new c197bafc0 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new 73be7b7eb 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 1bb731cb4 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 80ef7c947 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 74e377a22 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 8710f88e2 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new bee4ee6a0 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new ca35406e9 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 895338c08 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new d8382c41d 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new ded1079cf 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new a26e61489 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new f4ce6d3f7 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new 7093248b6 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 49dcdb198 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new 0d8ff268a 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new e81f6d71e 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new ad7a3943c 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new cabc41cb6 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new a23636e8c 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new b48a4d6c6 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new 0232a8228 101: onsuccess: #1693: 1: Success after glibc: 14 commits new d799c6dde 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new 9898da452 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new 713c91de0 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 8ed1b6c33 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] new 68c6bc796 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] 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 (f0a9d2fbe) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] 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 1720 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 29736 -> 29876 bytes 04-build_abe-stage1/console.log.xz | Bin 90636 -> 90268 bytes 06-build_abe-linux/console.log.xz | Bin 8700 -> 8304 bytes 07-build_abe-glibc/console.log.xz | Bin 233660 -> 234416 bytes 08-build_abe-stage2/console.log.xz | Bin 223376 -> 222976 bytes 09-build_abe-gdb/console.log.xz | Bin 37064 -> 37016 bytes 10-build_abe-qemu/console.log.xz | Bin 31704 -> 31872 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2580 -> 2436 bytes 13-check_regression/console.log.xz | Bin 4272 -> 5252 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 26 + 13-check_regression/results.compare | 9 +- 13-check_regression/results.compare2 | 41 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 26 + sumfiles/g++.log.xz | Bin 2656280 -> 2658780 bytes sumfiles/g++.sum | 20 +- sumfiles/gcc.log.xz | Bin 2194632 -> 2230276 bytes sumfiles/gcc.sum | 2110 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 877180 -> 882176 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201108 -> 201292 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 422556 -> 429104 bytes sumfiles/libstdc++.sum | 8 +- 43 files changed, 1268 insertions(+), 1151 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-lts-allyesconfig updated (98b955b42 -> 57ff12c0d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-lts-allyesconfig in repository toolchain/ci/base-artifacts. from 98b955b42 11: onsuccess: #364: all: Success after binutils/gcc: 14 commits new 57ff12c0d 12: onsuccess: #365: all: Success after binutils/gcc/linux/qe [...] The 1 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 1720 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 30268 -> 30064 bytes 04-build_abe-stage1/console.log.xz | Bin 68776 -> 68488 bytes 05-build_abe-qemu/console.log.xz | Bin 32092 -> 31644 bytes 06-build_linux/console.log.xz | Bin 3396 -> 3372 bytes 07-boot_linux/console.log.xz | Bin 576 -> 576 bytes 08-check_regression/console.log.xz | Bin 2296 -> 3160 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 17 files changed, 23 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_O1 updated (01a4b1b94 -> 0dd6398fc)

by git＠git.linaro.org

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-allyesconfig updated (84c625040 -> 1eff2c137)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-allyesconfig in repository toolchain/ci/base-artifacts. from 84c625040 12: onsuccess: #506: 33: Success after binutils/gcc: 137 commits new 1eff2c137 13: onsuccess: #507: 33: Success after binutils/gcc/linux/qem [...] The 1 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 1724 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30816 -> 30140 bytes 04-build_abe-stage1/console.log.xz | Bin 72636 -> 71836 bytes 05-build_abe-qemu/console.log.xz | Bin 32220 -> 31216 bytes 06-build_linux/console.log.xz | Bin 5116 -> 5452 bytes 08-check_regression/console.log.xz | Bin 2548 -> 3292 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 16 files changed, 23 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/release-aarch64 updated (e003376a7 -> 600f781e6)

by git＠git.linaro.org

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/release-aarch64 in repository toolchain/ci/base-artifacts. from e003376a7 16: onsuccess: #125: 6: Success after binutils/gcc/linux/glib [...] new 600f781e6 17: onsuccess: #126: 6: Success after binutils/gcc/gdb: 12 commits The 1 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 1704 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 38560 -> 37992 bytes 05-build_abe-gcc/console.log.xz | Bin 207380 -> 208256 bytes 06-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 07-build_abe-linux/console.log.xz | Bin 8628 -> 8584 bytes 08-build_abe-glibc/console.log.xz | Bin 239616 -> 240800 bytes 09-build_abe-gdb/console.log.xz | Bin 36804 -> 37172 bytes 10-check_regression/console.log.xz | Bin 3172 -> 2380 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 17 files changed, 21 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_llvm_tx1/llvm-release-aarch64-spec2k6-O3_LTO updated (254d3bc84 -> 855c13e5f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_llvm_tx1/llvm-release-aarch64-spec2k6-O3_LTO in repository toolchain/ci/base-artifacts. from 254d3bc84 5: onsuccess: #185: 1: [TCWG CI] No change after binutils/gcc [...] new 855c13e5f 6: onsuccess: #186: 1: [TCWG CI] 456.hmmer built and run OK a [...] The 1 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 1804 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30868 -> 30556 bytes 04-build_abe-stage1/console.log.xz | Bin 70760 -> 68700 bytes 06-build_abe-linux/console.log.xz | Bin 8648 -> 7840 bytes 07-build_abe-glibc/console.log.xz | Bin 238012 -> 237648 bytes 08-build_abe-stage2/console.log.xz | Bin 179204 -> 172612 bytes 09-build_llvm-true/console.log.xz | Bin 62428 -> 60200 bytes 10-benchmark/benchmark-build.log | 126 +- 10-benchmark/benchmark.log | 124 +- 10-benchmark/console.log.xz | Bin 4100 -> 4020 bytes 11-check_regression/console.log.xz | Bin 6180 -> 6460 bytes 11-check_regression/csv-results-0/md5sum.csv | 18248 +- 11-check_regression/csv-results-0/perf.csv | 83 +- 11-check_regression/csv-results-0/results.csv | 191751 +++++++------- 11-check_regression/csv-results-0/size.csv | 222008 ++++++++--------- 11-check_regression/csv-results-0/vect.csv | 11224 +- 11-check_regression/csv-results-1/md5sum.csv | 33046 +-- 11-check_regression/csv-results-1/perf.csv | 86 +- 11-check_regression/csv-results-1/results.csv | 216577 ++++++++-------- 11-check_regression/csv-results-1/size.csv | 235284 ++++++++++-------- 11-check_regression/csv-results-1/vect.csv | 22169 +- 11-check_regression/exe.improvement | 1 + 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/jira-body.txt | 3 + 11-check_regression/mail-body.txt | 3 + 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results-brief.csv | 33 +- 11-check_regression/results-compare.csv | 4 +- 11-check_regression/results-full.csv | 92 +- 11-check_regression/results-internal.csv | 42 +- 11-check_regression/results.csv | 42 +- 11-check_regression/results.log | 863 +- dashboard/dashboard-generate.sh | 2 +- .../squad/400.perlbench/results-metadata.json | 21 +- dashboard/squad/400.perlbench/results-metrics.json | 2 +- dashboard/squad/401.bzip2/results-metadata.json | 21 +- dashboard/squad/403.gcc/results-metadata.json | 21 +- dashboard/squad/403.gcc/results-metrics.json | 2 +- dashboard/squad/429.mcf/results-metadata.json | 21 +- dashboard/squad/429.mcf/results-metrics.json | 2 +- dashboard/squad/444.namd/results-metadata.json | 21 +- dashboard/squad/444.namd/results-metrics.json | 2 +- dashboard/squad/445.gobmk/results-metadata.json | 21 +- dashboard/squad/445.gobmk/results-metrics.json | 2 +- dashboard/squad/447.dealII/results-metadata.json | 21 +- dashboard/squad/447.dealII/results-metrics.json | 2 +- dashboard/squad/450.soplex/results-metadata.json | 21 +- dashboard/squad/450.soplex/results-metrics.json | 2 +- dashboard/squad/453.povray/results-metadata.json | 21 +- dashboard/squad/453.povray/results-metrics.json | 2 +- dashboard/squad/456.hmmer/results-functional.json | 4 +- dashboard/squad/456.hmmer/results-metadata.json | 21 +- dashboard/squad/456.hmmer/results-metrics.json | 3 + dashboard/squad/458.sjeng/results-metadata.json | 21 +- dashboard/squad/458.sjeng/results-metrics.json | 2 +- .../squad/462.libquantum/results-metadata.json | 21 +- .../squad/462.libquantum/results-metrics.json | 2 +- dashboard/squad/470.lbm/results-metadata.json | 21 +- dashboard/squad/470.lbm/results-metrics.json | 2 +- dashboard/squad/471.omnetpp/results-metadata.json | 21 +- dashboard/squad/471.omnetpp/results-metrics.json | 2 +- dashboard/squad/473.astar/results-metadata.json | 21 +- dashboard/squad/473.astar/results-metrics.json | 2 +- dashboard/squad/482.sphinx3/results-metadata.json | 21 +- dashboard/squad/482.sphinx3/results-metrics.json | 2 +- .../squad/483.xalancbmk/results-metadata.json | 21 +- dashboard/squad/483.xalancbmk/results-metrics.json | 2 +- .../results-functional.json | 0 dashboard/squad/Mean/results-metadata.json | 13 + dashboard/squad/Mean/results-metrics.json | 5 + dashboard/squad/dashboard-push-squad.sh | 295 +- dashboard/squad/summary-annotation.txt | 1 - git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 60 +- mail/mail-body.txt | 60 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 400516 -> 402164 bytes save-temps/403.gcc.tar.xz | Bin 1206788 -> 1210716 bytes save-temps/429.mcf.tar.xz | Bin 22768 -> 22816 bytes save-temps/444.namd.tar.xz | Bin 47004 -> 46872 bytes save-temps/445.gobmk.tar.xz | Bin 620632 -> 614460 bytes save-temps/447.dealII.tar.xz | Bin 872052 -> 854992 bytes save-temps/450.soplex.tar.xz | Bin 205676 -> 204016 bytes save-temps/453.povray.tar.xz | Bin 478968 -> 463512 bytes save-temps/456.hmmer.tar.xz | Bin 0 -> 125112 bytes save-temps/458.sjeng.tar.xz | Bin 52688 -> 52656 bytes save-temps/462.libquantum.tar.xz | Bin 24100 -> 24152 bytes save-temps/470.lbm.tar.xz | Bin 16040 -> 16032 bytes save-temps/471.omnetpp.tar.xz | Bin 322764 -> 324048 bytes save-temps/473.astar.tar.xz | Bin 43996 -> 43804 bytes save-temps/482.sphinx3.tar.xz | Bin 95852 -> 95764 bytes save-temps/483.xalancbmk.tar.xz | Bin 3300136 -> 3179532 bytes 99 files changed, 498058 insertions(+), 454639 deletions(-) create mode 100644 11-check_regression/exe.improvement copy dashboard/squad/{400.perlbench => Mean}/results-functional.json (100%) create mode 100644 dashboard/squad/Mean/results-metadata.json create mode 100644 dashboard/squad/Mean/results-metrics.json create mode 100644 save-temps/456.hmmer.tar.xz -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (04b6801f9 -> 88883432c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-arm in repository toolchain/ci/base-artifacts. discards 04b6801f9 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] discards 5757e1e9d 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards ea62c7123 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 10cb6e544 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] discards 451bf4ba6 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards fee1edc81 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] discards c374b1db9 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] discards 6aa2034b6 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards b3852eb93 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] discards 9022b346e 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] discards 3ddedaa82 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 4d3d663be 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] discards 8ee42dff9 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] discards e7cc0186f 95: onsuccess: #1529: 7: Success after baseline build: no new [...] discards 488391772 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards dd0d7ce11 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] discards fec155ae5 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards bd4c466cc 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards d0e8f23e6 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 6c1a46d82 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 5286a9ae8 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 978cd5b6a 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 830cc3b46 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards e36bb7d40 85: onsuccess: 7: Success after gcc: 9 commits discards ad819e31c 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 03531c426 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 5a6111ac5 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 3e38ed108 81: onsuccess: 7: Successful build after gcc: 2 commits discards 03a01dccf 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards cfd38d608 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards fbeb5e629 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 05bb13472 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards 3282187f0 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 3ff4e0653 75: onsuccess: 7: Successful build after linux: 44 commits discards d86067227 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards d026dc34a 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 8ee68758b 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 09df4e51b 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards ff0b4942d 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 7912da988 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 77f0ba9b6 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 563d17811 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 237552bef 66: onsuccess: 7: Successful build after gcc: 3 commits discards 95adce5e4 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 70165a7ea 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 0698d5f61 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards b333e2fda 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards dd0961ce0 61: onsuccess: 4: Successful build after gcc: 15 commits discards f984f7ad8 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards 169506537 59: force: 7: Successful build after gcc: 2 commits discards 0bde18d9b 58: onsuccess: 7: Successful build after glibc: 2 commits discards 8fcb7d424 57: onsuccess: 7: Successful build after gcc: 7 commits discards 28229e292 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 6b7c1b1f5 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 211dbf48f 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 42dd03b21 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] discards 9c2cdea2b 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 3066a416c 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 5c4b3d0bf 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards c5b366004 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards ebeb715f5 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards e27ae96c1 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards d75ff0081 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 605603cbd 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 5cbe4386c 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards f13c88c67 43: onsuccess: 7: Successful build after gcc: 2 commits discards 134cdc262 42: onsuccess: 7: Successful build after baseline build: no n [...] discards 45c5011a1 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards e01028825 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 28986ee55 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits discards d55655b7a 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards 563e11974 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 2a994227c 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 0bd61d968 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 7d983b2ec 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 7425ebb26 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 16c0577b9 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 1737cd1c9 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 8c7b8a013 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards bfa703dbc 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 27f280c88 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 8a7c9e0e7 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards a6085133c 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 08b3b99ec 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 0844e9f4a 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 969910196 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards f0b6a82d2 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 172a9a5ba 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6afe6e6d7 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 58452bcdd 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 8597778a9 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1820ebf08 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards faf8fed1c 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d015985fb 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards f22bfe65d 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards ca929676c 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6db2ca82f 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e498a68cb 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e373159b3 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 65f681604 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1e7f1bc66 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1ae139362 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c3c64b226 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d4ca95ed8 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 6479d85aa 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3843c3b43 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 45e0f5c25 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new fc1491857 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 99d7c834f 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2a2abf74e 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 8e1c71e06 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a5446a30b 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 7ae8ec1ff 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 022af0278 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 041e202b2 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 84fae595a 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 732815c6a 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new fdd91fb13 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 4275bac40 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 607d25ecc 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new cd4585977 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new a61b994cc 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 4856b2c48 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new f60b8aae4 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 5fc0e14a0 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new acf8dfab9 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new cbfedde46 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7bc561f95 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 77b30d5f1 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new ff0a489d1 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 2dd22db9b 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new c024811b6 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new 338e03928 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits new 57c8eb425 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 2e6408952 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new a40a66c2a 42: onsuccess: 7: Successful build after baseline build: no n [...] new 83a581875 43: onsuccess: 7: Successful build after gcc: 2 commits new bd9f696a6 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new 8e7911360 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 5e63cfe06 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 42b3de2bd 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 795fbc104 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new e6a8be295 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new e3171bb92 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new ed8bebfbb 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 97ecccb06 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 23d49f0b8 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] new 2280cdece 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 0734d7961 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 4f87930e8 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new c4aa7807d 57: onsuccess: 7: Successful build after gcc: 7 commits new 1b013e8eb 58: onsuccess: 7: Successful build after glibc: 2 commits new bc4b3449a 59: force: 7: Successful build after gcc: 2 commits new b79ef45bc 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new f97f478ae 61: onsuccess: 4: Successful build after gcc: 15 commits new addf298b2 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new ca4aa96ea 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new 3ff9cd38a 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new b28286d61 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 1186dfba2 66: onsuccess: 7: Successful build after gcc: 3 commits new 7a7c6290f 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 732821831 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 3c1db9c2f 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new bd70d72ec 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new c71e6cad3 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new 858997e14 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 2d00c0c4c 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7aa96f6c4 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 23a257327 75: onsuccess: 7: Successful build after linux: 44 commits new 34e94d5fa 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new ef92cee0e 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new 062c93c1d 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 497ec6233 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new a1f92afb0 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new b62d7372e 81: onsuccess: 7: Successful build after gcc: 2 commits new 32e211287 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 63302332c 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new e8d925d38 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 0822b650a 85: onsuccess: 7: Success after gcc: 9 commits new 184e03588 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 59d84f563 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 42073c882 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 8f4855f10 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 6a18492c5 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new e0e01b817 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 6317cb428 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 46cd8c12e 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] new e26323daf 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 587904de6 95: onsuccess: #1529: 7: Success after baseline build: no new [...] new dba7a9c16 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] new 5419b4f1f 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] new 2d3ce6250 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 99bed98f3 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] new 6db799019 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] new a06c5a2eb 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 103a8a1c4 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] new 379ec0de0 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] new 4397cc878 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new e9a3b76ed 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] new f58658e5d 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 397265f8d 107: onsuccess: #1618: 7: Success after gcc: 2 commits new a6c9d0abd 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] new 88883432c 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/gd [...] 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 (04b6801f9) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 1624 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 29840 -> 29644 bytes 05-build_abe-stage1/console.log.xz | Bin 90672 -> 90536 bytes 07-build_abe-linux/console.log.xz | Bin 8672 -> 8304 bytes 08-build_abe-glibc/console.log.xz | Bin 233540 -> 233184 bytes 09-build_abe-stage2/console.log.xz | Bin 226552 -> 222884 bytes 10-build_abe-gdb/console.log.xz | Bin 37112 -> 37232 bytes 11-build_abe-qemu/console.log.xz | Bin 31664 -> 31572 bytes 12-check_regression/console.log.xz | Bin 2148 -> 2704 bytes 13-update_baseline/console.log | 36 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++++++++++------------------ 20 files changed, 44 insertions(+), 44 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-mainline-allyesconfig updated (e4f4a6659 -> 38153fed7)

by git＠git.linaro.org

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-release-arm-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from e4f4a6659 14: onsuccess: #447: 20867: Success after binutils/llvm/linux [...] new 38153fed7 15: onsuccess: #448: 20867: Success after binutils/llvm/linux [...] The 1 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 1700 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 29888 -> 29940 bytes 04-build_kernel_llvm/console.log.xz | Bin 62724 -> 62800 bytes 05-build_abe-qemu/console.log.xz | Bin 31292 -> 31336 bytes 06-build_linux/console.log.xz | Bin 4544 -> 4500 bytes 08-check_regression/console.log.xz | Bin 2844 -> 3292 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 16 files changed, 23 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (ca92124f5 -> e5c4e1ae8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards ca92124f5 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddeed [...] discards 918dd66db 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/gl [...] discards 6ab324da4 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 41173fe03 102: force: #1551: 1: Failure after gcc: 306 commits discards eb07510ab 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 3b82ba05c 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] discards c64530c13 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards b828b7013 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] discards d43de639d 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards a38fbb374 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards aa492c0fe 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 6a1a85125 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 91905a3e7 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards ef73faab4 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 57bc3f873 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 88a35f87d 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 46fc0fb6e 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards b62f09fb5 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards ae50d31ae 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards f383e8cb3 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 50b220d50 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards 18971626f 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards bb44be56f 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards c65fe1c15 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards 45ada461e 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards c83e1780e 80: onsuccess: 7: Successful build after linux: 44 commits discards 8623fcf72 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 480e9c815 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] discards 3bfa358cb 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 4a62bed60 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards abecf3a7a 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards 4c4ef4b33 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 56ded0cc8 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 7f08e61db 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 15c8f4345 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 2728756e5 70: onsuccess: 7: Successful build after gcc: 4 commits discards 3a23c44d5 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 0fcd65981 68: onsuccess: 7: Successful build after linux: 6 commits discards d664223a9 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] discards c914fc3b9 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] discards 0e4f869be 65: onsuccess: 7: Successful build after binutils: 3 commits discards bbc1a508a 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards 33ffe9d4a 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 81360b523 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 3e892cfe0 61: onsuccess: 4: Successful build after gcc: 5 commits discards c31f5c843 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards 1e87f9307 59: force: 7: Successful build after gcc: 3 commits discards bff7ae527 58: onsuccess: 7: Successful build after glibc: 2 commits discards d534a58aa 57: onsuccess: 7: Successful build after gcc: 7 commits discards b67a39c0f 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 8fe01238f 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 072674471 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards 55d8eb86d 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 11 [...] discards 42690b36e 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 commits discards a3faea247 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 386b0ff31 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 4fc4d438b 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards bfbc0c254 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 447d5f469 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards d1b7e3a9f 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 6eb199a7c 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 5a4f69053 44: onsuccess: 7: Successful build after linux: 34 commits discards 1035a8b53 43: onsuccess: 7: Successful build after gcc: 2 commits discards 8df2ae890 42: onsuccess: 7: Successful build after baseline build: no n [...] discards 28256d12b 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards b3f09243d 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 1f24de0cd 39: onsuccess: 7: Successful build after gcc: 2 commits discards 31061df2d 38: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 257572bb4 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards d14d0d035 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 729027afd 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 51f77b8b8 34: onsuccess: 7: Successful build after gcc: 3 commits discards 853dfe9ac 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 7fe178b8a 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards dac27abf2 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 2b9c6e357 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits discards bb2fa943d 29: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 817c095e5 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards abd8d86c3 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 0b3c9df02 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 44ee5304c 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 0d80a24c6 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e94fb442c 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards a890b3b71 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards f08e96f29 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 925c1d615 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e0516de6b 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards c97f77b93 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 87a79285e 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 01b0a5861 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 23b156a42 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e049fed1f 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d11234bac 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 20e5b80b5 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 2fb09fb47 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d05272af4 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1220ce70b 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards f92705a26 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d31a1794e 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e9873b911 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards db4ae882c 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9264e73e0 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 200e01419 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1d8af85f4 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 16fac0bf5 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1fad067f5 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1d401cdce 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 4416c3e12 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 03844ac5d 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new b2e2ce9d2 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a47f3b257 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 194f45d10 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new b29a5c62a 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 667e0a50d 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 10a77fa9c 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 78c09da59 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new dc54371ad 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 778d691a8 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 435f2f28c 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9d1904546 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 391053473 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new ffeba14ae 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 7eefa17a9 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 4f93bdd74 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 77f6f5504 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new dffe74a60 29: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new ca940b10d 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits new 31aedec35 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 9462a4c79 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new bd1a5acb3 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 2da9ba46b 34: onsuccess: 7: Successful build after gcc: 3 commits new df0cc3788 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 2460a5925 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new eb5404794 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 86d353624 38: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new db64e2c23 39: onsuccess: 7: Successful build after gcc: 2 commits new dcec0d60a 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new e3045c6b4 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new a86b62fb1 42: onsuccess: 7: Successful build after baseline build: no n [...] new f727e48e8 43: onsuccess: 7: Successful build after gcc: 2 commits new e855ed53c 44: onsuccess: 7: Successful build after linux: 34 commits new ec45a9207 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new cdaf8b8d7 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new b199863f5 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new fcee221dc 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new f133f46a5 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 2e4f76ede 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new d177348ec 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 90b4f560a 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 commits new 34af3c700 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 11 [...] new 624defd97 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new b661023e0 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 29136c26b 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 3e799ddf1 57: onsuccess: 7: Successful build after gcc: 7 commits new d09b7911c 58: onsuccess: 7: Successful build after glibc: 2 commits new af5313569 59: force: 7: Successful build after gcc: 3 commits new 880c9bb4c 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new 9df252cf2 61: onsuccess: 4: Successful build after gcc: 5 commits new 449a972e7 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 1a5556804 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new e72b97df1 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new a1e04f42e 65: onsuccess: 7: Successful build after binutils: 3 commits new 9b58551ee 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] new c0d1aa8aa 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] new 1b0c44e07 68: onsuccess: 7: Successful build after linux: 6 commits new c846bc87e 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 1c8059fcd 70: onsuccess: 7: Successful build after gcc: 4 commits new 6a4b7d7b2 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 54a2a148a 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 43a7a4a73 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 1a3085888 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 636a35199 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new 036040a81 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 81bf6f7d1 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new dca52e982 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] new fe09a2f49 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new aa37489d2 80: onsuccess: 7: Successful build after linux: 44 commits new 452ebdda9 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 91a99a59f 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new d66fc23a8 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new b4eecbace 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 773b19b9c 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new d81bba1ff 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new f856b77dc 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new fe3c70dc5 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 66846a99e 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 291862f1b 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new a7f60a92d 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new f3107ee46 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 0472bd11e 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 2334f4674 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new b4cf283ee 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new c41185535 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new e321bb81c 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 7664c5265 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] new c07f2e50b 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 317f229c5 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] new aa4d73164 101: onsuccess: #1547: 7: Success after binutils: 82 commits new ac52a0007 102: force: #1551: 1: Failure after gcc: 306 commits new bd2c1b072 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 23265f9dc 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/gl [...] new ccdf5fc42 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddeed [...] new e5c4e1ae8 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/gd [...] 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 (ca92124f5) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 1652 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 30136 -> 30028 bytes 05-build_abe-stage1/console.log.xz | Bin 72212 -> 71812 bytes 07-build_abe-linux/console.log.xz | Bin 8668 -> 8300 bytes 08-build_abe-glibc/console.log.xz | Bin 240260 -> 240240 bytes 09-build_abe-stage2/console.log.xz | Bin 203048 -> 203304 bytes 10-build_abe-gdb/console.log.xz | Bin 37372 -> 37436 bytes 11-build_abe-qemu/console.log.xz | Bin 32108 -> 31804 bytes 12-check_regression/console.log.xz | Bin 2156 -> 2768 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 ++++++++++---------- 20 files changed, 58 insertions(+), 58 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022