Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-stable-allnoconfig updated (dd5ea4c1f8 -> 2dba47cd4a)

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-aarch64-stable-allnoconfig in repository toolchain/ci/base-artifacts. from dd5ea4c1f8 12: onsuccess: #405: boot: Success after binutils/gcc/linux/ [...] new 2dba47cd4a 13: onsuccess: #406: boot: Success after binutils/gcc/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1708 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30952 -> 30208 bytes 04-build_abe-stage1/console.log.xz | Bin 69280 -> 68700 bytes 05-build_abe-qemu/console.log.xz | Bin 31444 -> 32116 bytes 06-build_linux/console.log.xz | Bin 3964 -> 3284 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4140 -> 4200 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_kernel/llvm-master-aarch64-lts-allmodconfig updated (6affca3259 -> c536bc075e)

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-lts-allmodconfig in repository toolchain/ci/base-artifacts. from 6affca3259 22: onsuccess: #500: 37: Success after llvm: 12 commits new c536bc075e 23: onsuccess: #501: 37: Success after binutils/llvm/linux/q [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1684 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 30180 -> 30216 bytes 04-build_kernel_llvm/console.log.xz | Bin 63484 -> 66224 bytes 05-build_abe-qemu/console.log.xz | Bin 31252 -> 31800 bytes 06-build_linux/console.log.xz | Bin 4036 -> 4096 bytes 08-check_regression/console.log.xz | Bin 3068 -> 4528 bytes 08-check_regression/mail-body.txt | 9 --------- 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 | 11 +---------- mail/mail-subject.txt | 2 +- manifest.sh | 31 +++++++++++++++++-------------- 17 files changed, 25 insertions(+), 40 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/release-arm updated (7b19e369af -> d0c18842f9)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/release-arm in repository toolchain/ci/base-artifacts. from 7b19e369af 17: onsuccess: #176: 1: Success after binutils/gcc/gdb/qemu: [...] new d0c18842f9 18: onsuccess: #177: 1: Success after binutils/gcc/linux/gli [...] 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 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30040 -> 29944 bytes 04-build_abe-stage1/console.log.xz | Bin 86784 -> 86800 bytes 06-build_abe-linux/console.log.xz | Bin 8608 -> 8656 bytes 07-build_abe-glibc/console.log.xz | Bin 229364 -> 229660 bytes 08-build_abe-stage2/console.log.xz | Bin 220404 -> 221740 bytes 09-build_abe-gdb/console.log.xz | Bin 36844 -> 36588 bytes 10-build_abe-qemu/console.log.xz | Bin 30900 -> 31760 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3848 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2424 -> 2436 bytes 13-check_regression/console.log.xz | Bin 5772 -> 7468 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 26 + 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 72 +- 13-check_regression/results.regressions | 26 + dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +- results | 26 + sumfiles/g++.log.xz | Bin 2660488 -> 2674576 bytes sumfiles/g++.sum | 30 +- sumfiles/gcc.log.xz | Bin 2213664 -> 2192108 bytes sumfiles/gcc.sum | 2410 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 881620 -> 881280 bytes sumfiles/gfortran.sum | 16 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 195964 -> 196048 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429260 -> 421796 bytes sumfiles/libstdc++.sum | 18 +- 44 files changed, 1479 insertions(+), 1277 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_kernel/llvm-release-arm-next-allyesconfig updated (895bbe899a -> 3bdacdb03a)

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-next-allyesconfig in repository toolchain/ci/base-artifacts. from 895bbe899a 15: onsuccess: #349: 20954: Success after binutils/llvm/linu [...] new 3bdacdb03a 16: onsuccess: #350: 20983: 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 1716 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30396 -> 29872 bytes 04-build_kernel_llvm/console.log.xz | Bin 64372 -> 64252 bytes 05-build_abe-qemu/console.log.xz | Bin 31460 -> 31220 bytes 06-build_linux/console.log.xz | Bin 5844 -> 5716 bytes 08-check_regression/console.log.xz | Bin 4328 -> 4364 bytes 08-check_regression/mail-body.txt | 4 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 18 files changed, 29 insertions(+), 29 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 (23d8bda47a -> cd1d3dc030)

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 23d8bda47a 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] discards bd1dfe9057 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] discards 196a695d0c 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] discards 51e2ab23a7 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] discards 4564ada396 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] discards d64e6eefdd 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] discards 504d146467 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards 62a32d93a6 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 9d639ed0a4 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards be88b35496 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards 7ca50aaa2d 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards dc8a5a8722 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards 814ef567c2 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards 40f79e1b8d 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards 98dc547eec 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards 92569c0e4e 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards 2749749f2a 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards 555a25c1fc 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards 8497b1247e 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards 7f5873013e 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 8d0efa7cc1 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards d52d8ae693 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 18a927c389 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards f23ee1faef 132: onsuccess: #1645: 7: Success after linux: 23 commits discards b2000ab569 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards f1c8920699 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards dd8c58515a 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards d08ec090ac 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards e6955536bc 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards f3c7aef0a2 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 959b1637bd 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards 5733655264 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards ce019bd461 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards b855116e85 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 50596ef698 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards ab5087987f 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 5d03fb33ff 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 75e9d2fc31 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 1320ab0620 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 0049d2a33c 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards e35ee75fff 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards bfa01e9bc9 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 11cc3a610b 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards d55cd39f4b 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 097c4f1317 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 718085d095 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards c230b95375 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 1d0cd3007a 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards aa3442d744 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards dcfdc168b9 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards b40e480710 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards aa2dd8ec7b 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 4a8007bb0b 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 1bc1bf9843 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 6814a23fdc 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 9cc3b6bc7c 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards d3eca9139e 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 7cbad3a220 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards a41093a4d5 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards 2d3ecc880c 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards a0af6f81ff 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards 65ac1cc468 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards fd75cbae91 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards dafa7a9425 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards a01fe051a5 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 97a25ec627 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 9987b8feca 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 275b27477c 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards c7b909c75f 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 7c8475ae3b 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 1836d29fd4 85: onsuccess: 7: Success after gcc: 9 commits discards 7cefcb6d25 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 1d226837a1 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 216180d1f1 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards db1afba845 81: onsuccess: 7: Successful build after gcc: 2 commits discards 44afb099e3 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards c3ed4d84dc 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 47c4bca3e9 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ddf9b717da 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 35ddd4cab8 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 43951710c0 75: onsuccess: 7: Successful build after linux: 44 commits discards c9a0bc82da 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 09d07747fa 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 895a864236 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 2a6996bc68 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 20ef014f0c 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards ebce4357a7 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards c779c7ddff 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 86ff3cedc7 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards dffad8d835 66: onsuccess: 7: Successful build after gcc: 3 commits discards 34f33fc47b 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c4e540196f 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7f036f88d2 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 95cac1939e 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 2836b3a8c0 61: onsuccess: 4: Successful build after gcc: 15 commits discards e520de46b7 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards bcbc5d6a04 59: force: 7: Successful build after gcc: 2 commits discards b33764fcc5 58: onsuccess: 7: Successful build after glibc: 2 commits discards 70706f669a 57: onsuccess: 7: Successful build after gcc: 7 commits discards 668369e046 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 466d4cb0c0 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 627954a0be 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 67f35bb11d 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 1af97da021 57: onsuccess: 7: Successful build after gcc: 7 commits new b4b12de00d 58: onsuccess: 7: Successful build after glibc: 2 commits new 8f8ac02ec8 59: force: 7: Successful build after gcc: 2 commits new 2cdd019629 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new d8159120b0 61: onsuccess: 4: Successful build after gcc: 15 commits new 801c8879cf 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new cd2183cb63 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 94f29c0952 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 77b338c766 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 264e818ea8 66: onsuccess: 7: Successful build after gcc: 3 commits new e4240a704d 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new be37b6d6c6 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 992541897e 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 6619fa908a 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 14dfdb8349 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new a50613bde8 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 8ba2f9a9e7 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ba31b3fbd8 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 6a7abccaa0 75: onsuccess: 7: Successful build after linux: 44 commits new efbda1da5a 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2f0cdb48e0 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new fb3ae27480 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f9a9713737 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 42e5a73443 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new f889fcc440 81: onsuccess: 7: Successful build after gcc: 2 commits new 5d13c8b1f7 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new de7491ac6f 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 8e02269604 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 21a3236393 85: onsuccess: 7: Success after gcc: 9 commits new 631c0f8033 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 272d2abea3 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new b506e55a84 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new e7ddb66b4b 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new ce14c6d37d 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new b880738527 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 5090dfc09a 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 69620bd936 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new 58bae676cb 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new c4e5accfdd 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new da6efb947f 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 468dc8ba47 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new f9b99acf71 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new b5c38e9fe6 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 93bc58de6e 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new 0bde21774c 101: onsuccess: #1609: 7: Success after binutils: 78 commits new e03eda8831 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 408c617c0b 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 830edb590b 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new b7178a85f7 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new f2676eb0e5 106: onsuccess: #1617: 7: Success after gcc: 2 commits new bb96e74bb6 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 407944ff3b 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new e5418781c2 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 8d5f8a1a7c 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new d1416562e4 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 23268d734f 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 969cb91618 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 0020811527 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new dc3d305181 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 81da751eec 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new c225f56304 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new e1bbe81240 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 069c8ee768 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new e0ef7e239c 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 41177f5584 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new 85f675bab3 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 92871d6935 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 2d23b9b6ec 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 41a5da5b8f 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new 7542b75b8b 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new a455c61aae 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 35131f089b 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new ac7747a0e4 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 070971a1e6 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 7d0e08a1e8 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 73323a6bec 132: onsuccess: #1645: 7: Success after linux: 23 commits new e1875267f0 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new 6f0f717e8f 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new 7dd6764f31 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new 0d6b225315 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 9df2ff7ec0 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new 71ccc26b21 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new 27de09ba6a 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 3b27786536 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new 9b810befcd 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 20bb569de6 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 30469fc0af 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new 876e6dd44f 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new d0be6cbb7c 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new 7641615ead 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new 79a2917a44 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new 86d244cab1 148: onsuccess: #1663: 7: Success after glibc: 2 commits new c518e17024 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new 74931e38b8 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] new e32fbe7d30 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] new 9addbca9f4 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] new 5b75b5e95a 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] new 8eeae39a6e 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] new b38f38feb1 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] new cd1d3dc030 156: onsuccess: #1671: 7: Success after 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 (23d8bda47a) \ 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 1700 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 29664 -> 29880 bytes 05-build_abe-stage1/console.log.xz | Bin 90672 -> 91272 bytes 07-build_abe-linux/console.log.xz | Bin 8576 -> 8552 bytes 08-build_abe-glibc/console.log.xz | Bin 234356 -> 233688 bytes 09-build_abe-stage2/console.log.xz | Bin 223824 -> 224980 bytes 10-build_abe-gdb/console.log.xz | Bin 37240 -> 37200 bytes 11-build_abe-qemu/console.log.xz | Bin 31340 -> 31480 bytes 12-check_regression/console.log.xz | Bin 4316 -> 3236 bytes 13-update_baseline/console.log | 42 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 ++++++++++---------- 17 files changed, 38 insertions(+), 38 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_debug updated (2b77bbedc8 -> 01ee8c5995)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_debug in repository toolchain/ci/base-artifacts. from 2b77bbedc8 54: onsuccess: #443: 2: Success after binutils/gcc: 70 commits new 01ee8c5995 55: onsuccess: #444: 2: Success after binutils/gcc: 44 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1680 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2716 bytes 04-build_abe-binutils/console.log.xz | Bin 38852 -> 37912 bytes 05-build_abe-bootstrap_debug/console.log.xz | Bin 270532 -> 268332 bytes 06-check_regression/console.log.xz | Bin 3120 -> 3108 bytes 06-check_regression/mail-body.txt | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 13 files changed, 18 insertions(+), 18 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 (004a49bcd3 -> 423936e935)

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 004a49bcd3 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards c7f27ffa12 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] discards 274ae7a023 152: force: #1605: 7: Success after gcc: 9 commits discards 2842bc481f 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] discards 3f202981d1 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] discards a0e7ab4aa7 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards 465a495f48 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards 904d7c1437 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards 0f7fb94741 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards fc128d8b78 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards 2341dbe31b 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 155d676b99 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards 564924c90b 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards a32a770e64 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 5a2138b12e 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards 88e62445aa 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards 37cd6f0d19 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards 58b3d02c0d 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards fec6057633 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards d7aa2185f4 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards d86d38bade 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 86c2758959 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards 567e5ea927 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards 99e04dc2b1 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 91ffd0d840 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 84cb3f644c 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards d530175135 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 671958c438 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 98ca2d71d0 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards db871e5c98 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards b1321f25ca 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 67b9c78dd9 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards c23dbd135e 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 0788083ee8 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards 337ae95125 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards ebf4d60975 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 6b45abaa27 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards 8ef3abc5e8 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 8f371d992f 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 44928007a3 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards d0de182cbc 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards d700c4026a 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards f065017ae0 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards 0cde3dd95b 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 89893892ab 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards bfdf43eb0b 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards d4785a4cee 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 8d25ddef82 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 190f4158a6 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards f47d360b97 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards 67ec2ceb67 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards c01cb9d52c 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 9a050f23ce 102: force: #1551: 1: Failure after gcc: 306 commits discards 1406b6a760 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards b32c11dd98 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 37bda5fff6 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 21393194d0 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards d9ba8c0cba 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards d1a68a0974 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards df2f40cda1 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards acb1982c28 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 852d51ba71 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 633533068e 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 623252821d 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards ac55105442 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 1233ac4b9e 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards b7aec749ac 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 89b8261d4e 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards e2c166d34d 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 31344fdc73 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards b724be04ac 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 74feb20704 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9f9469154f 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 27137ac642 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b71ef982ee 80: onsuccess: 7: Successful build after linux: 44 commits discards f463802dde 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 633750aeeb 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards 35a44a3f07 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7b20421b16 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 6b1124bda5 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards dff83950a7 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 75a6ac00a4 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 02aadb216d 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0203295f2a 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 37b5b22787 70: onsuccess: 7: Successful build after gcc: 4 commits discards 912fd64c4c 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 1547c069b6 68: onsuccess: 7: Successful build after linux: 6 commits discards d898094ca2 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards d738de419a 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards d7b68b61d4 65: onsuccess: 7: Successful build after binutils: 3 commits discards 2d1d369039 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 30e3721045 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 1353e72aa0 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 5724cf5bd2 61: onsuccess: 4: Successful build after gcc: 5 commits discards 8889209de5 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 642a87b140 59: force: 7: Successful build after gcc: 3 commits discards 6dba4437f8 58: onsuccess: 7: Successful build after glibc: 2 commits discards 06f3bfed4f 57: onsuccess: 7: Successful build after gcc: 7 commits discards 22157db12c 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7242398605 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 43c056860c 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 3f02b9baeb 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 4814e8ebe9 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ba5a02ea29 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 0fd3b342f1 57: onsuccess: 7: Successful build after gcc: 7 commits new 442a1a2582 58: onsuccess: 7: Successful build after glibc: 2 commits new a1e74e687b 59: force: 7: Successful build after gcc: 3 commits new f1dfcadfaf 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 93337c3b23 61: onsuccess: 4: Successful build after gcc: 5 commits new e628353ae5 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new cd6b4a97d5 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 6f90d0b914 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new a82f34d42c 65: onsuccess: 7: Successful build after binutils: 3 commits new a9fb9ee174 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new ecb5e08d68 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new d868add1aa 68: onsuccess: 7: Successful build after linux: 6 commits new b4cac72e48 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7ba2b53333 70: onsuccess: 7: Successful build after gcc: 4 commits new f9a5fc79a9 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 8e8fe7a9e4 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 09c8cc3f2a 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4ec0a85c21 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 645c9be9d9 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new becd206a21 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 1fa90b445e 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a791f70b22 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new abfa216951 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 9814309a85 80: onsuccess: 7: Successful build after linux: 44 commits new ba5ab8179d 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 1a61f1b873 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 73f0638b1c 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e5b73c19d7 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new aa89750b4f 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 1785134ed0 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new a1b1014bb0 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 095984ba77 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 3069a60e99 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 3e62c0be7f 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 255b0ecbc9 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 8ad5c2f49b 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new dda8c43010 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new f279e72efe 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 7749c9aedd 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 9413415a86 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new b1819ce152 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new d6085ab9ca 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 08b70d3af8 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 41c77e18b2 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 3c74b1822f 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 389c86035e 102: force: #1551: 1: Failure after gcc: 306 commits new b5ace78c40 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 4b3c992906 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new a13c8f5374 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new f601cc4e34 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 322bd49e79 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new 2e8856c592 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new c2edbbd46b 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new f63a8679d5 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 5d142520f3 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new e873a9f428 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 905eab2877 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new 66ad76d031 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new b8e5479bee 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 8d081a8a33 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 48c8d34882 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new c8a2f5365b 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new d829680131 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new fbff942e6a 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 6e42257264 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 06ab988951 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 06c577dbe4 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new b77ec36499 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 0b4b10c64d 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 6c125fd272 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 2d7ea5129a 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new f14aeeae85 128: onsuccess: #1579: 7: Success after linux: 12 commits new 3a1994ae56 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new fd962234d7 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new dc3d1a6be4 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new bbdc87fec4 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 87f023a39e 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new 9ef655f5c4 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new 5ecd77450f 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new c4f3b66a36 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new 2e4a6d213c 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 1f1b0bc818 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new 96609aa3e9 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 98c239a86f 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new 9f8631e8a7 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new 31e8a1ce4a 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new 8f28a7ca31 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new 89704cab96 144: onsuccess: #1595: 7: Success after glibc: 2 commits new 82e8f8476d 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new 3d201ad9da 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new e7909c2728 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new 8c0b41f628 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new bac22a60af 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new e2d8a668b4 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] new fc66285472 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] new e40bdfe0fb 152: force: #1605: 7: Success after gcc: 9 commits new 3812cd38fe 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] new af6c05a11a 154: onsuccess: #1607: 1: Success after gcc: 2 commits new 423936e935 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] 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 (004a49bcd3) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1668 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 30108 -> 30208 bytes 05-build_abe-stage1/console.log.xz | Bin 41044 -> 72628 bytes 06-clean_sysroot/console.log.xz | Bin 0 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 0 -> 8548 bytes 08-build_abe-glibc/console.log.xz | Bin 0 -> 239352 bytes 09-build_abe-stage2/console.log.xz | Bin 0 -> 202836 bytes 10-build_abe-gdb/console.log.xz | Bin 0 -> 37392 bytes 11-build_abe-qemu/console.log.xz | Bin 0 -> 31872 bytes 12-check_regression/console.log.xz | Bin 2584 -> 4180 bytes 12-check_regression/mail-body.txt | 18 ++++++----- 13-update_baseline/console.log | 42 +++++++++++++------------- dashboard/dashboard-generate.sh | 2 +- dashboard/squad/score/results-functional.json | 1 + git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 20 +++++++----- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++++++++++----- results | 12 +++++++- 24 files changed, 91 insertions(+), 52 deletions(-) create mode 100644 06-clean_sysroot/console.log.xz create mode 100644 07-build_abe-linux/console.log.xz create mode 100644 08-build_abe-glibc/console.log.xz create mode 100644 09-build_abe-stage2/console.log.xz create mode 100644 10-build_abe-gdb/console.log.xz create mode 100644 11-build_abe-qemu/console.log.xz create mode 100644 dashboard/squad/score/results-functional.json -- 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_profiled updated (a3c81c8eaa -> 79a83a8ed9)

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_profiled in repository toolchain/ci/base-artifacts. from a3c81c8eaa 48: onsuccess: #444: 2: Success after binutils/gcc: 39 commits new 79a83a8ed9 49: onsuccess: #445: 2: Success after binutils/gcc: 56 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1680 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 50616 -> 50808 bytes 05-build_abe-bootstrap_profiled/console.log.xz | Bin 932944 -> 933068 bytes 06-check_regression/console.log.xz | Bin 2972 -> 3184 bytes 06-check_regression/mail-body.txt | 2 +- 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 | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 14 files changed, 18 insertions(+), 27 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 (8e8c69e1b8 -> 6caed188f4)

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 8e8c69e1b8 148: onsuccess: #2082: 1: Success after gdb-12-branchpoint-2 [...] discards b5961e2272 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 commits discards bf3994e9e7 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits discards aa89622928 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits discards 0c64ca336e 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits discards 8a28364cd5 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits discards 412687a309 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits discards 0d1c16e363 141: onsuccess: #2073: 1: Success after binutils: 3 commits discards 5486d17b3f 140: onsuccess: #2070: 1: Success after binutils: 4 commits discards aab7056a9b 139: onsuccess: #2067: 1: Success after binutils: 2 commits discards 239ebfbcdd 138: onsuccess: #2064: 1: Success after binutils: 4 commits discards 0fc6b0f62c 137: onsuccess: #2061: 1: Success after binutils: 2 commits discards ff4d81de9a 136: onsuccess: #2056: 1: Success after binutils: 4 commits discards 60c87c0ba6 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits discards b1d8fd0763 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits discards d2075ee067 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits discards d0ae765b84 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits discards 1041e3eba4 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] discards ace1cc2ab9 130: onsuccess: #2049: 1: Success after gcc: 9 commits discards 58252e1d37 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] discards ee52dab529 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] discards 0d1b0fed16 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] discards 3f1e6a1331 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] discards 44d715369a 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits discards 27bda6db6e 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits discards 124ab0484a 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits discards 636c752aa7 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits discards fec982af41 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits discards 38cc3d7db3 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits discards a0e4d5ea93 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits discards 8485ae37b1 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits discards 851f4501c6 117: onsuccess: #2034: 1: Success after binutils: 2 commits discards 2618173ae0 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits discards d787bbd23c 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits discards a128395bc6 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits discards 9e2f593b27 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits discards 9f0581e245 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits discards 49b18f67c0 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits discards 721ed5c435 110: onsuccess: #2027: 1: Success after gcc: 5 commits discards bab6b8e46b 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits discards 709903bf6e 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits discards 644c966117 107: onsuccess: #2024: 1: Success after gcc: 3 commits discards 30c070a3c9 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits discards 16e33a3e05 105: onsuccess: #2022: 1: Success after gcc: 4 commits discards acc5b87a7c 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards 08a42cc0a4 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards 7e31178459 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] discards 1c8026e49a 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards 01e85f69bf 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards 40c456a980 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards 92676ae38b 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards 4cdfe79ed5 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards 5efb38c723 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] discards 5fe1a6c119 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] discards dfa81ce217 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards 328955d441 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] discards a06523037f 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards 4b693535fd 91: onsuccess: 1: Success after gcc: Daily bump. discards 14ec5f6592 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards 2f803c605d 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards 7c4fc886fe 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards 2e8d90260d 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards ee9d465292 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards 3030cfa285 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards 62499e39bf 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards f2e53d9e26 83: onsuccess: 1: Success after gcc: 8 commits discards 6fdbb4a90d 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards c1ffd845da 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards d63c8c842f 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards 196873134c 79: onsuccess: 1: Successful build after gcc: Daily bump. discards 7e4cf51c26 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 70365e7a8e 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 0446ba0171 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 05577e9b9b 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 46ff1a4b34 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards 1bcdb4045e 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards 5467d8088f 72: onsuccess: 1: Successful build after gcc: 2 commits discards f4308ea64e 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 1101eb00ab 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards 2467c20fb0 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 6aa850c528 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 96eb82d06c 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 41c426716a 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 890ba6db22 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 5f77499030 64: onsuccess: 1: Successful build after gcc: 5 commits discards cc71966ca3 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 7ed39874d7 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards a62d5cafdb 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits discards 17e486225b 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 46cf9f8a78 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits discards 6ca4795b41 58: onsuccess: 1: Successful build after binutils: 2 commits discards 50b43cf78a 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards d4c8447c75 56: onsuccess: 1: Successful build after gcc: Daily bump. discards 3dec0958af 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 76eab3b7ac 54: onsuccess: 1: Successful build after gcc: 7 commits discards 45e5770a21 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 9b360aba82 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards bd6708fef5 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards f2a8096e37 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 8976443778 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards ca15b3c691 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 2d20d9725d 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits new e9e23214e0 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits new c634618510 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 4108636b90 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 4110966e2b 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 3267329082 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 924d7077a5 54: onsuccess: 1: Successful build after gcc: 7 commits new 16f6f9ca0e 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 1ebb543b1b 56: onsuccess: 1: Successful build after gcc: Daily bump. new 6c94a34241 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits new b9af89f194 58: onsuccess: 1: Successful build after binutils: 2 commits new 3af83067d0 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits new 831e61521d 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits new def61cd748 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits new 7cd405d27b 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits new ca61e65cd9 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits new c3eb431219 64: onsuccess: 1: Successful build after gcc: 5 commits new ad94635822 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 09bd341419 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new eff5b649f2 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new b890183fe8 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new d48f494767 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] new ebc2cd46b1 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new e47adb9114 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 90eb8b79ca 72: onsuccess: 1: Successful build after gcc: 2 commits new 6b6c96970f 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 15014f4ce7 74: onsuccess: 1: Successful build after binutils: Automatic [...] new 0a8eaa4d6c 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new c141be188e 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 0aa9cf1d41 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 30359863bd 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 0711d02b28 79: onsuccess: 1: Successful build after gcc: Daily bump. new c99a3c5477 80: onsuccess: 1: Success after binutils/gcc: 14 commits new 2cd170aa13 81: onsuccess: 1: Success after binutils/gcc: 27 commits new 769b232e29 82: onsuccess: 1: Success after binutils/gcc: 10 commits new 8b2168e113 83: onsuccess: 1: Success after gcc: 8 commits new 2ab8809d11 84: onsuccess: 1: Success after binutils/gcc: 9 commits new 389752f0c7 85: onsuccess: 1: Success after binutils/gcc: 9 commits new f9a5c61040 86: onsuccess: 1: Success after binutils/gcc: 13 commits new a14c1bb852 87: onsuccess: 1: Success after binutils/gcc: 4 commits new 4f9f4dcd9c 88: onsuccess: 1: Success after binutils/gcc: 16 commits new 31f3ed4f75 89: onsuccess: 1: Success after binutils/gcc: 9 commits new 6bb2cff445 90: onsuccess: 1: Success after binutils/gcc: 6 commits new d6034b53c1 91: onsuccess: 1: Success after gcc: Daily bump. new 201c177a50 92: onsuccess: #1965: 1: Success after gcc: 2 commits new a414d52656 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] new b278f546a1 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new bffcffa282 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] new c58a6d256c 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] new 1adee3c207 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new 88da88779c 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new c95f13ae56 99: onsuccess: #1974: 1: Success after gcc: 14 commits new 4b861ab015 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new 964696e49f 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new 095b33ff51 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] new 1708f28f20 103: onsuccess: #2020: 1: Success after gcc: 2 commits new 2eb552825a 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new 67e8fbc627 105: onsuccess: #2022: 1: Success after gcc: 4 commits new d744c69b64 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits new 0825d5d130 107: onsuccess: #2024: 1: Success after gcc: 3 commits new eb432b7b15 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits new 5240a32e18 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits new 5929b8e85e 110: onsuccess: #2027: 1: Success after gcc: 5 commits new 979d88fb21 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits new d0ad41dc82 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits new e4df43a811 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits new 3257135e89 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits new ac487f9600 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits new c056e228f3 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits new ce47f85448 117: onsuccess: #2034: 1: Success after binutils: 2 commits new ef98d3ec82 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits new 9e06d66204 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits new b2d503b2ee 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits new 7950f191a8 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits new f0105d2021 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits new a9b4ddd419 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits new 5246064dab 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits new 988ecd6e47 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits new 3b43a874ab 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] new ce19c7ab45 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] new 79842cb0d6 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] new 7e89f65b5d 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] new 82254f8f13 130: onsuccess: #2049: 1: Success after gcc: 9 commits new 303f121f52 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] new efbbadb893 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits new 6098c5b2b9 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits new bfa63b594b 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits new c12104171b 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits new ea84e61d05 136: onsuccess: #2056: 1: Success after binutils: 4 commits new 503f45b7a0 137: onsuccess: #2061: 1: Success after binutils: 2 commits new ba6992f4ab 138: onsuccess: #2064: 1: Success after binutils: 4 commits new 216a0e86aa 139: onsuccess: #2067: 1: Success after binutils: 2 commits new e0ba90ac76 140: onsuccess: #2070: 1: Success after binutils: 4 commits new 78af0c1711 141: onsuccess: #2073: 1: Success after binutils: 3 commits new 538eebe76f 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits new 64fd7314b9 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits new 781e8ebce2 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits new e53809ef24 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits new 074d685fc1 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits new 822c4c6caa 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 commits new 0dae795902 148: onsuccess: #2082: 1: Success after gdb-12-branchpoint-2 [...] new 6caed188f4 149: onsuccess: #2084: 1: Success after 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 (8e8c69e1b8) \ 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 1732 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 37916 -> 38092 bytes 04-build_abe-gcc/console.log.xz | Bin 212128 -> 214084 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3832 bytes 06-build_abe-check_gcc/console.log.xz | Bin 3124 -> 2792 bytes 07-check_regression/console.log.xz | Bin 4276 -> 4948 bytes 07-check_regression/mail-body.txt | 26 - 07-check_regression/results.compare | 30 +- 07-check_regression/results.compare2 | 33 +- 08-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 15 +- sumfiles/g++.log.xz | Bin 3584556 -> 3580332 bytes sumfiles/g++.sum | 138 +- sumfiles/gcc.log.xz | Bin 3094228 -> 3113216 bytes sumfiles/gcc.sum | 4779 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1040804 -> 1041932 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2192 -> 2188 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207424 -> 207708 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2540 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 451140 -> 449568 bytes sumfiles/libstdc++.sum | 19 +- 31 files changed, 2586 insertions(+), 2598 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 (c7ab88043c -> 1486117156)

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 c7ab88043c 48: onsuccess: #563: 1: Success after binutils/gcc: 149 commits new 1486117156 49: onsuccess: #564: 1: Success after binutils/gcc: 45 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 1692 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 50696 -> 52572 bytes 04-build_abe-bootstrap/console.log.xz | Bin 465760 -> 468140 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3796 -> 3820 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2656 -> 2752 bytes 07-check_regression/console.log.xz | Bin 9848 -> 6080 bytes 07-check_regression/extra-bisect-params | 1 - 07-check_regression/fails.sum | 13 - 07-check_regression/mail-body.txt | 22 +- 07-check_regression/results.compare | 75 +- 07-check_regression/results.compare2 | 1291 ++----- 07-check_regression/results.regressions | 76 - dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 24 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 76 - sumfiles/g++.log.xz | Bin 2865152 -> 2839556 bytes sumfiles/g++.sum | 265 +- sumfiles/gcc.log.xz | Bin 2471332 -> 2516348 bytes sumfiles/gcc.sum | 4951 ++++++++++++++------------- sumfiles/gfortran.log.xz | Bin 945864 -> 952396 bytes sumfiles/gfortran.sum | 52 +- sumfiles/libatomic.log.xz | Bin 2304 -> 2308 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 211880 -> 211408 bytes sumfiles/libgomp.sum | 59 +- sumfiles/libitm.log.xz | Bin 2720 -> 2728 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 477704 -> 478236 bytes sumfiles/libstdc++.sum | 10 +- 35 files changed, 3018 insertions(+), 3937 deletions(-) delete mode 100644 07-check_regression/extra-bisect-params delete mode 100644 07-check_regression/fails.sum delete mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022