Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (a90fb1877 -> 5c5b9a7e7)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards a90fb1877 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 1df385395 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards d42aaa21e 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards e42b64da9 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/gd [...] discards 714b737ee 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/gl [...] discards bac8880be 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/gl [...] discards 7ab714bc8 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/gd [...] discards 2ac1e477d 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/gd [...] discards f4225ad14 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 7d67a3f8a 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...] discards 20c7a3bca 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] discards bde1e6939 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits discards 37c3e6cc3 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] discards d3a1b2912 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] discards 2dc19ae73 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] discards a965c6d84 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] discards 3eb4bc22f 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 774d23ef3 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 064c7591f 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 267b79e9f 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] discards 942597a72 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] discards 0439292ba 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] discards 7de5dd537 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 75509b76c 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards ad9e94997 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards 9caf85c6e 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 6fdd4946c 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards 186ff70d5 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards b9ba0e385 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards 63f0213ba 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 03fa9a16a 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 69581a6fe 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards 8628ab628 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards 7338df7b1 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards edaf23198 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards 988b3190f 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 1d82dc939 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards fef7e7365 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards d15dc82ff 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 075d8c1c5 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 777c6890f 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 27eb4f5b6 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards dbc4b6900 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards a1cd43b46 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 0712eab38 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 987534954 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 04aef70d0 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards e2d0ea790 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards a6d1e7edc 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards ecc5acea9 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2dd29c08c 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards 955aef7c6 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d6a45135d 74: onsuccess: 1: Successful build after linux: 44 commits discards 622c40e62 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 2f90dcf0a 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2bb1b4e14 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards 867e8e3c3 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards d40b15909 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 36ec396a1 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a1c25317d 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards eebfffd0a 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 1755cc384 65: onsuccess: 1: Successful build after gcc: 4 commits discards ca1fd292a 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9a9b6455b 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 45d145c60 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards e0a6cda77 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 52171604c 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 83d6aac58 59: onsuccess: 1: Successful build after glibc: 2 commits discards 8533b96b6 58: onsuccess: 1: Successful build after binutils: 2 commits discards b7bdf61b2 57: onsuccess: 1: Successful build after gcc: 7 commits discards 8dc5163c7 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 40fba5fac 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2f4343bff 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 53e410e66 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 33ac97bc8 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 350660f24 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 197925b82 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ffbf2b3bb 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards e9b96e439 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 9c4bca773 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 662e91716 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards a637ce288 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 32e68d8aa 44: onsuccess: 1: Successful build after linux: 34 commits discards 8f97eb5bc 43: onsuccess: 1: Successful build after gcc: 2 commits discards 619af5518 42: onsuccess: 1: Successful build after baseline build: no n [...] discards 40a83d8f5 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards fad7898ad 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 4a5b5c3ff 39: onsuccess: 1: Successful build after gcc: 2 commits discards 5eaadde2a 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 046843dc5 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards bb5bc96eb 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9fc2afbc1 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards a959d826c 34: onsuccess: 1: Successful build after gcc: 3 commits discards 1b7ed1fcc 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e1e2766cf 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 2daf71987 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 32e1b956d 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards c79bafff1 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9ab7051d7 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 56989ea74 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards baf4a3c8a 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 656e65197 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e5aa90f98 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new dd9952277 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 7fede6098 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7a3a218ce 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 55d3c0d98 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 418c3c035 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new b7b05df82 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5615129c0 34: onsuccess: 1: Successful build after gcc: 3 commits new d43d1e4ff 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 9f8997930 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d91c3b69c 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 218d095ed 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d1a4c8185 39: onsuccess: 1: Successful build after gcc: 2 commits new a22154a8e 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2bacfb96d 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 9b0730539 42: onsuccess: 1: Successful build after baseline build: no n [...] new 5c46061b2 43: onsuccess: 1: Successful build after gcc: 2 commits new 457db79a2 44: onsuccess: 1: Successful build after linux: 34 commits new 993b830bc 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7906dd60c 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 7f3d6a68b 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cea172dc8 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new dcc47842d 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 24b50b4d1 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a61e31e27 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new df09c041c 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 43422bfd2 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new 24214537d 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new fbbce4d01 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 866067361 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 9731bdef7 57: onsuccess: 1: Successful build after gcc: 7 commits new 60f697bed 58: onsuccess: 1: Successful build after binutils: 2 commits new 43cfa8242 59: onsuccess: 1: Successful build after glibc: 2 commits new cb7b9266b 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 6a91fc17d 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 30839728a 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new e76e2c0c0 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b7efbee6a 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 6f3479732 65: onsuccess: 1: Successful build after gcc: 4 commits new 78ad44b0e 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 43047e947 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 58909e792 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 43fce54d1 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new d8b7b0232 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new 10bbbec0d 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new a2e46312c 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 9eb76997d 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new fd3ea558d 74: onsuccess: 1: Successful build after linux: 44 commits new edd79fbca 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new dec5c755a 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new fe0d992c6 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e1219dd8b 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 10e75f8c8 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 8c53a1aea 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new 477c92f57 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 2d7e46625 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new da69525f3 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 73686f9fe 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 1ffa07e02 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new b9434aa1c 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 2412d28ba 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 8e1b0a0a9 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new c22f72dec 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 7f03420af 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 03b59f733 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 2712aff8b 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new 5c198ccb1 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 454e4b939 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new 493bded24 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new 646799c67 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 32ce0067a 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new 3c7ef8241 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new 07fa6f853 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new 4b02043a1 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new 65c67f971 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 0750ab61a 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new 2b35d63f9 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new faceea8a2 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 3732f364e 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] new ac4b6456b 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] new 696ca3211 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] new 8c392da52 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new ed5116ad8 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 78286363e 110: onsuccess: #1703: 1: Success after gcc: 6 commits new dcab2f2f4 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] new 8606484cf 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] new 28e917751 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] new 069677c39 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] new 633890d79 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits new ff4826d89 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] new 1dea96696 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...] new c8706f740 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 3c7dc1573 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/gd [...] new 24613f0af 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/gd [...] new 84a65d35d 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/gl [...] new a022787d1 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/gl [...] new e86520955 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/gd [...] new 5e4c89121 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 249992a72 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 7ca1a7ea9 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 5c5b9a7e7 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 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 (a90fb1877) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1688 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30664 -> 29940 bytes 04-build_abe-stage1/console.log.xz | Bin 91336 -> 90376 bytes 06-build_abe-linux/console.log.xz | Bin 8740 -> 8764 bytes 07-build_abe-glibc/console.log.xz | Bin 234212 -> 233720 bytes 08-build_abe-stage2/console.log.xz | Bin 224532 -> 223256 bytes 09-build_abe-gdb/console.log.xz | Bin 37576 -> 37180 bytes 10-build_abe-qemu/console.log.xz | Bin 30968 -> 31016 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2904 -> 2440 bytes 13-check_regression/console.log.xz | Bin 5852 -> 5300 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 25 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 26 - sumfiles/g++.log.xz | Bin 2661552 -> 2683832 bytes sumfiles/g++.sum | 6 +- sumfiles/gcc.log.xz | Bin 2220888 -> 2198808 bytes sumfiles/gcc.sum | 2518 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 878688 -> 877232 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201144 -> 201104 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2676 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 421208 -> 423708 bytes sumfiles/libstdc++.sum | 2 +- 42 files changed, 1382 insertions(+), 1463 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions -- 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/gnu-master-aarch64-mainline-defconfig updated (63ef3c5b4 -> a6c5ec81f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-mainline-defconfig in repository toolchain/ci/base-artifacts. from 63ef3c5b4 14: onsuccess: #487: boot: Success after binutils/gcc/linux/q [...] new a6c5ec81f 15: onsuccess: #488: boot: Success after binutils/gcc/linux/q [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1708 -> 1908 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30288 -> 30116 bytes 04-build_abe-stage1/console.log.xz | Bin 72328 -> 72196 bytes 05-build_abe-qemu/console.log.xz | Bin 31316 -> 31692 bytes 06-build_linux/console.log.xz | Bin 5232 -> 5236 bytes 07-boot_linux/console.log.xz | Bin 6244 -> 6248 bytes 08-check_regression/console.log.xz | Bin 3300 -> 4392 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 31 ++++++++++++++++--------------- 17 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

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_O1 updated (d1be05a3c -> 01a46778d)

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_O1 in repository toolchain/ci/base-artifacts. from d1be05a3c 44: onsuccess: #433: 2: Success after binutils/gcc: 99 commits new 01a46778d 45: onsuccess: #434: 2: Success after binutils/gcc: 9 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 1860 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 37688 -> 38260 bytes 05-build_abe-bootstrap_O1/console.log.xz | Bin 270760 -> 270956 bytes 06-check_regression/console.log.xz | Bin 3076 -> 2964 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 12 files changed, 15 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/release-aarch64 updated (7eeb8ba37 -> 5cd60a03a)

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_native_build/release-aarch64 in repository toolchain/ci/base-artifacts. from 7eeb8ba37 18: onsuccess: #127: 6: Success after binutils/gcc/linux/glib [...] new 5cd60a03a 19: onsuccess: #128: 6: Success after binutils/gcc/linux/gdb: [...] 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 1696 -> 1852 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 38572 -> 37920 bytes 05-build_abe-gcc/console.log.xz | Bin 207116 -> 209100 bytes 06-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 07-build_abe-linux/console.log.xz | Bin 8540 -> 8608 bytes 08-build_abe-glibc/console.log.xz | Bin 240108 -> 239168 bytes 09-build_abe-gdb/console.log.xz | Bin 36948 -> 37288 bytes 10-check_regression/console.log.xz | Bin 3268 -> 3872 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 33 +++++++++++++++++---------------- 18 files changed, 25 insertions(+), 24 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_bmk_gnu_tx1/gnu-master-aarch64-spec2k6-O3 updated (5f055310c -> 7762ce43d)

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_gnu_tx1/gnu-master-aarch64-spec2k6-O3 in repository toolchain/ci/base-artifacts. from 5f055310c 0: init: #441: 1: [TCWG CI] No change after baseline build: n [...] new 7762ce43d 1: onsuccess: #445: 1: [TCWG CI] No change after glibc: 564 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 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 31048 -> 31972 bytes 04-build_abe-stage1/console.log.xz | Bin 72344 -> 74432 bytes 06-build_abe-linux/console.log.xz | Bin 9216 -> 9304 bytes 07-build_abe-glibc/console.log.xz | Bin 236484 -> 241780 bytes 08-build_abe-stage2/console.log.xz | Bin 174740 -> 179636 bytes 09-benchmark/benchmark-build.log | 106 +- 09-benchmark/benchmark.log | 104 +- 09-benchmark/console.log.xz | Bin 3756 -> 3752 bytes 10-check_regression/console.log.xz | Bin 13668 -> 15244 bytes 10-check_regression/csv-results-0/md5sum.csv | 2692 +- 10-check_regression/csv-results-0/results.csv | 34964 +- 10-check_regression/csv-results-0/size.csv | 499834 ++++++++--------- 10-check_regression/csv-results-0/vect.csv | 6376 +- 10-check_regression/csv-results-1/md5sum.csv | 2787 +- 10-check_regression/csv-results-1/perf.csv | 3313 +- 10-check_regression/csv-results-1/results.csv | 60883 ++- 10-check_regression/csv-results-1/size.csv | 510483 +++++++++--------- 10-check_regression/csv-results-1/vect.csv | 6304 +- 10-check_regression/results-brief.csv | 60 +- 10-check_regression/results-compare.csv | 9 +- 10-check_regression/results-full.csv | 3136 +- 10-check_regression/results-internal.csv | 255 +- 10-check_regression/results.csv | 255 +- 10-check_regression/results.log | 1220 +- 11-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- .../squad/400.perlbench/results-metadata.json | 10 +- dashboard/squad/400.perlbench/results-metrics.json | 4 +- dashboard/squad/401.bzip2/results-metadata.json | 10 +- dashboard/squad/401.bzip2/results-metrics.json | 2 +- dashboard/squad/403.gcc/results-metadata.json | 10 +- dashboard/squad/403.gcc/results-metrics.json | 2 +- dashboard/squad/410.bwaves/results-metadata.json | 10 +- dashboard/squad/410.bwaves/results-metrics.json | 2 +- dashboard/squad/416.gamess/results-metadata.json | 10 +- dashboard/squad/416.gamess/results-metrics.json | 2 +- dashboard/squad/429.mcf/results-metadata.json | 10 +- dashboard/squad/429.mcf/results-metrics.json | 2 +- dashboard/squad/433.milc/results-metadata.json | 10 +- dashboard/squad/433.milc/results-metrics.json | 2 +- dashboard/squad/434.zeusmp/results-metadata.json | 10 +- dashboard/squad/434.zeusmp/results-metrics.json | 2 +- dashboard/squad/435.gromacs/results-metadata.json | 10 +- dashboard/squad/435.gromacs/results-metrics.json | 2 +- .../squad/436.cactusADM/results-metadata.json | 10 +- dashboard/squad/436.cactusADM/results-metrics.json | 2 +- dashboard/squad/437.leslie3d/results-metadata.json | 10 +- dashboard/squad/437.leslie3d/results-metrics.json | 2 +- dashboard/squad/444.namd/results-metadata.json | 10 +- dashboard/squad/444.namd/results-metrics.json | 2 +- dashboard/squad/445.gobmk/results-metadata.json | 10 +- dashboard/squad/445.gobmk/results-metrics.json | 2 +- dashboard/squad/447.dealII/results-metadata.json | 10 +- dashboard/squad/447.dealII/results-metrics.json | 2 +- dashboard/squad/450.soplex/results-metadata.json | 10 +- dashboard/squad/450.soplex/results-metrics.json | 2 +- dashboard/squad/453.povray/results-metadata.json | 10 +- dashboard/squad/453.povray/results-metrics.json | 2 +- dashboard/squad/454.calculix/results-metadata.json | 10 +- dashboard/squad/454.calculix/results-metrics.json | 2 +- dashboard/squad/456.hmmer/results-metadata.json | 10 +- dashboard/squad/456.hmmer/results-metrics.json | 2 +- dashboard/squad/458.sjeng/results-metadata.json | 10 +- dashboard/squad/458.sjeng/results-metrics.json | 2 +- dashboard/squad/459.GemsFDTD/results-metadata.json | 10 +- dashboard/squad/459.GemsFDTD/results-metrics.json | 2 +- .../squad/462.libquantum/results-metadata.json | 10 +- .../squad/462.libquantum/results-metrics.json | 2 +- dashboard/squad/464.h264ref/results-metadata.json | 10 +- dashboard/squad/464.h264ref/results-metrics.json | 2 +- dashboard/squad/465.tonto/results-metadata.json | 10 +- dashboard/squad/465.tonto/results-metrics.json | 2 +- dashboard/squad/470.lbm/results-metadata.json | 10 +- dashboard/squad/470.lbm/results-metrics.json | 2 +- dashboard/squad/471.omnetpp/results-metadata.json | 10 +- dashboard/squad/471.omnetpp/results-metrics.json | 2 +- dashboard/squad/473.astar/results-metadata.json | 10 +- dashboard/squad/473.astar/results-metrics.json | 2 +- dashboard/squad/481.wrf/results-metadata.json | 10 +- dashboard/squad/481.wrf/results-metrics.json | 2 +- dashboard/squad/482.sphinx3/results-metadata.json | 10 +- dashboard/squad/482.sphinx3/results-metrics.json | 2 +- .../squad/483.xalancbmk/results-metadata.json | 10 +- dashboard/squad/483.xalancbmk/results-metrics.json | 2 +- dashboard/squad/Mean/results-metadata.json | 10 +- dashboard/squad/Mean/results-metrics.json | 2 +- dashboard/squad/dashboard-push-squad.sh | 122 +- git/glibc_rev | 2 +- mail/jira-body.txt | 8 +- mail/mail-body.txt | 8 +- mail/mail-subject.txt | 2 +- manifest.sh | 19 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 3104504 -> 3099968 bytes save-temps/401.bzip2.tar.xz | Bin 343384 -> 342424 bytes save-temps/403.gcc.tar.xz | Bin 7887496 -> 7912020 bytes save-temps/410.bwaves.tar.xz | Bin 176704 -> 177452 bytes save-temps/416.gamess.tar.xz | Bin 32829452 -> 32842856 bytes save-temps/429.mcf.tar.xz | Bin 71608 -> 71640 bytes save-temps/433.milc.tar.xz | Bin 553292 -> 560416 bytes save-temps/434.zeusmp.tar.xz | Bin 2384252 -> 2388776 bytes save-temps/435.gromacs.tar.xz | Bin 3697632 -> 3698448 bytes save-temps/436.cactusADM.tar.xz | Bin 2695064 -> 2695184 bytes save-temps/437.leslie3d.tar.xz | Bin 656868 -> 657128 bytes save-temps/444.namd.tar.xz | Bin 688832 -> 688780 bytes save-temps/445.gobmk.tar.xz | Bin 2801120 -> 2799316 bytes save-temps/447.dealII.tar.xz | Bin 15828828 -> 16137768 bytes save-temps/450.soplex.tar.xz | Bin 1547740 -> 1554136 bytes save-temps/453.povray.tar.xz | Bin 3158596 -> 3120500 bytes save-temps/454.calculix.tar.xz | Bin 6982996 -> 6956968 bytes save-temps/456.hmmer.tar.xz | Bin 1148752 -> 1149592 bytes save-temps/458.sjeng.tar.xz | Bin 341008 -> 341288 bytes save-temps/459.GemsFDTD.tar.xz | Bin 1855196 -> 1854280 bytes save-temps/462.libquantum.tar.xz | Bin 134200 -> 134776 bytes save-temps/464.h264ref.tar.xz | Bin 3675696 -> 3712900 bytes save-temps/465.tonto.tar.xz | Bin 16675268 -> 16659644 bytes save-temps/470.lbm.tar.xz | Bin 115616 -> 115656 bytes save-temps/471.omnetpp.tar.xz | Bin 1541344 -> 1531352 bytes save-temps/473.astar.tar.xz | Bin 164740 -> 164544 bytes save-temps/481.wrf.tar.xz | Bin 24885892 -> 24813432 bytes save-temps/482.sphinx3.tar.xz | Bin 744984 -> 747196 bytes save-temps/483.xalancbmk.tar.xz | Bin 18123740 -> 18009356 bytes 124 files changed, 576267 insertions(+), 557043 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 (6d08ddac8a -> 2497bdd529)

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 6d08ddac8a 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 5d7012b50f 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards 1ab5c2dbae 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards e73bacfcb7 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 98ba3a1413 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards ae032f9597 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 0a7b8ee13a 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards f20b3a7b16 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards b32edb902b 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 1e37b14910 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 1d4ec5a8f1 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards c14cddcd56 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards dc52cf507b 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 5b262909da 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards d82cbbd9f3 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 828d6abd52 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 5db7e5a67a 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 12c8e96736 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 578ba4f790 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 4b02b1535c 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards 19f6f246f9 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 438873e9a1 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 711407712b 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 82e955eac1 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 681d3c1d74 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards a5920b36d6 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 386f925681 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards ee1162e31e 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards e614d779ad 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 91bf8e2c15 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 05b21f7cd7 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 86dfb61be9 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 3f19614afe 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards 8667c6a010 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 057209f442 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards da446d2ac3 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 9e6abace4c 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 9f0e3f48f3 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 3c506509b0 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 58ebbea504 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 229c7c507e 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 0a93ae126e 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards d757387c30 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 2fb5524db4 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 56bc8bf892 85: onsuccess: 7: Success after gcc: 9 commits discards 77b97216d8 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards c29022829d 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 6ef4278eac 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 06ae6ab52f 81: onsuccess: 7: Successful build after gcc: 2 commits discards 7e02443d68 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards e8c76578af 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards d48094f150 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d6fa933da9 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 09a9c10fb0 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards baacebcb9d 75: onsuccess: 7: Successful build after linux: 44 commits discards 64a6b5f056 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 7c7990a7a7 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5cc15f0441 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards f839a46108 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 7aca935a75 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards a4a43c88ec 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards a3690d2b4b 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 68ceba377f 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 6ad870ecff 66: onsuccess: 7: Successful build after gcc: 3 commits discards 4c9eae220b 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6cadf58ac5 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 48cb833460 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards b4a906e667 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards fe07547ca2 61: onsuccess: 4: Successful build after gcc: 15 commits discards 19cccf1432 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 81b67b0132 59: force: 7: Successful build after gcc: 2 commits discards d03080cf17 58: onsuccess: 7: Successful build after glibc: 2 commits discards 0bcc957222 57: onsuccess: 7: Successful build after gcc: 7 commits discards 4bb08a7dc7 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 4dfaf069e7 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c7e5e1188f 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards a3cb18f12c 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards defcf20cd6 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 6b5fa67d57 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 9655685799 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6754180a8c 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 5aeb169645 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards e7f9b121ad 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9fa087fffa 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 3fb9ef8e58 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 8932f9390a 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards abb02ff09a 43: onsuccess: 7: Successful build after gcc: 2 commits discards 09ab7e600a 42: onsuccess: 7: Successful build after baseline build: no [...] discards e8ffbb6139 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 04c3b152b2 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 37dec96baf 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] discards 0a70df2f6c 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards da812d3874 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards f07aff1d95 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3b4119f9b2 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 7f9b6dfdb9 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 5e5ca4dd79 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 578a09b7d1 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 14d5080872 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 1947f00cc9 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards e03cb882ac 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 14a4eac068 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new d413b578d2 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 4ee07e3586 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 041863610f 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 19fff32746 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4c1a952953 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 615e76c186 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 93c351a8e8 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2da5d325dc 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 7497439294 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new 5429d1bf4c 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] new 0e6b3cc20f 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 757b2e4881 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 9477a0aa3c 42: onsuccess: 7: Successful build after baseline build: no [...] new c620ed0149 43: onsuccess: 7: Successful build after gcc: 2 commits new 1462e386cd 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new 88b0db44a8 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a381ba8387 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 49fdc0ab9c 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 86f02aa171 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 3f613d92b2 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 0fec386dc2 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2f090fbf4d 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 692d6e6a39 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 26cc08f049 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new eb51c54de8 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 20c8c359d0 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 3723cd04ad 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2c543d59d2 57: onsuccess: 7: Successful build after gcc: 7 commits new 3cd2ca20af 58: onsuccess: 7: Successful build after glibc: 2 commits new eebbc26355 59: force: 7: Successful build after gcc: 2 commits new 8827000a17 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 4ad7165232 61: onsuccess: 4: Successful build after gcc: 15 commits new c9c5e2f701 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 3d50205a63 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 9eb0d11084 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 88c936e152 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 0dfe2f10a9 66: onsuccess: 7: Successful build after gcc: 3 commits new 45db088d30 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 2880e03ceb 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ff3671aa0e 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 6bf1546b05 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 8586ae4981 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 2eda71f8e0 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 69f8dee4c7 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 50f74377af 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 9e5c751bb9 75: onsuccess: 7: Successful build after linux: 44 commits new 5c50d9431d 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e85cea04ce 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 03e057c6f5 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 643c78a01c 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new c7ed6593a2 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 99f845d3e2 81: onsuccess: 7: Successful build after gcc: 2 commits new c972943ce6 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 1a23392a68 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 0f6dde9cc8 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new d65e6ec9c4 85: onsuccess: 7: Success after gcc: 9 commits new 2f61d36b8e 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 3e04d6afee 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 380bef85d6 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 9e99e7016a 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 118c92c166 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 62820e8a4c 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new a7154827cc 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 2d6a1740e4 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new 7e978551e9 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 985658f8b2 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new c69f894461 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 05c1c9f9b3 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 9b5a4d338e 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 4769ead859 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new f47c003318 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new 2294bcbb6a 101: onsuccess: #1609: 7: Success after binutils: 78 commits new ef76209f77 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 88a64f7c6c 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 8c633eb6a8 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 7dd8362d91 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 140eea1175 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 277585c6c0 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 0a8dcd6199 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new cf47aa6649 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 2c37ffa5b6 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new 19b9ce2758 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 15382952af 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 53a8685fb5 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 4e664056b3 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 52f5d6b51d 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 9e19967eec 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 57033a3ba8 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 8cd74f83c9 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 55f333a68f 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new e4d87b6994 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 8325c31952 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new e66628799f 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new cf831a875c 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new f8eb5b43b1 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 9ed3b0bca4 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new 86d564aea0 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new ca288f599c 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 6752428391 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 772a97f10a 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 2497bdd529 130: onsuccess: #1643: 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 (6d08ddac8a) \ 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 1672 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30292 -> 29916 bytes 05-build_abe-stage1/console.log.xz | Bin 90904 -> 90664 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8808 -> 8680 bytes 08-build_abe-glibc/console.log.xz | Bin 233904 -> 234080 bytes 09-build_abe-stage2/console.log.xz | Bin 224060 -> 222984 bytes 10-build_abe-gdb/console.log.xz | Bin 37496 -> 37056 bytes 11-build_abe-qemu/console.log.xz | Bin 31240 -> 30924 bytes 12-check_regression/console.log.xz | Bin 3524 -> 3900 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 ++++++++++---------- 21 files changed, 58 insertions(+), 58 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 (85a2a8daa0 -> f814cac4ff)

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 85a2a8daa0 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 49242b440c 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards a91920d5d8 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 22b1f82203 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards e8baf691c6 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 4121f4aaa9 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards da57ee6488 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards 24c7949a42 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards a38b22e852 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards af6eb7c851 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 1df8f06da6 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 51b23f869b 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards 468dddc2fa 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards 38e6a7c740 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards 124ab08f1d 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards 275c563067 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 6051e30c02 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 80f7060736 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards a8a9f29035 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards e8120c6e67 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards bcab078db8 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards d2a3464363 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards 4fe384fc0a 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards d64111b749 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 9268a28694 102: force: #1551: 1: Failure after gcc: 306 commits discards a767d321b7 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 129a41c1aa 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 1b715dbaa4 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 32303b235e 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 57d5aceff9 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 19e758641f 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1b97459405 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards f331e64e26 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 93392d625a 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 4e34589da0 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 8cd5df09b3 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards a9b07a2624 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 4a232d30b1 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 2f387bc516 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards fdbd54fbcb 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 9cb7c408ae 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards bee71aeb0e 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 35c974405d 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards b939f542f5 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c49eff1070 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 96fd189bbf 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 343280731f 80: onsuccess: 7: Successful build after linux: 44 commits discards cfa8446f3d 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards c7047f1ca9 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards ffd3b0b893 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards cd5b30903e 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 3cd198ac84 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 2a22d16a4f 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 618cb2713e 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 53792f1fa3 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 4b228a1516 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 4f81920884 70: onsuccess: 7: Successful build after gcc: 4 commits discards b53bd5ac6a 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6533c9b300 68: onsuccess: 7: Successful build after linux: 6 commits discards ac2c84e400 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards e5d6f55d2d 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards b528f68757 65: onsuccess: 7: Successful build after binutils: 3 commits discards 3d125696ba 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards b10282fd51 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 63a97750b5 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 34d256e25a 61: onsuccess: 4: Successful build after gcc: 5 commits discards c33669efa3 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards af8e7fdf89 59: force: 7: Successful build after gcc: 3 commits discards e7a55f082b 58: onsuccess: 7: Successful build after glibc: 2 commits discards dcd63a104b 57: onsuccess: 7: Successful build after gcc: 7 commits discards 16f929bc2a 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 601fadc8cd 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5163295824 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards a6e9abf5ad 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards b8883b9baa 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] discards 9fab96f188 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards bd68f0ed50 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 37ea5bd952 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards bbeac4a5f4 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards f17830ed03 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a9a7b1e14a 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards bf326dd532 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e849702dd3 44: onsuccess: 7: Successful build after linux: 34 commits discards cff623d2f2 43: onsuccess: 7: Successful build after gcc: 2 commits discards ad13c4695b 42: onsuccess: 7: Successful build after baseline build: no [...] discards 5481d21e1f 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e8f79877ea 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a83f736847 39: onsuccess: 7: Successful build after gcc: 2 commits discards 6fe1737a60 38: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 718a926e6e 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards e00206a9ca 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 70ca254f04 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 1ed01b7da5 34: onsuccess: 7: Successful build after gcc: 3 commits discards a925507639 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 38720d2be1 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 1687beffba 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 94366262e3 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits discards 8d7d20ff20 29: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 144680cde6 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 2ab69de6bd 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 7805789ce4 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 63b9c8e7e9 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new ab50f88e40 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new b3269b51aa 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new b1ab6af424 29: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 840b5144c2 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits new a8f3f0265d 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new d5840cb28f 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new e11889faa0 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 87eb21a630 34: onsuccess: 7: Successful build after gcc: 3 commits new 86350b8788 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 278a3403ac 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 0d68fd371c 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 5e5851bbaa 38: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new aa6c15e02d 39: onsuccess: 7: Successful build after gcc: 2 commits new 5612ac7e95 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 93de5123f5 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4d144701d6 42: onsuccess: 7: Successful build after baseline build: no [...] new 23c2b103a4 43: onsuccess: 7: Successful build after gcc: 2 commits new c15d7db1d2 44: onsuccess: 7: Successful build after linux: 34 commits new c06814e269 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7f832c0247 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 371f99e4ae 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 94c77ae4fe 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 64a5f7e461 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 2544d65fb4 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 1bc6d9650b 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 635e24faa6 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new d947275211 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 2a592e63ee 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 845e79419e 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 08655c02d0 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f13c3bfa3e 57: onsuccess: 7: Successful build after gcc: 7 commits new dcb6341b39 58: onsuccess: 7: Successful build after glibc: 2 commits new 9e745f325f 59: force: 7: Successful build after gcc: 3 commits new 5d2cefedb3 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 9be9634a7c 61: onsuccess: 4: Successful build after gcc: 5 commits new 2362736106 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new b64aff1fdb 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new af34ecb48c 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 9e905e5703 65: onsuccess: 7: Successful build after binutils: 3 commits new 2e3c5387c0 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 74847e38ca 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new 000747f144 68: onsuccess: 7: Successful build after linux: 6 commits new 071e59c024 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e740596589 70: onsuccess: 7: Successful build after gcc: 4 commits new bdc1f1a655 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new b8fcb0cfa0 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 04521d0fbe 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2837a21669 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 390ffec6a8 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 8528903ec1 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 79cff6a15b 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2bdb884ac1 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new 141d25b463 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 75827db554 80: onsuccess: 7: Successful build after linux: 44 commits new 3f10d3fb9c 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7ceb226138 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 4e7bb782b6 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new eaa28a09bc 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new ba26cb8f85 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 2bd568a8a3 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new ec130d37cb 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new ce9d8259ed 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 8b10caefbc 89: onsuccess: 7: Success after gcc/glibc: 8 commits new faf463152d 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 3a469d2090 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new f089ab07f7 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 908eed94b9 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new b6c54812fa 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 9038bc39e8 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 7105424c1c 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 0a128a8df0 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 0c31b09c59 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 113afb1ab3 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 5a28e6ba12 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new b0302b3418 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 1e8c367fe2 102: force: #1551: 1: Failure after gcc: 306 commits new a5b8a67e92 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 1c4517fea0 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 8c897ab291 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 00e0f12df1 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 9ca66960db 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new 1c0e4f13df 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new 197e72fd50 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 9097c3122b 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 3a7c926f2f 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new 000ba84116 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 29c44d0270 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new 0a136f1c0a 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new d8b6c0d533 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 110eacf7a4 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 1ef4ead52e 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 5c545d6261 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new a8304f62fd 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new da37ad3276 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new aa38018f8b 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new f360b622ea 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 7104c5275a 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new 96473f55fa 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new db5e8f0e03 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new f6ef0429bf 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new f814cac4ff 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 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 (85a2a8daa0) \ 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 1668 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30556 -> 30188 bytes 05-build_abe-stage1/console.log.xz | Bin 73056 -> 72172 bytes 07-build_abe-linux/console.log.xz | Bin 8760 -> 8744 bytes 08-build_abe-glibc/console.log.xz | Bin 239796 -> 240224 bytes 09-build_abe-stage2/console.log.xz | Bin 203076 -> 202880 bytes 10-build_abe-gdb/console.log.xz | Bin 37940 -> 37432 bytes 11-build_abe-qemu/console.log.xz | Bin 31512 -> 31348 bytes 12-check_regression/console.log.xz | Bin 3524 -> 3312 bytes 13-update_baseline/console.log | 40 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++-------------- 19 files changed, 43 insertions(+), 43 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 (ab7ef947bb -> 036184a861)

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 ab7ef947bb 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] discards a392956e55 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits discards 38d50b8bd8 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits discards 94dce9ecad 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits discards 8865c7c9f7 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits discards 1ea76588c3 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits discards 89b1b6eeb3 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits discards 54c336ab87 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits discards c2bca64573 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits discards eebfbe9d94 117: onsuccess: #2034: 1: Success after binutils: 2 commits discards a9cd3c1435 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits discards 407b5964ff 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits discards 00480c3c5b 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits discards 481bbb7058 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits discards 86ed1f4fc4 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits discards 8fc0cdb4cf 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits discards d81b4daa42 110: onsuccess: #2027: 1: Success after gcc: 5 commits discards d54535c934 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits discards 28dd16b6c2 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits discards 16ed4c0c70 107: onsuccess: #2024: 1: Success after gcc: 3 commits discards ed3090e60b 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits discards cfa18f0ffa 105: onsuccess: #2022: 1: Success after gcc: 4 commits discards 052c632514 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards 8c2dfd60f0 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards aa24042c04 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] discards 63a660dedb 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards 38d00e4085 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards e6a06e4667 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards 1cf6855838 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards ee14795410 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards 00e4920aac 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] discards aa26e8eb7d 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] discards b57bc4de2c 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards 15b40ee819 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] discards 24cb197d68 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards 7618df91dd 91: onsuccess: 1: Success after gcc: Daily bump. discards 45b5c42ec7 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards 03ab871f57 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards ff863da737 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards 5cc58bb346 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards abca4e7e9c 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards ff30701015 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards 3dd64259d4 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards 4afaffe7ac 83: onsuccess: 1: Success after gcc: 8 commits discards bebadfa090 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards 197b4e9da7 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards 58dbf08b39 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards 5655e46ad2 79: onsuccess: 1: Successful build after gcc: Daily bump. discards 10a792b87c 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 1e535e6499 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 6366ae295c 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 4c66a9e4ab 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards a5189efa5f 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards 2763da7ba1 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards 2933b89d31 72: onsuccess: 1: Successful build after gcc: 2 commits discards 49fef718e6 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 83bcd5364a 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards 112a2a8149 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards caad774a76 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards ca4f3fe6ee 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards c87b0759db 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards eaf339e68f 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards c2200fc13e 64: onsuccess: 1: Successful build after gcc: 5 commits discards 7682651290 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 9432de8759 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards cac8b62f2a 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits discards ec6a5873fe 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 95563d9364 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits discards 997ff352ac 58: onsuccess: 1: Successful build after binutils: 2 commits discards 8d32560eea 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards 5fb4a14393 56: onsuccess: 1: Successful build after gcc: Daily bump. discards f501e4dd67 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 9cb886c660 54: onsuccess: 1: Successful build after gcc: 7 commits discards b693fd1682 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 07b1cde5ea 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards eda47f1ad5 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 6704ed05d0 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards a326593f8e 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 4080cc648a 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards aa6115cd9e 47: onsuccess: 1: Successful build after binutils: 2 commits discards 0d98ba6740 46: onsuccess: 1: Successful build after gcc: Daily bump. discards 89bdd220c1 45: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 0c61d3d6d4 44: onsuccess: 1: Successful build after gcc: 2 commits discards 5cdc026185 43: onsuccess: 1: Successful build after gcc: Daily bump. discards 50dccacf4e 42: onsuccess: 1: Successful build after binutils: Automatic [...] discards acdd45468c 41: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards fbab832eb1 40: onsuccess: 1: Successful build after gcc: 2 commits discards 3ff4db4968 39: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 285add4671 38: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards bd0e8d96d4 37: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards 0b7202cf92 36: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards baae8c78f8 35: onsuccess: 1: Successful build after gcc: 4 commits discards 070ce1c3b2 34: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 15368a6dc8 33: onsuccess: 1: Successful build after gcc: 10 commits discards 666deaa3d9 32: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards 558e182910 31: onsuccess: 1: Successful build after gcc: 2 commits discards 915475374e 30: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 7fe3945935 29: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 5bdc315540 28: onsuccess: 1: Successful build after binutils/gcc: 22 commits discards ffbf288433 27: onsuccess: binutils-gcc: 1 discards d85f713a13 26: onsuccess: binutils-gcc: 1 new b85a1ed06d 26: onsuccess: binutils-gcc: 1 new 63c85b20a4 27: onsuccess: binutils-gcc: 1 new 9442b8c2d9 28: onsuccess: 1: Successful build after binutils/gcc: 22 commits new fc0890c967 29: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 8da2684d31 30: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 7efd645b4a 31: onsuccess: 1: Successful build after gcc: 2 commits new c3516192f0 32: onsuccess: 1: Successful build after binutils/gcc: 9 commits new d74ae8e258 33: onsuccess: 1: Successful build after gcc: 10 commits new 3d90945668 34: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 823de2a97f 35: onsuccess: 1: Successful build after gcc: 4 commits new fd6229ff42 36: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 1e285abfe1 37: onsuccess: 1: Successful build after binutils/gcc: 12 commits new 7a40393c25 38: onsuccess: 1: Successful build after binutils/gcc: 5 commits new efea2343e3 39: onsuccess: 1: Successful build after binutils/gcc: 3 commits new f88c68f834 40: onsuccess: 1: Successful build after gcc: 2 commits new b51622006e 41: onsuccess: 1: Successful build after binutils/gcc: 6 commits new b019b2064b 42: onsuccess: 1: Successful build after binutils: Automatic [...] new 7ea315dcec 43: onsuccess: 1: Successful build after gcc: Daily bump. new 655cec8248 44: onsuccess: 1: Successful build after gcc: 2 commits new 1580cdb7a3 45: onsuccess: 1: Successful build after binutils/gcc: 4 commits new ae260524b3 46: onsuccess: 1: Successful build after gcc: Daily bump. new 6e6ad07936 47: onsuccess: 1: Successful build after binutils: 2 commits new 439033275e 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 4b00ff1e88 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits new a83c168c31 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 9b8836dd84 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 167e284ee5 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 5dd6c7f605 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 2369959b20 54: onsuccess: 1: Successful build after gcc: 7 commits new 3cad7ed6a5 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 6667cb1cdf 56: onsuccess: 1: Successful build after gcc: Daily bump. new 7b646dd5e6 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits new 11810de718 58: onsuccess: 1: Successful build after binutils: 2 commits new 28f78147fc 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits new 4fa0290a9e 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 817ddedf97 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits new a781bff76e 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 2246d4407c 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 22f49fa6f3 64: onsuccess: 1: Successful build after gcc: 5 commits new 47da4b122e 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits new b698fbae8e 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 2c16894b70 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new e47c0f6073 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new fc7f32040f 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 11d926aaf9 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new 32f79031e5 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 4d9920ef38 72: onsuccess: 1: Successful build after gcc: 2 commits new 7d0bbe6d50 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 398438f3c9 74: onsuccess: 1: Successful build after binutils: Automatic [...] new e78b8baa3c 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new b341754312 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new f5f41c4548 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new e59ae9d055 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 9cb5c90e4d 79: onsuccess: 1: Successful build after gcc: Daily bump. new 1b1baa54c4 80: onsuccess: 1: Success after binutils/gcc: 14 commits new 3ee6478082 81: onsuccess: 1: Success after binutils/gcc: 27 commits new 5dbfcd9556 82: onsuccess: 1: Success after binutils/gcc: 10 commits new 676ed97a57 83: onsuccess: 1: Success after gcc: 8 commits new 2541de8b04 84: onsuccess: 1: Success after binutils/gcc: 9 commits new 8b6262d4d0 85: onsuccess: 1: Success after binutils/gcc: 9 commits new f5d7859568 86: onsuccess: 1: Success after binutils/gcc: 13 commits new 7e796f39c6 87: onsuccess: 1: Success after binutils/gcc: 4 commits new 7a53698ff2 88: onsuccess: 1: Success after binutils/gcc: 16 commits new c661d5d715 89: onsuccess: 1: Success after binutils/gcc: 9 commits new e4fd828e08 90: onsuccess: 1: Success after binutils/gcc: 6 commits new f6bfd0903c 91: onsuccess: 1: Success after gcc: Daily bump. new 481faab88f 92: onsuccess: #1965: 1: Success after gcc: 2 commits new 40fc50e1d6 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] new 3711eac8c2 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new ef881a386c 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] new 327fa94d15 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] new 5419016e7e 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new 6d93ac11b8 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new 634f118ab7 99: onsuccess: #1974: 1: Success after gcc: 14 commits new d030ea1708 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new a0106bdf98 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new 8854fa0069 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] new 8044e2eb56 103: onsuccess: #2020: 1: Success after gcc: 2 commits new bfa8c7f191 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new 7e63c33a91 105: onsuccess: #2022: 1: Success after gcc: 4 commits new 4e0b037898 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits new d23ee89c03 107: onsuccess: #2024: 1: Success after gcc: 3 commits new 4b35d81016 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits new 342fe26999 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits new aca87d1925 110: onsuccess: #2027: 1: Success after gcc: 5 commits new b4ca5adec5 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits new 2a068f195e 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits new 97d015d2ca 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits new b3af0630a1 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits new ec8715f584 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits new c714a5554c 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits new 36bc03633a 117: onsuccess: #2034: 1: Success after binutils: 2 commits new 0c15d397ed 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits new dcce948543 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits new 33e3889ee1 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits new 720547a647 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits new 7e8c020082 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits new 02c1e28a75 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits new cec4fa3978 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits new 9be57e0b90 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits new dc04c280c0 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] new 036184a861 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] 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 (ab7ef947bb) \ 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 1740 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2704 bytes 03-build_abe-binutils/console.log.xz | Bin 38480 -> 37360 bytes 04-build_abe-gcc/console.log.xz | Bin 213200 -> 212024 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3816 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2824 -> 2852 bytes 07-check_regression/console.log.xz | Bin 5140 -> 4760 bytes 07-check_regression/extra-bisect-params | 1 - 07-check_regression/fails.sum | 7 - 07-check_regression/mail-body.txt | 64 +- 07-check_regression/results.compare | 34 +- 07-check_regression/results.compare2 | 51 +- 07-check_regression/results.regressions | 42 - 08-update_baseline/console.log | 42 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 66 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 42 - sumfiles/g++.log.xz | Bin 3580492 -> 3599380 bytes sumfiles/g++.sum | 116 +- sumfiles/gcc.log.xz | Bin 3132772 -> 3098164 bytes sumfiles/gcc.sum | 4692 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1025580 -> 1034784 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2184 -> 2184 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207440 -> 207372 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2548 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 440880 -> 446488 bytes sumfiles/libstdc++.sum | 10 +- 35 files changed, 2525 insertions(+), 2730 deletions(-) delete mode 100644 07-check_regression/extra-bisect-params delete mode 100644 07-check_regression/fails.sum delete mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[linux] branch master updated (1a61b828566f -> 105a36f3694e)

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 linux. from 1a61b828566f Merge tag 'char-misc-6.0-rc7' of git://git.kernel.org/pub/ [...] new d36cb843e456 OPP: Fix an un-initialized variable usage new c7e31e36d8a2 dt-bindings: opp: Add missing (unevaluated|additional)Prop [...] new 9614369a042a Merge tag 'opp-fixes-6.0' of git://git.kernel.org/pub/scm/ [...] new 42f9508b3bcb Merge tag 'pm-6.0-rc7' of git://git.kernel.org/pub/scm/lin [...] new 1918f2b20c3d s390/vfio-ap: bypass unnecessary processing of AP resources new 23b99237f86d Merge tag 's390-6.0-5' of git://git.kernel.org/pub/scm/lin [...] new 237fe7274942 scripts/clang-tools: remove unused module new 03764b30a4f0 Kconfig: remove unused function 'menu_get_root_menu' new 2154aca21408 certs: make system keyring depend on built-in x509 parser new 61f2b7c7497b Makefile.debug: set -g unconditional on CONFIG_DEBUG_INFO_SPLIT new 32ef9e5054ec Makefile.debug: re-enable debug info for .S files new 105a36f3694e Merge tag 'kbuild-fixes-v6.0-3' of git://git.kernel.org/pu [...] The 12 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: .../devicetree/bindings/opp/opp-v2-kryo-cpu.yaml | 1 + .../devicetree/bindings/opp/opp-v2-qcom-level.yaml | 1 + certs/Kconfig | 2 +- drivers/opp/core.c | 2 +- drivers/s390/crypto/vfio_ap_ops.c | 30 ++++++++++++++++++++++ lib/Kconfig.debug | 4 ++- scripts/Makefile.debug | 21 ++++++++------- scripts/clang-tools/run-clang-tools.py | 1 - scripts/kconfig/lkc.h | 1 - scripts/kconfig/menu.c | 5 ---- 10 files changed, 47 insertions(+), 21 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_bootstrap/master-arm-bootstrap_debug updated (8267187c13 -> 45d57e79d7)

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_debug in repository toolchain/ci/base-artifacts. from 8267187c13 47: onsuccess: #458: 2: Success after binutils/gcc: 98 commits new 45d57e79d7 48: onsuccess: #459: 2: Success after binutils/gcc: 11 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 -> 1660 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 50572 -> 50232 bytes 05-build_abe-bootstrap_debug/console.log.xz | Bin 467100 -> 466580 bytes 06-check_regression/console.log.xz | Bin 3132 -> 3052 bytes 07-update_baseline/console.log | 2 +- 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, 16 insertions(+), 16 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