Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-norov-allyesconfig updated (fe21ea9e79 -> 28c6047905)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-norov-allyesconfig in repository toolchain/ci/base-artifacts. from fe21ea9e79 15: onsuccess: #56: 21254: Success after linux: 7 commits new 28c6047905 16: onsuccess: #57: 21254: Success after binutils: 80 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 1716 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30828 -> 30280 bytes 04-build_kernel_llvm/console.log.xz | Bin 65748 -> 63808 bytes 05-build_abe-qemu/console.log.xz | Bin 31780 -> 31552 bytes 06-build_linux/console.log.xz | Bin 3612 -> 3736 bytes 08-check_regression/console.log.xz | Bin 2960 -> 2944 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 | 12 ++++++------ 13 files changed, 11 insertions(+), 11 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/gnu-release-arm-norov-allmodconfig updated (b3b86b94df -> 17a6ea0ac0)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-norov-allmodconfig in repository toolchain/ci/base-artifacts. from b3b86b94df 12: onsuccess: #44: all: Success after binutils/gcc/linux/qe [...] new 17a6ea0ac0 13: onsuccess: #45: all: Success after binutils/gcc/linux/qe [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1704 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 29880 -> 29800 bytes 04-build_abe-stage1/console.log.xz | Bin 87148 -> 86788 bytes 05-build_abe-qemu/console.log.xz | Bin 30948 -> 32228 bytes 06-build_linux/console.log.xz | Bin 3412 -> 3428 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4124 -> 4188 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 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_bmk_llvm_apm/llvm-release-arm-spec2k6-Oz_LTO updated (3a3fbb3193 -> 4ac0973cd3)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_llvm_apm/llvm-release-arm-spec2k6-Oz_LTO in repository toolchain/ci/base-artifacts. from 3a3fbb3193 14: onsuccess: #98: 1: [TCWG CI] No change after binutils/gc [...] new 4ac0973cd3 15: onsuccess: #99: 1: [TCWG CI] No change after binutils/gc [...] 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 1764 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 29800 -> 29956 bytes 04-build_abe-stage1/console.log.xz | Bin 87180 -> 87208 bytes 06-build_abe-linux/console.log.xz | Bin 8628 -> 8644 bytes 07-build_abe-glibc/console.log.xz | Bin 229288 -> 229500 bytes 08-build_abe-stage2/console.log.xz | Bin 208372 -> 206848 bytes 09-build_llvm-true-false-/console.log.xz | Bin 0 -> 61192 bytes 09-build_llvm-true/console.log.xz | Bin 61976 -> 0 bytes 10-benchmark/benchmark-build.log | 100 +- 10-benchmark/benchmark.log | 98 +- 10-benchmark/console.log.xz | Bin 3868 -> 3852 bytes 11-check_regression/console.log.xz | Bin 6900 -> 6836 bytes 11-check_regression/csv-results-0/perf.csv | 169 +- 11-check_regression/csv-results-0/results.csv | 381983 +++++++++-------- 11-check_regression/csv-results-0/size.csv | 379046 +++++++++-------- 11-check_regression/csv-results-0/vect.csv | 17253 +- 11-check_regression/csv-results-1/perf.csv | 175 +- 11-check_regression/csv-results-1/results.csv | 398635 +++++++++--------- 11-check_regression/csv-results-1/size.csv | 388952 ++++++++--------- 11-check_regression/csv-results-1/vect.csv | 17282 +- 11-check_regression/results-brief.csv | 40 +- 11-check_regression/results-compare.csv | 1 + 11-check_regression/results-full.csv | 193 +- 11-check_regression/results-internal.csv | 49 +- 11-check_regression/results.csv | 49 +- 11-check_regression/results.log | 731 +- dashboard/dashboard-generate.sh | 2 +- .../squad/400.perlbench/results-metadata.json | 16 +- dashboard/squad/401.bzip2/results-metadata.json | 16 +- dashboard/squad/401.bzip2/results-metrics.json | 2 +- dashboard/squad/403.gcc/results-metadata.json | 16 +- dashboard/squad/403.gcc/results-metrics.json | 2 +- dashboard/squad/429.mcf/results-metadata.json | 16 +- dashboard/squad/433.milc/results-metadata.json | 16 +- dashboard/squad/433.milc/results-metrics.json | 2 +- dashboard/squad/444.namd/results-metadata.json | 16 +- dashboard/squad/444.namd/results-metrics.json | 2 +- dashboard/squad/445.gobmk/results-metadata.json | 16 +- dashboard/squad/445.gobmk/results-metrics.json | 2 +- dashboard/squad/447.dealII/results-metadata.json | 16 +- dashboard/squad/447.dealII/results-metrics.json | 2 +- dashboard/squad/450.soplex/results-metadata.json | 16 +- dashboard/squad/450.soplex/results-metrics.json | 2 +- dashboard/squad/453.povray/results-metadata.json | 16 +- dashboard/squad/453.povray/results-metrics.json | 2 +- dashboard/squad/456.hmmer/results-metadata.json | 16 +- dashboard/squad/456.hmmer/results-metrics.json | 2 +- dashboard/squad/458.sjeng/results-metadata.json | 16 +- dashboard/squad/458.sjeng/results-metrics.json | 2 +- .../squad/462.libquantum/results-metadata.json | 16 +- .../squad/462.libquantum/results-metrics.json | 2 +- dashboard/squad/464.h264ref/results-metadata.json | 16 +- dashboard/squad/464.h264ref/results-metrics.json | 2 +- dashboard/squad/470.lbm/results-metadata.json | 16 +- dashboard/squad/470.lbm/results-metrics.json | 2 +- dashboard/squad/471.omnetpp/results-metadata.json | 16 +- dashboard/squad/471.omnetpp/results-metrics.json | 2 +- dashboard/squad/473.astar/results-metadata.json | 16 +- dashboard/squad/473.astar/results-metrics.json | 2 +- dashboard/squad/482.sphinx3/results-metadata.json | 16 +- dashboard/squad/482.sphinx3/results-metrics.json | 2 +- .../squad/483.xalancbmk/results-metadata.json | 16 +- dashboard/squad/483.xalancbmk/results-metrics.json | 2 +- dashboard/squad/dashboard-push-squad.sh | 78 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 50 +- mail/mail-body.txt | 50 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 2 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 401328 -> 401496 bytes save-temps/401.bzip2.tar.xz | Bin 42712 -> 42720 bytes save-temps/403.gcc.tar.xz | Bin 1213544 -> 1213228 bytes save-temps/429.mcf.tar.xz | Bin 22324 -> 22304 bytes save-temps/433.milc.tar.xz | Bin 58800 -> 58844 bytes save-temps/444.namd.tar.xz | Bin 45012 -> 45008 bytes save-temps/445.gobmk.tar.xz | Bin 619820 -> 619504 bytes save-temps/447.dealII.tar.xz | Bin 882368 -> 882208 bytes save-temps/450.soplex.tar.xz | Bin 207804 -> 207888 bytes save-temps/453.povray.tar.xz | Bin 460548 -> 460700 bytes save-temps/456.hmmer.tar.xz | Bin 123452 -> 123324 bytes save-temps/458.sjeng.tar.xz | Bin 50900 -> 50848 bytes save-temps/462.libquantum.tar.xz | Bin 23716 -> 23656 bytes save-temps/464.h264ref.tar.xz | Bin 176096 -> 176164 bytes save-temps/470.lbm.tar.xz | Bin 15556 -> 15544 bytes save-temps/471.omnetpp.tar.xz | Bin 316460 -> 316464 bytes save-temps/473.astar.tar.xz | Bin 41928 -> 41932 bytes save-temps/482.sphinx3.tar.xz | Bin 94124 -> 94068 bytes save-temps/483.xalancbmk.tar.xz | Bin 3290312 -> 3289760 bytes 94 files changed, 802619 insertions(+), 782707 deletions(-) create mode 100644 09-build_llvm-true-false-/console.log.xz delete mode 100644 09-build_llvm-true/console.log.xz -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (147f6ed39f6 -> beeb6898fe8)

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 147f6ed39f6 libstdc++: Implement ranges::join_with_view from P2441R2 new 7d8189882fc libstdc++: Define <bits/functexcept.h> functions for freest [...] new 7cdab65f3d7 libstdc++: Make <cstdint> work freestanding [PR107134] new b74ab7a1609 libstdc++: Enable std::hash<coroutine_handle<P>> [PR107139] new beeb6898fe8 libstdc++: Disable test for freestanding The 4 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: libstdc++-v3/include/bits/functexcept.h | 25 +++++++++ libstdc++-v3/include/c_global/cstdint | 59 +++++++++++++++++++++- libstdc++-v3/include/std/bitset | 8 +-- libstdc++-v3/include/std/coroutine | 10 +--- .../25_algorithms/stable_sort/mem_check.cc | 2 + 5 files changed, 87 insertions(+), 17 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-arm updated (6f2fc5cecc -> 7916bdb1d9)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-arm in repository toolchain/ci/base-artifacts. discards 6f2fc5cecc 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits discards 16397375b3 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/g [...] discards 93edb345fb 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/g [...] discards abb299f69d 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 [...] discards 5534b1e700 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits discards f050bf8da7 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/g [...] discards 9c5573b5e9 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/g [...] discards 5ede5ac01d 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] discards b13f7fb6a9 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] discards f19cf05719 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards cb63c422f1 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards 70ce602be0 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards cddf0027c3 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] discards 68c62c5bda 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] discards 5970b50c49 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] discards 3c0dbc59e3 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] discards 2a816711af 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] discards 8ca84bea96 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] discards 8e55a9c801 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards ac30d6d42d 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 859dfa73bc 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards e3fe88cf96 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards d8364af00c 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards f93fcc8898 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards 47066cfc12 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards b8f0dad22b 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards 21af2e3866 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards 46b4c2f48d 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards 5a3ca73afa 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards b2f1df63fe 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards 188edda9e5 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards d46d3be3a6 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 896c4e2d7a 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards e1d24b230f 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 590c81008f 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards ee76836c65 132: onsuccess: #1645: 7: Success after linux: 23 commits discards f164af0146 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards e08e102cfd 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards 12feb4dd5d 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 06dff9c9eb 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards 8bf29c6a51 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 7f5049c3d7 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 2296932836 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards cac9c60de4 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 9f48c56344 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards 548c00e83e 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 06700f2ec1 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 143266e692 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards b9d831981e 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 0ea5342558 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 72f1849b80 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 3d04a67149 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards f2c35e1fe8 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards e074ee5146 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards eb1710b2b8 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 5f767a4ca1 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 50a4d0ed85 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 7b7554c503 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards fdcc48e5d0 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 6d0f03fbe6 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 4e225f396d 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards e91c75162b 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 1639a658c1 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 7abb2bfb6a 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 40fc816b5c 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 81a94b407c 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 0acb7c58ca 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards f500a9bb99 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards cbaf7e5f38 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 0b9bf0eb70 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards a15e1fe63d 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards 263016b879 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 8379bb433d 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards 3b8106f343 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards dda5d374c6 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards b1a2ea57cd 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 0ba4db8d6f 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 4d4d0977f6 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 89b012e86f 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards f386cf7a9c 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 607ecfcabb 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 1ed26f9054 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards ae59519098 85: onsuccess: 7: Success after gcc: 9 commits discards 11c1379e9d 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards e61e3f9b04 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 2113388716 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 6be76d7f33 81: onsuccess: 7: Successful build after gcc: 2 commits discards 63da6ff13a 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards deec47693c 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 8544fdd511 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 931a11a8c7 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards e3e253b6f5 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 2fc44be430 75: onsuccess: 7: Successful build after linux: 44 commits discards faeeeead30 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 7cf6f9cd21 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 025fbe0e54 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 68ca0eb575 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 5fa0341b80 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards a6048f55ce 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards e708a1f458 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7bbe770a40 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 416b8940e0 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 445b360124 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 68f542be8c 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 510dfbd368 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 1610c84fbb 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 23f2216af2 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 7d4faefe3f 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d52a89d78b 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new ef1523e1ec 75: onsuccess: 7: Successful build after linux: 44 commits new ffc1c1c6ae 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c045768c7c 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 0a50d8d462 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5579718ace 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 63f8a1cc82 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 21a072ab1c 81: onsuccess: 7: Successful build after gcc: 2 commits new aad4485783 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 7d1d83c5e5 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 2bb2482a94 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 9a43162e1e 85: onsuccess: 7: Success after gcc: 9 commits new c14c97c0e5 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 0bda718ab8 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 45a6e2049b 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 3d0b9c51d0 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 9d3dbfc19e 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 97de3c590b 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 7825a0a551 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new e4a91aef1d 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new 9010195d46 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new fceed7f37d 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 8bd52144b2 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 09c4d220c1 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new cd6d4f2493 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 904d372724 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new a23b7774fc 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new 8745f0d21c 101: onsuccess: #1609: 7: Success after binutils: 78 commits new c951db21bf 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 7063ed33e7 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 24e20d6795 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new db7a4ed6f9 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 8a4f32be6b 106: onsuccess: #1617: 7: Success after gcc: 2 commits new cb61147bb9 107: onsuccess: #1618: 7: Success after gcc: 2 commits new a6dca3adb4 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new b5114b80ba 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new fe3410d281 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new e15d0f7d35 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new ed110970b3 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new d780e7e707 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 8c1c5fbb98 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new d38a2b8b4b 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 40a2ac1971 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 2928439de8 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 4ac182cf4d 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 9eef4e64b7 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new f154b78c64 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new ce73ed9f0d 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new 53c594459b 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 309646c7d9 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 2ccd81ff7d 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new fa03036df1 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new c75404c554 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new ae7d75d8fc 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 4b466b2c39 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 07db132c7f 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 22eda25ba1 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 2eda6b179a 131: onsuccess: #1644: 7: Success after gcc: 10 commits new e9f3412bc8 132: onsuccess: #1645: 7: Success after linux: 23 commits new 1bf35d2569 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new 0eb76adb52 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new 3919b6b833 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new 92fbd2e814 136: onsuccess: #1650: 7: Success after binutils: 2 commits new fc244a6abd 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new d7d24d0b04 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new 65427ca7eb 139: onsuccess: #1654: 1: Success after gcc: 11 commits new cebe390015 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new d18a41130d 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 1680a0c59c 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 4e2b88a7dd 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new f86d9f98ec 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new 0dcf9b8f22 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new 477e5451be 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new 6204c40cee 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new 9f24215075 148: onsuccess: #1663: 7: Success after glibc: 2 commits new dca19203e9 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new 57b33ba598 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] new a71a410464 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] new c7d105b795 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] new f68771a165 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] new f6beac0da5 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] new 1ea1fd5557 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] new 52e91f528c 156: onsuccess: #1671: 7: Success after gcc: 3 commits new c81addd5ae 157: onsuccess: #1672: 7: Success after gcc: 2 commits new a070442263 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new 44ec3ac4d7 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] new 0f74ab9b20 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] new b389cd26d4 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/g [...] new 9d6c8a67d7 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/g [...] new 29cda29c8b 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits new f49cec811a 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 [...] new c34b71d865 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/g [...] new 181989f7b9 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/g [...] new 483a41e597 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits new 7916bdb1d9 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 34 [...] 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 (6f2fc5cecc) \ 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 1728 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30064 -> 30096 bytes 05-build_abe-stage1/console.log.xz | Bin 90692 -> 90500 bytes 07-build_abe-linux/console.log.xz | Bin 9152 -> 9188 bytes 08-build_abe-glibc/console.log.xz | Bin 233904 -> 234012 bytes 09-build_abe-stage2/console.log.xz | Bin 224264 -> 222780 bytes 10-build_abe-gdb/console.log.xz | Bin 37184 -> 37360 bytes 11-build_abe-qemu/console.log.xz | Bin 31496 -> 31680 bytes 12-check_regression/console.log.xz | Bin 3600 -> 4044 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 | 36 ++++++++++---------- 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

