Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto updated (316b9b164a -> f0fec7cec5)

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 in repository toolchain/ci/base-artifacts. from 316b9b164a 47: force: #443: 1: Failure after basepoints/gcc-13-2871-g1b [...] new f0fec7cec5 48: onsuccess: #444: 1: Success after gcc: 14 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 1584 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2712 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 50424 -> 50852 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 107980 -> 108092 bytes 06-check_regression/console.log.xz | Bin 3276 -> 2668 bytes 06-check_regression/jira-body.txt | 2 +- 06-check_regression/mail-body.txt | 20 +- 06-check_regression/mail-subject.txt | 2 +- 06-check_regression/results.regressions | 9 - 06-check_regression/trigger-bisect | 2 - 06-check_regression/trigger-notify | 0 dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 210 --------------------- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 20 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 9 - 23 files changed, 33 insertions(+), 272 deletions(-) delete mode 100644 06-check_regression/results.regressions delete mode 100644 06-check_regression/trigger-bisect delete mode 100644 06-check_regression/trigger-notify delete mode 100644 jenkins/jira-status.draft delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

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

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 b721a53d64 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits discards 6686a2cca7 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] discards 60d42435ef 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits discards 3bf2cdcb54 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits discards 8f31cf030e 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards 787df8d6d6 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] discards eeeae63b7f 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards 46fc25c5fe 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards 816b54f8ce 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards e3dc3263a6 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards 4a3d6a598f 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards 95ecfe5d38 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards a1072df597 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards f81385134f 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards 61d2e43fb9 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards e9c3847eda 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards 2f45cad5ac 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards 6959193559 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards 334a74405e 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards c5e487bc0b 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards a70152c538 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards be50ea5e24 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 4023415c52 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards f3869da67b 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards efad3665d5 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards 83cf4376dd 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 935571ad1d 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 41e65df0da 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards bfac9a1fec 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards 37fabfd79b 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 96e3f4a1cc 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards caf4f9af2f 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards d8164a8a45 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 0b71ac8643 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 6fc9a2be25 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 669f8c689e 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards 9137420bea 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards a685304c92 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 4333429aff 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards 57e28253ed 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards 6db0bdbb1f 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 654d968bfd 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards a7486bdffd 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards 41e03433e7 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards d8948cda8d 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards f736f1f98c 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 9e5fc61408 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 4e1b8d523a 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards 8020a54b39 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards b04940768e 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 996d3c4887 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 6c0fba64f9 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 9efdb80e6f 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 15c77bbf8e 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 91d79f3538 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards ac87c3d470 88: onsuccess: 1: Success after gcc: 20 commits discards 22db97d9fd 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards 597d5bae0f 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards b3533c1cfe 85: onsuccess: 2: Success after binutils: 4 commits discards 9f9d7a0c33 84: onsuccess: 2: Success after gcc: 9 commits discards 28b471ff0a 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 1c788a79cc 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 40a8fcf668 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards f241733788 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 0ec2b1aecc 79: onsuccess: 1: Successful build after gcc: 3 commits discards b018776a85 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 3f9b94e076 77: force: 2: Successful build after gcc: 32 commits discards f3e5e06dbf 76: onsuccess: 2: Successful build after binutils: 10 commits discards 934c73b244 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 8549b36f9d 74: onsuccess: 2: Successful build after gcc: 13 commits discards 25d6b2d336 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 2da2369004 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 7abd7065f8 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards c7140e48b3 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards f77e97724c 69: onsuccess: 2: Successful build after baseline build: no [...] discards 776859926b 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 68fda19d4f 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards d119904856 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 5c64e704ae 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 9ef0685b0e 64: onsuccess: 2: Successful build after gcc: 7 commits discards 645d55db21 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards a105c79cb9 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards a1ef177779 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 799a54e448 60: onsuccess: 1: Successful build after gcc: 15 commits discards 3e6dfd59b9 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 59c4c0c747 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards 8bab4aea72 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards d723014e30 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 16b9478125 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 302df28d35 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 8859bd7423 53: onsuccess: 2: Successful build after gcc: 5 commits discards a92791edc4 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards c3ff845b96 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 2681a96aca 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 0b80d778e8 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards a4e7c553aa 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards ce85bff53a 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards a88c518f96 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards f11ef52def 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards d6015fd7b5 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 8ebc7de16b 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new 37b9a75ee9 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new 1532d99ed4 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 8a3d6d1b4b 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new d295b4ae19 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 4e480f3e44 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 3dbec75355 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 06930f8297 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 1366f69ddb 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 5386f73c8d 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 3242b09525 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new ce96fa0662 53: onsuccess: 2: Successful build after gcc: 5 commits new 1f01494fb3 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new e1e28d31c8 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 8eab788108 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 22d20b86f0 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new f4dc731767 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new d318d8d8cb 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 0ef4bea712 60: onsuccess: 1: Successful build after gcc: 15 commits new 5b56c692e3 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 5b862e1697 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 08f1b2aa74 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 26b3176a6e 64: onsuccess: 2: Successful build after gcc: 7 commits new 470450dbed 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 3a1068f8ba 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 6d3b1be02f 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 719f732a11 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 9d548d8d96 69: onsuccess: 2: Successful build after baseline build: no [...] new e539379257 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 8caa253f83 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 7bd44acb3a 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new cea596ad04 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 74e9f7ed5c 74: onsuccess: 2: Successful build after gcc: 13 commits new cfb9eab28b 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 4788067e50 76: onsuccess: 2: Successful build after binutils: 10 commits new 727249cbb3 77: force: 2: Successful build after gcc: 32 commits new 79b07110c1 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 9693732298 79: onsuccess: 1: Successful build after gcc: 3 commits new 899055e5a5 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new f8e152c383 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 1eb4c35a78 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 0199180fb4 83: onsuccess: 2: Success after binutils/gcc: 7 commits new dc9cc1f6d9 84: onsuccess: 2: Success after gcc: 9 commits new 8a85dcd14d 85: onsuccess: 2: Success after binutils: 4 commits new accd0785d6 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new df19746e4d 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new 7d5054890b 88: onsuccess: 1: Success after gcc: 20 commits new bfd1d0fb3a 89: onsuccess: 2: Success after binutils/gcc: 39 commits new f79fb68897 90: onsuccess: #1472: 2: Success after gcc: 2 commits new a9bccf7ddc 91: onsuccess: #1473: 2: Success after gcc: 2 commits new c32d83cec0 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 80c6c74124 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new f8660f567c 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new 9f8747e81b 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new a0c028c5b9 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 2a6bb15751 97: onsuccess: #1481: 2: Success after gcc: 8 commits new b1b2703e78 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new cecb35ac25 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 02465e095b 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new 5a9cb72da5 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new 5799181ab1 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new eeb2cf9a38 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 6556d37fa4 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new da97157abb 105: onsuccess: #1526: 2: Success after gcc: 2 commits new ccf7534114 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 0741e2e988 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new f14a01bb45 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 5584aa5011 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 005af6feee 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 9cf6f7fea0 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 1cf971cd9f 112: onsuccess: #1533: 2: Success after gcc: 5 commits new f1d0d76322 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new ba0f469dd0 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 7d524cd6e2 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 476455da13 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 6715c165c0 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new ac9ef75b6d 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 8a147f8b16 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new edbede8ab4 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 9e01213964 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new aab460dffb 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 3f12e5af96 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 712bcfbd73 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new c6617cf137 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new e0a319038c 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new 3e120b1959 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new b7a413f575 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new 0f7c0c3c5c 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new 3c2f592864 130: onsuccess: #1554: 2: Success after gcc: 9 commits new f8f17c7afc 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new e4070f3925 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new 1ee692072b 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new fe429ac68c 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new 058717bb5b 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new b209ee9feb 136: onsuccess: #1561: 2: Success after binutils: 3 commits new d61500f37c 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new 9dab17a7dc 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] new a90bbef6f7 139: onsuccess: #1566: 1: Success after gcc: 5 commits new 704a4654fd 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits new 1bf4835291 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits new 2c5cab1aed 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] new db33f9a08b 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits new e2df2325a5 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 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 (b721a53d64) \ 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 1740 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2708 bytes 04-build_abe-binutils/console.log.xz | Bin 37652 -> 37924 bytes 05-build_abe-bootstrap/console.log.xz | Bin 272200 -> 270884 bytes 06-check_regression/console.log.xz | Bin 2844 -> 2888 bytes 06-check_regression/mail-body.txt | 2 +- 07-update_baseline/console.log | 38 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 18 ++++++++-------- 14 files changed, 36 insertions(+), 36 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[binutils-gdb] branch master updated (ac9b8c676e9 -> 31282a84910)

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 ac9b8c676e9 Constify target_desc declarations new 31282a84910 gdb: constify target_stack::is_pushed The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gdb/inferior.h | 2 +- gdb/target.h | 2 +- 2 files changed, 2 insertions(+), 2 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_profiled_lto updated (f6cadb1960 -> 316b9b164a)

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 in repository toolchain/ci/base-artifacts. from f6cadb1960 46: force: #442: 2: Success after gcc: 28 commits new 316b9b164a 47: force: #443: 1: Failure after basepoints/gcc-13-2871-g1b [...] 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 1788 -> 1584 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2712 bytes 04-build_abe-binutils/console.log.xz | Bin 50756 -> 50424 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 950436 -> 107980 bytes 06-check_regression/console.log.xz | Bin 2712 -> 3276 bytes 06-check_regression/jira-body.txt | 2 +- 06-check_regression/mail-body.txt | 13 +- 06-check_regression/mail-subject.txt | 2 +- 06-check_regression/results.regressions | 9 + 06-check_regression/trigger-bisect | 2 + .../trigger-notify | 0 dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 210 +++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 13 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 11 +- 23 files changed, 275 insertions(+), 18 deletions(-) create mode 100644 06-check_regression/results.regressions create mode 100644 06-check_regression/trigger-bisect copy 07-update_baseline/console.log => 06-check_regression/trigger-notify (100%) create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/interesting-commits] branch master updated (f241528 -> f7d76eb)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from f241528 Add entry e07ead85a368173a56e96a21d6841aa497ad80f8 from https [...] new f7d76eb Add entry 1b74b5cb4e9d7191f298245063a8f9c3a1bbeff4 from https [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: .../build_url | 2 +- .../last_good | 0 .../summary.txt | 0 .../tcwg_gcc_bootstrap/status.txt | 3 +++ 4 files changed, 4 insertions(+), 1 deletion(-) copy gcc/sha1/1b74b5cb4e9d7191f298245063a8f9c3a1bbeff4/tcwg_gcc_bootstrap/{master- [...] copy gcc/sha1/1b74b5cb4e9d7191f298245063a8f9c3a1bbeff4/tcwg_gcc_bootstrap/{master- [...] copy gcc/sha1/1b74b5cb4e9d7191f298245063a8f9c3a1bbeff4/tcwg_gcc_bootstrap/{master- [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto updated (e24705461d -> f6cadb1960)

