Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-mainline-allyesconfig updated (c470313e21 -> da67ebfe46)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from c470313e21 12: onsuccess: #378: all: Success after binutils/llvm/linux/ [...] new da67ebfe46 13: onsuccess: #379: 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 1692 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30196 -> 30476 bytes 04-build_kernel_llvm/console.log.xz | Bin 64744 -> 64784 bytes 05-build_abe-qemu/console.log.xz | Bin 31188 -> 31864 bytes 06-build_linux/console.log.xz | Bin 3088 -> 3080 bytes 07-boot_linux/console.log.xz | Bin 576 -> 576 bytes 08-check_regression/console.log.xz | Bin 3192 -> 3384 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 17 files changed, 23 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-next-allnoconfig updated (e660aaac0d -> 0051b84a58)

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-next-allnoconfig in repository toolchain/ci/base-artifacts. from e660aaac0d 9: onsuccess: #398: boot: Success after binutils/gcc/linux: [...] new 0051b84a58 10: onsuccess: #400: 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 1704 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30004 -> 30492 bytes 04-build_abe-stage1/console.log.xz | Bin 68532 -> 68416 bytes 05-build_abe-qemu/console.log.xz | Bin 32008 -> 31484 bytes 06-build_linux/console.log.xz | Bin 3032 -> 3036 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 2768 -> 3276 bytes 08-check_regression/mail-body.txt | 2 +- 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 | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 18 files changed, 25 insertions(+), 25 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap updated (65dde5ac58 -> 9fa00d6b4c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap in repository toolchain/ci/base-artifacts. discards 65dde5ac58 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards cc3ac33d31 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards b492fe5c3e 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards bdfb4358d1 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards 60cfa05bdf 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards d851341fb9 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards 5a2e947e17 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards f882f7424d 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards 80cf0df6ab 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards 68ce1e399b 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards 048313f506 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards 3cbfd5b18a 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards 9479868109 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards e24c57bcf5 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards 88a8db1c8d 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards 5cbd080a2f 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards eae8e2b4d4 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards 2b3cfcb1de 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 0328e5271e 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards f0315c5e3a 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards 479af873aa 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards be8ceaa396 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards 84d2ec5172 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards 03bb3b47d8 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 4c4aebf0fc 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 45c6266568 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards 0852ad3c86 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards 6ba3c85b42 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards 35267f2dc8 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards 5c487e0603 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards 55a2ac5728 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards dfaf6e3b2d 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards f2bbcdcd2e 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards 0e1c940000 87: onsuccess: 2: Success after gcc: 4 commits discards bf09fceecb 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards 4dbc934001 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 95ea1f1209 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 66bc61f7f5 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 876fc20ecb 82: onsuccess: 1: Successful build after gcc: 3 commits discards ef645c2f0e 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 3293336af3 80: force: 2: Successful build after gcc: 14 commits discards c7993562b3 79: onsuccess: 2: Successful build after binutils: 5 commits discards 2426b94f2c 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards 34528cd3b7 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 149f1ba739 76: onsuccess: 2: Successful build after gcc: 12 commits discards 4fdb074cd0 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards e62ec81d93 74: onsuccess: 2: Successful build after baseline build: no [...] discards d2bcebbcfc 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 67213809df 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards ad8c675ddb 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 201c82637b 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 0ab502b128 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards f2240d3ac5 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards d43bcd5e7a 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 17f30767de 66: onsuccess: 2: Successful build after gcc: 9 commits discards 6593753515 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 43bf372690 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 6cdb5646f0 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards db119d841c 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 3cc47dca53 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards 7fae6fb0d0 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards 39edcdb691 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 17bc1b4e56 58: force: 2: Successful build after gcc: 6 commits discards 8891e41632 57: onsuccess: 2: Successful build after binutils: gdb: new [...] discards 7ae64b3dc5 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards d4f7ccf79b 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 2094ac45b2 54: onsuccess: 2: Successful build after gcc: 5 commits discards 7f882158f1 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 56ffeb8162 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards b4f9d5ee82 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 59eba7e46e 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 2cdac51e70 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 7778bb4472 48: onsuccess: 2: Successful build after gcc: 4 commits discards 79e4b71a13 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 3add412b14 46: onsuccess: 2: Successful build after baseline build: no [...] discards 0e6b9dae8c 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards 5fa15310ac 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards a628a14891 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards b872455078 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] discards 81cbf3afc2 41: onsuccess: 2: Successful build after gcc: libcpp: Implem [...] discards 9d76e73db3 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 14505038a7 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 1d8e56f283 38: onsuccess: 2: Successful build after gcc: 2 commits discards c7bd36d99d 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 3b5eec8316 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 575bfd150f 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 65ec1aec6a 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 4374d29565 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 476fef12b2 32: onsuccess: 2: Successful build after gcc: 6 commits discards 0ecb1c583d 31: onsuccess: 2: Successful build after gcc: 6 commits discards bc7008d7bd 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 6043bef12a 29: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards efc86aaecb 28: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards c81babf0fb 27: onsuccess: 2: Successful build after binutils/gcc: 14 commits discards 4afbe7c2fc 26: onsuccess: binutils-gcc: 2 discards 602dabc8a5 25: onsuccess: binutils-gcc: 2 discards af131eaefb 24: onsuccess: binutils-gcc: 2 discards 28dbc55d0d 23: onsuccess: binutils-gcc: 2 discards 01be3fb817 22: onsuccess: binutils-gcc: 2 discards c0dbbd474f 21: onsuccess: binutils-gcc: 2 discards 73bddbdcfa 20: onsuccess: binutils-gcc: 2 new 53269be05d 20: onsuccess: binutils-gcc: 2 new 1141cdefb5 21: onsuccess: binutils-gcc: 2 new 24f9a3e8e4 22: onsuccess: binutils-gcc: 2 new 0f2dc29825 23: onsuccess: binutils-gcc: 2 new fb0f908e81 24: onsuccess: binutils-gcc: 2 new 06af349081 25: onsuccess: binutils-gcc: 2 new 5b54f8a6df 26: onsuccess: binutils-gcc: 2 new 1de25ee363 27: onsuccess: 2: Successful build after binutils/gcc: 14 commits new 421aeac802 28: onsuccess: 2: Successful build after binutils/gcc: 8 commits new e1dbbe5695 29: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ad2b545ce4 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits new d541c9aecd 31: onsuccess: 2: Successful build after gcc: 6 commits new 9a480c158b 32: onsuccess: 2: Successful build after gcc: 6 commits new f2617482cc 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 2aa8928007 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 212933343f 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits new cc11305685 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 53c00b9fd0 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 81feae2997 38: onsuccess: 2: Successful build after gcc: 2 commits new af3915d01e 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 07be88a367 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 6594fb9540 41: onsuccess: 2: Successful build after gcc: libcpp: Implem [...] new 720caf5cf8 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] new a03ef7f243 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new e9503f931d 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 21b0ec8e75 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 44a9872192 46: onsuccess: 2: Successful build after baseline build: no [...] new 2621c7fed1 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits new ace43b4b56 48: onsuccess: 2: Successful build after gcc: 4 commits new fbba73c627 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 7dcfb7c7d0 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new d049d545ba 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 2425e15d41 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new a7b0da1e79 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 268d1700f2 54: onsuccess: 2: Successful build after gcc: 5 commits new 47e0801f6c 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 211453d88e 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 757d78d5c1 57: onsuccess: 2: Successful build after binutils: gdb: new [...] new ce23ffd9de 58: force: 2: Successful build after gcc: 6 commits new 27b40110b5 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new f65c208e8c 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 35c376db87 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new 82975a7cc2 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 015abfd73e 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new f101a5e846 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 4a817a36d3 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 73e2799374 66: onsuccess: 2: Successful build after gcc: 9 commits new 1e1e1d6808 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 1f682aa7c5 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new ca52da52e8 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new dc997508a5 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 01c49d818d 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 4c3027ebe2 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 486163667f 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 9f747561f0 74: onsuccess: 2: Successful build after baseline build: no [...] new 41821acb99 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 03031124ef 76: onsuccess: 2: Successful build after gcc: 12 commits new 7428f92c34 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new f06dce2f85 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new cea4b5ecb8 79: onsuccess: 2: Successful build after binutils: 5 commits new 5f69ff994f 80: force: 2: Successful build after gcc: 14 commits new 08143f8ea4 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new b6855bbc9a 82: onsuccess: 1: Successful build after gcc: 3 commits new c66be07d55 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new a9a54d73c9 84: onsuccess: 2: Success after binutils/gcc: 15 commits new 5845976a04 85: onsuccess: 2: Success after binutils/gcc: 25 commits new 079b6c9bf8 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 52c6e89bbf 87: onsuccess: 2: Success after gcc: 4 commits new 254dab8da9 88: onsuccess: 2: Success after binutils/gcc: 25 commits new 4f760ea871 89: onsuccess: 2: Success after binutils/gcc: 4 commits new abdc5d78eb 90: onsuccess: 2: Success after binutils/gcc: 16 commits new e2674f2968 91: onsuccess: 2: Success after binutils/gcc: 7 commits new d59ec5c06d 92: onsuccess: 2: Success after binutils/gcc: 9 commits new bae7187490 93: onsuccess: 2: Success after binutils/gcc: 3 commits new 2e86461e52 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new 50556255ab 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new e7655de579 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 05ca6549a7 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new 8b25b7f225 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new dffc0f6db4 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new 23a24e0e60 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 66ae4543bd 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new 3fe6b647ee 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new 2cb997b1cc 103: onsuccess: #1504: 2: Success after gcc: 2 commits new a939047858 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new 7f6b2a2d06 105: onsuccess: #1506: 2: Success after gcc: 2 commits new d271ea26e0 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 45926a5fe0 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new 5756cd1b81 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 505f2ed2bd 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new aff9863012 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new 2a93046dc4 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new d10266261c 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new 0255288311 113: onsuccess: #1514: 2: Success after gcc: 5 commits new fa0a292c60 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new bbb26a506e 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new e5a66b8973 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new 34ac7708b7 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 6867d0a7d2 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new 53c6e08389 119: onsuccess: #1520: 2: Success after binutils: 8 commits new 4203e35508 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new 9fa00d6b4c 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 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 (65dde5ac58) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1668 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 51056 -> 50968 bytes 05-build_abe-bootstrap/console.log.xz | Bin 465700 -> 468012 bytes 06-check_regression/console.log.xz | Bin 1888 -> 2128 bytes 07-update_baseline/console.log | 62 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 ++++----- 13 files changed, 45 insertions(+), 45 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[binutils-gdb] branch master updated (9c5f314314e -> 7abc6ec0a6f)

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 binutils-gdb. from 9c5f314314e gdb/testsuite: Add test to step through function epilogue new 7abc6ec0a6f gdb/python: restrict the names accepted by gdb.register_win [...] 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: gdb/NEWS | 5 ++ gdb/doc/python.texi | 4 +- gdb/testsuite/gdb.python/tui-window-names.exp | 84 +++++++++++++++++++++++++++ gdb/tui/tui-layout.c | 13 +++++ 4 files changed, 105 insertions(+), 1 deletion(-) create mode 100644 gdb/testsuite/gdb.python/tui-window-names.exp -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (8ebbee122f -> ec027cc4a1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. from 8ebbee122f 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new ec027cc4a1 43: onsuccess: #550: 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 1680 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 38220 -> 37808 bytes 04-build_abe-gcc/console.log.xz | Bin 212960 -> 213596 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8504 -> 8600 bytes 07-build_abe-glibc/console.log.xz | Bin 240188 -> 240660 bytes 08-build_abe-gdb/console.log.xz | Bin 37956 -> 37760 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3832 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2380 -> 2384 bytes 11-check_regression/console.log.xz | Bin 5264 -> 5220 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +-- sumfiles/binutils.log.xz | Bin 58500 -> 58168 bytes sumfiles/binutils.sum | 60 ++--- sumfiles/gas.log.xz | Bin 81168 -> 81072 bytes sumfiles/gas.sum | 268 +++++++++++----------- sumfiles/ld.log.xz | Bin 121328 -> 121132 bytes sumfiles/ld.sum | 342 ++++++++++++++--------------- 29 files changed, 369 insertions(+), 369 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-norov-defconfig updated (811abe7be6 -> 72dda7e3de)

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-defconfig in repository toolchain/ci/base-artifacts. from 811abe7be6 10: onsuccess: #54: boot: Success after binutils/llvm/qemu: [...] new 72dda7e3de 11: onsuccess: #55: boot: Success after binutils/llvm/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1712 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30208 -> 30628 bytes 04-build_kernel_llvm/console.log.xz | Bin 63300 -> 63840 bytes 05-build_abe-qemu/console.log.xz | Bin 31572 -> 31500 bytes 06-build_linux/console.log.xz | Bin 3500 -> 3496 bytes 07-boot_linux/console.log.xz | Bin 6260 -> 6280 bytes 08-check_regression/console.log.xz | Bin 2976 -> 3376 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 18 files changed, 27 insertions(+), 27 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (2372f0fa8e -> 92e78da9ba)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards 2372f0fa8e 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards c040422e7d 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 304fcf8a89 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards d9d565a8a1 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 701e26035f 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 8f039ea1a8 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 08bc6a7180 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 834b6277ba 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards b6ae48c3a2 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards d764dd4c4e 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 7312d445c5 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 575ca6dca2 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards f0797fe2d2 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards fdf8468266 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards b1a22d329e 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 8e85ee96d1 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 20126e09af 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 44233cc7dc 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 89b26baea5 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 0387bccd16 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards ca377744ba 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 8ca4577497 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards b1873dc420 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 9cc2a212cf 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 0703c62a5f 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards cdebd7243f 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards d6bfd23fad 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 46300ab7d6 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards aa84558d03 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 16d045c1f2 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 0758b62ed9 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 1f1c000ba2 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 2ef0a0b17d 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 55ff771f85 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards d07739e823 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 62777da00a 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 358b9d694f 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 4cd92e5319 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards d6d0c8d6b7 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 688a30a9d8 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 294bd4eef4 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5e7a232c42 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 9914f614de 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6af7a63158 74: onsuccess: 1: Successful build after linux: 44 commits discards a93dfd3a4c 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 161f0b0fee 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6048bbed2d 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards ade457bcd9 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards d889bb7914 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards dd0f1ed12c 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d3208856f8 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e12df93926 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0d8bbdbfb1 65: onsuccess: 1: Successful build after gcc: 4 commits discards caf5fe2cbd 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b76f299a55 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 49e75038d5 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 8c16362f35 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 33dd0a0c0a 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards cb8d7c502e 59: onsuccess: 1: Successful build after glibc: 2 commits discards c2c6da9330 58: onsuccess: 1: Successful build after binutils: 2 commits discards cff3d5f2ad 57: onsuccess: 1: Successful build after gcc: 7 commits discards 5291435034 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 43049cb4c2 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e407ea9769 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards aecdbf064b 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards c473e7cdcb 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 3a421b6e4d 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 635bad3553 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e86f15bb92 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 33a9dd23d3 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 59ea8af1e9 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5b471d52b1 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 48a25e7c24 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6d9b680a33 44: onsuccess: 1: Successful build after linux: 34 commits discards 9bc7f7a6f1 43: onsuccess: 1: Successful build after gcc: 2 commits discards 5a64154055 42: onsuccess: 1: Successful build after baseline build: no [...] discards c5603f6a6a 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9754dfaa17 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e236d677c8 39: onsuccess: 1: Successful build after gcc: 2 commits discards cfb55610af 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 24b7e5e09b 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 1c6406344d 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2ac8ae3d9d 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7a146f260e 34: onsuccess: 1: Successful build after gcc: 3 commits discards 99db62b9a5 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cd0ad42f4b 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 5953d169bb 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ff45e3063a 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards 82eb75f1db 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f04c2546d0 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards f892f4bec4 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 612301f775 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6f1705793f 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 73f6962919 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards df9fcd351d 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 60ccc6d0b2 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards bb1580caac 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 64b7c08dbd 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 0ddd688cda 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9d9a62b50d 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 56938f3961 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d948876a43 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7b881017fd 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e904360240 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c6f7da602e 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 45f3f2c50c 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bfb9e172cb 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4ff9bf1853 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new dd962e834e 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d5a7421770 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8f0da9d19e 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bb3a786868 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0219b582a8 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 2064a10c4b 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 23b5718d9e 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new fc6ba821c0 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 688e88adba 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new e6e55b447a 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0ad96e77e7 34: onsuccess: 1: Successful build after gcc: 3 commits new 7cbcd2b741 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 7df5a5c0c1 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3818138c33 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 21b73198c9 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7ba150a97d 39: onsuccess: 1: Successful build after gcc: 2 commits new 7a17cffb2f 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1069f85801 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 517dad31c9 42: onsuccess: 1: Successful build after baseline build: no [...] new a3308d4481 43: onsuccess: 1: Successful build after gcc: 2 commits new 38491c21f0 44: onsuccess: 1: Successful build after linux: 34 commits new a715394b37 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3a2842c188 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 1db8482bf1 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 588600ccc9 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 69c8c7f8e0 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new bc4a3d07b4 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4c1f8280c2 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 53c4045ee8 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 16dea68c01 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new be44f4e9d9 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 79c43450b8 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d761aacdae 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0861361722 57: onsuccess: 1: Successful build after gcc: 7 commits new bcbc1569a3 58: onsuccess: 1: Successful build after binutils: 2 commits new fb3cb6f818 59: onsuccess: 1: Successful build after glibc: 2 commits new cde0892cc8 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 4c6f477672 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 69af3079fc 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 1263774490 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new acff7919c3 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 26256efc24 65: onsuccess: 1: Successful build after gcc: 4 commits new ef0df15bb5 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4e1123edc2 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c7016c4c01 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new da368d2445 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new dd08703d39 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new d934242517 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new be41052664 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 53fc45885f 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new f69cfa089f 74: onsuccess: 1: Successful build after linux: 44 commits new 485409970a 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b5120a0559 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 45ed3070a4 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e35422d0ca 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b38fe65826 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 62bf2d0fe4 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new ebe94f93e3 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 9171959b6f 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new e0a1250b8e 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 8036372e53 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 0b4a9d3f94 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 874e177733 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 76bfeab4ce 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new dd7dd00e2c 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 347fd28641 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 25517ec4a1 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 34409ebc6e 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 5fbe2cb755 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 6d54a0ea2f 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new a80cf3b0cb 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 19fb2ffa3f 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 7f0d0cd48c 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 467ca08031 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new ea4b07ecab 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 194c636aa8 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 6cc8facd70 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 24d8cfb1fd 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 929d552e48 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 7745bb3632 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 48436c5297 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 78d2df76d2 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 44f47e2b9c 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 7d359056c8 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 6983c87402 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 534753df5d 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 9ddf15528c 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 0bbccd5494 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new ab9460b1d9 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 4cb2478226 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 394aafc0c0 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 736a47c08d 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 1329681a0b 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new d8412657e0 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 92e78da9ba 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (2372f0fa8e) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1700 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 29904 -> 29980 bytes 04-build_abe-stage1/console.log.xz | Bin 90852 -> 90780 bytes 06-build_abe-linux/console.log.xz | Bin 8592 -> 8564 bytes 07-build_abe-glibc/console.log.xz | Bin 234112 -> 233976 bytes 08-build_abe-stage2/console.log.xz | Bin 223148 -> 223588 bytes 09-build_abe-gdb/console.log.xz | Bin 37108 -> 37092 bytes 10-build_abe-qemu/console.log.xz | Bin 31488 -> 31536 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3844 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2444 -> 2580 bytes 13-check_regression/console.log.xz | Bin 4908 -> 4288 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 20 +- 14-update_baseline/console.log | 36 +- 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 | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- sumfiles/g++.log.xz | Bin 2686320 -> 2658324 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 2197952 -> 2233248 bytes sumfiles/gcc.sum | 2184 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 891892 -> 882700 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201156 -> 201220 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 421040 -> 424220 bytes sumfiles/libstdc++.sum | 8 +- 38 files changed, 1173 insertions(+), 1247 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[binutils-gdb] branch master updated (b59f8a90ba0 -> 9c5f314314e)

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 binutils-gdb. from b59f8a90ba0 ld/testsuite: allow to force another directory for gcc linker new 07bb02de723 gdb/testsuite: Add a proc to test where compiler links the [...] new d5bcff0343a Change gdb.base/skip-solib.exp deal with lack of epilogue i [...] new 4037b4191a0 gdb/testsuite: fix testing gdb.base/skip-inline.exp with clang new 8d215439f66 gdb/testsuite: fix gdb.base/msym-bp-shl when running with Clang new 53d4a55bebf fix gdb.base/jit-elf.exp when testing with clang new 7e1cd467b5c gdb.base/skip.exp: Use finish to exit functions new 9c5f314314e gdb/testsuite: Add test to step through function epilogue The 7 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: gdb/testsuite/gdb.base/jit-elf.exp | 2 +- gdb/testsuite/gdb.base/msym-bp-shl-main-2.c | 2 +- gdb/testsuite/gdb.base/skip-inline.exp | 107 ++++++++++++--------- gdb/testsuite/gdb.base/skip-solib-lib.c | 3 +- gdb/testsuite/gdb.base/skip-solib-main.c | 3 +- gdb/testsuite/gdb.base/skip.exp | 34 +++---- .../gdb.base/{return.c => step-through-epilogue.c} | 37 +++---- gdb/testsuite/gdb.base/step-through-epilogue.exp | 98 +++++++++++++++++++ gdb/testsuite/lib/gdb.exp | 32 ++++++ 9 files changed, 228 insertions(+), 90 deletions(-) copy gdb/testsuite/gdb.base/{return.c => step-through-epilogue.c} (72%) create mode 100644 gdb/testsuite/gdb.base/step-through-epilogue.exp -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-next-allnoconfig updated (5a80c32f17 -> 4ddf09ee91)

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-allnoconfig in repository toolchain/ci/base-artifacts. from 5a80c32f17 9: onsuccess: #307: all: Success after binutils/llvm/linux: [...] new 4ddf09ee91 10: onsuccess: #309: 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 1700 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 29848 -> 30024 bytes 04-build_kernel_llvm/console.log.xz | Bin 62720 -> 62844 bytes 05-build_abe-qemu/console.log.xz | Bin 30988 -> 31312 bytes 06-build_linux/console.log.xz | Bin 3156 -> 3140 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 2832 -> 3324 bytes 08-check_regression/mail-body.txt | 2 +- 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 | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 18 files changed, 25 insertions(+), 25 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-lts-allmodconfig updated (43527c39b9 -> 3e12e57a75)

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-lts-allmodconfig in repository toolchain/ci/base-artifacts. from 43527c39b9 12: onsuccess: #419: boot: Success after binutils/gcc/linux/ [...] new 3e12e57a75 13: onsuccess: #420: 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 1692 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30092 -> 30568 bytes 04-build_abe-stage1/console.log.xz | Bin 68372 -> 68632 bytes 05-build_abe-qemu/console.log.xz | Bin 31744 -> 31768 bytes 06-build_linux/console.log.xz | Bin 3396 -> 3372 bytes 07-boot_linux/console.log.xz | Bin 508 -> 508 bytes 08-check_regression/console.log.xz | Bin 3180 -> 3408 bytes 09-update_baseline/console.log | 8 ++++---- 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 | 30 +++++++++++++++--------------- 18 files changed, 27 insertions(+), 27 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022