Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-allmodconfig updated (f0c9c9d359 -> a3e0e6e5d4)

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-master-aarch64-next-allmodconfig in repository toolchain/ci/base-artifacts. from f0c9c9d359 22: onsuccess: #549: all: Success after qemu: 5 commits new a3e0e6e5d4 23: force: #550: all: Success after llvm: 157 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 1712 -> 1640 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30544 -> 30380 bytes 04-build_kernel_llvm/console.log.xz | Bin 65756 -> 65048 bytes 05-build_abe-qemu/console.log.xz | Bin 31668 -> 31000 bytes 06-build_linux/console.log.xz | Bin 3136 -> 3084 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 2936 -> 2964 bytes 09-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +++++++------- 15 files changed, 13 insertions(+), 13 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-stable-allmodconfig updated (3e7d125b0c -> e7e47aaefa)

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-master-arm-stable-allmodconfig in repository toolchain/ci/base-artifacts. from 3e7d125b0c 27: onsuccess: #499: 36: Success after llvm: 2 commits new e7e47aaefa 28: onsuccess: #500: 22763: Success after binutils/llvm/linu [...] 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 1696 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30372 -> 29724 bytes 04-build_kernel_llvm/console.log.xz | Bin 62404 -> 64304 bytes 05-build_abe-qemu/console.log.xz | Bin 30168 -> 30620 bytes 06-build_linux/console.log.xz | Bin 3768 -> 4588 bytes 08-check_regression/console.log.xz | Bin 2772 -> 4408 bytes 08-check_regression/mail-body.txt | 9 +-------- 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 | 11 ++--------- mail/mail-subject.txt | 2 +- manifest.sh | 31 +++++++++++++++++-------------- results | 2 +- 18 files changed, 28 insertions(+), 39 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[binutils-gdb] branch master updated (98847c1e38b -> e875475e19d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 98847c1e38b Treat Character as a discrete type in Ada new e875475e19d gdb: remove trailing spaces in README 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: gdb/README | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap updated (3b38f007a7 -> 8d3ce50bb6)

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 3b38f007a7 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] discards c95c27199c 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards ea7d32b33e 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards 06b7451ae8 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards f6ad800655 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards 9b9263957a 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards c3657bdca3 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards 34419b4a35 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards 43c33e05cf 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards 45f5da6719 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards 294b682dbc 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards bc4ed3039b 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards 53ec0861d1 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards 41477cd81f 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards e3e6364b84 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards b4cc7c9ecd 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards e5adde2946 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 012f927948 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards a459ad47a8 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards 9dc6f8ec53 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards c620ca5615 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 8a60830e5c 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 3db4358af4 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 01e2cb4887 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards 1db12fed60 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 6c8e5248b9 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards c58dca1ab4 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards 22b6cb9f3d 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 6e1cb3bc96 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards ae8fad7e73 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards e7a7df7cc9 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards df4ea85c38 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 78c8fc3bbf 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 1f74d9fcdf 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards 2194e01d56 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards 8ab246f469 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 8b855324b0 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards 1ab8bda371 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards bb65bdd14e 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 0dbbff286d 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards 5a10233fc0 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 55e5463dfe 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards c60019357f 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards 8ccba99bc1 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 5b92545e49 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards aeab17ffef 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 86ef9fde53 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 68004965a4 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 36db4d76e7 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 93f47e7c31 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards d2438795ba 88: onsuccess: 1: Success after gcc: 20 commits discards f0bdd1f642 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards f0b412bedd 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards eab8bd9bf5 85: onsuccess: 2: Success after binutils: 4 commits discards 29549835d5 84: onsuccess: 2: Success after gcc: 9 commits discards 58d952bbab 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards a3c5c836cb 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards d404924ebf 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards e553561f3f 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 6eebff1294 79: onsuccess: 1: Successful build after gcc: 3 commits discards a69ba7ef9b 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 158645ae27 77: force: 2: Successful build after gcc: 32 commits discards b270f546dd 76: onsuccess: 2: Successful build after binutils: 10 commits discards 9563688c8b 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards c6db2df7be 74: onsuccess: 2: Successful build after gcc: 13 commits discards 611b87ebf7 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 03d2b2a6aa 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 577a9cc7a7 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 4034001bdc 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 8b0131a7ec 69: onsuccess: 2: Successful build after baseline build: no [...] discards 3f7ea3653b 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 33cad3eccc 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards ccd572de74 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 75c26299b2 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 9df407f412 64: onsuccess: 2: Successful build after gcc: 7 commits discards 0a12daac8d 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 7975268b08 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 1aa673f3f3 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards bf566e4fb3 60: onsuccess: 1: Successful build after gcc: 15 commits discards fe38878f86 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 1fcffc8a43 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards 9f0a742486 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards ec6cd5399c 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 669ede2ca1 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 8bc9c5f764 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards f0e4db7377 53: onsuccess: 2: Successful build after gcc: 5 commits discards 3ca361e2b1 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 6317a6298f 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 4dfa2d9be5 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards bf9029ffa4 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 2a07952819 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 10c47d0ff5 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 3f9a58ed66 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 1f58250cbf 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards 4eeca6dda8 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 93b1ad8d9b 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards cd57c02bde 42: onsuccess: 2: Successful build after gcc: 2 commits discards 71a4b025c9 41: onsuccess: 2: Successful build after baseline build: no [...] discards 4104cc7482 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 62239f5b34 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 3b93f931c7 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 5f6b7353ec 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 457a838674 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 0e1e68c1c7 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 64bb8724ae 41: onsuccess: 2: Successful build after baseline build: no [...] new c3ed263c57 42: onsuccess: 2: Successful build after gcc: 2 commits new 398b451d1c 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new 30cb9ce6b9 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ba5c9817de 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 6dced22d8c 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new fe5695379d 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 41072eecf5 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new c7bae43b54 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 121679d000 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new f91be039ee 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 5428c6e577 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new eedd21a439 53: onsuccess: 2: Successful build after gcc: 5 commits new 0b00dffb7e 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new dc7c0110ee 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 6453a596f2 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new ee74832be8 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new c8636c2042 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new 293b7ea278 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 07f02e7124 60: onsuccess: 1: Successful build after gcc: 15 commits new 1f9eeee305 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 341a54ecc5 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ea643cbd23 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 8649af42c6 64: onsuccess: 2: Successful build after gcc: 7 commits new c8f8552414 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new bff996804f 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new d063059b07 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 4777b33d30 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 3ab930845f 69: onsuccess: 2: Successful build after baseline build: no [...] new 1e77c6bca6 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 63524d1fa4 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new e7af0b45f2 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new e9fdbbdbb2 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 2ca9e6b3c1 74: onsuccess: 2: Successful build after gcc: 13 commits new 6d20251af2 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new c51b03f19d 76: onsuccess: 2: Successful build after binutils: 10 commits new 9c3ed7c27f 77: force: 2: Successful build after gcc: 32 commits new 7c43b843ab 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 9809502afe 79: onsuccess: 1: Successful build after gcc: 3 commits new 1e5110bf00 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 372b2ac658 81: onsuccess: 2: Success after binutils/gcc: 16 commits new a557f4dbe0 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 47c3a850bc 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 9ade228813 84: onsuccess: 2: Success after gcc: 9 commits new bdce2ac01a 85: onsuccess: 2: Success after binutils: 4 commits new 2506632d75 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new 0771183c77 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new 283a417612 88: onsuccess: 1: Success after gcc: 20 commits new 3819152073 89: onsuccess: 2: Success after binutils/gcc: 39 commits new c9a019a51a 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 48712973d6 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 62dcb6be60 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new b11ee28046 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new 8500ee16fa 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new 55c83b6936 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 16371344e0 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 52ca284001 97: onsuccess: #1481: 2: Success after gcc: 8 commits new a529f2b8be 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new a3a92098d5 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 44b17f7e59 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new e12789585e 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new 7de3c09bd6 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new e21b53fd9a 103: onsuccess: #1524: 2: Success after gcc: 2 commits new a250a2c011 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new ea35bbde20 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 585dca773b 106: onsuccess: #1527: 2: Success after gcc: 2 commits new f4101169d3 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new 31da94eca3 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new a36acc7e59 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 0fdf9314de 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new d0c4b4420b 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new e006d20a7e 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 520f617b8c 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new d07fb31402 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 6466e5b73b 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 8c76e28b32 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 67c1011b89 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new 6736bd40b0 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 2c66720dc2 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new 655630692b 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 4220f91247 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new 1aa09c9e24 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 8bf71148ba 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 099d426846 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new ab3e7552c9 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new d488cadaff 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new 55a005c03a 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new 4a60fef982 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new 28657532c0 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new 2df96e5982 130: onsuccess: #1554: 2: Success after gcc: 9 commits new 0611b2b6df 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new 5a81cdead8 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new ade2f0c447 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new 6fd16afad0 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new e53ef5c895 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new 85f9ef4d12 136: onsuccess: #1561: 2: Success after binutils: 3 commits new 97e24dd4bd 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new 2d7f49b62d 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] new 8d3ce50bb6 139: onsuccess: #1566: 1: Success after gcc: 5 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 (3b38f007a7) \ 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 1672 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 39184 -> 39048 bytes 05-build_abe-bootstrap/console.log.xz | Bin 83788 -> 81024 bytes 06-check_regression/console.log.xz | Bin 3328 -> 2856 bytes 06-check_regression/jira-body.txt | 2 +- 06-check_regression/mail-body.txt | 20 +- 06-check_regression/mail-subject.txt | 2 +- 06-check_regression/results.regressions | 11 - 06-check_regression/trigger-bisect | 2 - 06-check_regression/trigger-notify | 0 07-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 1061 ------------------------------- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 20 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 11 - 24 files changed, 66 insertions(+), 1160 deletions(-) delete mode 100644 06-check_regression/results.regressions delete mode 100644 06-check_regression/trigger-bisect delete mode 100644 06-check_regression/trigger-notify delete mode 100644 jenkins/jira-status.draft delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-allnoconfig updated (42d4df1d99 -> ac8f76c358)

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-allnoconfig in repository toolchain/ci/base-artifacts. from 42d4df1d99 10: onsuccess: #452: boot: Success after binutils/gcc/linux/ [...] new ac8f76c358 11: onsuccess: #453: boot: Success after binutils/gcc/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 1688 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30568 -> 30432 bytes 04-build_abe-stage1/console.log.xz | Bin 72084 -> 72436 bytes 05-build_abe-qemu/console.log.xz | Bin 31068 -> 31104 bytes 06-build_linux/console.log.xz | Bin 3332 -> 3284 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4404 -> 4276 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 | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap updated (83e3847ac6 -> 3b38f007a7)

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 83e3847ac6 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards 114519ccf3 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards 11b1d26490 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards 9a9be68219 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards 91b6c7ae1f 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards ecc2220980 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards cb2b0c2159 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards 72219ccb76 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards ba00a90d6b 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards b09d1bf39d 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards 6107a98acc 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards 3c68bd0d12 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards 9a6d147db8 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards 1a60b73b97 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards ff1b94c33a 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards 032b3cfde7 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 9c2a7ad0ee 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards 99fbab5de1 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards f9ef2f9329 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards ce2a863b6c 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 3335ffd21c 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 0dcc4fd0d6 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 4290868587 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards 15ea156b8c 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 149585fb2e 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards 32baaf94b3 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards 8d0cf8b876 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 9eb377954a 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 327c5c382b 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 088d3777af 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards 932131948b 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 448fd30ffb 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 96fcd27eeb 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards 3b67dc52fd 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards 9ab13e424e 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards a79f912d38 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards ce7690a430 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards 38928ae750 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards b61e6c00df 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards a198e66a7e 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 687615bcb2 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards eecfccc6d7 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards aebc689fb0 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards e679ab4ecb 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 133a347da6 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 5f3c6791d3 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards dad3e0eb7a 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 97305f59de 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards adbb4d6961 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 81c2d4ddb4 88: onsuccess: 1: Success after gcc: 20 commits discards 8c160d131f 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards d91c975c90 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards 24e118a2f6 85: onsuccess: 2: Success after binutils: 4 commits discards afe8bfcbdc 84: onsuccess: 2: Success after gcc: 9 commits discards 5b5bf392d5 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 0f5d374cdf 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 1323827699 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards ffc08c2ba8 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 54133f7474 79: onsuccess: 1: Successful build after gcc: 3 commits discards b7f57ef072 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 24c445f6bf 77: force: 2: Successful build after gcc: 32 commits discards 2bd3a754ea 76: onsuccess: 2: Successful build after binutils: 10 commits discards 1cabecd014 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 0e1e07ab03 74: onsuccess: 2: Successful build after gcc: 13 commits discards b42747bc28 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards b1fec64e0a 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 0eea79fc8c 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 91b5a445c1 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards fc93483c88 69: onsuccess: 2: Successful build after baseline build: no [...] discards ae961cd9cb 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 384b9ed16c 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards e4d9ba0010 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 5bf4b901d4 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 8b9caae289 64: onsuccess: 2: Successful build after gcc: 7 commits discards 5cac00bd46 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 502397bd0c 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 67566a79c1 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 51ca05a10b 60: onsuccess: 1: Successful build after gcc: 15 commits discards a110822ce4 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 23cf5712c4 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards 272de95cf5 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 929b43ff21 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards ce24407efc 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 9202dd8a8e 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 96be7f36d4 53: onsuccess: 2: Successful build after gcc: 5 commits discards b41eeced20 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 0acf2bd610 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 4a82debf12 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 27345ecd99 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 7ba5e0cdc7 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 14f637e6dd 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 901cb7cda6 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards f7c3447c85 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards 774a02e743 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards e2f082ca5b 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards 96f419ebf5 42: onsuccess: 2: Successful build after gcc: 2 commits discards bc1ea137a6 41: onsuccess: 2: Successful build after baseline build: no [...] discards 81365b58db 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 3cbc004a1d 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 60dcc484f9 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 43fedade5d 37: onsuccess: 2: Successful build after gcc: 2 commits new 78bdc3170f 37: onsuccess: 2: Successful build after gcc: 2 commits new 3b93f931c7 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 62239f5b34 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 4104cc7482 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 71a4b025c9 41: onsuccess: 2: Successful build after baseline build: no [...] new cd57c02bde 42: onsuccess: 2: Successful build after gcc: 2 commits new 93b1ad8d9b 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new 4eeca6dda8 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 1f58250cbf 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 3f9a58ed66 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 10c47d0ff5 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 2a07952819 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new bf9029ffa4 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 4dfa2d9be5 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 6317a6298f 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 3ca361e2b1 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new f0e4db7377 53: onsuccess: 2: Successful build after gcc: 5 commits new 8bc9c5f764 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 669ede2ca1 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ec6cd5399c 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 9f0a742486 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 1fcffc8a43 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new fe38878f86 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new bf566e4fb3 60: onsuccess: 1: Successful build after gcc: 15 commits new 1aa673f3f3 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 7975268b08 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 0a12daac8d 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 9df407f412 64: onsuccess: 2: Successful build after gcc: 7 commits new 75c26299b2 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new ccd572de74 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 33cad3eccc 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 3f7ea3653b 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 8b0131a7ec 69: onsuccess: 2: Successful build after baseline build: no [...] new 4034001bdc 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 577a9cc7a7 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 03d2b2a6aa 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 611b87ebf7 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new c6db2df7be 74: onsuccess: 2: Successful build after gcc: 13 commits new 9563688c8b 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new b270f546dd 76: onsuccess: 2: Successful build after binutils: 10 commits new 158645ae27 77: force: 2: Successful build after gcc: 32 commits new a69ba7ef9b 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 6eebff1294 79: onsuccess: 1: Successful build after gcc: 3 commits new e553561f3f 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new d404924ebf 81: onsuccess: 2: Success after binutils/gcc: 16 commits new a3c5c836cb 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 58d952bbab 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 29549835d5 84: onsuccess: 2: Success after gcc: 9 commits new eab8bd9bf5 85: onsuccess: 2: Success after binutils: 4 commits new f0b412bedd 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new f0bdd1f642 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new d2438795ba 88: onsuccess: 1: Success after gcc: 20 commits new 93f47e7c31 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 36db4d76e7 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 68004965a4 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 86ef9fde53 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new aeab17ffef 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new 5b92545e49 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new 8ccba99bc1 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new c60019357f 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 55e5463dfe 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 5a10233fc0 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 0dbbff286d 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new bb65bdd14e 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new 1ab8bda371 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new 8b855324b0 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 8ab246f469 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 2194e01d56 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 1f74d9fcdf 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 78c8fc3bbf 106: onsuccess: #1527: 2: Success after gcc: 2 commits new df4ea85c38 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new e7a7df7cc9 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new ae8fad7e73 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 6e1cb3bc96 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 22b6cb9f3d 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new c58dca1ab4 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 6c8e5248b9 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new 1db12fed60 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 01e2cb4887 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 3db4358af4 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 8a60830e5c 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new c620ca5615 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 9dc6f8ec53 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new a459ad47a8 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 012f927948 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new e5adde2946 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new b4cc7c9ecd 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new e3e6364b84 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new 41477cd81f 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new 53ec0861d1 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new bc4ed3039b 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new 294b682dbc 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new 45f5da6719 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new 43c33e05cf 130: onsuccess: #1554: 2: Success after gcc: 9 commits new 34419b4a35 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new c3657bdca3 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new 9b9263957a 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new f6ad800655 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new 06b7451ae8 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new ea7d32b33e 136: onsuccess: #1561: 2: Success after binutils: 3 commits new c95c27199c 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new 3b38f007a7 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] 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 (83e3847ac6) \ 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 1656 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 38360 -> 39184 bytes 05-build_abe-bootstrap/console.log.xz | Bin 269504 -> 83788 bytes 06-check_regression/console.log.xz | Bin 2504 -> 3328 bytes 06-check_regression/jira-body.txt | 2 +- 06-check_regression/mail-body.txt | 15 +- 06-check_regression/mail-subject.txt | 2 +- 06-check_regression/results.regressions | 11 + 06-check_regression/trigger-bisect | 2 + 06-check_regression/trigger-notify | 0 07-update_baseline/console.log | 42 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 1061 +++++++++++++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 15 +- mail/mail-subject.txt | 2 +- manifest.sh | 12 +- results | 13 +- 24 files changed, 1154 insertions(+), 38 deletions(-) create mode 100644 06-check_regression/results.regressions create mode 100644 06-check_regression/trigger-bisect create mode 100644 06-check_regression/trigger-notify create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/interesting-commits] branch master updated (c06a15b -> 57d80b9)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from c06a15b Add entry b04208895fed34171eac6bafb60c90048eb1cb0c from https [...] new 57d80b9 Add entry b04208895fed34171eac6bafb60c90048eb1cb0c from https [...] 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: .../tcwg_gcc_bootstrap/master-aarch64-bootstrap/build_url | 2 +- .../last_good | 0 .../summary.txt | 0 .../tcwg_gcc_bootstrap/status.txt | 3 +++ 4 files changed, 4 insertions(+), 1 deletion(-) copy gcc/sha1/{953e08fde44a596e4ec2491efd15cd645e1ddc48 => b04208895fed34171eac6ba [...] copy gcc/sha1/b04208895fed34171eac6bafb60c90048eb1cb0c/tcwg_gcc_bootstrap/{master- [...] copy gcc/sha1/b04208895fed34171eac6bafb60c90048eb1cb0c/tcwg_gcc_bootstrap/{master- [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap updated (84293c4169 -> 83e3847ac6)

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 84293c4169 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards c617b4f2b3 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards c155b174e5 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards b311791d8e 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards 0ef80209a3 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards 79f0cfcced 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards f5c9175aee 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards 3735af67fa 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards d9a60a7f42 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards 0fe3ddcc8a 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards aee2e3aed2 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards 786d5abb19 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards a8c3d9cf73 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards d2694b1330 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards 0f1d2ddbc2 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 7ebb58ff9f 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards 7b73fa4044 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards 4527a2100a 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards 24d48aee7f 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards d8c4a759c4 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards a9d39d104c 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 07d7f8cb2f 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards 3f0d87f417 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards abc2180c5e 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards c1fe994f2d 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards c8bdef4094 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards c514874882 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 2a0eb1c03c 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 327512e19b 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards 7af8a74edd 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 6637cd9d3b 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards aea7a32945 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards 7eff3cb581 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards 6849cab5ca 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards e07da669e7 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards b97a4244b1 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards d24f1b6077 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 153af2adde 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards c0667641a9 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 05f0eb2dfa 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 0426b63700 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards f07e4552bb 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards e3597cd06f 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 2462ba46f4 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 88a732df7c 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 0313110a1b 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 28b90ab6d1 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards a2de5a278d 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 664a9dd562 88: onsuccess: 1: Success after gcc: 20 commits discards dca837b2c8 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards ae6926beba 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards 4f3dbb90da 85: onsuccess: 2: Success after binutils: 4 commits discards 41f967234e 84: onsuccess: 2: Success after gcc: 9 commits discards 86cfb827da 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 37b4764a1d 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 6a8e33bb5c 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 2f8923081b 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 0b77a71c8c 79: onsuccess: 1: Successful build after gcc: 3 commits discards 3ea405fd6d 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards dd8ec4d453 77: force: 2: Successful build after gcc: 32 commits discards 77b3646f6b 76: onsuccess: 2: Successful build after binutils: 10 commits discards 17fd198e92 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 5d29f346d6 74: onsuccess: 2: Successful build after gcc: 13 commits discards 4df9c337b6 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 1f91d63c75 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 9249e6a149 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 5d547438b5 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards b1ea0c7800 69: onsuccess: 2: Successful build after baseline build: no [...] discards aa60714c32 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards d3be365cc2 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 9750c93ad2 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 23c5e3e43f 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards d262b3997c 64: onsuccess: 2: Successful build after gcc: 7 commits discards 25b996c134 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 72fdd5d387 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 08f8641639 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 6b1db3bf52 60: onsuccess: 1: Successful build after gcc: 15 commits discards 6f68d1f3f6 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 7e1f8e581d 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards c599c3a0b2 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 5d3255499a 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 4c531f1f64 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 8afdd04fcb 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 89cc525855 53: onsuccess: 2: Successful build after gcc: 5 commits discards f983165c3e 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards bd202ca332 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 163454b7dc 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards e3c1ea949b 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 3dfa727e4a 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 9ad3ac9911 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 1c5deb07ca 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards e1ba7f6d31 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards e1ccc1bbba 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 6403dc9d49 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards e255b6c676 42: onsuccess: 2: Successful build after gcc: 2 commits discards 509ee1f28c 41: onsuccess: 2: Successful build after baseline build: no [...] discards 6f791e6c57 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards eccc89220a 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 5aeb1101f7 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards e049625997 37: onsuccess: 2: Successful build after gcc: 2 commits discards 977da20844 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits new c6b0429c74 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 43fedade5d 37: onsuccess: 2: Successful build after gcc: 2 commits new 60dcc484f9 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 3cbc004a1d 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 81365b58db 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new bc1ea137a6 41: onsuccess: 2: Successful build after baseline build: no [...] new 96f419ebf5 42: onsuccess: 2: Successful build after gcc: 2 commits new e2f082ca5b 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new 774a02e743 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new f7c3447c85 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 901cb7cda6 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 14f637e6dd 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 7ba5e0cdc7 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 27345ecd99 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 4a82debf12 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 0acf2bd610 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new b41eeced20 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 96be7f36d4 53: onsuccess: 2: Successful build after gcc: 5 commits new 9202dd8a8e 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ce24407efc 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 929b43ff21 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 272de95cf5 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 23cf5712c4 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new a110822ce4 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 51ca05a10b 60: onsuccess: 1: Successful build after gcc: 15 commits new 67566a79c1 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 502397bd0c 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 5cac00bd46 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 8b9caae289 64: onsuccess: 2: Successful build after gcc: 7 commits new 5bf4b901d4 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new e4d9ba0010 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 384b9ed16c 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ae961cd9cb 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new fc93483c88 69: onsuccess: 2: Successful build after baseline build: no [...] new 91b5a445c1 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 0eea79fc8c 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new b1fec64e0a 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new b42747bc28 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 0e1e07ab03 74: onsuccess: 2: Successful build after gcc: 13 commits new 1cabecd014 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 2bd3a754ea 76: onsuccess: 2: Successful build after binutils: 10 commits new 24c445f6bf 77: force: 2: Successful build after gcc: 32 commits new b7f57ef072 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 54133f7474 79: onsuccess: 1: Successful build after gcc: 3 commits new ffc08c2ba8 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 1323827699 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 0f5d374cdf 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 5b5bf392d5 83: onsuccess: 2: Success after binutils/gcc: 7 commits new afe8bfcbdc 84: onsuccess: 2: Success after gcc: 9 commits new 24e118a2f6 85: onsuccess: 2: Success after binutils: 4 commits new d91c975c90 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new 8c160d131f 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new 81c2d4ddb4 88: onsuccess: 1: Success after gcc: 20 commits new adbb4d6961 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 97305f59de 90: onsuccess: #1472: 2: Success after gcc: 2 commits new dad3e0eb7a 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 5f3c6791d3 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 133a347da6 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new e679ab4ecb 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new aebc689fb0 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new eecfccc6d7 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 687615bcb2 97: onsuccess: #1481: 2: Success after gcc: 8 commits new a198e66a7e 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new b61e6c00df 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 38928ae750 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new ce7690a430 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new a79f912d38 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 9ab13e424e 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 3b67dc52fd 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 96fcd27eeb 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 448fd30ffb 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 932131948b 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new 088d3777af 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 327c5c382b 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 9eb377954a 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 8d0cf8b876 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 32baaf94b3 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 149585fb2e 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new 15ea156b8c 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 4290868587 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 0dcc4fd0d6 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 3335ffd21c 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new ce2a863b6c 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new f9ef2f9329 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new 99fbab5de1 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 9c2a7ad0ee 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new 032b3cfde7 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new ff1b94c33a 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 1a60b73b97 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new 9a6d147db8 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new 3c68bd0d12 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new 6107a98acc 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new b09d1bf39d 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new ba00a90d6b 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new 72219ccb76 130: onsuccess: #1554: 2: Success after gcc: 9 commits new cb2b0c2159 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new ecc2220980 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new 91b6c7ae1f 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new 9a9be68219 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new 11b1d26490 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new 114519ccf3 136: onsuccess: #1561: 2: Success after binutils: 3 commits new 83e3847ac6 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] 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 (84293c4169) \ 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 1660 -> 1656 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 38468 -> 38360 bytes 05-build_abe-bootstrap/console.log.xz | Bin 272984 -> 269504 bytes 06-check_regression/console.log.xz | Bin 2608 -> 2504 bytes 07-update_baseline/console.log | 44 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++------- 12 files changed, 36 insertions(+), 36 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-stable-allnoconfig updated (cb5cc94911 -> 496544f74e)

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-stable-allnoconfig in repository toolchain/ci/base-artifacts. from cb5cc94911 10: onsuccess: #235: all: Success after binutils/llvm/linux/ [...] new 496544f74e 11: onsuccess: #236: all: 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 1696 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 29996 -> 30012 bytes 04-build_kernel_llvm/console.log.xz | Bin 64340 -> 63860 bytes 05-build_abe-qemu/console.log.xz | Bin 31264 -> 30904 bytes 06-build_linux/console.log.xz | Bin 3384 -> 3388 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4068 -> 4200 bytes 09-update_baseline/console.log | 8 ++++---- 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 | 32 ++++++++++++++++---------------- 18 files changed, 28 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (03f3365742a -> db288230db5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 03f3365742a RISC-V: Add ABI-defined RVV types. new db288230db5 i386: Mark XMM4-XMM6 as clobbered by encodekey128/encodekey256 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: gcc/config/i386/predicates.md | 20 ++++++++++---------- gcc/config/i386/sse.md | 4 ++-- .../gcc.target/i386/keylocker-encodekey128.c | 1 - .../gcc.target/i386/keylocker-encodekey256.c | 1 - 4 files changed, 12 insertions(+), 14 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022