Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (49f1387d6b -> 92620f09a7)

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 49f1387d6b 156: onsuccess: #2091: 1: Success after binutils/gcc: 2 commits discards b0f9a4c6d4 155: onsuccess: #2090: 1: Success after binutils/gcc: 22 commits discards 42841d2c3a 154: onsuccess: #2089: 1: Success after gcc: 4 commits discards d9d8f4ba4d 153: onsuccess: #2088: 1: Success after basepoints/gcc-13-30 [...] discards 2c039ea4c0 152: onsuccess: #2087: 1: Success after gdb-12-branchpoint-2 [...] discards f03d56bee0 151: onsuccess: #2086: 1: Success after gcc: 2 commits discards d2616e1326 150: onsuccess: #2085: 1: Success after gcc: 2 commits discards 19e05edd28 149: onsuccess: #2084: 1: Success after gcc: 16 commits discards f003a8a2a8 148: onsuccess: #2082: 1: Success after gdb-12-branchpoint-2 [...] discards 4db61b77da 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 commits discards 5ea5496933 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits discards 652ad6ff38 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits discards 71763c54bf 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits discards b8e9c5bc1f 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits discards e56414ea0c 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits discards a6f10f745a 141: onsuccess: #2073: 1: Success after binutils: 3 commits discards 47371215d8 140: onsuccess: #2070: 1: Success after binutils: 4 commits discards 5b4e3dceca 139: onsuccess: #2067: 1: Success after binutils: 2 commits discards ed97a198db 138: onsuccess: #2064: 1: Success after binutils: 4 commits discards 5555dc3b96 137: onsuccess: #2061: 1: Success after binutils: 2 commits discards 9b56473ca6 136: onsuccess: #2056: 1: Success after binutils: 4 commits discards d91ce5acda 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits discards c3a04eed5e 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits discards 3839e230c4 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits discards cf22d63b90 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits discards 2bf793e3b2 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] discards b8c88a0f02 130: onsuccess: #2049: 1: Success after gcc: 9 commits discards d2c264bdc7 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] discards 3432c7bdb9 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] discards e8ca1d42be 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] discards 586bb4dbad 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] discards 665fc3fe97 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits discards e35ce25684 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits discards 5be28be4a0 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits discards d81736c515 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits discards e888a8297e 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits discards 40243649a4 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits discards b2e87c8770 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits discards 93b1e22ae1 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits discards 3363d7cfb1 117: onsuccess: #2034: 1: Success after binutils: 2 commits discards 2dad60c5c6 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits discards 8769ec713b 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits discards 26a7021e32 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits discards 0d121d5529 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits discards f510853ca3 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits discards 6ba1a87f58 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits discards 4ec007d7bd 110: onsuccess: #2027: 1: Success after gcc: 5 commits discards 728fe2a627 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits discards 3940005b01 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits discards 9506021c31 107: onsuccess: #2024: 1: Success after gcc: 3 commits discards 3f3231e216 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits discards 3defe3f2f7 105: onsuccess: #2022: 1: Success after gcc: 4 commits discards b30b5ed017 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards d26d070186 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards b6b307f1d5 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] discards 0b3e0effbe 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards f8c9783129 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards a5d8027c61 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards ca655b1485 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards 6bdd7b4c42 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards 1b8f7221a3 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] discards b192889dfa 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] discards 3a733f132f 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards 01e026a65e 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] discards 5f5f527473 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards f295cae7c7 91: onsuccess: 1: Success after gcc: Daily bump. discards 8f55bf73d5 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards 98f3cc0dd5 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards 0e27c2867f 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards 6f1c5ad227 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards fc74099b10 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards 77e97cb500 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards 95d0881019 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards 55dd36a9df 83: onsuccess: 1: Success after gcc: 8 commits discards c39c3c4304 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards 8a06054d14 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards f01f020bd8 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards 513e6b6bd4 79: onsuccess: 1: Successful build after gcc: Daily bump. discards c4d51b63e5 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 06391cff3f 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 6ffdb5ebab 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 9438f72017 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 6933891453 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards 2ce97bb98b 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards 1d39405eab 72: onsuccess: 1: Successful build after gcc: 2 commits discards 3df210dd60 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards e8e4dda280 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards 5fe5545d30 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards ee72851462 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 1bc90e0992 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards a2c4998505 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards c98d7abe61 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 0afe30f4b6 64: onsuccess: 1: Successful build after gcc: 5 commits discards 7a8dcccfe8 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards a61ba9964b 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 157ea6825f 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits discards 6b3a5197ba 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 7935248a3a 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits discards cae6791d63 58: onsuccess: 1: Successful build after binutils: 2 commits discards 6c46e2bf18 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards 7a03db8de6 56: onsuccess: 1: Successful build after gcc: Daily bump. new f4b49c0d6f 56: onsuccess: 1: Successful build after gcc: Daily bump. new 760549801e 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits new eb078b9ed5 58: onsuccess: 1: Successful build after binutils: 2 commits new 24415b0d14 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits new b1f35369a1 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits new c131083a6e 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits new aa16ba0ea4 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits new f769c07d78 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 0dc8705c1c 64: onsuccess: 1: Successful build after gcc: 5 commits new 34c59047eb 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 02d7fd64ec 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 8f573274a5 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 79faf5360e 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new eb7cf3fb33 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 1d017365ef 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new 9091392f9a 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 2fd1bb9cda 72: onsuccess: 1: Successful build after gcc: 2 commits new a9380c84df 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 7b093b6378 74: onsuccess: 1: Successful build after binutils: Automatic [...] new 3f2b669ac3 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new eef2a3dcaf 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 9bd1d2cf80 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 9d86e20c5d 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new e9bc7cef71 79: onsuccess: 1: Successful build after gcc: Daily bump. new da56206a6b 80: onsuccess: 1: Success after binutils/gcc: 14 commits new 93187f5fcb 81: onsuccess: 1: Success after binutils/gcc: 27 commits new 26e6ff06d4 82: onsuccess: 1: Success after binutils/gcc: 10 commits new 5d58b96e90 83: onsuccess: 1: Success after gcc: 8 commits new faacf9faf3 84: onsuccess: 1: Success after binutils/gcc: 9 commits new e72722f38b 85: onsuccess: 1: Success after binutils/gcc: 9 commits new 70fac1b74c 86: onsuccess: 1: Success after binutils/gcc: 13 commits new abe3392865 87: onsuccess: 1: Success after binutils/gcc: 4 commits new 06e2d3b82e 88: onsuccess: 1: Success after binutils/gcc: 16 commits new 27b8ee4e36 89: onsuccess: 1: Success after binutils/gcc: 9 commits new 5423d3d5e5 90: onsuccess: 1: Success after binutils/gcc: 6 commits new e6464896b3 91: onsuccess: 1: Success after gcc: Daily bump. new 193deca291 92: onsuccess: #1965: 1: Success after gcc: 2 commits new b0b9e5838a 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] new 6bfe52c85d 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new bedbf4a11f 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] new 92a35cb387 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] new 2d19b0b583 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new bc2b0871da 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new 6e1915de01 99: onsuccess: #1974: 1: Success after gcc: 14 commits new e1d3d57652 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new 177a423b91 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new 6f8beab770 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] new 343f75742e 103: onsuccess: #2020: 1: Success after gcc: 2 commits new 8dfd91fa92 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new 5a9e0c2e8d 105: onsuccess: #2022: 1: Success after gcc: 4 commits new 95e60a7461 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits new 2f9e4dc82b 107: onsuccess: #2024: 1: Success after gcc: 3 commits new 3aa1d89207 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits new a8ab04ec6e 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits new 39d26fbdf3 110: onsuccess: #2027: 1: Success after gcc: 5 commits new 7d3fb164e7 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits new e740e59008 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits new 5ed74dc74a 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits new c91feb980a 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits new 9acda87fc3 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits new f33958f4c1 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits new c71373d6f4 117: onsuccess: #2034: 1: Success after binutils: 2 commits new 74d570b57c 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits new a12d23fd45 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits new 22579bc826 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits new 9c9f5fe08a 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits new b7fb2630f8 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits new f0edadb4a1 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits new adeae50e31 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits new 4076d97968 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits new 94cec3cdf2 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] new 12113676cb 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] new c848225f8c 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] new 6cc5a933da 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] new ac44eb9007 130: onsuccess: #2049: 1: Success after gcc: 9 commits new 9b1b9db56b 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] new c5512bc4d5 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits new db73f3da0a 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits new 6e4b2cfa2f 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits new c5d628db2e 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits new 0be55c129b 136: onsuccess: #2056: 1: Success after binutils: 4 commits new b156478a3b 137: onsuccess: #2061: 1: Success after binutils: 2 commits new 71cc64ff75 138: onsuccess: #2064: 1: Success after binutils: 4 commits new 6c1cf863da 139: onsuccess: #2067: 1: Success after binutils: 2 commits new 05a3701d95 140: onsuccess: #2070: 1: Success after binutils: 4 commits new a666748841 141: onsuccess: #2073: 1: Success after binutils: 3 commits new 04e382edd9 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits new c0ca22d9f6 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits new 9cab9e42ac 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits new 758758ba1c 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits new a87b89af4c 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits new 47ee7106ae 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 commits new 5c2ba26087 148: onsuccess: #2082: 1: Success after gdb-12-branchpoint-2 [...] new 4abd22af34 149: onsuccess: #2084: 1: Success after gcc: 16 commits new da595023ed 150: onsuccess: #2085: 1: Success after gcc: 2 commits new e6da4dbd6e 151: onsuccess: #2086: 1: Success after gcc: 2 commits new d39fa1f079 152: onsuccess: #2087: 1: Success after gdb-12-branchpoint-2 [...] new acafe28802 153: onsuccess: #2088: 1: Success after basepoints/gcc-13-30 [...] new 1f405f2da4 154: onsuccess: #2089: 1: Success after gcc: 4 commits new 262167dbcd 155: onsuccess: #2090: 1: Success after binutils/gcc: 22 commits new 135ec67af2 156: onsuccess: #2091: 1: Success after binutils/gcc: 2 commits new 92620f09a7 157: onsuccess: #2092: 1: Success after binutils/gcc: 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 (49f1387d6b) \ 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 1664 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2712 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 37480 -> 38984 bytes 04-build_abe-gcc/console.log.xz | Bin 213332 -> 214848 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3912 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2328 -> 2956 bytes 07-check_regression/console.log.xz | Bin 4368 -> 4480 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 6 +- 08-update_baseline/console.log | 42 +- 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 | 20 +- sumfiles/g++.log.xz | Bin 3570700 -> 3583096 bytes sumfiles/g++.sum | 118 +- sumfiles/gcc.log.xz | Bin 3085536 -> 3110200 bytes sumfiles/gcc.sum | 5382 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1043456 -> 1044908 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2188 -> 2184 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207260 -> 207540 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 447132 -> 450060 bytes sumfiles/libstdc++.sum | 10 +- 31 files changed, 2838 insertions(+), 2838 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-release-arm-stable-allmodconfig updated (a3ed2310cf -> 96498e9044)

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-stable-allmodconfig in repository toolchain/ci/base-artifacts. from a3ed2310cf 16: onsuccess: #260: 22763: Success after binutils/llvm/linu [...] new 96498e9044 17: onsuccess: #261: 22763: Success after binutils/llvm/linu [...] 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 1724 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30052 -> 29728 bytes 04-build_kernel_llvm/console.log.xz | Bin 64248 -> 64964 bytes 05-build_abe-qemu/console.log.xz | Bin 32544 -> 31388 bytes 06-build_linux/console.log.xz | Bin 4664 -> 4576 bytes 08-check_regression/console.log.xz | Bin 4344 -> 4344 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 | 32 ++++++++++++++++---------------- 16 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (4347fea9c28 -> 31d7c8bc263)

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 4347fea9c28 libstdc++: Fix gdb pretty printers when dealing with std::string new 31d7c8bc263 Fortran: fix testcases 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/testsuite/gfortran.dg/ieee/fma_1.f90 | 4 ---- gcc/testsuite/gfortran.dg/ieee/modes_1.f90 | 6 +++--- 2 files changed, 3 insertions(+), 7 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_gnu_cross_build/master-aarch64 updated (2569cec8bc -> 7a5cba4bfe)

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 2569cec8bc 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/g [...] discards 92fdca4930 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 40a3c90acb 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards 9f139dcee0 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] discards 26eb4ed769 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards 668548977f 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards bf6d8f9ca4 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] discards dba2d6f1e3 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards a9e4fa6e9a 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] discards 7903dea0d1 152: force: #1605: 7: Success after gcc: 9 commits discards 84f80cb704 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] discards 97b4c4b64d 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] discards 1031d607ed 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards a45ec68590 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards e029137264 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards c600c52c68 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards dcc0796546 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards fcda882e54 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 22676b3481 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards 2bf4d4e2a6 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards cebf98c761 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 65c0919e97 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards 60d90c5749 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards 0206132e59 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards 7754cba020 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 3420238807 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards 0b0cab4bcb 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards 805bae2b6c 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 36eafbf713 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards 546ea7e870 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards 8f693e6251 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards e01e8f69de 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 4919b7fc4d 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards 551a73f31e 128: onsuccess: #1579: 7: Success after linux: 12 commits discards dd6ac2b2a7 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 89bb0ceebf 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 04eff0dfc0 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 08536c162d 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 1a9a721147 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards 2f97529abe 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards e4af40a2e0 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards 95cca29c8c 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards be0a5a5d30 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards d7e4b73ade 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards 45c16e59f5 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 3f16a9f44a 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 88363b7f3e 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards 1671c2ab06 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards 862e681145 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards 63ab325d6c 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards 1ed7077eef 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 4d416d1aab 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards e3f33fd4a8 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 0c22ff2537 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards de4e97faba 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards fa37f0df71 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 6edbd49a2b 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards c0eef4895d 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards 5c360fc30a 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards b3526496bc 102: force: #1551: 1: Failure after gcc: 306 commits discards e4ddde1306 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards fcba73370b 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards a4c8ed2184 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards c764e3f4c5 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 74e3c019a2 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 7e468c3447 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 5f0ecd9498 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards c329db144f 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 7ef95d1ddc 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards a533e546ab 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 33b090a3ab 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 82bfddca9c 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 5692c179f0 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 36b246a30d 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 7effbd6536 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 9d8dd4d428 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 7c6a08e4e0 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards c09ede404f 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 7766f59472 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 31631f8c99 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards e91e6d7cfd 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 446d5f262a 80: onsuccess: 7: Successful build after linux: 44 commits discards 27be917cbc 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards fc7bf22373 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards 026c72758a 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f54bab375f 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 17af51ea3b 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards e909617504 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 31340586d4 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d0b6adccde 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a09f29de0c 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 2bfabaab8e 70: onsuccess: 7: Successful build after gcc: 4 commits discards 82b1c3116a 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e75bda3c0e 68: onsuccess: 7: Successful build after linux: 6 commits discards cbccbcbea2 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards eabd8fc759 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards c3bd17bf35 65: onsuccess: 7: Successful build after binutils: 3 commits discards 53ebfe58c8 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 6f200eca72 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 365308549e 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards ff4e9dbb4a 61: onsuccess: 4: Successful build after gcc: 5 commits new 2167b88295 61: onsuccess: 4: Successful build after gcc: 5 commits new 2819d1caff 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 7f969cfb58 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new c34c31dfaa 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 027b310ac0 65: onsuccess: 7: Successful build after binutils: 3 commits new cd34ddc3aa 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 140ed8aac1 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new cb33730cfa 68: onsuccess: 7: Successful build after linux: 6 commits new 95a0e7ef2a 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 46321c1245 70: onsuccess: 7: Successful build after gcc: 4 commits new 4ac553ad29 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new bd675c5b50 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new aa9def9dea 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 00c29dbb2c 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 129f67ea97 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 9e668ce861 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new c39054e3a2 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8422891d1f 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new 3861fbcc3a 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 6c9eb07418 80: onsuccess: 7: Successful build after linux: 44 commits new ffdef53379 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4d3b514afc 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new cd78b52454 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new da9210f170 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 39dea4a0ff 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 011c8bf7d5 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 74214679cc 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 1a9ae255b1 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new f08b3c8b35 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 147cb7fa1c 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 939c1c065e 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 2ff66c1746 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 9cab69657d 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new e7d4eeda29 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new b14fb5b49e 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new d0d89c289a 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 909037423e 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new a033d9a5f7 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new a26a253b08 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new bfb4458317 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new fd6fe55e68 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 49cec6e35e 102: force: #1551: 1: Failure after gcc: 306 commits new 7a25c90872 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 4dc1ec6533 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new c082fe2c0a 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new f289ffe7dc 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 6f3f61b2f9 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new ab697edbc1 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new 2c26eea556 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 717a15ef98 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 1f75d6912b 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new d4d4ef4fa8 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 6d01f75db4 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new b7464dd17d 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new f30f99bc14 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new d0e01bad2f 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 05563205e5 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new ddb283f868 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new e48bbf7d53 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new bfcd4427bb 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new eb31235770 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new ca28242a71 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 3ddce552e0 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new d5ad7c6dc8 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 014d311eaf 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 28390b5974 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 88d90bd61a 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new a84aae6935 128: onsuccess: #1579: 7: Success after linux: 12 commits new e8cb64a19c 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new 523091a862 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 23eae5a109 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new c65829e150 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 504817e7eb 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new 4ac7803a7a 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new a4be7379b9 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new 62149628e8 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new d6885e41aa 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 307c999730 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new 2d23bb7f7f 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 1faf284f73 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new f5dd0d34cc 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new 912b2a5fcf 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new 67e18d8499 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new d92bb00246 144: onsuccess: #1595: 7: Success after glibc: 2 commits new dbae15c79b 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new 79fe527a0c 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new 4d5d673e75 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new db846c16df 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new dfef8bc399 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new 46d8504251 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] new 1bfa62319e 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] new 796907be0a 152: force: #1605: 7: Success after gcc: 9 commits new ce05f00387 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] new 36d3360568 154: onsuccess: #1607: 1: Success after gcc: 2 commits new 1a200cddf0 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] new 151b91f446 156: onsuccess: #1609: 7: Success after gcc: 2 commits new 3cb7bd48df 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new c49bc70d58 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] new dc7c2fb25a 159: onsuccess: #1612: 7: Success after gcc: 4 commits new f4dcf81c1e 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 30552904e7 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/g [...] new 7a5cba4bfe 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 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 (2569cec8bc) \ 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 1676 -> 1636 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 30292 -> 30456 bytes 05-build_abe-stage1/console.log.xz | Bin 71840 -> 72592 bytes 07-build_abe-linux/console.log.xz | Bin 8272 -> 8268 bytes 08-build_abe-glibc/console.log.xz | Bin 239964 -> 239256 bytes 09-build_abe-stage2/console.log.xz | Bin 202344 -> 202872 bytes 10-build_abe-gdb/console.log.xz | Bin 37528 -> 37540 bytes 11-build_abe-qemu/console.log.xz | Bin 31836 -> 32244 bytes 12-check_regression/console.log.xz | Bin 3552 -> 3548 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ 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, 56 insertions(+), 56 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_bootstrap/master-arm-check_bootstrap updated (1b40799370 -> 81e1b7ff8f)

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 1b40799370 50: onsuccess: #565: 1: Success after binutils/gcc: 6 commits new 81e1b7ff8f 51: onsuccess: #566: 1: Success after binutils/gcc: 30 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 1724 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 53092 -> 50948 bytes 04-build_abe-bootstrap/console.log.xz | Bin 467836 -> 466020 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3808 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2352 -> 2424 bytes 07-check_regression/console.log.xz | Bin 5556 -> 5812 bytes 07-check_regression/fails.sum | 4 +- 07-check_regression/mail-body.txt | 64 +- 07-check_regression/results.compare | 32 +- 07-check_regression/results.compare2 | 67 +- 07-check_regression/results.regressions | 32 +- 08-update_baseline/console.log | 9 + dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 66 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 32 +- sumfiles/g++.log.xz | Bin 2838644 -> 2868944 bytes sumfiles/g++.sum | 128 +- sumfiles/gcc.log.xz | Bin 2495516 -> 2498728 bytes sumfiles/gcc.sum | 5002 +++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 953748 -> 951372 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2312 -> 2304 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 211444 -> 212036 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2728 -> 2724 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 473044 -> 479244 bytes sumfiles/libstdc++.sum | 10 +- 35 files changed, 2798 insertions(+), 2744 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-release-aarch64-mainline-allnoconfig updated (e4c75ab754 -> fda0d13942)

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-aarch64-mainline-allnoconfig in repository toolchain/ci/base-artifacts. from e4c75ab754 11: onsuccess: #429: boot: Success after binutils/llvm/linux [...] new fda0d13942 12: onsuccess: #430: 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 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30156 -> 30076 bytes 04-build_kernel_llvm/console.log.xz | Bin 65344 -> 65404 bytes 05-build_abe-qemu/console.log.xz | Bin 32392 -> 31880 bytes 06-build_linux/console.log.xz | Bin 3068 -> 3036 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4308 -> 4392 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 | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 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-arm-bootstrap_O1 updated (22af4383e5 -> 9433359884)

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_O1 in repository toolchain/ci/base-artifacts. from 22af4383e5 52: onsuccess: #444: 2: Success after binutils/gcc: 6 commits new 9433359884 53: onsuccess: #445: 2: Success after binutils/gcc: 31 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 1672 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 51020 -> 52224 bytes 05-build_abe-bootstrap_O1/console.log.xz | Bin 466280 -> 469784 bytes 06-check_regression/console.log.xz | Bin 2828 -> 3120 bytes 07-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 13 files changed, 24 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_gcc_check/master-arm updated (2012526d2a -> d5ad2f906f)

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-arm in repository toolchain/ci/base-artifacts. discards 2012526d2a 155: onsuccess: #1775: 1: Success after binutils: 2 commits discards f91b9c2354 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits discards 296e88e76a 153: onsuccess: #1773: 1: Success after gcc: 4 commits discards 65a7c271da 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits discards 8c0142e778 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] discards d644a3529a 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] discards e686951e50 149: onsuccess: #1769: 1: Success after gcc: 3 commits discards 48bae509d9 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits discards c8e15985cf 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits discards 0e60710996 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits discards fa01cd827c 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits discards 3882a85d87 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits discards 565d79502a 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits discards cde482198d 142: onsuccess: #1761: 1: Success after gcc: 83 commits discards c86f13a060 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] discards 9fba389f79 140: onsuccess: #1756: 1: Success after binutils: 3 commits discards cc3ad7b68c 139: onsuccess: #1753: 1: Success after binutils: 5 commits discards 3c95c3d606 138: onsuccess: #1749: 1: Success after binutils: 5 commits discards 39eebc453c 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] discards a8a6a41e38 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] discards f00b8987a2 135: onsuccess: #1739: 1: Success after binutils: 4 commits discards 5d91465c83 134: onsuccess: #1736: 1: Success after binutils: 3 commits discards 862285306f 133: onsuccess: #1733: 1: Success after binutils: 3 commits discards 5f27eec0bc 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits discards 89cae07b91 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits discards 10b8256b37 130: onsuccess: #1729: 1: Success after gcc: 9 commits discards b760f3cc0e 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] discards ec3f419afb 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits discards 62e3c86fa6 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] discards 2a67b0f0a2 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits discards b7c20f2fae 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits discards f6efcfeacb 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits discards 3b1c9195e1 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits discards db3738ba3a 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits discards b8fa92abe2 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits discards 45497ac3ea 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits discards 1e0cee5cb1 119: onsuccess: #1715: 1: Success after binutils: 4 commits discards a7dd5acd5d 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits discards 6b5a8bea2b 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits discards de33a075c0 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits discards 46d90f528f 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits discards f81d847fdf 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits discards 26c8608de3 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards f537aa3284 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards bbb20ec603 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards 8d47869ab5 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards c271bf7e32 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] discards 580cae4c6e 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards 829e08189d 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] discards 61cf300440 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards 92ed2cb70b 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards 62170a81d7 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards 014afaa6ee 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits discards 598ddc897d 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits discards 9c4c2e40f9 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits discards 79f19eab5b 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] discards 13f4b172be 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits discards cba9ce18dd 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits discards b8216f14ed 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits discards fc5c5aa192 96: onsuccess: #1654: 1: Success after gcc: 5 commits discards 90f544a655 95: onsuccess: #1653: 1: Success after gcc: 13 commits discards 8518f86b56 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits discards 5a2587214e 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] discards 9e9f595366 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits discards e396a0dc63 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] discards 1dfc0628c3 90: onsuccess: #1645: 1: Success after gcc: 2 commits discards 154d4446cd 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] discards 64a0cd739e 88: onsuccess: 1: Success after binutils/gcc: 2 commits discards 91fe1d2fd8 87: onsuccess: 1: Success after gcc: 6 commits discards 54a167f029 86: onsuccess: 1: Success after binutils/gcc: 8 commits discards 163f1bf091 85: onsuccess: 1: Success after binutils/gcc: 19 commits discards 5caa04c8c2 84: onsuccess: 1: Success after binutils/gcc: 2 commits discards 9bd5d6892c 83: onsuccess: 1: Success after gcc: 14 commits discards 7e09f1ef89 82: onsuccess: 1: Success after binutils/gcc: 9 commits discards 35995a4c75 81: onsuccess: 1: Success after binutils/gcc: 8 commits discards debd9ccf1d 80: onsuccess: 1: Success after binutils/gcc: 8 commits discards d1654d8657 79: onsuccess: 1: Success after binutils/gcc: 23 commits discards 1132794e93 78: onsuccess: 1: Success after binutils/gcc: 17 commits discards d26da6b21c 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 6765cf15b2 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 8f5d8f4446 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards f23bfd728b 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits discards 4a9aeca7a0 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards abbb3dfb44 72: onsuccess: 1: Successful build after baseline build: no [...] discards 99b09c1407 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards b84461ea21 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards c0728656d5 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] discards 46bf5f2538 68: onsuccess: 1: Successful build after gcc: 2 commits discards c23669ed12 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards e0b9f64df5 66: onsuccess: 1: Successful build after gcc: 4 commits discards 7516692dae 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 21a366f944 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards b82fd2fd3d 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 22ddb6cc0e 62: onsuccess: 1: Successful build after gcc: 4 commits discards e360852230 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 10c461ea19 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards fa17985a9c 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits discards 80c96d0981 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] discards b091356c62 57: onsuccess: 1: Successful build after binutils: 2 commits discards 45cd4d5c76 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards b4ada9e8dd 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits new acbdecb22c 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits new deb1f7741f 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 361b293cc1 57: onsuccess: 1: Successful build after binutils: 2 commits new 47723a78d3 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] new b309b2ac20 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits new e14280600c 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits new 3c86daa0b9 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits new fdcce19f14 62: onsuccess: 1: Successful build after gcc: 4 commits new bc3ed34d8c 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 98d77928d3 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 8280af0921 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits new c6e165ad2d 66: onsuccess: 1: Successful build after gcc: 4 commits new 43aee283f0 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 580b932a50 68: onsuccess: 1: Successful build after gcc: 2 commits new cdc3cf4e29 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] new a3a3008b1d 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 90a2e06f0a 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 2f5eff3b5d 72: onsuccess: 1: Successful build after baseline build: no [...] new 07a3f1df82 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 3d9193a8d9 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits new 2f911cd62f 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 2b4f423ce3 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 3925512906 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits new a44e62cdb3 78: onsuccess: 1: Success after binutils/gcc: 17 commits new 6a8a25d2c2 79: onsuccess: 1: Success after binutils/gcc: 23 commits new 4e759d7a82 80: onsuccess: 1: Success after binutils/gcc: 8 commits new 52ae058f77 81: onsuccess: 1: Success after binutils/gcc: 8 commits new 67e7a9b3c1 82: onsuccess: 1: Success after binutils/gcc: 9 commits new 8ff42c0fa7 83: onsuccess: 1: Success after gcc: 14 commits new bf454bc9cd 84: onsuccess: 1: Success after binutils/gcc: 2 commits new 918ead87e1 85: onsuccess: 1: Success after binutils/gcc: 19 commits new acef546356 86: onsuccess: 1: Success after binutils/gcc: 8 commits new 1b1e62e456 87: onsuccess: 1: Success after gcc: 6 commits new 110e9e6942 88: onsuccess: 1: Success after binutils/gcc: 2 commits new 24d0685342 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] new b02007acd7 90: onsuccess: #1645: 1: Success after gcc: 2 commits new ff3a46bd1f 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] new 4dad260312 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits new a4db3aaae7 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] new 09e463ccab 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits new 812edb513a 95: onsuccess: #1653: 1: Success after gcc: 13 commits new 2ea4cdb2f0 96: onsuccess: #1654: 1: Success after gcc: 5 commits new c8a53e05b3 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits new a8012f1bcf 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits new 8b72cb2ede 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits new 4c83116b68 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] new 013af144db 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits new e2bc26d662 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits new d116ea3ba5 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new fd8b9cbbde 104: onsuccess: #1700: 1: Success after gcc: 2 commits new b2b23c6940 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new 08fa285679 106: onsuccess: #1702: 1: Success after gcc: 4 commits new 7231233cd0 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] new 6e5c79a2f8 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new 3702522239 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] new db8ff18837 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new 2580e2d998 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new 49c15a8028 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new 798db5d99f 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new 2355a29f43 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits new 9556446c1c 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits new 7e6f81e755 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits new 11c610e9b4 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits new c6f51c00e7 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits new c15aec552c 119: onsuccess: #1715: 1: Success after binutils: 4 commits new e277a5ed68 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits new 717602683f 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits new 5fe2b8f63e 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits new 19ba7cf16e 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits new f4ac77841c 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits new 88c2dde081 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits new cd9c34fb84 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits new d90a7b8374 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] new 862913b7a6 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits new 93dd29dacb 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] new 79ff462ac2 130: onsuccess: #1729: 1: Success after gcc: 9 commits new ddd5049e2e 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits new 7663d16749 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits new 34c1cee3e8 133: onsuccess: #1733: 1: Success after binutils: 3 commits new 5448d508e5 134: onsuccess: #1736: 1: Success after binutils: 3 commits new cddb7cbb4a 135: onsuccess: #1739: 1: Success after binutils: 4 commits new b9f6a54251 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] new c477bf0e83 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] new da71314b51 138: onsuccess: #1749: 1: Success after binutils: 5 commits new a20a0ef94c 139: onsuccess: #1753: 1: Success after binutils: 5 commits new eae50328cc 140: onsuccess: #1756: 1: Success after binutils: 3 commits new 474bed3325 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] new c5f4c2f5c4 142: onsuccess: #1761: 1: Success after gcc: 83 commits new 467524e75d 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits new 2fc2dfd0f6 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits new 442a5c6c01 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits new ce5f8fb3b3 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits new 8fb7a5c6e4 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits new fce1c993cb 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits new 6f19307b6f 149: onsuccess: #1769: 1: Success after gcc: 3 commits new fb6b7fc8f2 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] new 314556c05b 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] new ac1377b41f 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits new 953dea0485 153: onsuccess: #1773: 1: Success after gcc: 4 commits new f7192e2727 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits new 4ee7f86097 155: onsuccess: #1775: 1: Success after binutils: 2 commits new d5ad2f906f 156: onsuccess: #1776: 1: Success after binutils/gcc: 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 (2012526d2a) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (d5 [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1664 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2712 bytes 03-build_abe-binutils/console.log.xz | Bin 50792 -> 50648 bytes 04-build_abe-gcc/console.log.xz | Bin 232616 -> 234492 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3832 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2460 -> 2396 bytes 07-check_regression/console.log.xz | Bin 4856 -> 4468 bytes 07-check_regression/mail-body.txt | 27 - 07-check_regression/results.compare | 31 +- 07-check_regression/results.compare2 | 36 +- 08-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 2807940 -> 2782780 bytes sumfiles/g++.sum | 112 +- sumfiles/gcc.log.xz | Bin 2358904 -> 2380156 bytes sumfiles/gcc.sum | 4492 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 908880 -> 912348 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2176 -> 2160 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 204536 -> 204428 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2536 -> 2548 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 466040 -> 464160 bytes sumfiles/libstdc++.sum | 10 +- 32 files changed, 2392 insertions(+), 2483 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_gnu_cross_check_gcc/master-aarch64 updated (94826eac4 -> 068e421f8)

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 94826eac4 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/gd [...] discards 330b64206 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 commits discards 319001da9 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 709476971 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 8d8dd18c8 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 2a81a2aff 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 7ae279969 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/gd [...] discards 37a536a95 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 43bf08fb6 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 commits discards 47c2fd9ee 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: 2 [...] discards 0e7b02a0f 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/gd [...] discards e9527f858 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/gd [...] discards 18c95ca23 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qemu [...] discards 6d62db897 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 09660b14e 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards de036dfc3 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/gl [...] discards ceb0933f6 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 commits discards 29d0d6f2b 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 63bd57274 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/gl [...] discards d8d46cdbe 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qemu [...] discards af6814997 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 24a6e24ed 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 commits discards 9d958f460 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/gd [...] discards 7bc723f08 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/gd [...] discards d25e54e99 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 commits discards 20cbc9c86 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 commits discards aa7cde98d 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/gd [...] discards e387e9eee 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 4e22b9317 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 92b89630b 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-283 [...] discards b0ee3aa11 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/gd [...] discards 65a38d119 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 7328d5ac9 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-283 [...] discards 5be70e4c7 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 5cad7ce7e 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/gd [...] discards 0f7239421 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/gl [...] discards 4dfe7484b 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/gl [...] discards ba59b8491 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/gl [...] discards 7ab72da4a 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/gd [...] discards 9f5555d2e 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 3ed3ee32c 115: onsuccess: #2147: 1: Success after binutils/linux/glibc/ [...] discards d2b25fff9 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/gd [...] discards e91028af3 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/gd [...] discards d4088026f 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/gd [...] discards 7fac7042d 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/gl [...] discards 962e9dfcd 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/gd [...] discards 448ec07cc 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards cfe50d1ad 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards edaf4db5b 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards ff6b10e57 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] discards c1dc9ad21 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] discards 73339f110 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 443e408ba 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] discards 170c80e02 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] discards b76df77aa 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards db9ccc04d 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] discards 42ba2f78b 99: onsuccess: #2074: 1: Success after baseline build: no new [...] discards de89e74e2 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards a2f03f66d 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 0414a2178 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards aed6ddb41 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] discards e2401bddc 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] discards e5d165a35 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 924afcb9b 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 7b0e265e7 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 1291957ee 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards a4a93b4af 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 5089cbd7e 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards f363095c4 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 5c48491f6 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 3c4f0899d 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 5ef3e5fba 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards c9aa8f0a9 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 5e7067778 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards a79cc899b 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits discards 41156ccd7 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 0b24af59d 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 1f80d0fa7 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 5bb657995 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits discards 487a7f6b5 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 25d3a5649 75: onsuccess: 1: Successful build after linux: 44 commits discards 664c4cd96 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 5f678f5d2 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 3b5ae4e32 72: onsuccess: 1: Successful build after linux: 12 commits discards 460075457 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 5a294ee92 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards f736cba4f 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 4690a12c2 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a53f55957 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] discards aa822a57f 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 79647b254 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ea50043cb 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 6d8e2b15b 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 22cbfb5ca 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] discards 09be2e9ea 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 00dd264d6 60: onsuccess: 1: Successful build after glibc: 2 commits discards e68efca98 59: onsuccess: 1: Successful build after binutils: 2 commits discards bacb60986 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] discards 3b408c19f 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards c4f0e6dd5 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9eaeee48f 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] new aa4f33392 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] new 1758f18e3 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 826db8772 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 0f13b1f63 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] new 061667502 59: onsuccess: 1: Successful build after binutils: 2 commits new 1daffc42f 60: onsuccess: 1: Successful build after glibc: 2 commits new a3bd176a1 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 28a6af862 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] new 6867a6282 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 0dac5fc1a 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 0790c6b1b 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 247b31a4d 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 63cd8bc3a 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] new 84fa7d72a 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 6fc9b72e7 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new eec562af1 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new d467ec984 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 2cd28e09f 72: onsuccess: 1: Successful build after linux: 12 commits new a70a667c2 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d7eca240e 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 91ebf9353 75: onsuccess: 1: Successful build after linux: 44 commits new 3687b0307 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e35b3786f 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits new e87545e12 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new e784f0173 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 531759ca5 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new a6a9e5534 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits new 74365579c 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new fe62cb5d2 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new d3962ad70 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 470357452 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new a21ab6367 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 4109ce939 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 3b75bb8b8 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 16e3725d7 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 893172ad2 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 1909a930a 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 3f8fe43fe 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 0821d1e40 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 90e3674ae 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] new 37ea60cce 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] new fda124138 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 4eb248c84 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 1ff02ff4a 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 936a8d905 99: onsuccess: #2074: 1: Success after baseline build: no new [...] new ff4d305d3 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] new de1e25c2a 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 51124edaa 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] new eec9ff7b4 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] new 14b1242b0 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 091a9c057 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] new 7487b7463 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] new 1390536b9 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new bddd2aa1c 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 36233c649 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new e39c87392 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/gd [...] new dd3f88e80 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/gl [...] new 11c304330 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/gd [...] new de5f591f6 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/gd [...] new ca424385e 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/gd [...] new 05e681558 115: onsuccess: #2147: 1: Success after binutils/linux/glibc/ [...] new aa5de271b 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new f53de9ff1 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/gd [...] new d5b194c71 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/gl [...] new 4429de90d 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/gl [...] new b86257f97 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/gl [...] new 4fd81086d 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/gd [...] new e55547bd7 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new a1383f684 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-283 [...] new cdfd41346 124: onsuccess: #2159: 1: Success after linux: 23 commits new 2a4f7d9d6 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/gd [...] new 83e91162b 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-283 [...] new 4021a0cc2 127: onsuccess: #2162: 1: Success after gcc: 9 commits new c9fa4b4fe 128: onsuccess: #2163: 1: Success after linux: 23 commits new f9d96f803 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/gd [...] new 87824472f 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 commits new da022fa3e 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 commits new 0b9b399ff 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/gd [...] new ba42e673a 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/gd [...] new 0f0d5e2c5 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 commits new 0f44721c6 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new e183ab724 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qemu [...] new c4a6b1ec5 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/gl [...] new 419600e24 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new e83b49d64 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 commits new 274ea7ab1 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/gl [...] new 28d10fffd 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new bc70d1cf0 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 4b6a42f6e 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qemu [...] new b084eed31 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/gd [...] new 563cb87b5 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/gd [...] new 9e4f4174f 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: 2 [...] new 8eb6bc059 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 commits new 49de3f8e9 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new b583b3e13 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/gd [...] new 848f26f1c 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 26b5195b4 151: onsuccess: #2186: 1: Success after gcc: 2 commits new cd65df7f8 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 160de5544 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new a82a0c79f 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 commits new 01fc05a6e 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/gd [...] new 068e421f8 156: onsuccess: #2191: 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 (94826eac4) \ 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 1700 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30368 -> 30136 bytes 04-build_abe-stage1/console.log.xz | Bin 72316 -> 72460 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8548 -> 8320 bytes 07-build_abe-glibc/console.log.xz | Bin 239844 -> 239796 bytes 08-build_abe-stage2/console.log.xz | Bin 203196 -> 203216 bytes 09-build_abe-gdb/console.log.xz | Bin 37712 -> 37548 bytes 10-build_abe-qemu/console.log.xz | Bin 31936 -> 31928 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2568 -> 2440 bytes 13-check_regression/console.log.xz | Bin 9528 -> 6008 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 8 + 13-check_regression/mail-body.txt | 129 +- 13-check_regression/results.compare | 68 +- 13-check_regression/results.compare2 | 732 +---- 13-check_regression/results.regressions | 28 + 14-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 131 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 28 + sumfiles/g++.log.xz | Bin 3411884 -> 3408516 bytes sumfiles/g++.sum | 171 +- sumfiles/gcc.log.xz | Bin 3031720 -> 3023416 bytes sumfiles/gcc.sum | 4435 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1034672 -> 1033820 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202288 -> 202416 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2656 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 427432 -> 423608 bytes sumfiles/libstdc++.sum | 18 +- 44 files changed, 2557 insertions(+), 3358 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions -- 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_native_check_gdb/master-aarch64 updated (121e17657 -> 7bf4c06e0)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. from 121e17657 49: onsuccess: #822: 1: Success after binutils/gcc/linux/glib [...] new 7bf4c06e0 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb: [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1688 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 37684 -> 37720 bytes 04-build_abe-gcc/console.log.xz | Bin 212276 -> 211832 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8928 -> 8220 bytes 07-build_abe-glibc/console.log.xz | Bin 239260 -> 239648 bytes 08-build_abe-gdb/console.log.xz | Bin 37200 -> 37632 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3832 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2008 -> 2304 bytes 11-check_regression/console.log.xz | Bin 13516 -> 12852 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 45 +- 11-check_regression/mail-body.txt | 183 +- 11-check_regression/results.compare | 94 +- 11-check_regression/results.compare2 | 3230 +++++++-------- 11-check_regression/results.regressions | 94 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 185 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 94 +- sumfiles/gdb.log.xz | Bin 1882140 -> 1840876 bytes sumfiles/gdb.sum | 6668 ++++++++++++++++--------------- 29 files changed, 5114 insertions(+), 5527 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 October 2022