Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[gcc] branch master updated (de613c6295e -> bfad7069b74)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from de613c6295e Daily bump. new 3db8e9c2422 Support 2-instruction vector shuffle for V4SI/V4SF in ix86_ [...] new bfad7069b74 rs6000: Fix condition of define_expand vec_shr_<mode> [PR100645] The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/config/i386/i386-expand.cc | 116 ++++++++++++++++++++++++++++ gcc/config/rs6000/vector.md | 2 +- gcc/testsuite/gcc.target/i386/pr53346-1.c | 70 +++++++++++++++++ gcc/testsuite/gcc.target/i386/pr53346-2.c | 59 ++++++++++++++ gcc/testsuite/gcc.target/i386/pr53346-3.c | 69 +++++++++++++++++ gcc/testsuite/gcc.target/i386/pr53346-4.c | 59 ++++++++++++++ gcc/testsuite/gcc.target/powerpc/pr100645.c | 13 ++++ 7 files changed, 387 insertions(+), 1 deletion(-) create mode 100644 gcc/testsuite/gcc.target/i386/pr53346-1.c create mode 100644 gcc/testsuite/gcc.target/i386/pr53346-2.c create mode 100644 gcc/testsuite/gcc.target/i386/pr53346-3.c create mode 100644 gcc/testsuite/gcc.target/i386/pr53346-4.c create mode 100644 gcc/testsuite/gcc.target/powerpc/pr100645.c -- 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-arm-mainline-allyesconfig updated (e5fbba52ec -> 2b49c6b06c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from e5fbba52ec 16: onsuccess: #485: 20867: Success after binutils: 61 commits new 2b49c6b06c 17: onsuccess: #487: 20867: Success after qemu: 98 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 1644 -> 1824 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 29764 -> 30020 bytes 04-build_kernel_llvm/console.log.xz | Bin 62816 -> 62328 bytes 05-build_abe-qemu/console.log.xz | Bin 30908 -> 30556 bytes 06-build_linux/console.log.xz | Bin 4664 -> 4576 bytes 08-check_regression/console.log.xz | Bin 2940 -> 2960 bytes dashboard/dashboard-generate.sh | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 13 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_gcc_bootstrap/master-aarch64-bootstrap updated (38d436c58e -> 27e11a3518)

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 38d436c58e 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards e9013dc6ca 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards 98766bb3bf 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards 0f7ab13959 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards 35d0158942 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards 1f0ffb622f 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards 5c8b362a8e 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards d09294dea1 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards 62279aa9ea 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 112567d1ed 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards 4e5eaba729 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards 58fe5df83c 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards f0a73ca4be 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards ed9de38f17 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 21d5b5bff8 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards ba649c2ed0 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards 4b032b4264 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 1f7107c5ed 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards 6bbbf0e3e6 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards 4faa51dd38 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 5f07e7e53d 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 7b345b8bca 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 42ca8858aa 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards 57daae923c 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 69acec3b3a 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 4b89932f99 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards 6097baf243 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards 60e317c33a 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 1a7056d6a8 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards 27401e0b22 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards fef9c66a8c 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 689e01f8d3 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards c5a30e5165 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 45d029a8a0 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 986d2f10fd 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards a1d5a7b0d8 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 23d965b120 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 9df746e28e 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 070c49eee1 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 70325ee7ec 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards ab8631dbec 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 758defe244 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 28473a9e1d 88: onsuccess: 1: Success after gcc: 20 commits discards 6a7a9ece7b 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards 8cc79ed589 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards ba17908229 85: onsuccess: 2: Success after binutils: 4 commits discards e0a0bf5ab0 84: onsuccess: 2: Success after gcc: 9 commits discards a3f38e23c4 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 65af30eaf0 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards c56192c0e8 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 118a251837 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 382f4385b5 79: onsuccess: 1: Successful build after gcc: 3 commits discards 390b05b763 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards edf9a5d3e8 77: force: 2: Successful build after gcc: 32 commits discards 473f39f96f 76: onsuccess: 2: Successful build after binutils: 10 commits discards c304604157 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 6759deea25 74: onsuccess: 2: Successful build after gcc: 13 commits discards c0d812344d 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 4ab963fc8f 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 059ce9ed9b 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards b33c8c1179 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 996bb27a4d 69: onsuccess: 2: Successful build after baseline build: no [...] discards 08039a1d95 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 72b8c6ba0b 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards c2c62e42d3 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards ce2f15b886 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 96dfbb09b2 64: onsuccess: 2: Successful build after gcc: 7 commits discards fd380a846d 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 568124093a 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 2acb023cd7 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 45c0982a55 60: onsuccess: 1: Successful build after gcc: 15 commits discards 7c9f5431b8 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 642e925d0b 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards 0287519306 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 9fb14eb516 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 7ea9f74759 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards cbb10b069d 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards d7fb3b1bae 53: onsuccess: 2: Successful build after gcc: 5 commits discards e395d01525 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards e0e6b93d1e 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 7b1eabe879 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 23c0093c7f 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 783c0a95c6 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 9aaae91f17 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 99414ffb58 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 7dc8d3ad0c 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards 9079eb6153 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 7265243ca3 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards d57f9fbf34 42: onsuccess: 2: Successful build after gcc: 2 commits discards ab5dbacf7a 41: onsuccess: 2: Successful build after baseline build: no [...] discards cb08266bd8 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 9dfea5890b 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards e6a49c3c0d 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards cde3af7e76 37: onsuccess: 2: Successful build after gcc: 2 commits discards afc452c3c6 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 86e5773715 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards b2c1835a5b 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 32e24b3040 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 571e23bb7d 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards c247ad79d0 31: onsuccess: 2: Successful build after gcc: 8 commits discards 9a26ec367b 30: onsuccess: 2: Successful build after gcc: 7 commits new 2ca859f2c0 30: onsuccess: 2: Successful build after gcc: 7 commits new f4da8dec33 31: onsuccess: 2: Successful build after gcc: 8 commits new 20b662bc94 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 9e9d3decc9 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 17e876bdfc 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits new e016108497 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 24bfe1fd30 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 10e9920efa 37: onsuccess: 2: Successful build after gcc: 2 commits new 9263c6b73f 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 08196d0261 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 579f99e901 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 522b48bfb5 41: onsuccess: 2: Successful build after baseline build: no [...] new 80b33a2e74 42: onsuccess: 2: Successful build after gcc: 2 commits new 515b172619 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new 3ed8a885cb 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 76d5f0fb0e 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 381ad556d2 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 12b4584fc8 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 0e78864bcd 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 7679927f40 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new cf8317b2fc 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 8e0f5db71b 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 2cf53ca9d3 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 476b092de7 53: onsuccess: 2: Successful build after gcc: 5 commits new df605f215b 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 7e6ada6c53 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 6c078821a3 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 03171dacc2 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 479384c360 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new 8740a99787 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 9d555c523f 60: onsuccess: 1: Successful build after gcc: 15 commits new e52605b9b6 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 8f29e15f18 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new c69321a0e5 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 7396db1101 64: onsuccess: 2: Successful build after gcc: 7 commits new 67455ede64 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 04cc069491 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 6672c69ba7 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 6756e51d81 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 2d0647fe99 69: onsuccess: 2: Successful build after baseline build: no [...] new 7a9524a8d4 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 83f347bd0f 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 252c7ddf14 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 00012aac26 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 20fd93c8b6 74: onsuccess: 2: Successful build after gcc: 13 commits new 17bdc84600 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 0863a7c989 76: onsuccess: 2: Successful build after binutils: 10 commits new 0fdf6b2366 77: force: 2: Successful build after gcc: 32 commits new 6f5aa82ad4 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new bfa201636e 79: onsuccess: 1: Successful build after gcc: 3 commits new 50dc54d7d1 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 37658304e2 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 2629186c9c 82: onsuccess: 2: Success after binutils/gcc: 26 commits new a9850c2a69 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 62c5f66e2f 84: onsuccess: 2: Success after gcc: 9 commits new 4f3a41fe0a 85: onsuccess: 2: Success after binutils: 4 commits new ae71eb3aa5 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new 59b8f67694 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new db6edca8f7 88: onsuccess: 1: Success after gcc: 20 commits new 965c1788ba 89: onsuccess: 2: Success after binutils/gcc: 39 commits new b4211312d0 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 6328799987 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 111dbc0000 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new de35d6d354 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new d346ef0b18 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new fddbb33601 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 6c20801748 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 6cb1d847e0 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 64f5a9ec4e 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 5c2ad93571 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 7f0fe9b8e2 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new e224c74c9d 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new 70f3a628f8 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 68bae4f3df 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 152e60c5b6 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 9d806d0574 105: onsuccess: #1526: 2: Success after gcc: 2 commits new ea230c425c 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 0e2c5954e5 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new 9dee013cc3 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 1bcec6839c 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 320d43bd50 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 66f2fffd72 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 6190b8effc 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 8a7cccbfaa 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new 5f85ed14c2 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new c041bd73de 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 547c61aede 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new aaf8be1074 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new db1809619b 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 1449171043 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new 1418d1173b 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 6314067f0f 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new 56c5450de6 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 3278bdbfca 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 76d36e33e5 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new b94a94ed9d 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new 753168cef2 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new 415300fd03 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new bf6fb62995 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new d14143e459 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new d8b9a617dc 130: onsuccess: #1554: 2: Success after gcc: 9 commits new 27e11a3518 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 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 (38d436c58e) \ 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 1732 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2704 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 37872 -> 38008 bytes 05-build_abe-bootstrap/console.log.xz | Bin 270644 -> 272024 bytes 06-check_regression/console.log.xz | Bin 2652 -> 2564 bytes 07-update_baseline/console.log | 62 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++----- 13 files changed, 46 insertions(+), 46 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-release-arm-lts-allyesconfig updated (1b81398f0d -> 91a150d6d8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-lts-allyesconfig in repository toolchain/ci/base-artifacts. from 1b81398f0d 15: onsuccess: #248: 19905: Success after binutils/llvm/linu [...] new 91a150d6d8 16: onsuccess: #249: 19905: Success after binutils/llvm/linu [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1696 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 30172 -> 29976 bytes 04-build_kernel_llvm/console.log.xz | Bin 64672 -> 62904 bytes 05-build_abe-qemu/console.log.xz | Bin 31476 -> 31168 bytes 06-build_linux/console.log.xz | Bin 4616 -> 4612 bytes 08-check_regression/console.log.xz | Bin 3344 -> 4076 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 31 ++++++++++++++++--------------- 17 files changed, 28 insertions(+), 27 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (ecafc414dd -> e6d3640795)

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 ecafc414dd 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 1df35921e5 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 6697c9623a 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 4b4c9b7ce8 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 2da93c514b 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 074ae5a59d 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 6d0dc37751 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards ad7047889d 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards ff50a187d3 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 72cca13661 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 1044c1a0e5 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 8aa951a37e 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards a83ddbae52 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 1e656048fc 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards b849b2f44e 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 21c52ad36c 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards d65c66311a 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 23e85aff34 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 7e3adfbcb9 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards e7b7493690 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 84bf42db5e 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards fb83898960 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 0d5045e104 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards dec8e033e1 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 8a6b446bf7 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 1ec1f55daa 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 0e154df4f1 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 4b2cb79166 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards ae231a65f3 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards cffbadc61a 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 4811a72de1 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards c6c0e8cd5c 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards db7c516e4a 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 2cc69b080e 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards df28a73a4e 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards ec98b8653a 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 557a183705 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 4d3fe9fe4b 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 7b4dfaf1f8 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 9a3b5430cd 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 273cdf6382 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 35af870548 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards f0078f3026 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 0c55d6f243 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 8c09d960fa 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 0e5fd0c817 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards e508c0d157 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 2677feccab 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 2daae6b96d 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 6f664ea9f6 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 5d2d8edb39 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards fdb33a2186 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 4f0bf57047 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards fb1a281379 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 60a0431366 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 03c1389e21 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0905b09dd1 74: onsuccess: 1: Successful build after linux: 44 commits discards 50fc9d3711 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 07a7ba7a56 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b2910842b1 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards e394e875b6 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 2fcb355a8e 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards ae56273fe4 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 53b4629172 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6cb0a62fd4 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c6e937f529 65: onsuccess: 1: Successful build after gcc: 4 commits discards f7a6dc9008 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1c9631906c 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c229702f1b 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards b8a7a25760 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards aacc4e5ae6 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 083fcb7623 59: onsuccess: 1: Successful build after glibc: 2 commits discards f7b3f02bf7 58: onsuccess: 1: Successful build after binutils: 2 commits discards ebcef19bfc 57: onsuccess: 1: Successful build after gcc: 7 commits discards 024417f60e 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 79a1ebd7f3 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5c85427cac 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 789e1d5906 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards d42c7e5879 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards dc08955d4b 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 05b547f523 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b41786864f 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f7da76ac15 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 818ef28b34 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e07301b0c7 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 3eb48879c6 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 193c50b5ab 44: onsuccess: 1: Successful build after linux: 34 commits discards 2b05f0c2a5 43: onsuccess: 1: Successful build after gcc: 2 commits discards 32ddef2b62 42: onsuccess: 1: Successful build after baseline build: no [...] discards 0fd014a920 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3588de45bc 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f9bf61470f 39: onsuccess: 1: Successful build after gcc: 2 commits discards 092a8d59f9 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d2749e0e0a 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0eacda666f 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d30516ef0c 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e2be69d981 34: onsuccess: 1: Successful build after gcc: 3 commits discards 0ee43e11bb 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7a863b7269 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 394268c90b 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 410b227e87 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new dc9c71c00f 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 07996cf9d3 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0727adf3cc 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new b4404b15bd 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e232137c1e 34: onsuccess: 1: Successful build after gcc: 3 commits new 48ac4c6980 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 03811c5634 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b4a40cbf0a 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d457a7aa23 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6864e6f436 39: onsuccess: 1: Successful build after gcc: 2 commits new a608605ab6 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 909ff62bba 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ab692564ed 42: onsuccess: 1: Successful build after baseline build: no [...] new eb6b17a89a 43: onsuccess: 1: Successful build after gcc: 2 commits new ed5d51cdaf 44: onsuccess: 1: Successful build after linux: 34 commits new 651c11857e 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 93361ddc1f 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 706ee75753 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 799671cf6a 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 69cb5a8a30 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c110fa40ab 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 50aa5b1746 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new da8a525772 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new a0d5057754 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new eeac610967 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 05f320dfe7 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b54afb5f9b 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7824adbcdd 57: onsuccess: 1: Successful build after gcc: 7 commits new 3ca387a528 58: onsuccess: 1: Successful build after binutils: 2 commits new 6e35ac5c8f 59: onsuccess: 1: Successful build after glibc: 2 commits new f94a6fc299 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 3a51591400 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new d541c6af21 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 75db1be36e 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6dd04b81d7 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 982074f803 65: onsuccess: 1: Successful build after gcc: 4 commits new b8ed6c4ef2 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 8d4e989dba 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2056e97bcb 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 97d4af1919 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 87dfec1baa 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 87f3729cd0 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 13314d2091 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0ef3024c2c 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 08405f57e6 74: onsuccess: 1: Successful build after linux: 44 commits new 57ef8a38a6 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 69109d7030 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 1108230c82 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 30ff581014 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c04aa6dbfc 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new baa6f69a7b 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new b96c1f8c90 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 73ec75fb88 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 8f82d97a2c 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new c9c950bd47 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 61368d3e0c 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new cdab33c5db 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 4b73727b8b 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 3d1d629559 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 1e2812df5f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new c733a579a1 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 2060606aa2 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new f4cde1b291 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 082d4b49b3 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 73d8d46d15 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new a84c53ed42 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new d37039416c 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 095278b8f4 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 120c0ebd1a 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 914decab46 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 551c7be5b9 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new a8e8ccf591 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 7c08dfe9d7 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 9c81e0e52b 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new a8160844ae 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 5c7496fb4d 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new e4168c6c21 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new b1cbe0fc5c 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new a1de7ff7ee 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 084da64930 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 8207c1bc71 110: onsuccess: #1703: 1: Success after gcc: 6 commits new c46f23b881 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 3093f364d7 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new e71943e0e7 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 786645428b 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 88f5238127 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new a2fdd841a8 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 5824033dfb 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new e0c5e59d6f 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 8ee473f5c7 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 19cd4de165 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new a2831576b7 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 9251a2792c 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new fe3ad7e747 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 14039e2a11 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new a9147d9e7b 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new ed5012b5b9 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 709a0f26bd 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new fdbb2dff2f 128: onsuccess: #1723: 1: Success after linux: 12 commits new 5485f06e00 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new e15d57c6a5 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new e6d3640795 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (ecafc414dd) \ 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 1772 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 29904 -> 29992 bytes 04-build_abe-stage1/console.log.xz | Bin 91260 -> 90388 bytes 06-build_abe-linux/console.log.xz | Bin 8956 -> 8312 bytes 07-build_abe-glibc/console.log.xz | Bin 234196 -> 233636 bytes 08-build_abe-stage2/console.log.xz | Bin 224268 -> 222660 bytes 09-build_abe-gdb/console.log.xz | Bin 37136 -> 37224 bytes 10-build_abe-qemu/console.log.xz | Bin 31040 -> 30944 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3848 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2888 -> 2424 bytes 13-check_regression/console.log.xz | Bin 6924 -> 5336 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 261 +--- 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.xz | Bin 2659916 -> 2659608 bytes sumfiles/g++.sum | 38 +- sumfiles/gcc.log.xz | Bin 2213044 -> 2197864 bytes sumfiles/gcc.sum | 2092 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 882136 -> 881268 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201260 -> 201268 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 426372 -> 426076 bytes sumfiles/libstdc++.sum | 2 +- 39 files changed, 1141 insertions(+), 1456 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_O1 updated (01a46778d1 -> 30b4ae6032)

by git＠git.linaro.org

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (ddd0c74138 -> d28144fc6f)

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 ddd0c74138 132: onsuccess: #1645: 7: Success after linux: 23 commits discards a4936447d3 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards c2ca83f703 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards e9b9fb29d9 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 4b7057699b 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards 4cf0ee6e18 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 9dadb4fc9e 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 7e632c65d2 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards dde697a2e6 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 111ae698d8 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards 936e20ac50 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 078dc744d1 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 738ad575cd 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 4003c25cd2 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards a18b179ace 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards b069915ed2 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 2a5c244b8f 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 33ccc14cc6 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 0ecfaf5eaa 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards f5bba27483 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 14aec26531 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 03850a5c1b 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 12f7358003 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards f92da29409 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards eef79c87d6 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 4f1c2dab26 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 4d0f3b6a86 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 2dba0a3822 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 88d2312559 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 490d2b1d0c 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 940fe2538e 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards f3e336ab11 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 5978c5890f 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 9ed09782e2 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards a833e6161e 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 769bd8257a 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards aadf30f7ab 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 9ab6a08a19 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards 6d4881eb26 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards c89a73d5d8 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards c420d6992b 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards ce421b9133 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards a2c8d000b9 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards ec0745e7b1 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 9208adc4ca 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 0334121631 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards af084dbeeb 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 2c0d7a1948 85: onsuccess: 7: Success after gcc: 9 commits discards d86b97dc9e 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 6b10208729 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards c8db720098 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 1facdb4d51 81: onsuccess: 7: Successful build after gcc: 2 commits discards 1f8fab3f9a 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards bf7687858f 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards c16d33be49 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 547e859590 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 3d92f186b9 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c0908260b4 75: onsuccess: 7: Successful build after linux: 44 commits discards 30a05b224a 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 4de412238e 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7c067038f6 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards ad77716a52 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 653fe7b7c8 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards e5f22dfb95 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 9e7634d129 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f2d8ab3ab2 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 34618e25e7 66: onsuccess: 7: Successful build after gcc: 3 commits discards 093806ef42 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 57b97b5ae4 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e4c27cdad0 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards af79c434a9 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards a707fc3802 61: onsuccess: 4: Successful build after gcc: 15 commits discards ffb7e8f75e 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards b34ab59d3f 59: force: 7: Successful build after gcc: 2 commits discards ceefb9a1ce 58: onsuccess: 7: Successful build after glibc: 2 commits discards f516126792 57: onsuccess: 7: Successful build after gcc: 7 commits discards 8591b8c931 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f5096e32dd 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ec17e73dc4 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 725576d6a1 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 9f1120f37c 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards abf9d89550 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 586a772d1f 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3565c0b346 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 1fad5add8c 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 5a5f963fa4 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards dd144527b4 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 096cb3f63f 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 05a1e1b8a2 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards e20c429777 43: onsuccess: 7: Successful build after gcc: 2 commits discards 8295a10709 42: onsuccess: 7: Successful build after baseline build: no [...] discards 32041ebfa6 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9f0455b084 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 4e6f813e70 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] discards 56ddc11bc7 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards 13d22ab1f8 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 4cd1a7c1d8 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 20b35b06a4 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 06067e6c6e 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 6555a9bd9e 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3f77f7fec6 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new a911a269c6 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 421d9991d7 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 285a4bb580 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 1b93fa8168 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new bc8179d0a4 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 33df65c22f 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new da26cec68b 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new c39f9b5350 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] new c9c8ce1fe3 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ed4548e62b 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 75be3d6f60 42: onsuccess: 7: Successful build after baseline build: no [...] new 5c34ab2b1c 43: onsuccess: 7: Successful build after gcc: 2 commits new 66f089319b 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new 10fed41588 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8c1b923b6c 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new f891fb79b4 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new dd56ff551c 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 74512398ba 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 1106f4bfcd 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2512d19885 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 9965c1666b 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 079d691dff 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 5f48053aaa 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new e78fe2ce34 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4a6819d6ff 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8c0e9f17da 57: onsuccess: 7: Successful build after gcc: 7 commits new d0267aa5cc 58: onsuccess: 7: Successful build after glibc: 2 commits new ed55ea9c29 59: force: 7: Successful build after gcc: 2 commits new 0743c44b51 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new de8c8ffa28 61: onsuccess: 4: Successful build after gcc: 15 commits new 67de57f4d7 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 91db018aed 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 288f2950b0 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8b83d76790 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a180c843c8 66: onsuccess: 7: Successful build after gcc: 3 commits new 4f3d0b9430 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 73b2350ed5 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 9539b42246 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 721d34ab85 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 76cba366d5 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 05d7edbb42 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 6ce713aac4 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8abb12021b 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new bc76e525d5 75: onsuccess: 7: Successful build after linux: 44 commits new 5eadbf2a09 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 69b51f53e9 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 5e12ff57b8 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7f2878f941 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 34b628b126 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new ccc93b7988 81: onsuccess: 7: Successful build after gcc: 2 commits new 568f587979 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 44130400c9 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new d7cea8b4f6 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new ea76ec0347 85: onsuccess: 7: Success after gcc: 9 commits new bbe1e157ac 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 790e0add82 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new a0daaf58e2 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 111c93d0dd 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new d89d7a5803 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new fed976755e 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 57bffadff4 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new d2c32198e8 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new a36f21f4a6 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new e770bc446c 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new dbaf7e15d6 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 67c8a81d8c 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new ce726ceae8 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 0a320c8e44 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new d5023e1238 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new bf50645c25 101: onsuccess: #1609: 7: Success after binutils: 78 commits new f96d2cb594 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 63f8c76bc9 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 020c811c85 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 88edffa48d 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new c5a1cba6cc 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 844e3324d5 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 5ceec3465a 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new 9a4d6695ff 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new f8e64f5dc0 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new 36bb5ffb2e 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 6963f29f93 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new ea52dde190 113: onsuccess: #1624: 7: Success after gcc: 6 commits new c26fb855c2 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 04a138f552 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new e8f8009d28 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 2994ab257e 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 1da0c4eaf8 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new fc0ee0a43b 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 4d929c058e 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 068ea6984c 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new f5378de37b 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new c952803dc2 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new c3af1b06c0 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 83e822bd61 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new 4289e0e832 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new 07583a60f9 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 75dd8dd561 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 3d386fd030 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new f1c9962735 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new bfbeea3234 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 99a9b3c828 132: onsuccess: #1645: 7: Success after linux: 23 commits new d28144fc6f 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (ddd0c74138) \ 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 1704 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 29944 -> 29896 bytes 05-build_abe-stage1/console.log.xz | Bin 91220 -> 90172 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8816 -> 8320 bytes 08-build_abe-glibc/console.log.xz | Bin 234688 -> 233740 bytes 09-build_abe-stage2/console.log.xz | Bin 226212 -> 223128 bytes 10-build_abe-gdb/console.log.xz | Bin 37804 -> 37212 bytes 11-build_abe-qemu/console.log.xz | Bin 31460 -> 31056 bytes 12-check_regression/console.log.xz | Bin 3540 -> 3520 bytes 13-update_baseline/console.log | 68 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++--------- 21 files changed, 59 insertions(+), 59 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-release-aarch64-mainline-allmodconfig updated (4bc4192f03 -> ab9280e509)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-mainline-allmodconfig in repository toolchain/ci/base-artifacts. from 4bc4192f03 14: onsuccess: #426: boot: Success after binutils/llvm/qemu: [...] new ab9280e509 15: onsuccess: #427: boot: Success after linux: 299 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 1708 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30180 -> 30260 bytes 04-build_kernel_llvm/console.log.xz | Bin 65540 -> 63924 bytes 05-build_abe-qemu/console.log.xz | Bin 31232 -> 31688 bytes 06-build_linux/console.log.xz | Bin 3188 -> 3016 bytes 07-boot_linux/console.log.xz | Bin 504 -> 508 bytes 08-check_regression/console.log.xz | Bin 3564 -> 2960 bytes dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 ++++++++---------- 14 files changed, 13 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_kernel/llvm-release-aarch64-mainline-defconfig updated (393876a4ae -> 51bc1e4aac)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-mainline-defconfig in repository toolchain/ci/base-artifacts. from 393876a4ae 10: onsuccess: #426: boot: Success after binutils/llvm/linux [...] new 51bc1e4aac 11: onsuccess: #427: boot: Success after binutils/llvm/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1716 -> 1916 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30200 -> 30748 bytes 04-build_kernel_llvm/console.log.xz | Bin 65204 -> 63604 bytes 05-build_abe-qemu/console.log.xz | Bin 31988 -> 31080 bytes 06-build_linux/console.log.xz | Bin 3120 -> 3056 bytes 07-boot_linux/console.log.xz | Bin 6236 -> 6312 bytes 08-check_regression/console.log.xz | Bin 3308 -> 4060 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 31 ++++++++++++++++--------------- 17 files changed, 24 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (857cdd208a -> 36f31ae190)

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 857cdd208a 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards cd5fed0637 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards d63a3b50f7 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 29f41efa2a 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 5ba72962b9 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 31db7ca2fe 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards c5ae83d640 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 4f8c255834 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards 781b7d197a 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 0d46b74766 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards 125178780b 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards db8ddfa811 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 6fc9e87118 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards c8b01efa81 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards c8318bd008 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 46ca78c2e9 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards a08fe22473 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards fa8c008922 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards cc799d1c3a 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards 250f14899e 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards aa3e218778 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards f94ffce4d6 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 0c2c81f544 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 9fbe66a422 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 88a30bdefd 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards d5803889fc 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards 29ef32fecd 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards 4960bb3bc1 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards ed83624174 102: force: #1551: 1: Failure after gcc: 306 commits discards d3e213c994 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 671d36e7f0 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 6def1f71dd 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards e6911cb7b5 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 85f4b47fd4 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 89ef73f798 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 65ec4c566d 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards fa1538b874 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 3de121297d 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards c307ed6d08 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 98712480f8 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards bf9c0cacff 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 9fab3c6747 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 1e6b394797 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 987f6ce0c0 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards b67749b9b0 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 854e221222 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 3e6cce3099 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 6d110c8a9f 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 4c990a60e8 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 4a0094d373 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b42dc08444 80: onsuccess: 7: Successful build after linux: 44 commits discards 02111f883a 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 85ea17dba6 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards 25c2b83f7f 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards cb08578540 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 0c8cdb3d50 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 2545074499 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 1b77ff46aa 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9473c60bb6 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c590052a8b 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards b913a3e2f1 70: onsuccess: 7: Successful build after gcc: 4 commits discards 6d712ada49 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f2c91d4230 68: onsuccess: 7: Successful build after linux: 6 commits discards 3411a1c4c6 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards 1805b18e79 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards 17d17039fb 65: onsuccess: 7: Successful build after binutils: 3 commits discards bb4df4385d 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 4c59c66a7b 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 8c77e2985a 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards a82603bc4d 61: onsuccess: 4: Successful build after gcc: 5 commits discards 8700832d5b 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 44dbf17f74 59: force: 7: Successful build after gcc: 3 commits discards c622b5f2c1 58: onsuccess: 7: Successful build after glibc: 2 commits discards a897b3d318 57: onsuccess: 7: Successful build after gcc: 7 commits discards cf2bc61480 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 49bd89f9b4 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a0027cc44a 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards 9a7f47e160 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards f11df70466 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] discards eef88938e6 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 5ceb69d2f2 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 052fb52a11 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards b38761ac17 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards b8910d04d0 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e0d4098ab7 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards f80eaff64b 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ccfba84fa3 44: onsuccess: 7: Successful build after linux: 34 commits discards 7a538e7268 43: onsuccess: 7: Successful build after gcc: 2 commits discards 01ee99f481 42: onsuccess: 7: Successful build after baseline build: no [...] discards 88d5bd0a38 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 239a80569a 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 29f9d0e0e9 39: onsuccess: 7: Successful build after gcc: 2 commits discards 072e6356a1 38: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 57c10df082 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 9d6937aa73 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ce2909c9f6 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 85b1fe4fb6 34: onsuccess: 7: Successful build after gcc: 3 commits discards bea8d7f9d2 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a435a9195f 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 6c891cca30 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 855cf90138 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits new 0cb2474cda 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits new c2fb8f2692 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 6bc3c496eb 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new d8c35c21bf 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7a58c5fb93 34: onsuccess: 7: Successful build after gcc: 3 commits new e0bf1aa8d3 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 920485dbe2 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ac0ae70ccb 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new d645642e24 38: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 351ab087a6 39: onsuccess: 7: Successful build after gcc: 2 commits new f571233679 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 768f3da56e 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c6c41eeef0 42: onsuccess: 7: Successful build after baseline build: no [...] new bdbf4d5170 43: onsuccess: 7: Successful build after gcc: 2 commits new 33343c643b 44: onsuccess: 7: Successful build after linux: 34 commits new e80224ea19 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2abf764158 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new bc71bf8e2a 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 15efb3bdd7 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 361925779b 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 2010f5e559 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 247250eb19 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new e34eb95f38 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new fdcee94fca 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 9f31bc4678 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 6e067c8bec 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 728772701c 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new cf1bd8cd02 57: onsuccess: 7: Successful build after gcc: 7 commits new 6dcf769e84 58: onsuccess: 7: Successful build after glibc: 2 commits new 0de61721a5 59: force: 7: Successful build after gcc: 3 commits new 17f1e4e7f1 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 6ed2616f5c 61: onsuccess: 4: Successful build after gcc: 5 commits new 937b3345c2 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 723bca7eea 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 8a3d3cf094 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 6503cb680c 65: onsuccess: 7: Successful build after binutils: 3 commits new 488d934849 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 4117af076d 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new 89f2f23feb 68: onsuccess: 7: Successful build after linux: 6 commits new e64b7f027a 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ed16f15033 70: onsuccess: 7: Successful build after gcc: 4 commits new b52ff1ae33 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 3b01b26133 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f55bf5006c 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8623318d1c 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 3b36959c41 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new df41dcc97c 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 7c3b52059f 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 93376dc9e7 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new bc621e22fe 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 0c8262c321 80: onsuccess: 7: Successful build after linux: 44 commits new 8940b3ae31 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f1d71c7dd3 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 881cfaf4cd 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 84b0ed1f5b 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 70828333f2 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 731bc6b624 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 91a33f4493 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 940c33904c 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 934fa11ce7 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 9aa3c6af1a 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 390741fb78 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 3009d44e8a 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 858e8c9573 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 2d351e39d4 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 59b9a6b6f4 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new c0071b5dbf 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 695dd34281 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 8386bffbf2 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new d44bfa6247 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new f124f406eb 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new d6c21540c4 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 0aa0a420a5 102: force: #1551: 1: Failure after gcc: 306 commits new b91df5d10b 103: onsuccess: #1552: 1: Success after gcc: 5 commits new b5fe76412d 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new d055570433 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 08528c624f 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 34c43d7bdb 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new e3fd0c79c9 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new 8205ff3ee2 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 3449384380 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 4b5e25e1a1 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new 9b564c4650 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new cc6bb2200b 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new 494f22e981 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 944c95e798 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 270dfcc120 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 44c469f12c 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 7bcc673b0d 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new d9cbd84829 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new b7d3feb6c5 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 68e387af6f 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 0f643325d0 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 1ebf5579e3 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new e4223b4f93 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new c4713ae5b4 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new cafca1693e 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new cafd084704 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new a45fb98289 128: onsuccess: #1579: 7: Success after linux: 12 commits new f7adb86f41 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new 57e2580a16 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 36f31ae190 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (857cdd208a) \ 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 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 30200 -> 30208 bytes 05-build_abe-stage1/console.log.xz | Bin 72724 -> 71736 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 8820 -> 8284 bytes 08-build_abe-glibc/console.log.xz | Bin 239128 -> 238988 bytes 09-build_abe-stage2/console.log.xz | Bin 202412 -> 202032 bytes 10-build_abe-gdb/console.log.xz | Bin 37452 -> 37480 bytes 11-build_abe-qemu/console.log.xz | Bin 31504 -> 31712 bytes 12-check_regression/console.log.xz | Bin 3756 -> 3704 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++--------- 21 files changed, 58 insertions(+), 58 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