Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (4b38d077b6 -> e9f116a428)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 4b38d077b6 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards a1283d2014 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards 2a1947f62b 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards c6c9b17e3f 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards c5e14eac5f 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 10c7579a58 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards d02370b37f 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards ca2a2cd98e 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards dc148f0b1b 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards 3cd8e41ad1 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards ba77f0af90 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 1ce153b331 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards 01fad9c3f7 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards b203ec2e16 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards afccf6acdd 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards 1a913165b7 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards a6dd16cc85 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards b881f5be78 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 3c60a61690 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 7708ae4625 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 474e10dcf4 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards 10d2caa01b 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards 7243b2bde4 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 3478d168a5 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards 0f931dc59e 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards 0ec3c88484 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 1e7aa225dd 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards c51ca3c679 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 0cfe5d8299 125: onsuccess: #614: 1: Success after linux: 12 commits discards c09801c04e 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 071e036679 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 64b68629ba 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards fff6d4c141 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 12258c2ff2 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 6129fdce89 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 990d4f319e 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards cad6d4d529 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 4586aa2a0e 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards ac6293367b 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards 0cca833d80 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 431bcf1dda 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 44e10472e6 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards 66f7ed138c 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards cb05491759 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 6885730d6d 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 0223e96185 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards d2b3319bbe 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards c1dad961d2 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 0a710190fd 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 0e2470953b 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 3a475ef208 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 53d328f7fc 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 2bf38e0baf 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards c57d5c9008 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 2c5fa233bd 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards c49a21cef7 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 72bea92ced 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 84922f0a85 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards d7def8229c 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards eb0a96ad75 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 337e2f148d 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards fadabddf40 92: onsuccess: #575: 1: Success after linux: 34 commits discards fb1de5d122 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 4c46dce73f 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 13a8f2db30 89: onsuccess: #570: 1: Success after linux: 11 commits discards 24ce7756e1 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 3ab1745a0f 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 5b0a642889 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards f4e44b29f7 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards bda3c5f2bc 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 193914c395 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards b8bb549ead 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 6311f60cc7 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 51fd3d6872 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 3de687a345 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 920fe272ed 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards b0837cda37 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 72170c58a5 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 26625cf5ea 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 6aa729d4a5 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards f94a53d6eb 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 7ccc30d564 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 29fdcb24f9 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 85669aa79d 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 81b0e4cc80 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards e9709a942a 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards a58621c35a 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 4f75c3269e 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 7d70374e17 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards c336daeff1 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 2495ee7014 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 4f5e340b0d 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards b112338fd1 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 641214b9ec 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards a73db00852 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 3ee2b7650c 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards da0d07466b 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards f4cc0b6de5 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 3786c33ff3 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 9bbb363c41 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards e69723b0cb 53: onsuccess: #531: 1: Success after binutils: 12 commits new 59e8d710ff 53: onsuccess: #531: 1: Success after binutils: 12 commits new 498d219552 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new ffe1e621e9 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 886bc195ab 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 48d8781b3a 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 771a7d5973 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new ae8f0da706 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 3a745f94f5 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new ae628412a5 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 22bf333200 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new b058e4ad47 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 4981b55623 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 24ada70878 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new c210b4dc31 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 43cfe799fb 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 7bb8fedf1e 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new dcc1d35a89 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new ec7db68d86 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 57bc2799ab 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 74a13ed02c 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 805468d5f7 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new ce82e93213 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new ee0e7ba2c4 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new ee4ecbb319 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 89c4a3e8eb 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 378a30a49a 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 8ac3153eee 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 31160b6c26 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 471288c2e8 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 15cbdde84b 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 5493a40a1f 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 0f0a91b800 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 14537aeace 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 60a40896be 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 1907c020a5 87: onsuccess: #567: 1: Success after binutils: 8 commits new beedc34dcc 88: onsuccess: #569: 1: Success after glibc: 10 commits new f529d5544c 89: onsuccess: #570: 1: Success after linux: 11 commits new 731a858fa2 90: onsuccess: #572: 1: Success after binutils: 15 commits new fb097dac96 91: onsuccess: #574: 1: Success after glibc: 3 commits new ca06fb3835 92: onsuccess: #575: 1: Success after linux: 34 commits new ad842dba91 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 707db10b5a 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 1a56da9788 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new a488068809 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 48ec703e66 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new f4fe821951 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new fdf2938d97 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new a995ece949 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new bddb186229 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 7ff051b5b7 102: onsuccess: #586: 1: Success after binutils: 5 commits new b8a7bf0377 103: onsuccess: #589: 1: Success after binutils: 3 commits new 0ef6223e94 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 8c4c7373e7 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 324b7f616c 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 1bdaad0de9 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 4dcc6fad6a 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 3043ef1458 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new e172642df6 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new caf885490a 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 1f02fb3dcf 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 436a490b06 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new 3588dae320 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 41e0d84d0c 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 6739be0d82 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 4bc4352ba8 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new 6f3f3073c7 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 56fa15e372 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new b121e603f4 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new ab230e10cf 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 9b0d89c081 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new bb64b1ced0 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new 716fa3c47a 124: onsuccess: #612: 1: Success after binutils: 18 commits new cc55955407 125: onsuccess: #614: 1: Success after linux: 12 commits new 80d941ad6c 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new 1a5da410b0 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 675e0de874 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new b666b44956 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 096e1c2516 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 1dac1e972b 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new b99a0f47df 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 58fe9c4907 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new 8423cf423a 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 500bf62188 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new f6b3ca5eff 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new d34d9d4093 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new c0eed13e99 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 09b529f500 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new 898ca7560a 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new 392cfad971 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new ae03c9e6c0 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new 80fcd42f32 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new f707ee2b3a 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new f13f6cb623 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 16b9821168 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new f1d64c1764 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new 5a0b864061 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 4101a035d9 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 3e1623e592 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new c4463e7464 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 39ba4c3378 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new c67c81d928 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new e9f116a428 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] 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 (4b38d077b6) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] 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 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 53160 -> 53412 bytes 04-build_abe-gcc/console.log.xz | Bin 239588 -> 240576 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8996 -> 8992 bytes 07-build_abe-glibc/console.log.xz | Bin 238424 -> 237316 bytes 08-build_abe-gdb/console.log.xz | Bin 52464 -> 52300 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3820 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2244 -> 2212 bytes 11-check_regression/console.log.xz | Bin 16476 -> 17104 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 138 +- 11-check_regression/mail-body.txt | 225 +- 11-check_regression/results.compare | 187 +- 11-check_regression/results.compare2 | 3336 ++++++----- 11-check_regression/results.regressions | 135 +- 12-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 227 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 135 +- sumfiles/gdb.log.xz | Bin 1714436 -> 1803940 bytes sumfiles/gdb.sum | 9212 +++++++++++++++++++++---------- 30 files changed, 8706 insertions(+), 5001 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (457956081e -> 7a14b6d8d3)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 457956081e 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] discards df8373149c 152: onsuccess: #903: 1: Success after linux: 22 commits discards 2d560158a3 151: onsuccess: #902: 1: Success after glibc: 8 commits discards a3f127c2a9 150: onsuccess: #900: 1: Success after gcc: 11 commits discards b2bb36cb3a 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 37c7bd95b0 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] discards 53b618e272 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] discards 140a1268c4 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] discards b9ea3cde68 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 2b74c9d0d7 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards a8cabe0fdf 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards 9150be5a77 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 58869bfd9b 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards 8145262f83 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 1b0ded0f7f 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards 57b65f462e 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 86d9c5134a 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 4bc331e774 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards 0d54b51171 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 594b0ff830 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards 3e6bea26bd 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 2ee59219b6 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards 5bf0666569 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 919d0e2dc0 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards 82b7fd1ace 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 5a33fd372d 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 42f898655e 127: onsuccess: #874: 1: Success after linux: 219 commits discards 84a2625344 126: onsuccess: #873: 1: Success after glibc: 2 commits discards f81a891981 125: onsuccess: #871: 1: Success after binutils: 26 commits discards ee3d97c177 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards 6dc2ea8935 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards 4bfe0d675d 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards 3f018c28b5 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards 230b91e784 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards 2168f168b3 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards f0201acc0d 118: onsuccess: #863: 1: Success after linux: 12 commits discards 68a2828268 117: onsuccess: #861: 1: Success after binutils: 18 commits discards e324023d1b 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 360fc7d6e8 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 6dab057057 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards 0a3dfc75a1 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards 73e2af7a3e 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 3949b432c1 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards f9ba57c46a 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards e80ae7bb1c 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards 26fc44a8c3 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 7c8412aa76 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 951acba236 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards ecedc2310b 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards da20b71cd0 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 3281b42958 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards b4afb52bb4 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 677833b977 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 50acd14367 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 17eaeceab0 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 14a51a1c79 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 0758cbdc74 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards b2a762b5e5 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards d1ac4e7dc3 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 4d2a7a859a 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 6450094061 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 421a8510a1 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards ffde741745 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 17194cbccc 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 4ed6c741a5 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 41e7f7f927 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 9a857dd235 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards c0218fd1cd 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards ec1836e2a5 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards c5fa577139 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 219cd19d69 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 6de3c8a575 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 06cb637df7 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 0947e2f760 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 14adc77da2 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 9265d60cff 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards e7be0abd00 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 5bcbf4bfe6 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 1edae6c711 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 5cfe6c829e 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 0629a322d2 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 9abd877871 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 481506d0d3 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 0ed951f1b4 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 7e1d2871ba 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards f4fe2edd84 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 6a7e211ca3 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards bb1063f51a 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards b0e7233362 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 18c5a5a303 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 27299d8dbd 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards ed3b059c93 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards c4ce562a7d 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 1d65c82aaa 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards 866bdf5ac8 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 23b868d504 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards 6d71b404ff 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 3d2167de8c 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 659ae60f73 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 789efd1671 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards 0690d5243b 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 4ee3c6290c 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 7a03cffc5b 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 53ea20c06d 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new aec0df62e9 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 29a57fdc26 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new 9e66592b60 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 1cfca385b8 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 305642f34a 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new be7dd7a850 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new c1f9fff756 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 85ab07a401 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new df8427254a 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 0841f80546 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 509de37115 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new df642ad2cd 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 3bbc29b088 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 69187de467 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 95d4d962e8 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new b859555849 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 4184f44548 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 2337c886ba 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 33eeae53a3 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new a015f7965c 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new fdfa8a12c6 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 9c61d6466f 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 91a649e5e0 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new b3854cbb9e 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new d4e636f08b 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 932c1eae17 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new 8a8603a97f 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new aeaccd57c4 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 147e247419 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 0a746ab260 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 129f6ea2f8 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new a660377f7f 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 00faa0524a 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 351ac90f9b 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new a1b6b00430 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new b58327d892 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 78ea7abd1f 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 362f252964 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new ba1579ca2a 94: onsuccess: #832: 1: Success after binutils: 5 commits new 4fca3f2dc3 95: onsuccess: #835: 1: Success after binutils: 3 commits new f37b81e102 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new b204f66e8c 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 4313250b84 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new ff23b8bceb 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 92b9183fe6 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 52f7a88c60 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 5a904cef31 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 606c5d3bab 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new d0ff2c3eef 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new d948c1f1b4 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 7282f5843c 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new cc06176097 107: onsuccess: #849: 1: Success after binutils: 5 commits new 74c320ff3e 108: onsuccess: #850: 1: Success after gcc: 2 commits new 966158af50 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 7d535e175a 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 75044df4f1 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 12fde78254 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new dd8e8dfd2c 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new 48381cebcc 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new 62e8fc5392 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new bbe483a52f 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new ff4faeea31 117: onsuccess: #861: 1: Success after binutils: 18 commits new 26aed354ea 118: onsuccess: #863: 1: Success after linux: 12 commits new a6b1f1cf6e 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new db2e90b651 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 64081bee4d 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new 84e0174dc4 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new 990acc209e 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 69d59f2c3e 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new ba2da63e55 125: onsuccess: #871: 1: Success after binutils: 26 commits new 953fa52492 126: onsuccess: #873: 1: Success after glibc: 2 commits new 832ceb68c8 127: onsuccess: #874: 1: Success after linux: 219 commits new eb21cfd105 128: onsuccess: #876: 1: Success after binutils: 12 commits new c2a909d9a9 129: onsuccess: #878: 1: Success after linux: 3008 commits new 4889c9e334 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new e4c1296b32 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new fa9bb678d1 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new 06cf0b6740 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new aeff30dce5 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new eb5d8f015d 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new a5963c1914 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 4528754d9c 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 8c77cd9a61 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 80f1d871c2 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new 71a2b72be4 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 6ad65fabfc 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new 1ed4b689e5 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new d6c5f8f213 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new 47f314f029 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new 5467061f70 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 610e74f299 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] new 615a782129 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] new a2e6bcdacd 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] new 67ae52ba79 149: onsuccess: #899: 1: Success after binutils: 15 commits new 686bf64217 150: onsuccess: #900: 1: Success after gcc: 11 commits new 135aa944ad 151: onsuccess: #902: 1: Success after glibc: 8 commits new 7dcf1fbc6b 152: onsuccess: #903: 1: Success after linux: 22 commits new 96a284c049 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] new 7a14b6d8d3 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] 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 (457956081e) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] 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 1748 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 39816 -> 39944 bytes 04-build_abe-gcc/console.log.xz | Bin 215532 -> 215468 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8948 -> 8856 bytes 07-build_abe-glibc/console.log.xz | Bin 245288 -> 245188 bytes 08-build_abe-gdb/console.log.xz | Bin 39536 -> 39668 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3844 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2808 -> 2888 bytes 11-check_regression/console.log.xz | Bin 6384 -> 6196 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 83 +- 12-update_baseline/console.log | 48 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- sumfiles/g++.log.xz | Bin 3764924 -> 3731792 bytes sumfiles/g++.sum | 152 +- sumfiles/gcc.log.xz | Bin 3312392 -> 3335620 bytes sumfiles/gcc.sum | 4324 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1078964 -> 1074888 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2280 -> 2272 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 233004 -> 232408 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 457488 -> 454116 bytes sumfiles/libstdc++.sum | 10 +- 37 files changed, 2434 insertions(+), 2319 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[binutils-gdb] branch master updated (d654ad96eb4 -> 0ad0387c85f)

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 d654ad96eb4 Use first_opcode in another spot new 4036ad07f42 gdb: ensure test_name is initialized in gdb_breakpoint new 0ad0387c85f x86: Remove duplicated I386_PCREL_TYPE_P/X86_64_PCREL_TYPE_P 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: bfd/elfxx-x86.h | 7 ------- gdb/testsuite/lib/gdb.exp | 3 ++- 2 files changed, 2 insertions(+), 8 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[gcc] branch master updated (fc349931adc -> 238e292cf5d)

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 fc349931adc c++: Error recovery in merge_default_template_args [PR108206] new 238e292cf5d c++: mark_single_function and SFINAE [PR108282] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/cp/decl2.cc | 2 +- gcc/testsuite/g++.dg/cpp2a/concepts-requires34.C | 19 +++++++++++++++++++ 2 files changed, 20 insertions(+), 1 deletion(-) create mode 100644 gcc/testsuite/g++.dg/cpp2a/concepts-requires34.C -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-lts-allmodconfig updated (92db59ddc0 -> a832c65962)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-lts-allmodconfig in repository toolchain/ci/base-artifacts. from 92db59ddc0 35: onsuccess: #497: 33: Success after binutils/gcc: 68 commits new a832c65962 36: onsuccess: #498: 33: Success after binutils/gcc/linux/qe [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1736 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31716 -> 31924 bytes 04-build_abe-stage1/console.log.xz | Bin 91548 -> 91440 bytes 05-build_abe-qemu/console.log.xz | Bin 31576 -> 31152 bytes 06-build_linux/console.log.xz | Bin 5128 -> 5080 bytes 08-check_regression/console.log.xz | Bin 3424 -> 4400 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 16 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-lts-allmodconfig updated (ef9cb2cdee -> 0889150cf6)

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-release-arm-lts-allmodconfig in repository toolchain/ci/base-artifacts. from ef9cb2cdee 35: onsuccess: #412: all: Success after binutils/gcc: 10 commits new 0889150cf6 36: onsuccess: #413: all: Success after binutils/gcc/linux/q [...] 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 1740 -> 1936 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30000 -> 30236 bytes 04-build_abe-stage1/console.log.xz | Bin 86960 -> 87016 bytes 05-build_abe-qemu/console.log.xz | Bin 30716 -> 31188 bytes 06-build_linux/console.log.xz | Bin 3460 -> 3452 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 3216 -> 4088 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 updated (08a32ac24c -> 6e43b40f0b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. from 08a32ac24c 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 6e43b40f0b 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] 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 1760 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 39900 -> 39716 bytes 04-build_abe-gcc/console.log.xz | Bin 214736 -> 215068 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8896 -> 8920 bytes 07-build_abe-glibc/console.log.xz | Bin 246552 -> 246300 bytes 08-build_abe-gdb/console.log.xz | Bin 40016 -> 40232 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3916 -> 3984 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2588 -> 2684 bytes 11-check_regression/console.log.xz | Bin 6116 -> 5700 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- 12-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- sumfiles/gdb.log.xz | Bin 14636 -> 14608 bytes sumfiles/gdb.sum | 34 +++++++++++++++++----------------- 25 files changed, 47 insertions(+), 47 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-arm updated (52d74b38df -> 7f86e58efc)

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/master-arm in repository toolchain/ci/base-artifacts. discards 52d74b38df 492: onsuccess: #2134: 1: Success after binutils/gcc: 4 commits discards 329b26e6bc 491: onsuccess: #2133: 1: Success after binutils/gcc: 7 commits discards 8cce3fc66e 490: onsuccess: #2132: 1: Success after binutils/gcc: 4 commits discards d26faddec9 489: onsuccess: #2131: 1: Success after binutils/gcc: 24 commits discards 1cc3e9956b 488: onsuccess: #2130: 1: Success after binutils/gcc: 17 commits discards 9bfed8195c 487: onsuccess: #2129: 1: Success after binutils/gcc: 16 commits discards 03274c8200 486: onsuccess: #2128: 1: Success after binutils/gcc: 2 commits discards aeb8fa59ca 485: onsuccess: #2127: 1: Success after binutils/gcc: 7 commits discards 373caf3701 484: onsuccess: #2126: 1: Success after binutils/gcc: 6 commits discards dc8c3862da 483: onsuccess: #2125: 1: Success after binutils/gcc: 5 commits discards 0fc0f2f603 482: onsuccess: #2124: 1: Success after binutils/gcc: 7 commits discards 02f600c208 481: onsuccess: #2123: 1: Success after binutils/gcc: 8 commits discards 11a31552ca 480: onsuccess: #2122: 1: Success after basepoints/gcc-13-49 [...] discards 38d9cdc0ae 479: onsuccess: #2121: 1: Success after binutils/gcc: 3 commits discards 4b27132036 478: onsuccess: #2120: 1: Success after basepoints/gcc-13-49 [...] discards 108ed0dd61 477: onsuccess: #2119: 1: Success after binutils/gcc: 5 commits discards 59f25ff1dd 476: onsuccess: #2118: 1: Success after binutils: 9 commits discards 1692131cc9 475: onsuccess: #2117: 1: Success after binutils/gcc: 2 commits discards 6d8d9e9bb1 474: onsuccess: #2116: 1: Success after binutils/gcc: 8 commits discards eca7ca5b75 473: onsuccess: #2115: 1: Success after binutils/gcc: 3 commits discards 369cfcc0a6 472: onsuccess: #2114: 1: Success after gcc: 17 commits discards 91ed1cb74a 471: onsuccess: #2113: 1: Success after gdb-13-branchpoint-2 [...] discards 35ba376231 470: onsuccess: #2112: 1: Success after binutils/gcc: 2 commits discards b1ab2f0b35 469: onsuccess: #2111: 1: Success after binutils/gcc: 3 commits discards 39f0b21604 468: onsuccess: #2110: 1: Success after gdb-13-branchpoint-2 [...] discards 6502e8f622 467: onsuccess: #2109: 1: Success after gcc: 2 commits discards 093a4a2134 466: onsuccess: #2108: 1: Success after binutils/gcc: 5 commits discards eea43dac1c 465: onsuccess: #2107: 1: Success after binutils/gcc: 6 commits discards e65233a681 464: onsuccess: #2106: 1: Success after gcc: 9 commits discards 9aad450344 463: onsuccess: #2105: 1: Success after binutils/gcc: 10 commits discards 06aa36046e 462: onsuccess: #2104: 1: Success after binutils/gcc: 2 commits discards 0c087daea2 461: onsuccess: #2103: 1: Success after binutils/gcc: 2 commits discards 0fdd7a2e97 460: onsuccess: #2102: 1: Success after binutils: 2 commits discards 0c3336ce11 459: onsuccess: #2101: 1: Success after binutils/gcc: 3 commits discards 664f6f9f66 458: onsuccess: #2100: 1: Success after gdb-13-branchpoint-1 [...] discards 273230c59a 457: onsuccess: #2099: 1: Success after binutils/gcc: 2 commits discards 555c6aefb8 456: onsuccess: #2098: 1: Success after binutils: 10 commits discards a768f7d839 455: onsuccess: #2097: 1: Success after binutils/gcc: 11 commits discards 4ccaf5a312 454: onsuccess: #2096: 1: Success after gcc: 4 commits discards 6dfffc62b9 453: onsuccess: #2095: 1: Success after gdb-13-branchpoint-1 [...] discards 182fc3f85f 452: onsuccess: #2094: 1: Success after binutils/gcc: 4 commits discards 8fdf28b827 451: onsuccess: #2093: 1: Success after binutils/gcc: 4 commits discards 28bc61c774 450: onsuccess: #2092: 1: Success after binutils/gcc: 28 commits discards 15f78e954f 449: onsuccess: #2091: 1: Success after binutils/gcc: 29 commits discards b030d936e1 448: onsuccess: #2090: 1: Success after binutils/gcc: 28 commits discards 1bae000ce7 447: onsuccess: #2089: 1: Success after binutils/gcc: 10 commits discards 024b204900 446: onsuccess: #2088: 1: Success after binutils/gcc: 6 commits discards db86da169a 445: onsuccess: #2087: 1: Success after binutils/gcc: 15 commits discards 8a04f8f3ed 444: onsuccess: #2086: 1: Success after binutils/gcc: 12 commits discards 9b6be32581 443: onsuccess: #2085: 1: Success after binutils/gcc: 4 commits discards 78a62f013b 442: onsuccess: #2084: 1: Success after binutils/gcc: 12 commits discards 6e06314ab1 441: onsuccess: #2083: 1: Success after binutils/gcc: 38 commits discards 984bcd33cc 440: onsuccess: #2082: 1: Success after binutils/gcc: 11 commits discards 190620204a 439: onsuccess: #2081: 1: Success after binutils/gcc: 4 commits discards cf449a5140 438: onsuccess: #2080: 1: Success after gcc: 3 commits discards f3bfc8300f 437: onsuccess: #2079: 1: Success after binutils/gcc: 4 commits discards 1e0c2a59b1 436: onsuccess: #2078: 1: Success after binutils/gcc: 6 commits discards 132acba5f2 435: onsuccess: #2077: 1: Success after gcc: 5 commits discards e6c27835b7 434: onsuccess: #2076: 1: Success after binutils/gcc: 30 commits discards d640ec9859 433: onsuccess: #2075: 1: Success after binutils/gcc: 16 commits discards e6dc7ad010 432: onsuccess: #2074: 1: Success after binutils/gcc: 2 commits discards 406964aff7 431: onsuccess: #2073: 1: Success after basepoints/gcc-13-47 [...] discards 61bffcbc59 430: onsuccess: #2072: 1: Success after binutils/gcc: 3 commits discards 70bf1c4c18 429: onsuccess: #2071: 1: Success after binutils/gcc: 5 commits discards 6322096e64 428: onsuccess: #2070: 1: Success after basepoints/gcc-13-47 [...] discards 82bc783a28 427: onsuccess: #2069: 1: Success after basepoints/gcc-13-47 [...] discards 223175acb8 426: onsuccess: #2068: 1: Success after binutils: 9 commits discards a964fe825d 425: onsuccess: #2067: 1: Success after binutils/gcc: 5 commits discards 2a72b773e5 424: onsuccess: #2066: 1: Success after gcc: 11 commits discards 9383dfd3b3 423: onsuccess: #2065: 1: Success after binutils/gcc: 21 commits discards 4e49a6e99b 422: onsuccess: #2063: 1: Success after binutils/gcc: 6 commits discards 02caab2888 421: onsuccess: #2062: 1: Success after binutils/gcc: 15 commits discards 0b99b5b601 420: onsuccess: #2061: 1: Success after binutils/gcc: 13 commits discards b1d0effc7f 419: onsuccess: #2060: 1: Success after gcc: 3 commits discards 0eaae4d320 418: onsuccess: #2059: 1: Success after binutils/gcc: 2 commits discards a3a394fd32 417: onsuccess: #2058: 1: Success after gcc: 7 commits discards 6ce19d5f8a 416: onsuccess: #2057: 1: Success after binutils/gcc: 17 commits discards 03af0b49d9 415: onsuccess: #2056: 1: Success after binutils/gcc: 10 commits discards b7d3d72e49 414: onsuccess: #2055: 1: Success after binutils/gcc: 12 commits discards 623fa3292b 413: onsuccess: #2054: 1: Success after binutils/gcc: 10 commits discards db149b6d31 412: onsuccess: #2053: 1: Success after binutils/gcc: 53 commits discards 611aa351d6 411: onsuccess: #2052: 1: Success after binutils/gcc: 6 commits discards d367cdbb71 410: onsuccess: #2051: 1: Success after binutils/gcc: 5 commits discards 3f25b26412 409: onsuccess: #2050: 1: Success after binutils/gcc: 6 commits discards ba5ee851ec 408: onsuccess: #2049: 1: Success after binutils/gcc: 26 commits discards 1d0e382845 407: onsuccess: #2048: 1: Success after binutils/gcc: 12 commits discards a250963b4f 406: onsuccess: #2047: 1: Success after binutils/gcc: 2 commits discards 6219026028 405: onsuccess: #2046: 1: Success after gcc: 2 commits discards 7f71ffa2aa 404: onsuccess: #2045: 1: Success after binutils/gcc: 8 commits discards 601e03a6b7 403: onsuccess: #2044: 1: Success after binutils/gcc: 2 commits discards cc7fb6382a 402: onsuccess: #2043: 1: Success after basepoints/gcc-13-45 [...] discards e1fca65572 401: onsuccess: #2042: 1: Success after binutils/gcc: 11 commits discards 5981390ce5 400: onsuccess: #2041: 1: Success after binutils/gcc: 8 commits discards 5998002728 399: onsuccess: #2040: 1: Success after binutils/gcc: 3 commits discards 6191057347 398: onsuccess: #2039: 1: Success after binutils/gcc: 4 commits discards 7a7c567bb8 397: onsuccess: #2038: 1: Success after binutils/gcc: 12 commits discards 949e1fa6ad 396: onsuccess: #2037: 1: Success after binutils/gcc: 22 commits discards 294a1b3378 395: onsuccess: #2035: 1: Success after gcc: 4 commits discards 5698d89686 394: onsuccess: #2034: 1: Success after binutils/gcc: 4 commits discards bec988b19e 393: onsuccess: #2033: 1: Success after binutils/gcc: 9 commits discards b4b8700e7a 392: onsuccess: #2032: 1: Success after binutils/gcc: 6 commits new 31b19136c5 392: onsuccess: #2032: 1: Success after binutils/gcc: 6 commits new bb6155a06e 393: onsuccess: #2033: 1: Success after binutils/gcc: 9 commits new 4b571fd021 394: onsuccess: #2034: 1: Success after binutils/gcc: 4 commits new bc1903b11c 395: onsuccess: #2035: 1: Success after gcc: 4 commits new cacccc2690 396: onsuccess: #2037: 1: Success after binutils/gcc: 22 commits new e460ea0d50 397: onsuccess: #2038: 1: Success after binutils/gcc: 12 commits new 82206a5bd4 398: onsuccess: #2039: 1: Success after binutils/gcc: 4 commits new 583dc24c55 399: onsuccess: #2040: 1: Success after binutils/gcc: 3 commits new 75511ccb2d 400: onsuccess: #2041: 1: Success after binutils/gcc: 8 commits new 7826c2064e 401: onsuccess: #2042: 1: Success after binutils/gcc: 11 commits new bb2c8e03c7 402: onsuccess: #2043: 1: Success after basepoints/gcc-13-45 [...] new 4c134c88f6 403: onsuccess: #2044: 1: Success after binutils/gcc: 2 commits new c3f0184641 404: onsuccess: #2045: 1: Success after binutils/gcc: 8 commits new 450f3b44c7 405: onsuccess: #2046: 1: Success after gcc: 2 commits new adc777e438 406: onsuccess: #2047: 1: Success after binutils/gcc: 2 commits new 7070dc695f 407: onsuccess: #2048: 1: Success after binutils/gcc: 12 commits new bd17bebbae 408: onsuccess: #2049: 1: Success after binutils/gcc: 26 commits new c7a4578a87 409: onsuccess: #2050: 1: Success after binutils/gcc: 6 commits new e0849b718c 410: onsuccess: #2051: 1: Success after binutils/gcc: 5 commits new fa668127a7 411: onsuccess: #2052: 1: Success after binutils/gcc: 6 commits new 686b521e3d 412: onsuccess: #2053: 1: Success after binutils/gcc: 53 commits new d697a3b8cc 413: onsuccess: #2054: 1: Success after binutils/gcc: 10 commits new f8a1af2dde 414: onsuccess: #2055: 1: Success after binutils/gcc: 12 commits new 62e98548e0 415: onsuccess: #2056: 1: Success after binutils/gcc: 10 commits new 9e5a2752b5 416: onsuccess: #2057: 1: Success after binutils/gcc: 17 commits new 18836720b0 417: onsuccess: #2058: 1: Success after gcc: 7 commits new e836c09d1c 418: onsuccess: #2059: 1: Success after binutils/gcc: 2 commits new b98af39510 419: onsuccess: #2060: 1: Success after gcc: 3 commits new 6c4724a8f4 420: onsuccess: #2061: 1: Success after binutils/gcc: 13 commits new a72e26b54a 421: onsuccess: #2062: 1: Success after binutils/gcc: 15 commits new 5a6be50d11 422: onsuccess: #2063: 1: Success after binutils/gcc: 6 commits new b87538ebb5 423: onsuccess: #2065: 1: Success after binutils/gcc: 21 commits new 4cd5773d02 424: onsuccess: #2066: 1: Success after gcc: 11 commits new f231493142 425: onsuccess: #2067: 1: Success after binutils/gcc: 5 commits new e471756e3d 426: onsuccess: #2068: 1: Success after binutils: 9 commits new 47c5c44f64 427: onsuccess: #2069: 1: Success after basepoints/gcc-13-47 [...] new 2a49695394 428: onsuccess: #2070: 1: Success after basepoints/gcc-13-47 [...] new ffb11f3768 429: onsuccess: #2071: 1: Success after binutils/gcc: 5 commits new 3c0d97aefe 430: onsuccess: #2072: 1: Success after binutils/gcc: 3 commits new 9df6287657 431: onsuccess: #2073: 1: Success after basepoints/gcc-13-47 [...] new f268a67ca1 432: onsuccess: #2074: 1: Success after binutils/gcc: 2 commits new 047f68e81c 433: onsuccess: #2075: 1: Success after binutils/gcc: 16 commits new dd75ffc850 434: onsuccess: #2076: 1: Success after binutils/gcc: 30 commits new 53ec2eb45a 435: onsuccess: #2077: 1: Success after gcc: 5 commits new f1649b0d49 436: onsuccess: #2078: 1: Success after binutils/gcc: 6 commits new f2c68f6bfc 437: onsuccess: #2079: 1: Success after binutils/gcc: 4 commits new 230e7f29bb 438: onsuccess: #2080: 1: Success after gcc: 3 commits new b99439d8ac 439: onsuccess: #2081: 1: Success after binutils/gcc: 4 commits new 1e854a10dc 440: onsuccess: #2082: 1: Success after binutils/gcc: 11 commits new d7738de152 441: onsuccess: #2083: 1: Success after binutils/gcc: 38 commits new c6d0877030 442: onsuccess: #2084: 1: Success after binutils/gcc: 12 commits new 5883d093f0 443: onsuccess: #2085: 1: Success after binutils/gcc: 4 commits new 123d994a8e 444: onsuccess: #2086: 1: Success after binutils/gcc: 12 commits new 353eb582c2 445: onsuccess: #2087: 1: Success after binutils/gcc: 15 commits new ef78602c20 446: onsuccess: #2088: 1: Success after binutils/gcc: 6 commits new 231fc18651 447: onsuccess: #2089: 1: Success after binutils/gcc: 10 commits new fc46618df3 448: onsuccess: #2090: 1: Success after binutils/gcc: 28 commits new dbd015cfd6 449: onsuccess: #2091: 1: Success after binutils/gcc: 29 commits new 811334e701 450: onsuccess: #2092: 1: Success after binutils/gcc: 28 commits new 9275ff0c1f 451: onsuccess: #2093: 1: Success after binutils/gcc: 4 commits new 82f227dc63 452: onsuccess: #2094: 1: Success after binutils/gcc: 4 commits new 2a3b894861 453: onsuccess: #2095: 1: Success after gdb-13-branchpoint-1 [...] new e67cc07eb5 454: onsuccess: #2096: 1: Success after gcc: 4 commits new afc5bc733f 455: onsuccess: #2097: 1: Success after binutils/gcc: 11 commits new 6d5bf5a4b5 456: onsuccess: #2098: 1: Success after binutils: 10 commits new dae700666e 457: onsuccess: #2099: 1: Success after binutils/gcc: 2 commits new b9c39ab2a3 458: onsuccess: #2100: 1: Success after gdb-13-branchpoint-1 [...] new 57000463c0 459: onsuccess: #2101: 1: Success after binutils/gcc: 3 commits new add1f934f7 460: onsuccess: #2102: 1: Success after binutils: 2 commits new e7847ed48d 461: onsuccess: #2103: 1: Success after binutils/gcc: 2 commits new 8cbec1c770 462: onsuccess: #2104: 1: Success after binutils/gcc: 2 commits new d8f249b44f 463: onsuccess: #2105: 1: Success after binutils/gcc: 10 commits new 04a4b20321 464: onsuccess: #2106: 1: Success after gcc: 9 commits new af4ceb3dbe 465: onsuccess: #2107: 1: Success after binutils/gcc: 6 commits new 1c49ab4c63 466: onsuccess: #2108: 1: Success after binutils/gcc: 5 commits new 7f569f83f3 467: onsuccess: #2109: 1: Success after gcc: 2 commits new 42044d9bb6 468: onsuccess: #2110: 1: Success after gdb-13-branchpoint-2 [...] new 1ffbbc219a 469: onsuccess: #2111: 1: Success after binutils/gcc: 3 commits new 36d1aa23da 470: onsuccess: #2112: 1: Success after binutils/gcc: 2 commits new 0119a3f847 471: onsuccess: #2113: 1: Success after gdb-13-branchpoint-2 [...] new ee2bd7aa63 472: onsuccess: #2114: 1: Success after gcc: 17 commits new d910e01457 473: onsuccess: #2115: 1: Success after binutils/gcc: 3 commits new 7e315314a3 474: onsuccess: #2116: 1: Success after binutils/gcc: 8 commits new c9ec23feca 475: onsuccess: #2117: 1: Success after binutils/gcc: 2 commits new 80f28e4e8b 476: onsuccess: #2118: 1: Success after binutils: 9 commits new 5e3523a6f5 477: onsuccess: #2119: 1: Success after binutils/gcc: 5 commits new 6691a8197b 478: onsuccess: #2120: 1: Success after basepoints/gcc-13-49 [...] new 69dd35ca1f 479: onsuccess: #2121: 1: Success after binutils/gcc: 3 commits new 3cced8886c 480: onsuccess: #2122: 1: Success after basepoints/gcc-13-49 [...] new 4e5544576b 481: onsuccess: #2123: 1: Success after binutils/gcc: 8 commits new 4c5ad42bb5 482: onsuccess: #2124: 1: Success after binutils/gcc: 7 commits new 849fb41fde 483: onsuccess: #2125: 1: Success after binutils/gcc: 5 commits new 8a7e855bd2 484: onsuccess: #2126: 1: Success after binutils/gcc: 6 commits new edb3b22795 485: onsuccess: #2127: 1: Success after binutils/gcc: 7 commits new 6902ded0e3 486: onsuccess: #2128: 1: Success after binutils/gcc: 2 commits new 6c3a8d41ca 487: onsuccess: #2129: 1: Success after binutils/gcc: 16 commits new 5d84b84809 488: onsuccess: #2130: 1: Success after binutils/gcc: 17 commits new e680e7fd6a 489: onsuccess: #2131: 1: Success after binutils/gcc: 24 commits new 9902aaf6f4 490: onsuccess: #2132: 1: Success after binutils/gcc: 4 commits new 5fca00f4fb 491: onsuccess: #2133: 1: Success after binutils/gcc: 7 commits new fbb6f5bc6d 492: onsuccess: #2134: 1: Success after binutils/gcc: 4 commits new 7f86e58efc 493: onsuccess: #2135: 1: Success after binutils/gcc: 17 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 (52d74b38df) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (7f [...] 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 1716 -> 1916 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 53132 -> 53212 bytes 04-build_abe-gcc/console.log.xz | Bin 239056 -> 239640 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3888 bytes 06-build_abe-check_gcc/console.log.xz | Bin 3356 -> 2592 bytes 07-check_regression/console.log.xz | Bin 4892 -> 5012 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 72 +- 08-update_baseline/console.log | 40 +- 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 +- sumfiles/g++.log.xz | Bin 2879440 -> 2835112 bytes sumfiles/g++.sum | 128 +- sumfiles/gcc.log.xz | Bin 2456476 -> 2469892 bytes sumfiles/gcc.sum | 5076 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 906820 -> 921020 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2168 -> 2176 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 217240 -> 217208 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2552 -> 2532 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 469024 -> 477028 bytes sumfiles/libstdc++.sum | 10 +- 31 files changed, 2706 insertions(+), 2734 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_eabi_stm32/gnu_eabi-master-arm_eabi-coremark-O3 updated (2f36886651 -> d65e7bbc89)

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_bmk_gnu_eabi_stm32/gnu_eabi-master-arm_eabi-coremark-O3 in repository toolchain/ci/base-artifacts. from 2f36886651 28: onsuccess: #349: 1: [TCWG CI] No change after binutils/g [...] new d65e7bbc89 29: onsuccess: #1: 1: [TCWG CI] No change after binutils/gcc [...] 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 1816 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31780 -> 31784 bytes 04-build_abe-stage1/console.log.xz | Bin 89752 -> 90328 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-newlib/console.log.xz | Bin 15200 -> 15176 bytes 07-build_abe-stage2/console.log.xz | Bin 165120 -> 164960 bytes 08-benchmark/benchmark-build.log | 94 ++++++++++----------- 08-benchmark/benchmark.log | 92 ++++++++++---------- 08-benchmark/console.log.xz | Bin 3820 -> 3804 bytes 09-check_regression/console.log.xz | Bin 4452 -> 4800 bytes 09-check_regression/results-vs-first.log | 80 +++++++++--------- 09-check_regression/results-vs-prev.log | 82 +++++++++--------- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/Mean/results-metadata.json | 12 +-- .../squad-vs-first/coremark/results-metadata.json | 12 +-- dashboard/squad-vs-first/dashboard-push-squad.sh | 14 +-- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/newlib_rev | 2 +- mail/jira-body.txt | 27 +++--- mail/mail-body.txt | 27 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++---- results_id | 2 +- 25 files changed, 242 insertions(+), 240 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-arm updated (ef8b91e28f -> 3d559f17b8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_build/master-arm in repository toolchain/ci/base-artifacts. discards ef8b91e28f 163: onsuccess: #586: 6: Success after binutils/gcc/linux/gl [...] discards 324b18bbe8 162: onsuccess: #579: 6: Success after gcc: 11 commits discards 607c75373d 161: onsuccess: #578: 6: Success after binutils: 15 commits discards 4ef6f89af9 160: onsuccess: #576: 6: Success after binutils/gcc/linux/gd [...] discards 1c7fc9c7b6 159: onsuccess: #575: 6: Success after binutils/gcc/linux/gd [...] discards d6744fa12a 158: onsuccess: #574: 6: Success after binutils/gcc/linux/gl [...] discards ea80b32a1e 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits discards 66c9c13971 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 commits discards f65aa91cd4 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 commits discards 2981976394 154: onsuccess: #570: 6: Success after binutils/gcc/linux/gd [...] discards 5d961f992a 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 commits discards 90ce5a7781 152: onsuccess: #568: 6: Success after binutils/gcc/linux/gd [...] discards bbb1d8862a 151: onsuccess: #567: 6: Success after binutils/gcc/linux/gl [...] discards d6548d76a0 150: onsuccess: #566: 6: Success after binutils/gcc/linux/gl [...] discards 49e4902ebf 149: onsuccess: #565: 6: Success after binutils/gcc/linux/gl [...] discards 3222e34665 148: onsuccess: #564: 6: Success after binutils/gcc/linux/gl [...] discards 9433fe3dcd 147: onsuccess: #563: 6: Success after binutils/gcc/linux/gl [...] discards 5d1901551d 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 commits discards 1e7c18f2a9 145: onsuccess: #561: 6: Success after binutils/gcc/linux/gd [...] discards dda8b053d1 144: onsuccess: #560: 6: Success after binutils/gcc/linux/gl [...] discards 7333dd64cd 143: onsuccess: #559: 6: Success after binutils/gcc/linux/gl [...] discards d2bb2b8168 142: onsuccess: #558: 6: Success after binutils/gcc/linux/gl [...] discards 8f26b1b075 141: onsuccess: #557: 6: Success after binutils/gcc/linux/gd [...] discards a1a5284259 140: onsuccess: #556: 6: Success after binutils/gcc/linux/gl [...] discards 7fcb429878 139: onsuccess: #555: 6: Success after binutils/gcc/linux/gd [...] discards 238d9a9a85 138: onsuccess: #554: 6: Success after binutils/gcc/linux/gd [...] discards 5ef6cb01ff 137: onsuccess: #553: 6: Success after binutils/gcc/linux/gl [...] discards d5235edca8 136: onsuccess: #551: 6: Success after binutils/gcc/linux/gl [...] discards b4f1673254 135: onsuccess: #550: 6: Success after binutils/gcc/linux/gl [...] discards d15813a23b 134: onsuccess: #544: 6: Success after binutils: 18 commits discards 2269831db5 133: onsuccess: #542: 6: Success after binutils/gcc/linux/gd [...] discards 98c6306430 132: onsuccess: #541: 6: Success after binutils/gcc/linux/gl [...] discards 0c943efdc3 131: onsuccess: #540: 6: Success after binutils/gcc/linux/gd [...] discards 6a4732c987 130: onsuccess: #539: 6: Success after binutils/gcc/linux/gl [...] discards 5206e42753 129: onsuccess: #538: 6: Success after binutils/gcc/linux/gl [...] discards 88d624d426 128: onsuccess: #537: 6: Success after binutils/gcc/linux/gl [...] discards d3fed674e9 127: onsuccess: #536: 6: Success after binutils/gcc/linux/gd [...] discards 62f5077e92 126: onsuccess: #535: 6: Success after binutils/gcc/linux/gd [...] discards 53777db206 125: onsuccess: #534: 6: Success after binutils/gcc/linux/gd [...] discards 39b0403314 124: onsuccess: #533: 6: Success after binutils/gcc/linux/gd [...] discards 99bc2212c6 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 commits discards eee1915102 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 commits discards f58cbeb59e 121: onsuccess: #530: 6: Success after binutils/gcc/linux/gl [...] discards 7376e6fa59 120: onsuccess: #529: 6: Success after binutils/gcc/linux/gd [...] discards c5fa5c7aea 119: onsuccess: #528: 6: Success after binutils/gcc/linux/gd [...] discards 45505ba97f 118: onsuccess: #527: 6: Success after binutils/gcc/linux/gl [...] discards a4e2ac3b20 117: onsuccess: #526: 6: Success after binutils/gcc/linux/gd [...] discards cca18be4ea 116: onsuccess: #525: 6: Success after binutils/gcc/linux/gd [...] discards 1ef4f9086b 115: onsuccess: #524: 6: Success after binutils/gcc/linux/gl [...] discards 1c664d1620 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits discards 734e0fb994 113: onsuccess: #522: 1: Success after gcc: 12 commits discards 9ba3d75c1c 112: force: #521: 1: Failure after basepoints/gcc-13-3918-gb [...] discards d84539ec73 111: force: #520: 6: Success after gcc: 9 commits discards b96d8caeb1 110: onsuccess: #518: 6: Success after binutils: 5 commits discards 0e245a1035 109: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] discards 6cbca35d75 108: onsuccess: #514: 6: Success after binutils/gcc/linux/gl [...] discards 48e084f6d0 107: onsuccess: #513: 6: Success after binutils/gcc/linux/gl [...] discards 0cb49dfb2c 106: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] discards 505b73d9a5 105: onsuccess: #511: 6: Success after binutils/gcc/linux/gd [...] discards 9d2c29508b 104: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] discards a924330682 103: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] discards bfcac221f6 102: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] discards 2e24276b7b 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] discards 6736813bc5 100: onsuccess: #506: 4: Success after baseline build: no ne [...] discards 1bbd1fb88e 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] discards b44f8f20ea 98: force: #504: 6: Success after gcc: 18 commits discards 85fa9367d6 97: onsuccess: #503: 6: Success after linux: 11 commits discards 84b0fc95af 96: onsuccess: #502: 6: Success after glibc: 10 commits discards 3a241f5aca 95: onsuccess: #500: 6: Success after binutils: 8 commits discards 0a957ac4da 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] discards 5760fd67de 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] discards ce102a8836 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] discards 1f68ca08fa 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] discards f9dad680c8 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] discards f0965bee01 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] discards 9188d244a7 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] discards 7f0b46d67a 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] discards be6fa0f049 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] discards d3ac9a3827 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] discards 0fad3b7bc7 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] discards dc15065efc 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] discards 11cade7e3c 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] discards aef585dbd7 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] discards 44fcff8b25 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] discards e1e1146f3a 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] discards 9b92f14e02 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] discards 5ec153f09a 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] discards b0d055d87d 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gli [...] discards d6c3665bea 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gli [...] discards 31fc6d7ab2 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] discards b53af53346 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] discards ed0523c8fd 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] discards e75890d278 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gdb [...] discards 0227f49710 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] discards 8200f50faa 69: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] discards 981641af70 68: onsuccess: #471: 6: Success after binutils/gcc/linux/gli [...] discards ea20732263 67: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] discards 636f91d05c 66: onsuccess: #469: 6: Success after binutils/gcc/linux/gli [...] discards 96e7a85f88 65: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] discards 33beda7f57 64: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] discards 8c63126916 63: onsuccess: #466: 6: Success after binutils/gcc/linux/gli [...] new 6730adc087 63: onsuccess: #466: 6: Success after binutils/gcc/linux/gli [...] new 35ea6a61c2 64: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] new e019c0aa14 65: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] new cc730df9cf 66: onsuccess: #469: 6: Success after binutils/gcc/linux/gli [...] new cd995bcc71 67: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] new db9bd03667 68: onsuccess: #471: 6: Success after binutils/gcc/linux/gli [...] new 88848f5f9f 69: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] new 2210212ae7 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] new dfbf2c7d90 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gdb [...] new e1fa6338a9 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] new 712b68d408 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] new 99b90a1f19 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] new b6b89babd3 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gli [...] new 2a8ef69e6e 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gli [...] new e9f4282fc7 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] new 6d653f1ba5 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] new c1a91c8e86 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] new 50081d6731 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] new 3db27bbbdd 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] new 538caca9ba 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] new 4b75fd4fcb 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] new 7a6133c814 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] new c5678f03aa 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] new 58a349eb44 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] new 371c2ac71e 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] new fa181206ba 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] new 52b7a2a18f 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] new e86a6df181 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] new 20238a7995 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] new 8153d03d61 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] new b228051373 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] new ad0421f7ae 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] new 3e37f051ff 95: onsuccess: #500: 6: Success after binutils: 8 commits new d29266ce97 96: onsuccess: #502: 6: Success after glibc: 10 commits new 8ec5b289e0 97: onsuccess: #503: 6: Success after linux: 11 commits new 948d9248fb 98: force: #504: 6: Success after gcc: 18 commits new e8685880a1 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] new 259298fbdd 100: onsuccess: #506: 4: Success after baseline build: no ne [...] new 605c8de867 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] new 5fe9f3a944 102: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] new 26a465f2b9 103: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] new ebe8cc07ee 104: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] new 45a0612ecc 105: onsuccess: #511: 6: Success after binutils/gcc/linux/gd [...] new 2e533c98d4 106: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] new 2d232dd4f2 107: onsuccess: #513: 6: Success after binutils/gcc/linux/gl [...] new 2bfae72179 108: onsuccess: #514: 6: Success after binutils/gcc/linux/gl [...] new 2d6498ae72 109: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] new 1109fa5310 110: onsuccess: #518: 6: Success after binutils: 5 commits new e6ab1e4ec1 111: force: #520: 6: Success after gcc: 9 commits new 896285c548 112: force: #521: 1: Failure after basepoints/gcc-13-3918-gb [...] new c59d981d09 113: onsuccess: #522: 1: Success after gcc: 12 commits new 44cf55721a 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits new a5dfac53e3 115: onsuccess: #524: 6: Success after binutils/gcc/linux/gl [...] new 37894ff705 116: onsuccess: #525: 6: Success after binutils/gcc/linux/gd [...] new ac77325117 117: onsuccess: #526: 6: Success after binutils/gcc/linux/gd [...] new 594ce3b524 118: onsuccess: #527: 6: Success after binutils/gcc/linux/gl [...] new a694675c68 119: onsuccess: #528: 6: Success after binutils/gcc/linux/gd [...] new aa3410845a 120: onsuccess: #529: 6: Success after binutils/gcc/linux/gd [...] new f8767c8da5 121: onsuccess: #530: 6: Success after binutils/gcc/linux/gl [...] new 0315a74be3 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 commits new ee03ebafc0 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 commits new fac1905482 124: onsuccess: #533: 6: Success after binutils/gcc/linux/gd [...] new d2f24ff44b 125: onsuccess: #534: 6: Success after binutils/gcc/linux/gd [...] new 453f2a4b38 126: onsuccess: #535: 6: Success after binutils/gcc/linux/gd [...] new 3356b3df42 127: onsuccess: #536: 6: Success after binutils/gcc/linux/gd [...] new 2a49be1585 128: onsuccess: #537: 6: Success after binutils/gcc/linux/gl [...] new efe3540fb1 129: onsuccess: #538: 6: Success after binutils/gcc/linux/gl [...] new 66714fef13 130: onsuccess: #539: 6: Success after binutils/gcc/linux/gl [...] new 689b990cec 131: onsuccess: #540: 6: Success after binutils/gcc/linux/gd [...] new 8ec2da0864 132: onsuccess: #541: 6: Success after binutils/gcc/linux/gl [...] new fa44732a5e 133: onsuccess: #542: 6: Success after binutils/gcc/linux/gd [...] new 73caebf529 134: onsuccess: #544: 6: Success after binutils: 18 commits new 5efabc0c6e 135: onsuccess: #550: 6: Success after binutils/gcc/linux/gl [...] new f9c2d2e4c2 136: onsuccess: #551: 6: Success after binutils/gcc/linux/gl [...] new 94b90f530a 137: onsuccess: #553: 6: Success after binutils/gcc/linux/gl [...] new be9b77fea8 138: onsuccess: #554: 6: Success after binutils/gcc/linux/gd [...] new 7af1cf2452 139: onsuccess: #555: 6: Success after binutils/gcc/linux/gd [...] new d24e407587 140: onsuccess: #556: 6: Success after binutils/gcc/linux/gl [...] new 81624b59c9 141: onsuccess: #557: 6: Success after binutils/gcc/linux/gd [...] new e97bd54e24 142: onsuccess: #558: 6: Success after binutils/gcc/linux/gl [...] new 03c201d467 143: onsuccess: #559: 6: Success after binutils/gcc/linux/gl [...] new e92eb28c90 144: onsuccess: #560: 6: Success after binutils/gcc/linux/gl [...] new 073478f9d1 145: onsuccess: #561: 6: Success after binutils/gcc/linux/gd [...] new 7dfc7dbcb2 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 commits new 1603febeef 147: onsuccess: #563: 6: Success after binutils/gcc/linux/gl [...] new 6342ecb794 148: onsuccess: #564: 6: Success after binutils/gcc/linux/gl [...] new 0a0c0cbcba 149: onsuccess: #565: 6: Success after binutils/gcc/linux/gl [...] new 17970dcbde 150: onsuccess: #566: 6: Success after binutils/gcc/linux/gl [...] new 0accefa4e2 151: onsuccess: #567: 6: Success after binutils/gcc/linux/gl [...] new 24b5bc99bb 152: onsuccess: #568: 6: Success after binutils/gcc/linux/gd [...] new c76fc31ae7 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 commits new 18ed097160 154: onsuccess: #570: 6: Success after binutils/gcc/linux/gd [...] new 1d203a5169 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 commits new 4134de5917 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 commits new 68c79cfe78 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits new 744e1f8d2d 158: onsuccess: #574: 6: Success after binutils/gcc/linux/gl [...] new e7277609fc 159: onsuccess: #575: 6: Success after binutils/gcc/linux/gd [...] new 50492fe2e9 160: onsuccess: #576: 6: Success after binutils/gcc/linux/gd [...] new 2bc614e4ca 161: onsuccess: #578: 6: Success after binutils: 15 commits new a69866e0dc 162: onsuccess: #579: 6: Success after gcc: 11 commits new 9c8ea5ec17 163: onsuccess: #586: 6: Success after binutils/gcc/linux/gl [...] new 3d559f17b8 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/gd [...] 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 (ef8b91e28f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...] 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 1792 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2772 bytes 04-build_abe-binutils/console.log.xz | Bin 53716 -> 53516 bytes 05-build_abe-gcc/console.log.xz | Bin 241260 -> 239540 bytes 07-build_abe-linux/console.log.xz | Bin 8836 -> 8932 bytes 08-build_abe-glibc/console.log.xz | Bin 235976 -> 237492 bytes 09-build_abe-gdb/console.log.xz | Bin 52296 -> 52260 bytes 10-check_regression/console.log.xz | Bin 4524 -> 3968 bytes 11-update_baseline/console.log | 40 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++-------------- 18 files changed, 44 insertions(+), 44 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits January 2023