by git＠git.linaro.org

2 years, 1 month

[gcc] branch master updated (04d54b70fe2 -> c2ee70f20de)

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 04d54b70fe2 c++: fix triviality of class with unsatisfied op= new c2ee70f20de c++: implicit lookup of std::initializer_list [PR102576] 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/cp/pt.cc | 5 +++-- gcc/testsuite/g++.dg/modules/{anon-2_a.H => pr102576_a.H} | 3 ++- gcc/testsuite/g++.dg/modules/pr102576_b.C | 9 +++++++++ 3 files changed, 14 insertions(+), 3 deletions(-) copy gcc/testsuite/g++.dg/modules/{anon-2_a.H => pr102576_a.H} (60%) create mode 100644 gcc/testsuite/g++.dg/modules/pr102576_b.C -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[glibc] branch users/skpgkp2/2.33/master updated (c5f094a2ef -> 46bcc6c0c9)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch users/skpgkp2/2.33/master in repository glibc. discards c5f094a2ef x86_64: roundeven with sse4.1 support discards d970e709cd math: redirect roundeven function new 5da65a9be3 AArch64: Add support for roundeven[f] new 63b6eecd08 math: redirect roundeven function new b85d5b3fe1 x86_64: roundeven with sse4.1 support new 6e6e51a1a2 Use GCC builtins for roundeven functions if desired. new 224c17c70b Update math: redirect roundeven function new 46bcc6c0c9 s390x: Update math: redirect roundeven function 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 (c5f094a2ef) \ N -- N -- N refs/heads/users/skpgkp2/2.33/master (46bcc6c0c9) 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 6 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: sysdeps/aarch64/fpu/{s_fmin.c => s_roundeven.c} | 11 ++++++----- sysdeps/{x86_64/fpu/s_fabsf.c => aarch64/fpu/s_roundevenf.c} | 12 +++++++----- sysdeps/generic/math-use-builtins-roundeven.h | 4 ++++ sysdeps/generic/math-use-builtins.h | 1 + sysdeps/ieee754/dbl-64/s_roundeven.c | 5 +++++ sysdeps/ieee754/float128/float128_private.h | 2 ++ sysdeps/ieee754/flt-32/s_roundevenf.c | 5 +++++ sysdeps/ieee754/ldbl-128/s_roundevenl.c | 5 +++++ sysdeps/ieee754/ldbl-128ibm/s_roundevenl.c | 1 + sysdeps/riscv/rv64/rvd/s_roundeven.c | 2 +- sysdeps/riscv/rvf/s_roundevenf.c | 1 + sysdeps/s390/fpu/s_roundeven.c | 2 +- sysdeps/s390/fpu/s_roundevenf.c | 1 + sysdeps/s390/fpu/s_roundevenl.c | 1 + 14 files changed, 41 insertions(+), 12 deletions(-) copy sysdeps/aarch64/fpu/{s_fmin.c => s_roundeven.c} (78%) copy sysdeps/{x86_64/fpu/s_fabsf.c => aarch64/fpu/s_roundevenf.c} (78%) create mode 100644 sysdeps/generic/math-use-builtins-roundeven.h -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch releases/gcc-12 updated (2773a90c0f4 -> aeba3e009b0)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-12 in repository gcc. from 2773a90c0f4 Fortran: error recovery while simplifying intrinsic UNPACK [...] new aeba3e009b0 c++: fix triviality of class with unsatisfied op= 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/cp/class.cc | 13 ++++++++-- gcc/testsuite/g++.dg/cpp2a/cond-triv3.C | 44 +++++++++++++++++++++++++++++++++ 2 files changed, 55 insertions(+), 2 deletions(-) create mode 100644 gcc/testsuite/g++.dg/cpp2a/cond-triv3.C -- 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 (d6530f261f -> 6a0c8c6863)

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 d6530f261f 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards 6345e70693 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 066f13e31c 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards 0462501b71 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards f868739e05 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards bcc0bd7205 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards 6f9ead865a 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards ff2d4fd0ad 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards 0276a34e79 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards 4ef3ca9455 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards b93336df1b 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards 0d866e2382 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards e86e925866 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards e477e1b269 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 93221a84a8 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards a1d426551e 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 0a7d9940e2 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards b247abb051 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 64c4e22f2e 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 9dea480071 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards ceea326da7 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards e101ca99d0 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards aa10567db8 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 1a065730fd 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 6f7508f0d7 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards 1bfe9ae672 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 925befb799 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards 78268e2576 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 138dd11ce8 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 269119eee2 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards df2634c3d0 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards bdf77a9a77 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards d012f54652 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 656d76f4cf 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 63197181b6 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 1ad91195be 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 3265a194bb 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 400bbd6ab7 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards ef727d7ad1 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards c5ec308fc3 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards dcc6688543 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 7e603acff7 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 942e893117 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards a7ca685515 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards d3ea949392 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 01a9c4283e 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 8aeebbfdbf 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 4316464788 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 7380c3392c 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 1c2606693b 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 32fdf7d18e 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 88cdb26c38 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards b4359b6b05 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards 8c3b333966 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 7b65713e6d 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards c40eabec47 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 7b100e76c9 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards b3c9b397bb 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards a5de335d1b 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1d7de50a5d 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 8c27c939c6 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards d96080d56e 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 4bb1925841 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards c3a7903478 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 506896a745 85: onsuccess: 7: Success after gcc: 9 commits discards 2504d485c1 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 8ecaf0ee5f 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards b1665ed8f6 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards dea433b0bf 81: onsuccess: 7: Successful build after gcc: 2 commits discards 1309e5aa52 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 37e89df739 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 9e853744d6 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c0a8c6d78b 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 3bf23d4a55 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 98de1353e0 75: onsuccess: 7: Successful build after linux: 44 commits discards e7e91712f8 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards b8d6a3aa9b 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 804b1ad909 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 25420a705e 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 4ec89117de 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards e5baf782cf 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 61aaa4d033 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 1d9d1c6075 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 119f12ca9d 66: onsuccess: 7: Successful build after gcc: 3 commits discards 22a29326a4 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9ac2396cc8 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f4a0ae7fca 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards a6bdaa32cd 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 1f77b5de7b 61: onsuccess: 4: Successful build after gcc: 15 commits discards 2582c51851 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 1be39ec317 59: force: 7: Successful build after gcc: 2 commits discards c62006d1f9 58: onsuccess: 7: Successful build after glibc: 2 commits discards a09b4234a3 57: onsuccess: 7: Successful build after gcc: 7 commits discards 6a3208a7b3 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f512d3f4dd 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 68d77a174b 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 720b238f81 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 69274a5aef 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards d76a646edd 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 1f8ff07fa0 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 53b44d0a0f 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 13009a059e 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new b0011699ae 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4d6625b041 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 3a408d0f25 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new e0753d7c7f 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 4314935b62 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 8fb95c4bb5 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 275a729692 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ed7e6d26da 57: onsuccess: 7: Successful build after gcc: 7 commits new c268477658 58: onsuccess: 7: Successful build after glibc: 2 commits new 15be51bdd1 59: force: 7: Successful build after gcc: 2 commits new d0c124760f 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new a6e464fcdc 61: onsuccess: 4: Successful build after gcc: 15 commits new 91c34a2184 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 29e03c624d 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new c64443559d 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 11cbac398c 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 52c71eca12 66: onsuccess: 7: Successful build after gcc: 3 commits new 6e348a1845 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new a94c9c32a7 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 04c9bf381e 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 51c9ef4933 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new f0e99b5512 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new e7121a894a 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new bddf0f3852 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f11df7affb 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new ff603f16ce 75: onsuccess: 7: Successful build after linux: 44 commits new 2db091681c 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 04d5c29079 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new e66943f687 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f0c24de5ee 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 181f07fd79 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 2f711d8e99 81: onsuccess: 7: Successful build after gcc: 2 commits new 6b1e447491 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 20f75d5df0 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 28e9aaa5aa 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 7c675aa576 85: onsuccess: 7: Success after gcc: 9 commits new f70138a08d 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 047d49b869 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new bb376421b6 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 3c1792c5ae 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new e50ba34e39 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 933db73a4e 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 6a6338b50b 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 6679cfece0 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new 9f901f685e 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 927dc72d09 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new feaf1ae7e8 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 6967f39b46 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 13edd0ccb4 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 38976bdc5e 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 8fa4929724 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new 92f603987b 101: onsuccess: #1609: 7: Success after binutils: 78 commits new a323258e3d 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 11c8f2e08f 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 2cd246ceb0 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 35195acd46 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 8dd99a1326 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 00e57e46db 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 64025fa4b4 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new ea841b8750 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 2102b5bc85 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new 4e2957400c 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 97a63a66c9 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new ca1e2762be 113: onsuccess: #1624: 7: Success after gcc: 6 commits new abf47d809c 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 10fde3257c 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 3a439d2f84 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new b75131d5bc 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new a4ac7028c2 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 956860dfb8 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 9c0822fb0c 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new e45a9ccc18 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new b4d48a8d3f 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 89f1825736 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new bae1252d24 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 64db71a4ed 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new 7fb3453c06 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new d7e0e28325 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 9a75e9059d 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 3ed8d9a4c3 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new e8123c44a5 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 7b1d8b15c0 131: onsuccess: #1644: 7: Success after gcc: 10 commits new df4e278bd4 132: onsuccess: #1645: 7: Success after linux: 23 commits new 076dfd5472 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new 4256df1dcb 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new 0d7fffa7d9 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new 709a46a2c4 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 0e2486eab7 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new 9cca03e509 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new 08e6b96583 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 1931309914 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new a03b36444e 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 74e161138c 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 7a8f878d1b 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new 5b7c5a62fa 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new 2d1e96b14e 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new 6f7e38ab08 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new 0d9197f93b 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new 8fe99d549b 148: onsuccess: #1663: 7: Success after glibc: 2 commits new 5d7d3ae495 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new 6a0c8c6863 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (d6530f261f) \ 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 1664 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30156 -> 30384 bytes 05-build_abe-stage1/console.log.xz | Bin 90744 -> 90568 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8752 -> 9308 bytes 08-build_abe-glibc/console.log.xz | Bin 234296 -> 234216 bytes 09-build_abe-stage2/console.log.xz | Bin 224192 -> 224120 bytes 10-build_abe-gdb/console.log.xz | Bin 37360 -> 37680 bytes 11-build_abe-qemu/console.log.xz | Bin 30724 -> 31404 bytes 12-check_regression/console.log.xz | Bin 3616 -> 4540 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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +++++++++++------------ 22 files changed, 62 insertions(+), 62 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022