Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (1baa64ab8 -> c45949056)

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 1baa64ab8 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g3 [...] discards 9aa522721 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 05c8ff49e 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 commits discards 89945737d 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 commits discards 522079d26 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/gd [...] discards 156cd3178 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 4b52754a8 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 7d633031a 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/gd [...] discards db2329393 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 7c7a1379d 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards 18cbfaf32 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 5270eef3e 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/gd [...] discards abd41ddf9 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/gl [...] discards cbf83e353 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/gl [...] discards 3b81b7427 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/gd [...] discards 9d143e07f 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/gd [...] discards 9f364dd12 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 commits discards 7d1e96b25 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qemu [...] discards eb89d0780 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/gl [...] discards 815950363 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 commits discards 69b2ccc31 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: 1 [...] discards 665c6c5d0 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/gd [...] discards ef6dca155 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/gl [...] discards b8a15305d 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/gd [...] discards c9a71aa37 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 3337ea9fe 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 22ff93602 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards aaf00973c 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/gd [...] discards 66272b995 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/gd [...] discards 27158f752 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] discards 10bd7e253 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 3076132a8 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 02ad490f2 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] discards e452f4f56 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 2f7ffd79c 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] discards ddfa27087 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] discards ca940ec39 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards c8997be80 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] discards 0e0c8d038 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] discards d8265c59e 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards f098bb9b7 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] discards ae6f25f06 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] discards d7eef1a6c 95: onsuccess: #1529: 7: Success after baseline build: no new [...] discards d23dae31d 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 6cace17ef 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] discards 7f50a9e92 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 740cb2d04 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 8999b85df 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 48a2362a8 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 3e32d0f18 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 12853b385 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 51a9695a2 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards a0da4c960 85: onsuccess: 7: Success after gcc: 9 commits discards 5a209a88c 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 2f6e4b03c 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards c04abc942 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 046180d29 81: onsuccess: 7: Successful build after gcc: 2 commits discards a15099f04 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards 22b76a633 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards ed7d9bd33 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 9c1decc92 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards eda2b185d 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards af1bb5887 75: onsuccess: 7: Successful build after linux: 44 commits discards 6ecf61a79 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards fa963026b 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 3c2211c6f 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards a23ba17b5 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards 8bb436a39 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards f28cddb4d 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards d423cc229 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 1cd8c7637 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards dd0ee3852 66: onsuccess: 7: Successful build after gcc: 3 commits discards c9a993102 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards f16b9f393 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 24a5e01d8 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards f12bbc155 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 853d2f5cf 61: onsuccess: 4: Successful build after gcc: 15 commits discards 4601b1d39 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards e274dfbfe 59: force: 7: Successful build after gcc: 2 commits discards a625a3ee6 58: onsuccess: 7: Successful build after glibc: 2 commits discards 6de229109 57: onsuccess: 7: Successful build after gcc: 7 commits discards 8a7308a6d 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 152c46350 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 65dabce27 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 61a085c1f 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] discards 6f3baf0a1 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 64f656a8b 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards b069cbef7 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards eb0f37fe9 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards ec39a459a 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards b2e85f64c 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 529fa75d6 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 6cad1d5b7 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 8de1c4103 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards 0f76335c4 43: onsuccess: 7: Successful build after gcc: 2 commits discards c296274d1 42: onsuccess: 7: Successful build after baseline build: no n [...] discards a449c3507 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards a36a5481a 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 310f1ba42 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits discards 16527ec24 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards 75ffcc14f 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new e26e15662 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new a9e6b7b57 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new a5a468522 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits new 5514ac04a 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new a6702a9c0 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new b912656c3 42: onsuccess: 7: Successful build after baseline build: no n [...] new 342a641a1 43: onsuccess: 7: Successful build after gcc: 2 commits new d87ca925f 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new cd5a34451 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 85da7c179 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new e6d66ee9e 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 19ab58c7c 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 051b7a9c4 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new a1d72a6b2 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 4fbbf0848 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 6cd12ed58 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 3823be3ee 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] new b19a9701c 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new b284da29b 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 93b728ac6 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 4bbf9ca5f 57: onsuccess: 7: Successful build after gcc: 7 commits new 7508c47c6 58: onsuccess: 7: Successful build after glibc: 2 commits new ef4702047 59: force: 7: Successful build after gcc: 2 commits new 2451c88ff 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new 1cd09c863 61: onsuccess: 4: Successful build after gcc: 15 commits new 10c4e9ca5 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 509eea76d 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new cb73212b0 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 92cef8b72 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new fa597fcef 66: onsuccess: 7: Successful build after gcc: 3 commits new 158648f9b 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new f8eb6e4a8 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 043e22025 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new da27b8ca5 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 721ff28bf 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new 7ec3e4142 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 2c35b691d 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 8107993ab 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new ac13c2e9b 75: onsuccess: 7: Successful build after linux: 44 commits new 48d923195 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 607d5f97c 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new ed7fe2bcf 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 5dba33e27 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new e99618380 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new db57ca789 81: onsuccess: 7: Successful build after gcc: 2 commits new 5dee91d98 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new ec7d14d64 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 45b78d3ad 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new aea958aef 85: onsuccess: 7: Success after gcc: 9 commits new 741cee099 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new bc5b1a48f 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new ad48414e0 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new ff9c75b6f 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 7d51c7512 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 427c4ea5f 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 8b2fc2220 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new dcb7df022 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] new e2349dfe0 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 9a3230d26 95: onsuccess: #1529: 7: Success after baseline build: no new [...] new 615a89df0 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] new a167d0d6d 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] new 0e559313d 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 32f29641b 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] new 5331a3652 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] new 774d77686 101: onsuccess: #1609: 7: Success after binutils: 78 commits new ac7a34398 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] new ff01790ea 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] new 1ea8c9c16 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 66665a4d0 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] new b4b9029c4 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 2672be9d2 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 60c07eb9b 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] new baea5c72c 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/gd [...] new 002bc1ed9 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/gd [...] new a45b5776a 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 344d7a1a9 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 5b7df1f48 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 66b7c06eb 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/gd [...] new edf0363cf 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/gl [...] new b97c31d63 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/gd [...] new cd618d766 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: 1 [...] new 65c5b54ef 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 commits new 441671e37 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/gl [...] new 31a6ec683 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qemu [...] new dae79fb01 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 commits new dcb38467b 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/gd [...] new 9a25c7d0b 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/gd [...] new ea668978c 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/gl [...] new 4efd31c94 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/gl [...] new 00c6bccc3 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/gd [...] new 7887c69c3 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 46af18f98 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 4bee4bc0d 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 579290342 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/gd [...] new a39281603 131: onsuccess: #1644: 7: Success after gcc: 10 commits new daec2460c 132: onsuccess: #1645: 7: Success after linux: 23 commits new c5f0ac1f4 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/gd [...] new 6c3b88cc2 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 commits new 14b064568 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 commits new 17b11341b 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 73a37b231 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g3 [...] new c45949056 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g1 [...] 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 (1baa64ab8) \ 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 1656 -> 1656 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 30528 -> 31040 bytes 05-build_abe-stage1/console.log.xz | Bin 91152 -> 61756 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 0 bytes 07-build_abe-linux/console.log.xz | Bin 8456 -> 0 bytes 08-build_abe-glibc/console.log.xz | Bin 234080 -> 0 bytes 09-build_abe-stage2/console.log.xz | Bin 223872 -> 0 bytes 10-build_abe-gdb/console.log.xz | Bin 37676 -> 0 bytes 11-build_abe-qemu/console.log.xz | Bin 31372 -> 0 bytes 12-check_regression/console.log.xz | Bin 2964 -> 3872 bytes 12-check_regression/jira-body.txt | 2 +- 12-check_regression/mail-body.txt | 22 ++- 12-check_regression/mail-subject.txt | 2 +- 12-check_regression/results.regressions | 8 + 12-check_regression/trigger-bisect | 2 + 12-check_regression/trigger-notify | 0 13-update_baseline/console.log | 70 ++++---- dashboard/dashboard-generate.sh | 2 +- dashboard/squad/score/results-functional.json | 1 - git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 219 ++++++++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 22 ++- mail/mail-subject.txt | 2 +- manifest.sh | 27 +--- results | 20 ++- 31 files changed, 314 insertions(+), 98 deletions(-) delete mode 100644 06-clean_sysroot/console.log.xz delete mode 100644 07-build_abe-linux/console.log.xz delete mode 100644 08-build_abe-glibc/console.log.xz delete mode 100644 09-build_abe-stage2/console.log.xz delete mode 100644 10-build_abe-gdb/console.log.xz delete mode 100644 11-build_abe-qemu/console.log.xz create mode 100644 12-check_regression/results.regressions create mode 100644 12-check_regression/trigger-bisect create mode 100644 12-check_regression/trigger-notify delete mode 100644 dashboard/squad/score/results-functional.json 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 (5cc7f3b -> 008afde)

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 5cc7f3b Add entry e07ead85a368173a56e96a21d6841aa497ad80f8 from https [...] new 008afde 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: .../tcwg_gnu_cross_build/master-arm/build_url | 1 + .../master-arm}/last_good | 0 .../master-arm}/summary.txt | 0 .../{tcwg_gnu_native_build => tcwg_gnu_cross_build}/status.txt | 4 ++-- 4 files changed, 3 insertions(+), 2 deletions(-) create mode 100644 gcc/sha1/1b74b5cb4e9d7191f298245063a8f9c3a1bbeff4/tcwg_gnu_cros [...] copy gcc/sha1/1b74b5cb4e9d7191f298245063a8f9c3a1bbeff4/{tcwg_gcc_bootstrap/master- [...] copy gcc/sha1/1b74b5cb4e9d7191f298245063a8f9c3a1bbeff4/{tcwg_gcc_bootstrap/master- [...] copy gcc/sha1/1b74b5cb4e9d7191f298245063a8f9c3a1bbeff4/{tcwg_gnu_native_build => t [...] -- 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-release-arm-norov-allmodconfig updated (c0e62aa1ea -> c4c393c0bd)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-norov-allmodconfig in repository toolchain/ci/base-artifacts. from c0e62aa1ea 14: onsuccess: #58: 23023: Success after binutils/llvm/qemu: [...] new c4c393c0bd 15: onsuccess: #60: 23023: Success after binutils/llvm/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1680 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30268 -> 30188 bytes 04-build_kernel_llvm/console.log.xz | Bin 65164 -> 64392 bytes 05-build_abe-qemu/console.log.xz | Bin 31244 -> 32000 bytes 06-build_linux/console.log.xz | Bin 4856 -> 5292 bytes 08-check_regression/console.log.xz | Bin 2844 -> 4380 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 31 ++++++++++++++++--------------- 16 files changed, 24 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[binutils-gdb] branch master updated (64dc622ffb2 -> e122316b7ce)

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 64dc622ffb2 Automatic date update in version.in new e122316b7ce PR29617, ld segfaults when bfd_close fails 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: ld/ldmain.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_llvm_tx1/llvm-master-aarch64-spec2k6-O3_LTO updated (b0ad936212 -> baceab3cd9)

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_bmk_llvm_tx1/llvm-master-aarch64-spec2k6-O3_LTO in repository toolchain/ci/base-artifacts. from b0ad936212 22: onsuccess: #469: 1: [TCWG CI] No change after binutils/g [...] new baceab3cd9 23: onsuccess: #470: 1: [TCWG CI] 456.hmmer built and run OK [...] 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 1772 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 31148 -> 30984 bytes 04-build_abe-stage1/console.log.xz | Bin 74048 -> 74472 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 7840 -> 8564 bytes 07-build_abe-glibc/console.log.xz | Bin 241140 -> 241752 bytes 08-build_abe-stage2/console.log.xz | Bin 179808 -> 182480 bytes 09-build_llvm-true/console.log.xz | Bin 62684 -> 63476 bytes 10-benchmark/benchmark-build.log | 116 +- 10-benchmark/benchmark.log | 114 +- 10-benchmark/console.log.xz | Bin 4088 -> 4012 bytes 11-check_regression/console.log.xz | Bin 7360 -> 7716 bytes 11-check_regression/csv-results-0/perf.csv | 72 +- 11-check_regression/csv-results-0/results.csv | 157256 +++++++------ 11-check_regression/csv-results-0/size.csv | 170019 +++++++------- 11-check_regression/csv-results-0/vect.csv | 19457 +- 11-check_regression/csv-results-1/perf.csv | 86 +- 11-check_regression/csv-results-1/results.csv | 181839 ++++++++------ 11-check_regression/csv-results-1/size.csv | 221203 ++++++++++-------- 11-check_regression/csv-results-1/vect.csv | 19817 +- 11-check_regression/exe.improvement | 4 + 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/jira-body.txt | 6 + 11-check_regression/mail-body.txt | 6 + 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results-brief.csv | 36 +- 11-check_regression/results-compare.csv | 8 +- 11-check_regression/results-full.csv | 95 +- 11-check_regression/results-internal.csv | 49 +- 11-check_regression/results.csv | 49 +- 11-check_regression/results.log | 1030 +- dashboard/dashboard-generate.sh | 2 +- .../squad/400.perlbench/results-metadata.json | 16 +- dashboard/squad/400.perlbench/results-metrics.json | 2 +- dashboard/squad/401.bzip2/results-functional.json | 4 +- dashboard/squad/401.bzip2/results-metadata.json | 16 +- dashboard/squad/401.bzip2/results-metrics.json | 3 + dashboard/squad/403.gcc/results-metadata.json | 16 +- dashboard/squad/403.gcc/results-metrics.json | 2 +- dashboard/squad/429.mcf/results-metadata.json | 16 +- dashboard/squad/429.mcf/results-metrics.json | 2 +- dashboard/squad/444.namd/results-functional.json | 4 +- dashboard/squad/444.namd/results-metadata.json | 16 +- dashboard/squad/444.namd/results-metrics.json | 3 + dashboard/squad/445.gobmk/results-metadata.json | 16 +- dashboard/squad/445.gobmk/results-metrics.json | 2 +- dashboard/squad/447.dealII/results-metadata.json | 16 +- dashboard/squad/447.dealII/results-metrics.json | 2 +- dashboard/squad/450.soplex/results-metadata.json | 16 +- dashboard/squad/450.soplex/results-metrics.json | 2 +- dashboard/squad/453.povray/results-functional.json | 4 +- dashboard/squad/453.povray/results-metadata.json | 16 +- dashboard/squad/453.povray/results-metrics.json | 3 + dashboard/squad/456.hmmer/results-functional.json | 4 +- dashboard/squad/456.hmmer/results-metadata.json | 16 +- dashboard/squad/456.hmmer/results-metrics.json | 3 + dashboard/squad/458.sjeng/results-metadata.json | 16 +- .../squad/462.libquantum/results-metadata.json | 16 +- .../squad/462.libquantum/results-metrics.json | 2 +- dashboard/squad/470.lbm/results-metadata.json | 16 +- dashboard/squad/470.lbm/results-metrics.json | 2 +- dashboard/squad/471.omnetpp/results-metadata.json | 16 +- dashboard/squad/471.omnetpp/results-metrics.json | 2 +- dashboard/squad/473.astar/results-metadata.json | 16 +- dashboard/squad/473.astar/results-metrics.json | 2 +- dashboard/squad/482.sphinx3/results-metadata.json | 16 +- dashboard/squad/482.sphinx3/results-metrics.json | 2 +- .../squad/483.xalancbmk/results-metadata.json | 16 +- dashboard/squad/483.xalancbmk/results-metrics.json | 2 +- dashboard/squad/Mean/results-metadata.json | 16 +- dashboard/squad/Mean/results-metrics.json | 6 +- dashboard/squad/dashboard-push-squad.sh | 74 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 57 +- mail/mail-body.txt | 57 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 402592 -> 402564 bytes save-temps/401.bzip2.tar.xz | Bin 0 -> 44460 bytes save-temps/403.gcc.tar.xz | Bin 1200640 -> 1200680 bytes save-temps/429.mcf.tar.xz | Bin 22800 -> 22828 bytes save-temps/444.namd.tar.xz | Bin 0 -> 46792 bytes save-temps/445.gobmk.tar.xz | Bin 613980 -> 614660 bytes save-temps/447.dealII.tar.xz | Bin 943852 -> 933956 bytes save-temps/450.soplex.tar.xz | Bin 203948 -> 204504 bytes save-temps/453.povray.tar.xz | Bin 0 -> 466644 bytes save-temps/456.hmmer.tar.xz | Bin 0 -> 125064 bytes save-temps/458.sjeng.tar.xz | Bin 52664 -> 52628 bytes save-temps/462.libquantum.tar.xz | Bin 24216 -> 24164 bytes save-temps/470.lbm.tar.xz | Bin 16032 -> 16044 bytes save-temps/471.omnetpp.tar.xz | Bin 380932 -> 375728 bytes save-temps/473.astar.tar.xz | Bin 43828 -> 43860 bytes save-temps/482.sphinx3.tar.xz | Bin 95692 -> 95868 bytes save-temps/483.xalancbmk.tar.xz | Bin 3334612 -> 3335784 bytes 99 files changed, 425255 insertions(+), 346595 deletions(-) create mode 100644 11-check_regression/exe.improvement create mode 100644 save-temps/401.bzip2.tar.xz create mode 100644 save-temps/444.namd.tar.xz create mode 100644 save-temps/453.povray.tar.xz create mode 100644 save-temps/456.hmmer.tar.xz -- 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-aarch64-next-allmodconfig updated (a3b5ad0206 -> 16d5b29068)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-allmodconfig in repository toolchain/ci/base-artifacts. from a3b5ad0206 19: onsuccess: #543: 23421: Success after binutils/llvm/linu [...] new 16d5b29068 20: onsuccess: #546: all: Success after linux: 1668 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 1704 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 31116 -> 31148 bytes 04-build_kernel_llvm/console.log.xz | Bin 63876 -> 65720 bytes 05-build_abe-qemu/console.log.xz | Bin 32312 -> 31720 bytes 06-build_linux/console.log.xz | Bin 4180 -> 3000 bytes 07-boot_linux/console.log.xz | Bin 0 -> 508 bytes 08-check_regression/console.log.xz | Bin 3524 -> 3100 bytes 08-check_regression/mail-body.txt | 6 ++++-- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 8 +++++--- mail/mail-subject.txt | 2 +- manifest.sh | 24 +++++++++++------------- results | 4 +++- 16 files changed, 27 insertions(+), 23 deletions(-) create mode 100644 07-boot_linux/console.log.xz -- 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 (e5ed23320e -> 1baa64ab81)

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 e5ed23320e 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 46bf6f4bca 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards 44a77d10e4 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 2832ac864b 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards 90ac4315b9 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 4c36219ba9 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 2011bcabf9 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards 34e92c6048 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 48423baabc 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards 0cf2510a5e 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 3c5590174b 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards df9a8786ab 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards e9da771096 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 09f75547fe 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards 2875152957 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards ab9c046d52 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 41d968f8d3 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 7037bb3360 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards cf9f671806 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 521048dc80 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards f253ac3906 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards b78ce432f9 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 5b2ca1259f 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 1b1f0bc61f 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards a8927ac4f5 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 33df6824cf 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 6df1789ade 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards 07e3047665 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 131a656f6c 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards d4af839ec0 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 5efbc82dd4 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 24540d0c05 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards aa35e7b516 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 9f13b7f128 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards f93cab7dca 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 730f83fcf7 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 1487844d68 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 9fa0133786 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards bc4b7ffec5 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards c14e7aa540 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards 0ac7b2b96d 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 00148f5ca0 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards 6b0da940cc 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards e3fb9f8c99 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 0a82724fb8 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 4e2b7fe0ba 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 0562c502fe 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 784e1c61d2 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards d7eae72d93 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 2d2acb6594 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 63a80aadb5 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards d16beee65b 85: onsuccess: 7: Success after gcc: 9 commits discards 8b9ba0aa0c 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 457ff43175 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards fb235b85b8 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 94e0cf2e79 81: onsuccess: 7: Successful build after gcc: 2 commits discards f634fdcb03 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards af0143ef46 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 9100a3e74d 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 8f0cd582a2 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 5029c7078f 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c182a3c112 75: onsuccess: 7: Successful build after linux: 44 commits discards 83b8e80b14 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards cfdfa0246d 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f65ba37155 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards ed54cadd47 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards f8d748329d 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards c9d236980a 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 39d8f28dcd 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6deb56e8f2 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards f97b6fcd17 66: onsuccess: 7: Successful build after gcc: 3 commits discards 7124383fda 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 095a4ba8c6 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 44e5687802 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards f6c0c977cb 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 4712c3c818 61: onsuccess: 4: Successful build after gcc: 15 commits discards 048b832124 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 26fc8209fb 59: force: 7: Successful build after gcc: 2 commits discards cfd7fcca9b 58: onsuccess: 7: Successful build after glibc: 2 commits discards b5f4b37e83 57: onsuccess: 7: Successful build after gcc: 7 commits discards cdb34ba457 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 34eb5d63dc 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 1244724b1d 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards ea56145cbc 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 86aac34ded 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 4fce2ba8c6 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 4858562489 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6ae8ec44a6 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 040306d9c8 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards d39caf35df 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3639615307 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards a3f432cadb 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 09876b5ea6 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards 4e56256d2c 43: onsuccess: 7: Successful build after gcc: 2 commits discards 9f7267628c 42: onsuccess: 7: Successful build after baseline build: no [...] discards 88d1ced87b 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e5600a2c0b 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 8e9619090b 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] discards f3e2aff676 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards f9114f8452 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 17866a8165 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b5b1cebc04 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 75ffcc14fb 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 16527ec245 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new 310f1ba424 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] new a36a5481a7 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a449c35072 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c296274d1f 42: onsuccess: 7: Successful build after baseline build: no [...] new 0f76335c41 43: onsuccess: 7: Successful build after gcc: 2 commits new 8de1c41036 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new 6cad1d5b73 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 529fa75d66 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new b2e85f64cd 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ec39a459ae 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new eb0f37fe9f 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new b069cbef70 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 64f656a8ba 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 6f3baf0a10 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 61a085c1f7 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 65dabce277 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 152c46350b 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8a7308a6d1 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6de229109b 57: onsuccess: 7: Successful build after gcc: 7 commits new a625a3ee6d 58: onsuccess: 7: Successful build after glibc: 2 commits new e274dfbfe7 59: force: 7: Successful build after gcc: 2 commits new 4601b1d39d 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 853d2f5cfd 61: onsuccess: 4: Successful build after gcc: 15 commits new f12bbc1551 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 24a5e01d8e 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new f16b9f393b 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c9a993102e 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new dd0ee38529 66: onsuccess: 7: Successful build after gcc: 3 commits new 1cd8c7637b 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new d423cc2295 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f28cddb4df 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 8bb436a39a 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new a23ba17b5d 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 3c2211c6f2 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new fa963026ba 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6ecf61a794 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new af1bb5887a 75: onsuccess: 7: Successful build after linux: 44 commits new eda2b185dc 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 9c1decc928 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new ed7d9bd331 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 22b76a6338 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new a15099f04c 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 046180d296 81: onsuccess: 7: Successful build after gcc: 2 commits new c04abc942b 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 2f6e4b03c4 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 5a209a88cc 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new a0da4c9604 85: onsuccess: 7: Success after gcc: 9 commits new 51a9695a21 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 12853b3852 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 3e32d0f188 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 48a2362a87 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 8999b85df7 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 740cb2d042 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 7f50a9e92b 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 6cace17ef8 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new d23dae31d8 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new d7eef1a6cc 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new ae6f25f060 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new f098bb9b75 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new d8265c59e0 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 0e0c8d038e 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new c8997be80c 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new ca940ec398 101: onsuccess: #1609: 7: Success after binutils: 78 commits new ddfa27087d 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 2f7ffd79c9 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new e452f4f566 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 02ad490f21 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 3076132a83 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 10bd7e2535 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 27158f752a 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new 66272b9957 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new aaf00973c8 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new 22ff93602a 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 3337ea9fe9 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new c9a71aa375 113: onsuccess: #1624: 7: Success after gcc: 6 commits new b8a15305d9 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new ef6dca1558 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 665c6c5d0f 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 69b2ccc311 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 8159503631 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new eb89d07806 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 7d1e96b250 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 9f364dd128 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new 9d143e07fd 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 3b81b74276 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new cbf83e3537 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new abd41ddf91 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new 5270eef3ec 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new 18cbfaf32c 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 7c7a1379d9 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new db23293931 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 7d633031a3 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 4b52754a83 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 156cd31782 132: onsuccess: #1645: 7: Success after linux: 23 commits new 522079d267 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new 89945737d6 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new 05c8ff49e6 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new 9aa5227212 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 1baa64ab81 137: force: #1652: 7: Success after basepoints/gcc-13-2870-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 (e5ed23320e) \ 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 1692 -> 1656 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2748 bytes 04-build_abe-binutils/console.log.xz | Bin 30324 -> 30528 bytes 05-build_abe-stage1/console.log.xz | Bin 91032 -> 91152 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8376 -> 8456 bytes 08-build_abe-glibc/console.log.xz | Bin 235640 -> 234080 bytes 09-build_abe-stage2/console.log.xz | Bin 224104 -> 223872 bytes 10-build_abe-gdb/console.log.xz | Bin 37496 -> 37676 bytes 11-build_abe-qemu/console.log.xz | Bin 31672 -> 31372 bytes 12-check_regression/console.log.xz | Bin 3056 -> 2964 bytes 13-update_baseline/console.log | 72 +++++++++++++++++------------------ 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 | 24 ++++++------ 18 files changed, 53 insertions(+), 53 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-next-allmodconfig updated (b3282a292e -> 064812760e)

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-next-allmodconfig in repository toolchain/ci/base-artifacts. from b3282a292e 20: force: #485: 36: Failure after llvmorg-16-init-5673-ge07 [...] new 064812760e 21: onsuccess: #486: 36: Success after llvm: 12 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 1636 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 29860 -> 30340 bytes 04-build_kernel_llvm/console.log.xz | Bin 62836 -> 62280 bytes 05-build_abe-qemu/console.log.xz | Bin 30808 -> 30288 bytes 06-build_linux/console.log.xz | Bin 4564 -> 4552 bytes 08-check_regression/console.log.xz | Bin 3736 -> 2996 bytes 08-check_regression/jira-body.txt | 2 +- 08-check_regression/mail-body.txt | 18 +- 08-check_regression/mail-subject.txt | 2 +- 08-check_regression/results.regressions | 7 - 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 | 440 -------------------------------- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 18 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 7 - 26 files changed, 32 insertions(+), 497 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

[gcc] branch releases/gcc-12 updated (be18783dea5 -> 7cb8784fbd3)

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 be18783dea5 Daily bump. new 7cb8784fbd3 Daily bump. 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/DATESTAMP | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[gcc] branch releases/gcc-11 updated (50592ed4703 -> db6c03c11a2)

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-11 in repository gcc. from 50592ed4703 Fortran: error recovery on invalid ARRAY argument to FINDLO [...] new db6c03c11a2 Daily bump. 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/DATESTAMP | 2 +- gcc/fortran/ChangeLog | 9 +++++++++ gcc/testsuite/ChangeLog | 8 ++++++++ 3 files changed, 18 insertions(+), 1 deletion(-) -- 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