Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allmodconfig updated (defa9c728 -> 56c78d79e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allmodconfig in repository toolchain/ci/base-artifacts. from defa9c728 14: onsuccess: #482: 33: Success after binutils/gcc/qemu: 93 commits new 56c78d79e 15: onsuccess: #483: 33: Success after binutils/gcc/linux/qem [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1700 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 29996 -> 30384 bytes 04-build_abe-stage1/console.log.xz | Bin 72364 -> 73104 bytes 05-build_abe-qemu/console.log.xz | Bin 31668 -> 31512 bytes 06-build_linux/console.log.xz | Bin 5028 -> 4968 bytes 08-check_regression/console.log.xz | Bin 2936 -> 4332 bytes 09-update_baseline/console.log | 16 ++++++++-------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 31 ++++++++++++++++--------------- 17 files changed, 32 insertions(+), 31 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 (8f3536796 -> 76540e1b6)

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 8f3536796 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards ebb5ec7eb 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards 71be77ab3 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 54f1f95c1 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards c313a9c4a 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards a733eb8e9 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards c684ec5c1 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 5932a236f 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 0be3af258 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 2003a600d 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards db66cc1ed 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 1105b1b20 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards 7dc5012d2 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards bdf39b3bf 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 5ef15448b 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards d52a73682 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 6220f677b 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-271 [...] discards f4170df95 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards baaabbc1c 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards b4f5a024c 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards eb362832d 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards 142d3e0e2 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 20c1ef5e1 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards 865865331 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards 7e1c26775 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 020470b03 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards c7ae78543 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 6ed924959 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 84720f8db 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards ecf6092d4 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 1fc5da151 94: onsuccess: #1476: 2: Success after baseline build: no new [...] discards 2265af61c 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-2393 [...] discards 2e6f4ffae 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 7a95a3e4c 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards ed3611c3a 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards d9e316b1b 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards e181b1e8b 88: onsuccess: 1: Success after gcc: 20 commits discards a638d60b2 87: force: 1: Failure after gcc: Fix up dump_printf_loc forma [...] discards 9d4ae449a 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 w [...] discards 556b94f89 85: onsuccess: 2: Success after binutils: 4 commits discards a525d4fa2 84: onsuccess: 2: Success after gcc: 9 commits discards ef019a76a 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 5548aab83 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 40dae8233 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards f1500a79e 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 1973ed94a 79: onsuccess: 1: Successful build after gcc: 3 commits discards 17d7e065c 78: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] discards b7aeb71fe 77: force: 2: Successful build after gcc: 32 commits discards 36fb60659 76: onsuccess: 2: Successful build after binutils: 10 commits discards 47080fd75 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards a753cddac 74: onsuccess: 2: Successful build after gcc: 13 commits discards 94dbceedd 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 6e7ef6b5e 72: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] discards 38f587b29 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards ff29a7721 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards df7a82076 69: onsuccess: 2: Successful build after baseline build: no n [...] discards 148194542 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 364de079b 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 1999b0917 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 4690e8cdd 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 1096d171d 64: onsuccess: 2: Successful build after gcc: 7 commits discards 62f36bfd9 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 5e6b5a1ba 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 05c8189ff 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards cdc8d7b49 60: onsuccess: 1: Successful build after gcc: 15 commits discards a51259b13 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] discards b4bbc220d 58: force: 2: Successful build after gcc: tree.cc: Fix optimi [...] discards 8904c2c90 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards e0c36a21d 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 68f4397b0 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 92bea6257 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 13acdf7ca 53: onsuccess: 2: Successful build after gcc: 5 commits discards ad9fe76e1 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 48b65a688 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 34ad37759 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 17306260c 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 4c21d5192 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards b1d8c72a7 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards bdc33bc6f 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 6ab5d64d3 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards 3ae096e11 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 8b798e6dd 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] discards a6d5eba7b 42: onsuccess: 2: Successful build after gcc: 2 commits discards e4b532612 41: onsuccess: 2: Successful build after baseline build: no n [...] discards 67a3d6e7f 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 467515cc2 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards ac71046e3 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 4b918533e 37: onsuccess: 2: Successful build after gcc: 2 commits discards 4ddd94893 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 3e57ff107 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 733d65d5b 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 28b8cfb62 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 070a5b356 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards aad193669 31: onsuccess: 2: Successful build after gcc: 8 commits discards 2675769fe 30: onsuccess: 2: Successful build after gcc: 7 commits discards ed6a650d2 29: onsuccess: 2: Successful build after binutils: 5 commits discards 4910b903f 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards d5c5768d1 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 5b4a86f7b 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits discards 3d56489bf 25: onsuccess: binutils-gcc: 2 discards 069807280 24: onsuccess: binutils-gcc: 2 new 9fe4c6bc6 24: onsuccess: binutils-gcc: 2 new c6cee18ea 25: onsuccess: binutils-gcc: 2 new 38dae2829 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits new 0a8d27768 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits new b5400579e 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 3cb25474a 29: onsuccess: 2: Successful build after binutils: 5 commits new 2bd80f533 30: onsuccess: 2: Successful build after gcc: 7 commits new 32317af3d 31: onsuccess: 2: Successful build after gcc: 8 commits new c0f1b33b6 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 76c7c7b49 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits new e5d4a7867 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 64bfa906f 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 326c1ffb9 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 4356068f9 37: onsuccess: 2: Successful build after gcc: 2 commits new c6cdc3fb6 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits new a9b000fc4 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 6f09ee769 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 7999368fd 41: onsuccess: 2: Successful build after baseline build: no n [...] new fa5f5c8d9 42: onsuccess: 2: Successful build after gcc: 2 commits new b2e6973ce 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] new 4e38aa9c8 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ddc091e7a 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 2010ac3b1 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new b51ae64d0 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 43068431b 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 4cd43a522 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 9fb1275b6 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 378f309bc 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 37d3b8d88 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new f0e2714d0 53: onsuccess: 2: Successful build after gcc: 5 commits new d1da4434e 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 90f3d37fc 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 62688ec6b 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 87c588c0e 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 69a344bdc 58: force: 2: Successful build after gcc: tree.cc: Fix optimi [...] new dd7d119dd 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] new 721909222 60: onsuccess: 1: Successful build after gcc: 15 commits new abcb4eb38 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new c7c88d0d3 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 1d0680235 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new ccc195929 64: onsuccess: 2: Successful build after gcc: 7 commits new b0a2016e7 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new af37595c3 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new fb390a9ac 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 1fb1ed7a4 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new b846e2a28 69: onsuccess: 2: Successful build after baseline build: no n [...] new 4c6a4d98a 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 12ba011ab 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 5ebf5caaa 72: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] new 0a4929635 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 07ad20e4a 74: onsuccess: 2: Successful build after gcc: 13 commits new c06cad2ac 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new edc514aa1 76: onsuccess: 2: Successful build after binutils: 10 commits new b9024e52f 77: force: 2: Successful build after gcc: 32 commits new 0081d60a1 78: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] new b87cfbdb5 79: onsuccess: 1: Successful build after gcc: 3 commits new 7a58becd5 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new a32a8ddd0 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 2ef88b122 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 8967b82ab 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 85f9bf1fa 84: onsuccess: 2: Success after gcc: 9 commits new 55b219c5a 85: onsuccess: 2: Success after binutils: 4 commits new 6bb456a4e 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 w [...] new 442f95e73 87: force: 1: Failure after gcc: Fix up dump_printf_loc forma [...] new 799a4b42a 88: onsuccess: 1: Success after gcc: 20 commits new 64a6b781e 89: onsuccess: 2: Success after binutils/gcc: 39 commits new ff7b796ca 90: onsuccess: #1472: 2: Success after gcc: 2 commits new bf295f4b2 91: onsuccess: #1473: 2: Success after gcc: 2 commits new ea3fd4f2b 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new bbb38a36d 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-2393 [...] new a72e7a275 94: onsuccess: #1476: 2: Success after baseline build: no new [...] new 3ffa32a4d 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 1da91e1fc 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new f82cf5db3 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 87acbddd1 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new ff4cf8f26 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 2ca3f4197 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new c5104705f 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new c023a1700 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new d882c94f1 103: onsuccess: #1524: 2: Success after gcc: 2 commits new b6a4d13c3 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 4bc7c7f4c 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 4a17a1fe7 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 74f65273b 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new fac94f433 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-271 [...] new 7ed15e39a 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new b3d82ff0a 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 05408733f 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new a13fb6d4e 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 23b2d0b02 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new 9938ab163 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 1cfd45ab2 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 5cd78fe3a 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 670eb4aee 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new 500f95dbd 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 3766c68cf 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new 201a306e9 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 01bf6b40a 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new 236ca15d1 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 298d40a9a 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 16f50db6f 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new 76540e1b6 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (8f3536796) \ 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 1708 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 38828 -> 37812 bytes 05-build_abe-bootstrap/console.log.xz | Bin 272636 -> 272892 bytes 06-check_regression/console.log.xz | Bin 2896 -> 2648 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_check_bootstrap/master-aarch64-check_bootstrap updated (712bbab9a -> 761c1f964)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check_bootstrap/master-aarch64-check_bootstrap in repository toolchain/ci/base-artifacts. from 712bbab9a 42: onsuccess: #570: 1: Success after binutils/gcc: 34 commits new 761c1f964 43: onsuccess: #572: 1: Success after binutils/gcc: 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 1728 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 38132 -> 38544 bytes 04-build_abe-bootstrap/console.log.xz | Bin 269624 -> 270672 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3876 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2552 -> 2420 bytes 07-check_regression/console.log.xz | Bin 5044 -> 11908 bytes 07-check_regression/extra-bisect-params | 2 +- 07-check_regression/fails.sum | 583 ++- 07-check_regression/mail-body.txt | 123 +- 07-check_regression/results.compare | 616 ++- 07-check_regression/results.compare2 | 1531 ++++++- 07-check_regression/results.regressions | 131 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 125 +- mail/mail-subject.txt | 2 +- manifest.sh | 19 +- results | 131 +- sumfiles/g++.log.xz | Bin 3645624 -> 3619980 bytes sumfiles/g++.sum | 702 ++-- sumfiles/gcc.log.xz | Bin 3209992 -> 3255068 bytes sumfiles/gcc.sum | 5853 +++++++++++++++------------ sumfiles/gfortran.log.xz | Bin 1093396 -> 1076984 bytes sumfiles/gfortran.sum | 59 +- sumfiles/libatomic.log.xz | Bin 2356 -> 2352 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213592 -> 213200 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2724 -> 2724 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 462972 -> 465516 bytes sumfiles/libstdc++.sum | 133 +- 35 files changed, 6861 insertions(+), 3183 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-aarch64-mainline-allmodconfig updated (48ddc6c4d -> ded5dad7a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-mainline-allmodconfig in repository toolchain/ci/base-artifacts. from 48ddc6c4d 14: onsuccess: #553: 33: Success after binutils/gcc/linux/qem [...] new ded5dad7a 15: onsuccess: #554: 33: Success after binutils/gcc/linux/qem [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1712 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 30720 -> 30204 bytes 04-build_abe-stage1/console.log.xz | Bin 73248 -> 72540 bytes 05-build_abe-qemu/console.log.xz | Bin 32136 -> 31616 bytes 06-build_linux/console.log.xz | Bin 4944 -> 4780 bytes 08-check_regression/console.log.xz | Bin 3296 -> 4332 bytes 09-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 31 ++++++++++++++++--------------- 17 files changed, 24 insertions(+), 32 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[binutils-gdb] branch master updated (b7098e650c9 -> 7f241585834)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from b7098e650c9 gdbserver: remove unused for loop new 7f241585834 gdb/source.c: Fix undefined behaviour dereferencing empty string 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: gdb/source.c | 10 +--------- 1 file changed, 1 insertion(+), 9 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-stable-allmodconfig updated (833a4adea -> 4a05fb56e)

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-stable-allmodconfig in repository toolchain/ci/base-artifacts. from 833a4adea 10: onsuccess: #266: boot: Success after binutils/llvm/qemu: [...] new 4a05fb56e 11: onsuccess: #267: 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 1704 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 30260 -> 30404 bytes 04-build_kernel_llvm/console.log.xz | Bin 63440 -> 65404 bytes 05-build_abe-qemu/console.log.xz | Bin 31480 -> 31500 bytes 06-build_linux/console.log.xz | Bin 3372 -> 3376 bytes 07-boot_linux/console.log.xz | Bin 508 -> 508 bytes 08-check_regression/console.log.xz | Bin 2828 -> 3960 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_check_gcc/master-arm updated (cc17bcb0d -> 2f260e26c)

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 cc17bcb0d 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/gd [...] discards 51e27da21 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/gl [...] discards ee0bfe16f 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/gl [...] discards 6a9667b0e 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/gd [...] discards 160888ce2 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/gd [...] discards 2c2849f0d 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards febff4038 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...] discards 57ea2ffd6 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] discards d7a5b89cf 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits discards dc3b375bc 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] discards 42a4c7a6f 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] discards 78b0b9b1c 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] discards 4481c8678 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] discards fc8b989eb 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards f53f2e205 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards cf72f252b 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 6eae883c3 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] discards 5c591ccc1 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] discards abfc5ddc2 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] discards 2a5c3272d 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 4f758614d 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards 7f5f6d7ec 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards 2432e9aab 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards e714c77b5 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards ca3870ab0 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards c8c3a7090 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards 478c74a71 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 8aa956030 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 6e6d1d45c 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards c3e6cf025 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards 795402db8 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 5d3900b38 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards af27b2637 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 632b153f1 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards b8b80364e 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards aaa181510 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 8ca402148 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 8dc347515 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 93921b1ea 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards e52dc2e2d 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards a9ab0dd4c 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 6ec0bb130 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 0270fc55e 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 38ff74b06 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards 068c4e173 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 74588c6b9 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards bcf0fbe40 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 34222d04d 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards 09359b31d 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards af3997333 74: onsuccess: 1: Successful build after linux: 44 commits discards 817d7950c 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 5dac47b73 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ba9b43904 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards 398aea4a3 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards 7bfaf003c 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 853253fcb 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e6148b427 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 3202be04d 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 330a21264 65: onsuccess: 1: Successful build after gcc: 4 commits discards a931cd649 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f0e5deb09 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 442da472f 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards 6f309f9dc 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 35531e783 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 425ce3ea3 59: onsuccess: 1: Successful build after glibc: 2 commits discards b8ffa14ce 58: onsuccess: 1: Successful build after binutils: 2 commits discards 58e3c1bc9 57: onsuccess: 1: Successful build after gcc: 7 commits discards c7ceed897 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e536191c1 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d8f5573c2 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 50fe527ce 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards d07f7405e 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards a344f16b4 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards d336dba99 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a69be3069 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards d694ab6b8 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 0e7e2f26a 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1fd08dde7 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 3a3a4ec6e 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1b79f6fc1 44: onsuccess: 1: Successful build after linux: 34 commits discards 4e9a9e098 43: onsuccess: 1: Successful build after gcc: 2 commits discards 94ad81bf8 42: onsuccess: 1: Successful build after baseline build: no n [...] discards fe224d46f 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 016c0e8fb 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 618032b17 39: onsuccess: 1: Successful build after gcc: 2 commits discards 8c32cee33 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 98803be80 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards a874e1b13 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 545b32d17 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards a088ecc08 34: onsuccess: 1: Successful build after gcc: 3 commits discards ce49020bb 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards dfb9ab794 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 146725e3a 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 8d13d7625 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards baf75111b 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7aae42b72 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 65dca3e12 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards c1bca36e0 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 94d1d7a46 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b0267f0f5 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c0f842d8b 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 10bf4dfa5 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 400806b5f 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a1b3e7204 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2b9f8f8c8 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5ef301488 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 32276625e 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 07984f40f 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2f873fa46 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new df4861eef 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new b346af96e 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 0005672bd 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 57b66db3d 34: onsuccess: 1: Successful build after gcc: 3 commits new b118770ed 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new ee58f11ed 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 33c873156 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 02182fecf 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new efb64e088 39: onsuccess: 1: Successful build after gcc: 2 commits new a6b5c4e72 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2636640f3 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a8d9133b8 42: onsuccess: 1: Successful build after baseline build: no n [...] new 399f5b106 43: onsuccess: 1: Successful build after gcc: 2 commits new 7ad547a5b 44: onsuccess: 1: Successful build after linux: 34 commits new 785a12f70 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 06a3a6a2a 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new a3af03175 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 671ff536d 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 4c4f0ac82 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new ecb16f14b 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new dd7a2bf2e 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new c3f3e6c08 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new f23f5c1c5 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new fea5c7955 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new b99573bfd 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 3f946d6c5 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 17eec5513 57: onsuccess: 1: Successful build after gcc: 7 commits new 7c1578770 58: onsuccess: 1: Successful build after binutils: 2 commits new e719a90bf 59: onsuccess: 1: Successful build after glibc: 2 commits new ee1e6db7d 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 2a6bf4391 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 5b99bef05 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new 2c0f53d65 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 01e2800c2 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c6932390a 65: onsuccess: 1: Successful build after gcc: 4 commits new cc16f96b3 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new dc5173138 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new dd15e0c06 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 634d523c1 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new f82c035e6 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new c7ea99df3 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new 30b3196b1 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 33acda8e4 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new a54224135 74: onsuccess: 1: Successful build after linux: 44 commits new 4898ced99 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e36b4ff52 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new 929e5d238 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 262023bd2 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new cd5ad136c 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new c28d77d88 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new 7bc67ea73 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new f879448ca 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new e6717fd33 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 2b7ff7148 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 006281681 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 41331744a 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 215edec3a 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 1c8216536 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 251539605 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new d7a79745a 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new c912562c2 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 7bd2195f5 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new 0a681be15 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 9e04678d0 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new b350273bf 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new fb7c9c1a5 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 80d01fc73 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new 8c4d20c10 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new 3caa2c447 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new c8bf6a03c 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new dd433b442 101: onsuccess: #1693: 1: Success after glibc: 14 commits new b693ec556 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new 6e96051c6 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new 8de2316ca 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 2a25fd9ac 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] new f3a5d2551 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] new 0ce2c4929 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] new 226aadc42 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 03b25f166 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new fa5322b39 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 7c52dee1c 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] new 3c38dacce 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] new 6b6de671e 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] new 787c0b6ac 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] new fca47379d 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits new 7005d8bef 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] new 1b1685a57 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...] new fb01ee06b 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 75f39fff4 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/gd [...] new 0a0aa5ee4 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/gd [...] new 5605e65c8 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/gl [...] new 97f8f6190 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/gl [...] new 6ac2284ce 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/gd [...] new 2f260e26c 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (cc17bcb0d) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1692 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 29980 -> 30032 bytes 04-build_abe-stage1/console.log.xz | Bin 90796 -> 90540 bytes 06-build_abe-linux/console.log.xz | Bin 8844 -> 8808 bytes 07-build_abe-glibc/console.log.xz | Bin 233684 -> 233776 bytes 08-build_abe-stage2/console.log.xz | Bin 222864 -> 223020 bytes 09-build_abe-gdb/console.log.xz | Bin 37112 -> 37228 bytes 10-build_abe-qemu/console.log.xz | Bin 30940 -> 31256 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3852 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2432 -> 2440 bytes 13-check_regression/console.log.xz | Bin 7100 -> 5348 bytes 13-check_regression/results.compare | 14 + 13-check_regression/results.compare2 | 698 +--------- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- sumfiles/g++.log.xz | Bin 2684376 -> 2651708 bytes sumfiles/g++.sum | 34 +- sumfiles/gcc.log.xz | Bin 2199756 -> 2207648 bytes sumfiles/gcc.sum | 2256 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 882348 -> 879888 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201156 -> 201268 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 419880 -> 426708 bytes sumfiles/libstdc++.sum | 8 +- 36 files changed, 1230 insertions(+), 1894 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 updated (3d1deb601 -> ea67de89a)

