Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-lts-allnoconfig updated (063e6dc17c -> 1619e5eb97)

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-arm-lts-allnoconfig in repository toolchain/ci/base-artifacts. from 063e6dc17c 11: onsuccess: #355: all: Success after binutils/gcc/linux/q [...] new 1619e5eb97 12: onsuccess: #356: all: Success after binutils/gcc/linux/q [...] 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 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30432 -> 29892 bytes 04-build_abe-stage1/console.log.xz | Bin 88220 -> 86604 bytes 05-build_abe-qemu/console.log.xz | Bin 31164 -> 31332 bytes 06-build_linux/console.log.xz | Bin 3304 -> 3288 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4164 -> 4108 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap updated (a13bd97f5f -> d3ae91fcad)

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 a13bd97f5f 153: onsuccess: #1580: 2: Success after binutils/gcc: 2 commits discards 948a1d42d4 152: onsuccess: #1579: 2: Success after gcc: 2 commits discards d61612e6c5 151: onsuccess: #1578: 2: Success after gcc: 2 commits discards 2c5e8b0f46 150: onsuccess: #1577: 2: Success after gcc: 3 commits discards 59d8a39371 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 commits discards 864ba528c5 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits discards b69bbab7ad 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits discards 0b3a9b8f44 146: onsuccess: #1573: 2: Success after binutils: 7 commits discards 5a4c6e4cb9 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits discards d8ffc32a73 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits discards 500acf2132 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits discards 14f0c19ec8 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] discards 758fd385f6 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits discards ebb37fa610 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits discards 97f4d6ead7 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards cc2b7db73d 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] discards 30c6244d40 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards 85be350605 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards b2e8df1c8b 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards b6bbbdcdf0 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards f6d699a1b4 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards fd4f05089d 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards a459a316c6 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards 97ef9fe406 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards 3710219943 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards 35afb0941a 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards 76a3da7fce 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards 0ed1ae04fd 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards 676374665d 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards 13dfbddad1 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards 190e86e7ac 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards a6fe2e7d69 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 4bb4983bf5 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards 2ec7782de2 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards 752e8d68b2 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards ab3990892c 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 20993b73b9 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards b435bd8cac 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 4f264d43ab 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards ecfaca2154 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 4b09664fc0 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards 94fd6bdcd5 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards f56b00613f 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 8ae9e14d96 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 0d79064a97 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 2f80c4a5f8 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards 4e44882efa 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 3bb1d1d877 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards d453054030 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards 0c3c0dd485 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards 86d741a375 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards bfd9015120 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards 271127888c 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards e7159edb79 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 49bc0dc801 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards dc689448ab 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards fc3c9f0c8b 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 3002f1b5bd 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards d7c04644ef 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards bc42a5b2cd 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 7b28e9ae04 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards cdcb056ce5 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 7c8e4c91c4 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 16de2a276a 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 2b212e8a38 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 41a730049a 88: onsuccess: 1: Success after gcc: 20 commits discards 4d491600e1 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards 02680d74cd 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards ce48e1e549 85: onsuccess: 2: Success after binutils: 4 commits discards 22396a4c5d 84: onsuccess: 2: Success after gcc: 9 commits discards c99921694f 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 75bcf79d07 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 2ef2ab2e79 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 7ab7059579 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 0be8e9bc9a 79: onsuccess: 1: Successful build after gcc: 3 commits discards cf6ffeec73 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 03778c15a1 77: force: 2: Successful build after gcc: 32 commits discards e31335d004 76: onsuccess: 2: Successful build after binutils: 10 commits discards 1118ee9ed6 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 537fbb59e6 74: onsuccess: 2: Successful build after gcc: 13 commits discards 00c976e30c 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards e4c9ac3e71 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 3e46a34edf 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 6d79f8e769 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 61d68f1a1f 69: onsuccess: 2: Successful build after baseline build: no [...] discards 18c27ece88 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 6bb811445e 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards c80f07dbf6 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 0645a70e2b 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards e711baaa1d 64: onsuccess: 2: Successful build after gcc: 7 commits discards 8ca4a9d9fe 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 0d87b50e03 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 7e56bc7fab 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 2feeb5e97a 60: onsuccess: 1: Successful build after gcc: 15 commits discards 5d3230a730 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards afd490e54b 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards 5049d33fab 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 4bc766f239 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 63429f7245 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 054d2b280b 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards d21b9b7849 53: onsuccess: 2: Successful build after gcc: 5 commits new 92daf4b40c 53: onsuccess: 2: Successful build after gcc: 5 commits new 9e6b133af7 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 529bdce97b 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new a3a402743b 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 0495418cde 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 086d97b460 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new 40f39bf50c 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 7622a11a32 60: onsuccess: 1: Successful build after gcc: 15 commits new 057beeac22 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 6b2a944e54 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new f686baa13c 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 1f0ea1ee6e 64: onsuccess: 2: Successful build after gcc: 7 commits new da458845dd 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 27563f0545 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 3cc02a7509 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new d9af3b2852 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 410e18a434 69: onsuccess: 2: Successful build after baseline build: no [...] new 1f95a93f6a 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 1274b745e3 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new fe3d82abaf 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 0d31871bc7 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new a4fc167be3 74: onsuccess: 2: Successful build after gcc: 13 commits new 561025b851 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new a1af02045a 76: onsuccess: 2: Successful build after binutils: 10 commits new cd864cb72d 77: force: 2: Successful build after gcc: 32 commits new 495932f879 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 2fbcd8b731 79: onsuccess: 1: Successful build after gcc: 3 commits new 4ef1c655cc 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new eadd1e1c61 81: onsuccess: 2: Success after binutils/gcc: 16 commits new e27be0a2e7 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 161da0f08c 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 5abbf3bd40 84: onsuccess: 2: Success after gcc: 9 commits new ad31a3f518 85: onsuccess: 2: Success after binutils: 4 commits new 0c4cff0d27 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new d26a77d116 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new a3f2840ae6 88: onsuccess: 1: Success after gcc: 20 commits new 8b5c8af771 89: onsuccess: 2: Success after binutils/gcc: 39 commits new eb965aa03d 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 61f24f4d3a 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 4513824fe5 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 0e89437239 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new 7364cf79c2 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new 5d0811c839 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 6a5055defe 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 7bf1444ada 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 582389ff00 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new dadcc68ef1 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new f8b4e8daa6 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new 0d37c77103 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new bc452583c0 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 93d33074b1 103: onsuccess: #1524: 2: Success after gcc: 2 commits new a0a2020516 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 802d5be8ea 105: onsuccess: #1526: 2: Success after gcc: 2 commits new b88442ae5b 106: onsuccess: #1527: 2: Success after gcc: 2 commits new b26e3e7247 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new af4225f443 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 832ac4a487 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new b068c5a142 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 66daaca269 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 63fcf97377 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 0489ca1a90 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new 6718e90894 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 7fbbe6c66a 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new a6e181df01 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 06839a6dda 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new 35e75ddb85 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new e5f2a20b36 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new a36bbec7f2 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 6292b51fc5 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new cbb4026bd3 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 0b3c41ae27 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new c49efd27ae 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new b437aa3189 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new aff2f02cf7 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new 67b37a4d56 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new b383a5e16c 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new d4c7890642 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new e679b908d8 130: onsuccess: #1554: 2: Success after gcc: 9 commits new 97f4184d4d 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new f21fa521cb 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new d45f8caaa0 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new 1cb2bbe1c6 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new 320d3653c8 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new bf02087697 136: onsuccess: #1561: 2: Success after binutils: 3 commits new d9c80a1dae 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new 530503ec6f 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] new a61dc54e1c 139: onsuccess: #1566: 1: Success after gcc: 5 commits new e9bbe6e0ea 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits new 658f6aa45a 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits new 66008454f7 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] new 532eee14a5 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits new 5cd242c93a 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits new b6630ceede 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits new fe70e1b1f5 146: onsuccess: #1573: 2: Success after binutils: 7 commits new d82df82df5 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits new ccd4351a42 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits new af969bf87f 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 commits new 2f2a62bcc1 150: onsuccess: #1577: 2: Success after gcc: 3 commits new 39cf0ddd4f 151: onsuccess: #1578: 2: Success after gcc: 2 commits new f71716f44d 152: onsuccess: #1579: 2: Success after gcc: 2 commits new 19b8b76708 153: onsuccess: #1580: 2: Success after binutils/gcc: 2 commits new d3ae91fcad 154: onsuccess: #1581: 2: Success after binutils/gcc: 11 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 (a13bd97f5f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1660 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2700 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 37508 -> 38216 bytes 05-build_abe-bootstrap/console.log.xz | Bin 272852 -> 270628 bytes 06-check_regression/console.log.xz | Bin 2544 -> 3024 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

