Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap updated (99f42d082 -> ab36b0cad)

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 99f42d082 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-271 [...] discards 4e6c827e5 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 98b1feb2c 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-271 [...] discards 5d13638eb 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards c9ac3f0e9 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards 7c3e7021e 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards d6f33a593 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 0c53ad48a 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards 08a141a49 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards 64af4ac60 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards ceaf9ed61 99: onsuccess: #1455: 2: Success after baseline build: no new [...] discards 7cdc0a4f9 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-2393 [...] discards b8897a541 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 0218e78a7 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 1d920daae 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-2389 [...] discards df7a89c4c 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP 5 [...] discards 46e70672e 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards 670868fb6 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards e003d811e 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards 46a180aae 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards 7808153ed 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards a3fdb2917 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards c23c17f00 87: onsuccess: 2: Success after gcc: 4 commits discards b86d0a0e7 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards a37d257fd 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 584ae1dbd 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards c0caeadbd 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 0f00f0912 82: onsuccess: 1: Successful build after gcc: 3 commits discards 3e272bc3e 81: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] discards 7c4ba746d 80: force: 2: Successful build after gcc: 14 commits discards f79c3d3c8 79: onsuccess: 2: Successful build after binutils: 5 commits discards 0ed94b61e 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards fcae232af 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 82dcf60a3 76: onsuccess: 2: Successful build after gcc: 12 commits discards 89f0c5726 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 96b441578 74: onsuccess: 2: Successful build after baseline build: no n [...] discards 8e99ffcd8 73: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] discards 4c135374c 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 862d0024e 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 59c7d496f 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 9c0181c79 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards bacac9da4 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards e9fb0537f 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards a6a63555d 66: onsuccess: 2: Successful build after gcc: 9 commits discards 42671a815 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 1b876b23d 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 8bf0db122 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 0a8659e1b 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 15e8e695d 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards 5e07c8c5f 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards 956423056 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] discards 5a8f189a4 58: force: 2: Successful build after gcc: 6 commits discards 59b59cc3b 57: onsuccess: 2: Successful build after binutils: gdb: new ' [...] discards 342edb60f 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards d892bf9ff 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 1301eddef 54: onsuccess: 2: Successful build after gcc: 5 commits discards bd3226d59 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 560a41022 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 0d880deec 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 5c3c6ff55 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards e2690741d 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 2580645be 48: onsuccess: 2: Successful build after gcc: 4 commits discards dd6862ff8 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 04060cdf9 46: onsuccess: 2: Successful build after baseline build: no n [...] discards e2f725613 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards 5b4556c55 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards d9755dba9 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] discards dfd397af7 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] discards 95435db27 41: onsuccess: 2: Successful build after gcc: libcpp: Impleme [...] discards d53aac1aa 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards f419e5414 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 556aea462 38: onsuccess: 2: Successful build after gcc: 2 commits discards 946c113d1 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards fe8b24ca7 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 627de489e 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 597e5ace2 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 70225d4b9 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 66e26b791 32: onsuccess: 2: Successful build after gcc: 6 commits discards 589a53f65 31: onsuccess: 2: Successful build after gcc: 6 commits discards b0c524c7d 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards a17730306 29: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards a7206b491 28: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 1ad955018 27: onsuccess: 2: Successful build after binutils/gcc: 14 commits discards b450988e7 26: onsuccess: binutils-gcc: 2 discards d8aff61bc 25: onsuccess: binutils-gcc: 2 discards 8d2b29fd5 24: onsuccess: binutils-gcc: 2 discards 000ea7364 23: onsuccess: binutils-gcc: 2 discards 1e8ca5b72 22: onsuccess: binutils-gcc: 2 discards 575708393 21: onsuccess: binutils-gcc: 2 discards 32bbe9fed 20: onsuccess: binutils-gcc: 2 discards 2f61755d3 19: onsuccess: binutils-gcc: 2 discards 3648023ea 18: onsuccess: binutils-gcc: 2 discards 0657a8efc 17: onsuccess: binutils-gcc: 2 discards 1d680a369 16: onsuccess: binutils-gcc: 2 discards 1741fb0c2 15: onsuccess: binutils-gcc: 2 discards bb84dfd9f 14: onsuccess: binutils-gcc: 2 discards 7d5069b06 13: onsuccess: binutils-gcc: 2 discards 76b0ecd83 12: onsuccess: binutils-gcc: 2 discards fed7df753 11: onsuccess: binutils-gcc: 2 discards 714ce525e 10: onsuccess: binutils-gcc: 2 discards ec12251a5 9: onsuccess: binutils-gcc: 2 new a48e5601d 9: onsuccess: binutils-gcc: 2 new 45a965cb3 10: onsuccess: binutils-gcc: 2 new 7fc699b9c 11: onsuccess: binutils-gcc: 2 new 1ca4f9b33 12: onsuccess: binutils-gcc: 2 new 726a262f6 13: onsuccess: binutils-gcc: 2 new 48ed1e0fd 14: onsuccess: binutils-gcc: 2 new a70202584 15: onsuccess: binutils-gcc: 2 new 8fc3e3d0c 16: onsuccess: binutils-gcc: 2 new bf64b1338 17: onsuccess: binutils-gcc: 2 new 9bbcc670e 18: onsuccess: binutils-gcc: 2 new 2e75f9106 19: onsuccess: binutils-gcc: 2 new 40e08149d 20: onsuccess: binutils-gcc: 2 new ee0082290 21: onsuccess: binutils-gcc: 2 new 999430bd4 22: onsuccess: binutils-gcc: 2 new 27046cede 23: onsuccess: binutils-gcc: 2 new 1d595e73f 24: onsuccess: binutils-gcc: 2 new 49abaf7c3 25: onsuccess: binutils-gcc: 2 new 17e060d5a 26: onsuccess: binutils-gcc: 2 new 4940ff966 27: onsuccess: 2: Successful build after binutils/gcc: 14 commits new 099147e4c 28: onsuccess: 2: Successful build after binutils/gcc: 8 commits new e2d9d0d5a 29: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 86fdc04e4 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits new e4c8502bc 31: onsuccess: 2: Successful build after gcc: 6 commits new 2d0370042 32: onsuccess: 2: Successful build after gcc: 6 commits new 05a27f17b 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits new b8d59f42a 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 69b1ad1f1 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 7fd4e3401 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits new ce3f7723e 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits new b0bb3fbd2 38: onsuccess: 2: Successful build after gcc: 2 commits new 6ec357ce2 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 3b0e752fd 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new e022ae7b4 41: onsuccess: 2: Successful build after gcc: libcpp: Impleme [...] new 5ddb7c18d 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] new d0ceb93ff 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] new a19c3f458 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new a892e3e53 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new e9f30a16d 46: onsuccess: 2: Successful build after baseline build: no n [...] new 4d03a259b 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 9c724b831 48: onsuccess: 2: Successful build after gcc: 4 commits new 8c8b3ada2 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new b6791b9c3 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 96ba00465 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 7add1e434 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 1d361e139 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 988871b3e 54: onsuccess: 2: Successful build after gcc: 5 commits new b2e43c219 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 1e46cac80 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 6b9b74927 57: onsuccess: 2: Successful build after binutils: gdb: new ' [...] new 5e43b2f92 58: force: 2: Successful build after gcc: 6 commits new 193ee8ac9 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] new 9cf848c9d 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 712aeb2b8 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new 4a68b6437 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new fcf24bca4 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 3bb47f854 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ac3ab2caf 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 632ea0807 66: onsuccess: 2: Successful build after gcc: 9 commits new 9a9510a0b 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new b190560ca 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 09118ee55 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 71d3b59cb 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new e37267238 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new d997a82e2 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 7a2a3cc70 73: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] new 321aba584 74: onsuccess: 2: Successful build after baseline build: no n [...] new 2e2b73678 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 744b46b96 76: onsuccess: 2: Successful build after gcc: 12 commits new 62c336569 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 54a2e2e53 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new d9ef5a549 79: onsuccess: 2: Successful build after binutils: 5 commits new 55cbd4969 80: force: 2: Successful build after gcc: 14 commits new e5499d1c9 81: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] new 4fa47ba9d 82: onsuccess: 1: Successful build after gcc: 3 commits new 27b034d06 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new 7c2fd729c 84: onsuccess: 2: Success after binutils/gcc: 15 commits new 858a94998 85: onsuccess: 2: Success after binutils/gcc: 25 commits new 9937af82e 86: onsuccess: 2: Success after binutils/gcc: 10 commits new dfc144e5c 87: onsuccess: 2: Success after gcc: 4 commits new a3954bb70 88: onsuccess: 2: Success after binutils/gcc: 25 commits new f6fc52597 89: onsuccess: 2: Success after binutils/gcc: 4 commits new d5751639d 90: onsuccess: 2: Success after binutils/gcc: 16 commits new dd3ead0b2 91: onsuccess: 2: Success after binutils/gcc: 7 commits new e0babab80 92: onsuccess: 2: Success after binutils/gcc: 9 commits new 6f94f31b2 93: onsuccess: 2: Success after binutils/gcc: 3 commits new 23ef84c47 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP 5 [...] new 580b67fb8 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-2389 [...] new 91cb905be 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 85d16925c 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new 87287c364 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-2393 [...] new ecab5de36 99: onsuccess: #1455: 2: Success after baseline build: no new [...] new e1e1c3707 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 43d8b5d6e 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new b0c2bf3c8 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new bbdfb7f40 103: onsuccess: #1504: 2: Success after gcc: 2 commits new d619a0972 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new 832ba1b66 105: onsuccess: #1506: 2: Success after gcc: 2 commits new 130a949d2 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 20deb853a 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-271 [...] new f71c8159c 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 988f08558 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-271 [...] new ab36b0cad 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (99f42d082) \ 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 1672 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2752 bytes 04-build_abe-binutils/console.log.xz | Bin 50768 -> 50960 bytes 05-build_abe-bootstrap/console.log.xz | Bin 466872 -> 462500 bytes 06-check_regression/console.log.xz | Bin 1804 -> 1940 bytes 07-update_baseline/console.log | 64 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++----- 13 files changed, 47 insertions(+), 47 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_ubsan updated (ac7f28ca1 -> 4bb54415a)

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/release-arm-bootstrap_ubsan in repository toolchain/ci/base-artifacts. from ac7f28ca1 12: onsuccess: #132: 2: Success after binutils/gcc: 10 commits new 4bb54415a 13: onsuccess: #133: 2: Success after binutils/gcc: 9 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 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2708 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 51972 -> 50436 bytes 05-build_abe-bootstrap_ubsan/console.log.xz | Bin 525220 -> 524948 bytes 06-check_regression/console.log.xz | Bin 2116 -> 2104 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 12 files changed, 15 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto_lean updated (980919029 -> 26e0ca5ff)

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_profiled_lto_lean in repository toolchain/ci/base-artifacts. from 980919029 39: onsuccess: #418: 2: Success after binutils/gcc: 6 commits new 26e0ca5ff 40: onsuccess: #419: 2: Success after binutils/gcc: 7 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 1732 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 38504 -> 38676 bytes .../console.log.xz | Bin 521384 -> 520204 bytes 06-check_regression/console.log.xz | Bin 2032 -> 2088 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 ++++++++-------- 12 files changed, 14 insertions(+), 14 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (68c6bc796e -> 2adfa206a2)

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 68c6bc796e 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 8ed1b6c335 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 713c91de09 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 9898da4527 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards d799c6ddec 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 0232a82286 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards b48a4d6c67 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards a23636e8c1 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards cabc41cb6c 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards ad7a3943c1 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards e81f6d71e4 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 0d8ff268ab 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 49dcdb1984 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 7093248b68 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards f4ce6d3f73 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards a26e61489c 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards ded1079cfd 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards d8382c41d0 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 895338c080 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards ca35406e94 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards bee4ee6a0d 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 8710f88e24 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 74e377a225 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 80ef7c9477 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 1bb731cb4d 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 73be7b7eb1 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards c197bafc02 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 5deb93c8cc 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 21b0b48746 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3700eb112b 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards be113203e8 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 9ed5bd9cca 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 24f18710d9 74: onsuccess: 1: Successful build after linux: 44 commits discards b3bab9d064 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 0177a41f92 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ad25a1aeb3 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards d4ebaa0de7 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards b53781fcfe 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 553f6e8f9f 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6b91e4f9fb 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a3c0d849e1 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 8023dfd518 65: onsuccess: 1: Successful build after gcc: 4 commits discards fb1c0c38d7 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 92aabb69dc 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b0da992dd6 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 9fae3404e7 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 948aea6482 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 26eb1864b5 59: onsuccess: 1: Successful build after glibc: 2 commits discards 2f3793e59a 58: onsuccess: 1: Successful build after binutils: 2 commits discards b9a18d4884 57: onsuccess: 1: Successful build after gcc: 7 commits discards 43597fc912 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d6a22debcb 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c2930cbfb3 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 9150dce748 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 192559c1b2 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 40e8a67465 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 05d990cd5a 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 826750db48 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f8bbe16bcf 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards a60c1a758d 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c9607f5f16 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 4c49f08f6f 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5a0e42385c 44: onsuccess: 1: Successful build after linux: 34 commits discards 42ece4c6e0 43: onsuccess: 1: Successful build after gcc: 2 commits discards 0b44c1923d 42: onsuccess: 1: Successful build after baseline build: no [...] discards 43f4c842e5 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c9e1f3ad6f 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c145675fab 39: onsuccess: 1: Successful build after gcc: 2 commits discards de03bf3b2e 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 818e90bd90 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 25a28f43b2 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4fe49d9a56 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 45d7a55a69 34: onsuccess: 1: Successful build after gcc: 3 commits discards 4397ffc737 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b650ad00d1 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 7255ea3cc8 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards cb96c2bf40 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards c9420d769b 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards db008e5e2c 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 59aff2dcfc 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ae8f3d59be 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 52bb4dd59f 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e7063eb688 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 25a73d5f84 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5e86024a65 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8c5700423d 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2236cb17e3 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 32c74b0b07 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a6064e2f6c 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5193ed4294 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 01e6e39389 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2712d7b6ae 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards eda44fe668 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a29c18aacc 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1026504c7c 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6cc7c1a22e 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8b76c7fde2 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 0f67fca95c 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 818201c92a 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c5875a60d0 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7465676c35 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2a411260f0 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7ee3c50fb0 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8949ac312c 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7f3ea2cef4 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 17c1bd196b 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2ca5c67d60 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b9e70264c7 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 194de195c2 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a78ba57480 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new df214d17c4 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b6b86948d9 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 30d0fc1695 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new dc516e545e 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2ba30c93fe 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new aef029d994 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e6016ee31d 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2ac055f48a 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7e1a6ca3c8 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e53bbc4bd4 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 895f20ff6d 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f895094252 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 21872ed293 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 9ebbafc1a8 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new b6197d9193 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 18bb267bc2 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 0490e0850a 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 27a609e36d 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new b6a2cd5d2e 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4f1ca5579d 34: onsuccess: 1: Successful build after gcc: 3 commits new 83ef60dad3 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 5469dc6e4b 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 287623755f 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 5ce2c91155 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e6752971aa 39: onsuccess: 1: Successful build after gcc: 2 commits new f50318db8a 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 46dc21173c 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 20c8452a5b 42: onsuccess: 1: Successful build after baseline build: no [...] new 02e416a11b 43: onsuccess: 1: Successful build after gcc: 2 commits new 8b9abcf74a 44: onsuccess: 1: Successful build after linux: 34 commits new faac3f9534 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d6f00e76f3 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 4784448446 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 74347fdcaf 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new e8539ce43f 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 18a202fd05 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 47d5a0ee8e 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ac86fdf74f 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new b3db204ecb 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new dbde0bb9b1 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new b9fb0cce6c 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7ec77e4d2d 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cb4c9a5b7c 57: onsuccess: 1: Successful build after gcc: 7 commits new 97434561fc 58: onsuccess: 1: Successful build after binutils: 2 commits new 62365ffb88 59: onsuccess: 1: Successful build after glibc: 2 commits new cab83a4596 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new ad49bd104c 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 569d986a4a 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new c7365b3879 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7235f5ef89 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 93883b81c5 65: onsuccess: 1: Successful build after gcc: 4 commits new 4596614932 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 78526e1945 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 263abe4926 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 37db33b538 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 5699e31d1f 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 48ff41a310 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 7618648ecb 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ecd2200422 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 244549c5bc 74: onsuccess: 1: Successful build after linux: 44 commits new 9bc994461e 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9744764c16 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 1e8b24dcc2 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new faea5e2147 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new bb799d06e1 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 20902eae2e 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 7c4ea452cc 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 429aa3bd25 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 75acce6221 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 9c0bb3f15c 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 5ac1253750 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new df2e3926f3 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new a059c3597f 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new f585e0e317 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new e43e423aa1 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new b525ff7e88 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 3d9feecf27 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new b340758fd2 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 8c371a4d3e 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new e29c782e21 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 676f2a7a11 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new b7f5b30449 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new d39daa612c 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 85665bc36a 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 4715bb62c8 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new d80f5dee81 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new ceb17611aa 101: onsuccess: #1693: 1: Success after glibc: 14 commits new fd293db8be 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 4563482b0a 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 8b05a72c8c 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 7a8a678c14 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new a8da0c9018 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 2adfa206a2 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/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 (68c6bc796e) \ 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 1676 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 29876 -> 30180 bytes 04-build_abe-stage1/console.log.xz | Bin 90268 -> 90908 bytes 06-build_abe-linux/console.log.xz | Bin 8304 -> 8296 bytes 07-build_abe-glibc/console.log.xz | Bin 234416 -> 233668 bytes 08-build_abe-stage2/console.log.xz | Bin 222976 -> 223788 bytes 09-build_abe-gdb/console.log.xz | Bin 37016 -> 37344 bytes 10-build_abe-qemu/console.log.xz | Bin 31872 -> 31304 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2436 -> 2792 bytes 13-check_regression/console.log.xz | Bin 5252 -> 5404 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 17 +- 13-check_regression/mail-body.txt | 67 +- 13-check_regression/results.compare | 41 +- 13-check_regression/results.compare2 | 70 +- 13-check_regression/results.regressions | 41 +- 14-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 69 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 41 +- sumfiles/g++.log.xz | Bin 2658780 -> 2658708 bytes sumfiles/g++.sum | 4 +- sumfiles/gcc.log.xz | Bin 2230276 -> 2209524 bytes sumfiles/gcc.sum | 2236 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 882176 -> 879452 bytes sumfiles/gfortran.sum | 83 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201292 -> 201008 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429104 -> 424208 bytes sumfiles/libstdc++.sum | 8 +- 43 files changed, 1520 insertions(+), 1279 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap updated (e0a4d4aeb0 -> 208bb7c4ba)

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 e0a4d4aeb0 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards d3a72888ec 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards ff0eb61714 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 109dab1a51 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards 40689e6738 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards 17a367aeb1 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 2d63cf4fd1 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards 90ecabe337 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards 4d21d74311 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 0069d7cbeb 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards 8f386e4381 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 78576c2332 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 6179368432 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards 5f57026f41 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 2820e717c0 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 62023c2769 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 15376059d6 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards f1cc7c56d8 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 70faf1ae1b 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards e6cc686e39 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 49a3c713cd 88: onsuccess: 1: Success after gcc: 20 commits discards e2727b7988 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards b88ea3b241 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards 466ac7f72f 85: onsuccess: 2: Success after binutils: 4 commits discards 7e51a222ae 84: onsuccess: 2: Success after gcc: 9 commits discards 1aa2cc8a78 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 9f851489b3 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards e7761c45d3 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 8fc643901f 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards b13c3bd560 79: onsuccess: 1: Successful build after gcc: 3 commits discards 91350c9f47 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards bbc7428158 77: force: 2: Successful build after gcc: 32 commits discards 0e14954010 76: onsuccess: 2: Successful build after binutils: 10 commits discards 437d2159f4 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 277dd31b63 74: onsuccess: 2: Successful build after gcc: 13 commits discards 901446d471 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards ddc46699ef 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 85c8667e40 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 67fbc23fdc 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards af291393aa 69: onsuccess: 2: Successful build after baseline build: no [...] discards c91f8d5a72 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 5ce11f80dd 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 04af07eef4 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 1b18ca4316 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 6ecf6006ef 64: onsuccess: 2: Successful build after gcc: 7 commits discards 528ae452f7 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 8b18776b0c 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 09862662fd 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards c2469ab667 60: onsuccess: 1: Successful build after gcc: 15 commits discards f0347b552e 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 2e66986f61 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards 94e69e2d9c 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards abc2a1663b 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards acb2d9a6f4 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 108d85308d 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards af65653cfc 53: onsuccess: 2: Successful build after gcc: 5 commits discards 40f2a17c05 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 65e703f196 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 19eeb853ed 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 8047587048 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 4975f7dd6c 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 5216ce2ab7 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards dc992cb364 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 90500c97d6 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards 1f77c02cb8 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards e0bf3831da 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards 200d255b41 42: onsuccess: 2: Successful build after gcc: 2 commits discards 619a2f9d7d 41: onsuccess: 2: Successful build after baseline build: no [...] discards 41b4b92e1a 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 7f3cfda3d9 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 8f2aa2198b 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 7d1b06184a 37: onsuccess: 2: Successful build after gcc: 2 commits discards 557ecdeb4b 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 4b6c65b572 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards fe5f451992 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 401a5e2a22 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 7f0069543a 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 54cb62fb8c 31: onsuccess: 2: Successful build after gcc: 8 commits discards 765b97156e 30: onsuccess: 2: Successful build after gcc: 7 commits discards 29bdc821b1 29: onsuccess: 2: Successful build after binutils: 5 commits discards 1e51294d60 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 912b632fd3 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards c34c4c652d 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits discards 86609a055e 25: onsuccess: binutils-gcc: 2 discards 7481b72add 24: onsuccess: binutils-gcc: 2 discards 8b316ec5ec 23: onsuccess: binutils-gcc: 2 discards 713858b5ad 22: onsuccess: binutils-gcc: 2 discards 51147fd63a 21: onsuccess: binutils-gcc: 2 discards b2b6b773f4 20: onsuccess: binutils-gcc: 2 discards 8905280857 19: onsuccess: binutils-gcc: 2 discards 076f1474d9 18: onsuccess: binutils-gcc: 2 discards fffd0f7ca4 17: onsuccess: binutils-gcc: 2 discards cd4568f55a 16: onsuccess: binutils-gcc: 2 discards 7266527397 15: onsuccess: binutils-gcc: 2 discards e42fba7035 14: onsuccess: binutils-gcc: 2 discards 2815484c39 13: onsuccess: binutils-gcc: 2 discards bda3c14ef9 12: onsuccess: binutils-gcc: 2 discards effb376014 11: onsuccess: binutils-gcc: 2 discards 5d9af76f7f 10: onsuccess: binutils-gcc: 2 discards 0929ea750a 9: onsuccess: binutils-gcc: 2 discards bf0d8b9964 8: onsuccess: binutils-gcc: 2 new 64965edf35 8: onsuccess: binutils-gcc: 2 new 19cb1b0f9e 9: onsuccess: binutils-gcc: 2 new 1ab8cbf39e 10: onsuccess: binutils-gcc: 2 new 13dac8e290 11: onsuccess: binutils-gcc: 2 new 59c2382a10 12: onsuccess: binutils-gcc: 2 new 4ec931d44e 13: onsuccess: binutils-gcc: 2 new 6d817b6c2e 14: onsuccess: binutils-gcc: 2 new 3e902d222f 15: onsuccess: binutils-gcc: 2 new cd6209d282 16: onsuccess: binutils-gcc: 2 new f744fb4ed1 17: onsuccess: binutils-gcc: 2 new b6e549fa75 18: onsuccess: binutils-gcc: 2 new 9543fafaf3 19: onsuccess: binutils-gcc: 2 new ae4e1b20ea 20: onsuccess: binutils-gcc: 2 new e0d7f4a335 21: onsuccess: binutils-gcc: 2 new efa90b8cce 22: onsuccess: binutils-gcc: 2 new cab0bd1669 23: onsuccess: binutils-gcc: 2 new 6d89f22dd8 24: onsuccess: binutils-gcc: 2 new ea1186019c 25: onsuccess: binutils-gcc: 2 new 46cbe228a2 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits new e30b1e3d90 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits new d9a26526d8 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits new c08b18b4f6 29: onsuccess: 2: Successful build after binutils: 5 commits new c157a51330 30: onsuccess: 2: Successful build after gcc: 7 commits new 0822ecd200 31: onsuccess: 2: Successful build after gcc: 8 commits new 0404e3c49c 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 89cef886a7 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits new e09734200e 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits new fee1af4bb6 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 8222311dd5 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 2b592f536b 37: onsuccess: 2: Successful build after gcc: 2 commits new 38443b49b2 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 880d692790 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 88f9f91c79 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 4e3c5f8974 41: onsuccess: 2: Successful build after baseline build: no [...] new 6e4ad1f533 42: onsuccess: 2: Successful build after gcc: 2 commits new 16b8e360f8 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new a5f3f5b2ba 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 5eb69a213e 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 8873dd5970 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 6603ae1e7e 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ccfb29059d 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 399508d3b6 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 75eb0cec56 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new cd59d05d7f 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 4d33e291cc 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new cef5c42440 53: onsuccess: 2: Successful build after gcc: 5 commits new 76c7ec7494 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 74a965d925 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new c8e05218e4 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new d6fbd02d22 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 2e682bc340 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new 8de4029ad3 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new d431f50b56 60: onsuccess: 1: Successful build after gcc: 15 commits new ce63f1e78f 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 73baa69613 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new f6ba541da1 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 53d39f3dde 64: onsuccess: 2: Successful build after gcc: 7 commits new ff2f4d5f08 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 860d8d4f57 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 6c32ac2eec 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 9d4ed54281 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 2b13b79ed4 69: onsuccess: 2: Successful build after baseline build: no [...] new 990518f912 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 62d86c05b3 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 7ef0feacd4 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new f13015b75e 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 8b3a608691 74: onsuccess: 2: Successful build after gcc: 13 commits new 066f5d9625 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 6031ace44a 76: onsuccess: 2: Successful build after binutils: 10 commits new da12104792 77: force: 2: Successful build after gcc: 32 commits new 6a2f086b67 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 02df05937f 79: onsuccess: 1: Successful build after gcc: 3 commits new 0a4f5e9935 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new de867070c9 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 3d523e7267 82: onsuccess: 2: Success after binutils/gcc: 26 commits new aa3769b836 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 73a017a19a 84: onsuccess: 2: Success after gcc: 9 commits new d04fb39571 85: onsuccess: 2: Success after binutils: 4 commits new 7e0ea5ca33 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new 9f04f1d2a3 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new 4d744a6b9a 88: onsuccess: 1: Success after gcc: 20 commits new 8c0604c437 89: onsuccess: 2: Success after binutils/gcc: 39 commits new d9a77f5754 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 9d58c5b071 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 66fd21edcb 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new e90af6ce06 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new 72d382118e 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new ca396ccf0d 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 6318d63e9f 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 04aeddfaa2 97: onsuccess: #1481: 2: Success after gcc: 8 commits new b03c61f752 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new e66eb0c4e5 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new ba537ba30d 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new 0a8caa56af 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new 4e880f0f9c 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new e5f275b5b4 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 2033e0b2fb 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 081cbfa1ce 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 83999cb0a5 106: onsuccess: #1527: 2: Success after gcc: 2 commits new b0ff8073cd 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new 94722d3232 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 208bb7c4ba 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (e0a4d4aeb0) \ 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 1684 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 38140 -> 37660 bytes 05-build_abe-bootstrap/console.log.xz | Bin 270712 -> 270736 bytes 06-check_regression/console.log.xz | Bin 1800 -> 1928 bytes 07-update_baseline/console.log | 64 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++----- 13 files changed, 47 insertions(+), 47 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-norov-allmodconfig updated (36b95a02c8 -> 70f1ada254)

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-norov-allmodconfig in repository toolchain/ci/base-artifacts. from 36b95a02c8 9: onsuccess: #37: 33: Success after binutils/gcc: 143 commits new 70f1ada254 10: onsuccess: #38: 33: Success after binutils/gcc/qemu: 95 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 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30332 -> 29956 bytes 04-build_abe-stage1/console.log.xz | Bin 90332 -> 90928 bytes 05-build_abe-qemu/console.log.xz | Bin 31740 -> 31748 bytes 06-build_linux/console.log.xz | Bin 4920 -> 5012 bytes 08-check_regression/console.log.xz | Bin 2568 -> 2860 bytes 09-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +++++++++++++------------- 16 files changed, 20 insertions(+), 29 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allyesconfig updated (b783920379 -> 00c7198352)

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-allyesconfig in repository toolchain/ci/base-artifacts. from b783920379 13: onsuccess: #485: all: Success after binutils/llvm/linux: [...] new 00c7198352 14: onsuccess: #486: all: 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 1720 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30532 -> 30216 bytes 04-build_kernel_llvm/console.log.xz | Bin 64740 -> 65164 bytes 05-build_abe-qemu/console.log.xz | Bin 32164 -> 31584 bytes 06-build_linux/console.log.xz | Bin 3900 -> 3424 bytes 07-boot_linux/console.log.xz | Bin 576 -> 576 bytes 08-check_regression/console.log.xz | Bin 2984 -> 2952 bytes 08-check_regression/mail-body.txt | 4 +++- 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 | 6 ++++-- mail/mail-subject.txt | 2 +- manifest.sh | 26 +++++++++++++------------- 17 files changed, 26 insertions(+), 22 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto_lean updated (b4a97d2755 -> a4cb39b23b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto_lean in repository toolchain/ci/base-artifacts. from b4a97d2755 39: onsuccess: #414: 2: Success after binutils/gcc: 6 commits new a4cb39b23b 40: onsuccess: #415: 2: Success after binutils/gcc: 7 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 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 50304 -> 50364 bytes .../console.log.xz | Bin 941440 -> 941376 bytes 06-check_regression/console.log.xz | Bin 2032 -> 2104 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 ++++++++-------- 12 files changed, 14 insertions(+), 14 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (88883432ca -> 7188413ffe)

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 88883432ca 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards a6c9d0abdc 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 397265f8df 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards f58658e5db 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards e9a3b76ed7 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 4397cc878c 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 379ec0de0e 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 103a8a1c41 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards a06c5a2eba 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 6db799019e 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 99bed98f34 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 2d3ce6250e 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 5419b4f1ff 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards dba7a9c16e 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 587904de66 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards e26323dafe 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 46cd8c12e3 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 6317cb428c 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards e0e01b817f 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 6a18492c5a 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 8f4855f106 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 42073c882c 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 59d84f563c 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 184e03588f 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 0822b650a3 85: onsuccess: 7: Success after gcc: 9 commits discards e8d925d388 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 63302332cb 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 32e2112876 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards b62d7372e8 81: onsuccess: 7: Successful build after gcc: 2 commits discards a1f92afb08 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 497ec6233b 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 062c93c1dd 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ef92cee0e6 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 34e94d5fa8 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 23a2573271 75: onsuccess: 7: Successful build after linux: 44 commits discards 7aa96f6c43 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 2d00c0c4c0 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 858997e148 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards c71e6cad3b 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards bd70d72ecb 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 3c1db9c2f1 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 7328218313 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7a7c6290fc 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 1186dfba27 66: onsuccess: 7: Successful build after gcc: 3 commits discards b28286d61d 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3ff9cd38ae 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ca4aa96ea1 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards addf298b22 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards f97f478ae4 61: onsuccess: 4: Successful build after gcc: 15 commits discards b79ef45bc5 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards bc4b3449a0 59: force: 7: Successful build after gcc: 2 commits discards 1b013e8ebf 58: onsuccess: 7: Successful build after glibc: 2 commits discards c4aa7807d9 57: onsuccess: 7: Successful build after gcc: 7 commits discards 4f87930e8c 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0734d79611 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 2280cdeceb 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 23d49f0b84 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 97ecccb06f 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards ed8bebfbbb 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards e3171bb92d 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e6a8be2956 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 795fbc1045 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 42b3de2bde 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5e63cfe068 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 8e79113605 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards bd9f696a64 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards 83a5818750 43: onsuccess: 7: Successful build after gcc: 2 commits discards a40a66c2a8 42: onsuccess: 7: Successful build after baseline build: no [...] discards 2e64089527 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 57c8eb4259 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 338e03928e 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] discards c024811b6b 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards 2dd22db9be 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards ff0a489d1f 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 77b30d5f1c 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 7bc561f950 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards cbfedde467 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards acf8dfab9f 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 5fc0e14a0c 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards f60b8aae47 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 4856b2c483 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards a61b994cc7 28: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards cd45859779 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 607d25ecc0 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 4275bac40c 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards fdd91fb13f 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 732815c6a1 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 84fae595a6 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 041e202b25 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 022af02786 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 7ae8ec1ffb 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards a5446a30b4 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 8e1c71e06a 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 2a2abf74ec 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 99d7c834f4 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards fc14918575 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 45e0f5c252 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 3843c3b43d 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6479d85aa0 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d4ca95ed82 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards c3c64b226e 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2fd7203f28 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5174d44d25 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new f996a6f47e 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 939eed6e9d 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e7dab826e2 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 85d2a92b4a 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 991a729361 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 7ef6e6baa2 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 84ab4b046b 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 62ca1d3a0c 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 570a03155f 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 6c63635af5 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a02cc254a7 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 847ef84346 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 87d17978a0 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 0169b68e34 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new cd6fd675b2 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 8194144daf 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new bdd5604543 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new fca4a2f227 28: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5daa69de2a 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 993b60017b 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 9fe063e469 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 6d5a80fcac 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new c0a8642efe 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new bb37ef83f2 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new e6f05f43b6 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new ed5a06c12a 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 84e3cad055 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 3eab0f107d 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new 17af356876 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] new ea2631d7f1 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8a6e62a6b7 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5d0f06376c 42: onsuccess: 7: Successful build after baseline build: no [...] new 9fa0a3f523 43: onsuccess: 7: Successful build after gcc: 2 commits new acf93d6840 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new 85908e7902 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 22434522c8 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new c2d73951c2 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2a4a386cd4 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new cc332a705d 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new b39dd7a77f 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a4bd75a8e4 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 936e4316f5 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 271b9b2896 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 687cd2472f 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 24c4d21a1a 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 76a2285f5c 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 1c0e9be129 57: onsuccess: 7: Successful build after gcc: 7 commits new 3de990cd02 58: onsuccess: 7: Successful build after glibc: 2 commits new 36a8940d5e 59: force: 7: Successful build after gcc: 2 commits new b63d1a926f 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new dc890bbf5b 61: onsuccess: 4: Successful build after gcc: 15 commits new 5a454856ed 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new a6787642af 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new d9563e16b6 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7bf9466502 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4e43b6ce88 66: onsuccess: 7: Successful build after gcc: 3 commits new 7af80d88b8 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 28333c1a37 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 261865bb27 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new a68a512de2 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 5dd20c0eef 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 82cd4d6b8c 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 0236b1863d 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b99cb1212d 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new d0c1527752 75: onsuccess: 7: Successful build after linux: 44 commits new a7e3a6e084 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b5e99dfa8d 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 3717cc0f0d 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5a6fdb29f1 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 903f3cd15b 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 297e1cf04e 81: onsuccess: 7: Successful build after gcc: 2 commits new 7302bee703 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new f65dea1e5c 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new ca5d1f2d42 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 7db50040bc 85: onsuccess: 7: Success after gcc: 9 commits new f025ce448b 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new cda37812bd 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 7aa2a35cec 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 2b5d739fd6 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new c2fde2634b 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new fa93f73520 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new c75486ca22 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 8ce688d90d 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new 982b1150e6 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new f232efbca8 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new ac3c28b677 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 584db62d30 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new a9495eb7ee 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 93942c1bff 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new d25afb7056 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new 1b68590f63 101: onsuccess: #1609: 7: Success after binutils: 78 commits new d41d0125d8 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 821279c40d 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 2a6d182ed2 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new c4d4ec1ce2 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new cdfe277e65 106: onsuccess: #1617: 7: Success after gcc: 2 commits new fd42eac8ea 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 1c5c05d4da 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new 417500e155 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 7188413ffe 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/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 (88883432ca) \ 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 1676 -> 1628 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 29644 -> 29928 bytes 05-build_abe-stage1/console.log.xz | Bin 90536 -> 90788 bytes 07-build_abe-linux/console.log.xz | Bin 8304 -> 8296 bytes 08-build_abe-glibc/console.log.xz | Bin 233184 -> 232900 bytes 09-build_abe-stage2/console.log.xz | Bin 222884 -> 223152 bytes 10-build_abe-gdb/console.log.xz | Bin 37232 -> 37332 bytes 11-build_abe-qemu/console.log.xz | Bin 31572 -> 31632 bytes 12-check_regression/console.log.xz | Bin 2704 -> 2580 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/glibc_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, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (e5c4e1ae85 -> 41653a0903)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards e5c4e1ae85 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards ccdf5fc428 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards 23265f9dc8 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards bd2c1b0728 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards ac52a0007c 102: force: #1551: 1: Failure after gcc: 306 commits discards aa4d731645 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 317f229c5e 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards c07f2e50b3 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 7664c52652 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards e321bb81cb 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards c411855353 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards b4cf283eee 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2334f4674f 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 0472bd11e1 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards f3107ee463 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards a7f60a92d9 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 291862f1b3 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 66846a99e7 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards fe3c70dc5a 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards f856b77dcd 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards d81bba1fff 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 773b19b9cf 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards b4eecbace9 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards d66fc23a82 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 91a99a59f3 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 452ebdda98 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards aa37489d2b 80: onsuccess: 7: Successful build after linux: 44 commits discards fe09a2f494 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards dca52e9829 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards 81bf6f7d11 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 036040a813 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 636a351995 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 1a30858888 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 43a7a4a73c 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 54a2a148aa 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6a4b7d7b21 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 1c8059fcdb 70: onsuccess: 7: Successful build after gcc: 4 commits discards c846bc87e1 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 1b0c44e074 68: onsuccess: 7: Successful build after linux: 6 commits discards c0d1aa8aa5 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards 9b58551ee1 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards a1e04f42ec 65: onsuccess: 7: Successful build after binutils: 3 commits discards e72b97df12 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 1a55568040 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 449a972e7c 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 9df252cf27 61: onsuccess: 4: Successful build after gcc: 5 commits discards 880c9bb4c5 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards af5313569e 59: force: 7: Successful build after gcc: 3 commits discards d09b7911c5 58: onsuccess: 7: Successful build after glibc: 2 commits discards 3e799ddf1e 57: onsuccess: 7: Successful build after gcc: 7 commits discards 29136c26b8 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b661023e0e 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 624defd97a 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards 34af3c700c 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 90b4f560ab 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] discards d177348eca 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 2e4f76ede9 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f133f46a57 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards fcee221dcd 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards b199863f50 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards cdaf8b8d72 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards ec45a9207b 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e855ed53c0 44: onsuccess: 7: Successful build after linux: 34 commits discards f727e48e8a 43: onsuccess: 7: Successful build after gcc: 2 commits discards a86b62fb19 42: onsuccess: 7: Successful build after baseline build: no [...] discards e3045c6b42 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards dcec0d60a6 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards db64e2c23d 39: onsuccess: 7: Successful build after gcc: 2 commits discards 86d3536243 38: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards eb5404794a 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 2460a59251 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards df0cc3788e 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 2da9ba46b8 34: onsuccess: 7: Successful build after gcc: 3 commits discards bd1a5acb31 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9462a4c795 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 31aedec35b 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards ca940b10d5 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits discards dffe74a60f 29: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 77f6f55045 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 4f93bdd743 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 7eefa17a9b 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards ffeba14ae3 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 391053473f 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 9d19045461 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 435f2f28cd 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 778d691a8a 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards dc54371ad3 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 78c09da59b 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 10a77fa9cc 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 667e0a50d7 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b29a5c62a8 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 194f45d10a 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards a47f3b2570 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b2e2ce9d20 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 03844ac5d6 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 4416c3e124 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1d401cdce5 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1fad067f56 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 16fac0bf5a 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1d8af85f48 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 200e014194 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 13ae22c48f 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e6a076803e 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 4f5e7ca041 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 6de1303940 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 61b4856036 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 34063d0270 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new acbc32c975 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 0a2931b5d7 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 49936d6317 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 320c51b596 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 811eb78557 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e6a1a28d07 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 596168d866 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 606a21d39e 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new f8641aae7b 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c81bd7a368 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3243ee46cb 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d1c4834415 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 4a77ea7f50 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 85fc29c33f 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5f6b789094 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d97ccd11ab 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new f65b1f85d1 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new a314249612 29: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2f20232e90 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits new 7d246b189f 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new dcc490af8f 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 67cde4e67e 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 459226a28e 34: onsuccess: 7: Successful build after gcc: 3 commits new 84ff586b82 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new c1468d4e5a 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7f3769e82c 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 1a7c1e2b8e 38: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e6012edf32 39: onsuccess: 7: Successful build after gcc: 2 commits new 763935deed 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 33dc958a61 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new dd6eeace57 42: onsuccess: 7: Successful build after baseline build: no [...] new 6bd285bba4 43: onsuccess: 7: Successful build after gcc: 2 commits new 9745ea63b7 44: onsuccess: 7: Successful build after linux: 34 commits new a921343b7a 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 082e4a1c94 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new ac1acb34f5 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 3d3e7cd493 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new b0a7e65b8c 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 84c7888831 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 24fba1894c 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 68352136c0 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new 1f464f8808 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new b630ddbba9 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new fbca687aa1 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 824f7fc881 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 58db60996f 57: onsuccess: 7: Successful build after gcc: 7 commits new 538bb9fa57 58: onsuccess: 7: Successful build after glibc: 2 commits new 8b8ab1f1d7 59: force: 7: Successful build after gcc: 3 commits new b6b537a750 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 9928c7c69b 61: onsuccess: 4: Successful build after gcc: 5 commits new 8f04ab40a7 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new e6a502b858 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new dea75590c3 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new b8eb6d94f5 65: onsuccess: 7: Successful build after binutils: 3 commits new 65a49219f9 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 8bc670579f 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new f27abb88cd 68: onsuccess: 7: Successful build after linux: 6 commits new 5b8f3280a0 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b8b8783001 70: onsuccess: 7: Successful build after gcc: 4 commits new afee202041 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 7df4d10fb8 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 975f38246b 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new af3afb5fbc 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 3f0722d830 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 0b50d2a968 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new e9b0a9d749 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5bdf306d4f 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new ec6e930333 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new e13e8db2bb 80: onsuccess: 7: Successful build after linux: 44 commits new d8b9ba1f56 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d5e21aa546 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 285d8a49c9 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 89b682a858 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 54be0a69d0 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 968a0c1c1e 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 01f86985da 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 56bab9677d 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new a03d9c9d1e 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 0020747600 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 27b29ad0f0 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 35ccecf9fe 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new b2fcc6f892 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 649b480ac3 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 4987e49bb3 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 999adcea7d 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new d0e02947c6 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 639772bf17 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 18fdf10cc7 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new d853e4600d 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 1f6550e3fa 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 020ea2b333 102: force: #1551: 1: Failure after gcc: 306 commits new a93abbe48a 103: onsuccess: #1552: 1: Success after gcc: 5 commits new ecdc22230f 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new a2cceafcf6 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new b03f2de2fc 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 41653a0903 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/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 (e5c4e1ae85) \ 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 1736 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30028 -> 30348 bytes 05-build_abe-stage1/console.log.xz | Bin 71812 -> 72700 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 8300 -> 8296 bytes 08-build_abe-glibc/console.log.xz | Bin 240240 -> 239488 bytes 09-build_abe-stage2/console.log.xz | Bin 203304 -> 203332 bytes 10-build_abe-gdb/console.log.xz | Bin 37436 -> 37592 bytes 11-build_abe-qemu/console.log.xz | Bin 31804 -> 31640 bytes 12-check_regression/console.log.xz | Bin 2768 -> 2580 bytes 13-update_baseline/console.log | 40 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++++++++++++++++----------------- 21 files changed, 47 insertions(+), 47 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022