Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[gcc] branch master updated (1a46a0a8b30 -> 233c966dba5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 1a46a0a8b30 testsuite: 'b' instruction can't do long enough jumps new 233c966dba5 testsuite: mark a test with xfail The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/testsuite/gcc.dg/tree-prof/cmpsf-1.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allmodconfig updated (c536bc075e -> 72af4b6f59)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allmodconfig in repository toolchain/ci/base-artifacts. from c536bc075e 23: onsuccess: #501: 37: Success after binutils/llvm/linux/q [...] new 72af4b6f59 24: onsuccess: #502: boot: Success after binutils/llvm/qemu: [...] 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 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30216 -> 30428 bytes 04-build_kernel_llvm/console.log.xz | Bin 66224 -> 66224 bytes 05-build_abe-qemu/console.log.xz | Bin 31800 -> 32460 bytes 06-build_linux/console.log.xz | Bin 4096 -> 3540 bytes 07-boot_linux/console.log.xz | Bin 0 -> 508 bytes 08-check_regression/console.log.xz | Bin 4528 -> 4052 bytes 08-check_regression/mail-body.txt | 6 +++++- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 8 ++++++-- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- results | 6 +++++- 18 files changed, 36 insertions(+), 24 deletions(-) create mode 100644 07-boot_linux/console.log.xz -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (b2803ff5c2 -> cb2d36a977)

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-arm in repository toolchain/ci/base-artifacts. from b2803ff5c2 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new cb2d36a977 58: onsuccess: #474: 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 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 51912 -> 51092 bytes 04-build_abe-gcc/console.log.xz | Bin 234588 -> 235108 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9080 -> 9168 bytes 07-build_abe-glibc/console.log.xz | Bin 231924 -> 234040 bytes 08-build_abe-gdb/console.log.xz | Bin 49516 -> 48952 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3812 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2156 -> 2348 bytes 11-check_regression/console.log.xz | Bin 6156 -> 6144 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 | 38 ++-- sumfiles/binutils.log.xz | Bin 55672 -> 55988 bytes sumfiles/binutils.sum | 60 ++--- sumfiles/gas.log.xz | Bin 98412 -> 98056 bytes sumfiles/gas.sum | 268 +++++++++++----------- sumfiles/ld.log.xz | Bin 131344 -> 131336 bytes sumfiles/ld.sum | 342 ++++++++++++++--------------- 29 files changed, 370 insertions(+), 370 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (fa8e3a055a0 -> 1a46a0a8b30)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from fa8e3a055a0 testsuite: Windows reports errors with CreateProcess new 1a46a0a8b30 testsuite: 'b' instruction can't do long enough jumps The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/testsuite/gcc.target/arm/stack-protector-1.c | 4 ++-- gcc/testsuite/gcc.target/arm/stack-protector-3.c | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (b77bcdf4456 -> fa8e3a055a0)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from b77bcdf4456 RISC-V: remove deprecate pic code model macro new 5fe2e4f87e5 testsuite: /dev/null is not accessible on Windows new fa8e3a055a0 testsuite: Windows reports errors with CreateProcess The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/testsuite/g++.dg/modules/bad-mapper-1.C | 2 +- gcc/testsuite/gcc.misc-tests/outputs.exp | 17 ++++++++++++----- 2 files changed, 13 insertions(+), 6 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 (9b2548ee3c -> dffb5e30e3)

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 9b2548ee3c 169: onsuccess: #1574: 2: Success after binutils/gcc: 10 commits discards bff14c106d 168: onsuccess: #1573: 2: Success after binutils/gcc: 9 commits discards dbe895eaf2 167: onsuccess: #1572: 2: Success after binutils/gcc: 15 commits discards 520b7b7e4a 166: onsuccess: #1571: 2: Success after binutils/gcc: 13 commits discards f8d4b3b924 165: onsuccess: #1570: 2: Success after binutils/gcc: 5 commits discards 8d49dc43f5 164: onsuccess: #1569: 2: Success after binutils/gcc: 16 commits discards 119b23258f 163: onsuccess: #1568: 2: Success after binutils/gcc: 14 commits discards 7bc35a1839 162: onsuccess: #1567: 2: Success after binutils/gcc: 5 commits discards e82b2c2a63 161: onsuccess: #1566: 2: Success after binutils/gcc: 2 commits discards ff4081113c 160: onsuccess: #1565: 2: Success after binutils/gcc: 15 commits discards 3ecbf8bb40 159: onsuccess: #1564: 2: Success after binutils/gcc: 11 commits discards 8f585d3322 158: onsuccess: #1563: 2: Success after binutils/gcc: 2 commits discards a0c4c48ecb 157: onsuccess: #1562: 2: Success after gcc: 2 commits discards 829bd3110f 156: onsuccess: #1561: 2: Success after gcc: 2 commits discards b2b4230b55 155: onsuccess: #1560: 2: Success after gcc: 3 commits discards 4f4afeabd9 154: onsuccess: #1559: 2: Success after binutils/gcc: 12 commits discards 5fdf50371f 153: onsuccess: #1558: 2: Success after binutils/gcc: 12 commits discards e982635850 152: onsuccess: #1557: 2: Success after binutils/gcc: 12 commits discards 1f047bba86 151: onsuccess: #1556: 2: Success after binutils: 12 commits discards d1801c4940 150: onsuccess: #1555: 2: Success after binutils/gcc: 14 commits discards d171115cc3 149: onsuccess: #1554: 2: Success after binutils/gcc: 15 commits discards a0f18d84e1 148: onsuccess: #1553: 2: Success after binutils/gcc: 32 commits discards bb6a27ff7c 147: onsuccess: #1552: 1: Success after gcc: 2 commits discards 5c2baad4ab 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 commits discards d91934058f 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits discards 532f8dbf67 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits discards ee601cd58d 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits discards 4babd74796 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits discards f9009c287f 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits discards f630cb03e3 140: onsuccess: #1545: 1: Success after gcc: 7 commits discards f8ddbac09b 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits discards b5a8ea085a 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits discards 3c51b7c531 137: onsuccess: #1542: 1: Success after gcc: 4 commits discards 8077113d62 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] discards acce1f3f59 135: force: #1540: 2: Success after gcc: 23 commits discards 6cde170f29 134: onsuccess: #1538: 2: Success after binutils: 2 commits discards 6cd0d70501 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits discards 7fdc700801 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits discards e2dbebfb5a 131: onsuccess: #1534: 2: Success after gcc: 9 commits discards f02e6e8339 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] discards 587ada950b 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits discards cfa809707d 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 33de3e295f 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards 02f21db306 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards 4be22f90e4 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards afa32fbb3e 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards 656f964b07 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards 7eb1f00b1e 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards 97133bc9e7 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards 69f0cb0ecb 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards 61f948fb33 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards ef7502e9f2 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards 08091fb570 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards 23cac352b4 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards 6883337cdd 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards 29d0619b73 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 68d34cfa57 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards e6a9945518 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards 3bed6a03c5 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards 020468747d 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards 74dd787325 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards 9490ba7609 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards b67636e38b 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards ba3898edd2 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards e13056c9fc 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards 06a9107ab6 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards ec5b37177c 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 9a0d343a99 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards 85d28beae6 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards ec1f33b0d3 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards 409663be0c 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards 17e1195ba5 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards 6c398e8a72 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards a01baccf3c 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 245d8792ca 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards c4113b8736 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards 98c83bb286 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards acd7cc7219 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards a12142957b 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards 1eb7d556c8 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards 36237b8690 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards bea4c02cac 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards 1a13e3c722 87: onsuccess: 2: Success after gcc: 4 commits discards aefc0f71d4 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards 9e59a79924 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 7fd8ba1910 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 5564277df4 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 6f71acfad1 82: onsuccess: 1: Successful build after gcc: 3 commits discards b08b34a084 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 7b882b1470 80: force: 2: Successful build after gcc: 14 commits discards 788b110e88 79: onsuccess: 2: Successful build after binutils: 5 commits discards b7bcc0da15 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards 9a5109e606 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 43f5bff20a 76: onsuccess: 2: Successful build after gcc: 12 commits discards c203c3c01d 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards fe7bea70ce 74: onsuccess: 2: Successful build after baseline build: no [...] discards 6377015c98 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards a61b64f9ea 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards b3d3530963 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 88d3b44576 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 137b5f3e1f 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 54efc663b8 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 004878e6be 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 389ca1f4e3 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new ae043ac1c0 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 0cfe68c213 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 90059cbc89 74: onsuccess: 2: Successful build after baseline build: no [...] new f59aee05b6 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 6902e45ced 76: onsuccess: 2: Successful build after gcc: 12 commits new 3a3e72add2 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new a727fba197 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new 62e0e54ff4 79: onsuccess: 2: Successful build after binutils: 5 commits new 873fdcbf31 80: force: 2: Successful build after gcc: 14 commits new c2b5e88a28 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 619e58ca5a 82: onsuccess: 1: Successful build after gcc: 3 commits new e0037ba004 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new f30c7cb4be 84: onsuccess: 2: Success after binutils/gcc: 15 commits new 3b7772a5a0 85: onsuccess: 2: Success after binutils/gcc: 25 commits new de08346bdb 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 034e6e67ac 87: onsuccess: 2: Success after gcc: 4 commits new e5bb2f814f 88: onsuccess: 2: Success after binutils/gcc: 25 commits new b60a9e3c29 89: onsuccess: 2: Success after binutils/gcc: 4 commits new fa62055001 90: onsuccess: 2: Success after binutils/gcc: 16 commits new 584b79a4c3 91: onsuccess: 2: Success after binutils/gcc: 7 commits new 8a3d173e65 92: onsuccess: 2: Success after binutils/gcc: 9 commits new de2d1cf5bf 93: onsuccess: 2: Success after binutils/gcc: 3 commits new efefa76f10 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new be24f7a5dc 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new eda5eb18a6 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 68ef439a47 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new d2488cac0a 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new a69585a845 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new d4d48bad12 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 98b1519cdc 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new 125acb8406 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new 4c404aa893 103: onsuccess: #1504: 2: Success after gcc: 2 commits new 7b409a1c9d 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new efb014a573 105: onsuccess: #1506: 2: Success after gcc: 2 commits new 8e8d0a1a7f 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 2564612870 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new 1d45078f43 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 0273d28cc3 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new 4f3d6cd6a3 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new b6903fe7c0 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new 672c8776ae 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new 80de3f87d2 113: onsuccess: #1514: 2: Success after gcc: 5 commits new 6b2f4073d6 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new bc29924869 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new 51d775d655 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new 580de59085 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 3e6ff8f427 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new 5a670fc5c4 119: onsuccess: #1520: 2: Success after binutils: 8 commits new cb9a7785a7 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new 3ea1604212 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new 8dcefdb43b 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new 7ada5d0078 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new bae6e4103a 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new 4ce2dfac32 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new 8c7255b81f 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new b13cd37253 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new d69ac708a2 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new fbcb1ab590 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits new 5bcadacebc 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] new ecf918bdc4 131: onsuccess: #1534: 2: Success after gcc: 9 commits new 3e324ee3e2 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits new f66a8b311b 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits new 230ed09e91 134: onsuccess: #1538: 2: Success after binutils: 2 commits new d095d63222 135: force: #1540: 2: Success after gcc: 23 commits new e7c737fcea 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] new eb26b3aa56 137: onsuccess: #1542: 1: Success after gcc: 4 commits new 5360504776 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits new 139164ced9 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits new 4f85265723 140: onsuccess: #1545: 1: Success after gcc: 7 commits new 65ec9524cf 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits new 5d1d0907c5 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits new 74b5a46f25 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits new f3bb6e626f 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits new b07a70c02e 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits new 5f4ec907b0 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 commits new a9b52a004c 147: onsuccess: #1552: 1: Success after gcc: 2 commits new 57edfdfbb3 148: onsuccess: #1553: 2: Success after binutils/gcc: 32 commits new 9bb36ef148 149: onsuccess: #1554: 2: Success after binutils/gcc: 15 commits new e2094b05ea 150: onsuccess: #1555: 2: Success after binutils/gcc: 14 commits new 203a73dbca 151: onsuccess: #1556: 2: Success after binutils: 12 commits new 337210c2ca 152: onsuccess: #1557: 2: Success after binutils/gcc: 12 commits new 516f4856cc 153: onsuccess: #1558: 2: Success after binutils/gcc: 12 commits new c3cc88f599 154: onsuccess: #1559: 2: Success after binutils/gcc: 12 commits new d7c448e406 155: onsuccess: #1560: 2: Success after gcc: 3 commits new a8e15b7ed0 156: onsuccess: #1561: 2: Success after gcc: 2 commits new 2ccca8074c 157: onsuccess: #1562: 2: Success after gcc: 2 commits new fb2dafc0a1 158: onsuccess: #1563: 2: Success after binutils/gcc: 2 commits new f8009bafb9 159: onsuccess: #1564: 2: Success after binutils/gcc: 11 commits new c7e1c2b796 160: onsuccess: #1565: 2: Success after binutils/gcc: 15 commits new 1529065cf5 161: onsuccess: #1566: 2: Success after binutils/gcc: 2 commits new dc188f77b4 162: onsuccess: #1567: 2: Success after binutils/gcc: 5 commits new 4e57bcb316 163: onsuccess: #1568: 2: Success after binutils/gcc: 14 commits new b4eb1876db 164: onsuccess: #1569: 2: Success after binutils/gcc: 16 commits new 91a61b60de 165: onsuccess: #1570: 2: Success after binutils/gcc: 5 commits new f491dd72a9 166: onsuccess: #1571: 2: Success after binutils/gcc: 13 commits new 11663cbdcd 167: onsuccess: #1572: 2: Success after binutils/gcc: 15 commits new c69cdb8a22 168: onsuccess: #1573: 2: Success after binutils/gcc: 9 commits new 7fe7d0d765 169: onsuccess: #1574: 2: Success after binutils/gcc: 10 commits new dffb5e30e3 170: onsuccess: #1575: 2: Success after binutils: 5 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (9b2548ee3c) \ 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 1680 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 50732 -> 51472 bytes 05-build_abe-bootstrap/console.log.xz | Bin 470240 -> 467264 bytes 06-check_regression/console.log.xz | Bin 2920 -> 2700 bytes 07-update_baseline/console.log | 38 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 ++++++------- 12 files changed, 31 insertions(+), 31 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-aarch64-check_bootstrap updated (0060a3c9ac -> 9f0f7a5421)

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-aarch64-check_bootstrap in repository toolchain/ci/base-artifacts. from 0060a3c9ac 53: onsuccess: #588: 1: Success after binutils/gcc: 38 commits new 9f0f7a5421 54: onsuccess: #589: 1: Success after binutils/gcc: 51 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 1696 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 37744 -> 39240 bytes 04-build_abe-bootstrap/console.log.xz | Bin 270836 -> 271912 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3824 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2676 -> 2548 bytes 07-check_regression/console.log.xz | Bin 6876 -> 6352 bytes 07-check_regression/results.compare | 37 +- 07-check_regression/results.compare2 | 601 ++-- 08-update_baseline/console.log | 9 + dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- sumfiles/g++.log.xz | Bin 3668884 -> 3661924 bytes sumfiles/g++.sum | 231 +- sumfiles/gcc.log.xz | Bin 3231324 -> 3222216 bytes sumfiles/gcc.sum | 4505 ++++++++++++++------------- sumfiles/gfortran.log.xz | Bin 1093208 -> 1081424 bytes sumfiles/gfortran.sum | 48 +- sumfiles/libatomic.log.xz | Bin 2348 -> 2356 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213624 -> 213724 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2724 -> 2724 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 468084 -> 466572 bytes sumfiles/libstdc++.sum | 14 +- 31 files changed, 2898 insertions(+), 2605 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (6c2ad1a6d1 -> dc2b2c0826)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-arm in repository toolchain/ci/base-artifacts. discards 6c2ad1a6d1 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/g [...] discards 210f7bdeef 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/g [...] discards a88c953cec 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 34 [...] discards 5769596029 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits discards 24b2c677b0 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/g [...] discards cb4abf3268 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/g [...] discards c8eb924984 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 [...] discards 45f7d1e310 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits discards a2a94eb4c3 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/g [...] discards c34ebb74cf 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/g [...] discards 96e6d16942 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] discards 5aba51e225 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] discards 552d55cc6d 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards 1327a777bf 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards 1f4f429b04 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards 21a12a111d 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] discards ee04dcbe89 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] discards 51eb481fde 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] discards 36cba05c0a 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] discards 954180bf86 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] discards 418f093754 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] discards 0613b68299 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards 9df91c6f9a 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 1647ec8b30 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards 6cd09f8b14 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards 0738794471 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards 8be115c6bc 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards 207bb51c79 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards afa4841411 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards d74acae11f 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards 5ae85cf3dd 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards b7f4c2d3b2 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards f5926da9f2 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards 04fa14279e 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards 5663bdf5c7 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 471bb090ea 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards e784671329 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards f6383171c0 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards 754077a5db 132: onsuccess: #1645: 7: Success after linux: 23 commits discards aace6c4dd6 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 92fb33d581 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards 97a6e8b25b 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 9db4f7f42f 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards 6981084aad 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards eafa962738 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 0f658c7e0b 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards 347037033e 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 74c7b95cb4 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards cd163ce53e 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards f3d14b256d 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 76ed15357d 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 6c71b7058b 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 08704966cf 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 33352d277a 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 9f38d12f05 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards f990276e86 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 78e20e8478 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards c60641490d 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 4bf6e23393 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 60dfeca61c 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 3bc7b30aeb 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards 2d41cc8ca5 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards d0aef42c35 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 8cd765c177 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 11fd77a340 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards abf82e3cea 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 0fc20b62be 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards b350fd345a 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards c716a91dd3 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 796fea142a 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 9cf11abc15 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 3fb1892410 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards c201cef728 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 60b3e7b775 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards 67f0a709ce 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards bff3ffe498 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards 05b6d1d95e 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 870b85d714 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 8072f54863 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 5bcb0475fe 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 76fc9adf12 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 62f123e8c2 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 1d103861a8 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards d6b0223306 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards e8465fb339 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards c39614f4a1 85: onsuccess: 7: Success after gcc: 9 commits discards 3be8efab31 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 4b5b8d291d 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards af19eed45e 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards c9b712e99b 81: onsuccess: 7: Successful build after gcc: 2 commits discards ab444439f8 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards c70eafc0be 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards a3ef319da9 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a59426b346 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 88279b81e8 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 64b16f984c 75: onsuccess: 7: Successful build after linux: 44 commits discards ece41c0364 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 99310fa1cc 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 61ee85ef51 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 81b7d8fb86 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards db3df740ed 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 383352ab35 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 1320bc996b 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new eeff4a7e6c 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new bb5b7fe898 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ec47d4e91a 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new ae7ccdf72d 75: onsuccess: 7: Successful build after linux: 44 commits new 82f2037e0c 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 863b790d35 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 60d2185dbe 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new af2e8eb677 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new b6ae8f147f 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 52e52aa765 81: onsuccess: 7: Successful build after gcc: 2 commits new cc9adf7335 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 77715be12f 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new ee3bf3e427 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new b2360a6de1 85: onsuccess: 7: Success after gcc: 9 commits new e77bdd4ec5 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 98ac68a9fe 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new f33083c00c 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new efdd051952 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 334eb86567 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 7f4e3778de 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new f41f3e9d48 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new ccbb97f21f 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new f32f72c086 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 3453730dbe 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 0d5ac984b3 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 422dd6badf 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 4905daae38 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 2ec83574aa 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 41f127a605 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new 2822dc6945 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 81052dbf95 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 0d7eb77b4a 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 6a48929156 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 28c22468bf 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 89196f25c5 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 4e5787a270 107: onsuccess: #1618: 7: Success after gcc: 2 commits new e8e39d6f8d 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new 8767e2678a 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 10c4683e50 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new e5dafbca41 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 0b8c22a254 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 404b801030 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 0165779c44 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 87fe009553 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 0153fa856e 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new bc39ee902a 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new c971b31eea 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 06147766f1 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 9953acd1fc 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 1b1d577889 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new 3074731af0 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new faccd64c64 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 59495adcbf 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new a265086753 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new 5d67d5ad54 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new 1ef13e4577 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 6af6d95646 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new cfd548cffc 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new d7d9f54b82 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 5de83423d5 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 250fceb5af 132: onsuccess: #1645: 7: Success after linux: 23 commits new ad602882d0 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new 95cfeb12bf 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new 40f8d4306e 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new e56eb9e1a3 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 888393bfae 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new e9ad9d6776 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new 688f05f264 139: onsuccess: #1654: 1: Success after gcc: 11 commits new b003c493f0 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new eebd6f6ef2 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 535365a1cd 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new fbd60828fd 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new 2c01d8ae0c 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new 8b421a942d 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new 20a297a933 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new 2b14042b74 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new 182ab1de1c 148: onsuccess: #1663: 7: Success after glibc: 2 commits new dc1aa65997 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new 23c7916d8a 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] new 89cd29fa00 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] new 6804de440f 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] new 1b8852e172 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] new b6a2f93666 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] new 8a86a69db8 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] new 60abbd0098 156: onsuccess: #1671: 7: Success after gcc: 3 commits new 1ad55a6dc4 157: onsuccess: #1672: 7: Success after gcc: 2 commits new 3d19f1f808 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new d5ac6d71e0 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] new f75aed4ca6 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] new 24ad874e65 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/g [...] new 9f723919c1 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/g [...] new 3e3447c61e 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits new aa6954ade9 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 [...] new 2bc4e24f0b 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/g [...] new d4d8658d3b 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/g [...] new bdc60a43ba 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits new 6f13c7eaa0 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 34 [...] new 3d503bacb9 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/g [...] new 46bfd3f717 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/g [...] new dc2b2c0826 171: onsuccess: #1686: 7: 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 (6c2ad1a6d1) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1700 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 30012 -> 30472 bytes 05-build_abe-stage1/console.log.xz | Bin 92516 -> 91872 bytes 07-build_abe-linux/console.log.xz | Bin 11948 -> 9172 bytes 08-build_abe-glibc/console.log.xz | Bin 234068 -> 234184 bytes 09-build_abe-stage2/console.log.xz | Bin 224748 -> 223396 bytes 10-build_abe-gdb/console.log.xz | Bin 37088 -> 37680 bytes 11-build_abe-qemu/console.log.xz | Bin 31476 -> 31816 bytes 12-check_regression/console.log.xz | Bin 4440 -> 4156 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++++++++++---------- 20 files changed, 60 insertions(+), 60 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_native_check_binutils/master-aarch64 updated (691321a263 -> 4ef785899c)

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 691321a263 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] new 4ef785899c 55: onsuccess: #569: 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 1684 -> 1848 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 37620 -> 38916 bytes 04-build_abe-gcc/console.log.xz | Bin 212360 -> 215276 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9092 -> 9140 bytes 07-build_abe-glibc/console.log.xz | Bin 238892 -> 239560 bytes 08-build_abe-gdb/console.log.xz | Bin 37676 -> 37564 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3824 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2140 -> 2320 bytes 11-check_regression/console.log.xz | Bin 6172 -> 6176 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 | 38 ++-- sumfiles/binutils.log.xz | Bin 58740 -> 58352 bytes sumfiles/binutils.sum | 60 ++--- sumfiles/gas.log.xz | Bin 81116 -> 81092 bytes sumfiles/gas.sum | 268 +++++++++++----------- sumfiles/ld.log.xz | Bin 121420 -> 121244 bytes sumfiles/ld.sum | 342 ++++++++++++++--------------- 29 files changed, 370 insertions(+), 370 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-stable-allnoconfig updated (402ea0283b -> af645fd12c)

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-stable-allnoconfig in repository toolchain/ci/base-artifacts. from 402ea0283b 13: onsuccess: #461: boot: Success after binutils/gcc/linux/ [...] new af645fd12c 14: onsuccess: #462: boot: Success after binutils/gcc/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1708 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30248 -> 30504 bytes 04-build_abe-stage1/console.log.xz | Bin 72764 -> 73228 bytes 05-build_abe-qemu/console.log.xz | Bin 31996 -> 32120 bytes 06-build_linux/console.log.xz | Bin 4648 -> 4664 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4452 -> 4420 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022