Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (452e71714d -> 8e77c1d247)

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 452e71714d 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new 8e77c1d247 54: onsuccess: #470: 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 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2704 -> 2716 bytes 03-build_abe-binutils/console.log.xz | Bin 50328 -> 51068 bytes 04-build_abe-gcc/console.log.xz | Bin 233100 -> 234936 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8392 -> 8500 bytes 07-build_abe-glibc/console.log.xz | Bin 232188 -> 233004 bytes 08-build_abe-gdb/console.log.xz | Bin 49380 -> 49572 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3796 -> 3836 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2160 -> 2068 bytes 11-check_regression/console.log.xz | Bin 6324 -> 6084 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 56092 -> 55508 bytes sumfiles/binutils.sum | 60 ++--- sumfiles/gas.log.xz | Bin 98016 -> 98048 bytes sumfiles/gas.sum | 268 +++++++++++----------- sumfiles/ld.log.xz | Bin 131284 -> 131348 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_gcc_check/release-aarch64 updated (eaaa66f3f0 -> 111b26ee90)

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/release-aarch64 in repository toolchain/ci/base-artifacts. from eaaa66f3f0 16: onsuccess: #219: 1: Success after binutils/gcc: 8 commits new 111b26ee90 17: onsuccess: #220: 1: Success after binutils/gcc: 14 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 1672 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 37608 -> 37580 bytes 04-build_abe-gcc/console.log.xz | Bin 206844 -> 207388 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3816 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2384 -> 2308 bytes 07-check_regression/console.log.xz | Bin 5252 -> 5644 bytes 07-check_regression/extra-bisect-params | 2 +- 07-check_regression/fails.sum | 8 +- 07-check_regression/mail-body.txt | 60 +- 07-check_regression/results.compare | 30 +- 07-check_regression/results.compare2 | 84 +- 07-check_regression/results.regressions | 30 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 62 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 30 +- sumfiles/g++.log.xz | Bin 3524736 -> 3487948 bytes sumfiles/g++.sum | 144 +- sumfiles/gcc.log.xz | Bin 3006196 -> 2998624 bytes sumfiles/gcc.sum | 4602 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1025796 -> 1034884 bytes sumfiles/gfortran.sum | 100 +- sumfiles/libatomic.log.xz | Bin 2192 -> 2188 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201844 -> 202256 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2552 -> 2540 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 437152 -> 435452 bytes sumfiles/libstdc++.sum | 24 +- 35 files changed, 2646 insertions(+), 2586 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (2555071c954 -> 153ca019b77)

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 2555071c954 Improve Z flag handling on H8 new 153ca019b77 OpenACC: Fix struct-component-kind-1.c test 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/gimplify.cc | 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_gcc_bootstrap/master-arm-bootstrap updated (23f2057058 -> cc9121d751)

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 23f2057058 154: onsuccess: #1559: 2: Success after binutils/gcc: 12 commits discards b1a3fb2d77 153: onsuccess: #1558: 2: Success after binutils/gcc: 12 commits discards d80674d200 152: onsuccess: #1557: 2: Success after binutils/gcc: 12 commits discards 8496422919 151: onsuccess: #1556: 2: Success after binutils: 12 commits discards e0153931bb 150: onsuccess: #1555: 2: Success after binutils/gcc: 14 commits discards 04d1899904 149: onsuccess: #1554: 2: Success after binutils/gcc: 15 commits discards d0354a8b88 148: onsuccess: #1553: 2: Success after binutils/gcc: 32 commits discards b92ef0d8ab 147: onsuccess: #1552: 1: Success after gcc: 2 commits discards 2f6b454464 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 commits discards 24510866a6 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits discards a419b430ae 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits discards 28af8cb32a 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits discards 5b54659d9d 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits discards 5cfee4c854 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits discards 6b2ce4d224 140: onsuccess: #1545: 1: Success after gcc: 7 commits discards cdeac792ca 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits discards 3ad993c3d3 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits discards 02d90f8355 137: onsuccess: #1542: 1: Success after gcc: 4 commits discards 1d135542dd 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] discards ada4680054 135: force: #1540: 2: Success after gcc: 23 commits discards 1d5a263090 134: onsuccess: #1538: 2: Success after binutils: 2 commits discards 4c9e847a93 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits discards 4758431bae 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits discards ecc62bfc1d 131: onsuccess: #1534: 2: Success after gcc: 9 commits discards 29a2321798 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] discards a1358b8265 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits discards b742e42e0e 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 6850683691 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards d84e77de63 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards 1cd377319f 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards b3b1562b57 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards e3e0215c79 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards 41bbc496cf 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards 39120d659f 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards a75af294b9 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards d5e035ba35 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards 7d24a0ac0a 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards 4cd4a7e9c5 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards d36d11d6d5 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards 9bcf6789c0 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards ed2d83e92c 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards ee1a18996a 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards a8c4f779c7 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards 5a1299aaf4 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards b5e54ccf81 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards d00608783d 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards 953c4c2371 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards ab9266530e 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards e7abde070f 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards 570c199bb4 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards 49a176e0ec 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards c2efa6dd70 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 004e2ce697 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards dcd2b46ca3 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards d57f1748e5 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards b51368f9d0 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards 207e471758 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards 6727d53f8b 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards ded6864892 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 82eab80823 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards a0205da39b 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards 2342b624a9 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards 69c7c1506f 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards b436fabe7f 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards 2ccfe898d4 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards b6cc64dcdf 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards 5474ab83b0 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards 14576ed93e 87: onsuccess: 2: Success after gcc: 4 commits discards 5184ebf890 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards 9918b388dd 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 52e26f5c20 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 0b0165d8b9 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 164625ff6a 82: onsuccess: 1: Successful build after gcc: 3 commits discards c1b3bc6566 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 27e767e9cc 80: force: 2: Successful build after gcc: 14 commits discards ed11a9e2bf 79: onsuccess: 2: Successful build after binutils: 5 commits discards 19d05c000e 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards 332f857372 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 341840d558 76: onsuccess: 2: Successful build after gcc: 12 commits discards c86cb12cc2 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 91e13f495b 74: onsuccess: 2: Successful build after baseline build: no [...] discards 29091184a2 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 2520377bb6 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 3385c0b1f4 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 9166aaa704 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards db2820a0fa 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 2c9d24b7d4 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 3459bfa63e 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 598e011ab3 66: onsuccess: 2: Successful build after gcc: 9 commits discards 220003bfec 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 0d6858c4f0 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 004961dae8 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 7268261618 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 6c33333c1a 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards bbc3e91a57 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards a53d1b8f72 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 41006219f8 58: force: 2: Successful build after gcc: 6 commits discards 02bf9e6071 57: onsuccess: 2: Successful build after binutils: gdb: new [...] discards 16c9771a5c 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards ed17a87506 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 929a18ed99 54: onsuccess: 2: Successful build after gcc: 5 commits new c9e8fe9dbb 54: onsuccess: 2: Successful build after gcc: 5 commits new fc5c4f3699 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 10e9607087 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 2901a6e5f1 57: onsuccess: 2: Successful build after binutils: gdb: new [...] new aa66c7831f 58: force: 2: Successful build after gcc: 6 commits new 678c63a2a7 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 9814f0be7b 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new d9eab96ef6 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new 91b4db3588 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new a094800dd6 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 652cd6d748 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 27fc2b4812 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 1371ead51a 66: onsuccess: 2: Successful build after gcc: 9 commits new e69b7558ff 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new c41b200de3 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 15073ed488 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 67664d231d 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 5fd737326a 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new df1a901a95 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 791cfa39a3 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 0574c95926 74: onsuccess: 2: Successful build after baseline build: no [...] new 50a138ba57 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 68d50e84f5 76: onsuccess: 2: Successful build after gcc: 12 commits new 49e0f1f931 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 84fce51f1b 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new 8cbfdf4bd5 79: onsuccess: 2: Successful build after binutils: 5 commits new b90925ff21 80: force: 2: Successful build after gcc: 14 commits new 5a84f195c0 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new a8b66d8447 82: onsuccess: 1: Successful build after gcc: 3 commits new 6622f3d8e9 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new 7584407f55 84: onsuccess: 2: Success after binutils/gcc: 15 commits new c688893019 85: onsuccess: 2: Success after binutils/gcc: 25 commits new 1f61a67e7b 86: onsuccess: 2: Success after binutils/gcc: 10 commits new bc5a107a1b 87: onsuccess: 2: Success after gcc: 4 commits new a21f5af944 88: onsuccess: 2: Success after binutils/gcc: 25 commits new c6c698ca01 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 8bdbf3372d 90: onsuccess: 2: Success after binutils/gcc: 16 commits new 38f42d44af 91: onsuccess: 2: Success after binutils/gcc: 7 commits new e6ebb73afe 92: onsuccess: 2: Success after binutils/gcc: 9 commits new bdefc416fa 93: onsuccess: 2: Success after binutils/gcc: 3 commits new ec8d2fa575 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new 489ded116e 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new 42d76b6985 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 55fd70d881 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new 038216c875 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new f8c0bfbaf0 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new 8703e1a774 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new afce57e35b 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new 10662dcd6d 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new 172eaefa7d 103: onsuccess: #1504: 2: Success after gcc: 2 commits new 9369b7cdaa 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new 8a181994f8 105: onsuccess: #1506: 2: Success after gcc: 2 commits new 2a2370f405 106: onsuccess: #1507: 2: Success after gcc: 2 commits new f3c54d21d5 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new bb5ad1a56a 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new b136cad24c 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new 726ce8050f 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new 1538bb2fe3 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new cb4c62fb3c 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new 4993012221 113: onsuccess: #1514: 2: Success after gcc: 5 commits new ab354a1a18 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new 7ffe27a014 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new 87b9687490 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new 9699afb220 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 19f366e3d7 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new fb3f1e03b1 119: onsuccess: #1520: 2: Success after binutils: 8 commits new da4e535cd7 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new 38a50ee6e2 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new 489a5d09de 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new abc1c0f00f 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new b9b574ee99 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new 5e1780c24f 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new c5dc9db3ec 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new 3ea52d4720 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new 0ba3c4088f 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 5144dbb43c 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits new 01030dba38 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] new 9ec04a59f8 131: onsuccess: #1534: 2: Success after gcc: 9 commits new 476e239221 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits new b04460dd1d 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits new 46f9e3da0e 134: onsuccess: #1538: 2: Success after binutils: 2 commits new 45504b1d4d 135: force: #1540: 2: Success after gcc: 23 commits new e8d458c184 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] new 6c184229b8 137: onsuccess: #1542: 1: Success after gcc: 4 commits new cbf073b516 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits new 31bb8e83e6 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits new 56d8411c7d 140: onsuccess: #1545: 1: Success after gcc: 7 commits new 12b907a503 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits new b885401a0f 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits new eb57b4d6c7 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits new 8a9e0ad52d 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits new 6622b755da 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits new 2698a8d373 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 commits new 8af2fb8e13 147: onsuccess: #1552: 1: Success after gcc: 2 commits new c5ff48da29 148: onsuccess: #1553: 2: Success after binutils/gcc: 32 commits new 6d1cf0c969 149: onsuccess: #1554: 2: Success after binutils/gcc: 15 commits new e60d1f9100 150: onsuccess: #1555: 2: Success after binutils/gcc: 14 commits new 3c4bef27b6 151: onsuccess: #1556: 2: Success after binutils: 12 commits new 49d8b1f574 152: onsuccess: #1557: 2: Success after binutils/gcc: 12 commits new 392f89c0bb 153: onsuccess: #1558: 2: Success after binutils/gcc: 12 commits new 7184c49ace 154: onsuccess: #1559: 2: Success after binutils/gcc: 12 commits new cc9121d751 155: onsuccess: #1560: 2: Success after gcc: 3 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (23f2057058) \ 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 1676 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2716 bytes 04-build_abe-binutils/console.log.xz | Bin 51068 -> 50588 bytes 05-build_abe-bootstrap/console.log.xz | Bin 465072 -> 463608 bytes 06-check_regression/console.log.xz | Bin 2780 -> 2576 bytes 07-update_baseline/console.log | 62 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 ++++---- 12 files changed, 43 insertions(+), 43 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 (023a1f39d1 -> 4bf695ffed)

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 023a1f39d1 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] new 4bf695ffed 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1688 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2716 bytes 03-build_abe-binutils/console.log.xz | Bin 37784 -> 37892 bytes 04-build_abe-gcc/console.log.xz | Bin 211976 -> 214096 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8348 -> 8532 bytes 07-build_abe-glibc/console.log.xz | Bin 239424 -> 240412 bytes 08-build_abe-gdb/console.log.xz | Bin 37168 -> 37548 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3836 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2128 -> 2072 bytes 11-check_regression/console.log.xz | Bin 6272 -> 6232 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 58528 -> 58752 bytes sumfiles/binutils.sum | 60 ++--- sumfiles/gas.log.xz | Bin 81112 -> 81104 bytes sumfiles/gas.sum | 268 +++++++++++----------- sumfiles/ld.log.xz | Bin 121224 -> 121388 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 (e0c0013509 -> 402ea0283b)

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 e0c0013509 12: onsuccess: #460: boot: Success after binutils/gcc/linux/ [...] new 402ea0283b 13: onsuccess: #461: 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 1696 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30932 -> 30248 bytes 04-build_abe-stage1/console.log.xz | Bin 73316 -> 72764 bytes 05-build_abe-qemu/console.log.xz | Bin 31700 -> 31996 bytes 06-build_linux/console.log.xz | Bin 4688 -> 4648 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4384 -> 4452 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/master-aarch64-check_bootstrap updated (806523dde6 -> 53f6737acc)

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 806523dde6 49: onsuccess: #584: 1: Success after binutils/gcc: 148 commits new 53f6737acc 50: onsuccess: #585: 1: Success after binutils/gcc: 44 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1680 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2708 bytes 03-build_abe-binutils/console.log.xz | Bin 38036 -> 37448 bytes 04-build_abe-bootstrap/console.log.xz | Bin 268036 -> 268976 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3824 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2728 -> 2808 bytes 07-check_regression/console.log.xz | Bin 14068 -> 6500 bytes 07-check_regression/extra-bisect-params | 2 +- 07-check_regression/fails.sum | 18 +- 07-check_regression/mail-body.txt | 49 +- 07-check_regression/results.compare | 618 +--- 07-check_regression/results.compare2 | 1819 ++------- 07-check_regression/results.regressions | 96 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 51 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 96 +- sumfiles/g++.log.xz | Bin 3623712 -> 3635080 bytes sumfiles/g++.sum | 269 +- sumfiles/gcc.log.xz | Bin 3214540 -> 3247208 bytes sumfiles/gcc.sum | 5305 ++++++++++++++------------- sumfiles/gfortran.log.xz | Bin 1087828 -> 1080440 bytes sumfiles/gfortran.sum | 52 +- sumfiles/libatomic.log.xz | Bin 2356 -> 2356 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213408 -> 213724 bytes sumfiles/libgomp.sum | 59 +- sumfiles/libitm.log.xz | Bin 2724 -> 2728 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 466224 -> 466908 bytes sumfiles/libstdc++.sum | 10 +- 35 files changed, 3283 insertions(+), 5201 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap updated (b6a90f490c -> ee7b66d021)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap in repository toolchain/ci/base-artifacts. discards b6a90f490c 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 commits discards d83b4db6ef 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits discards 0b1466da42 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits discards 3b28e39842 146: onsuccess: #1573: 2: Success after binutils: 7 commits discards b3933a40e3 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits discards 8e86b771ed 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits discards 4d1f13a002 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits discards 5819892fa9 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] discards 0a58bf2898 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits discards d3038fa375 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits discards bfb6fda6fb 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards 3a60d3ef2a 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] discards 8344e7204d 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards 5f4770833d 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards 303183c1d5 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards dbc84c98a5 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards 8de8695b3c 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards 336945620b 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards 78fa02aa73 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards c745d59691 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards 454a591af0 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards f2d3dc94e7 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards 7995cfd802 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards 6142cf4b3d 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards edd06a0e02 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards 78ba38dec0 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards 1020a2a88b 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards b833d10fb9 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 8714baa7d1 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards 340e573135 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards 97b214103a 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards f6d6dba286 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards bcd2817843 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 89aac0a04e 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 3ccd8937f3 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards d84d611b8a 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards e48ceb93e6 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards 15df5b50a9 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards 7b6369efdf 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 2023b6c634 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards b5be17c291 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards fc30e01ca5 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards 2ba80a7c3c 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 19cdca73d7 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 7e51ff4798 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards 1dc1c42a77 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards d188f8299d 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards dd8d1c8ae1 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards 12a2532a9e 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards 44c7ebb4d9 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 738c8fdac6 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards d2a639d925 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 16731c5caa 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 22e9d596ad 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards e99748b8c7 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 02ff7c2713 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 32b87ee68b 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards d8078e5fe8 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 48c3c647ce 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 30d4c697b9 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards f566f0bcbd 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards b445b8c033 88: onsuccess: 1: Success after gcc: 20 commits discards 68e0bcb775 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards 1bec249d08 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards 2c45a8f723 85: onsuccess: 2: Success after binutils: 4 commits discards f4e08839a1 84: onsuccess: 2: Success after gcc: 9 commits discards 3faef8e62f 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 8655172494 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards cbf6f785bd 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards ff3818fbe5 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards f449ffbbf0 79: onsuccess: 1: Successful build after gcc: 3 commits discards b14c87c840 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards de1394c417 77: force: 2: Successful build after gcc: 32 commits discards 4cac9035bb 76: onsuccess: 2: Successful build after binutils: 10 commits discards 3c7cfb1653 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 93e70c27a4 74: onsuccess: 2: Successful build after gcc: 13 commits discards 5cd67e6054 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards ec2af3a61b 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 1f78d67946 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards d016b68f82 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards a441650377 69: onsuccess: 2: Successful build after baseline build: no [...] discards 72a3a8e8f2 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards b1daf97ea9 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards f88dbd9cc6 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 3e304bbdb9 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 957d828ebb 64: onsuccess: 2: Successful build after gcc: 7 commits discards b8c25854eb 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards cbd36816a3 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 63754cc99c 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards e1fe65398d 60: onsuccess: 1: Successful build after gcc: 15 commits discards fcbc68a6e9 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 611a265c08 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards cadf87e0ee 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards bcc7330e4b 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards b3c320dbbb 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 5a505e86e4 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 75fed7da3c 53: onsuccess: 2: Successful build after gcc: 5 commits discards 4ae6559cd0 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards cc2c6b7512 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 1d58882cde 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards ae2a002a2b 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 826a4e9f38 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 6030583097 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new b8490b8adc 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 988975894d 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 91c0a6c3fb 53: onsuccess: 2: Successful build after gcc: 5 commits new a5bb581b58 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new eb875ba1f4 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new db1bff7504 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 6355bb7d85 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new a4415d2ce0 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new cc0bc0ad2a 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new f02607d5c2 60: onsuccess: 1: Successful build after gcc: 15 commits new 55d17ae059 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 6dca9da0ed 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ce51c007b3 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new d17761fdb0 64: onsuccess: 2: Successful build after gcc: 7 commits new 6e576540e1 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 6b5a352522 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 705cb1c887 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 37865c0590 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 1b9a0e68a5 69: onsuccess: 2: Successful build after baseline build: no [...] new 772729ddf6 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 6aca6bb332 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 1c54fb73ec 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new ce1bd66462 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new d0d7930e3a 74: onsuccess: 2: Successful build after gcc: 13 commits new f7781f4deb 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 84c8576e7f 76: onsuccess: 2: Successful build after binutils: 10 commits new 26fb8a6d79 77: force: 2: Successful build after gcc: 32 commits new e9797a7c6f 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 18e7321282 79: onsuccess: 1: Successful build after gcc: 3 commits new 05669a632a 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 71a612a71f 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 54e20ab4b3 82: onsuccess: 2: Success after binutils/gcc: 26 commits new a4c49ae8d3 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 149248a158 84: onsuccess: 2: Success after gcc: 9 commits new c56becdde4 85: onsuccess: 2: Success after binutils: 4 commits new 16256ceae2 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new a2fac8668a 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new 465b3e8e31 88: onsuccess: 1: Success after gcc: 20 commits new 5355cf6daf 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 792a7a5bdd 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 8d3eff201d 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 6b1fd6ce19 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 57198f2c59 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new 0639eace09 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new 62751df599 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 2208158987 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 54804229b9 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 1f75bf8ed9 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 5a9c1208f0 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 11476046a0 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new baef9e0521 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new f1cfc6ba11 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 964e9f8925 103: onsuccess: #1524: 2: Success after gcc: 2 commits new cf162303a3 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 05e26092a1 105: onsuccess: #1526: 2: Success after gcc: 2 commits new e6755db199 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 34379e9698 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new 4eb547021b 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 7f78e02fb2 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new b72bef24ff 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 5737bfcfc2 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 0f6c0b9ca3 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 94a86a4f2d 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new 27c9bdc28e 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 3449903c77 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new e9d65ab56c 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 10d7c10645 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new a44d7d8a77 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new ce0f7cc3b1 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new d4329e63a9 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 9d3dc26928 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new b792ef0bc5 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 0e55212faf 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 4d75bf9fa7 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new a73a391a8b 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new 277ac9da8b 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new b80125c53e 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new 78edd610f5 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new a2c60d6c5d 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new eeeef968ca 130: onsuccess: #1554: 2: Success after gcc: 9 commits new ba24f20a0c 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new 84c2b1fdd0 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new 84e41f5f4a 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new 0289124de4 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new e1791e8333 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new fd149a3a40 136: onsuccess: #1561: 2: Success after binutils: 3 commits new ebd361714a 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new ce64493a65 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] new 0743fa020e 139: onsuccess: #1566: 1: Success after gcc: 5 commits new c2f8ca5c1a 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits new 31e50d1a2b 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits new 80a3cdb044 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] new 94cb635dcb 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits new 4ea8dfe22d 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits new e2a8e7662c 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits new 6d29c8f282 146: onsuccess: #1573: 2: Success after binutils: 7 commits new b4a9d7d73d 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits new 32e6b657bc 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits new 96f9c188f8 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 commits new ee7b66d021 150: onsuccess: #1577: 2: Success after gcc: 3 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (b6a90f490c) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] 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 1720 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 38304 -> 38324 bytes 05-build_abe-bootstrap/console.log.xz | Bin 274448 -> 271232 bytes 06-check_regression/console.log.xz | Bin 2824 -> 2572 bytes 07-update_baseline/console.log | 40 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 ++++++------ 12 files changed, 32 insertions(+), 32 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 (be22469ea3 -> ff621dbcb5)

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 be22469ea3 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards 93c9a8b712 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 909886b2ce 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards b447b3fc1d 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 180c584964 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards f3242af5c9 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 9e8b035568 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 21a74ea47c 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards c2def89621 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 87653b3735 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 2014e9cd8c 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards ccd92d4aa9 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards eadf6c8eed 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards a64a1e272a 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 46488db0ab 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 949a6c62a1 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 6a8f680e3e 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards ebaaad2962 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards d239fdee81 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 76a32cb3b2 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 826e20d11e 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 1e01781b70 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards bb62a55664 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards e350d9987a 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 5903740896 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 578bf3a719 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 2a7855faf8 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 2792f465d8 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 8fa8ffe3e3 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 4960880e1f 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 86664e8516 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 219f6065dd 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 144cc3eded 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards a981689307 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards d3a23cb3e4 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 0153a9a2cb 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 4f30537b55 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 54fb90f967 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards e0066dd6f1 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards ffba6f748f 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 25823e2216 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 95bff9c995 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 6283e6ced7 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards cf590efcdd 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 9a22133d13 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 602fae82cc 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards c3bef21ba6 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 39adf8cc24 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 14ac9a099b 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards b2c4262913 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards df67eef8a0 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 7174c5f6f4 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 37a4d92771 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 29429d71f1 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 22aeca399b 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 533a61f689 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards f0a73b0ad5 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 5ac05d11c3 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards c2600f27af 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 528a801d5b 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 3ba5601b0f 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 184ab19a71 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 556a3b0663 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards e3479b08ed 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards e8288fc131 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards e54f133e71 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards adf05ba43b 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards c7d9223c89 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 3364880c6f 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 6d77c265c9 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 5ddbbff27e 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 17d6de449a 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 200f42b170 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 76f5b070ee 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 451d7dbe39 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b2cbfd1263 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 986e545050 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 53fc1bc285 74: onsuccess: 1: Successful build after linux: 44 commits discards 21215796ef 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 74a81fb194 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d7a51559de 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 5ef792ad56 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards ed8c9f3ea1 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards a53320e710 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 64f4be014b 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 02dda90490 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2009a6fc70 65: onsuccess: 1: Successful build after gcc: 4 commits discards af278c90d8 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4c4acb4f4b 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 315e609fe8 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards c8a9710061 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 245aa6b28c 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards d3aa5d91b0 59: onsuccess: 1: Successful build after glibc: 2 commits discards fd5454f717 58: onsuccess: 1: Successful build after binutils: 2 commits discards 700be9be19 57: onsuccess: 1: Successful build after gcc: 7 commits discards 451f7f1b15 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e2c3245533 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0eed999457 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 7e834a6fef 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards b2958b3c3b 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards fb27844bcd 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new dd39213e0b 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 06420c7c7c 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 0688911fb7 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 39172c2e80 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 03eb593d1a 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5d8748cb2d 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 339e4e945e 57: onsuccess: 1: Successful build after gcc: 7 commits new 6e177482ef 58: onsuccess: 1: Successful build after binutils: 2 commits new 65af3c3fea 59: onsuccess: 1: Successful build after glibc: 2 commits new 2d63cc63d6 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new b2ea7b0380 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new e9265d5f66 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 1c788be814 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2db3a1a7f3 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b47ec9fca8 65: onsuccess: 1: Successful build after gcc: 4 commits new 4ab06fdddc 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 12eabb1d94 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new db6032f131 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a0d9f01b1b 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 0d8ab57085 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 0e12ff442e 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 155e968124 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bb09e1d495 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 5d49feac1f 74: onsuccess: 1: Successful build after linux: 44 commits new f7aa18647d 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 698245907e 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new add019f0ff 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 39228cefdd 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new f3b145f502 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 787a2c277f 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 3f69ca9ce0 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 991676dc99 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new f3eb8dc38b 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 6187bab771 84: onsuccess: 1: Success after gcc/glibc: 9 commits new b073c139a2 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new e2461ac2cf 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 47515cd280 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 576b82762b 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 37d1a1ae5f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 9d52fdba53 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 9eee0cb5eb 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 861572f7c4 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 88ccc41a41 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new e474484e94 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new ab9645916e 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 599745eb24 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new f4efd47fa9 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 03d7a7f7e6 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 87c62c8f8e 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 4244d31dd2 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 9ae613b91d 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 39b82befcd 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 8cf311e582 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new bc75d391f6 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 15ea730c70 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 6884d2ae4c 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 2ecba69575 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new cb4dc7ea42 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 7e97687fb8 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 3ebe1593d7 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 356277c100 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 2c5cda828f 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new ef382abf50 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 4ee84a9b94 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new c7c0451111 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new bcf87233c2 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 135ef10d37 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 3a93a2a3f0 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new fe49b21234 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 3a2992c529 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 13ce89ec29 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new ee5cb5f870 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 55037aaa95 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new df0907cf82 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 44e7a26ba7 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new a7f854a471 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new de42f3f702 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 6988545518 128: onsuccess: #1723: 1: Success after linux: 12 commits new d2f395d18d 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 6789dc87b5 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 8fc0a90ff0 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new d4b6c07010 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new b34e037cf2 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new d9ff36d65e 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 7f05b6169d 135: onsuccess: #1733: 1: Success after binutils: 5 commits new effd140662 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new feffe4ff61 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 6781fbda9e 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 57fbed27c3 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new b61fdb3f75 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 0f77eb2d08 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 83fa9c15ba 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new f502d4b80f 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 2370dabc5e 144: onsuccess: #1743: 1: Success after glibc: 2 commits new b0c205f361 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 4a1f0daa06 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new b116803e8f 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 8c86bef3f5 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new a6fc1ce02f 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new b16227dd10 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 1d951e2f2b 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new ff621dbcb5 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (be22469ea3) \ 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 1684 -> 1920 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30040 -> 29916 bytes 04-build_abe-stage1/console.log.xz | Bin 91148 -> 90860 bytes 06-build_abe-linux/console.log.xz | Bin 8804 -> 8612 bytes 07-build_abe-glibc/console.log.xz | Bin 234236 -> 234432 bytes 08-build_abe-stage2/console.log.xz | Bin 223816 -> 224160 bytes 09-build_abe-gdb/console.log.xz | Bin 37436 -> 37192 bytes 10-build_abe-qemu/console.log.xz | Bin 31292 -> 31368 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3172 -> 2820 bytes 13-check_regression/console.log.xz | Bin 5316 -> 6464 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 61 +- 13-check_regression/results.compare | 29 +- 13-check_regression/results.compare2 | 48 +- 13-check_regression/results.regressions | 40 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 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 | 63 +- mail/mail-subject.txt | 2 +- manifest.sh | 35 +- results | 40 - sumfiles/g++.log.xz | Bin 2667116 -> 2691360 bytes sumfiles/g++.sum | 37 +- sumfiles/gcc.log.xz | Bin 2229916 -> 2202388 bytes sumfiles/gcc.sum | 2401 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 885780 -> 881524 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201444 -> 201600 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 425100 -> 422168 bytes sumfiles/libstdc++.sum | 11 +- 43 files changed, 1355 insertions(+), 1509 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-lts-allyesconfig updated (04e7906219 -> 4cfff418f8)

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-arm-lts-allyesconfig in repository toolchain/ci/base-artifacts. from 04e7906219 16: onsuccess: #465: 33: Success after binutils/gcc/linux/qe [...] new 4cfff418f8 17: onsuccess: #466: 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 1708 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30128 -> 30008 bytes 04-build_abe-stage1/console.log.xz | Bin 90572 -> 91192 bytes 05-build_abe-qemu/console.log.xz | Bin 31532 -> 31636 bytes 06-build_linux/console.log.xz | Bin 4892 -> 3612 bytes 08-check_regression/console.log.xz | Bin 4404 -> 4364 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, 24 insertions(+), 33 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