Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-lts-defconfig updated (37e1ce0af -> cb6e3f687)

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-aarch64-lts-defconfig in repository toolchain/ci/base-artifacts. from 37e1ce0af 11: onsuccess: #254: boot: Success after binutils/llvm/linux/ [...] new cb6e3f687 12: onsuccess: #255: boot: 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 1716 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30864 -> 30196 bytes 04-build_kernel_llvm/console.log.xz | Bin 65784 -> 64272 bytes 05-build_abe-qemu/console.log.xz | Bin 32676 -> 31760 bytes 06-build_linux/console.log.xz | Bin 3472 -> 3956 bytes 07-boot_linux/console.log.xz | Bin 6104 -> 6052 bytes 08-check_regression/console.log.xz | Bin 4416 -> 4260 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 | 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 (22b11c8e6 -> a5064c949)

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 22b11c8e6 155: onsuccess: #1582: 2: Success after binutils/gcc: 15 commits discards 17230b9af 154: onsuccess: #1581: 2: Success after binutils/gcc: 11 commits discards fc723ebd2 153: onsuccess: #1580: 2: Success after binutils/gcc: 2 commits discards 0da65ecc7 152: onsuccess: #1579: 2: Success after gcc: 2 commits discards d003c4eff 151: onsuccess: #1578: 2: Success after gcc: 2 commits discards cd2fdc90c 150: onsuccess: #1577: 2: Success after gcc: 3 commits discards 6fd4e5d93 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 commits discards 79dd2176e 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits discards df5a81719 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits discards b3a0e0eb3 146: onsuccess: #1573: 2: Success after binutils: 7 commits discards f12cfb182 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits discards 8e9f81990 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits discards e51914175 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits discards c3450b73c 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-292 [...] discards 247bf5fe6 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits discards 345c85ed3 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits discards d587544d2 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards 2d69bdee5 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-gb [...] discards 09ffe0249 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g8 [...] discards 454d36de6 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards 35471273e 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards e65c93ac5 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards c1a562f90 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards 46cc46e40 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards 7b72e4cce 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards 6853aeaab 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards 4a39755e8 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-283 [...] discards 97b198803 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards f6ff83425 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-283 [...] discards 3d574ce45 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-20 [...] discards 29da3a6b1 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards 9f67dbd66 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards 0e45d967b 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards fe94950d1 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards dca7b4634 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards 07451cdca 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards eeaa7d5e4 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards d9f59c382 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 4628b6c3f 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 947589be9 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards e60104e45 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards aad77732c 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 7f8a966a5 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards e75f8687f 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards 19f39a905 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 309a26be3 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards f3c8f1507 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 1d806b567 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-271 [...] discards c1454feab 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 34e8e375d 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 8ac56721e 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards a71881fa3 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards dfd67ecca 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 01cf4f7ba 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards 8841ba178 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards 02147de5a 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 626c72826 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards e7c3ea92f 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards be280762a 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 5d11342ca 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards af9f972d9 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 9cc667a70 94: onsuccess: #1476: 2: Success after baseline build: no new [...] discards 6b4fe9eaf 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-2393 [...] discards 672a654ad 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards a92c25328 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 67a468cc3 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 5ab19a073 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards bb1468045 88: onsuccess: 1: Success after gcc: 20 commits discards b1ecd35df 87: force: 1: Failure after gcc: Fix up dump_printf_loc forma [...] discards 0d4352ec6 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 w [...] discards d77400479 85: onsuccess: 2: Success after binutils: 4 commits discards fa38cca73 84: onsuccess: 2: Success after gcc: 9 commits discards 0c9773cd8 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards c421cff2b 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 73aa3c4f3 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards a69b9c9f9 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 075d40893 79: onsuccess: 1: Successful build after gcc: 3 commits discards 25161b783 78: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] discards aa4fe7e4f 77: force: 2: Successful build after gcc: 32 commits discards b24e3077a 76: onsuccess: 2: Successful build after binutils: 10 commits discards 5de7dfe93 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards f26458c51 74: onsuccess: 2: Successful build after gcc: 13 commits discards 2129f3ef0 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards c2d204422 72: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] discards 430279652 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 4dceb06e2 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards b3656ac48 69: onsuccess: 2: Successful build after baseline build: no n [...] discards b899ab7e9 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 556df20d5 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards f9cd98eec 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards ca9bc11b5 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 004b37670 64: onsuccess: 2: Successful build after gcc: 7 commits discards 615fe50c9 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 91fd0175e 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards b34723e8e 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 7b0878f99 60: onsuccess: 1: Successful build after gcc: 15 commits discards 693d4b816 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] discards ab5cf88ef 58: force: 2: Successful build after gcc: tree.cc: Fix optimi [...] discards 9aa137682 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards f41574a4d 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 40d358c4e 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 1df887d85 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new f103ec288 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 34b836b43 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 0f1337ced 58: force: 2: Successful build after gcc: tree.cc: Fix optimi [...] new 6ffe8a732 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] new 7e54dda58 60: onsuccess: 1: Successful build after gcc: 15 commits new 69e36aa13 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 203725763 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 07aa17c63 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 1aa884d67 64: onsuccess: 2: Successful build after gcc: 7 commits new ad2fa447d 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new a376725ae 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new e117f8109 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 2ebbe6e84 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new a4a8e14a2 69: onsuccess: 2: Successful build after baseline build: no n [...] new 4c4ca49e3 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new f4cef4f41 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 3ba1cca41 72: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] new 9fa27d3b8 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new bebdcc175 74: onsuccess: 2: Successful build after gcc: 13 commits new bc7e1483c 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 3c8c524e4 76: onsuccess: 2: Successful build after binutils: 10 commits new 793478953 77: force: 2: Successful build after gcc: 32 commits new 7a264149d 78: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] new 801e7b0ea 79: onsuccess: 1: Successful build after gcc: 3 commits new 980ecf0a1 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 3e1a3416c 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 3996d2baa 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 3d0f269bf 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 37af5167e 84: onsuccess: 2: Success after gcc: 9 commits new 095fd49f0 85: onsuccess: 2: Success after binutils: 4 commits new d545ffaf2 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 w [...] new 91bdd27cc 87: force: 1: Failure after gcc: Fix up dump_printf_loc forma [...] new 1693f6b62 88: onsuccess: 1: Success after gcc: 20 commits new d8b82c983 89: onsuccess: 2: Success after binutils/gcc: 39 commits new a18773fd6 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 242c8e60b 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 244c8c319 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 0a228d838 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-2393 [...] new fc70fdda5 94: onsuccess: #1476: 2: Success after baseline build: no new [...] new 3933dd4eb 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 540cad5fd 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 40c8ed80b 97: onsuccess: #1481: 2: Success after gcc: 8 commits new a5e3b9d9e 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 818f8cdd2 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 82b5c863d 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new c6f7cc5bf 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new f876a1b75 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new ccf99a189 103: onsuccess: #1524: 2: Success after gcc: 2 commits new c125bb168 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 17c8f564c 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 4c3f4da38 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 1c4f9c47b 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new 75c2243cd 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-271 [...] new 2c2a5c3f5 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new b8d0715ad 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new d31a436b9 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 5427c205f 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 2e3177cd5 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new d11979c18 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new b23835394 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 0ab9b414d 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 023dd5995 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new f9553d9f9 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 8ba22f6d9 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new eed16b55c 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new e95f6b8e2 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new 2c88ff6db 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 925ed3b7c 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 32b32b5e7 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new 27c25668b 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new 5028d6c4d 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-20 [...] new 00c66ba9a 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-283 [...] new 53830d380 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new e84a64246 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-283 [...] new 998573932 130: onsuccess: #1554: 2: Success after gcc: 9 commits new 5a4d008e7 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new 959f55c93 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new db71d0e46 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new 3188d3254 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new 3c48bacbc 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new 530ee89d1 136: onsuccess: #1561: 2: Success after binutils: 3 commits new b956fd509 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g8 [...] new 474c950d1 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-gb [...] new f14ce9014 139: onsuccess: #1566: 1: Success after gcc: 5 commits new e08a76399 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits new 5d3081649 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits new 40a66d6a0 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-292 [...] new a6a5c601d 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits new 9a44fa2c5 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits new ba3a324c3 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits new 133762c37 146: onsuccess: #1573: 2: Success after binutils: 7 commits new f9c6823e5 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits new a60ef20c1 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits new 19874b6a1 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 commits new 3632171a1 150: onsuccess: #1577: 2: Success after gcc: 3 commits new ed86f5255 151: onsuccess: #1578: 2: Success after gcc: 2 commits new 4612c44ef 152: onsuccess: #1579: 2: Success after gcc: 2 commits new 4ff574147 153: onsuccess: #1580: 2: Success after binutils/gcc: 2 commits new 41b2efd5d 154: onsuccess: #1581: 2: Success after binutils/gcc: 11 commits new 34bf312fa 155: onsuccess: #1582: 2: Success after binutils/gcc: 15 commits new a5064c949 156: onsuccess: #1583: 2: Success after binutils/gcc: 2 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 (22b11c8e6) \ 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 1704 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2704 bytes 04-build_abe-binutils/console.log.xz | Bin 37672 -> 38040 bytes 05-build_abe-bootstrap/console.log.xz | Bin 269692 -> 273804 bytes 06-check_regression/console.log.xz | Bin 2880 -> 2544 bytes 07-update_baseline/console.log | 40 +++++++++++++++++----------------- 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 | 18 +++++++-------- 13 files changed, 35 insertions(+), 35 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_gnu_cross_check_gcc/master-arm updated (f740145c1 -> e15e88bf4)

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 f740145c1 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/gd [...] discards d9b7b677f 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards c51b96d51 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/gd [...] discards 37970634b 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards e5e8b8455 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 858a6ee4c 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards af219a0ec 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-20 [...] discards 457b485c2 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/gl [...] discards ff770dc30 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 commits discards 1b3c2b66d 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/gd [...] discards 928a58485 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/gd [...] discards 875fe07cb 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/gd [...] discards f3a36367a 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 commits discards d19d6e37c 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 001d9b053 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/gl [...] discards b7c59dcb7 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/gd [...] discards b0f79df81 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 88b80a103 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 01008fadd 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/gl [...] discards a88998f3b 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/gd [...] discards 0ba633710 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 86b7c1f7e 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/gl [...] discards 6914395f4 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 718719eac 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 382579a31 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 commits discards 9e6005598 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 commits discards b5420abb8 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/gd [...] discards a0e526535 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 822cb98a2 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-283 [...] discards 7be11d995 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 9d7b9c42a 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 80b117d53 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 668872cbc 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 03b73a43a 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 0abb50db5 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/gd [...] discards f4eb9e27e 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/gl [...] discards 1abc3ef5b 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/gl [...] discards 9086b73b7 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/gd [...] discards 6d68a4c99 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/gd [...] discards 4b772ca22 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 290a5e15f 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...] discards 2217732be 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] discards e16ddc3a9 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits discards 2404fb081 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] discards 68fe4b45b 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] discards 2f491d33d 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] discards b17fdd341 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] discards a5475a242 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 8bc646729 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 660168e94 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 90f5d4cba 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] discards 6394d4100 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] discards 13a14ffab 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] discards b909bb8fe 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards b9dd739de 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards c4bb99fdc 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards 8f706581b 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 44f24b26f 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards 722e7ec55 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards 357926a57 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards ce6fa07c3 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 9c6742eab 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards c7c41a21b 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards 886129b69 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards d46cc3da3 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards d632a4d99 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards 3f784b01a 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 3afbfdaaf 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 4255c80f5 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 6ea96986d 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 2adb753fe 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 56abce38e 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 40da81c92 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 3d16d80b3 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards fe79e20ce 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 03029ca8a 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards bc64bff95 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 2f26b37c3 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards a89581730 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 5b3a19e5f 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 8d63ce45f 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5df569e56 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards 1b179d1fd 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards deb1ef4af 74: onsuccess: 1: Successful build after linux: 44 commits discards 3544a24dd 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 1a3f0baa6 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 8920c9dd7 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards 4c39bcd74 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards e0afcd4e5 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 9edd0d1d0 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ce8cb66de 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 886a88ec4 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards c93a6cebe 65: onsuccess: 1: Successful build after gcc: 4 commits discards aea51986c 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1567f0b79 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 0bd234bba 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards 8766b9982 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards f5e0f6d88 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards d5c654dd7 59: onsuccess: 1: Successful build after glibc: 2 commits discards 45294a07b 58: onsuccess: 1: Successful build after binutils: 2 commits discards 5668360fe 57: onsuccess: 1: Successful build after gcc: 7 commits new db0771476 57: onsuccess: 1: Successful build after gcc: 7 commits new 404b50d6e 58: onsuccess: 1: Successful build after binutils: 2 commits new 02c6301c0 59: onsuccess: 1: Successful build after glibc: 2 commits new b0ee4d416 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new ad5d390a5 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new b26aea5b4 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new df657412f 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 51b7aeb70 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 55a0eb4f6 65: onsuccess: 1: Successful build after gcc: 4 commits new 260296f59 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 6a488f28b 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b38479dac 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e666bc676 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new 1d1408cff 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new ee5858bb4 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new 28cd5942d 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f9241ce0d 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new edaabc892 74: onsuccess: 1: Successful build after linux: 44 commits new faac05f0f 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new bedd8bcc1 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new d2a98f0fc 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 82819dc76 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new cd702b528 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new dafe4eb5a 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new 6b354ef39 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 984ca5fb8 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 2f35e4f77 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 073a7652f 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 2f0c757c4 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new f16057939 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 0e736ffff 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new dd062f5b0 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 0c16a7ff3 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 0d0cbbe0d 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new d3f385a53 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 286de4b60 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new 10ebe55e3 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 355222567 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new 275b39ece 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new cc561b533 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 4f3721f78 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new b3a2bc3dc 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new 94a2e2a82 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new f51e82156 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new 87ffb2d6c 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 31855f163 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new 30de8ab6f 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new 5291ee5c0 104: onsuccess: #1697: 1: Success after gcc: 4 commits new a7f853176 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] new a7a46cacd 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] new a4f70a063 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] new 66b5a9f6f 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new ba11a374a 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 57e5f85fb 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 41f6fa258 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] new 0fbdb67ee 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] new 44ff92f8c 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] new e36111d36 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] new 730a1ce55 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits new f928a2759 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] new 12ee00998 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...] new 4285f47b3 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new c27b385a2 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/gd [...] new a5e88d6eb 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/gd [...] new 23c24cc36 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/gl [...] new f3a0b8b8b 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/gl [...] new 36f8fb749 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/gd [...] new 50bc5185c 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 03f3473f0 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 5b452361b 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 2567b2ca5 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 22d1c5eec 128: onsuccess: #1723: 1: Success after linux: 12 commits new b7d055c6f 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-283 [...] new d7f2ee2c7 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 4e5335cf7 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/gd [...] new d38afdd9d 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 commits new 2d18f9096 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 commits new 56144f788 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 6ac4a37f7 135: onsuccess: #1733: 1: Success after binutils: 5 commits new bc1ec4c25 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/gl [...] new c5cefc6e9 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 3d7f91d9f 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/gd [...] new 76126432a 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/gl [...] new 7bafe3111 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 819fb1c12 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 8475f0889 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/gd [...] new b2a329cfb 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/gl [...] new 72fe91367 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 35caa48fc 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 commits new 0dc460b26 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/gd [...] new aa99bfc61 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/gd [...] new 75f83f74b 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/gd [...] new 5cd0b2f45 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 commits new 8ad02e3b9 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/gl [...] new 4aff86539 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-20 [...] new fe48e7c89 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 2a5e57ea6 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 925a8a560 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 9d1dc356f 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/gd [...] new c59556df9 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 25f216494 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/gd [...] new e15e88bf4 158: onsuccess: #1759: 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 (f740145c1) \ 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 1688 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30184 -> 30012 bytes 04-build_abe-stage1/console.log.xz | Bin 90880 -> 90668 bytes 06-build_abe-linux/console.log.xz | Bin 8532 -> 8312 bytes 07-build_abe-glibc/console.log.xz | Bin 233852 -> 234208 bytes 08-build_abe-stage2/console.log.xz | Bin 222592 -> 223748 bytes 09-build_abe-gdb/console.log.xz | Bin 37328 -> 37144 bytes 10-build_abe-qemu/console.log.xz | Bin 31272 -> 31576 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2564 -> 2420 bytes 13-check_regression/console.log.xz | Bin 6160 -> 5564 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 14 +- 14-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 | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- sumfiles/g++.log.xz | Bin 2655104 -> 2675652 bytes sumfiles/g++.sum | 12 +- sumfiles/gcc.log.xz | Bin 2234564 -> 2222920 bytes sumfiles/gcc.sum | 2222 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 882444 -> 891784 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201476 -> 201596 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 428400 -> 429304 bytes sumfiles/libstdc++.sum | 8 +- 39 files changed, 1215 insertions(+), 1253 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/gnu-master-aarch64-lts-allyesconfig updated (1f02ae8bc -> da3c803b7)

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 1f02ae8bc 14: onsuccess: #509: 33: Success after binutils/gcc/linux/qem [...] new da3c803b7 15: onsuccess: #510: 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 1712 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30256 -> 30032 bytes 04-build_abe-stage1/console.log.xz | Bin 72292 -> 72236 bytes 05-build_abe-qemu/console.log.xz | Bin 32216 -> 31884 bytes 06-build_linux/console.log.xz | Bin 5004 -> 3756 bytes 08-check_regression/console.log.xz | Bin 4396 -> 4416 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 ++++++++++++++++---------------- 16 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_O1 updated (a7affc28f -> 2d2b906e4)

