Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[gcc] branch master updated (5608e410914 -> 32524808fad)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 5608e410914 Convert CFN_BUILT_IN_PARITY to range-ops. new 32524808fad Update gcc fr.po The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/po/fr.po | 19 ++++++++----------- 1 file changed, 8 insertions(+), 11 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_check_gcc/master-arm updated (5eee49435 -> 6cf93a4fe)

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 5eee49435 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/gd [...] discards 3b31328ce 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards e42a6a4cd 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...] discards 7b4d7d5d7 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] discards d56b9fa94 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits discards 0f2bd9f18 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] discards 606657068 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] discards 7b2989576 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] discards de8da2c43 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] discards cfd9633f8 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 1acba66f5 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 314680c66 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards ca0acc48e 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] discards 5848b94ba 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] discards fbbd4aaa3 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] discards a2f6d4d09 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards a15639085 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards abb42dd2a 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards 06d7f906a 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards e65a4cd20 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards 863533311 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards a49fe621c 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards 4dd84ef20 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 2f6b61209 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards a6a343160 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards 72d1da76e 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards 1cbf3cb75 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards beb649489 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards 8796c28f0 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 451c35959 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 9b737f5a8 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards e71c5736d 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 49a75a010 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 332fc6944 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 5ee245671 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 2b449b0a4 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 1d2fdf91f 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 5de05162f 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 2b69b0fd1 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards ae093f858 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards c16990a3d 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards b5d4a1410 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 1fc3c9791 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f6e920241 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards 3e5e083ad 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9d11781cc 74: onsuccess: 1: Successful build after linux: 44 commits discards 3268a2560 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 2490b0279 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7e1166dae 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards 3980ce15f 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards b3105e237 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 773be991a 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 67800a782 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b9f5386ab 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 179bc2e62 65: onsuccess: 1: Successful build after gcc: 4 commits discards 22d2af539 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a3ceefbc4 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a57697b96 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards 7fa83bf2b 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 9b61c9f47 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 9ec81ee78 59: onsuccess: 1: Successful build after glibc: 2 commits discards 282838ae8 58: onsuccess: 1: Successful build after binutils: 2 commits discards 0bb728355 57: onsuccess: 1: Successful build after gcc: 7 commits discards 6fa70e3f9 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 712ad4f26 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 8db389579 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards cffdcdfbe 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 91341f894 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards e747c395e 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 87cfc5046 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 377dfcf0e 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 664c15179 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 0c4eb4d95 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 4c09c1521 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 2e276e379 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 03cfd693a 44: onsuccess: 1: Successful build after linux: 34 commits discards b3678b7cf 43: onsuccess: 1: Successful build after gcc: 2 commits discards e1a691ea9 42: onsuccess: 1: Successful build after baseline build: no n [...] discards 6e0f910d9 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 805f55b30 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 58804fa87 39: onsuccess: 1: Successful build after gcc: 2 commits discards d18c60efa 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a0a622bd5 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards e95117588 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5ff7f484c 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards f8751408b 34: onsuccess: 1: Successful build after gcc: 3 commits discards 4eb590d39 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 186bff417 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 23b372b20 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 99e551480 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards 02e2da320 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f51d218c1 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 8e63d3709 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 1f9088d70 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 01b309d12 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6e3cb7561 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 17fa8e6fb 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a2ac290a2 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 94a7a5c27 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 883d4f6ee 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b8c4afc7a 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5493d34d2 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9a007a697 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 66aeb1d4f 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b5d3969c9 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6e855d221 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b9998e2af 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 76af08d71 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5e5f3b1e3 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f0a438f08 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 59b14e109 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new f68ae2c1e 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cfd427be3 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new b7f13cc06 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new a2cd69e24 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new d95552334 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c4e0195e5 34: onsuccess: 1: Successful build after gcc: 3 commits new 45451b5cd 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 659e8c990 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c80680021 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new e472062a9 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 790984d2d 39: onsuccess: 1: Successful build after gcc: 2 commits new c539472f5 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 81ef9bd52 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a8d8faccf 42: onsuccess: 1: Successful build after baseline build: no n [...] new 6e1192658 43: onsuccess: 1: Successful build after gcc: 2 commits new 8e0a1c2a8 44: onsuccess: 1: Successful build after linux: 34 commits new f4ec3fd84 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d57c27aff 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new d1543f6f7 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new da86da570 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 6379d45be 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new ddee9d582 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 112951b06 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 9b4148e59 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 20c2afa76 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new 68b0edb93 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 2c962715d 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e806de8a9 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new ce67293d4 57: onsuccess: 1: Successful build after gcc: 7 commits new 57c6c1285 58: onsuccess: 1: Successful build after binutils: 2 commits new 993cb7230 59: onsuccess: 1: Successful build after glibc: 2 commits new 2ce99b79d 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 3f73fbdf9 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 121aee673 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new 0d292a008 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a513d5cbc 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d2c9f5164 65: onsuccess: 1: Successful build after gcc: 4 commits new 5bd301bc3 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new d29b2b9a4 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c89ffff3a 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 76e869f38 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new bbdd4f8ef 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new 1bbf45f94 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new 51a65f188 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cbc1cb86e 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 40d211043 74: onsuccess: 1: Successful build after linux: 44 commits new b85b0e3c0 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 168df3119 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new 04f433d63 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 463c2415a 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new cd79f331a 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 7b659a6dc 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new 607d8be8b 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 01a4526e5 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 1b5b575c9 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 5ead184d6 84: onsuccess: 1: Success after gcc/glibc: 9 commits new cbee85da6 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new fc8975484 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 2d85a3bbe 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 3aca5cb93 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 2f9624dcf 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new f1930121b 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new b4391ae68 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 9ca037e35 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new b9fa43af7 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 1aa99a1df 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new faed20e4e 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new ea8feb0dc 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new fb2259f5c 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new 4dd3ae978 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new 46090094f 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new 27a2df966 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new 598a8fc9a 101: onsuccess: #1693: 1: Success after glibc: 14 commits new b16a78a43 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new e04b33fd1 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new ace8fdd15 104: onsuccess: #1697: 1: Success after gcc: 4 commits new dda2bfc9d 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] new c655dad47 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] new cac44c007 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] new 2eba566b5 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 69d9f93d3 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 210deb0d8 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 70b3063a3 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] new 6f0a0b944 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] new 5edc62e08 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] new 8ef15db9b 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] new 8e1398106 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits new 2a12462e9 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] new 5c1146216 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...] new ab91e4b90 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 3744ea364 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/gd [...] new 6cf93a4fe 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/gd [...] 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 (5eee49435) \ 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 1684 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 29988 -> 31136 bytes 04-build_abe-stage1/console.log.xz | Bin 90892 -> 91220 bytes 06-build_abe-linux/console.log.xz | Bin 8584 -> 9264 bytes 07-build_abe-glibc/console.log.xz | Bin 234352 -> 234064 bytes 08-build_abe-stage2/console.log.xz | Bin 225100 -> 225256 bytes 09-build_abe-gdb/console.log.xz | Bin 37312 -> 38260 bytes 10-build_abe-qemu/console.log.xz | Bin 31448 -> 31348 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3908 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2968 -> 2624 bytes 13-check_regression/console.log.xz | Bin 5616 -> 6456 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 | 199 ++- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- results | 26 - sumfiles/g++.log.xz | Bin 2664008 -> 2684556 bytes sumfiles/g++.sum | 32 +- sumfiles/gcc.log.xz | Bin 2233884 -> 2216340 bytes sumfiles/gcc.sum | 2082 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 880560 -> 881176 bytes sumfiles/gfortran.sum | 17 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201052 -> 201032 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 420272 -> 422452 bytes sumfiles/libstdc++.sum | 122 +- 44 files changed, 1411 insertions(+), 1333 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/llvm-master-aarch64-stable-allnoconfig updated (8493816db -> fb55ddb0f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-allnoconfig in repository toolchain/ci/base-artifacts. from 8493816db 12: onsuccess: #460: boot: Success after binutils/llvm/linux/ [...] new fb55ddb0f 13: onsuccess: #461: boot: Success after binutils/llvm/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1708 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30088 -> 31144 bytes 04-build_kernel_llvm/console.log.xz | Bin 65300 -> 65744 bytes 05-build_abe-qemu/console.log.xz | Bin 31612 -> 31716 bytes 06-build_linux/console.log.xz | Bin 3316 -> 3384 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3324 -> 3344 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 18 files changed, 27 insertions(+), 27 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 updated (2b4e6ed2e -> 09a2186a6)

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 in repository toolchain/ci/base-artifacts. discards 2b4e6ed2e 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards 1b9ebf74f 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards 4eaa85c1f 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards 7a3446e4e 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards 3f942a7a7 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards b46c5ea4f 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards a2742507f 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards 289d09307 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards cbd433e0b 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 63aa492b3 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards 9d864e640 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards 60b4194f4 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards ae99d8006 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards a51615b3e 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-271 [...] discards fcc224655 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards a36951fc1 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-271 [...] discards e42482d1e 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards e7cfd9f5c 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards db93b2abb 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards db0f14c5e 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 6bf9c4afc 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards 546eb8081 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards f07b75b08 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards 4ee495408 99: onsuccess: #1455: 2: Success after baseline build: no new [...] discards 38817966b 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-2393 [...] discards c42c3509c 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 0a2579708 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards d647de5c9 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-2389 [...] discards 48dfff37a 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP 5 [...] discards 8d8922fc1 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards 428ac0027 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards ebde0fbc7 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards 6da3adcbf 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards df6e97854 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards 412a5c903 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards c41c5d26d 87: onsuccess: 2: Success after gcc: 4 commits discards ce666aa00 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards 65aa6e3b8 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards befe94f28 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 9bf289d15 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 2d70fe544 82: onsuccess: 1: Successful build after gcc: 3 commits discards 0a1cc7b57 81: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] discards 744adeca8 80: force: 2: Successful build after gcc: 14 commits discards 8a7a20944 79: onsuccess: 2: Successful build after binutils: 5 commits discards 61ca8d84d 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards acbeb8a31 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards c74e844f7 76: onsuccess: 2: Successful build after gcc: 12 commits discards 88cc44f7f 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 4bb1cc10d 74: onsuccess: 2: Successful build after baseline build: no n [...] discards 4034d1927 73: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] discards 332ca07fc 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards d2e644a70 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 116ddae30 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards ba805f6d9 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards f94ce8bba 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 265992b2b 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 95f7e6632 66: onsuccess: 2: Successful build after gcc: 9 commits discards a76912c4f 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 12803b244 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards c2ac15692 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 64df50042 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 20401ee45 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards c7073dfdf 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards 2586723ab 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] discards 15c58ab46 58: force: 2: Successful build after gcc: 6 commits discards 7c7bb5b11 57: onsuccess: 2: Successful build after binutils: gdb: new ' [...] discards 6e2e71dcb 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards a42f32380 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 3792236e2 54: onsuccess: 2: Successful build after gcc: 5 commits discards e2da99778 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 30db68dfe 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards d7ab783d2 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 4772e8e3c 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 70f82ae77 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards a9ef5e06b 48: onsuccess: 2: Successful build after gcc: 4 commits discards 1baa29cc2 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 3161cd421 46: onsuccess: 2: Successful build after baseline build: no n [...] discards 8982cf618 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards ca66df0f6 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 0487946d7 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] discards 9e63eec8e 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] discards 9e3b56eb9 41: onsuccess: 2: Successful build after gcc: libcpp: Impleme [...] discards abac04e7a 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards ae3ad89ef 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards ad40ee494 38: onsuccess: 2: Successful build after gcc: 2 commits discards 0f0cd5a2a 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 169883f88 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 2a35ae932 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 114322144 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 5b32fe87b 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 2d83294dd 32: onsuccess: 2: Successful build after gcc: 6 commits discards 315a909db 31: onsuccess: 2: Successful build after gcc: 6 commits discards d5d3e9cdb 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 72cf12906 29: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards d141a4b66 28: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards be2a73a48 27: onsuccess: 2: Successful build after binutils/gcc: 14 commits discards 664dc968d 26: onsuccess: binutils-gcc: 2 discards d3b379979 25: onsuccess: binutils-gcc: 2 discards d489dba4e 24: onsuccess: binutils-gcc: 2 discards 13ede2722 23: onsuccess: binutils-gcc: 2 discards ed52b0845 22: onsuccess: binutils-gcc: 2 new 90d5763fc 22: onsuccess: binutils-gcc: 2 new 8500b8e62 23: onsuccess: binutils-gcc: 2 new 7fd0b17d6 24: onsuccess: binutils-gcc: 2 new 64002f830 25: onsuccess: binutils-gcc: 2 new 0a7bbb96a 26: onsuccess: binutils-gcc: 2 new 4ae689427 27: onsuccess: 2: Successful build after binutils/gcc: 14 commits new f867e4aa2 28: onsuccess: 2: Successful build after binutils/gcc: 8 commits new e53d28050 29: onsuccess: 2: Successful build after binutils/gcc: 4 commits new fb7f8978a 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 411d1401d 31: onsuccess: 2: Successful build after gcc: 6 commits new f1ed75777 32: onsuccess: 2: Successful build after gcc: 6 commits new 57329e400 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 512f57cc8 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 5364c9877 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 8490f1fb9 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 60698d910 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 174412c93 38: onsuccess: 2: Successful build after gcc: 2 commits new a153064d4 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 0f4ec7cdb 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new ca36ce64a 41: onsuccess: 2: Successful build after gcc: libcpp: Impleme [...] new fb3026abf 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] new aa3883ee4 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] new 46426b58b 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new a929f0ff3 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 71cd2eac7 46: onsuccess: 2: Successful build after baseline build: no n [...] new 6f0134f25 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits new af910a7db 48: onsuccess: 2: Successful build after gcc: 4 commits new 1277283a0 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new a72b6c7e9 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new f55f1e402 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new b30ec9768 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 340add4d1 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 68746ed7b 54: onsuccess: 2: Successful build after gcc: 5 commits new db5873312 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new bf0e0a874 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new e6b7d325e 57: onsuccess: 2: Successful build after binutils: gdb: new ' [...] new c15976e7a 58: force: 2: Successful build after gcc: 6 commits new 52c0776a0 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] new 811639c2e 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 4b580337c 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new 52ca71afe 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new ccd89f1c9 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new e01843844 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new c50b75c58 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 8312473b0 66: onsuccess: 2: Successful build after gcc: 9 commits new 9f80817c6 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 1a547f297 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new ccab9bb6e 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new e478d64a9 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 1588d2d59 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 546c87a31 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 7fa06251b 73: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] new e978f46cb 74: onsuccess: 2: Successful build after baseline build: no n [...] new 90b9589bc 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new dbf652446 76: onsuccess: 2: Successful build after gcc: 12 commits new 69aedb6c5 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new abe39c62b 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new 22670154d 79: onsuccess: 2: Successful build after binutils: 5 commits new c08dcfe09 80: force: 2: Successful build after gcc: 14 commits new f1bc04db4 81: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] new d9284241c 82: onsuccess: 1: Successful build after gcc: 3 commits new 59ec75f97 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new 027802294 84: onsuccess: 2: Success after binutils/gcc: 15 commits new 938d874b8 85: onsuccess: 2: Success after binutils/gcc: 25 commits new 99a4a699b 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 769895d93 87: onsuccess: 2: Success after gcc: 4 commits new 0c9290b01 88: onsuccess: 2: Success after binutils/gcc: 25 commits new c8530d3f3 89: onsuccess: 2: Success after binutils/gcc: 4 commits new eee9a4d8b 90: onsuccess: 2: Success after binutils/gcc: 16 commits new 03014beb6 91: onsuccess: 2: Success after binutils/gcc: 7 commits new fad4342e9 92: onsuccess: 2: Success after binutils/gcc: 9 commits new 24de503ac 93: onsuccess: 2: Success after binutils/gcc: 3 commits new 3ab731600 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP 5 [...] new 62001c262 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-2389 [...] new 02078956b 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 65b0e0857 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new 8dfd8f08c 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-2393 [...] new 8cb4766b7 99: onsuccess: #1455: 2: Success after baseline build: no new [...] new d0f9ebd66 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new e84a68dc7 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new 31a9c9ca9 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new d66764bb9 103: onsuccess: #1504: 2: Success after gcc: 2 commits new e4ef62faa 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new 89a75d52e 105: onsuccess: #1506: 2: Success after gcc: 2 commits new cd6199c7a 106: onsuccess: #1507: 2: Success after gcc: 2 commits new c5d32dc10 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-271 [...] new 11381470f 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 1635da04f 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-271 [...] new 3e816aab1 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new 2ca4c4e45 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new 527479ef3 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new 38f642657 113: onsuccess: #1514: 2: Success after gcc: 5 commits new a6a502277 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new fb9bd77a7 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new 8baf7ea42 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new 4d727691a 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 0b5507207 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new dedca665a 119: onsuccess: #1520: 2: Success after binutils: 8 commits new 1d4a2af93 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new c15c9e905 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new ba9a70673 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new 09a2186a6 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 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 (2b4e6ed2e) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] 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 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 50604 -> 52080 bytes 05-build_abe-bootstrap/console.log.xz | Bin 464588 -> 461812 bytes 06-check_regression/console.log.xz | Bin 2340 -> 2204 bytes 07-update_baseline/console.log | 28 ++++++++++++++-------------- 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 | 16 ++++++++-------- 13 files changed, 28 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-defconfig updated (5bf56f16a -> e475c2646)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-defconfig in repository toolchain/ci/base-artifacts. from 5bf56f16a 11: onsuccess: #427: boot: Success after binutils/llvm/linux: [...] new e475c2646 12: onsuccess: #429: boot: Success after binutils/llvm/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1700 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30076 -> 30880 bytes 04-build_kernel_llvm/console.log.xz | Bin 64156 -> 64012 bytes 05-build_abe-qemu/console.log.xz | Bin 31504 -> 31264 bytes 06-build_linux/console.log.xz | Bin 4216 -> 4268 bytes 07-boot_linux/console.log.xz | Bin 5656 -> 5664 bytes 08-check_regression/console.log.xz | Bin 2940 -> 3512 bytes 08-check_regression/mail-body.txt | 4 ++-- 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- results | 2 +- 20 files changed, 32 insertions(+), 32 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-lts-defconfig updated (f151955e0 -> 295b913e7)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-lts-defconfig in repository toolchain/ci/base-artifacts. from f151955e0 9: onsuccess: #262: boot: Success after binutils/llvm/linux/q [...] new 295b913e7 10: onsuccess: #263: boot: Success after binutils/llvm/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1704 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 29968 -> 30332 bytes 04-build_kernel_llvm/console.log.xz | Bin 64620 -> 64420 bytes 05-build_abe-qemu/console.log.xz | Bin 31108 -> 31512 bytes 06-build_linux/console.log.xz | Bin 3440 -> 3524 bytes 07-boot_linux/console.log.xz | Bin 5836 -> 5832 bytes 08-check_regression/console.log.xz | Bin 3328 -> 3316 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 17 files changed, 23 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 updated (30f8a9f7c -> b4a01dd19)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap in repository toolchain/ci/base-artifacts. discards 30f8a9f7c 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards dde232c6d 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards ee0085dbe 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards fb8d94800 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards c08276e95 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 8b4055d7a 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards dd999cd45 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards ffc1b4aad 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards 394c7e0d8 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards ec0fa22d4 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 309b9971b 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 58fcfe314 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards e2a9a3b29 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-271 [...] discards 907128fe4 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 506deef40 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 3ccabaae6 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards f8d12f974 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards c8fd5a422 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 47a353d8b 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards ab1eeee05 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards 55a16e690 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards f9c8e8c85 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards 7db2afd45 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 5e914c002 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 8aabf6af4 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards 483200ed3 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards ff0ac5567 94: onsuccess: #1476: 2: Success after baseline build: no new [...] discards c17d2f8fc 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-2393 [...] discards 3618c6bca 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 63d9489f6 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards c457e0b98 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards b96f025df 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 265670357 88: onsuccess: 1: Success after gcc: 20 commits discards 0b271cee6 87: force: 1: Failure after gcc: Fix up dump_printf_loc forma [...] discards 21894c293 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 w [...] discards 9cf761e07 85: onsuccess: 2: Success after binutils: 4 commits discards 9a8ec60e6 84: onsuccess: 2: Success after gcc: 9 commits discards 6bcf3a337 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards bbde91b34 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 948bab7e3 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 96d94d108 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 55a26f8b0 79: onsuccess: 1: Successful build after gcc: 3 commits discards 63d06a8f9 78: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] discards 6530c4b6c 77: force: 2: Successful build after gcc: 32 commits discards 03992634f 76: onsuccess: 2: Successful build after binutils: 10 commits discards 68f3e3f63 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 5761762fd 74: onsuccess: 2: Successful build after gcc: 13 commits discards 332905964 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 2dd6f86b5 72: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] discards e7aa06686 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards cf797c406 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards fe2337b23 69: onsuccess: 2: Successful build after baseline build: no n [...] discards edb2c1859 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards d032c887b 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 883041eee 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 68aef5d87 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards bb03abc1e 64: onsuccess: 2: Successful build after gcc: 7 commits discards 179d41a9c 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 58deab211 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 448374dad 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 58ad9529b 60: onsuccess: 1: Successful build after gcc: 15 commits discards 7ee32ab51 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] discards 0c585c83c 58: force: 2: Successful build after gcc: tree.cc: Fix optimi [...] discards fa16e226d 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards c4a85cac1 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 28467d2a3 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards bec1ecfb7 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 37070cbb5 53: onsuccess: 2: Successful build after gcc: 5 commits discards b5af5f8a2 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 739ba49a1 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 90bc99e35 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 78546fd37 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards e18bff4ff 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards e4690e840 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 2c3f8dc5c 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards cd1d3fb68 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards f89e61e8e 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards c9a152514 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] discards a4f23f6d6 42: onsuccess: 2: Successful build after gcc: 2 commits discards 7e6a859e7 41: onsuccess: 2: Successful build after baseline build: no n [...] discards 04cf2511b 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards e92c57c72 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards a214b0c29 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 95a37247f 37: onsuccess: 2: Successful build after gcc: 2 commits discards 57b14b3c0 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 5a601a930 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards a13a22303 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 3ac27e838 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 5a08e9832 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 0d7247a7c 31: onsuccess: 2: Successful build after gcc: 8 commits discards b6b6c42e8 30: onsuccess: 2: Successful build after gcc: 7 commits discards 847d43a04 29: onsuccess: 2: Successful build after binutils: 5 commits discards 30fec5378 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 199affdd3 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards f643aca3e 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits discards 2517cc3c2 25: onsuccess: binutils-gcc: 2 discards ad3d39049 24: onsuccess: binutils-gcc: 2 discards 9e9d95f58 23: onsuccess: binutils-gcc: 2 discards 2fdf658a0 22: onsuccess: binutils-gcc: 2 discards 7de4a7169 21: onsuccess: binutils-gcc: 2 discards cb10369cf 20: onsuccess: binutils-gcc: 2 new 1d3b4b5b9 20: onsuccess: binutils-gcc: 2 new a4bf7384d 21: onsuccess: binutils-gcc: 2 new 6251ce8e9 22: onsuccess: binutils-gcc: 2 new 3033ac14f 23: onsuccess: binutils-gcc: 2 new b9b5a2a33 24: onsuccess: binutils-gcc: 2 new ca0df5ca1 25: onsuccess: binutils-gcc: 2 new f0391a7a5 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits new aa9f8871d 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits new ffc2ecb96 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 79d422114 29: onsuccess: 2: Successful build after binutils: 5 commits new f6a1d89a5 30: onsuccess: 2: Successful build after gcc: 7 commits new 07cdee283 31: onsuccess: 2: Successful build after gcc: 8 commits new 0e0be3443 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits new b05daff25 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits new af241c685 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 2d7210eb8 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 6a05039c9 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits new d8ff7357c 37: onsuccess: 2: Successful build after gcc: 2 commits new 32053bbaa 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 410d49d15 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new be1d773fd 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 574e61d20 41: onsuccess: 2: Successful build after baseline build: no n [...] new 6b400dcf8 42: onsuccess: 2: Successful build after gcc: 2 commits new a143e8da5 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] new ebfa06f4c 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 1aa364261 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 0c88bf22a 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new f9d0c0d00 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 140279317 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new e230a48d6 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 5e6e195fd 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new e7cc45425 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 1cb9313b0 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 85504b980 53: onsuccess: 2: Successful build after gcc: 5 commits new d9a068ac4 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 1bd3031ed 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 13dda1361 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 13284a9a6 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 9d3e57b6a 58: force: 2: Successful build after gcc: tree.cc: Fix optimi [...] new 1fbb52378 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] new eae241fdb 60: onsuccess: 1: Successful build after gcc: 15 commits new e09d15511 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 47d069817 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new a3437e6f3 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 49ef3f4b0 64: onsuccess: 2: Successful build after gcc: 7 commits new 7c9c21111 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 35901a6f1 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new d852fa191 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new f0acdab2b 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 710a746a8 69: onsuccess: 2: Successful build after baseline build: no n [...] new 0640f9b67 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 4305c1976 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new d518f37e8 72: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] new d0ccf0e6d 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 2eb7e83f1 74: onsuccess: 2: Successful build after gcc: 13 commits new 1c0773722 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 8286b19fa 76: onsuccess: 2: Successful build after binutils: 10 commits new 9825aa0e5 77: force: 2: Successful build after gcc: 32 commits new 7bcfedee4 78: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] new 7e50d0667 79: onsuccess: 1: Successful build after gcc: 3 commits new 453da941c 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 614ebd12c 81: onsuccess: 2: Success after binutils/gcc: 16 commits new eaa373f88 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 362748323 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 55f0e81c4 84: onsuccess: 2: Success after gcc: 9 commits new 3ad54daf7 85: onsuccess: 2: Success after binutils: 4 commits new c8b101cf7 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 w [...] new af51d5fee 87: force: 1: Failure after gcc: Fix up dump_printf_loc forma [...] new 909c73c5d 88: onsuccess: 1: Success after gcc: 20 commits new 420cb1307 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 05c5e18d9 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 68bd3a43d 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 4c425eff6 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 871afe38a 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-2393 [...] new 034bdc50c 94: onsuccess: #1476: 2: Success after baseline build: no new [...] new a61f51706 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new cd88d6e5e 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 3abec6e89 97: onsuccess: #1481: 2: Success after gcc: 8 commits new d02a38712 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new cd765611f 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 7b072f3c0 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new 14f8f9842 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new 0b3827bfd 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new b27419266 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 7a648fd34 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 7d812aba6 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 90ab6cf6c 106: onsuccess: #1527: 2: Success after gcc: 2 commits new ac2560b9d 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new 710ab8bf2 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-271 [...] new f6115336a 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new dd66a9a09 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 48ef46032 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 27268b311 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 37aff398d 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new bb43ccb84 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new daeb8a5b4 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 06a01b9eb 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new b0f074f60 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new 02b9d0369 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 028646771 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new 0c7db8b95 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new b4a01dd19 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 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 (30f8a9f7c) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1680 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 37964 -> 38520 bytes 05-build_abe-bootstrap/console.log.xz | Bin 269200 -> 267760 bytes 06-check_regression/console.log.xz | Bin 2328 -> 2212 bytes 07-update_baseline/console.log | 30 +++++++++++++++--------------- 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 | 16 ++++++++-------- 13 files changed, 29 insertions(+), 29 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allnoconfig updated (e2fc6387a -> 1c84b294f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allnoconfig in repository toolchain/ci/base-artifacts. from e2fc6387a 10: onsuccess: #400: all: Success after binutils/llvm/linux/q [...] new 1c84b294f 11: onsuccess: #401: all: Success after binutils/llvm/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 1684 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 29784 -> 29928 bytes 04-build_kernel_llvm/console.log.xz | Bin 63736 -> 63984 bytes 05-build_abe-qemu/console.log.xz | Bin 31248 -> 32208 bytes 06-build_linux/console.log.xz | Bin 3160 -> 3188 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 3260 -> 3548 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 17 files changed, 23 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_gnu_cross_build/master-arm updated (c31b8d9e7 -> 5e8c7fa77)

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 c31b8d9e7 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/gd [...] discards 4cd7bf5ca 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 commits discards 4ba699fbd 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qemu [...] discards 594804c97 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/gl [...] discards 93270e9ad 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 commits discards f69070503 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: 1 [...] discards 99a39ccfc 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/gd [...] discards 599d79951 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/gl [...] discards 97ef2d6e0 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/gd [...] discards 4481469d8 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 061c94002 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards e91710427 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards b24badc8e 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/gd [...] discards d8e67dbe6 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/gd [...] discards 447a1a85b 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] discards 8d87f960c 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 40aa13e15 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 774816839 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] discards d0d64d8fe 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards b3565d640 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] discards 68b6e1b8f 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] discards 16b3d9b6a 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 3eb985a02 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] discards 34876508f 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] discards d9cd804a7 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 151d5b8b2 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] discards 431dc89b4 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] discards b6b166c95 95: onsuccess: #1529: 7: Success after baseline build: no new [...] discards 67bd8fce1 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 5217168bf 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] discards bed3d15e2 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 0fc6e4c44 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 6fa1f5060 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards a8e6e1f8a 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 74ff28634 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards b5f46a8e9 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 7e325e73d 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 5f4abfecd 85: onsuccess: 7: Success after gcc: 9 commits discards 14d00af28 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 2e58bd434 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 8f72e7176 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 629786bcb 81: onsuccess: 7: Successful build after gcc: 2 commits discards 2f4d936c3 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards d1fbef398 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards a87aaa5ff 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 49fc63c77 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards c373bdc3b 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards d46176055 75: onsuccess: 7: Successful build after linux: 44 commits discards db28b8248 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 92df71b51 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 37320d3cb 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 0f02668d2 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards 2e4381b8e 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 69d6aa930 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards ee01a30a0 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards a8c689209 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 9ad670432 66: onsuccess: 7: Successful build after gcc: 3 commits discards 3e33994df 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 6aadb3925 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards da3a1d423 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards aa1bb901e 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 5cbc3da9f 61: onsuccess: 4: Successful build after gcc: 15 commits discards f18c3fa67 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards c0ad6e020 59: force: 7: Successful build after gcc: 2 commits discards 12d3d27a7 58: onsuccess: 7: Successful build after glibc: 2 commits discards 5b6b12166 57: onsuccess: 7: Successful build after gcc: 7 commits discards 4a4d1fd5c 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards fb6bab1e2 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 796756069 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 6621ce56d 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] discards f80683e9e 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards b4628c209 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 68e53cc0d 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 3baa528b9 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 7e701591a 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards aae9cea29 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 3f78b184d 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 2427951ff 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 799f1a80f 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards 7d41dc089 43: onsuccess: 7: Successful build after gcc: 2 commits discards a767e326c 42: onsuccess: 7: Successful build after baseline build: no n [...] discards 39da3bfb4 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 389c18975 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards cbd6dbb15 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits discards 76e8203fd 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards 475a719a8 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 447ed930a 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards d68bbc4da 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 911f77519 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 325af6fe9 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 3361656c5 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 5507c41a1 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards db22db8f2 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 7f34a4e93 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards c30f37b30 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards db22471fd 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 5ffbc9db0 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 9db8c80e2 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 5f271bfb7 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 314f1097e 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 39eb15450 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new ac09af813 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2c6c939d1 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 7265b8d7e 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5851cd388 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 225d1fcbc 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new aa5985aa0 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 68f5c05c1 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 82d42abc7 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 2d8f91733 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 7bfc1f74a 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 648f2f701 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new f81747f7d 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new c04c3831d 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new e274fa173 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 535e0e5c2 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 55cf2e6eb 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 6f9d84a6a 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new 703572dbc 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits new 73c578f7d 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new d8dbd2cc0 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 272c3b1ba 42: onsuccess: 7: Successful build after baseline build: no n [...] new 64bad5bd0 43: onsuccess: 7: Successful build after gcc: 2 commits new 75532b6ba 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new a71e364a4 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 056ee381c 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 1913bb8cf 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7bf131156 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 6bb1ea241 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new db25c112a 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 65a77ec24 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 7d3885fbf 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new a145fd369 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] new 69eda8d6d 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 2d4d49f6a 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new f9fad0ac0 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 0cd274855 57: onsuccess: 7: Successful build after gcc: 7 commits new eca38ca1e 58: onsuccess: 7: Successful build after glibc: 2 commits new a445c5174 59: force: 7: Successful build after gcc: 2 commits new cc267f41c 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new 342011460 61: onsuccess: 4: Successful build after gcc: 15 commits new 1c657e08d 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 2f3941a82 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new ea52b05a0 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 825e04bb8 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new b5916f3f8 66: onsuccess: 7: Successful build after gcc: 3 commits new e4fd571b6 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 94a48647a 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new af74fd920 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 8da4f0d04 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 73461b729 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new 28d9853ea 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 37b9adbe1 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new b41b206a2 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new faf262815 75: onsuccess: 7: Successful build after linux: 44 commits new 770ec00e6 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 2c9fc7d94 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new fb6fd79bd 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new a4180d90a 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new b72a0e0af 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new 9611ebeb9 81: onsuccess: 7: Successful build after gcc: 2 commits new c83db62bb 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new a865f02f6 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new f3350d011 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new f12f56882 85: onsuccess: 7: Success after gcc: 9 commits new 134bd3920 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new bfeae5946 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 3a56f1115 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 359fffacb 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 5481bd6ec 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 899922a0b 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new ebed77e5a 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 6a04a36e0 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] new 401108a42 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 7aaa3d243 95: onsuccess: #1529: 7: Success after baseline build: no new [...] new a503f80fe 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] new b1ca56d41 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] new cc97c9002 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new dd2ef7b30 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] new 5f275894e 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] new 6090bc9e0 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 0f4d9e84b 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] new 205a3efda 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] new bf99e1341 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new f633a7284 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] new 53c02de73 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 3d6400690 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 3f4cb1d0a 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] new 8f756dffd 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/gd [...] new b28c40b5e 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/gd [...] new efbe59256 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new f5d6d4a0a 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new adebe918f 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 30ad5734f 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/gd [...] new 47f26fc32 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/gl [...] new fca29f0e2 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/gd [...] new 3e32a723c 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: 1 [...] new 7939e7691 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 commits new f926b061d 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/gl [...] new f32f289c4 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qemu [...] new 059b428c1 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 commits new 01e47905e 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/gd [...] new 5e8c7fa77 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/gd [...] 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 (c31b8d9e7) \ 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 1680 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2748 bytes 04-build_abe-binutils/console.log.xz | Bin 29944 -> 30796 bytes 05-build_abe-stage1/console.log.xz | Bin 90896 -> 91700 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8528 -> 9240 bytes 08-build_abe-glibc/console.log.xz | Bin 233268 -> 234408 bytes 09-build_abe-stage2/console.log.xz | Bin 225024 -> 223808 bytes 10-build_abe-gdb/console.log.xz | Bin 37164 -> 38148 bytes 11-build_abe-qemu/console.log.xz | Bin 31392 -> 31096 bytes 12-check_regression/console.log.xz | Bin 3088 -> 3516 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 ++++++++++----------- 22 files changed, 62 insertions(+), 62 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_fx/gnu-master-aarch64-cpu2017rate-O3 created (now 44838b393)

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_fx/gnu-master-aarch64-cpu2017rate-O3 in repository toolchain/ci/base-artifacts. at 44838b393 0: init: #1: 1: [TCWG CI] No change after baseline build: no [...] This branch includes the following new commits: new 44838b393 0: init: #1: 1: [TCWG CI] No change after baseline build: no [...] 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. -- 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