Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-mainline-defconfig updated (f41b0a84d9 -> 420ca8045b)

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-mainline-defconfig in repository toolchain/ci/base-artifacts. from f41b0a84d9 12: onsuccess: #475: boot: Success after binutils/llvm/linux [...] new 420ca8045b 13: onsuccess: #476: 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 1696 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30040 -> 30212 bytes 04-build_kernel_llvm/console.log.xz | Bin 66104 -> 66296 bytes 05-build_abe-qemu/console.log.xz | Bin 31644 -> 32500 bytes 06-build_linux/console.log.xz | Bin 3036 -> 3128 bytes 07-boot_linux/console.log.xz | Bin 6224 -> 6268 bytes 08-check_regression/console.log.xz | Bin 4364 -> 4452 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 | 32 ++++++++++++++++---------------- results | 2 +- 19 files changed, 27 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_kernel/llvm-release-arm-mainline-allyesconfig updated (7ba874e60e -> 490dc179a3)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from 7ba874e60e 17: onsuccess: #451: 20867: Success after binutils/llvm/linu [...] new 490dc179a3 18: onsuccess: #452: 20921: 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 1696 -> 1964 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 29984 -> 30108 bytes 04-build_kernel_llvm/console.log.xz | Bin 62140 -> 64456 bytes 05-build_abe-qemu/console.log.xz | Bin 31864 -> 31476 bytes 06-build_linux/console.log.xz | Bin 4760 -> 4792 bytes 08-check_regression/console.log.xz | Bin 4368 -> 4296 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 | 32 ++++++++++++++++---------------- results | 2 +- 18 files changed, 27 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_kernel/llvm-master-arm-lts-allyesconfig updated (d42ddce88b -> a189bd46c4)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-allyesconfig in repository toolchain/ci/base-artifacts. from d42ddce88b 27: onsuccess: #491: 37: Success after binutils/llvm/linux/q [...] new a189bd46c4 28: onsuccess: #492: 19909: 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 1708 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30116 -> 30696 bytes 04-build_kernel_llvm/console.log.xz | Bin 62664 -> 66388 bytes 05-build_abe-qemu/console.log.xz | Bin 31484 -> 31804 bytes 06-build_linux/console.log.xz | Bin 3904 -> 4832 bytes 08-check_regression/console.log.xz | Bin 4420 -> 4612 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 | 32 ++++++++++++++++---------------- results | 2 +- 18 files changed, 27 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_kernel/gnu-master-aarch64-norov-allmodconfig updated (c2a7e3e4ac -> 9d82f083ad)

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-master-aarch64-norov-allmodconfig in repository toolchain/ci/base-artifacts. from c2a7e3e4ac 12: onsuccess: #41: 33: Success after binutils/gcc/linux/qem [...] new 9d82f083ad 13: onsuccess: #42: 33: Success after binutils/gcc/linux/qem [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1696 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30108 -> 31472 bytes 04-build_abe-stage1/console.log.xz | Bin 72140 -> 72920 bytes 05-build_abe-qemu/console.log.xz | Bin 32124 -> 32076 bytes 06-build_linux/console.log.xz | Bin 3772 -> 3804 bytes 08-check_regression/console.log.xz | Bin 4456 -> 4320 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 ++++++++++++++++---------------- 16 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/master-arm-check_bootstrap_lto updated (5166cf3a54 -> f9ee228494)

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_lto in repository toolchain/ci/base-artifacts. from 5166cf3a54 56: onsuccess: #482: 1: Success after binutils/gcc: 31 commits new f9ee228494 57: onsuccess: #483: 1: Success after binutils/gcc: 54 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 2716 -> 2716 bytes 03-build_abe-binutils/console.log.xz | Bin 51420 -> 52020 bytes 04-build_abe-bootstrap_lto/console.log.xz | Bin 477592 -> 475480 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3808 bytes 06-build_abe-check_bootstrap_lto/console.log.xz | Bin 2424 -> 2440 bytes 07-check_regression/console.log.xz | Bin 6408 -> 7500 bytes 07-check_regression/extra-bisect-params | 2 +- 07-check_regression/fails.sum | 8 +- 07-check_regression/mail-body.txt | 54 +- 07-check_regression/results.compare | 13 +- 07-check_regression/results.compare2 | 659 ++-- 07-check_regression/results.regressions | 13 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 56 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 13 +- sumfiles/g++.log.xz | Bin 2837904 -> 2845540 bytes sumfiles/g++.sum | 258 +- sumfiles/gcc.log.xz | Bin 2528356 -> 2523008 bytes sumfiles/gcc.sum | 4178 ++++++++++++----------- sumfiles/gfortran.log.xz | Bin 954684 -> 944788 bytes sumfiles/gfortran.sum | 24 +- sumfiles/libatomic.log.xz | Bin 2308 -> 2312 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 211504 -> 211252 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2732 -> 2732 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 482616 -> 480624 bytes sumfiles/libstdc++.sum | 2 +- 35 files changed, 2939 insertions(+), 2375 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-next-allmodconfig updated (d58a37b25c -> 3e97db1062)

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-master-aarch64-next-allmodconfig in repository toolchain/ci/base-artifacts. from d58a37b25c 16: onsuccess: #545: 33: Success after binutils/gcc/linux/qe [...] new 3e97db1062 17: onsuccess: #546: 33: Success after binutils/gcc/linux/qe [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1700 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 30140 -> 30972 bytes 04-build_abe-stage1/console.log.xz | Bin 72028 -> 72996 bytes 05-build_abe-qemu/console.log.xz | Bin 32028 -> 32424 bytes 06-build_linux/console.log.xz | Bin 3404 -> 3436 bytes 08-check_regression/console.log.xz | Bin 4412 -> 4436 bytes 09-update_baseline/console.log | 9 +++++++++ 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, 33 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-release-aarch64-lts-defconfig updated (cb6e3f6877 -> 81f1f25ca8)

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-lts-defconfig in repository toolchain/ci/base-artifacts. from cb6e3f6877 12: onsuccess: #255: boot: Success after binutils/llvm/linux [...] new 81f1f25ca8 13: onsuccess: #256: 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 1708 -> 1960 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30196 -> 30340 bytes 04-build_kernel_llvm/console.log.xz | Bin 64272 -> 65760 bytes 05-build_abe-qemu/console.log.xz | Bin 31760 -> 32192 bytes 06-build_linux/console.log.xz | Bin 3956 -> 3564 bytes 07-boot_linux/console.log.xz | Bin 6052 -> 6064 bytes 08-check_regression/console.log.xz | Bin 4260 -> 4216 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap updated (02813f102c -> 83027e5946)

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 02813f102c 176: onsuccess: #1581: 2: Success after binutils/gcc: 4 commits discards 2efb851e36 175: onsuccess: #1580: 2: Success after binutils/gcc: 34 commits discards 1e614b015e 174: onsuccess: #1579: 2: Success after binutils/gcc: 11 commits discards 301d4eb963 173: onsuccess: #1578: 2: Success after binutils/gcc: 3 commits discards 710a2b4d66 172: onsuccess: #1577: 2: Success after gcc: 8 commits discards 837af36e7b 171: onsuccess: #1576: 2: Success after gcc: 14 commits discards 57b866d52d 170: onsuccess: #1575: 2: Success after binutils: 5 commits discards e4e4d329b2 169: onsuccess: #1574: 2: Success after binutils/gcc: 10 commits discards 92409183f0 168: onsuccess: #1573: 2: Success after binutils/gcc: 9 commits discards 9f933d4cbb 167: onsuccess: #1572: 2: Success after binutils/gcc: 15 commits discards 5e4d65443d 166: onsuccess: #1571: 2: Success after binutils/gcc: 13 commits discards 3af7c5597c 165: onsuccess: #1570: 2: Success after binutils/gcc: 5 commits discards 5fa7e4920a 164: onsuccess: #1569: 2: Success after binutils/gcc: 16 commits discards c571ca34ae 163: onsuccess: #1568: 2: Success after binutils/gcc: 14 commits discards 25d265e749 162: onsuccess: #1567: 2: Success after binutils/gcc: 5 commits discards ad95a031d2 161: onsuccess: #1566: 2: Success after binutils/gcc: 2 commits discards f565651248 160: onsuccess: #1565: 2: Success after binutils/gcc: 15 commits discards 9610bb00b5 159: onsuccess: #1564: 2: Success after binutils/gcc: 11 commits discards c8961269cf 158: onsuccess: #1563: 2: Success after binutils/gcc: 2 commits discards 44e69bb121 157: onsuccess: #1562: 2: Success after gcc: 2 commits discards 198fb8a389 156: onsuccess: #1561: 2: Success after gcc: 2 commits discards b5aa52a20c 155: onsuccess: #1560: 2: Success after gcc: 3 commits discards bad449a558 154: onsuccess: #1559: 2: Success after binutils/gcc: 12 commits discards 61787cec61 153: onsuccess: #1558: 2: Success after binutils/gcc: 12 commits discards 405d4fd3b7 152: onsuccess: #1557: 2: Success after binutils/gcc: 12 commits discards 8e1d317549 151: onsuccess: #1556: 2: Success after binutils: 12 commits discards 12316714f2 150: onsuccess: #1555: 2: Success after binutils/gcc: 14 commits discards 356e390588 149: onsuccess: #1554: 2: Success after binutils/gcc: 15 commits discards 3392459f57 148: onsuccess: #1553: 2: Success after binutils/gcc: 32 commits discards 913e787693 147: onsuccess: #1552: 1: Success after gcc: 2 commits discards 0c0b3e07c5 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 commits discards 7c1accd288 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits discards 03f469b1ef 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits discards db4241e580 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits discards 12d201ef04 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits discards 732bf767c5 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits discards 7d15dbd9ef 140: onsuccess: #1545: 1: Success after gcc: 7 commits discards 0d2cb12a53 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits discards ae20312c63 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits discards 002197dc11 137: onsuccess: #1542: 1: Success after gcc: 4 commits discards 2ba577f8af 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] discards 03d1934ce5 135: force: #1540: 2: Success after gcc: 23 commits discards 88ff43cee5 134: onsuccess: #1538: 2: Success after binutils: 2 commits discards 9877f1d5ab 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits discards 26cb933852 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits discards 0198914543 131: onsuccess: #1534: 2: Success after gcc: 9 commits discards efcea88515 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] discards 2dea1c910f 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits discards 5a22975165 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 998257a086 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards 0fbf5adb8f 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards 1ca4475490 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards 895b45e3ef 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards 07c9e456d4 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards 2826419b34 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards e9fd422497 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards bbc88b027b 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards 8f5c165ebd 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards 3ea8435ce5 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards af8062e62e 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards 46a1246b9f 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards 3c91ba8538 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards c2ac389fd7 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards f77d4a173a 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards 03e132db20 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards 2b342679e9 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards b38871cbf5 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards 1598a469c4 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards 56187200bf 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 20af0be727 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards 47e207d5c8 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards 7651b6ac4f 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards 649e1133cc 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards 2df539765d 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 6e56ecc1aa 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards 0f4d1c110a 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards 20987fe16e 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards a3dda3ee51 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards 1702d834bb 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards 4ee3839639 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 2d413fe562 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 4cfcb4a689 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards 97ae0ec0b2 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards a490b34aad 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards 52de0fc750 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards e2dd7f7746 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards 3fd831ee1f 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards 0f75ba704b 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards 0ee5c8a495 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards d3c90170b5 87: onsuccess: 2: Success after gcc: 4 commits discards 8963c7293b 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards 47d6be9591 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 64a588068a 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 0720023752 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 6645d61fdb 82: onsuccess: 1: Successful build after gcc: 3 commits discards 62f76ae554 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 61d30286e0 80: force: 2: Successful build after gcc: 14 commits discards 61a17e0e70 79: onsuccess: 2: Successful build after binutils: 5 commits discards d0ddcd5e9c 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards c6c06451bc 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 64d756a775 76: onsuccess: 2: Successful build after gcc: 12 commits new 449d564bc3 76: onsuccess: 2: Successful build after gcc: 12 commits new a326265c41 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 8ae110922e 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new 50c2ecedbd 79: onsuccess: 2: Successful build after binutils: 5 commits new e14bb4676c 80: force: 2: Successful build after gcc: 14 commits new b7949d9cd0 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 83a9f2c1a4 82: onsuccess: 1: Successful build after gcc: 3 commits new 82fe7af424 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new d22160cee5 84: onsuccess: 2: Success after binutils/gcc: 15 commits new 2a8e5b27e6 85: onsuccess: 2: Success after binutils/gcc: 25 commits new b582e4abd8 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 4f03a94e88 87: onsuccess: 2: Success after gcc: 4 commits new 0798a046a7 88: onsuccess: 2: Success after binutils/gcc: 25 commits new 80ef627c8a 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 313f71620b 90: onsuccess: 2: Success after binutils/gcc: 16 commits new d913bd9dec 91: onsuccess: 2: Success after binutils/gcc: 7 commits new 19dfb39525 92: onsuccess: 2: Success after binutils/gcc: 9 commits new da2b792119 93: onsuccess: 2: Success after binutils/gcc: 3 commits new 293aaf4794 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new 7511b2632c 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new 4d0e381c03 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 72625dc658 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new ad6b501970 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new 9958a01cf0 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new 14c03fa5c6 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 0881b184a9 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new 5545499c2d 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new fd7856ac61 103: onsuccess: #1504: 2: Success after gcc: 2 commits new a737c8f2d5 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new bd7808b0f6 105: onsuccess: #1506: 2: Success after gcc: 2 commits new 97a61506ff 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 3e46cd4504 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new 8ed07f43ce 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 8e2b897592 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new 5795404954 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new c2bab56c5b 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new 6265cbe85b 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new 86a89e8376 113: onsuccess: #1514: 2: Success after gcc: 5 commits new 218e5971ca 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new d0bc659acc 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new 3a8421ff76 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new c6bb8ca4ae 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 004be8628a 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new 86e80d1f07 119: onsuccess: #1520: 2: Success after binutils: 8 commits new 4c4ab07647 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new 1d4fadea6b 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new 1247659c25 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new e350821f0f 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new 99c78bc4be 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new fac4475698 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new f4cec8fa49 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new 519050fea9 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new 7544203dfb 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 87c8bb6fcd 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits new 3f84aee8db 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] new cf61c5710e 131: onsuccess: #1534: 2: Success after gcc: 9 commits new 0177f2261f 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits new 92a794a961 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits new 5614209f1c 134: onsuccess: #1538: 2: Success after binutils: 2 commits new e9cd640504 135: force: #1540: 2: Success after gcc: 23 commits new fd8568bdb5 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] new 2f4ba821f6 137: onsuccess: #1542: 1: Success after gcc: 4 commits new 827e15bf83 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits new fa24282cd0 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits new b54bb5aeb4 140: onsuccess: #1545: 1: Success after gcc: 7 commits new 3dfc6741bc 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits new 67031098c3 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits new 9c68d109e7 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits new b016767995 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits new 85137b05f4 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits new 0b0f2c2086 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 commits new 19e8a36e6f 147: onsuccess: #1552: 1: Success after gcc: 2 commits new ff652b8ca6 148: onsuccess: #1553: 2: Success after binutils/gcc: 32 commits new a7e4ac24d6 149: onsuccess: #1554: 2: Success after binutils/gcc: 15 commits new f507147775 150: onsuccess: #1555: 2: Success after binutils/gcc: 14 commits new 51ceb0b66d 151: onsuccess: #1556: 2: Success after binutils: 12 commits new 29ce9b45f5 152: onsuccess: #1557: 2: Success after binutils/gcc: 12 commits new 976f4d6ce0 153: onsuccess: #1558: 2: Success after binutils/gcc: 12 commits new 1ab3033249 154: onsuccess: #1559: 2: Success after binutils/gcc: 12 commits new 33ec293007 155: onsuccess: #1560: 2: Success after gcc: 3 commits new 24785701cf 156: onsuccess: #1561: 2: Success after gcc: 2 commits new 06aaf6342d 157: onsuccess: #1562: 2: Success after gcc: 2 commits new 942761c6aa 158: onsuccess: #1563: 2: Success after binutils/gcc: 2 commits new 67e542f7b9 159: onsuccess: #1564: 2: Success after binutils/gcc: 11 commits new 3286d8eeb9 160: onsuccess: #1565: 2: Success after binutils/gcc: 15 commits new 0abf289b8a 161: onsuccess: #1566: 2: Success after binutils/gcc: 2 commits new f6349b1b7b 162: onsuccess: #1567: 2: Success after binutils/gcc: 5 commits new 4f3727cda5 163: onsuccess: #1568: 2: Success after binutils/gcc: 14 commits new 308c5815ba 164: onsuccess: #1569: 2: Success after binutils/gcc: 16 commits new 9370691de8 165: onsuccess: #1570: 2: Success after binutils/gcc: 5 commits new 99087d16d2 166: onsuccess: #1571: 2: Success after binutils/gcc: 13 commits new 521ce145d0 167: onsuccess: #1572: 2: Success after binutils/gcc: 15 commits new d67727d1c2 168: onsuccess: #1573: 2: Success after binutils/gcc: 9 commits new 88750a749c 169: onsuccess: #1574: 2: Success after binutils/gcc: 10 commits new 83dcf71995 170: onsuccess: #1575: 2: Success after binutils: 5 commits new 473274ee1b 171: onsuccess: #1576: 2: Success after gcc: 14 commits new cd8db79ddf 172: onsuccess: #1577: 2: Success after gcc: 8 commits new 68fc914d52 173: onsuccess: #1578: 2: Success after binutils/gcc: 3 commits new 9ed73fcb2b 174: onsuccess: #1579: 2: Success after binutils/gcc: 11 commits new f6b767a183 175: onsuccess: #1580: 2: Success after binutils/gcc: 34 commits new 662aa9b3f2 176: onsuccess: #1581: 2: Success after binutils/gcc: 4 commits new 83027e5946 177: onsuccess: #1582: 2: Success after binutils/gcc: 6 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 (02813f102c) \ 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 1700 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 50504 -> 51496 bytes 05-build_abe-bootstrap/console.log.xz | Bin 463444 -> 467144 bytes 06-check_regression/console.log.xz | Bin 2716 -> 2832 bytes 07-update_baseline/console.log | 36 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 ++++++++--------- 13 files changed, 33 insertions(+), 33 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (8f47374776 -> dd0d23501f)

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 8f47374776 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards 95d741e1ac 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards 5057f64310 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards 43ab69790d 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards 2b60423303 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards 4ab18f443b 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards e6fabc3067 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards d496596cc2 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards 20dcdbe54e 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards 47d637db6d 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards 70e35f7f85 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards d3ef3c5b3b 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards b799c9b4da 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards 28d16c9e31 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards c09cdea6ff 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 471828a42f 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards 92cfd9a51b 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards af4338db9f 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 53616cf308 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 79de365429 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards ec7a39df4a 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 5ddd5ff7f7 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards ff01c89276 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards 0702afbf32 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 56fe00bc18 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 9a3a44403d 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 473f6c2f6b 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards f06db59e9d 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 6ce2722f7a 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 361c2a6443 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards be3d9fb610 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards a8e93ce1ce 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards bdd0d4f99c 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 6271cf63ab 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 2dd6adb399 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 416e2d3933 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 4bf906431c 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 654ba430e6 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 55e4507f34 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 9b7a340d40 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards f29ef3409c 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards b8fc0b9242 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 3b58d2724e 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 426a19aa36 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards fbcda176a2 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 4aaafa698f 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 417d9b509c 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards d73908cf0f 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 3f1ed7ed4a 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards c35c91d011 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 37232e3cf0 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 77712d26ba 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 17d207d5ec 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 46e0d9afb9 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards cc08949c29 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards f37fc69b86 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 9feda5690b 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards c228af9534 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 0b9f6379b9 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 125e645395 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards c206c735b5 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards c577800867 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 235f3a30d1 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 6a8956e0bd 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards cc9bf2afa2 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 34925e3465 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards a83d319651 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 9a5422d0d7 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards fbfa870a58 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 9e8e5bba79 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 21e4bd8ac9 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards fcd46dcc7d 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 0142f23f5b 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards ae42f7d416 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards da686c3630 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 29334242c4 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 9008315e7e 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 43b2c8a657 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 5265167497 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards f406df92ed 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 3778614c02 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards d854255f14 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 1b0bbb8ebc 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards ffe4387016 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1e3b2e760f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards d2199eeb9a 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards e51ed00750 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards b5324e6c79 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 9b47a14354 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 73633dd06c 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 291541faea 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 65286e789d 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 579b063342 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards ab0173e022 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards a9a999bbbc 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards b4a6b0a5f9 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 76aa1cf865 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7ea2bbadf7 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 1cbda5a426 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards eb26223940 74: onsuccess: 1: Successful build after linux: 44 commits discards da77442f1d 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 977144eb97 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 97e7b8074f 74: onsuccess: 1: Successful build after linux: 44 commits new 573d2b46fa 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 63916ec43e 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 0c23e26d6c 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 56f09a1bf4 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 900c18f71d 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 886f5d14f2 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 68cc75c977 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new d1594c5f9f 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 52d0e0e468 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 4817adad1a 84: onsuccess: 1: Success after gcc/glibc: 9 commits new dfe161ce9f 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new b6e58d22d6 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 460ac12fd9 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 30f74f3fce 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 48b2c1b2d6 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new e0b3bbb227 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new c7319e6b58 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new b588a1229f 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new c389d1a58f 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 8511cc1e25 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 4fa59f29b0 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 57d41791a3 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new d76a75de48 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 5971142123 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new f5e528f9ae 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 0cacf6c55d 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new ad8be835d2 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 15cf3c3a80 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 7275e5ec37 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new c5fc2bca54 104: onsuccess: #1697: 1: Success after gcc: 4 commits new e4e3ec1268 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 8d8d02f84e 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 9aec2fb9af 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 16e406ea44 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 4fda817db4 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new e1641919fd 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 2e871697ef 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 2c15e251b1 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 37e4d5c427 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 56cc21dad1 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 3fb7eb2bc4 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new da8b5bc6f0 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 653eb54d51 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 922dd93460 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 914d5921bc 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 32d493a9cc 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 7ed25814b0 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 5f413b9275 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new c555e34276 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new dedd557498 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 3e596ceaa2 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 5db474567c 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new befd3bd75a 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new bc8cb33f8c 128: onsuccess: #1723: 1: Success after linux: 12 commits new 633106ddfe 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 4d81bebeb5 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new e8ba8971e7 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new cca68c0192 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new b7e7c2c7b2 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new e17b009aa2 134: onsuccess: #1730: 1: Success after binutils: 2 commits new e3f81eae0a 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 45cea36b25 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 4e54dc4c6c 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 8782632382 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 27f84ae717 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new aef3c811e8 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 603ea273ef 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 4f5210f735 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new a2a6d8fdad 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 07b7d46c8c 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 52bd9b33e7 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 259a028b77 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 6b1dcd29f3 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 75afc10d26 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new fa2c401405 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 879c4176fc 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new b0150ca119 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 63859ce7b5 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new f57fb97a9d 153: onsuccess: #1754: 1: Success after gcc: 2 commits new f92ecdee0f 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 3bbcdc52c5 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 0ea851af38 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 2891848af1 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 208dc0de72 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 1f747dea02 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new 73c2be95a5 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new c4f14e6b68 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new 27f993db34 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new 2a41917b16 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 3284ef3a61 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new 31da5a1cee 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new a7ed720694 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new 232cedcf27 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new 196dcecc16 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new 14efe4f21b 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new 63e3d5c6cd 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new 7ff5666b6e 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new bcbe73e3b4 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new 3463f08d46 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new dd0d23501f 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (8f47374776) \ 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 1692 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 31380 -> 30028 bytes 04-build_abe-stage1/console.log.xz | Bin 92284 -> 90924 bytes 06-build_abe-linux/console.log.xz | Bin 9528 -> 8764 bytes 07-build_abe-glibc/console.log.xz | Bin 236300 -> 236272 bytes 08-build_abe-stage2/console.log.xz | Bin 227408 -> 224160 bytes 09-build_abe-gdb/console.log.xz | Bin 38700 -> 37512 bytes 10-build_abe-qemu/console.log.xz | Bin 31724 -> 32468 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2644 -> 2460 bytes 13-check_regression/console.log.xz | Bin 7584 -> 6592 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 10 +- 13-check_regression/mail-body.txt | 60 +- 13-check_regression/results.compare | 42 +- 13-check_regression/results.compare2 | 123 +- 13-check_regression/results.regressions | 42 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 62 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 42 +- sumfiles/g++.log.xz | Bin 2675008 -> 2655948 bytes sumfiles/g++.sum | 38 +- sumfiles/gcc.log.xz | Bin 2233560 -> 2238232 bytes sumfiles/gcc.sum | 2200 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 889516 -> 883248 bytes sumfiles/gfortran.sum | 22 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201268 -> 201488 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 439148 -> 426080 bytes sumfiles/libstdc++.sum | 2 +- 43 files changed, 1327 insertions(+), 1440 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[binutils-gdb] branch master updated (fea044ba7b5 -> ea4e4a19b7f)

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 fea044ba7b5 Automatic date update in version.in new ea4e4a19b7f PR29653, objcopy/strip: fuzzed small input file induces lar [...] 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: bfd/peXXigen.c | 55 ++++++++++++++++++------------------------------------- bfd/peicode.h | 34 ++++++++++++++++++++++++++++------ 2 files changed, 46 insertions(+), 43 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022