by git＠git.linaro.org

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-lts-allyesconfig updated (6dea0ef13 -> fe3c3ddf1)

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 6dea0ef13 13: onsuccess: #367: all: Success after binutils/gcc/linux/qe [...] new fe3c3ddf1 14: onsuccess: #368: 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 1688 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 30236 -> 30236 bytes 04-build_abe-stage1/console.log.xz | Bin 69004 -> 68712 bytes 05-build_abe-qemu/console.log.xz | Bin 32320 -> 32072 bytes 06-build_linux/console.log.xz | Bin 3404 -> 3380 bytes 07-boot_linux/console.log.xz | Bin 576 -> 576 bytes 08-check_regression/console.log.xz | Bin 4204 -> 4156 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_gnu_cross_build/master-arm updated (e11b99025 -> e76048c96)

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 e11b99025 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/gd [...] discards 8de402f62 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 commits discards 67efe6c56 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/gd [...] discards 25f49d1c9 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards 4d61c7dec 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards 0a95bc69d 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards 3c31bcac4 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/gl [...] discards 9309e9109 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/gl [...] discards 02a379e7e 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 commits discards 51bb85f23 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/gd [...] discards d050438f8 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/gd [...] discards 240b4aca5 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/gd [...] discards e265e7a19 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 commits discards 02502ae1e 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 2b8e94be9 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/gd [...] discards 849bf278b 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/gl [...] discards 9bcf5c318 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 commits discards 6f2609854 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards 390ae6bcc 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/gl [...] discards 913b2f053 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/gd [...] discards d3e3f287c 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards 6c06dae84 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/gl [...] discards 90d8c6c72 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards 2a4a9e16a 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g1 [...] discards 2d1c14d09 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g3 [...] discards c68020be2 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 96765c13a 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 commits discards 60da4cee2 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 commits discards f37bc5471 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/gd [...] discards 6ac2d34e0 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 54fd24fca 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards e861f0657 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/gd [...] discards e78a7cc0f 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 2fd049073 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards 676293c59 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 32a05d55e 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/gd [...] discards 5841ff80f 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/gl [...] discards 19d04e3c9 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/gl [...] discards 8e5cbaa3c 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/gd [...] discards e234da341 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/gd [...] discards 4c449b33c 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 commits discards 7cecb9c69 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qemu [...] discards ea8c80867 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/gl [...] discards 693937461 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 commits discards ee5f3a97c 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: 1 [...] discards 15432b249 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/gd [...] discards 3a61df695 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/gl [...] discards 6c930756a 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/gd [...] discards 1e18d1440 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 44a43a295 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 539e0a666 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 17dbfb970 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/gd [...] discards 533736081 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/gd [...] discards e3cc1d088 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] discards 8a4cf6108 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 5ea4988cf 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 651d6df52 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] discards 4aa1a53eb 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards a7f7a694c 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] discards fbc8953e6 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] discards cdedf97e2 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards a32bd9586 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] discards 49a53011a 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] discards 239fd223e 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 6415e0936 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] discards 144254ebf 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] discards 97b38b811 95: onsuccess: #1529: 7: Success after baseline build: no new [...] discards a6c3cd593 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 210500f23 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] discards 85dad9617 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards d240d62ec 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards e8dfe1710 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 946fee573 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards f379b4599 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 74d3bb4ff 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 68e9a6051 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards b5d7150d2 85: onsuccess: 7: Success after gcc: 9 commits discards 5e5a97304 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 9faf3fc9b 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 8c419d8de 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards b4d17ff78 81: onsuccess: 7: Successful build after gcc: 2 commits discards 9592f60ca 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards c87223474 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 359cae1f6 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards b0584d89c 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards 7758e7a84 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 1dab41867 75: onsuccess: 7: Successful build after linux: 44 commits discards f7af90ddb 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 9a68ee3a6 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 6baa688f5 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 0cd8fa9e2 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards 78e6aee41 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 3fa9b08bd 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 387cc9bcb 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 71589c026 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards a44a2dfd5 66: onsuccess: 7: Successful build after gcc: 3 commits discards 4cdf4408d 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards fed89f2f9 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards cbbf8e3ec 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards 44ae4e9f8 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 9953ff8ac 61: onsuccess: 4: Successful build after gcc: 15 commits new 5644799f4 61: onsuccess: 4: Successful build after gcc: 15 commits new 6729adbb5 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 54a202518 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new b8bd5ac6d 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 0d6516886 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 71247f48a 66: onsuccess: 7: Successful build after gcc: 3 commits new ae1c28a4b 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new a3934ebde 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new aac13e1dc 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 4df9a580c 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 655c24bcb 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new 04f4a3a34 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 6371cc4af 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7c0be0545 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 110827a0c 75: onsuccess: 7: Successful build after linux: 44 commits new 848e5b9db 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 422871962 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new e7a50c74b 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 5a32fd151 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 05fdfa0ca 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new df642638b 81: onsuccess: 7: Successful build after gcc: 2 commits new 7dfb79a27 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new c1d2f44a8 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new a0d06dd39 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new e787c9fde 85: onsuccess: 7: Success after gcc: 9 commits new b1ff630aa 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 57759a88f 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new bd24b2565 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 701c521f0 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 9348e4c31 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new e6e39da04 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 16473c5ce 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 558f76dc6 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] new ae23779c4 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new f97dc49d8 95: onsuccess: #1529: 7: Success after baseline build: no new [...] new e87f324e2 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] new 5282bd03f 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] new fb640b64f 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 97b9b510a 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] new 4f452f4b3 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] new dcf0c5d7b 101: onsuccess: #1609: 7: Success after binutils: 78 commits new b4dc8a034 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] new 7027b9bdd 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] new 38ea11357 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 4b54d7d3a 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] new 73c4177f2 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 1536b2f68 107: onsuccess: #1618: 7: Success after gcc: 2 commits new b2f138b79 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] new ec89092ea 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/gd [...] new f1e4cfa4e 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/gd [...] new d7e8b4a06 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 63f9665da 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 96f458203 113: onsuccess: #1624: 7: Success after gcc: 6 commits new f3ad82d72 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/gd [...] new 32b6148db 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/gl [...] new a4aa80631 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/gd [...] new 11476844a 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: 1 [...] new ad8d611b0 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 commits new c897772da 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/gl [...] new ef8707f57 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qemu [...] new f757bc862 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 commits new d40d27662 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/gd [...] new 596b9a292 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/gd [...] new 7c48171c8 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/gl [...] new c1ba27d68 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/gl [...] new 3f35d351b 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/gd [...] new d6d53a15c 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 2fe2a3bed 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 3f88333bf 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new ef52b1dc5 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/gd [...] new 0ac20c96c 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 834e357e1 132: onsuccess: #1645: 7: Success after linux: 23 commits new 8149cbfc8 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/gd [...] new 48e442492 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 commits new f17b24e49 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 commits new 12f2085fc 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 122091d0b 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g3 [...] new 7be583ad1 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g1 [...] new 72ddeff97 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 2cde0f833 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/gl [...] new 154f28bbb 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 929b73335 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/gd [...] new 8d2892eea 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/gl [...] new 78c34f11e 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new 76724cf07 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 commits new 1e6c1edb2 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/gl [...] new cf4e13a72 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/gd [...] new a38949d37 148: onsuccess: #1663: 7: Success after glibc: 2 commits new d173a5c05 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 commits new 163d2449e 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/gd [...] new 179068be3 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/gd [...] new 4f4504102 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/gd [...] new 2f4d31c21 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 commits new 85bd76127 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/gl [...] new 74c477217 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/gl [...] new bf964f372 156: onsuccess: #1671: 7: Success after gcc: 3 commits new 3b6e538fb 157: onsuccess: #1672: 7: Success after gcc: 2 commits new 8a3acaf16 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new 13f38724a 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/gd [...] new c50b747fc 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 commits new 040582629 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/gd [...] new e76048c96 162: onsuccess: #1677: 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 (e11b99025) \ 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 1712 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 30100 -> 30000 bytes 05-build_abe-stage1/console.log.xz | Bin 90848 -> 90612 bytes 07-build_abe-linux/console.log.xz | Bin 8512 -> 8316 bytes 08-build_abe-glibc/console.log.xz | Bin 233736 -> 233588 bytes 09-build_abe-stage2/console.log.xz | Bin 223688 -> 223564 bytes 10-build_abe-gdb/console.log.xz | Bin 37420 -> 37280 bytes 11-build_abe-qemu/console.log.xz | Bin 31360 -> 31372 bytes 12-check_regression/console.log.xz | Bin 4276 -> 3448 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, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-mainline-allyesconfig updated (da74ef10f -> 7ba874e60)

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 da74ef10f 16: onsuccess: #450: 20867: Success after binutils/llvm/linux [...] new 7ba874e60 17: onsuccess: #451: 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 1724 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30244 -> 29984 bytes 04-build_kernel_llvm/console.log.xz | Bin 64344 -> 62140 bytes 05-build_abe-qemu/console.log.xz | Bin 32524 -> 31864 bytes 06-build_linux/console.log.xz | Bin 4572 -> 4760 bytes 08-check_regression/console.log.xz | Bin 4556 -> 4368 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 | 32 ++++++++++++++++---------------- 16 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_gnu_cross_build/master-aarch64 updated (91bebf899 -> 2569cec8b)

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 91bebf899 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/gd [...] discards d933d7735 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards 71cd79e7f 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/gd [...] discards 3905286c0 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards 446da8ee9 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards f49724ebb 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] discards bf0c5c077 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards a1dc00f4b 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g1 [...] discards f75c2bff4 152: force: #1605: 7: Success after gcc: 9 commits discards 82b62275d 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-20 [...] discards 337b91a8e 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/gl [...] discards 394f37e1d 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 commits discards 918aa8124 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/gd [...] discards ab1a125a0 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/gd [...] discards 95f5f75c1 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/gd [...] discards a16a829ec 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 commits discards 1a1775cbd 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 8117e0197 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/gl [...] discards ce7902845 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/gd [...] discards e72b1d12d 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards b53983a1a 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards 648d53710 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/gl [...] discards 50f31fb80 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/gd [...] discards 6811c0a45 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards cf21e57ea 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 commits discards 34fa3261a 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/gd [...] discards 63057a60a 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/gd [...] discards 1eb4b3f85 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 commits discards d08ff1249 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 commits discards 6b9d93763 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/gd [...] discards 45bb6c37b 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 500a15593 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-283 [...] discards df7f1f293 128: onsuccess: #1579: 7: Success after linux: 12 commits discards f30d71102 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards e3f623809 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 405d6558a 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 964eff35f 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards ad181b9bb 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/gd [...] discards 3e7e88086 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/gl [...] discards 3f6ace9e2 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/gl [...] discards 30f95bece 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/gd [...] discards a94f24504 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/gd [...] discards a03b32fd5 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards 33da039b0 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qemu [...] discards 175075e9e 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/gl [...] discards aaabae0ec 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 commits discards 9355b47cd 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: 1 [...] discards 80b7b37e4 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/gd [...] discards 1854a3da2 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/gl [...] discards 47e1bd93f 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/gd [...] discards 93db4b326 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards a02b99784 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards e1d71fea1 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-272 [...] discards b83feafa4 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/gd [...] discards 7b0e02052 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/gd [...] discards a61605a57 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddeed [...] discards 4175db2d6 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/gl [...] discards 6556960d9 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards d8ffa80d1 102: force: #1551: 1: Failure after gcc: 306 commits discards d689df0f1 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 60e53503a 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] discards 98a72f780 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 6bfb5884d 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] discards 63cc8fb41 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 35168ded4 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 82025c362 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 3671a2585 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 57d727fbe 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 167e0d814 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 485cc8774 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 15656c0dd 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 26810453e 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards a88443887 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards c8b343ef2 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards f5189409c 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards d145c791e 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards 87c5e1305 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards badb8324a 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 81be85513 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards 11cae9a73 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 59751b8ab 80: onsuccess: 7: Successful build after linux: 44 commits discards e9fb76319 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 865a8e732 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] discards 8886c63dd 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 54126b018 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 9d2ce55a9 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards 63cd6fc93 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 57e4d14a9 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 0a7796ff0 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 253549615 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards db70d8d3e 70: onsuccess: 7: Successful build after gcc: 4 commits discards 2451b278b 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 404d98d3c 68: onsuccess: 7: Successful build after linux: 6 commits discards 57dd16a5e 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] discards 7d0952815 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] discards 75d3a49ff 65: onsuccess: 7: Successful build after binutils: 3 commits discards a97784af3 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards 5b303716f 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards dfd449b12 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 6ea8be9d0 61: onsuccess: 4: Successful build after gcc: 5 commits discards 505e8599e 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new d02e626c2 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new ff4e9dbb4 61: onsuccess: 4: Successful build after gcc: 5 commits new 365308549 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 6f200eca7 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 53ebfe58c 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new c3bd17bf3 65: onsuccess: 7: Successful build after binutils: 3 commits new eabd8fc75 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] new cbccbcbea 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] new e75bda3c0 68: onsuccess: 7: Successful build after linux: 6 commits new 82b1c3116 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 2bfabaab8 70: onsuccess: 7: Successful build after gcc: 4 commits new a09f29de0 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new d0b6adccd 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 31340586d 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new e90961750 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 17af51ea3 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new f54bab375 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 026c72758 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new fc7bf2237 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] new 27be917cb 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 446d5f262 80: onsuccess: 7: Successful build after linux: 44 commits new e91e6d7cf 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 31631f8c9 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new 7766f5947 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new c09ede404 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 7c6a08e4e 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new 9d8dd4d42 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 7effbd653 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 36b246a30 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 5692c179f 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 82bfddca9 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 33b090a3a 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new a533e546a 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 7ef95d1dd 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new c329db144 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 5f0ecd949 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 7e468c344 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 74e3c019a 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new c764e3f4c 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] new a4c8ed218 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new fcba73370 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] new e4ddde130 101: onsuccess: #1547: 7: Success after binutils: 82 commits new b3526496b 102: force: #1551: 1: Failure after gcc: 306 commits new 5c360fc30 103: onsuccess: #1552: 1: Success after gcc: 5 commits new c0eef4895 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/gl [...] new 6edbd49a2 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddeed [...] new fa37f0df7 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/gd [...] new de4e97fab 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/gd [...] new 0c22ff253 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-272 [...] new e3f33fd4a 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 4d416d1aa 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 1ed7077ee 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/gd [...] new 63ab325d6 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/gl [...] new 862e68114 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/gd [...] new 1671c2ab0 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: 1 [...] new 88363b7f3 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 commits new 3f16a9f44 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/gl [...] new 45c16e59f 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qemu [...] new d7e4b73ad 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new be0a5a5d3 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/gd [...] new 95cca29c8 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/gd [...] new e4af40a2e 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/gl [...] new 2f97529ab 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/gl [...] new 1a9a72114 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/gd [...] new 08536c162 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 04eff0dfc 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 89bb0ceeb 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new dd6ac2b2a 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new 551a73f31 128: onsuccess: #1579: 7: Success after linux: 12 commits new 4919b7fc4 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-283 [...] new e01e8f69d 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 8f693e625 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/gd [...] new 546ea7e87 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 commits new 36eafbf71 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 commits new 805bae2b6 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/gd [...] new 0b0cab4bc 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/gd [...] new 342023880 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 commits new 7754cba02 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 0206132e5 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/gd [...] new 60d90c574 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/gl [...] new 65c0919e9 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new cebf98c76 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new 2bf4d4e2a 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/gd [...] new 22676b348 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/gl [...] new fcda882e5 144: onsuccess: #1595: 7: Success after glibc: 2 commits new dcc079654 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 commits new c600c52c6 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/gd [...] new e02913726 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/gd [...] new a45ec6859 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/gd [...] new 1031d607e 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 commits new 97b4c4b64 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/gl [...] new 84f80cb70 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-20 [...] new 7903dea0d 152: force: #1605: 7: Success after gcc: 9 commits new a9e4fa6e9 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g1 [...] new dba2d6f1e 154: onsuccess: #1607: 1: Success after gcc: 2 commits new bf6d8f9ca 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] new 668548977 156: onsuccess: #1609: 7: Success after gcc: 2 commits new 26eb4ed76 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new 9f139dcee 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/gd [...] new 40a3c90ac 159: onsuccess: #1612: 7: Success after gcc: 4 commits new 92fdca493 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/gd [...] new 2569cec8b 161: onsuccess: #1614: 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 (91bebf899) \ 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 1708 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 30352 -> 30292 bytes 05-build_abe-stage1/console.log.xz | Bin 72292 -> 71840 bytes 07-build_abe-linux/console.log.xz | Bin 8544 -> 8272 bytes 08-build_abe-glibc/console.log.xz | Bin 240268 -> 239964 bytes 09-build_abe-stage2/console.log.xz | Bin 203104 -> 202344 bytes 10-build_abe-gdb/console.log.xz | Bin 37612 -> 37528 bytes 11-build_abe-qemu/console.log.xz | Bin 31764 -> 31836 bytes 12-check_regression/console.log.xz | Bin 4248 -> 3552 bytes 13-update_baseline/console.log | 62 +++++++++++++++++------------------ 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, 57 insertions(+), 57 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_check/master-aarch64 updated (a51c72f0d -> 49f1387d6)

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_check/master-aarch64 in repository toolchain/ci/base-artifacts. discards a51c72f0d 155: onsuccess: #2090: 1: Success after binutils/gcc: 22 commits discards b31d667a3 154: onsuccess: #2089: 1: Success after gcc: 4 commits discards ba3426aed 153: onsuccess: #2088: 1: Success after basepoints/gcc-13-301 [...] discards da3ad1cc7 152: onsuccess: #2087: 1: Success after gdb-12-branchpoint-20 [...] discards 43c776724 151: onsuccess: #2086: 1: Success after gcc: 2 commits discards 0f8ac50e1 150: onsuccess: #2085: 1: Success after gcc: 2 commits discards d45a8b403 149: onsuccess: #2084: 1: Success after gcc: 16 commits discards 7db603e1c 148: onsuccess: #2082: 1: Success after gdb-12-branchpoint-20 [...] discards f8482b05d 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 commits discards d7c642a45 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits discards 4b8083688 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits discards 4a0a61c9d 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits discards 45f1959ce 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits discards 4e95e4ecb 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits discards 2ffdde00d 141: onsuccess: #2073: 1: Success after binutils: 3 commits discards 132eb758f 140: onsuccess: #2070: 1: Success after binutils: 4 commits discards 517b27fcb 139: onsuccess: #2067: 1: Success after binutils: 2 commits discards 977ecd544 138: onsuccess: #2064: 1: Success after binutils: 4 commits discards f2498b42a 137: onsuccess: #2061: 1: Success after binutils: 2 commits discards bd45cba44 136: onsuccess: #2056: 1: Success after binutils: 4 commits discards 062c6a8a7 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits discards 685188745 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits discards 47e69c392 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits discards 08d762fe9 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits discards 26b42e1ed 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-20 [...] discards 5e4e753c7 130: onsuccess: #2049: 1: Success after gcc: 9 commits discards a5f1fa1b6 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-283 [...] discards 5454fc4ac 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-283 [...] discards 7a0165628 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-20 [...] discards f3f97f30e 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-283 [...] discards eb3794ec6 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits discards 2beebc7bc 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits discards bec0cc029 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits discards bedbb65af 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits discards 63077e14d 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits discards 6b1d4230d 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits discards bfa4c3a49 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits discards a9593bdf8 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits discards c8af5ce1a 117: onsuccess: #2034: 1: Success after binutils: 2 commits discards 2acc8fc70 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits discards 1987c4a17 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits discards 7c9bf46ac 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits discards c9b1517b0 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits discards d6daaf5fe 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits discards c0009690f 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits discards a6d664909 110: onsuccess: #2027: 1: Success after gcc: 5 commits discards 56be9c365 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits discards 46de82f30 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits discards 483781980 107: onsuccess: #2024: 1: Success after gcc: 3 commits discards 87afffa9e 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits discards 1b29cdf54 105: onsuccess: #2022: 1: Success after gcc: 4 commits discards ee79ca069 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards 32f9ca3db 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards c0d1d2f31 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-270 [...] discards 08c3b7eb9 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards 3ab03f170 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards e50b902d2 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards c33a6d670 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards d0b6f4a2f 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards c2a592b44 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-2393 [...] discards 3cd9d71be 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-2392 [...] discards 7b0028bcc 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards e25800031 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-2390 [...] discards c02e15e11 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards 8be263151 91: onsuccess: 1: Success after gcc: Daily bump. discards 7f1f81b8e 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards b875fb670 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards a0527befa 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards e11a2f74c 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards d44bf86de 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards 9f0d37db8 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards 9d2b989cf 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards f61612e2c 83: onsuccess: 1: Success after gcc: 8 commits discards 34347293c 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards 324a4772e 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards 456e38073 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards 4303355d0 79: onsuccess: 1: Successful build after gcc: Daily bump. discards f27bac7e9 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 7e63c8346 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards b50440ab8 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 21e987825 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards b46cdda1d 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards 476e4b058 73: onsuccess: 1: Successful build after binutils: PR29494 Tr [...] discards dff9175ce 72: onsuccess: 1: Successful build after gcc: 2 commits discards 4bb787c8e 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 53cbc958b 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards 0ff50b11a 69: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards 801d65713 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards a5e212668 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards c05b0d1bb 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 2aa898bea 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 7d1ed7663 64: onsuccess: 1: Successful build after gcc: 5 commits discards ed1dcf4c6 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards dcca2713e 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 6441419f3 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits discards 9c18bcae2 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 74a430a62 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits discards 469a6add7 58: onsuccess: 1: Successful build after binutils: 2 commits discards fa0af7b90 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards 5266afb9a 56: onsuccess: 1: Successful build after gcc: Daily bump. discards f622e2844 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 81152fd8d 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 7a03db8de 56: onsuccess: 1: Successful build after gcc: Daily bump. new 6c46e2bf1 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits new cae6791d6 58: onsuccess: 1: Successful build after binutils: 2 commits new 7935248a3 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits new 6b3a5197b 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 157ea6825 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits new a61ba9964 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 7a8dcccfe 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 0afe30f4b 64: onsuccess: 1: Successful build after gcc: 5 commits new c98d7abe6 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits new a2c499850 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 1bc90e099 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new ee7285146 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 5fe5545d3 69: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new e8e4dda28 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new 3df210dd6 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 1d39405ea 72: onsuccess: 1: Successful build after gcc: 2 commits new 2ce97bb98 73: onsuccess: 1: Successful build after binutils: PR29494 Tr [...] new 693389145 74: onsuccess: 1: Successful build after binutils: Automatic [...] new 9438f7201 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 6ffdb5eba 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 06391cff3 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new c4d51b63e 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 513e6b6bd 79: onsuccess: 1: Successful build after gcc: Daily bump. new f01f020bd 80: onsuccess: 1: Success after binutils/gcc: 14 commits new 8a06054d1 81: onsuccess: 1: Success after binutils/gcc: 27 commits new c39c3c430 82: onsuccess: 1: Success after binutils/gcc: 10 commits new 55dd36a9d 83: onsuccess: 1: Success after gcc: 8 commits new 95d088101 84: onsuccess: 1: Success after binutils/gcc: 9 commits new 77e97cb50 85: onsuccess: 1: Success after binutils/gcc: 9 commits new fc74099b1 86: onsuccess: 1: Success after binutils/gcc: 13 commits new 6f1c5ad22 87: onsuccess: 1: Success after binutils/gcc: 4 commits new 0e27c2867 88: onsuccess: 1: Success after binutils/gcc: 16 commits new 98f3cc0dd 89: onsuccess: 1: Success after binutils/gcc: 9 commits new 8f55bf73d 90: onsuccess: 1: Success after binutils/gcc: 6 commits new f295cae7c 91: onsuccess: 1: Success after gcc: Daily bump. new 5f5f52747 92: onsuccess: #1965: 1: Success after gcc: 2 commits new 01e026a65 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-2390 [...] new 3a733f132 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new b192889df 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-2392 [...] new 1b8f7221a 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-2393 [...] new 6bdd7b4c4 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new ca655b148 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new a5d8027c6 99: onsuccess: #1974: 1: Success after gcc: 14 commits new f8c978312 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new 0b3e0effb 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new b6b307f1d 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-270 [...] new d26d07018 103: onsuccess: #2020: 1: Success after gcc: 2 commits new b30b5ed01 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new 3defe3f2f 105: onsuccess: #2022: 1: Success after gcc: 4 commits new 3f3231e21 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits new 9506021c3 107: onsuccess: #2024: 1: Success after gcc: 3 commits new 3940005b0 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits new 728fe2a62 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits new 4ec007d7b 110: onsuccess: #2027: 1: Success after gcc: 5 commits new 6ba1a87f5 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits new f510853ca 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits new 0d121d552 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits new 26a7021e3 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits new 8769ec713 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits new 2dad60c5c 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits new 3363d7cfb 117: onsuccess: #2034: 1: Success after binutils: 2 commits new 93b1e22ae 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits new b2e87c877 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits new 40243649a 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits new e888a8297 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits new d81736c51 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits new 5be28be4a 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits new e35ce2568 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits new 665fc3fe9 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits new 586bb4dba 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-283 [...] new e8ca1d42b 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-20 [...] new 3432c7bdb 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-283 [...] new d2c264bdc 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-283 [...] new b8c88a0f0 130: onsuccess: #2049: 1: Success after gcc: 9 commits new 2bf793e3b 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-20 [...] new cf22d63b9 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits new 3839e230c 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits new c3a04eed5 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits new d91ce5acd 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits new 9b56473ca 136: onsuccess: #2056: 1: Success after binutils: 4 commits new 5555dc3b9 137: onsuccess: #2061: 1: Success after binutils: 2 commits new ed97a198d 138: onsuccess: #2064: 1: Success after binutils: 4 commits new 5b4e3dcec 139: onsuccess: #2067: 1: Success after binutils: 2 commits new 47371215d 140: onsuccess: #2070: 1: Success after binutils: 4 commits new a6f10f745 141: onsuccess: #2073: 1: Success after binutils: 3 commits new e56414ea0 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits new b8e9c5bc1 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits new 71763c54b 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits new 652ad6ff3 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits new 5ea549693 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits new 4db61b77d 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 commits new f003a8a2a 148: onsuccess: #2082: 1: Success after gdb-12-branchpoint-20 [...] new 19e05edd2 149: onsuccess: #2084: 1: Success after gcc: 16 commits new d2616e132 150: onsuccess: #2085: 1: Success after gcc: 2 commits new f03d56bee 151: onsuccess: #2086: 1: Success after gcc: 2 commits new 2c039ea4c 152: onsuccess: #2087: 1: Success after gdb-12-branchpoint-20 [...] new d9d8f4ba4 153: onsuccess: #2088: 1: Success after basepoints/gcc-13-301 [...] new 42841d2c3 154: onsuccess: #2089: 1: Success after gcc: 4 commits new b0f9a4c6d 155: onsuccess: #2090: 1: Success after binutils/gcc: 22 commits new 49f1387d6 156: onsuccess: #2091: 1: Success after binutils/gcc: 2 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 (a51c72f0d) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-aarch64 [...] 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 1724 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2712 bytes 03-build_abe-binutils/console.log.xz | Bin 39444 -> 37480 bytes 04-build_abe-gcc/console.log.xz | Bin 213648 -> 213332 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3872 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2508 -> 2328 bytes 07-check_regression/console.log.xz | Bin 5324 -> 4368 bytes 07-check_regression/mail-body.txt | 32 - 07-check_regression/results.compare | 36 +- 07-check_regression/results.compare2 | 42 +- 08-update_baseline/console.log | 48 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 34 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 3573804 -> 3570700 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 3132992 -> 3085536 bytes sumfiles/gcc.sum | 5184 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1041148 -> 1043456 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2192 -> 2188 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207700 -> 207260 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 439628 -> 447132 bytes sumfiles/libstdc++.sum | 10 +- 32 files changed, 2746 insertions(+), 2858 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 October 2022