Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[gcc] branch devel/modula-2 updated (5a359399d8f -> d5d3e57d33b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch devel/modula-2 in repository gcc. from 5a359399d8f Remove ServerSocket.def and ServerSocket.mod new d5d3e57d33b Python3 detected in gcc/configure.ac, python3 modules insta [...] 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/aclocal.m4 | 286 --------------------------------------------------- gcc/configure | 236 ++++++++---------------------------------- gcc/configure.ac | 14 ++- gcc/doc/install.texi | 49 +++++++-- gcc/m2/Make-lang.in | 27 +++-- 5 files changed, 114 insertions(+), 498 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-arm updated (d1f90251c30 -> 0861f3fea3e)

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 d1f90251c30 139: onsuccess: #555: 6: Success after binutils/gcc/linux/g [...] discards d58c64b0d64 138: onsuccess: #554: 6: Success after binutils/gcc/linux/g [...] discards afc8291e7e7 137: onsuccess: #553: 6: Success after binutils/gcc/linux/g [...] discards 2c65ec89b7d 136: onsuccess: #551: 6: Success after binutils/gcc/linux/g [...] discards 1bdcbeef5ca 135: onsuccess: #550: 6: Success after binutils/gcc/linux/g [...] discards 418f6506fbf 134: onsuccess: #544: 6: Success after binutils: 18 commits discards eab9d58f52f 133: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] discards 45543685c42 132: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] discards 4dfe2008800 131: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] discards 818b8234902 130: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] discards efe7d993fcb 129: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] discards c24c5a15bcd 128: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] discards fa4d9448461 127: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] discards 94acbe1d194 126: onsuccess: #535: 6: Success after binutils/gcc/linux/g [...] discards 0283661e187 125: onsuccess: #534: 6: Success after binutils/gcc/linux/g [...] discards bf0ed85207b 124: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] discards e7256569d86 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 [...] discards 6e15100fd93 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 [...] discards 9ef02c844c6 121: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] discards 66c25a0588f 120: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] discards 9558b66ab6b 119: onsuccess: #528: 6: Success after binutils/gcc/linux/g [...] discards 12c925461a9 118: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] discards 1d1b8b1afeb 117: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] discards e6d27b97fee 116: onsuccess: #525: 6: Success after binutils/gcc/linux/g [...] discards 308db249a93 115: onsuccess: #524: 6: Success after binutils/gcc/linux/g [...] discards 83dbe6e483b 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits discards 3d8787c69dc 113: onsuccess: #522: 1: Success after gcc: 12 commits discards cf7551fc866 112: force: #521: 1: Failure after basepoints/gcc-13-3918-g [...] discards fdd055f8d98 111: force: #520: 6: Success after gcc: 9 commits discards 736e33a8b33 110: onsuccess: #518: 6: Success after binutils: 5 commits discards 24218292342 109: onsuccess: #516: 6: Success after binutils/gcc/linux/g [...] discards b67daa5c219 108: onsuccess: #514: 6: Success after binutils/gcc/linux/g [...] discards 9dd09d6add9 107: onsuccess: #513: 6: Success after binutils/gcc/linux/g [...] discards 3ba371a28ff 106: onsuccess: #512: 6: Success after binutils/gcc/linux/g [...] discards c53ac7c0020 105: onsuccess: #511: 6: Success after binutils/gcc/linux/g [...] discards bcdcd85c5d9 104: onsuccess: #510: 6: Success after binutils/gcc/linux/g [...] discards 2672318b48c 103: onsuccess: #509: 6: Success after binutils/gcc/linux/g [...] discards d7f9ee7bd1d 102: onsuccess: #508: 6: Success after binutils/gcc/linux/g [...] discards 141fb9ddcb6 101: onsuccess: #507: 4: Success after binutils/gcc/linux/g [...] discards 2b7aec214b7 100: onsuccess: #506: 4: Success after baseline build: no n [...] discards bf4b0c6662e 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge [...] discards f1984de3a24 98: force: #504: 6: Success after gcc: 18 commits discards a205182c635 97: onsuccess: #503: 6: Success after linux: 11 commits discards 840fb45b858 96: onsuccess: #502: 6: Success after glibc: 10 commits discards fe2e9d8a392 95: onsuccess: #500: 6: Success after binutils: 8 commits discards a076e6bd10c 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gl [...] discards 8ba72ce07e8 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gd [...] discards 3d8e87d337e 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gl [...] discards 4e7ca93b869 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gl [...] discards 0c7f114f9b2 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gl [...] discards 002974ab7da 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gl [...] discards 822f27e9774 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gl [...] discards 65827990a81 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gd [...] discards bc11e819ab5 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gd [...] discards 701952c35da 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gl [...] discards c356d17deb3 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gd [...] discards f35c7b36959 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gl [...] discards 799ad3740df 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gl [...] discards 601c0ba00a0 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gl [...] discards 80ad0e12c7a 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gd [...] discards fc9d9920f9e 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gl [...] discards 3c016efa163 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gl [...] discards cacef0dd1fa 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gl [...] discards 5317cdf089d 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gl [...] discards 45cabd8806d 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gl [...] discards 2f354761e88 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gl [...] discards 48d473ae478 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gl [...] discards 3801eadf513 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gl [...] discards 8e2d2641691 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gd [...] discards 7e0d2cce30c 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gl [...] discards 2bed4bde94c 69: onsuccess: #472: 6: Success after binutils/gcc/linux/gl [...] discards fc14b60e4a4 68: onsuccess: #471: 6: Success after binutils/gcc/linux/gl [...] discards 5631a0fb0b1 67: onsuccess: #470: 6: Success after binutils/gcc/linux/gl [...] discards b388c297bfc 66: onsuccess: #469: 6: Success after binutils/gcc/linux/gl [...] discards 4e302e05469 65: onsuccess: #468: 6: Success after binutils/gcc/linux/gl [...] discards ab2d240f982 64: onsuccess: #467: 6: Success after binutils/gcc/linux/gl [...] discards e73164e7832 63: onsuccess: #466: 6: Success after binutils/gcc/linux/gl [...] discards 99521e5b791 62: onsuccess: #465: 1: Success after binutils/gcc: 27 commits discards 9005dd205ae 61: onsuccess: #464: 1: Success after binutils/gcc: 30 commits discards b51adc04932 60: onsuccess: #463: 1: Success after gcc: 10 commits discards 0a53874cd28 59: force: #462: 1: Failure after basepoints/gcc-13-2871-g1 [...] discards c2f98422db4 58: force: #461: 6: Success after gcc: 29 commits discards c96dbe39511 57: onsuccess: #459: 6: Success after binutils: 8 commits discards 6849dac8683 56: onsuccess: #457: 6: Success after binutils/gcc/linux/gd [...] discards dfe8a4c04a0 55: onsuccess: #456: 6: Success after binutils/gcc/linux/gd [...] discards b396c291593 54: onsuccess: #455: 6: Success after binutils/gcc/linux/gl [...] discards f1cdc1cb9df 53: onsuccess: #454: 6: Success after binutils/gcc/glibc/gd [...] discards a2a80a64e5f 52: onsuccess: #453: 6: Success after binutils/gcc/linux/gl [...] discards c2a01fa5602 51: onsuccess: #452: 6: Success after binutils/gcc/glibc/gd [...] discards 9bda6e2ef3b 50: onsuccess: #451: 6: Success after binutils/gcc/linux/gl [...] discards ea74abeab59 49: onsuccess: #450: 6: Success after binutils/gcc/linux/gl [...] discards c8360b5a906 48: onsuccess: #449: 6: Success after binutils/gcc/linux/gl [...] discards 27fdd134498 47: onsuccess: #448: 4: Success after binutils/gcc/linux/gl [...] discards 01a074c09bd 46: onsuccess: #447: 4: Success after binutils/gcc: 19 commits discards 2084fb08706 45: onsuccess: #446: 4: Success after gcc: 13 commits discards f5985c12b3e 44: force: #445: 4: Failure after basepoints/gcc-13-2658-g6 [...] discards 1013743509d 43: force: #444: 6: Success after gcc: 5 commits discards 5b848ca6702 42: onsuccess: #443: 6: Success after v6.0-rc5-25-g3245cb65 [...] discards c29daa84425 41: onsuccess: #442: 6: Success after glibc: 3 commits discards 720fdb8577c 40: onsuccess: #440: 6: Success after binutils: 11 commits discards dd03bdc85e3 39: onsuccess: #438: 6: Success after binutils/gcc/linux/gl [...] new 025ba42c106 39: onsuccess: #438: 6: Success after binutils/gcc/linux/gl [...] new 47c2f836dbc 40: onsuccess: #440: 6: Success after binutils: 11 commits new fc05cf987ca 41: onsuccess: #442: 6: Success after glibc: 3 commits new aee860b9ab6 42: onsuccess: #443: 6: Success after v6.0-rc5-25-g3245cb65 [...] new bf71e4bc201 43: force: #444: 6: Success after gcc: 5 commits new 1004a1ca2dd 44: force: #445: 4: Failure after basepoints/gcc-13-2658-g6 [...] new 1aecaecb9b2 45: onsuccess: #446: 4: Success after gcc: 13 commits new 9162b27162f 46: onsuccess: #447: 4: Success after binutils/gcc: 19 commits new b4ac4052ad1 47: onsuccess: #448: 4: Success after binutils/gcc/linux/gl [...] new 9ee5d824f26 48: onsuccess: #449: 6: Success after binutils/gcc/linux/gl [...] new 9a97015a2d9 49: onsuccess: #450: 6: Success after binutils/gcc/linux/gl [...] new 290afec9d30 50: onsuccess: #451: 6: Success after binutils/gcc/linux/gl [...] new 38a892f2127 51: onsuccess: #452: 6: Success after binutils/gcc/glibc/gd [...] new 522f6a2841e 52: onsuccess: #453: 6: Success after binutils/gcc/linux/gl [...] new 2272be55a95 53: onsuccess: #454: 6: Success after binutils/gcc/glibc/gd [...] new ac9d6a43b48 54: onsuccess: #455: 6: Success after binutils/gcc/linux/gl [...] new b1623cbed97 55: onsuccess: #456: 6: Success after binutils/gcc/linux/gd [...] new 0436e77ec66 56: onsuccess: #457: 6: Success after binutils/gcc/linux/gd [...] new 00e48cf2dfd 57: onsuccess: #459: 6: Success after binutils: 8 commits new 771d36640f8 58: force: #461: 6: Success after gcc: 29 commits new dc5b9de9948 59: force: #462: 1: Failure after basepoints/gcc-13-2871-g1 [...] new a86293dc218 60: onsuccess: #463: 1: Success after gcc: 10 commits new 65d20a7dbb7 61: onsuccess: #464: 1: Success after binutils/gcc: 30 commits new 40c351420b9 62: onsuccess: #465: 1: Success after binutils/gcc: 27 commits new 9b64b681c34 63: onsuccess: #466: 6: Success after binutils/gcc/linux/gl [...] new cb595baf4d6 64: onsuccess: #467: 6: Success after binutils/gcc/linux/gl [...] new 0e21952cff2 65: onsuccess: #468: 6: Success after binutils/gcc/linux/gl [...] new 1ab0988f558 66: onsuccess: #469: 6: Success after binutils/gcc/linux/gl [...] new dfc9995f598 67: onsuccess: #470: 6: Success after binutils/gcc/linux/gl [...] new 8b7b3267862 68: onsuccess: #471: 6: Success after binutils/gcc/linux/gl [...] new c4c019baf81 69: onsuccess: #472: 6: Success after binutils/gcc/linux/gl [...] new a613e285a1a 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gl [...] new 89a6487f941 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gd [...] new 3d1d9632ee5 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gl [...] new 87f46ae1b61 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gl [...] new 0c4dae89363 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gl [...] new 617deaa7e00 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gl [...] new 0b01b1baf3a 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gl [...] new 049e823e319 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gl [...] new 7576dc634d6 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gl [...] new 4bb393b4f3b 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gl [...] new 993b2636602 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gd [...] new d81e9ee515a 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gl [...] new cc5d0dba9bd 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gl [...] new e249caeaa72 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gl [...] new ec2b521f58f 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gd [...] new 032ce397d1d 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gl [...] new d56e84706bf 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gd [...] new e3765169056 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gd [...] new a61e3b4e818 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gl [...] new d005565fd11 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gl [...] new 80bb8ed6b73 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gl [...] new 4199770e867 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gl [...] new fbb99e01101 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gl [...] new bc364e2fdf6 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gd [...] new 9f2f08c38e3 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gl [...] new af62e41638e 95: onsuccess: #500: 6: Success after binutils: 8 commits new 80c5a74d52e 96: onsuccess: #502: 6: Success after glibc: 10 commits new 5d39f725911 97: onsuccess: #503: 6: Success after linux: 11 commits new fbd00312ed3 98: force: #504: 6: Success after gcc: 18 commits new c4e27993e52 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge [...] new 04f97540288 100: onsuccess: #506: 4: Success after baseline build: no n [...] new 61cd9c3c4f1 101: onsuccess: #507: 4: Success after binutils/gcc/linux/g [...] new d3aeb7075e8 102: onsuccess: #508: 6: Success after binutils/gcc/linux/g [...] new 44823252c35 103: onsuccess: #509: 6: Success after binutils/gcc/linux/g [...] new c1c3225c908 104: onsuccess: #510: 6: Success after binutils/gcc/linux/g [...] new 817f9c396f9 105: onsuccess: #511: 6: Success after binutils/gcc/linux/g [...] new b470fd5da58 106: onsuccess: #512: 6: Success after binutils/gcc/linux/g [...] new aacdcbf0884 107: onsuccess: #513: 6: Success after binutils/gcc/linux/g [...] new fcc7f9750c1 108: onsuccess: #514: 6: Success after binutils/gcc/linux/g [...] new 197a1a6d7c8 109: onsuccess: #516: 6: Success after binutils/gcc/linux/g [...] new 378253d0d58 110: onsuccess: #518: 6: Success after binutils: 5 commits new 4c36cc5233d 111: force: #520: 6: Success after gcc: 9 commits new ba71e3f2376 112: force: #521: 1: Failure after basepoints/gcc-13-3918-g [...] new 9f07742e328 113: onsuccess: #522: 1: Success after gcc: 12 commits new 87bb33331b5 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits new 1c0d656ae3c 115: onsuccess: #524: 6: Success after binutils/gcc/linux/g [...] new 982f6d84617 116: onsuccess: #525: 6: Success after binutils/gcc/linux/g [...] new a503c759f77 117: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] new c730629c665 118: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] new d44e7653686 119: onsuccess: #528: 6: Success after binutils/gcc/linux/g [...] new 3ca25503dfe 120: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] new 6c03b931b0e 121: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] new 6a3987222da 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 [...] new b3cca0c2a33 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 [...] new 2112c42a91a 124: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] new 5bdf67a120c 125: onsuccess: #534: 6: Success after binutils/gcc/linux/g [...] new bf1b49da7c7 126: onsuccess: #535: 6: Success after binutils/gcc/linux/g [...] new 648540088c8 127: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] new e9f7f978078 128: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] new 4dbdf286e78 129: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] new 27c5af951d7 130: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] new a8069437c59 131: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] new 9cf2ac0057c 132: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] new 7142a97980c 133: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] new 739590f0229 134: onsuccess: #544: 6: Success after binutils: 18 commits new ea2498a0681 135: onsuccess: #550: 6: Success after binutils/gcc/linux/g [...] new b94f48a13cb 136: onsuccess: #551: 6: Success after binutils/gcc/linux/g [...] new cc1d6f871c1 137: onsuccess: #553: 6: Success after binutils/gcc/linux/g [...] new 15beb7566be 138: onsuccess: #554: 6: Success after binutils/gcc/linux/g [...] new 4cb979e55eb 139: onsuccess: #555: 6: Success after binutils/gcc/linux/g [...] new 0861f3fea3e 140: onsuccess: #556: 6: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (d1f90251c30) \ 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 1752 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 53132 -> 52792 bytes 05-build_abe-gcc/console.log.xz | Bin 235076 -> 233592 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 8780 -> 9832 bytes 08-build_abe-glibc/console.log.xz | Bin 235236 -> 235520 bytes 09-build_abe-gdb/console.log.xz | Bin 51360 -> 50844 bytes 10-check_regression/console.log.xz | Bin 3920 -> 4332 bytes 11-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 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 ++++++++++---------- 20 files changed, 59 insertions(+), 59 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (f11973bec74 -> caa2fe586e5)

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-aarch64 in repository toolchain/ci/base-artifacts. discards f11973bec74 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 2 [...] discards 7f95ed22c2f 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/ [...] discards 5dfee9bed3d 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards 07cb7c2e58b 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 [...] discards 82958026e0a 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/ [...] discards 70b843a63d6 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 1 [...] discards 0c5363411aa 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/ [...] discards 533cfb1c574 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/ [...] discards 2c86d8a9c10 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/ [...] discards 9984f3c4659 204: onsuccess: #2435: 1: Success after linux: 3 commits discards fe4eaca48a1 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards 458738ae488 202: onsuccess: #2431: 1: Success after linux: 944 commits discards de64e3184e6 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards 2d5a97de336 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 66793b77a13 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/ [...] discards 2ccaf10b216 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/ [...] discards 2329f097bb0 197: onsuccess: #2348: 1: Success after linux: 190 commits discards aac5e5f4389 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 4 [...] discards 49c5adababa 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/ [...] discards a74bf9a8b1c 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/ [...] discards 930e2241de2 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/ [...] discards 76339cdb452 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/ [...] discards 8b3b157902c 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 0142ca99f46 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/ [...] discards 873143d3246 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/ [...] discards 6f9289a284b 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/ [...] discards 11064ad51d1 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/ [...] discards 56dc90c9853 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/ [...] discards e6835c4be69 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/ [...] discards 453925b651d 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/ [...] discards 255108fce39 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/ [...] discards b4bd6413318 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/ [...] discards d788c0ebde8 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/ [...] discards 6703a051d88 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/ [...] discards f9b91ec4492 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/ [...] discards db2d1c9fc63 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] discards c686f98f0a9 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards a90ab92c4c4 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] discards 584a9a2b47d 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] discards b11ecd7918a 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 2 [...] discards 865eb315121 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 7032b68fe47 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] discards 4373f7ff2b3 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/ [...] discards 48d22eca13e 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/ [...] discards 60423b20d70 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/ [...] discards b806c068258 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/ [...] discards 5809413c816 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qem [...] discards 59586691463 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards df986c278f3 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 48d5868b6e3 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/ [...] discards 4d1d79b270d 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/ [...] discards ed773070ddc 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/ [...] discards d816692645c 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/ [...] discards f055ef2fd49 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/ [...] discards c85fba3b6bc 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 19 [...] discards 3b2f9014350 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] discards db51ebeed41 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 [...] discards f02a2c847ae 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/ [...] discards 743b784e5f0 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] discards c28e898ad22 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 1 [...] discards d253a93bf30 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 [...] discards 37468c04b0d 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 [...] discards aeb5edf799d 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 8cf6be61640 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 9b605a16dae 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/ [...] discards 6fb3b09dfe4 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 [...] discards 7df51d4f2e1 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 1 [...] discards a2b3c7950e9 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards c18dc274866 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/ [...] discards 070024aabe9 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/ [...] discards 7964c8a56b9 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qe [...] discards dcb2ed815d3 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 103ef7c5bb6 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 [...] discards 86afab3e34d 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/ [...] discards bd36c560626 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 1 [...] discards f8fdab425c5 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 [...] discards feeb71cced2 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/ [...] discards 9c701d104e6 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qe [...] discards 590003f1c81 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards bfb339de667 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 1 [...] discards facc6ef2343 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/ [...] discards 3a2a55b6b19 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/ [...] discards 4d9fcea5dd7 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 1 [...] discards d5447d5b671 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 3 [...] discards 9c71dabe41d 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/ [...] discards afdddcb615d 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 111ac015d8e 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 752014e7204 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-2 [...] discards 70bd570897a 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/ [...] discards 954b7c70db4 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 45f21164733 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-2 [...] discards c63ebe7bd4e 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 [...] discards 0db75f2a9c3 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/ [...] discards 0c8a8941699 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/ [...] discards 79fb400416f 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/ [...] discards d44619820d5 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/ [...] discards 827b6abff0d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/ [...] discards c83db938101 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 [...] discards 8e1e28a68a1 115: onsuccess: #2147: 1: Success after binutils/linux/glib [...] discards e616b818924 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/ [...] discards 4aed3e71605 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/ [...] new 4a843065c5b 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/ [...] new e337a3caf02 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/ [...] new 4c0e0e786d4 115: onsuccess: #2147: 1: Success after binutils/linux/glib [...] new 85dea889c34 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 [...] new 1f013be07c7 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/ [...] new 7e4f2cd1963 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/ [...] new ee2811866cc 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/ [...] new 5ccd20f5cde 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/ [...] new 78d11216c39 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/ [...] new 08943fe105c 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 [...] new 7cf9c332fe2 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-2 [...] new e6441a4031c 124: onsuccess: #2159: 1: Success after linux: 23 commits new 2967627d594 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/ [...] new 1a6060a5d04 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-2 [...] new e248b7d3f27 127: onsuccess: #2162: 1: Success after gcc: 9 commits new a53a3dc6ff3 128: onsuccess: #2163: 1: Success after linux: 23 commits new 8820ebcb77b 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/ [...] new 7d3a3fae83c 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 3 [...] new 0bda5c13824 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 1 [...] new b4eaabca08a 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/ [...] new 695de868349 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/ [...] new d8a99013d38 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 1 [...] new fc1af76a56d 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new bde1f7c002a 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qe [...] new 1a38bd89153 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/ [...] new 630c2976fa8 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 [...] new 2d269d0f4b2 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 1 [...] new e0088d773cf 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/ [...] new 12432a7d3de 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 [...] new 1823b85860b 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new fdaf5a55394 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qe [...] new 909052b9c7b 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/ [...] new d9f05e5611a 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/ [...] new 96bf8890153 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new e8cd0691172 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 1 [...] new 8ba3df23e8e 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 [...] new c3ba27656ae 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/ [...] new f8b277a3e2b 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 66a1ae08e7a 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 7aea0ccddf2 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 [...] new 93537e1a32e 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 [...] new 07a7f5b8cd0 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 1 [...] new ea89e7f2f0d 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] new 3b8fc0a1d00 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/ [...] new b6be9948f08 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 [...] new 2f8eb6bfd4a 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] new 0685f452544 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 19 [...] new 9b8ebce6658 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/ [...] new 2c074beedd5 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/ [...] new 21ea07cb753 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/ [...] new 3e82084cb57 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/ [...] new 41831e21828 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/ [...] new 197406c0ca2 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 4dd850fa385 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new c88ae3b30de 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qem [...] new 5cbd7a66d84 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/ [...] new dcceb1dac80 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/ [...] new 92e60e78682 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/ [...] new e458335a15a 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/ [...] new 8c82a7b0733 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] new 91b4c0ce462 173: onsuccess: #2208: 1: Success after gcc: 10 commits new ef0d28f3168 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 2 [...] new 234d2a23484 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] new e0fa4ee2289 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] new 6957653c81f 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 5d9fcad780a 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] new c2d1fa12c51 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/ [...] new d502960ad5c 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/ [...] new 1dc29ad4983 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/ [...] new b9ac723b8eb 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/ [...] new 7367d28ecfb 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/ [...] new db19a6eb763 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/ [...] new 480cd956951 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/ [...] new 73274186441 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/ [...] new 8586167ad1f 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/ [...] new 34758462844 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/ [...] new 943aad4ed11 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/ [...] new a85769d7f75 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/ [...] new 6d1a7134eb6 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new ff33bcc956a 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/ [...] new 6eb9fc9b609 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/ [...] new a86ee56d5c9 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/ [...] new df0a2d461a9 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/ [...] new 20252a1eae2 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 4 [...] new 56ce9208649 197: onsuccess: #2348: 1: Success after linux: 190 commits new 3b0337907f1 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/ [...] new 1a26438a462 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/ [...] new 58b0d498061 200: onsuccess: #2427: 1: Success after binutils: 274 commits new e34699d7ef2 201: onsuccess: #2430: 1: Success after glibc: 26 commits new 5b4e1e3f108 202: onsuccess: #2431: 1: Success after linux: 944 commits new 2112e54506a 203: onsuccess: #2433: 1: Success after binutils: 27 commits new 0db6166ea0e 204: onsuccess: #2435: 1: Success after linux: 3 commits new c4d07d55b15 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/ [...] new f5145feae55 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/ [...] new 3b08803a4f4 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/ [...] new 6f043c1ee25 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 1 [...] new 8062960a9a3 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/ [...] new fb7d15067d5 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 [...] new 02889a13630 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new 7cb9e562e7a 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/ [...] new a5827ba62f7 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 2 [...] new caa2fe586e5 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/ [...] 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 (f11973bec74) \ 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 1748 -> 1856 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31784 -> 32092 bytes 04-build_abe-stage1/console.log.xz | Bin 73056 -> 73204 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8324 -> 8324 bytes 07-build_abe-glibc/console.log.xz | Bin 242948 -> 244192 bytes 08-build_abe-stage2/console.log.xz | Bin 204024 -> 204632 bytes 09-build_abe-gdb/console.log.xz | Bin 39056 -> 39184 bytes 10-build_abe-qemu/console.log.xz | Bin 30708 -> 30548 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3040 -> 2956 bytes 13-check_regression/console.log.xz | Bin 13344 -> 13664 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 223 +- 13-check_regression/mail-body.txt | 208 +- 13-check_regression/results.compare | 57 +- 13-check_regression/results.compare2 | 938 ++--- 13-check_regression/results.regressions | 50 +- 14-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 | 210 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 50 +- sumfiles/g++.log.xz | Bin 3407676 -> 3438852 bytes sumfiles/g++.sum | 181 +- sumfiles/gcc.log.xz | Bin 3032436 -> 3009120 bytes sumfiles/gcc.sum | 6037 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1039580 -> 1041668 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 214644 -> 214716 bytes sumfiles/libgomp.sum | 21 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 426580 -> 435248 bytes sumfiles/libstdc++.sum | 20 +- 44 files changed, 4168 insertions(+), 3999 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_O3 updated (8425e705f93 -> 8f334ec8ab4)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_O3 in repository toolchain/ci/base-artifacts. from 8425e705f93 37: onsuccess: #146: 2: Success after binutils/gcc: 8 commits new 8f334ec8ab4 38: onsuccess: #147: 2: Success after binutils/gcc: 16 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 1724 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 51720 -> 52456 bytes 05-build_abe-bootstrap_O3/console.log.xz | Bin 461160 -> 461524 bytes 06-check_regression/console.log.xz | Bin 2752 -> 2808 bytes 07-update_baseline/console.log | 2 +- 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, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[linux] branch master updated (3a28c2c89f4b -> 43686598b557)

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 linux. from 3a28c2c89f4b Merge tag 'unsigned-char-6.2-for-linus' of git://git.kerne [...] new 99b3b837855b pstore/zone: Use GFP_ATOMIC to allocate zone buffer new d85644dc5cf4 pstore: Improve error reporting in case of backend overlap new 8f5de3fd38b7 pstore: Expose kmsg_bytes as a module parameter new 6a14f1982e6b pstore: Inform unregistered backend names as well new 893c5f1de620 efi: pstore: Follow convention for the efi-pstore backend name new 3219122b8cdd pstore/ram: Consolidate kfree() paths new 6daf4e82bd54 pstore/ram: Move pmsg init earlier new 8bd4da0f0626 pstore/ram: Move internal definitions out of kernel-wide include new 06b4e09aab6c pstore/ram: Set freed addresses to NULL new 7d7eca411fa0 MAINTAINERS: Update pstore maintainers new 38b91847c314 pstore: Alert on backend write error new e1fce564900f pstore/ram: Fix error return code in ramoops_probe() new e6b842741b4f pstore: Avoid kcore oops by vmap()ing with VM_IOREMAP new 059c4a341df7 Merge tag 'pstore-v6.2-rc1' of git://git.kernel.org/pub/sc [...] new fc1e3980044f selftests/seccomp: Check CAP_SYS_ADMIN capability in the t [...] new a1140cb215fa seccomp: Move copy_seccomp() to no failure path. new b9069728a70c seccomp: document the "filter_count" field new 667161ba0a1c Merge tag 'seccomp-v6.2-rc1' of git://git.kernel.org/pub/s [...] new 2b5f9dad32ed fs/exec: switch timens when a task gets a new mm new af4fddffbe95 selftests/timens: add a test for vfork+exit new 23a7aea5faf6 ELF uapi: add spaces before '{' new 275498a98b1f exec: Add comments on check_unsafe_exec() fs counting new 8f6e3f9e5a0f binfmt: Fix whitespace issues new bfb4a2b95875 exec: simplify initial stack size expansion new cfc46ca4fdca binfmt_elf: fix documented return value for load_elf_phdrs() new ef20c5139c31 binfmt_elf: simplify error handling in load_elf_phdrs() new dc64cc12bcd1 binfmt_elf: replace IS_ERR() with IS_ERR_VALUE() new cd57e443831d exec: Remove FOLL_FORCE for stack setup new e7f703ff2507 binfmt: Fix error return code in load_elf_fdpic_binary() new 6a46bf558803 binfmt_misc: fix shift-out-of-bounds in check_special_flags new 7fc035058eab Merge tag 'execve-v6.2-rc1' of git://git.kernel.org/pub/sc [...] new 7e8e5cc818bd filelock: WARN_ON_ONCE when ->fl_file and filp don't match new ab1ddef98a71 filelock: new helper: vfs_inode_has_locks new 401a8b8fd5ac filelock: add a new locks_inode_context accessor function new d4e78663f6bc ceph: use locks_inode_context helper new a1fde8ee771f cifs: use locks_inode_context helper new 87f00aba211e ksmbd: use locks_inode_context helper new 98b41ffe0afd lockd: use locks_inode_context helper new 17b985def2a8 nfs: use locks_inode_context helper new 77c67530e1f9 nfsd: use locks_inode_context helper new f2f2494c8aa3 Add process name and pid to locks warning new 73fa58dca802 Merge tag 'locks-v6.2' of git://git.kernel.org/pub/scm/lin [...] new 66283a8f49c0 vsprintf: replace in_irq() with in_hardirq() new fd070e8ceb90 test_printf: Refactor fwnode_pointer() to make it more readable new 7b0592a23e4f printk: fix a typo of comment new 7365df19e8ff printk: use strscpy() to instead of strlcpy() new 0cd7e350abc4 rcu: Make SRCU mandatory new 51f5f78a4f80 srcu: Make Tiny synchronize_srcu() check for readers new 9e409c4778af serial: kgdboc: Lock console list in probe function new d9a4af5690e2 printk: Convert console_drivers list to hlist new 6c4afa79147e printk: Prepare for SRCU console list protection new 114570361246 printk: register_console: use "registered" for variable names new b80ea0e81b39 printk: move @seq initialization to helper new a42427609368 printk: fix setting first seq for consoles new 3860e7c57fd2 um: kmsg_dump: only dump when no output console available new 0fb413ea6460 tty: serial: kgdboc: document console_lock usage new d25a2e748ae1 tty: tty_io: document console_lock usage new 8b5dd40088f7 proc: consoles: document console_lock usage new 4dc64682ad37 printk: introduce console_list_lock new 100bdef2c198 console: introduce wrappers to read/write console flags new 12335446e06f um: kmsg_dumper: use srcu console list iterator new b8ef04be6e19 kdb: use srcu console list iterator new fc956ae0de7f printk: console_flush_all: use srcu console list iterator new eb7f1ed2509c printk: __pr_flush: use srcu console list iterator new 12f1da5fc4c7 printk: console_is_usable: use console_srcu_read_flags new d792db6f6b90 printk: console_unblank: use srcu console list iterator new 87f2e4b7d9e5 printk: console_flush_on_panic: use srcu console list iterator new 8cb15f7f492f printk: console_device: use srcu console list iterator new 1fd4224a6b64 console: introduce console_is_registered() new 452b9b247540 serial_core: replace uart_console_enabled() with uart_cons [...] new de61a1a3a083 tty: nfcon: use console_is_registered() new 794c8e847d04 efi: earlycon: use console_is_registered() new 34d9541edef7 tty: hvc: use console_is_registered() new 6e35d977fa1e tty: serial: earlycon: use console_is_registered() new f5bea480f136 tty: serial: pic32_uart: use console_is_registered() new ad3b7f6141f8 tty: serial: samsung_tty: use console_is_registered() new 4b71a443cb0a tty: serial: xilinx_uartps: use console_is_registered() new 9490b22ab39d usb: early: xhci-dbc: use console_is_registered() new 2c6b4b7065a7 netconsole: avoid CON_ENABLED misuse to track registration new 6f8836756f3c printk, xen: fbfront: create/use safe function for forcing [...] new 7c2af0f634f1 tty: tty_io: use console_list_lock for list synchronization new 28de287a9536 proc: consoles: use console_list_lock for list iteration new 7e537af99774 tty: serial: kgdboc: use srcu console list iterator new 66857443699b tty: serial: kgdboc: use console_list_lock for list traversal new 6193bc90849a tty: serial: kgdboc: synchronize tty_find_polling_driver() [...] new e2b396522836 tty: serial: kgdboc: use console_list_lock to trap exit new 848a9c106625 printk: relieve console_lock of list synchronization duties new ff707dfd79f7 tty: serial: sh-sci: use setup() callback for early console new 5074ffbec67a printk: htmldocs: add missing description new 6b2b0d839aca Merge branch 'rework/console-list-lock' into for-linus new 98d0052d0d9d Merge tag 'printk-for-6.2' of git://git.kernel.org/pub/scm [...] new a8e53869995b mm/slub: remove dead code for debug caches on deactivate_slab() new e8753e416c7e percpu: adjust the value of PERCPU_DYNAMIC_EARLY_SIZE new a0dc161ae773 mm/slub, percpu: correct the calculation of early percpu a [...] new 838de63b1011 mm/slab: move and adjust kernel-doc for kmem_cache_alloc new 4b28ba9eeab4 Merge branch 'slab/for-6.2/cleanups' into slab/for-next new b539ce9f1a31 mm/slab: Annotate kmem_cache_node->list_lock as raw new 14d3eb66e16a Merge branch 'slab/for-6.2/locking' into slab/for-next new 979857ea2dea mm: slub: remove dead and buggy code from sysfs_slab_add() new 1a5ad30b89b4 mm: slub: make slab_sysfs_init() a late_initcall new 7c82b3b308f9 mm: Make failslab writable again new c64b95d3dd02 Merge branch 'slab/for-6.2/slub-sysfs' into slab/for-next new 654058e67b94 tools/vm/slabinfo: indicates the cause of the EACCES error new 1c1aaa3319ab Merge branch 'slab/for-6.2/tools' into slab/for-next new bc29d5bd2ba9 mm/slub: perform free consistency checks before call_rcu new 8b8817630ae8 mm/migrate: make isolate_movable_page() skip slab pages new 130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head new 76537db3b95c Merge branch 'slab/for-6.2/fit_rcu_head' into slab/for-next new 9ce67395f5a0 mm/slub: only zero requested size of buffer for kzalloc wh [...] new 5d1ba3108762 mm: kasan: Extend kasan_metadata_size() to also cover in-o [...] new 946fa0dbf2d8 mm/slub: extend redzone check to extra allocated kmalloc s [...] new 90e9b23a60d5 Merge branch 'slab/for-6.2/kmalloc_redzone' into slab/for-next new 3bf019334fbb slab: Clean up SLOB vs kmalloc() definition new 6fa57d78aa7f slab: Remove special-casing of const 0 size allocations new b5e72d27e39a Merge branch 'slab/for-6.2/alloc_size' into slab/for-next new 4d9dd4b0ce88 mm/slub, kunit: add SLAB_SKIP_KFENCE flag for cache creation new 6cd6d33ca41f mm/slub, kunit: Add a test case for kmalloc redzone check new 617666521385 Merge branch 'slab/for-6.2/kmalloc_redzone' into slab/for-next new 346907ceb9d1 mm, slab: ignore hardened usercopy parameters when disabled new e240e53ae0ab mm, slub: add CONFIG_SLUB_TINY new b1a413a39a1a mm, slub: disable SYSFS support with CONFIG_SLUB_TINY new 5a8a3c1f73c6 mm, slub: retain no free slabs on partial list with CONFIG [...] new 90ce872c22b2 mm, slub: lower the default slub_max_order with CONFIG_SLUB_TINY new 2f7c1c1396b5 mm, slub: don't create kmalloc-rcl caches with CONFIG_SLUB_TINY new 3d97d976e5d5 mm, slab: ignore SLAB_RECLAIM_ACCOUNT with CONFIG_SLUB_TINY new fa9b88e459d7 mm, slub: refactor free debug processing new 56d5a2b9ba85 mm, slub: split out allocations from pre/post hooks new 0af8489b0216 mm, slub: remove percpu slabs with CONFIG_SLUB_TINY new be784ba861b9 mm, slub: don't aggressively inline with CONFIG_SLUB_TINY new 149b6fa228ed mm, slob: rename CONFIG_SLOB to CONFIG_SLOB_DEPRECATED new dc19745ad0e4 Merge branch 'slub-tiny-v1r6' into slab/for-next new 893660b0e1c8 Merge tag 'slab-for-6.2-rc1' of git://git.kernel.org/pub/s [...] new 04593028d7c1 tpm: st33zp24: drop support for platform data new 3f8019093775 tpm: st33zp24: switch to using gpiod API new e10de46bc3c6 tpm: Avoid function type cast of put_device() new 1506fba28b53 KEYS: trusted: tee: Make registered shm dependency explicit new 561d6ef75628 tpm: tis_i2c: Fix sanity check interrupt enable mask new 7bfda9c73fa9 tpm: Add flag to use default cancellation policy new 8740a12ca2e2 tpm: acpi: Call acpi_put_table() to fix memory leak new 37e90c374dd1 tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak new db9622f76210 tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak new 2b7d07f7acaa tpm/tpm_ftpm_tee: Fix error handling in ftpm_mod_init() new f52640680719 tpm/tpm_crb: Fix error message in __crb_relinquish_locality() new eaabc245b02a tpm: st33zp24: remove pointless checks on probe new 43686598b557 Merge tag 'tpmdd-next-v6.2-rc1' of git://git.kernel.org/pu [...] The 145 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: .clang-format | 1 + Documentation/mm/slub.rst | 2 + MAINTAINERS | 8 +- arch/arm/configs/clps711x_defconfig | 3 +- arch/arm/configs/collie_defconfig | 3 +- arch/arm/configs/multi_v4t_defconfig | 3 +- arch/arm/configs/omap1_defconfig | 3 +- arch/arm/configs/pxa_defconfig | 3 +- arch/arm/configs/tct_hammer_defconfig | 3 +- arch/arm/configs/xcep_defconfig | 3 +- arch/m68k/emu/nfcon.c | 9 +- arch/openrisc/configs/or1ksim_defconfig | 3 +- arch/openrisc/configs/simple_smp_defconfig | 3 +- arch/riscv/configs/nommu_k210_defconfig | 3 +- arch/riscv/configs/nommu_k210_sdcard_defconfig | 3 +- arch/riscv/configs/nommu_virt_defconfig | 3 +- arch/sh/configs/rsk7201_defconfig | 3 +- arch/sh/configs/rsk7203_defconfig | 3 +- arch/sh/configs/se7206_defconfig | 3 +- arch/sh/configs/shmin_defconfig | 3 +- arch/sh/configs/shx3_defconfig | 3 +- arch/um/kernel/kmsg_dump.c | 24 +- drivers/char/tpm/eventlog/acpi.c | 12 +- drivers/char/tpm/st33zp24/i2c.c | 142 +----- drivers/char/tpm/st33zp24/spi.c | 145 +----- drivers/char/tpm/st33zp24/st33zp24.c | 39 +- drivers/char/tpm/st33zp24/st33zp24.h | 7 +- drivers/char/tpm/tpm-chip.c | 7 +- drivers/char/tpm/tpm_crb.c | 31 +- drivers/char/tpm/tpm_ftpm_tee.c | 8 +- drivers/char/tpm/tpm_tis.c | 9 +- drivers/char/tpm/tpm_tis_core.c | 20 +- drivers/char/tpm/tpm_tis_core.h | 1 + drivers/char/tpm/tpm_tis_i2c.c | 3 +- drivers/firmware/efi/earlycon.c | 8 +- drivers/firmware/efi/efi-pstore.c | 2 +- drivers/net/netconsole.c | 21 +- drivers/tty/hvc/hvc_console.c | 4 +- drivers/tty/serial/8250/8250_core.c | 2 +- drivers/tty/serial/earlycon.c | 4 +- drivers/tty/serial/kgdboc.c | 46 +- drivers/tty/serial/pic32_uart.c | 4 +- drivers/tty/serial/samsung_tty.c | 2 +- drivers/tty/serial/serial_core.c | 14 +- drivers/tty/serial/sh-sci.c | 20 +- drivers/tty/serial/xilinx_uartps.c | 2 +- drivers/tty/tty_io.c | 18 +- drivers/usb/early/xhci-dbc.c | 2 +- drivers/video/fbdev/xen-fbfront.c | 12 +- fs/binfmt_elf.c | 32 +- fs/binfmt_elf_fdpic.c | 7 +- fs/binfmt_misc.c | 8 +- fs/ceph/locks.c | 4 +- fs/cifs/file.c | 2 +- fs/exec.c | 34 +- fs/ksmbd/vfs.c | 2 +- fs/lockd/svcsubs.c | 4 +- fs/locks.c | 50 +- fs/nfs/delegation.c | 2 +- fs/nfs/nfs4state.c | 2 +- fs/nfs/pagelist.c | 2 +- fs/nfs/write.c | 4 +- fs/nfsd/nfs4state.c | 6 +- fs/proc/consoles.c | 21 +- fs/pstore/platform.c | 25 +- fs/pstore/ram.c | 44 +- fs/pstore/ram_core.c | 20 +- .../linux/pstore_ram.h => fs/pstore/ram_internal.h | 47 +- fs/pstore/zone.c | 2 +- include/linux/console.h | 129 ++++- include/linux/fs.h | 20 + include/linux/kasan.h | 5 +- include/linux/nsproxy.h | 1 + include/linux/percpu.h | 2 +- include/linux/platform_data/st33zp24.h | 16 - include/linux/pstore_ram.h | 99 ---- include/linux/rcutiny.h | 4 - include/linux/seccomp.h | 1 + include/linux/serial_core.h | 10 +- include/linux/slab.h | 64 ++- include/linux/slab_def.h | 2 + include/linux/slub_def.h | 8 +- include/linux/srcu.h | 9 +- include/uapi/linux/elf.h | 14 +- kernel/configs/tiny.config | 5 +- kernel/debug/kdb/kdb_io.c | 18 +- kernel/fork.c | 26 +- kernel/nsproxy.c | 23 +- kernel/printk/printk.c | 498 ++++++++++++++----- kernel/printk/printk_ringbuffer.c | 2 +- kernel/rcu/Kconfig | 11 +- kernel/rcu/Kconfig.debug | 3 - kernel/rcu/rcu.h | 8 +- kernel/rcu/srcutiny.c | 10 + kernel/rcu/update.c | 18 +- lib/Kconfig.kasan | 2 +- lib/slub_kunit.c | 57 ++- lib/test_printf.c | 26 +- lib/vsprintf.c | 2 +- mm/Kconfig | 38 +- mm/Kconfig.debug | 2 +- mm/kasan/generic.c | 19 +- mm/migrate.c | 15 +- mm/slab.c | 113 ++--- mm/slab.h | 86 ++-- mm/slab_common.c | 27 +- mm/slub.c | 553 ++++++++++++++------- security/keys/trusted-keys/trusted_tee.c | 3 +- tools/testing/selftests/seccomp/seccomp_bpf.c | 6 +- tools/testing/selftests/timens/.gitignore | 1 + tools/testing/selftests/timens/Makefile | 2 +- tools/testing/selftests/timens/vfork_exec.c | 139 ++++++ tools/vm/slabinfo.c | 6 +- 113 files changed, 1918 insertions(+), 1183 deletions(-) copy include/linux/pstore_ram.h => fs/pstore/ram_internal.h (76%) delete mode 100644 include/linux/platform_data/st33zp24.h create mode 100644 tools/testing/selftests/timens/vfork_exec.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[binutils-gdb] branch master updated (b99ceddc917 -> c6c1fccd8f5)

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 b99ceddc917 [gdb/testsuite] Fix PR20630 regression test in gdb.base/pri [...] new 78eb490c2c0 libctf: remove unnecessary zlib constructs new c6c1fccd8f5 libctf: remove AC_CONFIG_MACRO_DIR 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: libctf/configure | 12 ++++-------- libctf/configure.ac | 8 ++------ 2 files changed, 6 insertions(+), 14 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/master-aarch64-check_bootstrap_lto updated (4c181857c9d -> e92d57ce2a5)

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_lto in repository toolchain/ci/base-artifacts. discards 4c181857c9d 119: onsuccess: #678: 1: Success after binutils/gcc: 8 commits discards 74b82cc7fd6 118: onsuccess: #677: 1: Success after binutils/gcc: 19 commits discards c94daee4f64 117: onsuccess: #676: 1: Success after binutils/gcc: 61 commits discards 2953d86b403 116: onsuccess: #674: 1: Success after binutils/gcc: 30 commits discards ecf812a017b 115: onsuccess: #673: 1: Success after binutils/gcc: 42 commits discards 9deff6a9375 114: onsuccess: #672: 1: Success after binutils/gcc: 29 commits discards 409120d767c 113: onsuccess: #671: 1: Success after binutils/gcc: 10 commits discards a6ba8865870 112: onsuccess: #670: 1: Success after binutils/gcc: 14 commits discards a995e5bb352 111: onsuccess: #669: 1: Success after binutils/gcc: 39 commits discards d9faae1cd62 110: onsuccess: #668: 1: Success after binutils/gcc: 87 commits discards b38a81a0487 109: onsuccess: #666: 1: Success after binutils/gcc: 60 commits discards 6320692897e 108: onsuccess: #665: 1: Success after binutils/gcc: 83 commits discards 99ed50aca4c 107: onsuccess: #663: 1: Success after gcc: 7 commits discards 3afea539f7c 106: onsuccess: #660: 1: Success after binutils/gcc: 17 commits discards 5049453d7bf 105: onsuccess: #659: 1: Success after binutils/gcc: 50 commits discards 6549a6bdfad 104: onsuccess: #658: 1: Success after binutils/gcc: 48 commits discards 4881beebe48 103: onsuccess: #657: 1: Success after binutils/gcc: 44 commits discards f2f13fcb0b4 102: onsuccess: #656: 1: Success after gcc: 30 commits discards ce2317bc61c 101: onsuccess: #655: 1: Success after binutils: 5 commits discards 05e324f1e4c 100: onsuccess: #653: 1: Success after binutils/gcc: 11 commits discards 6be2b1bffd9 99: onsuccess: #652: 1: Success after binutils/gcc: 35 commits discards 31cc228e3b9 98: onsuccess: #651: 1: Success after binutils/gcc: 34 commits discards 0e2829a340d 97: onsuccess: #650: 1: Success after binutils/gcc: 43 commits discards 30a8104a652 96: onsuccess: #649: 1: Success after binutils/gcc: 25 commits discards c39d52fba1b 95: onsuccess: #648: 1: Success after binutils/gcc: 220 commits discards 1f2d2901d3b 94: onsuccess: #645: 1: Success after binutils: 3 commits discards af8bbf89033 93: onsuccess: #642: 1: Success after binutils: 5 commits discards 057362a7568 92: onsuccess: #640: 1: Success after binutils/gcc: 71 commits discards 26c0a6528d0 91: onsuccess: #639: 1: Success after binutils/gcc: 46 commits discards ce0939857f6 90: onsuccess: #638: 1: Success after binutils/gcc: 59 commits discards 4bf72e99a38 89: onsuccess: #637: 1: Success after binutils/gcc: 70 commits discards 45d1138c98d 88: onsuccess: #636: 1: Success after binutils/gcc: 56 commits discards 58063baa9f0 87: onsuccess: #635: 1: Success after binutils/gcc: 12 commits discards 29c5709d01f 86: onsuccess: #634: 1: Success after binutils/gcc: 28 commits discards 187723b1c0b 85: onsuccess: #633: 1: Success after binutils/gcc: 86 commits discards 3c1f12258b3 84: onsuccess: #632: 1: Success after binutils/gcc: 31 commits discards 1ad19f87390 83: onsuccess: #631: 1: Success after binutils/gcc: 26 commits discards 37427c03d4a 82: onsuccess: #630: 1: Success after binutils/gcc: 34 commits discards ed400fb0c33 81: onsuccess: #629: 1: Success after binutils/gcc: 26 commits discards 9f83b78237a 80: onsuccess: #628: 1: Success after binutils/gcc: 3 commits discards 77481d1e731 79: onsuccess: #627: 1: Success after binutils/gcc: 32 commits discards 9b597b995e9 78: onsuccess: #626: 1: Success after binutils/gcc: 35 commits discards ecf03f91ee4 77: onsuccess: #625: 1: Success after binutils/gcc: 29 commits discards c8fa3da5941 76: onsuccess: #624: 1: Success after binutils/gcc: 35 commits discards 5e99e2ea7c6 75: onsuccess: #623: 1: Success after binutils/gcc: 45 commits discards 1876437f93b 74: onsuccess: #622: 1: Success after binutils/gcc: 25 commits discards 2bfd2c61e6e 73: onsuccess: #621: 1: Success after binutils/gcc: 4 commits discards df6f5292b71 72: onsuccess: #620: 1: Success after binutils/gcc: 15 commits discards de0bb6c7aab 71: onsuccess: #619: 1: Success after binutils/gcc: 45 commits discards f0f34401ad8 70: onsuccess: #618: 1: Success after binutils/gcc: 43 commits discards b91eb6c4705 69: onsuccess: #617: 1: Success after binutils/gcc: 40 commits discards 2f1d8260067 68: onsuccess: #616: 1: Success after binutils/gcc: 58 commits discards ff3336ab3c8 67: onsuccess: #615: 1: Success after binutils/gcc: 29 commits discards 0796ec72294 66: onsuccess: #614: 1: Success after binutils/gcc: 9 commits discards 26f4e4c5c76 65: onsuccess: #613: 1: Success after binutils/gcc: 15 commits discards 09d3fbd54bb 64: onsuccess: #612: 1: Success after binutils/gcc: 52 commits discards 328f8707331 63: onsuccess: #611: 1: Success after binutils/gcc: 28 commits discards f6283a60a1b 62: onsuccess: #610: 1: Success after binutils/gcc: 40 commits discards b4a1dbd4a73 61: onsuccess: #609: 1: Success after binutils/gcc: 100 commits discards 55f432dd5bb 60: onsuccess: #607: 1: Success after binutils: 16 commits discards edc94f5994d 59: onsuccess: #604: 1: Success after gdb-12-branchpoint-21 [...] discards 98044bf8646 58: onsuccess: #601: 1: Success after binutils: 5 commits discards 87c29ea23c9 57: onsuccess: #599: 1: Success after binutils/gcc: 37 commits discards df26f468870 56: onsuccess: #598: 1: Success after binutils/gcc: 56 commits discards df762ba3739 55: onsuccess: #597: 1: Success after binutils/gcc: 37 commits discards 92596078a3d 54: onsuccess: #596: 1: Success after binutils/gcc: 38 commits discards a15346a5533 53: onsuccess: #595: 1: Success after binutils/gcc: 48 commits discards 4b27de6e3ed 52: onsuccess: #594: 1: Success after binutils/gcc: 15 commits discards 6cccdec8a64 51: onsuccess: #593: 1: Success after binutils/gcc: 27 commits discards ad4d1c5a391 50: onsuccess: #592: 1: Success after binutils/gcc: 54 commits discards d5a80ac6ab7 49: onsuccess: #591: 1: Success after binutils/gcc: 87 commits discards e1bac4b6140 48: onsuccess: #589: 1: Success after binutils: 11 commits discards 7d026ead4b2 47: onsuccess: #586: 1: Success after binutils: 8 commits discards 9f9c4614d27 46: onsuccess: #584: 1: Success after binutils/gcc: 43 commits discards 249f2ffe2b2 45: onsuccess: #583: 1: Success after binutils/gcc: 12 commits discards af329d84484 44: onsuccess: #582: 1: Success after binutils/gcc: 19 commits discards 8711fb5dc52 43: onsuccess: #581: 1: Success after binutils/gcc: 55 commits discards f66fd251c6e 42: onsuccess: #580: 1: Success after binutils/gcc: 40 commits discards 3286b8a37dd 41: onsuccess: #579: 1: Success after binutils/gcc: 47 commits discards 95f02831178 40: onsuccess: #578: 1: Success after binutils/gcc: 26 commits discards f6aa6d6b5e0 39: onsuccess: #577: 1: Success after binutils/gcc: 8 commits discards 1dbbd16aeea 38: onsuccess: #576: 1: Success after binutils/gcc: 6 commits discards 2598d7e4836 37: onsuccess: #575: 1: Success after binutils/gcc: 14 commits discards 20929917c97 36: onsuccess: #574: 1: Success after binutils/gcc: 25 commits discards 4b05034d362 35: onsuccess: #573: 1: Success after binutils/gcc: 16 commits discards 504e9688faf 34: onsuccess: #572: 1: Success after binutils/gcc: 34 commits discards 9a7d7d303f7 33: onsuccess: #571: 1: Success after binutils/gcc: 34 commits discards 287549745ca 32: onsuccess: #570: 1: Success after binutils/gcc: 59 commits discards 416d7427362 31: onsuccess: #569: 1: Success after binutils/gcc: 5 commits discards 7386046c258 30: onsuccess: #568: 1: Success after binutils/gcc: 17 commits discards 059c120ce19 29: onsuccess: #567: 1: Success after binutils/gcc: 24 commits discards 39c6a1e1a37 28: onsuccess: #566: 1: Success after binutils/gcc: 25 commits discards b52e4154583 27: onsuccess: #565: 1: Success after binutils/gcc: 149 commits discards f6fbe486c62 26: onsuccess: #563: 1: Success after binutils/gcc: 5 commits discards bf528bf0629 25: onsuccess: #562: 1: Success after binutils/gcc: 14 commits discards 091b386418c 24: onsuccess: 1: Success after binutils/gcc: 39 commits discards 5597a2d4895 23: onsuccess: 1: Success after binutils/gcc: 52 commits discards a0e1257590b 22: onsuccess: 1: Success after binutils/gcc: 33 commits discards edffb0f8f34 21: onsuccess: 1: Successful build after binutils/gcc: 61 commits discards 71b4cd57947 20: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 8afb8f3f83b 19: onsuccess: 1: Successful build after binutils/gcc: 18 commits new dfb1eb7cc3d 19: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 81566e8139f 20: onsuccess: 1: Successful build after binutils/gcc: 5 commits new c9c17481532 21: onsuccess: 1: Successful build after binutils/gcc: 61 commits new bb160aa3155 22: onsuccess: 1: Success after binutils/gcc: 33 commits new e901aaf5dad 23: onsuccess: 1: Success after binutils/gcc: 52 commits new 7173478870a 24: onsuccess: 1: Success after binutils/gcc: 39 commits new 91d43caab88 25: onsuccess: #562: 1: Success after binutils/gcc: 14 commits new 286a0899493 26: onsuccess: #563: 1: Success after binutils/gcc: 5 commits new db1d96cb5bf 27: onsuccess: #565: 1: Success after binutils/gcc: 149 commits new 015bac9f02d 28: onsuccess: #566: 1: Success after binutils/gcc: 25 commits new 8815cfc0952 29: onsuccess: #567: 1: Success after binutils/gcc: 24 commits new 201d1128f15 30: onsuccess: #568: 1: Success after binutils/gcc: 17 commits new c5ccf67a9d4 31: onsuccess: #569: 1: Success after binutils/gcc: 5 commits new fac1a487f5c 32: onsuccess: #570: 1: Success after binutils/gcc: 59 commits new 74eb885afad 33: onsuccess: #571: 1: Success after binutils/gcc: 34 commits new b1dcf38d9b4 34: onsuccess: #572: 1: Success after binutils/gcc: 34 commits new 636becee9f2 35: onsuccess: #573: 1: Success after binutils/gcc: 16 commits new 86ef5b5a200 36: onsuccess: #574: 1: Success after binutils/gcc: 25 commits new 42c887cea07 37: onsuccess: #575: 1: Success after binutils/gcc: 14 commits new eff980e7002 38: onsuccess: #576: 1: Success after binutils/gcc: 6 commits new a4594e830a5 39: onsuccess: #577: 1: Success after binutils/gcc: 8 commits new 2a367c82d53 40: onsuccess: #578: 1: Success after binutils/gcc: 26 commits new f95750447ce 41: onsuccess: #579: 1: Success after binutils/gcc: 47 commits new 01834e40244 42: onsuccess: #580: 1: Success after binutils/gcc: 40 commits new 221809b5c86 43: onsuccess: #581: 1: Success after binutils/gcc: 55 commits new 29bb677dbaf 44: onsuccess: #582: 1: Success after binutils/gcc: 19 commits new cc1996e7aa6 45: onsuccess: #583: 1: Success after binutils/gcc: 12 commits new cafbe2b6019 46: onsuccess: #584: 1: Success after binutils/gcc: 43 commits new 93179b39318 47: onsuccess: #586: 1: Success after binutils: 8 commits new 4cebc1fa7fc 48: onsuccess: #589: 1: Success after binutils: 11 commits new 85a36016c07 49: onsuccess: #591: 1: Success after binutils/gcc: 87 commits new bf71057fce7 50: onsuccess: #592: 1: Success after binutils/gcc: 54 commits new a09f5f699b0 51: onsuccess: #593: 1: Success after binutils/gcc: 27 commits new bbbe13174e2 52: onsuccess: #594: 1: Success after binutils/gcc: 15 commits new 368982640ac 53: onsuccess: #595: 1: Success after binutils/gcc: 48 commits new 6a9caa5cfcd 54: onsuccess: #596: 1: Success after binutils/gcc: 38 commits new f5c019037b9 55: onsuccess: #597: 1: Success after binutils/gcc: 37 commits new 81c5492957d 56: onsuccess: #598: 1: Success after binutils/gcc: 56 commits new 7f4b7ed47fd 57: onsuccess: #599: 1: Success after binutils/gcc: 37 commits new 27b41533c66 58: onsuccess: #601: 1: Success after binutils: 5 commits new fa5a94cdb33 59: onsuccess: #604: 1: Success after gdb-12-branchpoint-21 [...] new 6c94c6b8080 60: onsuccess: #607: 1: Success after binutils: 16 commits new 8f35bfc0f4a 61: onsuccess: #609: 1: Success after binutils/gcc: 100 commits new c2d0670e498 62: onsuccess: #610: 1: Success after binutils/gcc: 40 commits new 5a821a37bf9 63: onsuccess: #611: 1: Success after binutils/gcc: 28 commits new a8e57dc7956 64: onsuccess: #612: 1: Success after binutils/gcc: 52 commits new 951252a1b9e 65: onsuccess: #613: 1: Success after binutils/gcc: 15 commits new 0318a26a45b 66: onsuccess: #614: 1: Success after binutils/gcc: 9 commits new cddf246113a 67: onsuccess: #615: 1: Success after binutils/gcc: 29 commits new e729f73a15d 68: onsuccess: #616: 1: Success after binutils/gcc: 58 commits new 0dd636486d5 69: onsuccess: #617: 1: Success after binutils/gcc: 40 commits new 888068ec4cc 70: onsuccess: #618: 1: Success after binutils/gcc: 43 commits new 7e05380f841 71: onsuccess: #619: 1: Success after binutils/gcc: 45 commits new b98d3dcf838 72: onsuccess: #620: 1: Success after binutils/gcc: 15 commits new d56ccf53561 73: onsuccess: #621: 1: Success after binutils/gcc: 4 commits new df27c33661a 74: onsuccess: #622: 1: Success after binutils/gcc: 25 commits new 7cbd572ea10 75: onsuccess: #623: 1: Success after binutils/gcc: 45 commits new 2ec59ee5908 76: onsuccess: #624: 1: Success after binutils/gcc: 35 commits new 4c71353b281 77: onsuccess: #625: 1: Success after binutils/gcc: 29 commits new 55ddb646b74 78: onsuccess: #626: 1: Success after binutils/gcc: 35 commits new 05c4c402baa 79: onsuccess: #627: 1: Success after binutils/gcc: 32 commits new 2601afad161 80: onsuccess: #628: 1: Success after binutils/gcc: 3 commits new 00873e6a644 81: onsuccess: #629: 1: Success after binutils/gcc: 26 commits new 7c9a7695efa 82: onsuccess: #630: 1: Success after binutils/gcc: 34 commits new 37ddac7b349 83: onsuccess: #631: 1: Success after binutils/gcc: 26 commits new 694018aa167 84: onsuccess: #632: 1: Success after binutils/gcc: 31 commits new 9bf476df0ea 85: onsuccess: #633: 1: Success after binutils/gcc: 86 commits new 5f43f548967 86: onsuccess: #634: 1: Success after binutils/gcc: 28 commits new ceef4736a52 87: onsuccess: #635: 1: Success after binutils/gcc: 12 commits new 2fafd23be3f 88: onsuccess: #636: 1: Success after binutils/gcc: 56 commits new b2eaeb11fdc 89: onsuccess: #637: 1: Success after binutils/gcc: 70 commits new 8378bc95d2b 90: onsuccess: #638: 1: Success after binutils/gcc: 59 commits new 4cde105fd38 91: onsuccess: #639: 1: Success after binutils/gcc: 46 commits new 7cdc6bd0f23 92: onsuccess: #640: 1: Success after binutils/gcc: 71 commits new 3957fbb2415 93: onsuccess: #642: 1: Success after binutils: 5 commits new 63bcacafc3a 94: onsuccess: #645: 1: Success after binutils: 3 commits new b585b73888e 95: onsuccess: #648: 1: Success after binutils/gcc: 220 commits new cd95ed7a7e0 96: onsuccess: #649: 1: Success after binutils/gcc: 25 commits new 415715c2623 97: onsuccess: #650: 1: Success after binutils/gcc: 43 commits new 1a405f2bbaf 98: onsuccess: #651: 1: Success after binutils/gcc: 34 commits new 787df6ad17f 99: onsuccess: #652: 1: Success after binutils/gcc: 35 commits new e12f047217a 100: onsuccess: #653: 1: Success after binutils/gcc: 11 commits new 2569446852f 101: onsuccess: #655: 1: Success after binutils: 5 commits new 91f44100ef4 102: onsuccess: #656: 1: Success after gcc: 30 commits new 5bf2f426e4d 103: onsuccess: #657: 1: Success after binutils/gcc: 44 commits new 3d2021e01d2 104: onsuccess: #658: 1: Success after binutils/gcc: 48 commits new fe3d7c751ec 105: onsuccess: #659: 1: Success after binutils/gcc: 50 commits new 6388849d9f5 106: onsuccess: #660: 1: Success after binutils/gcc: 17 commits new 01afc9e4811 107: onsuccess: #663: 1: Success after gcc: 7 commits new 693969cf5ef 108: onsuccess: #665: 1: Success after binutils/gcc: 83 commits new e11ccbafa82 109: onsuccess: #666: 1: Success after binutils/gcc: 60 commits new c7e39678134 110: onsuccess: #668: 1: Success after binutils/gcc: 87 commits new 488615fa43a 111: onsuccess: #669: 1: Success after binutils/gcc: 39 commits new 0ec549172b5 112: onsuccess: #670: 1: Success after binutils/gcc: 14 commits new 3e48e5b3daa 113: onsuccess: #671: 1: Success after binutils/gcc: 10 commits new b53fa56004a 114: onsuccess: #672: 1: Success after binutils/gcc: 29 commits new c06834b568c 115: onsuccess: #673: 1: Success after binutils/gcc: 42 commits new 1027938f2d7 116: onsuccess: #674: 1: Success after binutils/gcc: 30 commits new cbbcf17cdf1 117: onsuccess: #676: 1: Success after binutils/gcc: 61 commits new 541bda12108 118: onsuccess: #677: 1: Success after binutils/gcc: 19 commits new 4d1a050196b 119: onsuccess: #678: 1: Success after binutils/gcc: 8 commits new e92d57ce2a5 120: onsuccess: #679: 1: Success after binutils/gcc: 39 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 (4c181857c9d) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check_bootstrap/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 1756 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 39428 -> 39668 bytes 04-build_abe-bootstrap_lto/console.log.xz | Bin 279072 -> 278196 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3916 bytes 06-build_abe-check_bootstrap_lto/console.log.xz | Bin 2692 -> 2728 bytes 07-check_regression/console.log.xz | Bin 5400 -> 5280 bytes 07-check_regression/mail-body.txt | 31 - 07-check_regression/results.compare | 35 +- 07-check_regression/results.compare2 | 69 +- 08-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 33 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 3690624 -> 3645608 bytes sumfiles/g++.sum | 126 +- sumfiles/gcc.log.xz | Bin 3262080 -> 3280820 bytes sumfiles/gcc.sum | 4557 ++++++++++++----------- sumfiles/gfortran.log.xz | Bin 1089784 -> 1098976 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2352 -> 2348 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 225856 -> 226228 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2736 -> 2724 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 474356 -> 455844 bytes sumfiles/libstdc++.sum | 16 +- 32 files changed, 2464 insertions(+), 2561 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-lts-allmodconfig updated (069eaea1269 -> 1691c204c98)

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 069eaea1269 30: onsuccess: #406: all: Success after binutils/gcc/qemu: [...] new 1691c204c98 31: onsuccess: #408: all: Success after binutils/gcc/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1736 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30064 -> 30088 bytes 04-build_abe-stage1/console.log.xz | Bin 87124 -> 86972 bytes 05-build_abe-qemu/console.log.xz | Bin 30372 -> 30896 bytes 06-build_linux/console.log.xz | Bin 3468 -> 3452 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 3720 -> 4184 bytes 09-update_baseline/console.log | 8 ++++---- 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 ++++++++++++++++---------------- 18 files changed, 28 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

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

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 c65e1dbfef5 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 7cd8be832fc 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/ [...] discards e27dc82fdc1 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/ [...] discards eb32450cb12 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-4 [...] discards 49ff25e2f5e 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/ [...] discards a72c307d539 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 1 [...] discards 24e99451e62 225: onsuccess: #2039: 1: Success after binutils/linux/glib [...] discards 81cede9dcb9 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/ [...] discards 9ffd525ea2f 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/ [...] discards 308d2f807dd 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/ [...] discards efb12c21f10 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards be00e0fd27e 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/ [...] discards c614c2fbf55 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/ [...] discards 0bdcb35fe69 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards a9b7ab61fbd 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/ [...] discards bb3c9942d70 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/ [...] discards 0e80856e100 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...] discards ca92678b122 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] discards bf4bcc2097a 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards e99ab282285 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 4fd02fdf379 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 0dea73171f5 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards a84776eedb8 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 2ba2f74afd0 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 7356c915aa5 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards b830de642a2 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 055dcc09765 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 646b4ca7a39 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards b11ffa579fe 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards 6b784cb0ccc 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards 6e14d17bd56 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards b8743817546 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards a59ca0a46ad 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 379a4220338 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards 685704cd5fe 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards a62b58c9185 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards 85864621ee8 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards 8d86b9187ca 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 466f755379c 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards b9f124b2e7a 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards 3f14b630af4 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards 462b9ee997b 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards 38cd6604edd 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards a9f49aa4fb8 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards 600dab674be 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards a549b21de45 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards 59ac1103a08 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards f27c1ab162d 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards 081f2656eff 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards 03d0a3c99bd 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards 663a0607c68 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards d01f6fb2f87 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards a20fef256fb 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards edf5981e7e0 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards ef510463811 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards bbc8e924437 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards 54c90516d75 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards 74d82851b40 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards 2e9a1db984a 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards 5737cd9b648 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards d7e5f1d2262 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards c9c620661d4 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards b0d232703dd 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards 118fd5d1c95 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards c464265b420 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards 2679e180d44 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards 776247fffba 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards 75f6210971b 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards f0724479bd2 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards c78fd69fbc2 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards bca59920b7f 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards 0615d5cddc2 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards ff780f46eca 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards 77aa2ada221 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards 483673d9abb 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards 378be1d3f5e 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards a64d15fe8c8 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards ebd4adf2fe6 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 0e893c85b01 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 65f59b4f695 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards 0b2803a0e15 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards a5e6ae76f41 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards 44ca356c563 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards 5d2e436a736 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards 7267b5ac0f5 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards 99804bb8c72 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards 7f69abc2eed 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards 04b877e4729 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 3552073cb1e 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards 656f2fe5197 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards abb4b1e9a95 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards b5391ccfebd 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards 9cfebbce141 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards 63518bff90f 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards daa7ca7f2bf 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards ff16c36138d 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards 5bb9b2f0788 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 90142e673e1 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards bd0f2518b66 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards d71b7b87ae1 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] discards 4cacbdd938a 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new 895022171e6 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new 2b110f807f1 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new 6d49028a069 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new 76d9055fdc8 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 5ddba33d7bd 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 2f58885fc0f 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new f7ae7c9a751 137: onsuccess: #1736: 1: Success after gcc: 5 commits new f569da6cd60 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new a38aa7d4138 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new 7968b159b3e 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new 054d916db34 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new f19830eda26 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new 78c653331c1 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 82dc7954575 144: onsuccess: #1743: 1: Success after glibc: 2 commits new b924446f60e 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new 53178a21bab 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new 17a97b059e8 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new 437767c45af 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new 97bbbac00f2 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new 31c4fb4f969 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new 316d05efa59 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new 36997dde6a3 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new bded2320aa6 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 425c8025e0d 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 27bac6c7879 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new 32200643ef1 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 8bf8415c947 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new 697f44d61bf 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new 4be89cf0c8d 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new 5edf14b761a 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new bc00c8a223a 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new 3b43cbb266a 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new 9e50f53a0dc 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new d56602f69c4 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new e99371b0cd0 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new bcf52b76611 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new 1f5634eecc9 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new 1a861afe7db 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new 8bb0c9feb5f 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new ea0969d650a 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new a5aef2539e6 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new 604f98cc344 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new 1827309b40e 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new aa880173a98 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new 26f0780e746 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new ec5e49834ab 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new d48109653fa 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new 7f20a10ac45 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new 0292e60dfb5 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new 65cc6fb9ad8 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new 2b7aeacf0cc 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new ac877667c07 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new 09b580411a3 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new 8fcb6866c62 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new 8a3dc48fce5 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new cf178464fed 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new dbd094242ce 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new f6ecaa89782 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new 8123e617f8d 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new 04ec169ef75 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new aaf8818cafa 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new f692d707766 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new 4f19ae983dd 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 73adbd10096 194: onsuccess: #1995: 1: Success after linux: 517 commits new bce43513b0d 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new 47373b6bc37 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new 541c8cfbd2e 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new 8bfeab54347 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new dfdf7ce080d 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 49234892ffb 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new fe676f6aff3 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 11a9bbdac68 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new 85486685f7e 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new 54d5e2c7fc5 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new d08597a7c65 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 68cb67d3a01 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 073272dd018 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 6dc1e2a15ec 208: onsuccess: #2012: 1: Success after linux: 12 commits new 5dd4545fc76 209: onsuccess: #2014: 1: Success after binutils: 12 commits new d5dae83e032 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 5c452bac99b 211: onsuccess: #2020: 1: Success after binutils: 10 commits new a0a333d7476 212: onsuccess: #2022: 1: Success after linux: 3 commits new c5c47b1cd1f 213: onsuccess: #2024: 1: Success after binutils: 3 commits new d3a40c47969 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] new 71dc7e24739 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...] new 63301faae53 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/ [...] new 327589f9bdf 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/ [...] new 855c2c94c89 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 849d4681b61 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/ [...] new 737c3a2ee42 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/ [...] new 7cc91813e28 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 856b836d6f1 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/ [...] new 635140ca592 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/ [...] new 65d29bbf306 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/ [...] new 45be50f4d8b 225: onsuccess: #2039: 1: Success after binutils/linux/glib [...] new 87174822940 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 1 [...] new a6c8538af5d 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/ [...] new 98f87369448 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-4 [...] new 2df14d234a4 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/ [...] new 7a3673524f2 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/ [...] new 17def68b54f 231: onsuccess: #2047: 1: Success after gcc: 4 commits new e9de057a43d 232: onsuccess: #2048: 1: Success after glibc: 2 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (c65e1dbfef5) \ 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 1788 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31640 -> 31536 bytes 04-build_abe-stage1/console.log.xz | Bin 91504 -> 91424 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8448 -> 8388 bytes 07-build_abe-glibc/console.log.xz | Bin 235800 -> 234908 bytes 08-build_abe-stage2/console.log.xz | Bin 224064 -> 225112 bytes 09-build_abe-gdb/console.log.xz | Bin 38916 -> 38744 bytes 10-build_abe-qemu/console.log.xz | Bin 30296 -> 30404 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2552 -> 2544 bytes 13-check_regression/console.log.xz | Bin 5008 -> 5148 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 26 + 13-check_regression/results.compare | 31 +- 13-check_regression/results.compare2 | 36 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +- results | 26 + sumfiles/g++.log.xz | Bin 2661704 -> 2682708 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 2222200 -> 2242348 bytes sumfiles/gcc.sum | 2776 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 893904 -> 893056 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 214076 -> 213956 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 433460 -> 427692 bytes sumfiles/libstdc++.sum | 16 +- 41 files changed, 1686 insertions(+), 1568 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-lts-allmodconfig updated (61eb6dd3c35 -> 65039cce7a7)

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 61eb6dd3c35 30: onsuccess: #491: 33: Success after binutils/gcc/qemu: 2 [...] new 65039cce7a7 31: onsuccess: #493: 33: 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 1792 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 32036 -> 31692 bytes 04-build_abe-stage1/console.log.xz | Bin 92264 -> 91584 bytes 05-build_abe-qemu/console.log.xz | Bin 30672 -> 30452 bytes 06-build_linux/console.log.xz | Bin 5964 -> 4988 bytes 08-check_regression/console.log.xz | Bin 4028 -> 4344 bytes 09-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 33 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022