by git＠git.linaro.org

2 years, 2 months

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

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 fd8f90be3 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/gd [...] discards 199d59109 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/gl [...] discards ce9a85603 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/gl [...] discards 25f39e358 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/gd [...] discards 1017ab4cf 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/gd [...] discards e41cef4e2 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 commits discards 27030e006 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qemu [...] discards a76a0ddc4 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/gl [...] discards 6d40639db 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 commits discards b6d6121af 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: 1 [...] discards 71a712b51 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/gd [...] discards bd520f3f3 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/gl [...] discards 595dd9e78 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/gd [...] discards 3a0689e7e 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards c8acedfc8 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 46f58b6a4 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards c5c4bea16 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/gd [...] discards 62abbd79b 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/gd [...] discards 15d85de01 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] discards 79bb0ee93 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards cac78799e 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards a3585f8e8 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] discards bd3286aa0 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 6d017f555 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] discards 4eb3b4088 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] discards 521167911 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 4947c46d8 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] discards 32076d0dc 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] discards a06022765 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards ec7df211a 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] discards ae2aa64f1 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] discards ddecc247c 95: onsuccess: #1529: 7: Success after baseline build: no new [...] discards eaf6532d3 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 56724737a 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] discards 38cfa7f47 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 4719a1032 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 4ece09073 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 92c03812e 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 1e85a7449 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 5ccda7118 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards c37975494 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 825f49059 85: onsuccess: 7: Success after gcc: 9 commits discards d212f16e1 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards b4fe3a12f 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 9f7f44f1d 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 6bc2ce444 81: onsuccess: 7: Successful build after gcc: 2 commits discards 0210a401f 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards 1a0a75365 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 9b79b2a87 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 42b4e8d79 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards db87e1e0e 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 786e9c58b 75: onsuccess: 7: Successful build after linux: 44 commits discards 318d19d20 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 96f91810e 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 542592ceb 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards ae286348b 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards c22b4b8fb 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 49a2c9b4f 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards bb59d772b 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards b658da989 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards f7e4e800c 66: onsuccess: 7: Successful build after gcc: 3 commits discards dff26935b 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 9cd6d9b0c 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 2a00f9008 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards b2f7162cc 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 8aa7fe33a 61: onsuccess: 4: Successful build after gcc: 15 commits discards aa3a53c54 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards 4182d4094 59: force: 7: Successful build after gcc: 2 commits discards 495368494 58: onsuccess: 7: Successful build after glibc: 2 commits discards dbbbc11d8 57: onsuccess: 7: Successful build after gcc: 7 commits discards 57e947998 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 07e4dba29 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 9e2b47a1e 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards fdd2f4930 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] discards 13bae1b71 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 1b3999eed 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 19c517d8d 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 43413e1a2 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 2f044a545 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 5c7f42d73 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 04f35ab2e 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards f5f895619 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 6778dd4b6 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards d0dc7cc09 43: onsuccess: 7: Successful build after gcc: 2 commits discards f2610ced9 42: onsuccess: 7: Successful build after baseline build: no n [...] discards 4cc7af68b 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 8448e0fcf 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 1c8c4ba58 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits discards 15f6e85dc 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards f771d7b63 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 39505d1a7 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 56fdfb03f 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 38cfed6b0 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 38c9514b6 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards f764a2d01 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards adaf9aaf5 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards fb5207c21 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards f6c8a2ced 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards b50e24064 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 5487b9695 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 7f76438cc 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new fbc7a77a3 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d1ac45e88 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 7a33f2458 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new da028d88f 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 865acf879 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 1739232bc 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 35769b966 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 8e304221d 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 43b1079d9 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 7ea57e0a8 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new e55b0bc19 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 5dd422653 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new b3426e742 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new 358ae0604 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits new 80b1eadeb 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 0750a1271 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 2555a03b1 42: onsuccess: 7: Successful build after baseline build: no n [...] new 0aa30cc47 43: onsuccess: 7: Successful build after gcc: 2 commits new 929ea3bef 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new da1dc1c6b 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 5ab01466a 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 858fc6135 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 2c5f3368e 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new e3089e707 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new ab06ddce1 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 70a841cf2 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 20b2d653d 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new f35c0d16a 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] new 88ca4c386 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new a0b59b067 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new f1e423365 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new a94e558a1 57: onsuccess: 7: Successful build after gcc: 7 commits new b09165db0 58: onsuccess: 7: Successful build after glibc: 2 commits new 350338094 59: force: 7: Successful build after gcc: 2 commits new 793a7e683 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new 6990fdd7d 61: onsuccess: 4: Successful build after gcc: 15 commits new 6913ad3d1 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new f8703333c 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new 3255156d5 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new eafdba27f 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 708f8e28e 66: onsuccess: 7: Successful build after gcc: 3 commits new 417a6c876 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 373cc17d0 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new b212e45ce 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new cfb11acf2 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 50f7ceaad 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new a847b91ab 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 2be9520aa 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 90295ba2e 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 5e6e9365b 75: onsuccess: 7: Successful build after linux: 44 commits new c6aae2339 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new d9d2c7b93 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new 3c0e8e83f 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 9315273ee 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 7874cc93e 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new 3df637800 81: onsuccess: 7: Successful build after gcc: 2 commits new ef18471cb 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new aff283b4e 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 278d46354 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 62f4f38dc 85: onsuccess: 7: Success after gcc: 9 commits new 96e782588 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 47c2e4bba 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new ff11be6ec 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 72c6d996f 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 6cd6e4555 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 7332a33ff 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new b75355288 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 5f73d7458 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] new a59f617b7 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 2c9732a9f 95: onsuccess: #1529: 7: Success after baseline build: no new [...] new 0d970f8fb 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] new 7f4fb7254 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] new 1866cd6bf 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 96ef0e031 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] new d4f90635e 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] new fd191c9b1 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 2ea2e0a71 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] new 364e07196 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] new aa2bfa10f 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new e17510dec 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] new 4e14393a5 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 36f1d5048 107: onsuccess: #1618: 7: Success after gcc: 2 commits new a7e460ccc 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] new 51c81b842 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/gd [...] new 6dfac3ecf 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/gd [...] new 2785a589a 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new d81ed3de6 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 3eb50701a 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 6241e6656 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/gd [...] new 259594465 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/gl [...] new 8c6afc09d 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/gd [...] new 54f149203 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: 1 [...] new 6f1e05bed 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 commits new 84cbc57d0 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/gl [...] new 903130602 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qemu [...] new eadc68b39 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 commits new 1aac5897b 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/gd [...] new aa8e016d3 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/gd [...] new 2ed18c1a9 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/gl [...] new 73a47f647 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/gl [...] new 65ba61a5d 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/gd [...] new a070be858 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (fd8f90be3) \ 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 1692 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 29792 -> 30252 bytes 05-build_abe-stage1/console.log.xz | Bin 90852 -> 90624 bytes 07-build_abe-linux/console.log.xz | Bin 8824 -> 8860 bytes 08-build_abe-glibc/console.log.xz | Bin 234092 -> 234140 bytes 09-build_abe-stage2/console.log.xz | Bin 222484 -> 223500 bytes 10-build_abe-gdb/console.log.xz | Bin 37184 -> 37276 bytes 11-build_abe-qemu/console.log.xz | Bin 31076 -> 30912 bytes 12-check_regression/console.log.xz | Bin 4076 -> 3416 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +++++++-------- 18 files changed, 52 insertions(+), 52 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_debug updated (6cefebbcd -> b60f962ef)

by git＠git.linaro.org

2 years, 2 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022