[gcc] branch master updated (b83b13331ac -> d01bd0b0f3b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from b83b13331ac Adjust LIBGCC2_INCLUDES for VxWorks and augment comment new d01bd0b0f3b tree-cfg: Fix a verification diagnostic typo [PR107121] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/tree-cfg.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- 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-arm-bootstrap_profiled_lto_lean updated (33b9a1058c -> 265a4db03e)

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-arm-bootstrap_profiled_lto_lean in repository toolchain/ci/base-artifacts. from 33b9a1058c 49: onsuccess: #429: 1: Success after gcc: 13 commits new 265a4db03e 50: onsuccess: #430: 2: Success after binutils/gcc: 178 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1760 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 51168 -> 50832 bytes .../console.log.xz | Bin 108624 -> 943688 bytes 06-check_regression/console.log.xz | Bin 2696 -> 3100 bytes 06-check_regression/mail-body.txt | 11 +---------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 13 ++----------- mail/mail-subject.txt | 2 +- manifest.sh | 19 ++++++++++--------- results | 2 +- 14 files changed, 19 insertions(+), 36 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (f66aa59dce -> 7e73ab5066)

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 f66aa59dce 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] discards ec621a5daa 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards 6b1d8a2cdd 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards b8f4efd8b8 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards d99bdc01d1 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] discards 3645e2b592 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] discards 2f28d893ff 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] discards 3adf16e743 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] discards 828dab02c7 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] discards eac5a522d3 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] discards f6af14368a 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards 41e39514d4 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 4910007065 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards 395b6aec0a 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards c48fd553d4 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards c10f3425ff 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards 49aa7eaf0d 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards 74523839dd 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards b41b51ca6f 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards 9baf101e64 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards f5befff18b 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards 6a5f062429 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards cdd53867bd 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards 4c65af6aeb 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 2f0f607b8f 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards f7082a6c37 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards c4e539a305 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards 1c13ebbbf9 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 0a7ae1210c 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 07e9a861ba 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards f2fefdad31 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 8ef3de8467 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards 4598d1a3ff 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 7dfcaa3ce0 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards a6cd8e5f10 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards f4ee23ea65 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards f94366b8d3 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards c48356e068 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards e12031f3f6 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 13caf14860 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards ea6a2e9726 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards f7e1884269 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards e58d6d76a4 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 4a5044a174 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 567f4c2685 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards dc708bbd71 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 59712f9747 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards b7a65798dc 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards fdad6b7a10 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards c2d258cdbf 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards 073b2c2942 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 1248fd4890 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 95564bbc5a 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 196ca9e270 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 1401a9210e 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards a8d7dda2a7 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 22f6526a2d 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards bbad8951b9 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 40354ed403 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 0456b8aee9 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards a5747de29b 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 7355495a58 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards faca721fe1 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards 81418b3ec5 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 2640a9ece9 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards a5f70618dc 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 995c4d0236 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards ad5b5bda84 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 23f316f5ca 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 932a18c2ca 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 77b8318d92 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 0e65634838 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 3ea044971f 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 274a3e1b25 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards caa9279753 85: onsuccess: 7: Success after gcc: 9 commits discards 985696a425 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 363c71f3ec 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 762aa6cc29 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 57236cd271 81: onsuccess: 7: Successful build after gcc: 2 commits discards d98431ccb9 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 562c8be091 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards e954dd97b5 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5aba00baee 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 8fa9e3a3df 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d01323d97f 75: onsuccess: 7: Successful build after linux: 44 commits discards 6a0e47a6ef 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 07f87da525 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ce739660cb 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards d3b519d657 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 42cfca2cce 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 4786c6bbb7 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 50b8aacd6f 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3bd59fa326 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards f42c456359 66: onsuccess: 7: Successful build after gcc: 3 commits discards fe93bb7569 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 584d74d387 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ad42113c00 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards d611ff4cbe 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 766cf1fd41 61: onsuccess: 4: Successful build after gcc: 15 commits discards bb90cb6852 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 730d43987a 59: force: 7: Successful build after gcc: 2 commits new 0852fab017 59: force: 7: Successful build after gcc: 2 commits new f781dd7177 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 9d47d14e8d 61: onsuccess: 4: Successful build after gcc: 15 commits new eefb4c7cb2 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 9279d55d0e 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 39ec9d363f 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 9af4a7e7c8 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 3b47ac3346 66: onsuccess: 7: Successful build after gcc: 3 commits new 8cfb060ddc 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new ada926e41e 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d73671ba06 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 795ad8bab0 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new f6fa4583e2 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 758ccd4cbd 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 0593ff11e8 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new dd1f5f2e99 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 33bbb2a971 75: onsuccess: 7: Successful build after linux: 44 commits new af79f5011b 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ee471ca07f 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 7ff96c8a0c 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 87e41ca8b9 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 41699e62e4 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 30aea6aa01 81: onsuccess: 7: Successful build after gcc: 2 commits new 1946df345a 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new ee8e8b6ac2 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 2934fcb684 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 48b4efc901 85: onsuccess: 7: Success after gcc: 9 commits new 5ec3059fe7 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new dd9159b84c 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new ca609c3418 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new af8cbf9556 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new a8e3f39417 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 97d5f89354 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 5a681c4cf7 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 8220bb8f71 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new 313bfb2176 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 7b144dbae0 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 45665e521b 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 732d3514f2 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new c2c3a4b900 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 99a81ad410 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new fe9a61579a 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new 1a9cca7e28 101: onsuccess: #1609: 7: Success after binutils: 78 commits new edc3a28a8d 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new d23704bc00 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new ed7ed91536 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new de53fb8c85 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 1a6508fe8d 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 96973cf7f4 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 2772cd2496 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new 545e96a0e0 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 999eb53f16 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new 6b01cb23c7 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new d7a453d7c9 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new d568b59611 113: onsuccess: #1624: 7: Success after gcc: 6 commits new d0d4898a7c 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 5c107d5bd0 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 1fe4ab3767 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 92defe93b9 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new f1e71cdd87 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new c1ac5df4e7 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 1d0e854441 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 91909f1019 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new d79b8e77be 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 45dc69ae26 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new fe09bd97d7 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 58ace28472 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new 51b4415095 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new e1bfb2fd3f 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new adfa47e84d 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 7089616024 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 3fa6a3c028 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 35e62d7167 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 6736a89f7a 132: onsuccess: #1645: 7: Success after linux: 23 commits new 75c0af8031 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new 882eb2f18e 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new e373206256 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new ec7ae68788 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 221fd7d3a9 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new 1150cd89c1 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new 95e387365a 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 7fc241f3bf 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new e2d9e22b89 141: onsuccess: #1656: 7: Success after gcc: 7 commits new d0c43e9192 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 1c19605622 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new 22e345f38d 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new b8bdd13243 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new a803702533 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new 6d2998a4c3 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new c0ea47b995 148: onsuccess: #1663: 7: Success after glibc: 2 commits new dbb9f48324 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new bd8303db12 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] new f9d5cbed53 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] new 4ca2da5710 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] new 0fa7c06b83 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] new 1ac2d6e841 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] new 7f328d7c8f 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] new c6612840ef 156: onsuccess: #1671: 7: Success after gcc: 3 commits new 839cdeced4 157: onsuccess: #1672: 7: Success after gcc: 2 commits new bcd26242bb 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new 1701088e33 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] new 7e73ab5066 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] 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 (f66aa59dce) \ 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 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 29944 -> 30628 bytes 05-build_abe-stage1/console.log.xz | Bin 90876 -> 90728 bytes 07-build_abe-linux/console.log.xz | Bin 8932 -> 8908 bytes 08-build_abe-glibc/console.log.xz | Bin 233496 -> 233472 bytes 09-build_abe-stage2/console.log.xz | Bin 223668 -> 225116 bytes 10-build_abe-gdb/console.log.xz | Bin 37256 -> 37948 bytes 11-build_abe-qemu/console.log.xz | Bin 31396 -> 31496 bytes 12-check_regression/console.log.xz | Bin 3516 -> 3756 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++---------- 19 files changed, 56 insertions(+), 56 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_ubsan updated (83f4a0c3d8 -> 7d53c052b6)

