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/release-arm updated (be0c450683 -> 7b19e369af)

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/release-arm in repository toolchain/ci/base-artifacts. from be0c450683 16: onsuccess: #175: 1: Success after binutils/gcc/linux/gdb [...] new 7b19e369af 17: onsuccess: #176: 1: Success after binutils/gcc/gdb/qemu: [...] 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 1740 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30492 -> 30040 bytes 04-build_abe-stage1/console.log.xz | Bin 88448 -> 86784 bytes 06-build_abe-linux/console.log.xz | Bin 8716 -> 8608 bytes 07-build_abe-glibc/console.log.xz | Bin 232168 -> 229364 bytes 08-build_abe-stage2/console.log.xz | Bin 223888 -> 220404 bytes 09-build_abe-gdb/console.log.xz | Bin 36648 -> 36844 bytes 10-build_abe-qemu/console.log.xz | Bin 31104 -> 30900 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2436 -> 2424 bytes 13-check_regression/console.log.xz | Bin 6520 -> 5772 bytes 13-check_regression/results.compare | 20 +- 13-check_regression/results.compare2 | 17 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- sumfiles/g++.log.xz | Bin 2651280 -> 2660488 bytes sumfiles/g++.sum | 38 +- sumfiles/gcc.log.xz | Bin 2218964 -> 2213664 bytes sumfiles/gcc.sum | 2076 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 875996 -> 881620 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 195928 -> 195964 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 420628 -> 429260 bytes sumfiles/libstdc++.sum | 2 +- 37 files changed, 1105 insertions(+), 1114 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (469012805b -> b95b39b4aa)

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 469012805b 137: onsuccess: #2061: 1: Success after binutils: 2 commits discards 86ba0736fb 136: onsuccess: #2056: 1: Success after binutils: 4 commits discards 4d8df0874e 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits discards f66809d64d 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits discards 178d277c3c 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits discards 97c15baadd 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits discards 65696f47aa 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] discards 8139be540f 130: onsuccess: #2049: 1: Success after gcc: 9 commits discards 79244cd80b 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] discards a863f8dffe 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] discards d652bcd19c 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] discards da27607ee5 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] discards 4cb07e0d4f 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits discards c654f8d9fc 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits discards e1063f6312 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits discards 0714d4bba0 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits discards 115b93c0d9 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits discards eb11cf9e75 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits discards 314842b524 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits discards 1e484daf1a 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits discards 7db4c105b4 117: onsuccess: #2034: 1: Success after binutils: 2 commits discards 228ee62866 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits discards b86b007755 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits discards 98d95fe772 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits discards 7e72888e20 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits discards 6b1d320ed6 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits discards b80045a0fb 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits discards 51f4e7e3a4 110: onsuccess: #2027: 1: Success after gcc: 5 commits discards 2e60b8256d 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits discards dc59ce5b9e 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits discards f862370ddf 107: onsuccess: #2024: 1: Success after gcc: 3 commits discards 3534010a91 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits discards 7879355ee5 105: onsuccess: #2022: 1: Success after gcc: 4 commits discards ac43801ce2 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards d1b07a04bf 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards 03fc6aaf55 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] discards 9c95e58acf 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards 2b07e794ec 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards 19b000104a 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards 8f83448282 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards 4ac4686b39 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards aed7b65b03 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] discards 4e31f390a1 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] discards 98ba27235d 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards 59984dff86 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] discards 0189321e4e 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards 6111dbb583 91: onsuccess: 1: Success after gcc: Daily bump. discards 35c0d49303 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards e7552b2848 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards 3e4a22b019 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards a488641c2b 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards f4b71a0183 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards 0ac27624c2 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards ef7889bc6b 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards b8adf01785 83: onsuccess: 1: Success after gcc: 8 commits discards 3d0390ca1d 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards e77b157de1 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards a1f959b8e9 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards 955c0a1b34 79: onsuccess: 1: Successful build after gcc: Daily bump. discards 8adf7edb8c 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 96115456a5 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards f83c5816b5 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards c255515d79 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 20eda2f3c1 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards dcdc70f177 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards 530d972a8a 72: onsuccess: 1: Successful build after gcc: 2 commits discards 3646b90b51 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 66f83f2649 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards ac0a214519 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 39efa65ff0 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards c887721344 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 2be08e794e 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 945841132d 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 22ac5046b9 64: onsuccess: 1: Successful build after gcc: 5 commits discards ce45221b2d 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 7a31226670 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards eb1c1f21c6 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits discards ba29b7ed7d 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards dfc44a851f 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits discards 24901196f8 58: onsuccess: 1: Successful build after binutils: 2 commits discards 8d939a50f9 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards 958c2a821d 56: onsuccess: 1: Successful build after gcc: Daily bump. discards 250b01504e 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards b3850d136b 54: onsuccess: 1: Successful build after gcc: 7 commits discards 7e31e5edd5 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 27e1c5b505 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards afc1ba3bba 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards b13a4feed5 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 560e01ca60 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 91dc08909d 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 84ccd69bb5 47: onsuccess: 1: Successful build after binutils: 2 commits discards b2777536fb 46: onsuccess: 1: Successful build after gcc: Daily bump. discards e3aaf08c1a 45: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards e8cc22ebfe 44: onsuccess: 1: Successful build after gcc: 2 commits discards 2b5678befa 43: onsuccess: 1: Successful build after gcc: Daily bump. discards 3450447342 42: onsuccess: 1: Successful build after binutils: Automatic [...] discards 3fccf44710 41: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 378c30690d 40: onsuccess: 1: Successful build after gcc: 2 commits discards 2bc3a94b66 39: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 2feb15f45b 38: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards a0adb788f6 37: onsuccess: 1: Successful build after binutils/gcc: 12 commits new ff9ec0e3bf 37: onsuccess: 1: Successful build after binutils/gcc: 12 commits new 4397b261a6 38: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 3d5d6815a4 39: onsuccess: 1: Successful build after binutils/gcc: 3 commits new f8fb42ffa0 40: onsuccess: 1: Successful build after gcc: 2 commits new ded9e7efb9 41: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 33c1638f22 42: onsuccess: 1: Successful build after binutils: Automatic [...] new 830ee0fd46 43: onsuccess: 1: Successful build after gcc: Daily bump. new 07335b90ac 44: onsuccess: 1: Successful build after gcc: 2 commits new 184809002d 45: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 6eaeed6e24 46: onsuccess: 1: Successful build after gcc: Daily bump. new fb84f97f91 47: onsuccess: 1: Successful build after binutils: 2 commits new 946a5abe67 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 7c16e301a1 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits new e7ad14e4e9 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 67d736bbbc 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits new fa04799493 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits new c14cfe871d 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new e74b4fb879 54: onsuccess: 1: Successful build after gcc: 7 commits new 997c82bcb6 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits new bc30e2d605 56: onsuccess: 1: Successful build after gcc: Daily bump. new 682ac22aaf 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits new d332d06731 58: onsuccess: 1: Successful build after binutils: 2 commits new 06d7d17813 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits new c4b62b94fa 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 1b0486dabd 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits new fa047d54cf 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 9d0377bad0 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 5fa87c8325 64: onsuccess: 1: Successful build after gcc: 5 commits new 245362e43d 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 65f371a84f 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new ca21567acf 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 7cf072c4a9 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 08d518e8a1 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 28c6f232a3 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new 012b37208f 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 06e3491452 72: onsuccess: 1: Successful build after gcc: 2 commits new 0af66f1838 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] new b263565b68 74: onsuccess: 1: Successful build after binutils: Automatic [...] new 213872c3ed 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 3a251008b9 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new fb58ebadc2 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new d3d2db5fae 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 95d885c911 79: onsuccess: 1: Successful build after gcc: Daily bump. new ce20fb87c1 80: onsuccess: 1: Success after binutils/gcc: 14 commits new 0340bbf3b4 81: onsuccess: 1: Success after binutils/gcc: 27 commits new d05879082e 82: onsuccess: 1: Success after binutils/gcc: 10 commits new 49885f43cc 83: onsuccess: 1: Success after gcc: 8 commits new 1347bfbeeb 84: onsuccess: 1: Success after binutils/gcc: 9 commits new 9ab001fca9 85: onsuccess: 1: Success after binutils/gcc: 9 commits new 5cb8b6be54 86: onsuccess: 1: Success after binutils/gcc: 13 commits new 0184d6812a 87: onsuccess: 1: Success after binutils/gcc: 4 commits new a7da1ddc7a 88: onsuccess: 1: Success after binutils/gcc: 16 commits new dccd4c320b 89: onsuccess: 1: Success after binutils/gcc: 9 commits new 229fe6ca2b 90: onsuccess: 1: Success after binutils/gcc: 6 commits new 9b151777a8 91: onsuccess: 1: Success after gcc: Daily bump. new 1406c153df 92: onsuccess: #1965: 1: Success after gcc: 2 commits new 6f1febde83 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] new b1089919d9 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new 832dd0c471 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] new 6ff60f5bc4 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] new c3fa51d246 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new e451d2acc4 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new d072794b16 99: onsuccess: #1974: 1: Success after gcc: 14 commits new b1c65817e6 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new 4d9059f057 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new 19da7c149d 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] new ab079a3ed7 103: onsuccess: #2020: 1: Success after gcc: 2 commits new 0c7a09b3b7 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new 8a97fa13cb 105: onsuccess: #2022: 1: Success after gcc: 4 commits new 7a8a9ae0b4 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits new ca94bffcc7 107: onsuccess: #2024: 1: Success after gcc: 3 commits new fd858f2814 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits new 5cefbb4895 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits new f66ba051a1 110: onsuccess: #2027: 1: Success after gcc: 5 commits new a77904992b 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits new 4fd7018c87 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits new b6c5adb253 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits new baacdd9295 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits new ccaf60a3a3 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits new 49a142df58 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits new 419db43d70 117: onsuccess: #2034: 1: Success after binutils: 2 commits new 921b2d930f 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits new 91585927ff 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits new d81201736c 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits new 2e58cccebd 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits new 2665317e7e 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits new b694cb4e04 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits new 710235e078 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits new f020b43c24 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits new 06df88da4c 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] new 0c8b4234bf 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] new c4d9d715ef 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] new 2aa6377e2c 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] new cc0ec03ff4 130: onsuccess: #2049: 1: Success after gcc: 9 commits new cc10636f22 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] new 20040b2d0d 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits new b3b9fd0728 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits new 9a20396299 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits new 9cc5f197f5 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits new e87c5dbae5 136: onsuccess: #2056: 1: Success after binutils: 4 commits new 56e1f87e72 137: onsuccess: #2061: 1: Success after binutils: 2 commits new b95b39b4aa 138: onsuccess: #2064: 1: Success after binutils: 4 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 (469012805b) \ 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 1716 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 37652 -> 38832 bytes 04-build_abe-gcc/console.log.xz | Bin 213312 -> 216008 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3952 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2956 -> 2940 bytes 07-check_regression/console.log.xz | Bin 4256 -> 4324 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 6 +- 08-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- sumfiles/g++.log.xz | Bin 3572748 -> 3575060 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 3095832 -> 3102728 bytes sumfiles/gcc.sum | 5306 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1045220 -> 1042264 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2192 -> 2192 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 206820 -> 206944 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 442436 -> 446936 bytes sumfiles/libstdc++.sum | 10 +- 30 files changed, 2817 insertions(+), 2817 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_tk1/gnu-master-arm-spec2k6-O3 updated (0f7047dc80 -> 598972bb47)

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_tk1/gnu-master-arm-spec2k6-O3 in repository toolchain/ci/base-artifacts. from 0f7047dc80 4: force: #457: 1: [TCWG CI] 447.dealII failed to build afte [...] new 598972bb47 5: force: #458: 1: [TCWG CI] 471.omnetpp slowed down by 7% a [...] 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 1648 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 31156 -> 31496 bytes 04-build_abe-stage1/console.log.xz | Bin 93348 -> 94140 bytes 06-build_abe-linux/console.log.xz | Bin 8692 -> 8756 bytes 07-build_abe-glibc/console.log.xz | Bin 235980 -> 236024 bytes 08-build_abe-stage2/console.log.xz | Bin 220232 -> 220100 bytes 09-benchmark/benchmark-build.log | 110 +- 09-benchmark/benchmark.log | 108 +- 09-benchmark/console.log.xz | Bin 3820 -> 3824 bytes 10-check_regression/console.log.xz | Bin 15380 -> 15508 bytes 10-check_regression/csv-results-0/md5sum.csv | 2759 +- 10-check_regression/csv-results-0/perf.csv | 3204 +- 10-check_regression/csv-results-0/results.csv | 40094 +- 10-check_regression/csv-results-0/size.csv | 433481 +++++++++--------- 10-check_regression/csv-results-0/vect.csv | 320 +- 10-check_regression/csv-results-1/md5sum.csv | 2547 +- 10-check_regression/csv-results-1/perf.csv | 3116 +- 10-check_regression/csv-results-1/results.csv | 22088 +- 10-check_regression/csv-results-1/size.csv | 313097 +++++++------ 10-check_regression/csv-results-1/vect.csv | 390 +- 10-check_regression/exe.improvement | 1 - 10-check_regression/exe.regression | 3 +- 10-check_regression/extra-bisect-params | 2 +- 10-check_regression/jira-body.txt | 5 +- 10-check_regression/mail-body.txt | 5 +- 10-check_regression/mail-subject.txt | 2 +- 10-check_regression/results-brief.csv | 68 +- 10-check_regression/results-compare.csv | 12 +- 10-check_regression/results-full.csv | 3256 +- 10-check_regression/results-internal.csv | 239 +- 10-check_regression/results.csv | 239 +- 10-check_regression/results.log | 1545 +- 10-check_regression/results.regressions | 7 +- 10-check_regression/trigger-bisect | 4 +- 10-check_regression/trigger-notify | 0 11-update_baseline/console.log | 8 +- 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 | 4 +- 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 | 4 +- 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 | 4 +- .../squad/436.cactusADM/results-metadata.json | 10 +- dashboard/squad/436.cactusADM/results-metrics.json | 4 +- 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/450.soplex/results-metadata.json | 10 +- dashboard/squad/450.soplex/results-metrics.json | 4 +- dashboard/squad/453.povray/results-metadata.json | 10 +- dashboard/squad/453.povray/results-metrics.json | 4 +- dashboard/squad/454.calculix/results-metadata.json | 10 +- dashboard/squad/454.calculix/results-metrics.json | 4 +- 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 | 4 +- dashboard/squad/459.GemsFDTD/results-metadata.json | 10 +- dashboard/squad/459.GemsFDTD/results-metrics.json | 4 +- .../squad/462.libquantum/results-metadata.json | 10 +- .../squad/462.libquantum/results-metrics.json | 4 +- dashboard/squad/464.h264ref/results-metadata.json | 10 +- dashboard/squad/464.h264ref/results-metrics.json | 4 +- dashboard/squad/465.tonto/results-metadata.json | 10 +- dashboard/squad/465.tonto/results-metrics.json | 4 +- 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 | 4 +- 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 | 4 +- dashboard/squad/482.sphinx3/results-metadata.json | 10 +- dashboard/squad/482.sphinx3/results-metrics.json | 4 +- .../squad/483.xalancbmk/results-metadata.json | 10 +- dashboard/squad/483.xalancbmk/results-metrics.json | 4 +- dashboard/squad/dashboard-push-squad.sh | 122 +- dashboard/squad/summary-annotation.txt | 2 +- git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 190 + jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 16 +- mail/mail-body.txt | 16 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 7 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 2898736 -> 2906044 bytes save-temps/401.bzip2.tar.xz | Bin 298700 -> 298756 bytes save-temps/403.gcc.tar.xz | Bin 7562316 -> 7548352 bytes save-temps/410.bwaves.tar.xz | Bin 53392 -> 53300 bytes save-temps/416.gamess.tar.xz | Bin 16704928 -> 16683772 bytes save-temps/429.mcf.tar.xz | Bin 71388 -> 71380 bytes save-temps/433.milc.tar.xz | Bin 366684 -> 366812 bytes save-temps/434.zeusmp.tar.xz | Bin 544092 -> 543344 bytes save-temps/435.gromacs.tar.xz | Bin 2320868 -> 2320084 bytes save-temps/436.cactusADM.tar.xz | Bin 1746468 -> 1746452 bytes save-temps/437.leslie3d.tar.xz | Bin 175476 -> 175536 bytes save-temps/444.namd.tar.xz | Bin 492608 -> 493860 bytes save-temps/445.gobmk.tar.xz | Bin 2691360 -> 2706796 bytes save-temps/450.soplex.tar.xz | Bin 1379124 -> 1396856 bytes save-temps/453.povray.tar.xz | Bin 2559204 -> 2560620 bytes save-temps/454.calculix.tar.xz | Bin 3502672 -> 3515664 bytes save-temps/456.hmmer.tar.xz | Bin 986524 -> 984028 bytes save-temps/458.sjeng.tar.xz | Bin 319748 -> 320220 bytes save-temps/459.GemsFDTD.tar.xz | Bin 635548 -> 634888 bytes save-temps/462.libquantum.tar.xz | Bin 116480 -> 116348 bytes save-temps/464.h264ref.tar.xz | Bin 3108264 -> 3076924 bytes save-temps/465.tonto.tar.xz | Bin 8094320 -> 8105468 bytes save-temps/470.lbm.tar.xz | Bin 53428 -> 53444 bytes save-temps/471.omnetpp.tar.xz | Bin 1511108 -> 1488900 bytes save-temps/473.astar.tar.xz | Bin 156656 -> 157284 bytes save-temps/481.wrf.tar.xz | Bin 9098596 -> 9079956 bytes save-temps/482.sphinx3.tar.xz | Bin 586332 -> 585532 bytes save-temps/483.xalancbmk.tar.xz | Bin 16926728 -> 17126636 bytes 137 files changed, 411537 insertions(+), 415941 deletions(-) delete mode 100644 10-check_regression/exe.improvement create mode 100644 10-check_regression/trigger-notify create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (36be2d1102 -> 95ac522823)

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 36be2d1102 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards f222b8ce57 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards 105572d308 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 0eca00a7ab 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards 57fe99b3a4 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards 2ff1f6fca3 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards d40a36392d 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards 6244963ef8 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards fde143ef9f 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 6cfa2ff767 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards a5786ae1a6 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards 95b12a665f 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 44a725720f 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 97cfed9f24 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards c887a65f5c 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 6b3507f7f3 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards a99d657452 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards 7d3bbe45c2 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards dfee7b845a 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards d775aa1356 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards dc3d277640 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 07cae833d0 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards e24f5f31c2 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 406c302489 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards adc81d871b 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards c0574a9f29 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards f094af8316 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards 39ceec173f 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards d4a1da4dc6 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 0e063eb2ae 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 699510e6f3 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 8e4b731bf6 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 56754b6bbe 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 92cb56cf32 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 33faf9c5b0 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards bab7032ae3 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards 43ad8888c6 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards f228f62b5f 102: force: #1551: 1: Failure after gcc: 306 commits discards 1aca1de445 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 4d42a2971d 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards d29b24b970 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 2baa428850 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards ea7b4ea49a 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 6894733d36 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 21e378ccc6 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards b46af41e13 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards e5acd52e3c 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 1e231c01e2 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 2acd8eeec6 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 46d7c30844 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards c021e312d5 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards d6c5633b38 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards e741182df7 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 384fc06ab1 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 0e219d26e5 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 954259dbae 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards fefa17a51a 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards de644bfa88 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards ef20f09b1c 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f173e97cd0 80: onsuccess: 7: Successful build after linux: 44 commits discards 00388e0f0b 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards f96d338a81 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards b35065da15 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c8f2af03bc 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 97b180e1d5 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 1cf7376d5c 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards d617f833ef 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 2787c2709d 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 05c2f06642 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards d03b0568cf 70: onsuccess: 7: Successful build after gcc: 4 commits discards d84cac4b1a 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 61f66b285e 68: onsuccess: 7: Successful build after linux: 6 commits discards 8477d8787e 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards 49fda9778e 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards ed6ddac84d 65: onsuccess: 7: Successful build after binutils: 3 commits discards c3132710b3 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 52e0965b82 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 7d65b60f26 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 483fb759e2 61: onsuccess: 4: Successful build after gcc: 5 commits discards 150cd7e51a 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 0f60806092 59: force: 7: Successful build after gcc: 3 commits discards 653d8911d3 58: onsuccess: 7: Successful build after glibc: 2 commits discards d50fced84b 57: onsuccess: 7: Successful build after gcc: 7 commits discards 99fb467e91 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 604c7bcd10 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 1b58f92667 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards b0340f850d 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 93858e5907 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] discards 9596818c73 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards f119c58867 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a7e78d1ff3 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 04a5bfc8ad 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 3cc1b58a73 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards afedc651f9 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 65c1be3200 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6e6ab568b5 44: onsuccess: 7: Successful build after linux: 34 commits discards 0d10a0658e 43: onsuccess: 7: Successful build after gcc: 2 commits discards 6d4d67e1d9 42: onsuccess: 7: Successful build after baseline build: no [...] discards 80f0919bc7 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5f9c5fcb3f 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a6716b6105 39: onsuccess: 7: Successful build after gcc: 2 commits new d718a41f4e 39: onsuccess: 7: Successful build after gcc: 2 commits new 4836a5e715 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7b54a011c1 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 776128bd84 42: onsuccess: 7: Successful build after baseline build: no [...] new c85faeda2a 43: onsuccess: 7: Successful build after gcc: 2 commits new 691d0367b3 44: onsuccess: 7: Successful build after linux: 34 commits new 526858087f 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4f01d98eff 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 5e064bfa10 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 142e89f369 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new a373594beb 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 90817053df 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new dbf0adec6f 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 630211012e 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new 9320a7cbe8 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new f57e2dba07 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 0f8b2e88c9 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 0de8b69026 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new aa69268649 57: onsuccess: 7: Successful build after gcc: 7 commits new 45631c9a5c 58: onsuccess: 7: Successful build after glibc: 2 commits new f67b04bdce 59: force: 7: Successful build after gcc: 3 commits new 6f8e201028 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 9e32740f92 61: onsuccess: 4: Successful build after gcc: 5 commits new c44f34cbc9 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new b9f97a83e9 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new da86973e4f 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 77dcb3e724 65: onsuccess: 7: Successful build after binutils: 3 commits new 17357b7d4a 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 2e26e88fb1 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new 3a55c0f5c7 68: onsuccess: 7: Successful build after linux: 6 commits new 82df6c8a50 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new aafd2e6e71 70: onsuccess: 7: Successful build after gcc: 4 commits new 7c628bcfa9 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 571cbc1150 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new de1812d592 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 31adf0594f 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 892d36360e 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 9083f88a8c 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 5e02c25390 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7f35dd0000 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new 1b2dc99010 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 35575f17c6 80: onsuccess: 7: Successful build after linux: 44 commits new 09524e4a66 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new eabf91a90a 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new eb7e6ba347 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7cf4d8a67b 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 4d911a3122 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new a277443936 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 72d527effa 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new b9c0a939aa 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new bbd4d99f2f 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 291cf7d977 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new a021b916e2 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new c230b401ee 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 501aa0ac91 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 6ecc160acb 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 537f48bdfc 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new ae27499a81 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 500addf91a 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 1c1891a83d 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 447a1c2cd5 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 6a71565d3e 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 438036b42f 101: onsuccess: #1547: 7: Success after binutils: 82 commits new cdb490762b 102: force: #1551: 1: Failure after gcc: 306 commits new 25e6cfdda6 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 72f63e0d37 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new e94c934fda 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new b68570af5f 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 794a49a021 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new 328de3bb2e 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new fe37402a3c 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 372885c957 110: onsuccess: #1559: 7: Success after gcc: 4 commits new c9880b8ca4 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new f7317a612d 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 4bcc78bd66 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new 5c513f3b60 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new ababe594ed 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 6241ead3c3 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 604fb6157c 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 1c24418c32 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new 35ff898901 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new 51b7799726 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new a7aa59e5ac 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 7e40136ba8 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 061fc5109f 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new 19e5b30c9e 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new ebd9a04652 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 9dff3b1ae2 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 3fe2928ae3 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new df13045644 128: onsuccess: #1579: 7: Success after linux: 12 commits new d7e964595a 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new c3acea2ed5 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 7ee7e48616 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new 945c2442b7 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 39d7be7d6b 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new cfb91af089 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new e274db665c 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new 2bae18dfc9 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new 2c431b6916 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 163b46979e 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new 7134c0dc2e 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 95ac522823 140: onsuccess: #1591: 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 (36be2d1102) \ 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 1724 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30236 -> 30680 bytes 05-build_abe-stage1/console.log.xz | Bin 72580 -> 72176 bytes 07-build_abe-linux/console.log.xz | Bin 9260 -> 9236 bytes 08-build_abe-glibc/console.log.xz | Bin 240788 -> 239444 bytes 09-build_abe-stage2/console.log.xz | Bin 204828 -> 202076 bytes 10-build_abe-gdb/console.log.xz | Bin 37660 -> 37916 bytes 11-build_abe-qemu/console.log.xz | Bin 32008 -> 31388 bytes 12-check_regression/console.log.xz | Bin 4548 -> 3376 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ 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 | 34 +++++++++--------- 19 files changed, 57 insertions(+), 57 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/interesting-commits] branch master updated (0602282 -> 9236a78)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from 0602282 Add entry e07ead85a368173a56e96a21d6841aa497ad80f8 from https [...] new 9236a78 Add entry 7f04b0d786e13ff5c1bd952a24fd324224415c9a from https [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/basepoints/gcc-13-322-g7f04b0d786e | 1 + .../gnu-master-arm-spec2k6-O3/build_url | 1 + .../gnu-master-arm-spec2k6-O3/last_good | 1 + .../gnu-master-arm-spec2k6-O3/summary.txt | 8 +++++ .../tcwg_bmk_gnu_tk1/status.txt | 36 ++++++++++++++++++++++ 5 files changed, 47 insertions(+) create mode 120000 gcc/basepoints/gcc-13-322-g7f04b0d786e create mode 100644 gcc/sha1/7f04b0d786e13ff5c1bd952a24fd324224415c9a/tcwg_bmk_gnu_ [...] create mode 100644 gcc/sha1/7f04b0d786e13ff5c1bd952a24fd324224415c9a/tcwg_bmk_gnu_ [...] create mode 100644 gcc/sha1/7f04b0d786e13ff5c1bd952a24fd324224415c9a/tcwg_bmk_gnu_ [...] create mode 100644 gcc/sha1/7f04b0d786e13ff5c1bd952a24fd324224415c9a/tcwg_bmk_gnu_ [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/master-arm-check_bootstrap updated (0f9b7c9c04 -> 54ebc287c7)

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_bootstrap/master-arm-check_bootstrap in repository toolchain/ci/base-artifacts. from 0f9b7c9c04 45: onsuccess: #555: 1: Success after binutils: 13 commits new 54ebc287c7 46: onsuccess: #558: 1: Success after binutils: 7 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 1748 -> 1656 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 52020 -> 52412 bytes 04-build_abe-bootstrap/console.log.xz | Bin 463484 -> 465156 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3808 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2720 -> 2620 bytes 07-check_regression/console.log.xz | Bin 4496 -> 4444 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 6 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- sumfiles/g++.log.xz | Bin 2822272 -> 2869920 bytes sumfiles/g++.sum | 128 +- sumfiles/gcc.log.xz | Bin 2523500 -> 2462108 bytes sumfiles/gcc.sum | 4706 +++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 954604 -> 944680 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2304 -> 2316 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 211944 -> 210972 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2728 -> 2728 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 477080 -> 475496 bytes sumfiles/libstdc++.sum | 10 +- 29 files changed, 2479 insertions(+), 2479 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (a25982ada52 -> fa4bc21bac7)

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 a25982ada52 stack-protector: Check stack canary before throwing exception new fa4bc21bac7 LoongArch: Libitm add LoongArch support. 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: libitm/config/{sh/target.h => loongarch/asm.h} | 51 +++++----- libitm/config/loongarch/sjlj.S | 127 +++++++++++++++++++++++++ libitm/config/{aarch64 => loongarch}/target.h | 29 +++--- libitm/configure.tgt | 2 + 4 files changed, 175 insertions(+), 34 deletions(-) copy libitm/config/{sh/target.h => loongarch/asm.h} (58%) create mode 100644 libitm/config/loongarch/sjlj.S copy libitm/config/{aarch64 => loongarch}/target.h (68%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (60d0ea4eb3 -> 2f0bd18e1b)

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-aarch64 in repository toolchain/ci/base-artifacts. discards 60d0ea4eb3 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 5e4136c6f8 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 01fb2b1d63 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 38f8e1bcf5 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 8838883943 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards b1d8afa74d 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 37862fc0be 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards cee5f9f500 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 608f1e86b8 128: onsuccess: #2163: 1: Success after linux: 23 commits discards d68a5e4ae7 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards b1a551287e 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards dd8ea9eaa5 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 8df7ee5828 124: onsuccess: #2159: 1: Success after linux: 23 commits discards d2c1352c17 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards e841245aa5 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards d6ddff5fd8 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 0188e2b155 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 8dd0b6f83d 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 1c7a14beaf 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 724b863077 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards d3ada16de5 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards e34343872a 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards b9fa0b5aa7 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards d5fa55596c 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards bf2f166684 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards df6ec97f7e 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 7c70835d1b 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 0ceb9392aa 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 17597255fa 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 48131d5b71 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards a8b5a096ce 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 4cd4574444 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards e574656042 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 5f2b8c6f4d 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards c8dc08ffb2 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 62e166ec2f 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards be223602e1 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards fe0b812c6c 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 856f822255 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards c306e01759 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards a044f01739 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 811e731bed 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards d77cc9e653 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards b23728a5ec 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards a2b03adc22 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards f04e9ad027 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 4f765e7320 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 7a50c29e17 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 89ba3bc252 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 861b1557f0 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards fe06b51432 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 095aaa3120 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 132fcaf7bf 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 8a5abc7bb2 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 6929afa859 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 14a4aea679 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 181bb00769 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 16b63c9612 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f7d5302c38 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards af6bc4187a 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 348cc62231 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7918aa952c 75: onsuccess: 1: Successful build after linux: 44 commits discards 1089286317 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 9a1fa3a474 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fac779b736 72: onsuccess: 1: Successful build after linux: 12 commits discards d7a0eef58a 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 544f2dd42b 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 7437d13e98 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards edf1568939 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5b3f891c66 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 2124b8a34c 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 72c434a7c7 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dc4a60c45a 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7ab5a32133 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 2323668a7a 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 3b4e7cb816 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 6f9fdae999 60: onsuccess: 1: Successful build after glibc: 2 commits discards a08d5a3410 59: onsuccess: 1: Successful build after binutils: 2 commits discards a352478c19 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards af71982b06 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 1bad3543fe 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e4cce4407a 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 1ba4bdb4de 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards ff88439f3d 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards c8ff032367 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 28917aefd5 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1698216bff 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 37dd956bcb 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards a1c54c3027 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c67a1505b4 47: onsuccess: 1: Successful build after linux: 10 commits discards 78505351b2 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 4ea96c58ea 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5d91dffb26 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards fd9487b6a5 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards e0ca7ea642 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards e1b8dafe35 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3efe71a581 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards e8d5e597e6 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 7eb3ed195f 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 61163f5fbc 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 360dc629de 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3e37a22980 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3b5b1c694d 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d1e5082f3e 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 2ebd895110 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new dc1c5f71e8 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new 905dab919f 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e33353919f 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new 2b8a9824b5 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new c0584a6d25 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new b1cedfa74f 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new db2045bab5 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new b23d37cabc 47: onsuccess: 1: Successful build after linux: 10 commits new 355e80ddce 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 69f4c9fee6 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 00e115a90b 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c67538186c 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 737cacc5db 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 5c0e1b23a6 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 34e9c6334c 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new fb7c59c594 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 7dcb990e0b 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 304e45e116 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3063411a8f 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 149a1bd6c2 59: onsuccess: 1: Successful build after binutils: 2 commits new 38773ab7f1 60: onsuccess: 1: Successful build after glibc: 2 commits new a83b909ea0 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 8902d4b641 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new ee7212cc8b 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 246f2271bb 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fa3b9875a1 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0971c22445 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 2defc4f52b 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 5437f60966 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 58152d6f55 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 66ba17fca3 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 92a8fc131d 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new ced95d6a6d 72: onsuccess: 1: Successful build after linux: 12 commits new edb37700aa 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ebffd26bbc 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 2e60696a39 75: onsuccess: 1: Successful build after linux: 44 commits new 422d9d0c88 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b77cfdf676 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new a74b2b5dd6 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new e8f90de37f 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new cfa89370c6 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 741690bbbf 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 429daf61e4 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 3b66b510d7 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new d77d3e5681 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new fd5e25d1ff 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 5f637c54ab 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 93b0b44894 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 6ec8c04193 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new aa20f029f9 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 76d89e2b35 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 1586fb541e 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new bf3b12a629 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 0451cee8b6 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new dc81c01cc7 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new db94162dea 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 3fdd26d597 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new c2b14e1cd6 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 38309e3532 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 9babc9f047 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 97c55c1d6e 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 2c6dcea025 101: onsuccess: #2130: 1: Success after binutils: 81 commits new d104287f34 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 03ad8aa2a3 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 1c22c546ef 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 1840d3046e 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 0b9accb707 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 1570cea9be 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 8a2f71d470 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 9f462eb928 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 4227199e40 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 315c867586 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 552125c96e 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 8b04c2f958 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 4a3d1e73ed 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 0e4bc6e2e5 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 0c58ed3a7a 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new d3df47627d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 23b1e57a5b 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new eb74488074 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new ac77ae8536 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 35752a1e98 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new aae75b6762 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 0a38f85998 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 847b1b3b72 124: onsuccess: #2159: 1: Success after linux: 23 commits new 7147463366 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 5182944ab0 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new e7d4ada082 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 41ae789b0b 128: onsuccess: #2163: 1: Success after linux: 23 commits new 04df5792c5 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 2cebd6532c 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 769a1b591a 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new ef31bb73d4 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new af5bed7004 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 01c495d8d0 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new bb0b67ae11 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 85b09476ae 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 2f0bd18e1b 137: onsuccess: #2172: 1: 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 (60d0ea4eb3) \ 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 1720 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30472 -> 30520 bytes 04-build_abe-stage1/console.log.xz | Bin 72832 -> 72676 bytes 06-build_abe-linux/console.log.xz | Bin 8632 -> 9268 bytes 07-build_abe-glibc/console.log.xz | Bin 240280 -> 240244 bytes 08-build_abe-stage2/console.log.xz | Bin 203276 -> 204836 bytes 09-build_abe-gdb/console.log.xz | Bin 37800 -> 37732 bytes 10-build_abe-qemu/console.log.xz | Bin 31300 -> 31532 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3900 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2660 -> 2620 bytes 13-check_regression/console.log.xz | Bin 72748 -> 12988 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 176 +- 13-check_regression/mail-body.txt | 180 +- 13-check_regression/results.compare | 298 +- 13-check_regression/results.compare2 | 16321 +++--------------------------- 13-check_regression/results.regressions | 134 +- 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 182 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 134 +- sumfiles/g++.log.xz | Bin 3420960 -> 3443752 bytes sumfiles/g++.sum | 188 +- sumfiles/gcc.log.xz | Bin 3031424 -> 3015508 bytes sumfiles/gcc.sum | 5705 +++++------ sumfiles/gfortran.log.xz | Bin 1035640 -> 1034636 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202548 -> 202032 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 420032 -> 414524 bytes sumfiles/libstdc++.sum | 8 +- 44 files changed, 4775 insertions(+), 18681 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled updated (13e45eb4fb -> 60ab1cdc93)

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_profiled in repository toolchain/ci/base-artifacts. from 13e45eb4fb 46: onsuccess: #439: 2: Success after binutils/gcc: 46 commits new 60ab1cdc93 47: onsuccess: #441: 2: Success after binutils: 8 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 1680 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 38264 -> 37880 bytes 05-build_abe-bootstrap_profiled/console.log.xz | Bin 514624 -> 511468 bytes 06-check_regression/console.log.xz | Bin 3200 -> 2788 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 19 +++++++++---------- 11 files changed, 14 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-allmodconfig updated (ec03d968e4 -> 8fe2e1aa43)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-allmodconfig in repository toolchain/ci/base-artifacts. from ec03d968e4 23: onsuccess: #491: 21887: Success after binutils: 43 commits new 8fe2e1aa43 24: onsuccess: #493: 21887: Success after qemu: 5 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 1660 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30148 -> 29788 bytes 04-build_kernel_llvm/console.log.xz | Bin 63548 -> 63748 bytes 05-build_abe-qemu/console.log.xz | Bin 32100 -> 31008 bytes 06-build_linux/console.log.xz | Bin 4632 -> 4648 bytes 08-check_regression/console.log.xz | Bin 2924 -> 2992 bytes dashboard/dashboard-generate.sh | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 13 files changed, 15 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022