[glibc] branch master updated (7e8283170c -> 1f3f0060a1)

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 glibc. from 7e8283170c x86-64: Require BMI1/BMI2 for AVX2 strrchr and wcsrchr imple [...] new 1f3f0060a1 Use Linux 6.0 in build-many-glibcs.py 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: scripts/build-many-glibcs.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (e886ebd1796 -> 147f6ed39f6)

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 e886ebd1796 install.texi: gcn - update llvm reqirements, gcn/nvptx - ne [...] new 147f6ed39f6 libstdc++: Implement ranges::join_with_view from P2441R2 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: libstdc++-v3/include/std/ranges | 458 +++++++++++++++++++++ .../testsuite/std/ranges/adaptors/join_with/1.cc | 97 +++++ 2 files changed, 555 insertions(+) create mode 100644 libstdc++-v3/testsuite/std/ranges/adaptors/join_with/1.cc -- 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-mainline-allnoconfig updated (a56b3543aa -> f07e49ad14)

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-mainline-allnoconfig in repository toolchain/ci/base-artifacts. from a56b3543aa 12: onsuccess: #363: all: Success after binutils/llvm/linux/ [...] new f07e49ad14 13: onsuccess: #364: all: 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 1696 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30160 -> 30016 bytes 04-build_kernel_llvm/console.log.xz | Bin 64536 -> 64480 bytes 05-build_abe-qemu/console.log.xz | Bin 30988 -> 32252 bytes 06-build_linux/console.log.xz | Bin 3128 -> 3136 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4252 -> 4236 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_check/master-aarch64 updated (7f48074235 -> cd39d033bc)

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 7f48074235 161: onsuccess: #2096: 1: Success after gcc: 2 commits discards 8aa3367f13 160: onsuccess: #2095: 1: Success after binutils/gcc: 4 commits discards e58ec47978 159: onsuccess: #2094: 1: Success after binutils/gcc: 23 commits discards 11a2516103 158: onsuccess: #2093: 1: Success after binutils/gcc: 9 commits discards 0442a8f000 157: onsuccess: #2092: 1: Success after binutils/gcc: 3 commits discards 0b7fdcb8e0 156: onsuccess: #2091: 1: Success after binutils/gcc: 2 commits discards 32e6fe7393 155: onsuccess: #2090: 1: Success after binutils/gcc: 22 commits discards 7d3fa70ad4 154: onsuccess: #2089: 1: Success after gcc: 4 commits discards 3f1bd5ca28 153: onsuccess: #2088: 1: Success after basepoints/gcc-13-30 [...] discards 2907312b0a 152: onsuccess: #2087: 1: Success after gdb-12-branchpoint-2 [...] discards a65b229d1d 151: onsuccess: #2086: 1: Success after gcc: 2 commits discards 87b01fc3ab 150: onsuccess: #2085: 1: Success after gcc: 2 commits discards 3f7fc35025 149: onsuccess: #2084: 1: Success after gcc: 16 commits discards 3f9143cabf 148: onsuccess: #2082: 1: Success after gdb-12-branchpoint-2 [...] discards 9c06dd4abf 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 commits discards e7334c8310 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits discards 18525c925c 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits discards e43a586c1a 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits discards ecbb0daac7 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits discards e6cf52b59e 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits discards ae6fada69f 141: onsuccess: #2073: 1: Success after binutils: 3 commits discards 9a43cade41 140: onsuccess: #2070: 1: Success after binutils: 4 commits discards 9cb18e80e2 139: onsuccess: #2067: 1: Success after binutils: 2 commits discards 2b1d215067 138: onsuccess: #2064: 1: Success after binutils: 4 commits discards 204ddf6dbd 137: onsuccess: #2061: 1: Success after binutils: 2 commits discards 8da6f82ab2 136: onsuccess: #2056: 1: Success after binutils: 4 commits discards d89fccb26d 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits discards 54eb1e0cd6 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits discards 7165c69570 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits discards 6f7d031269 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits discards 5c8eea70d1 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] discards 12b9bfd592 130: onsuccess: #2049: 1: Success after gcc: 9 commits discards aab90982e7 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] discards e283d9ed5a 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] discards 46f388ad4c 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] discards 10b3e41eda 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] discards 16dc62a5f8 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits discards 110a43df0e 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits discards 5606b20b55 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits discards ad06dcf168 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits discards 96c914dd49 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits discards 671c900ed2 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits discards 84b6cec1ad 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits discards ca30261a27 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits discards 172eae09be 117: onsuccess: #2034: 1: Success after binutils: 2 commits discards c695fe38df 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits discards 2be48529b6 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits discards 6fca77bd8d 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits discards 1be2153ea4 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits discards 8cc8a41c1b 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits discards 5e97f8d937 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits discards 199388bd84 110: onsuccess: #2027: 1: Success after gcc: 5 commits discards 344deacef9 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits discards 3022257024 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits discards 6839857238 107: onsuccess: #2024: 1: Success after gcc: 3 commits discards 43c13353b1 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits discards 1b812a870d 105: onsuccess: #2022: 1: Success after gcc: 4 commits discards 2e704cee06 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards 8403b8749a 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards 52f0db5850 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] discards aa46b6f21c 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards 8bf307b79b 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards b1f9a61ee7 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards 00f5424f7d 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards e943e97c5b 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards 5e51a128c6 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] discards 63d9240f2e 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] discards 6a010d65bc 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards 4f0007c873 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] discards 6d7dee092d 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards 18ceec43c8 91: onsuccess: 1: Success after gcc: Daily bump. discards 710e5a2bc6 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards ffb44bb5fe 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards 01fbb5dfcd 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards 412e650f34 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards 26b965db88 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards 99c349a063 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards 6ad49e8bdb 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards 7838a88ab9 83: onsuccess: 1: Success after gcc: 8 commits discards 609aa2c998 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards 4ed4288f24 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards 6b34ac04e0 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards d75aa85985 79: onsuccess: 1: Successful build after gcc: Daily bump. discards a3a5a1e32e 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 16e56dd954 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards ed0003b34f 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 158b46a972 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards e7e1f2ebca 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards cec0b82980 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards 2a2b518c1c 72: onsuccess: 1: Successful build after gcc: 2 commits discards 761649872e 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 18ca241d02 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards 9f6441ddec 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards df19c61a6c 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 70d32a58e2 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 9d3e806a90 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 90bc1cfff6 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards d6b694ff4f 64: onsuccess: 1: Successful build after gcc: 5 commits discards a33869e2c9 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 15acd9f89d 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 30818264f7 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits new 9921b8d524 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits new 9c437a394c 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 5d2dd94246 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits new f4601ee8e2 64: onsuccess: 1: Successful build after gcc: 5 commits new 0a374f81a5 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits new a2f3b81ca8 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new f5b3ee85ab 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new cd2f970e0a 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new d199ebd984 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 99891acb4d 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new c572f5e965 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 8426ada97c 72: onsuccess: 1: Successful build after gcc: 2 commits new 4acebcd7d4 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 2263d9f257 74: onsuccess: 1: Successful build after binutils: Automatic [...] new c485004715 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 935c64ec65 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 2628178b6c 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 8dc5eb7a69 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new b77f5f53f8 79: onsuccess: 1: Successful build after gcc: Daily bump. new 4389ef92d1 80: onsuccess: 1: Success after binutils/gcc: 14 commits new f4dc5c40c4 81: onsuccess: 1: Success after binutils/gcc: 27 commits new 9a19883661 82: onsuccess: 1: Success after binutils/gcc: 10 commits new 8e2c5204b8 83: onsuccess: 1: Success after gcc: 8 commits new 4baa8ea66d 84: onsuccess: 1: Success after binutils/gcc: 9 commits new 23f058da4b 85: onsuccess: 1: Success after binutils/gcc: 9 commits new 0fc2ed63f4 86: onsuccess: 1: Success after binutils/gcc: 13 commits new b775e676b3 87: onsuccess: 1: Success after binutils/gcc: 4 commits new a0790efefa 88: onsuccess: 1: Success after binutils/gcc: 16 commits new 8c825f5436 89: onsuccess: 1: Success after binutils/gcc: 9 commits new cd3fc103ef 90: onsuccess: 1: Success after binutils/gcc: 6 commits new d8271c1954 91: onsuccess: 1: Success after gcc: Daily bump. new 9e251159ba 92: onsuccess: #1965: 1: Success after gcc: 2 commits new c1eec7c0c2 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] new f0ac78177b 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new 17135d8bec 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] new eaf54c2b41 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] new 5fdb1a7841 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new d6863250ea 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new 6e59dff35e 99: onsuccess: #1974: 1: Success after gcc: 14 commits new d220e53f48 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new 209da209cc 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new 81d563ced5 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] new 0ba7c9d647 103: onsuccess: #2020: 1: Success after gcc: 2 commits new 6ed3b5edd6 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new 60fc966a24 105: onsuccess: #2022: 1: Success after gcc: 4 commits new ab73c6c372 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits new 07ba1279a2 107: onsuccess: #2024: 1: Success after gcc: 3 commits new b1067f3b72 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits new 87e850fb5d 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits new b87a84f82d 110: onsuccess: #2027: 1: Success after gcc: 5 commits new 5f1cdd721a 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits new 56fad62644 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits new de2cae76a8 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits new 8d60e80a76 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits new 50a95187f6 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits new e6d9cc99ec 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits new e42f784b2f 117: onsuccess: #2034: 1: Success after binutils: 2 commits new c1f3104df9 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits new 62420ae8d2 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits new d097dadac5 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits new f61cc9e2ec 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits new 2f8a7df287 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits new 7beecebfb1 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits new 390e3f7a87 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits new 96c64cb326 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits new ae63322767 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] new 4fa3bfc186 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] new 6b77a952f4 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] new b65e580ab5 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] new a61d2c4b00 130: onsuccess: #2049: 1: Success after gcc: 9 commits new 68dd7af46b 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] new 3cf910ce07 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits new 015454bf14 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits new e61cbeaddb 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits new 8e914fd298 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits new d1bdeb449c 136: onsuccess: #2056: 1: Success after binutils: 4 commits new 8ce6ea6416 137: onsuccess: #2061: 1: Success after binutils: 2 commits new 386df4cec5 138: onsuccess: #2064: 1: Success after binutils: 4 commits new e9ceca3d9a 139: onsuccess: #2067: 1: Success after binutils: 2 commits new df4dbcd58e 140: onsuccess: #2070: 1: Success after binutils: 4 commits new f4e9bc147b 141: onsuccess: #2073: 1: Success after binutils: 3 commits new 3d7d59c712 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits new 2c54dab308 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits new 08bf7a8d76 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits new d25de95785 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits new 2c5dc5812c 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits new 90873939f9 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 commits new c64a413958 148: onsuccess: #2082: 1: Success after gdb-12-branchpoint-2 [...] new 17dfd1521c 149: onsuccess: #2084: 1: Success after gcc: 16 commits new 5ea83c42d4 150: onsuccess: #2085: 1: Success after gcc: 2 commits new 4fc9623c9d 151: onsuccess: #2086: 1: Success after gcc: 2 commits new 38a642b8d4 152: onsuccess: #2087: 1: Success after gdb-12-branchpoint-2 [...] new cb03a46dc0 153: onsuccess: #2088: 1: Success after basepoints/gcc-13-30 [...] new c942cf0fbd 154: onsuccess: #2089: 1: Success after gcc: 4 commits new d61bad794d 155: onsuccess: #2090: 1: Success after binutils/gcc: 22 commits new 45286b1ac0 156: onsuccess: #2091: 1: Success after binutils/gcc: 2 commits new 7628af9990 157: onsuccess: #2092: 1: Success after binutils/gcc: 3 commits new 06ec7ebcd0 158: onsuccess: #2093: 1: Success after binutils/gcc: 9 commits new 841eea304a 159: onsuccess: #2094: 1: Success after binutils/gcc: 23 commits new da8e9cb518 160: onsuccess: #2095: 1: Success after binutils/gcc: 4 commits new f8911fdd59 161: onsuccess: #2096: 1: Success after gcc: 2 commits new cd39d033bc 162: onsuccess: #2097: 1: Success after binutils/gcc: 16 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 (7f48074235) \ 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 1688 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 38364 -> 37376 bytes 04-build_abe-gcc/console.log.xz | Bin 214612 -> 213536 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3832 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2656 -> 2448 bytes 07-check_regression/console.log.xz | Bin 4624 -> 5524 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 191 +- 08-update_baseline/console.log | 48 +- 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 3592588 -> 3588200 bytes sumfiles/g++.sum | 232 +- sumfiles/gcc.log.xz | Bin 3096552 -> 3137520 bytes sumfiles/gcc.sum | 4876 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1039448 -> 1040412 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2188 -> 2188 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207316 -> 207380 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2548 -> 2548 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 447944 -> 461104 bytes sumfiles/libstdc++.sum | 12 +- 31 files changed, 2853 insertions(+), 2624 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 (16c4987cd6 -> adc066924f)

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 16c4987cd6 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits discards c9de17b3f8 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/g [...] discards 0c10baef71 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/g [...] discards 024fdf7df0 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 12 [...] discards 8fd7c8f5ec 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 commits discards 847d7f5854 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/g [...] discards 7d173cf516 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 6c468e89d6 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards 84046a49dc 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] discards 978dc2f99e 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards eb50fd9e94 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards bf410f9220 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] discards 8e4bddf97b 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards 66f651b985 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] discards 60b36eeb6d 152: force: #1605: 7: Success after gcc: 9 commits discards 85f655ce4e 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] discards f2e1555ce4 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] discards f54139fd9a 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards 1d4b773feb 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards 882ec38f4a 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards 95004a7895 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards a303762b0f 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards e7b6d21748 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards cfd5cdd549 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards f3eaa4ca16 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards d25371f549 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 57c4efbe7d 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards 2c70e4dc49 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards ad9b1e6f83 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards 8ee50b790e 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 53ceb0fe6f 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards 59a900a8f3 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards 8ecc37794b 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards dce54a15a6 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards a08de9ab63 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards 87d5ffcea3 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 130602d992 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards afd27fc1d2 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards c7e28addb8 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 081d46a029 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards cced09c658 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 6de43d29ae 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 85919344c7 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 108b7af7d7 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards ea83f3114b 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 95704c6bd5 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards 4f6de7a8f1 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards 594484ae35 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 19bfdb87b2 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards d6c39b1b24 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 2672fa12a7 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards fb178b105b 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards d2e8651311 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards 4b4a47d425 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards 49a8bcc5c9 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards 625edb26b4 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 47290986bd 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards e8b5be1cd0 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards f471e87dde 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 0ed39e4c48 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 51758d111c 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards d0f98e02a2 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards 97283c0700 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards 65641fd863 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards ca5a904938 102: force: #1551: 1: Failure after gcc: 306 commits discards 02d232ad3d 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards c161b3ebb4 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 7d3d377f0e 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 1d0e347b21 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 2543a83367 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 9638409d42 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 46194b7927 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 7b668b92eb 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 6e6ed17073 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 18760b52dd 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards b232f476e0 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards d5eb129fce 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards d052838a3f 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 92e14dbe94 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 8d93a94953 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards bfe274860c 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards a42710cbe6 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards ee6ba0b887 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards b1b2c87ee6 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 947fd43ef3 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 53f47c4489 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d2313b43e5 80: onsuccess: 7: Successful build after linux: 44 commits discards 2a4cccf593 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 80c680f87b 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards 9de1c8b714 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 48c7fd65d8 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 2061bef4a6 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 08a6bf2515 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 58c0a560e3 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 09f2203def 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b759a9457f 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards e3faf5f0e2 70: onsuccess: 7: Successful build after gcc: 4 commits discards 56b8e519d5 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c8ab2c0a63 68: onsuccess: 7: Successful build after linux: 6 commits discards 22fa1d3572 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards 1f080ec8d7 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 16b0aa9b71 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new f6f6a318f2 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new 08aefb9841 68: onsuccess: 7: Successful build after linux: 6 commits new fc93b13ddb 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 94c29bf1a9 70: onsuccess: 7: Successful build after gcc: 4 commits new 7823a0d9b6 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 5ee9abf94c 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new aa49a793f8 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 1828e2fa34 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 1cdd9c54b5 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new b0d4a616fe 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 0c11c05f24 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 269fd8d8ae 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new 578f1e3200 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 3ffa801c31 80: onsuccess: 7: Successful build after linux: 44 commits new adfb84e075 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7a578f8baa 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 3f9366988d 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 30c4d12c0e 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new ca022ac4a1 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 12696a192b 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 959dc710e0 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 7cc9dafa9a 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new b498b76981 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 6537459d92 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 98b57dfae5 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 65a36bb895 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 98696d05c5 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 2551640925 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new dc49940813 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 113c0e3a00 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new ae28a21646 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 7f88fd9059 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 4e3bfd2758 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 2ad2c261d1 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new e47223d598 101: onsuccess: #1547: 7: Success after binutils: 82 commits new e312ca885d 102: force: #1551: 1: Failure after gcc: 306 commits new bcf4a1b5c5 103: onsuccess: #1552: 1: Success after gcc: 5 commits new ca3ed92223 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 030da85e5d 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new d78a83469f 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 3fd34dee17 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new 626a94f69b 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new b396ecaf1c 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 4d30eed496 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 4196879a44 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new 8a053d9f57 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 741c54b68a 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new 2205bb5a39 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new c75576111b 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 619d7d0751 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 69abdc6ed5 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 9819661bef 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new 586468c6e5 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new f517d28f37 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 958f99f375 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 0cce678b33 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new b1ddffe13a 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new a491ed7328 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new d2d7a706b0 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 7d9a956847 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 8ff64d33c0 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new 6a86814812 128: onsuccess: #1579: 7: Success after linux: 12 commits new 797bc84e88 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new 15685a4dc6 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 76522eaa91 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new cb2102ee13 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new fc1324d184 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new 69e8dfc7ed 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new 12686bf733 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new 6f694c50f4 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new c668b8fe60 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 3832948d55 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new 95b1129d1a 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new f34138f662 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new 84f81b88d8 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new 43d0051d9f 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new dc40500729 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new 75e4900e32 144: onsuccess: #1595: 7: Success after glibc: 2 commits new 592cd071b8 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new 1dadd712e6 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new 2503cec2a6 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new fc21ff5b6d 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new 160083fc22 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new bd5b07d16c 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] new 0b0085187e 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] new 705e93adae 152: force: #1605: 7: Success after gcc: 9 commits new 14acac8873 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] new c37b857078 154: onsuccess: #1607: 1: Success after gcc: 2 commits new 283bdf6aec 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] new dcea9c8d9f 156: onsuccess: #1609: 7: Success after gcc: 2 commits new 9363f2578d 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new eb8bdc2082 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] new f19b823036 159: onsuccess: #1612: 7: Success after gcc: 4 commits new 1b26951976 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 8b9a48ecc0 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/g [...] new 4495801901 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 commits new b8f0f3e177 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 12 [...] new cf7d47f956 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/g [...] new 0980971081 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/g [...] new f274818629 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits new adc066924f 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 28 [...] 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 (16c4987cd6) \ 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 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30128 -> 30364 bytes 05-build_abe-stage1/console.log.xz | Bin 72584 -> 72476 bytes 07-build_abe-linux/console.log.xz | Bin 9184 -> 9168 bytes 08-build_abe-glibc/console.log.xz | Bin 239884 -> 240132 bytes 09-build_abe-stage2/console.log.xz | Bin 202840 -> 203084 bytes 10-build_abe-gdb/console.log.xz | Bin 37364 -> 37440 bytes 11-build_abe-qemu/console.log.xz | Bin 31908 -> 32388 bytes 12-check_regression/console.log.xz | Bin 3604 -> 4076 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 | 36 +++++++++---------- 19 files changed, 58 insertions(+), 58 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