by git＠git.linaro.org

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (af2ba26857 -> 60a3cd7a06)

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 af2ba26857 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] discards b9e92d29fd 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards 2d5214071b 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards f60bb9eb26 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] discards 8e88a51949 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards 46bbafd920 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] discards 3c0735fee9 152: force: #1605: 7: Success after gcc: 9 commits discards affe6cf32f 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] discards 98904c1e5e 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] discards 8db763f10a 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards abce17689f 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards 788acb5b48 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards 387127f3dc 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards 985ca1e3e2 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards 65fb4db14d 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards ed1fc0b108 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards 0d2cd92d06 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards 2aa269d149 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 7df32d4bc2 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards 077760e0bc 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards 492c9e22c7 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards f457f16375 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards a34dba1d4b 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards 56d0efb601 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards 3b15a950df 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 080a21e8d0 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards c8dec8b57c 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards f50a5f4a05 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 5afbe7dddd 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards a892df1af6 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards 350ee1c9e5 128: onsuccess: #1579: 7: Success after linux: 12 commits discards a761b29289 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 7a7af163c8 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards e0086f8473 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 2e5084844f 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 56b9ddd57e 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards 3b14b1904b 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 4fee11018a 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards dc1433bcf2 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards b39d99f567 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 1ce3afd386 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards 7e8b2db11a 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 3eea3f12d6 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 09c70b08e4 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards 4a09e4e59f 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards f93c6a47a6 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards 503cce654f 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards a6625e5656 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 9d0e0fd9b4 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards b83d3f5e6d 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 2a4df8765e 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 535573218e 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards e003d3303c 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 18df55aa1c 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards eeb18ff22e 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards fbcf315bc6 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards c65d15b5fd 102: force: #1551: 1: Failure after gcc: 306 commits discards ef60a2f8e1 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards bd88b8bf9f 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards c5930e4837 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 353308bec6 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 0b28dfa314 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards faa36f4877 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards e97e2ab38a 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 97095d6e3e 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 21ece6f5dc 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 19953f972b 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 865286ed92 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 4033e1938f 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 929a10f318 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards e5d6f062f2 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 7d1bc4909f 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 0ab4d96c93 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 44ccb80a0d 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards ff809557c7 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 28ccb293d6 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c7ec69596f 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 65fcee3931 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 557286e519 80: onsuccess: 7: Successful build after linux: 44 commits discards 2f5a5f18d6 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards f7cb2dfdea 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards 824afb25fb 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 1e701c3013 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards db0bf38dfe 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards bf7825cc74 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 824920e8c8 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7bd03a326f 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f62cf68859 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 64963b7cbb 70: onsuccess: 7: Successful build after gcc: 4 commits discards 4f4a24e3ad 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards bb7874c954 68: onsuccess: 7: Successful build after linux: 6 commits discards 6eb995b2c1 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards 124412b2d1 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards 83ca292340 65: onsuccess: 7: Successful build after binutils: 3 commits discards 3cc552165e 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 5bd46c3bfa 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 9f1fd7fb44 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 24976e03f0 61: onsuccess: 4: Successful build after gcc: 5 commits discards 75cb483732 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 0197b2aa13 59: force: 7: Successful build after gcc: 3 commits discards c8764e4c60 58: onsuccess: 7: Successful build after glibc: 2 commits new ba8297be13 58: onsuccess: 7: Successful build after glibc: 2 commits new 4895dc8ee5 59: force: 7: Successful build after gcc: 3 commits new d5c745bd3c 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new c2f8b91b1e 61: onsuccess: 4: Successful build after gcc: 5 commits new bb613e303b 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new ce746a5f4e 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 21e1995d0d 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 68f1b10702 65: onsuccess: 7: Successful build after binutils: 3 commits new a736141f24 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 6438ead306 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new 76e3c631a1 68: onsuccess: 7: Successful build after linux: 6 commits new 2c5529f10c 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new fb4f55d7cc 70: onsuccess: 7: Successful build after gcc: 4 commits new 8002a8654c 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 27f7eaf739 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ddc3928f3c 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ab967ab2d9 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new b0af0062b5 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 9bef6434c0 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 8f4c03dd1e 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ee333e60a6 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new 002c7ec127 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new d801300802 80: onsuccess: 7: Successful build after linux: 44 commits new b36699094a 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 3d4b00dcc6 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 40a7586b1a 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 88b2d015a7 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 78b10a7d9c 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 7a30f6f391 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 0ee8116b35 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 6a39ef7f33 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new f169fe305a 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 3b5f364c05 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new e4225e4b72 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new bbb821dfaa 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 3fe108bb8d 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new bbf4732637 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new d55e86e42f 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new faa3fd82b4 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 400652cda3 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 039032bcce 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 90229fc493 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new ea08f4e31d 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 1cba7c1d0c 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 0d17e6ad13 102: force: #1551: 1: Failure after gcc: 306 commits new abfef80665 103: onsuccess: #1552: 1: Success after gcc: 5 commits new cb245a4088 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 631f3ca597 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 7e15ab1407 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new e0c4c47f55 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new ef513e3eac 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new 65352e352f 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 03e690785f 110: onsuccess: #1559: 7: Success after gcc: 4 commits new c197c5b15d 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new 4ec5a84307 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new cf55bbe302 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new d367a2aafc 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new f98525d12d 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new d734833654 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new b2275e9fed 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 93c4f2ae94 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new 1b03871248 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new aeac4a3ed7 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 54bcb79e38 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 9e27257dd1 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 31108e5da5 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new 1875495ae3 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new d40c9be29d 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new c3a102d532 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 9caeb080b3 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new 3be7ec6e7d 128: onsuccess: #1579: 7: Success after linux: 12 commits new 24cc3e8eb4 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new 541558ddde 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 1f362b4906 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new d44e376f0e 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 28714960cb 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new d0ad94469a 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new dd31bcf752 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new 22d40b9e7a 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new cb90e385fb 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 0cbe1a26f2 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new d772d39889 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 7dd0b12020 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new 3b892a5e37 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new c154a4f422 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new ea38c0029f 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new c206a37e7c 144: onsuccess: #1595: 7: Success after glibc: 2 commits new 235bf898a2 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new 802d77262d 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new 4afca552ed 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new 4b7f2798e3 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new b34497026a 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new 45745f3332 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] new 07e7582890 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] new b96417f884 152: force: #1605: 7: Success after gcc: 9 commits new 9cf398a612 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] new 0f467d2eac 154: onsuccess: #1607: 1: Success after gcc: 2 commits new cd70b56d0c 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] new 1ec68e5bf4 156: onsuccess: #1609: 7: Success after gcc: 2 commits new 4225951f76 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new f923e4f6da 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] new 60a3cd7a06 159: onsuccess: #1612: 7: Success after gcc: 4 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 (af2ba26857) \ 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 1660 -> 1920 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 30124 -> 30244 bytes 05-build_abe-stage1/console.log.xz | Bin 72160 -> 72520 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 8920 -> 8928 bytes 08-build_abe-glibc/console.log.xz | Bin 239164 -> 239812 bytes 09-build_abe-stage2/console.log.xz | Bin 202180 -> 203488 bytes 10-build_abe-gdb/console.log.xz | Bin 37380 -> 37372 bytes 11-build_abe-qemu/console.log.xz | Bin 31980 -> 31932 bytes 12-check_regression/console.log.xz | Bin 3640 -> 3332 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +++++++------- 18 files changed, 51 insertions(+), 51 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-arm-bootstrap_lto updated (c7b9e5fca7 -> 3cbd8e7d35)

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-arm-bootstrap_lto in repository toolchain/ci/base-artifacts. from c7b9e5fca7 52: onsuccess: #461: 2: Success after binutils/gcc: 32 commits new 3cbd8e7d35 53: onsuccess: #462: 2: Success after binutils/gcc: 8 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1664 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2700 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 50568 -> 50636 bytes 05-build_abe-bootstrap_lto/console.log.xz | Bin 473280 -> 473912 bytes 06-check_regression/console.log.xz | Bin 3044 -> 2824 bytes 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 +++++++++--------- 12 files changed, 15 insertions(+), 15 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 (7bc7537330 -> c9cbf18666)

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 7bc7537330 153: onsuccess: #2088: 1: Success after basepoints/gcc-13-30 [...] discards 472c4dd295 152: onsuccess: #2087: 1: Success after gdb-12-branchpoint-2 [...] discards 52b6e7375e 151: onsuccess: #2086: 1: Success after gcc: 2 commits discards 9259650403 150: onsuccess: #2085: 1: Success after gcc: 2 commits discards ba06ad9fe9 149: onsuccess: #2084: 1: Success after gcc: 16 commits discards d906f00347 148: onsuccess: #2082: 1: Success after gdb-12-branchpoint-2 [...] discards 60c52b4f73 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 commits discards c272b1dce8 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits discards 54666e0249 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits discards f45c507203 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits discards 04c2e5ee8a 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits discards fba4b601e8 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits discards 93b8f2fb42 141: onsuccess: #2073: 1: Success after binutils: 3 commits discards f462c6afce 140: onsuccess: #2070: 1: Success after binutils: 4 commits discards e78fbdba6c 139: onsuccess: #2067: 1: Success after binutils: 2 commits discards 979b0b747c 138: onsuccess: #2064: 1: Success after binutils: 4 commits discards 516495b0d9 137: onsuccess: #2061: 1: Success after binutils: 2 commits discards 407cc67967 136: onsuccess: #2056: 1: Success after binutils: 4 commits discards daeff7dc9e 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits discards a4e455a84c 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits discards 3960eeaf83 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits discards 465db58de4 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits discards 77571b88c7 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] discards 69e9d43541 130: onsuccess: #2049: 1: Success after gcc: 9 commits discards fb5a8dbf9e 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] discards 9ca30f2853 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] discards 5645a4e6bc 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] discards 4893330d62 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] discards b90d27abd4 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits discards 82b55ebc07 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits discards 27f3ba11d7 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits discards 3df8dc468b 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits discards ca117e02d8 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits discards 7ab5f00c2a 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits discards 65e975adff 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits discards 03496da56b 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits discards 9b92ff97ee 117: onsuccess: #2034: 1: Success after binutils: 2 commits discards 94930d452e 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits discards 40b2d5107e 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits discards ccbd7401e7 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits discards c25f9d1461 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits discards 3f74f319bb 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits discards 0e2374e031 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits discards ddf8164137 110: onsuccess: #2027: 1: Success after gcc: 5 commits discards 859a81760c 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits discards e5b43f54cb 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits discards efd9a9562f 107: onsuccess: #2024: 1: Success after gcc: 3 commits discards 4e7410a503 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits discards 8ebd22746f 105: onsuccess: #2022: 1: Success after gcc: 4 commits discards d113af2e62 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards 9cf1c3df58 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards 1f0dcd637c 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] discards 28c16ae2c7 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards 65aae017c4 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards 3c14c663d4 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards be8884cb6c 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards bebcf56344 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards 88f50c43ef 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] discards 8b2c04302d 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] discards 2087ef2464 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards 2c797a747f 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] discards 6ff667cec4 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards 751407757c 91: onsuccess: 1: Success after gcc: Daily bump. discards 2c1554af44 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards b4726e85b9 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards c1a21de63c 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards e1764a69b8 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards a06f732784 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards 1d48d71085 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards 61645c402c 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards a4c562eecc 83: onsuccess: 1: Success after gcc: 8 commits discards ddf7d73791 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards d7897b5aa4 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards a7e9b38337 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards 43888555de 79: onsuccess: 1: Successful build after gcc: Daily bump. discards cc2e4fc59c 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 017ab6ab12 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 5f2af24737 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards f75ac976b6 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 07f004a6fb 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards c1856c4aa5 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards 9e44891e36 72: onsuccess: 1: Successful build after gcc: 2 commits discards 20c305093c 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards fd56fa1228 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards 4c80d989d9 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards fc6fd27d01 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards c0ec256b6e 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards b1da618004 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards fa20282b96 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards f6a38de7a8 64: onsuccess: 1: Successful build after gcc: 5 commits discards a0883acf85 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards ee3be0514f 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 5be640e7f9 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits discards 6aaf12a463 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 7d42fc6141 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits discards 5262203c9a 58: onsuccess: 1: Successful build after binutils: 2 commits discards f68c3c0dfc 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards 8eb918dc2e 56: onsuccess: 1: Successful build after gcc: Daily bump. discards 2f1a79bcbb 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 663838a2ff 54: onsuccess: 1: Successful build after gcc: 7 commits discards 7bf024cb1e 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 3ec53ff373 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 59853a802f 54: onsuccess: 1: Successful build after gcc: 7 commits new 50ddeb4e21 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits new db852d4aad 56: onsuccess: 1: Successful build after gcc: Daily bump. new a1e8128709 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits new b685b3b560 58: onsuccess: 1: Successful build after binutils: 2 commits new a4fdcc88e0 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits new bbd7bedbf8 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits new c660902ff6 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits new 067d5b85f3 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits new d10648aca2 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits new bc9cf32470 64: onsuccess: 1: Successful build after gcc: 5 commits new 401d220fce 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits new e50e22a26d 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 066b27a8cd 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new f999ef9e7d 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new be9cbaf782 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] new ff44481147 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new e4963164bc 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new cc97739687 72: onsuccess: 1: Successful build after gcc: 2 commits new 8dd360b863 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 95f11eef6a 74: onsuccess: 1: Successful build after binutils: Automatic [...] new e8ab019cb3 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 23d38ca617 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 686cd33034 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 3cb1180f7e 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new e2c0e4e77c 79: onsuccess: 1: Successful build after gcc: Daily bump. new 262cd5c60c 80: onsuccess: 1: Success after binutils/gcc: 14 commits new 0fe6c7edfb 81: onsuccess: 1: Success after binutils/gcc: 27 commits new 84c096e2a2 82: onsuccess: 1: Success after binutils/gcc: 10 commits new 008ed59bc5 83: onsuccess: 1: Success after gcc: 8 commits new 5a53635d78 84: onsuccess: 1: Success after binutils/gcc: 9 commits new 344cee9d4a 85: onsuccess: 1: Success after binutils/gcc: 9 commits new 14e486c5f3 86: onsuccess: 1: Success after binutils/gcc: 13 commits new e364cedcbf 87: onsuccess: 1: Success after binutils/gcc: 4 commits new d58be10787 88: onsuccess: 1: Success after binutils/gcc: 16 commits new f29590316f 89: onsuccess: 1: Success after binutils/gcc: 9 commits new 0fc19a26c3 90: onsuccess: 1: Success after binutils/gcc: 6 commits new fe2ecbd00a 91: onsuccess: 1: Success after gcc: Daily bump. new a6b9bbafa9 92: onsuccess: #1965: 1: Success after gcc: 2 commits new 6fdf73064b 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] new 5f69382c3d 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new aff0e1a33b 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] new 0cc30a4807 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] new 400667b915 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new 8183c793f1 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new d90a9e2b21 99: onsuccess: #1974: 1: Success after gcc: 14 commits new 45cdd9b89d 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new edca4cfc17 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new e6034ffb55 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] new d763134cbe 103: onsuccess: #2020: 1: Success after gcc: 2 commits new 52f2704f1d 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new f5b13b12d3 105: onsuccess: #2022: 1: Success after gcc: 4 commits new 95858b6ad2 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits new 75a6817d63 107: onsuccess: #2024: 1: Success after gcc: 3 commits new 67204e3022 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits new cd20320efc 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits new 7c6e38328d 110: onsuccess: #2027: 1: Success after gcc: 5 commits new 1c20a91b50 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits new cd0b7d64bc 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits new 885d043f68 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits new bc72612c67 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits new 7948dad018 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits new 759eae518d 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits new 2ac191abad 117: onsuccess: #2034: 1: Success after binutils: 2 commits new 1f0a7ba875 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits new ca719c1064 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits new 7e475a00de 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits new 9c7f8fd1ce 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits new 2c26af006a 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits new f25503fca4 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits new a3c75d8e72 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits new 1630d56b19 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits new 96d061d760 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] new f5ac95f85b 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] new 4b6be5552e 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] new 35aca19414 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] new fd3ce7e0de 130: onsuccess: #2049: 1: Success after gcc: 9 commits new 0a240623ed 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] new 6cdbac918c 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits new 5ff901348d 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits new 2adf3a01db 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits new adfa335ff6 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits new 6268cc4be7 136: onsuccess: #2056: 1: Success after binutils: 4 commits new b526021275 137: onsuccess: #2061: 1: Success after binutils: 2 commits new 77d9108fce 138: onsuccess: #2064: 1: Success after binutils: 4 commits new 4420338100 139: onsuccess: #2067: 1: Success after binutils: 2 commits new ad1506c871 140: onsuccess: #2070: 1: Success after binutils: 4 commits new c528b8c435 141: onsuccess: #2073: 1: Success after binutils: 3 commits new 3dd63f74a0 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits new f26bf6a971 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits new 6224afda52 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits new f77e07073f 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits new c5c89b72a8 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits new 62fffada52 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 commits new 395d6ca0db 148: onsuccess: #2082: 1: Success after gdb-12-branchpoint-2 [...] new e8c8efb7e6 149: onsuccess: #2084: 1: Success after gcc: 16 commits new 03ff894c3c 150: onsuccess: #2085: 1: Success after gcc: 2 commits new 883a41e65a 151: onsuccess: #2086: 1: Success after gcc: 2 commits new 2468f7bbad 152: onsuccess: #2087: 1: Success after gdb-12-branchpoint-2 [...] new 1dfefea628 153: onsuccess: #2088: 1: Success after basepoints/gcc-13-30 [...] new c9cbf18666 154: onsuccess: #2089: 1: Success after gcc: 4 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 (7bc7537330) \ 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 1732 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 38084 -> 37564 bytes 04-build_abe-gcc/console.log.xz | Bin 214392 -> 213372 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3836 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2376 -> 2828 bytes 07-check_regression/console.log.xz | Bin 4312 -> 5200 bytes 07-check_regression/extra-bisect-params | 1 + 07-check_regression/fails.sum | 12 + 07-check_regression/mail-body.txt | 32 + 07-check_regression/results.compare | 31 +- 07-check_regression/results.compare2 | 46 +- 07-check_regression/results.regressions | 32 + 08-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 34 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 32 + sumfiles/g++.log.xz | Bin 3588420 -> 3585388 bytes sumfiles/g++.sum | 114 +- sumfiles/gcc.log.xz | Bin 3099260 -> 3091848 bytes sumfiles/gcc.sum | 5400 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1039552 -> 1041764 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2184 -> 2188 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207604 -> 207636 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2548 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 450100 -> 450640 bytes sumfiles/libstdc++.sum | 10 +- 35 files changed, 3032 insertions(+), 2850 deletions(-) create mode 100644 07-check_regression/extra-bisect-params create mode 100644 07-check_regression/fails.sum create mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[binutils-gdb] branch master updated (f7052ade774 -> 08f406e9a1e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from f7052ade774 Automatic date update in version.in new 21a52f7d827 gdb/testsuite: new test for -data-disassemble opcodes format new d309a8f9b34 gdb/disasm: read opcodes bytes with a single read_code call new d4ce49b7ac0 gdb: disassembler opcode display formatting new 2bfed4e8725 gdb: make gdb_disassembly_flag unsigned new 48883ade647 gdb/doc: update syntax of -data-disassemble command arguments new 924272f2bf5 gdb/mi: some int to bool conversion new 08f406e9a1e gdb/mi: new options for -data-disassemble command The 7 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gdb/NEWS | 12 +++ gdb/cli/cli-cmds.c | 6 ++ gdb/disasm-flags.h | 3 +- gdb/disasm.c | 55 +++++++++-- gdb/disasm.h | 3 + gdb/doc/gdb.texinfo | 159 +++++++++++++++++++++++++------- gdb/mi/mi-cmd-disas.c | 105 ++++++++++++++++----- gdb/record.c | 3 + gdb/testsuite/gdb.mi/mi-disassemble.exp | 153 +++++++++++++++++++++++++----- gdb/testsuite/lib/mi-support.exp | 27 ++++++ 10 files changed, 437 insertions(+), 89 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