Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-allyesconfig updated (5dbcbda011 -> 4d958db092)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-allyesconfig in repository toolchain/ci/base-artifacts. from 5dbcbda011 25: force: #489: 37: Failure after llvmorg-16-init-5673-ge07 [...] new 4d958db092 26: onsuccess: #490: 37: Success after llvm: 145 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 1688 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 30136 -> 30172 bytes 04-build_kernel_llvm/console.log.xz | Bin 64676 -> 62620 bytes 05-build_abe-qemu/console.log.xz | Bin 32132 -> 32160 bytes 06-build_linux/console.log.xz | Bin 4644 -> 3844 bytes 08-check_regression/console.log.xz | Bin 3720 -> 3124 bytes 08-check_regression/jira-body.txt | 2 +- 08-check_regression/mail-body.txt | 14 +- 08-check_regression/mail-subject.txt | 2 +- 08-check_regression/results.regressions | 5 - 08-check_regression/trigger-bisect | 2 - 08-check_regression/trigger-notify | 0 09-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/llvm_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 438 -------------------------------- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 14 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 5 - 26 files changed, 28 insertions(+), 487 deletions(-) delete mode 100644 08-check_regression/results.regressions delete mode 100644 08-check_regression/trigger-bisect delete mode 100644 08-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, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled updated (c2030b1142 -> b82986dffb)

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 in repository toolchain/ci/base-artifacts. from c2030b1142 43: onsuccess: #437: 2: Success after binutils: 8 commits new b82986dffb 44: force: #440: 2: Success after gcc: 29 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 1628 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 51680 -> 52268 bytes 05-build_abe-bootstrap_profiled/console.log.xz | Bin 936028 -> 930384 bytes 06-check_regression/console.log.xz | Bin 2704 -> 2704 bytes dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 11 files changed, 14 insertions(+), 14 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-allyesconfig updated (3403d7764f -> 5dbcbda011)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-allyesconfig in repository toolchain/ci/base-artifacts. from 3403d7764f 24: force: #488: 19905: Success after llvm: 638 commits new 5dbcbda011 25: force: #489: 37: Failure after llvmorg-16-init-5673-ge07 [...] 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 2752 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30392 -> 30136 bytes 04-build_kernel_llvm/console.log.xz | Bin 64220 -> 64676 bytes 05-build_abe-qemu/console.log.xz | Bin 32392 -> 32132 bytes 06-build_linux/console.log.xz | Bin 4624 -> 4644 bytes 08-check_regression/console.log.xz | Bin 3092 -> 3720 bytes 08-check_regression/jira-body.txt | 2 +- 08-check_regression/mail-body.txt | 9 +- 08-check_regression/mail-subject.txt | 2 +- 08-check_regression/results.regressions | 5 + 08-check_regression/trigger-bisect | 2 + 08-check_regression/trigger-notify | 0 dashboard/dashboard-generate.sh | 2 +- git/llvm_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 438 ++++++++++++++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 9 +- mail/mail-subject.txt | 2 +- manifest.sh | 12 +- results | 7 +- 25 files changed, 486 insertions(+), 17 deletions(-) create mode 100644 08-check_regression/results.regressions create mode 100644 08-check_regression/trigger-bisect create mode 100644 08-check_regression/trigger-notify create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/interesting-commits] branch master updated (1dfd8d9 -> fad7948)

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 1dfd8d9 Add entry 1b7089fe67b924bdd5ecef786a34bdba7a88778f from https [...] new fad7948 Add entry e07ead85a368173a56e96a21d6841aa497ad80f8 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 .../e07ead85a368173a56e96a21d6841aa497ad80f8/tcwg_kernel/status.txt | 3 +++ 4 files changed, 4 insertions(+), 1 deletion(-) copy llvm/sha1/e07ead85a368173a56e96a21d6841aa497ad80f8/tcwg_kernel/{llvm-master-a [...] copy llvm/sha1/e07ead85a368173a56e96a21d6841aa497ad80f8/tcwg_kernel/{llvm-master-a [...] copy llvm/sha1/e07ead85a368173a56e96a21d6841aa497ad80f8/tcwg_kernel/{llvm-master-a [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

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

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 dffe7e64a4 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits discards fc971084a2 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards 5bd3750114 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] discards f8450a4e96 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards 36033ee4e8 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards 758f6ac094 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards 1f351730bb 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards b18efac88e 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards 0ad5d579f3 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards 1f86a7de80 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards 07a1e448ea 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards f2102539cc 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards d0643c32cb 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards 48b8570fa6 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards 3c9ff417e9 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards 3f7a3451aa 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards fc169844ad 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards 7e1a112706 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards af67af3263 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 67c1dad625 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards db73ab08db 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards 45422693ae 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards f6ea1fee85 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 8a89d87672 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 66743fe5ce 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 8152a2fbe4 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards 8c8547ce9a 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards d1e0a4d1f7 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards fd45360139 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards 11b09fd6fd 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 4c5664b55e 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 3bbb609891 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 0b795bebc9 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards a3c63e85b6 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 323a223e3e 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 90c42ee657 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards 07db120b6c 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards bf98fbea7a 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 9ed795ab61 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards b2cf20ae98 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards c642153784 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 6905a77008 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards 904a1af05f 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards f1891e42a4 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards eb2d00236c 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards e59cc35961 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 3b53d22a56 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 3b8bdbfc85 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 60d3432bf1 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 237a8278cf 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards e5e4074570 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 8d0aa589b7 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 0617c8302d 88: onsuccess: 1: Success after gcc: 20 commits discards 502efe2eb3 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards f6a6f6e8ae 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards f49f3fbcc1 85: onsuccess: 2: Success after binutils: 4 commits discards 4f76d2c8d3 84: onsuccess: 2: Success after gcc: 9 commits discards 7e4cd4c665 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards e7ef387a6d 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 0717c72393 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 57277fbfde 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 6b113239fb 79: onsuccess: 1: Successful build after gcc: 3 commits discards b32084d20e 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 116adef768 77: force: 2: Successful build after gcc: 32 commits discards 29f84e0a5c 76: onsuccess: 2: Successful build after binutils: 10 commits discards 0b63f680d1 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 74165f3c8f 74: onsuccess: 2: Successful build after gcc: 13 commits discards 1a4f4f9229 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards e5aeb7928a 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 7edfba27ce 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 87c21bb655 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 2ca5ee087d 69: onsuccess: 2: Successful build after baseline build: no [...] discards 7a9153f206 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 45e67ffbb0 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 75981bf6d0 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 1f67d9b284 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards a24a10c930 64: onsuccess: 2: Successful build after gcc: 7 commits discards 8b385ff1b8 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards a79f286b64 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 23b22cbecd 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 6d4538fa99 60: onsuccess: 1: Successful build after gcc: 15 commits discards af4c7cb2b4 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 385281cff7 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards 8d496666e4 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 4c9bffe094 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 7f09a53e5b 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 178a4865d0 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 1f34fdf8e6 53: onsuccess: 2: Successful build after gcc: 5 commits discards 59bcb84a77 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 435f42b3fa 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 5d2d247355 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 9e8c011283 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards cff74e1b22 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 2d9e00ca61 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 41dfc5430e 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 6d09b9354c 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards 7000d9480c 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 157c628e18 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards 5a755ce570 42: onsuccess: 2: Successful build after gcc: 2 commits discards 2645c6f7ec 41: onsuccess: 2: Successful build after baseline build: no [...] discards 9a82deaf09 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new fae6962f6d 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 0dcedb1613 41: onsuccess: 2: Successful build after baseline build: no [...] new 77e3d060a8 42: onsuccess: 2: Successful build after gcc: 2 commits new b71aedf8c0 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new f6de4a8d54 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 022d0ba10c 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new ad2df3fafe 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 459a7ad7a4 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 60c0ddcc49 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 27ef903bac 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 096025cc3e 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new a926ec0b45 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new c94291233a 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new e31bfcf08a 53: onsuccess: 2: Successful build after gcc: 5 commits new f26fd6c241 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 51fbd39765 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new a4496ef2c2 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new c98c0fcbb5 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 6a5e223314 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new 2749a7ac8b 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new a2bf100a15 60: onsuccess: 1: Successful build after gcc: 15 commits new 443f71d456 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 9b40d67311 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 76f3d48474 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 09c5984d61 64: onsuccess: 2: Successful build after gcc: 7 commits new e397509ff9 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 3267ddd7ac 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 5314aaa81f 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new c35b1bde18 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 00976aca70 69: onsuccess: 2: Successful build after baseline build: no [...] new a20c0469fc 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 1c7d38c1ac 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 23b5db938e 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 5c54365a28 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 6cf842652b 74: onsuccess: 2: Successful build after gcc: 13 commits new 9e6e00c077 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 4d97984824 76: onsuccess: 2: Successful build after binutils: 10 commits new c829258f47 77: force: 2: Successful build after gcc: 32 commits new 72d4d2e384 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 9ba08bbaf5 79: onsuccess: 1: Successful build after gcc: 3 commits new c9f104817b 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 706a0f2f4d 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 353e9657ee 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 0d6756a9a4 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 2f36657552 84: onsuccess: 2: Success after gcc: 9 commits new b35318e71e 85: onsuccess: 2: Success after binutils: 4 commits new 70ea99e876 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new 7cfcba9a33 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new defef53ca7 88: onsuccess: 1: Success after gcc: 20 commits new f8163cf810 89: onsuccess: 2: Success after binutils/gcc: 39 commits new c101ab7dfa 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 77f160a8b4 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 9ca58a450b 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 3446d7c940 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new 3d7296adbc 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new 4151e7bd6d 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new caa413966b 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 9ce40e9ca5 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 18643dea4f 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 3da63a48b6 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 8c92762909 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new ce6af7080c 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new 62ee7971c2 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 769a566fab 103: onsuccess: #1524: 2: Success after gcc: 2 commits new d82fef84d1 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 6de85b5071 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 64e7ebd51f 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 68e955358a 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new a6858a2332 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 848939d72b 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 5a27be31a1 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new bfbe2874ff 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new e2e7c8e051 112: onsuccess: #1533: 2: Success after gcc: 5 commits new e6131d811e 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new 7ca45609e4 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 2f4145fa58 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 4340076d74 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new f751ebe0e6 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new e03fea1c78 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 197630f33a 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new b803da1498 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 7369843715 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new afa68c22c6 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new ecd8fdf2c6 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 2e159c424d 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new 0be9fe3b40 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new 235e5da1cb 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new 2361bf8cd2 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new 2427a6e541 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new 99144ceb20 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new 1a95d390b7 130: onsuccess: #1554: 2: Success after gcc: 9 commits new 4cbb2323c5 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new 30d8067b3c 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new 65dece7e6e 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new 08ad8c5e00 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new dbdfe38659 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new e144415d79 136: onsuccess: #1561: 2: Success after binutils: 3 commits new b5073e015c 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new 23af48f50d 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] new c89278ad42 139: onsuccess: #1566: 1: Success after gcc: 5 commits new db4b5e1b6e 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits new 8f1830b193 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 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 (dffe7e64a4) \ 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 1664 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2716 bytes 04-build_abe-binutils/console.log.xz | Bin 38064 -> 37640 bytes 05-build_abe-bootstrap/console.log.xz | Bin 78636 -> 79072 bytes 06-check_regression/console.log.xz | Bin 3120 -> 2792 bytes 07-update_baseline/console.log | 58 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++------ 13 files changed, 44 insertions(+), 44 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[glibc] branch release/2.31/master updated (c8f2a3e803 -> d4b7559457)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch release/2.31/master in repository glibc. from c8f2a3e803 Add test for bug 29530 new b8bb48a18d x86-64: Require BMI2 for strchr-avx2.S [BZ #29611] new d4b7559457 x86-64: Require BMI2 for avx2 functions [BZ #29611] The 2 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/x86_64/multiarch/ifunc-avx2.h | 4 +-- sysdeps/x86_64/multiarch/ifunc-impl-list.c | 50 ++++++++++++++++++++++-------- 2 files changed, 39 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (30c3e235d1 -> 5011ad2e3e)

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 30c3e235d1 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards 35c2b014a0 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards d4d779c2bd 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards 4da951eddc 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards 8e34232ec4 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards 68efea14ea 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards f42e5525e9 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards 862578ec82 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards 7178cac400 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards 0779b1b394 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards 53b4505c7f 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards b01ddcd352 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards 059a5093de 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 1939cda643 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards 1293cb4b2e 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 1a7efd4e76 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 866659b308 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards 272792eac6 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards fd65f9481f 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards 8f64c50419 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards e8881f11d5 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards bd1a3ed940 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards a778c51cdb 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards bdb55bd006 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards 5efa611571 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 3057312286 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards eb74760a95 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 7a18dcadd7 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 260094f831 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 5c8142f579 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 4b97b7d7e1 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 8527ad15ac 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 6cfad942bf 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 887bcb3e14 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 4d1e6d1cdc 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards eed571ce73 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 50ea6c7aed 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards 145c5a5fb8 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards ef5a513a6f 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 1f5d20ab63 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards ae07a9199b 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards f14c68e8f8 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 0e4ef79fa4 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 9699667d49 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 8946396fb6 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 68ee53cc71 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 07670cc210 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 39d0947002 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 6fe24b4b83 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards b5f5998ef9 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards c95b081cf2 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 6d17af861a 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards ca6f898337 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards f8191d79e9 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 1a8f686e58 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 3483d5f6f1 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1c0b1d4385 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 4b465f1fa1 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards ded3cf4eb4 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 2ec1ca4b14 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 7b5e6a89c2 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 20e3bdfbcb 85: onsuccess: 7: Success after gcc: 9 commits discards 907b251ffa 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 6e5a3f752a 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards eb3766c2f7 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 6b8f5ab553 81: onsuccess: 7: Successful build after gcc: 2 commits discards a1e27a4e8c 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards ba1c8c8f78 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 8759bc274f 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c58da9d1c3 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 2f3d7d2d7b 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards eb63abb001 75: onsuccess: 7: Successful build after linux: 44 commits discards c52bc08a6d 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards c4bcd32b61 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 24f0908483 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards a65e0217b3 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 903ff494a1 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards a8bb77e5a1 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards cfab058404 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 783604a055 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards f0e1f1b0ea 66: onsuccess: 7: Successful build after gcc: 3 commits discards cb13df0148 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 65e3eeeceb 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9871cf19b5 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards cccecd93d0 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 8f9e0f817e 61: onsuccess: 4: Successful build after gcc: 15 commits discards 37b1c839ee 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards ae92effa19 59: force: 7: Successful build after gcc: 2 commits discards 2b58508246 58: onsuccess: 7: Successful build after glibc: 2 commits discards 1788c45115 57: onsuccess: 7: Successful build after gcc: 7 commits discards 4760adea9a 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6419aa4ec5 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 72442602f6 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards cebf8a350c 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 42c093b377 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 96ff5757ad 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 26b916726b 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0af42f46f3 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 4a06020c3a 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 3e5c33a278 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c8f05a9492 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 35d1731a48 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 7b5262a8ca 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e9f4b54313 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 4099a3e94d 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 21fde2f0db 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 31806af0de 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 8b1abdcfa9 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new f083c23cf2 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 41dce59db1 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new ca969db069 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new dee5b3fe8b 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new cb21598aa8 57: onsuccess: 7: Successful build after gcc: 7 commits new 9f8901377d 58: onsuccess: 7: Successful build after glibc: 2 commits new 8c9202f169 59: force: 7: Successful build after gcc: 2 commits new 8ead2b1644 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 84ae9744d0 61: onsuccess: 4: Successful build after gcc: 15 commits new db78079cdd 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new c5b3a5e252 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 3f40f84260 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 3cfa30846f 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f413c4c018 66: onsuccess: 7: Successful build after gcc: 3 commits new f603ccf60c 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new c46fced192 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 952dee6504 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new a520354962 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 178d4a0a1d 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 936d4778fd 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 61f2ce91ae 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 9a1b098092 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 9932dc3d8c 75: onsuccess: 7: Successful build after linux: 44 commits new ccad7b9384 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4e6bb3072c 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 0294b18e7c 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 26c65df972 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 3c7c808bae 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 5a3caee4a8 81: onsuccess: 7: Successful build after gcc: 2 commits new 01a6cb7a9d 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 1b0466e395 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 4de4b2840d 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new aaa2ae5778 85: onsuccess: 7: Success after gcc: 9 commits new 462fd58049 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 4d9c2e5b55 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 98a2e57b03 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new a9a9e69d0a 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new c941e02590 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new cc3f9b5170 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 4ef0b0e6bf 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new e4c545af5a 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new ac5fa1e508 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new e63383dd10 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new a421de4760 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new d549779d1b 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 9b3dccd0bb 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 060fac7f84 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 43ee5ff724 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new ad5b2f7cf1 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 381667e2a3 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 225127e64c 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 6be1af5398 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 965bf0927b 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 7dd2b34bfb 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 6dbd99987f 107: onsuccess: #1618: 7: Success after gcc: 2 commits new cbf50f8013 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new cf806e91d7 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 18c1b88726 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new 328c05b730 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new d26ac7b5de 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 5edafe0eea 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 7fcb6283ce 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 2576e35eeb 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 3b963be55b 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 5e0787e32d 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 19f48866b7 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 5ce061d139 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 6376b856f9 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new f2bf180647 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new 98564b0a6d 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 7d93eec2e2 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 53fafbb5e2 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 1c3e514548 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new aed03ba134 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new d0d251fa58 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new df20369e01 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new e8d7b37d79 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 20a120042f 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new a8203cb27a 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 439368fc47 132: onsuccess: #1645: 7: Success after linux: 23 commits new 2c810b4474 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new b2c24781ac 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new 549ae943c7 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new b45ad949eb 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 7de3d67664 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new 1a93687791 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new 00dbe8a65c 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 7990b3a031 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new 3722eb4f78 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 228c11e1c2 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 261a47e696 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new 278a58ec31 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new f772fe0a23 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new b24ac875a8 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new 5011ad2e3e 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/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 (30c3e235d1) \ 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 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30860 -> 29980 bytes 05-build_abe-stage1/console.log.xz | Bin 90900 -> 90448 bytes 07-build_abe-linux/console.log.xz | Bin 8680 -> 8760 bytes 08-build_abe-glibc/console.log.xz | Bin 233216 -> 234124 bytes 09-build_abe-stage2/console.log.xz | Bin 224788 -> 223712 bytes 10-build_abe-gdb/console.log.xz | Bin 38124 -> 37256 bytes 11-build_abe-qemu/console.log.xz | Bin 30904 -> 30728 bytes 12-check_regression/console.log.xz | Bin 4504 -> 3716 bytes 13-update_baseline/console.log | 46 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++++++++++++++--------------- 20 files changed, 50 insertions(+), 50 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[glibc] branch release/2.32/master updated (51b72ac04b -> 6bbc1a3a35)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch release/2.32/master in repository glibc. from 51b72ac04b elf: Call __libc_early_init for reused namespaces (bug 29528) new f9e29095fc x86-64: Require BMI2 for strchr-avx2.S [BZ #29611] new 6bbc1a3a35 x86-64: Require BMI2 for avx2 functions [BZ #29611] The 2 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/x86_64/multiarch/ifunc-avx2.h | 4 +-- sysdeps/x86_64/multiarch/ifunc-impl-list.c | 50 ++++++++++++++++++++++-------- 2 files changed, 39 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (51b3175f11 -> c2b61d0805)

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 51b3175f11 140: onsuccess: #2070: 1: Success after binutils: 4 commits discards a42b125eaf 139: onsuccess: #2067: 1: Success after binutils: 2 commits discards 9a034fa335 138: onsuccess: #2064: 1: Success after binutils: 4 commits discards b056ad53a0 137: onsuccess: #2061: 1: Success after binutils: 2 commits discards 4bc0402d6d 136: onsuccess: #2056: 1: Success after binutils: 4 commits discards e6fd857d32 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits discards 389ea81f50 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits discards 4072ed33c8 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits discards baacb519af 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits discards 7bc2c3af6f 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] discards 5a4c16678c 130: onsuccess: #2049: 1: Success after gcc: 9 commits discards 6ebf7792be 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] discards c75ba669fa 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] discards cec3800041 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] discards 60c7adf022 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] discards c69063424a 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits discards eec3299490 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits discards 986c60a91b 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits discards 9d5c7a10cc 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits discards c55f2662e0 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits discards 020530e355 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits discards 87c09d01b7 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits discards 29caa60f81 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits discards 7ea661d7ad 117: onsuccess: #2034: 1: Success after binutils: 2 commits discards 681921196a 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits discards fa3c5da242 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits discards e87f929b7e 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits discards 40f5e01df6 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits discards ef42da44ac 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits discards a8632c9ab7 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits discards 360918ce43 110: onsuccess: #2027: 1: Success after gcc: 5 commits discards 665fe12b1c 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits discards c3d7a3c714 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits discards 84550db676 107: onsuccess: #2024: 1: Success after gcc: 3 commits discards 0f45b4a353 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits discards bc69b265af 105: onsuccess: #2022: 1: Success after gcc: 4 commits discards c5e0106b13 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards 96e6323696 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards 39d076899b 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] discards 51bdeae6ac 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards 89d7bc02f3 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards 4befb6b4f5 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards d35db73e30 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards 22de06faff 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards a2009dd381 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] discards 63cdacfe5a 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] discards ca2ed1da33 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards 6056267f6e 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] discards abf155637e 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards 2a345e23b7 91: onsuccess: 1: Success after gcc: Daily bump. discards 0c5a6ccade 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards 7151c7c78e 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards 9ef55f9aa6 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards 97ca35feff 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards fea3771a7a 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards 8bcadefec8 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards 0cd5458f07 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards 7e02de0e05 83: onsuccess: 1: Success after gcc: 8 commits discards f0b7fa8a6b 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards 7c90ae12c5 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards c8d4aa3405 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards 640a140abb 79: onsuccess: 1: Successful build after gcc: Daily bump. discards b6610990b2 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 99f5c60a91 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards e42c8d63c4 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 21101f856c 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 277334a57e 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards 6482369947 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards ae19f51dc2 72: onsuccess: 1: Successful build after gcc: 2 commits discards 4d53a54cc8 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 7a6305fb73 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards df46791e98 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards bf7bb447fc 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 940f1300ab 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 19e5edad26 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards f9d7163fda 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards c03affcbab 64: onsuccess: 1: Successful build after gcc: 5 commits discards 914abe791a 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards d3f490dccb 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 02098a12ad 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits discards 2cbc968cb0 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards f84ebdcb64 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits discards be1bbbc452 58: onsuccess: 1: Successful build after binutils: 2 commits discards 6e42dfe560 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards 84c21554a4 56: onsuccess: 1: Successful build after gcc: Daily bump. discards 0253d94768 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards c44e912020 54: onsuccess: 1: Successful build after gcc: 7 commits discards 6c3d3e99c8 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 05365518e0 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards a3c81657f8 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 870986b8cf 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 54502f68b2 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards a9146def7a 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards d074365810 47: onsuccess: 1: Successful build after binutils: 2 commits discards 8e40210de2 46: onsuccess: 1: Successful build after gcc: Daily bump. discards 28b328fb51 45: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards ba40490a95 44: onsuccess: 1: Successful build after gcc: 2 commits discards a07ebb8251 43: onsuccess: 1: Successful build after gcc: Daily bump. discards 339e42a4fc 42: onsuccess: 1: Successful build after binutils: Automatic [...] discards 4a1e7e5f91 41: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 138f6a4927 40: onsuccess: 1: Successful build after gcc: 2 commits new 761781fa1a 40: onsuccess: 1: Successful build after gcc: 2 commits new 7f295c2a7b 41: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 20a6cd19f9 42: onsuccess: 1: Successful build after binutils: Automatic [...] new 99cf1a6e04 43: onsuccess: 1: Successful build after gcc: Daily bump. new 8b458fa92e 44: onsuccess: 1: Successful build after gcc: 2 commits new d97588af44 45: onsuccess: 1: Successful build after binutils/gcc: 4 commits new d3e16f371a 46: onsuccess: 1: Successful build after gcc: Daily bump. new a1dfcd8d0b 47: onsuccess: 1: Successful build after binutils: 2 commits new a34ad80a48 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits new c552bc6496 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits new ca10478245 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 877d3a4615 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 9c22e51653 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 2b9e8d8a65 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 5d98cbc195 54: onsuccess: 1: Successful build after gcc: 7 commits new dcc4934c49 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 77696d9faa 56: onsuccess: 1: Successful build after gcc: Daily bump. new 117e5a7950 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits new 066b1883fe 58: onsuccess: 1: Successful build after binutils: 2 commits new ba69f08edb 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits new 726c6eb50b 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits new cadfcc07b7 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits new c4a996524b 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 1e3de92d0a 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits new b5d7e54fa5 64: onsuccess: 1: Successful build after gcc: 5 commits new 84b7302014 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits new bae927af47 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new cb12a8e706 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 4b813c8241 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 0e555d7144 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 83aa45dffb 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new 5f0b2d9355 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 15229671e0 72: onsuccess: 1: Successful build after gcc: 2 commits new dd86c39792 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 04fe329602 74: onsuccess: 1: Successful build after binutils: Automatic [...] new a8fec1e223 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 9794d2e0c9 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 9d9a1f142e 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 2b31fa4c98 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 1f7d7d7d0a 79: onsuccess: 1: Successful build after gcc: Daily bump. new 5140471f43 80: onsuccess: 1: Success after binutils/gcc: 14 commits new e44dcdc5c5 81: onsuccess: 1: Success after binutils/gcc: 27 commits new 3121b1e0c3 82: onsuccess: 1: Success after binutils/gcc: 10 commits new 39f599d0eb 83: onsuccess: 1: Success after gcc: 8 commits new 6ca1c1dc56 84: onsuccess: 1: Success after binutils/gcc: 9 commits new d68ba96a25 85: onsuccess: 1: Success after binutils/gcc: 9 commits new 1d19f08a97 86: onsuccess: 1: Success after binutils/gcc: 13 commits new b9e19f2db0 87: onsuccess: 1: Success after binutils/gcc: 4 commits new 1db1533934 88: onsuccess: 1: Success after binutils/gcc: 16 commits new 5548cf1664 89: onsuccess: 1: Success after binutils/gcc: 9 commits new 7a81fb5ba2 90: onsuccess: 1: Success after binutils/gcc: 6 commits new c84b649cb1 91: onsuccess: 1: Success after gcc: Daily bump. new a3b77c07ba 92: onsuccess: #1965: 1: Success after gcc: 2 commits new fc50a178df 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] new d73e8051f6 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new 97424fb045 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] new 7212c7f92d 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] new df246aa452 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new 855e211175 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new 711f59d3b2 99: onsuccess: #1974: 1: Success after gcc: 14 commits new b03e87a5e1 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new d4eee57fe7 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new ca2dc31b47 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] new b9729c83a1 103: onsuccess: #2020: 1: Success after gcc: 2 commits new d84775b4dd 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new 60043d51f6 105: onsuccess: #2022: 1: Success after gcc: 4 commits new 6620ef5f18 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits new 32fe3b298a 107: onsuccess: #2024: 1: Success after gcc: 3 commits new 905e546f11 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits new c1703d2e46 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits new de56d0b460 110: onsuccess: #2027: 1: Success after gcc: 5 commits new 87fa799d4b 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits new 7c23a74199 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits new b052366c7f 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits new a850ed99a7 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits new 770992f93d 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits new 989661cec4 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits new 2cada22edc 117: onsuccess: #2034: 1: Success after binutils: 2 commits new 306bfcc47e 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits new bc8855d628 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits new 4d9c807436 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits new 01c442c57e 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits new f32dfe8b2d 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits new cfabca040a 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits new 9eef1cb1cb 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits new d350ab6418 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits new f88a2c955c 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] new d5fec62425 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] new 57dc9ed416 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] new 61bff5f7be 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] new 7be279e774 130: onsuccess: #2049: 1: Success after gcc: 9 commits new 8ec9d9b305 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] new 212c505aa5 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits new 2f9bc74e8b 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits new 685f54e1c1 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits new e7b4c26674 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits new 01b7222250 136: onsuccess: #2056: 1: Success after binutils: 4 commits new 989bb76633 137: onsuccess: #2061: 1: Success after binutils: 2 commits new a485a3b356 138: onsuccess: #2064: 1: Success after binutils: 4 commits new 45f508bc07 139: onsuccess: #2067: 1: Success after binutils: 2 commits new d1c9d696f5 140: onsuccess: #2070: 1: Success after binutils: 4 commits new c2b61d0805 141: onsuccess: #2073: 1: Success after binutils: 3 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (51b3175f11) \ 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 1728 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 38944 -> 37668 bytes 04-build_abe-gcc/console.log.xz | Bin 214164 -> 212080 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3816 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2960 -> 2876 bytes 07-check_regression/console.log.xz | Bin 4400 -> 4320 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 6 +- 08-update_baseline/console.log | 52 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 12 +- sumfiles/g++.log.xz | Bin 3572384 -> 3609816 bytes sumfiles/g++.sum | 108 +- sumfiles/gcc.log.xz | Bin 3134616 -> 3116828 bytes sumfiles/gcc.sum | 4744 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1043276 -> 1042656 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2188 -> 2184 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207140 -> 207544 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2548 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 440836 -> 442748 bytes sumfiles/libstdc++.sum | 10 +- 30 files changed, 2513 insertions(+), 2513 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (2ac8ecb992 -> 04cf66f630)

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 2ac8ecb992 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards a385cc84f3 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 4bbf5a4687 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards 64a6a720c6 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards 130cdaea7f 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards 1cd54bc6df 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards e904926c49 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards 2c7d35fe27 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards e6d94f2d0c 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards a013e45345 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards df9ef6ad9d 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards a8c4bc0e15 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 1559488fe4 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 9d17a6597e 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards ea9b908308 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 446011f0b5 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards cc10efc315 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards b60564f54d 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 0ce651bf97 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 4d2d73a0b8 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards 7327df512a 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 095ee15fdb 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards b3eab68e63 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards e5adcfd79a 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards e4a14e9ab6 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards 19e4be3316 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 8282e87b6d 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 19fa63f611 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards 8e4fe512ca 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards d7f63e39e2 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards 3a577d6aa8 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards 5c89102aed 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards fb1de1e94b 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 9f3a39a7ea 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 44a5ce8af0 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards b61b86ed57 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 77b3969a82 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards d0af900cf2 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards 4108e358b0 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards be9003ec57 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 696bf9240a 102: force: #1551: 1: Failure after gcc: 306 commits discards d8ec71bd74 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 1bfd751970 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 2cfe113a07 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 5d070e75bf 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards a6a1d23aa6 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards cbe1b83320 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 92aa2d9b1d 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2c9dcaf28d 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards caf4f1bbf8 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards b2be34ea08 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 442ca635de 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 1a33be4a23 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 03946cb073 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 60686ff505 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards cf18d35f54 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 9205634985 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 5baa1e4c79 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards b3cfb00447 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 0ce0b25708 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 1667a0a935 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards a9ce87ab68 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5bd533e600 80: onsuccess: 7: Successful build after linux: 44 commits discards 971f8f97ef 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 125086c986 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards 56c15c832f 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards eb5331fe5d 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards cead1cf73e 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 421e4edb0f 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards e782ecd815 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c11aa4c106 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c4912b99d8 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 4e2725919e 70: onsuccess: 7: Successful build after gcc: 4 commits discards e19364156f 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d5845659f2 68: onsuccess: 7: Successful build after linux: 6 commits discards 75806c69b1 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards 904eb79f9a 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards b98da2839a 65: onsuccess: 7: Successful build after binutils: 3 commits discards 1ea11422e5 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards e80748b9b5 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards ee0c3f64c7 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards aed9ad92f7 61: onsuccess: 4: Successful build after gcc: 5 commits discards f55753a971 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 02e720c74f 59: force: 7: Successful build after gcc: 3 commits discards 92b430b9dc 58: onsuccess: 7: Successful build after glibc: 2 commits discards 324ce89b8d 57: onsuccess: 7: Successful build after gcc: 7 commits discards ed5d0d1c4d 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards acb203dbac 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6fee5844e3 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards ba22d3315f 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 3de6946c47 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] discards 2103c6afee 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards b8bbd5a62f 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 49dd0b8fd0 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards fb9155c731 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards c8b7fa0a26 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 88a1a32110 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards ca85e8961f 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 38e072e517 44: onsuccess: 7: Successful build after linux: 34 commits discards 21fdfed654 43: onsuccess: 7: Successful build after gcc: 2 commits discards 003ff4e6cf 42: onsuccess: 7: Successful build after baseline build: no [...] new ba4bb46c3e 42: onsuccess: 7: Successful build after baseline build: no [...] new 955479f945 43: onsuccess: 7: Successful build after gcc: 2 commits new 98f3d82a28 44: onsuccess: 7: Successful build after linux: 34 commits new 371747810f 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b815d2f547 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 60d8aaeb07 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 3d10625f40 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 786a16a089 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 6fcb06a5bc 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e07d56432f 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 97a428db00 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new ccbe58c386 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new c376ecb459 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 9a378b5d85 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new bb7ad47d01 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d572d3db2b 57: onsuccess: 7: Successful build after gcc: 7 commits new 46b3b82de4 58: onsuccess: 7: Successful build after glibc: 2 commits new 6a974ec635 59: force: 7: Successful build after gcc: 3 commits new e918e3548e 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 18479aaf38 61: onsuccess: 4: Successful build after gcc: 5 commits new bd9390c256 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 1437da5d6a 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 5e55b2f164 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 72e90f17de 65: onsuccess: 7: Successful build after binutils: 3 commits new d5506bfd66 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 17484cb063 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new c06a83b5d0 68: onsuccess: 7: Successful build after linux: 6 commits new 033b665c55 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6e04898d0c 70: onsuccess: 7: Successful build after gcc: 4 commits new 86588bde81 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new eb53f88481 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 0da412b9d9 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new db9212e553 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new ae293087af 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new d117eda6fe 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 561aa06804 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8dd6fb5a06 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new f9a89750cd 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 43cc483e3b 80: onsuccess: 7: Successful build after linux: 44 commits new a7a7847525 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 27218916af 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 707c2e4a81 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7b423f56ec 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 920198b0e5 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new b6860d56a4 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 753e3ca1bb 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new b252a3027f 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 8b1787ce36 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 3cbf850e5e 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 001122f392 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 46318791ce 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 441189964e 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new c7705e11c9 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new dff69d58da 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 258b6e44ca 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new f301972b8a 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 153f0d569b 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new b30f9386cd 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new ce22105627 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new a1868f1cfd 101: onsuccess: #1547: 7: Success after binutils: 82 commits new bcc05c8e54 102: force: #1551: 1: Failure after gcc: 306 commits new c9b135c2d2 103: onsuccess: #1552: 1: Success after gcc: 5 commits new f7758290ab 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new b82f2774c8 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new a669118997 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new c22e79386e 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new cde6b02889 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new dafab6f28b 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new ef94e36126 110: onsuccess: #1559: 7: Success after gcc: 4 commits new e7d862ec88 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new 0f7bef7f8d 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new eea477c51e 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new fbaac69648 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new cbbefc49d2 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new c8e8792ee2 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 4183af5a47 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new f42976e3f9 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new 3850b68b98 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new b86124e24d 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 232f8a53de 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 8af8ce8fc4 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 7bfd1aec26 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new 907b2901f8 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new df18cf54ce 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 920f6b6462 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 77526a2a77 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new be37d4f2f7 128: onsuccess: #1579: 7: Success after linux: 12 commits new 240fe41463 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new b1691bef6b 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new d2668218c9 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new b8f950296b 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new adda31b975 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new 6a556a6397 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new 03c007e8c0 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new f769cb571c 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new 0d48932481 137: onsuccess: #1588: 7: Success after gcc: 5 commits new eeba06a990 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new 83e2675725 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 76f0244a54 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new 5bd0c89d06 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new e4111fd4df 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new 04cf66f630 143: onsuccess: #1594: 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 (2ac8ecb992) \ 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 1696 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 30364 -> 30176 bytes 05-build_abe-stage1/console.log.xz | Bin 72544 -> 72180 bytes 07-build_abe-linux/console.log.xz | Bin 9236 -> 8708 bytes 08-build_abe-glibc/console.log.xz | Bin 240008 -> 239652 bytes 09-build_abe-stage2/console.log.xz | Bin 203280 -> 202160 bytes 10-build_abe-gdb/console.log.xz | Bin 37736 -> 37564 bytes 11-build_abe-qemu/console.log.xz | Bin 31484 -> 31232 bytes 12-check_regression/console.log.xz | Bin 4168 -> 4456 bytes 13-update_baseline/console.log | 48 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +++++++++++++++--------------- 21 files changed, 54 insertions(+), 54 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022