Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_O3 updated (97ba2716937 -> 13104f561d1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_O3 in repository toolchain/ci/base-artifacts. discards 97ba2716937 220: onsuccess: #31: 2: Success after binutils/gcc: 38 commits discards 7d3c3652d98 219: onsuccess: #30: 2: Success after binutils/gcc: 40 commits discards 0844b146dda 218: onsuccess: #29: 2: Success after binutils/gcc: 43 commits discards be95312c9af 217: onsuccess: #27: 2: Success after binutils/gcc: 33 commits discards 9b0f95fc8e1 216: onsuccess: #26: 2: Success after binutils/gcc: 45 commits discards d7f320b88b2 215: onsuccess: #25: 2: Success after binutils/gcc: 36 commits discards 021f26b0d0e 214: onsuccess: #24: 2: Success after binutils/gcc: 37 commits discards b6a537f47e7 213: onsuccess: #23: 2: Success after binutils/gcc: 56 commits discards c9c636b9ec9 212: onsuccess: #22: 2: Success after binutils/gcc: 42 commits discards 91c6be470c1 211: onsuccess: #21: 2: Success after binutils/gcc: 15 commits discards eb517c18c2b 210: onsuccess: #20: 2: Success after binutils/gcc: 15 commits discards 2fd854ce918 209: onsuccess: #19: 2: Success after binutils/gcc: 57 commits discards 47b43b784b9 208: onsuccess: #18: 2: Success after binutils/gcc: 33 commits discards 596e79adf1a 207: onsuccess: #17: 2: Success after binutils/gcc: 55 commits discards b1cf72ea139 206: onsuccess: #16: 0: Success after binutils: 17 commits discards 3b84433df34 205: force: #15: 0: Failure after gdb-13-branchpoint-1318-g [...] discards 0de41cc951a 204: force: #14: 2: Success after binutils: 17 commits discards bd4efb841b7 203: onsuccess: #12: 2: Success after binutils/gcc: 27 commits discards 3af19dac8d9 202: onsuccess: #11: 2: Success after binutils/gcc: 18 commits discards 476f3e3f212 201: onsuccess: #10: 2: Success after binutils/gcc: 17 commits discards 84ec94ed4f0 200: onsuccess: #9: 2: Success after binutils/gcc: 53 commits discards d7c0fd9e223 199: onsuccess: #8: 2: Success after binutils/gcc: 40 commits discards 41e47186ebd 198: onsuccess: #7: 2: Success after binutils/gcc: 24 commits discards 54ad3efacf7 197: onsuccess: #6: 2: Success after binutils/gcc: 47 commits discards 6c411474932 196: onsuccess: #5: 2: Success after binutils/gcc: 40 commits discards e9353bc53b9 195: onsuccess: #4: 2: Success after binutils/gcc: 7 commits discards 11741fefd9b 194: onsuccess: #3: 2: Success after binutils/gcc: 8 commits discards c30ba7763b9 193: onsuccess: #2: 2: Success after binutils/gcc: 19 commits discards ac2ebbb7fb4 192: onsuccess: #1: 2: Success after binutils/gcc: 29 commits discards a1b2574bf08 191: onsuccess: #630: 2: Success after binutils/gcc: 41 commits discards f70f1da3290 190: onsuccess: #629: 2: Success after binutils/gcc: 34 commits discards 79516f3cad3 189: onsuccess: #628: 2: Success after binutils/gcc: 281 commits discards da8cd7b04f8 188: onsuccess: #622: 2: Success after binutils/gcc: 114 commits discards c0dfe1946ac 187: onsuccess: #621: 2: Success after binutils/gcc: 25 commits discards 25e30e2cce4 186: onsuccess: #620: 2: Success after binutils/gcc: 93 commits discards 5b239677e73 185: onsuccess: #619: 2: Success after binutils/gcc: 109 commits discards 6f2166273a9 184: onsuccess: #618: 2: Success after binutils/gcc: 64 commits discards 9331bab02e9 183: onsuccess: #617: 2: Success after binutils/gcc: 85 commits discards c2ed310f967 182: onsuccess: #615: 2: Success after binutils/gcc: 37 commits discards a177ce69215 181: onsuccess: #614: 2: Success after binutils/gcc: 16 commits discards d71d6e9fb15 180: onsuccess: #613: 2: Success after binutils/gcc: 24 commits discards d494a46dd9f 179: onsuccess: #612: 2: Success after binutils/gcc: 14 commits discards 6e528b0ba98 178: onsuccess: #611: 2: Success after binutils/gcc: 29 commits discards 135072843dc 177: onsuccess: #610: 2: Success after binutils/gcc: 58 commits discards 88192481b86 176: onsuccess: #609: 2: Success after binutils/gcc: 42 commits discards 955b6d27cd6 175: onsuccess: #608: 2: Success after binutils/gcc: 106 commits discards 62385dbfa33 174: onsuccess: #607: 2: Success after binutils/gcc: 50 commits discards cc35bd73c15 173: onsuccess: #606: 2: Success after binutils/gcc: 17 commits discards e5982a3dc0e 172: onsuccess: #605: 2: Success after binutils/gcc: 57 commits discards 1abc455cce1 171: onsuccess: #604: 2: Success after binutils/gcc: 104 commits discards c484006ce22 170: onsuccess: #603: 2: Success after binutils/gcc: 63 commits discards 7e8c791246b 169: onsuccess: #602: 2: Success after binutils/gcc: 30 commits discards 63038000b67 168: onsuccess: #601: 2: Success after binutils/gcc: 47 commits discards b21996592f0 167: onsuccess: #600: 2: Success after binutils/gcc: 15 commits discards 2402a746f3c 166: onsuccess: #599: 2: Success after binutils/gcc: 44 commits discards 8a918f36697 165: onsuccess: #598: 2: Success after binutils/gcc: 43 commits discards 1963dc87ebf 164: onsuccess: #597: 2: Success after binutils/gcc: 40 commits discards 8aa6fe1e596 163: onsuccess: #596: 2: Success after binutils/gcc: 65 commits discards d48ac0492bc 162: onsuccess: #595: 2: Success after binutils/gcc: 36 commits discards 5514da25b53 161: onsuccess: #594: 2: Success after binutils/gcc: 135 commits discards 96c244d3fe8 160: onsuccess: #593: 2: Success after binutils/gcc: 40 commits discards 7a8dcc8868c 159: onsuccess: #592: 2: Success after binutils/gcc: 131 commits discards 19f6f1c0662 158: onsuccess: #588: 2: Success after binutils/gcc: 6 commits discards a18cd223312 157: onsuccess: #587: 2: Success after binutils/gcc: 16 commits discards dd6a4b5d96c 156: onsuccess: #586: 2: Success after binutils/gcc: 55 commits discards 5908419c1fa 155: onsuccess: #585: 2: Success after binutils/gcc: 36 commits discards 88510ea1f84 154: onsuccess: #584: 2: Success after binutils/gcc: 36 commits discards 930f6cd3a16 153: onsuccess: #583: 2: Success after binutils/gcc: 45 commits discards 047d072f06e 152: onsuccess: #582: 2: Success after binutils/gcc: 25 commits discards 010e3a8e757 151: onsuccess: #581: 2: Success after binutils/gcc: 12 commits discards 4e8ee6091e5 150: onsuccess: #580: 2: Success after binutils/gcc: 19 commits discards 88155e36ae1 149: onsuccess: #579: 2: Success after binutils/gcc: 20 commits discards 4b151f128b8 148: onsuccess: #578: 2: Success after binutils/gcc: 7 commits discards f4368464e54 147: onsuccess: #577: 2: Success after binutils/gcc: 22 commits discards ab880204e8d 146: onsuccess: #576: 2: Success after binutils/gcc: 16 commits discards 7808c7d81d0 145: onsuccess: #575: 2: Success after binutils/gcc: 6 commits discards 70146fb6b78 144: onsuccess: #574: 2: Success after binutils/gcc: 26 commits discards d1e1eb53c58 143: onsuccess: #573: 2: Success after binutils/gcc: 35 commits discards 1c1e1eb1a57 142: onsuccess: #572: 2: Success after binutils/gcc: 74 commits discards 61fc2025c89 141: onsuccess: #571: 2: Success after binutils/gcc: 43 commits discards b3b8e2cbc72 140: onsuccess: #570: 2: Success after binutils/gcc: 56 commits discards 901841982fc 139: onsuccess: #569: 2: Success after binutils/gcc: 42 commits discards 89a01537c0b 138: onsuccess: #568: 2: Success after binutils/gcc: 22 commits discards ef7dd1ddaeb 137: onsuccess: #567: 2: Success after binutils/gcc: 10 commits discards b1d2df705a9 136: onsuccess: #566: 2: Success after binutils/gcc: 37 commits discards a4e94696b5d 135: onsuccess: #565: 2: Success after binutils/gcc: 40 commits discards 715e2fb7c15 134: onsuccess: #564: 1: Success after binutils/gcc: 30 commits discards 38f5966d695 133: onsuccess: #563: 1: Success after binutils/gcc: 108 commits discards e78e251d4b8 132: onsuccess: #562: 1: Success after baseline build: no n [...] discards 950e61db080 131: force: #561: 1: Failure after gdb-12-branchpoint-3046- [...] discards 4f72efd3351 130: force: #560: 2: Success after binutils: 21 commits discards 6358c279d8d 129: onsuccess: #556: 2: Success after binutils/gcc: 23 commits discards c7ab2917205 128: onsuccess: #555: 2: Success after binutils/gcc: 4 commits discards 1ecd56a32f4 127: onsuccess: #554: 2: Success after binutils/gcc: 20 commits discards 2fffd3cd9f2 126: onsuccess: #553: 2: Success after binutils/gcc: 36 commits discards 51d4a778e57 125: onsuccess: #552: 2: Success after binutils/gcc: 25 commits discards 61a83d1cbb7 124: onsuccess: #551: 2: Success after binutils/gcc: 41 commits discards ba7871a6d16 123: onsuccess: #550: 2: Success after binutils/gcc: 40 commits discards 6a6d910dcf1 122: onsuccess: #549: 2: Success after binutils/gcc: 20 commits discards f76718ae7ca 121: onsuccess: #548: 2: Success after binutils/gcc: 9 commits discards a3ece1a4a86 120: onsuccess: #547: 2: Success after binutils/gcc: 17 commits new 1af3fa1c742 120: onsuccess: #547: 2: Success after binutils/gcc: 17 commits new bf8b588c7ab 121: onsuccess: #548: 2: Success after binutils/gcc: 9 commits new 03d519188c8 122: onsuccess: #549: 2: Success after binutils/gcc: 20 commits new 05c0a420d7e 123: onsuccess: #550: 2: Success after binutils/gcc: 40 commits new 5a7f99a375f 124: onsuccess: #551: 2: Success after binutils/gcc: 41 commits new 95444985724 125: onsuccess: #552: 2: Success after binutils/gcc: 25 commits new 9c617e41342 126: onsuccess: #553: 2: Success after binutils/gcc: 36 commits new c30a8e4dfca 127: onsuccess: #554: 2: Success after binutils/gcc: 20 commits new 39561920f5b 128: onsuccess: #555: 2: Success after binutils/gcc: 4 commits new 80627de499c 129: onsuccess: #556: 2: Success after binutils/gcc: 23 commits new 2092049537c 130: force: #560: 2: Success after binutils: 21 commits new 43be915f567 131: force: #561: 1: Failure after gdb-12-branchpoint-3046- [...] new 68c45ce204f 132: onsuccess: #562: 1: Success after baseline build: no n [...] new 013fea70de7 133: onsuccess: #563: 1: Success after binutils/gcc: 108 commits new a5a64694792 134: onsuccess: #564: 1: Success after binutils/gcc: 30 commits new 8823bdc62a1 135: onsuccess: #565: 2: Success after binutils/gcc: 40 commits new 9411d0f39cf 136: onsuccess: #566: 2: Success after binutils/gcc: 37 commits new 663ed91383d 137: onsuccess: #567: 2: Success after binutils/gcc: 10 commits new ddcde785fec 138: onsuccess: #568: 2: Success after binutils/gcc: 22 commits new afd0ae16ce1 139: onsuccess: #569: 2: Success after binutils/gcc: 42 commits new 74ccadccbf9 140: onsuccess: #570: 2: Success after binutils/gcc: 56 commits new 8f40abec6cd 141: onsuccess: #571: 2: Success after binutils/gcc: 43 commits new 61bd31923f3 142: onsuccess: #572: 2: Success after binutils/gcc: 74 commits new 8de79738bcd 143: onsuccess: #573: 2: Success after binutils/gcc: 35 commits new 8f12da7b408 144: onsuccess: #574: 2: Success after binutils/gcc: 26 commits new 7c938072663 145: onsuccess: #575: 2: Success after binutils/gcc: 6 commits new e8f51715ee5 146: onsuccess: #576: 2: Success after binutils/gcc: 16 commits new 2ff98c285f8 147: onsuccess: #577: 2: Success after binutils/gcc: 22 commits new 3e346951b0e 148: onsuccess: #578: 2: Success after binutils/gcc: 7 commits new 3232970b710 149: onsuccess: #579: 2: Success after binutils/gcc: 20 commits new 3199c1f61b4 150: onsuccess: #580: 2: Success after binutils/gcc: 19 commits new 1e203f96637 151: onsuccess: #581: 2: Success after binutils/gcc: 12 commits new 900ec4144f9 152: onsuccess: #582: 2: Success after binutils/gcc: 25 commits new 295b67920ac 153: onsuccess: #583: 2: Success after binutils/gcc: 45 commits new ffe9731f950 154: onsuccess: #584: 2: Success after binutils/gcc: 36 commits new 1f703922f00 155: onsuccess: #585: 2: Success after binutils/gcc: 36 commits new 0aa204227a7 156: onsuccess: #586: 2: Success after binutils/gcc: 55 commits new 2a5b9bd6474 157: onsuccess: #587: 2: Success after binutils/gcc: 16 commits new 17c8ccfcc87 158: onsuccess: #588: 2: Success after binutils/gcc: 6 commits new 7e6a4baa5e0 159: onsuccess: #592: 2: Success after binutils/gcc: 131 commits new dc56523750d 160: onsuccess: #593: 2: Success after binutils/gcc: 40 commits new 3271cb1ebb0 161: onsuccess: #594: 2: Success after binutils/gcc: 135 commits new 0dc418254bf 162: onsuccess: #595: 2: Success after binutils/gcc: 36 commits new 4f67a4d83d1 163: onsuccess: #596: 2: Success after binutils/gcc: 65 commits new 2328def4353 164: onsuccess: #597: 2: Success after binutils/gcc: 40 commits new 12f2515a9c1 165: onsuccess: #598: 2: Success after binutils/gcc: 43 commits new 8f5c72cafe3 166: onsuccess: #599: 2: Success after binutils/gcc: 44 commits new a59ce77f6df 167: onsuccess: #600: 2: Success after binutils/gcc: 15 commits new c3cead32143 168: onsuccess: #601: 2: Success after binutils/gcc: 47 commits new 4c7af1e9e7e 169: onsuccess: #602: 2: Success after binutils/gcc: 30 commits new a09170c58c0 170: onsuccess: #603: 2: Success after binutils/gcc: 63 commits new 4c7b8dcf5d9 171: onsuccess: #604: 2: Success after binutils/gcc: 104 commits new 677f079be74 172: onsuccess: #605: 2: Success after binutils/gcc: 57 commits new 9c7ccd4f720 173: onsuccess: #606: 2: Success after binutils/gcc: 17 commits new 76af5f9a79e 174: onsuccess: #607: 2: Success after binutils/gcc: 50 commits new b308b5ae259 175: onsuccess: #608: 2: Success after binutils/gcc: 106 commits new c5a1e3ea34f 176: onsuccess: #609: 2: Success after binutils/gcc: 42 commits new 3b52bd5fa9a 177: onsuccess: #610: 2: Success after binutils/gcc: 58 commits new 1ad5de68c78 178: onsuccess: #611: 2: Success after binutils/gcc: 29 commits new f5dfd17e2bb 179: onsuccess: #612: 2: Success after binutils/gcc: 14 commits new 508bc6e8936 180: onsuccess: #613: 2: Success after binutils/gcc: 24 commits new 11a922f6313 181: onsuccess: #614: 2: Success after binutils/gcc: 16 commits new ac0c467f5a5 182: onsuccess: #615: 2: Success after binutils/gcc: 37 commits new 00a2ac6fca8 183: onsuccess: #617: 2: Success after binutils/gcc: 85 commits new fdbaeb04bd5 184: onsuccess: #618: 2: Success after binutils/gcc: 64 commits new 957715cb8b3 185: onsuccess: #619: 2: Success after binutils/gcc: 109 commits new a465e4b91e4 186: onsuccess: #620: 2: Success after binutils/gcc: 93 commits new d5d99db6d32 187: onsuccess: #621: 2: Success after binutils/gcc: 25 commits new 2e49dfd2bbe 188: onsuccess: #622: 2: Success after binutils/gcc: 114 commits new c3a4c92feb5 189: onsuccess: #628: 2: Success after binutils/gcc: 281 commits new b2a914c25e8 190: onsuccess: #629: 2: Success after binutils/gcc: 34 commits new 15eaa1b3678 191: onsuccess: #630: 2: Success after binutils/gcc: 41 commits new 3514550575d 192: onsuccess: #1: 2: Success after binutils/gcc: 29 commits new 958db059fb0 193: onsuccess: #2: 2: Success after binutils/gcc: 19 commits new b44b43181c6 194: onsuccess: #3: 2: Success after binutils/gcc: 8 commits new 863ace956ed 195: onsuccess: #4: 2: Success after binutils/gcc: 7 commits new b4b6e0ffbc0 196: onsuccess: #5: 2: Success after binutils/gcc: 40 commits new f540a5229ff 197: onsuccess: #6: 2: Success after binutils/gcc: 47 commits new f9d9a091ce8 198: onsuccess: #7: 2: Success after binutils/gcc: 24 commits new a3edc311a15 199: onsuccess: #8: 2: Success after binutils/gcc: 40 commits new 178a1ea5cc4 200: onsuccess: #9: 2: Success after binutils/gcc: 53 commits new 70ceb786a17 201: onsuccess: #10: 2: Success after binutils/gcc: 17 commits new 6710e9e8c65 202: onsuccess: #11: 2: Success after binutils/gcc: 18 commits new b23e3de6920 203: onsuccess: #12: 2: Success after binutils/gcc: 27 commits new 4b6c36d4f99 204: force: #14: 2: Success after binutils: 17 commits new 9465205c2bf 205: force: #15: 0: Failure after gdb-13-branchpoint-1318-g [...] new 912041d8a56 206: onsuccess: #16: 0: Success after binutils: 17 commits new d7dde7ac769 207: onsuccess: #17: 2: Success after binutils/gcc: 55 commits new 53f5d38d9c9 208: onsuccess: #18: 2: Success after binutils/gcc: 33 commits new 23d28f7de37 209: onsuccess: #19: 2: Success after binutils/gcc: 57 commits new 7cdce7c90cb 210: onsuccess: #20: 2: Success after binutils/gcc: 15 commits new 5bcbbc8f047 211: onsuccess: #21: 2: Success after binutils/gcc: 15 commits new 996dee4331d 212: onsuccess: #22: 2: Success after binutils/gcc: 42 commits new fdd96421ea7 213: onsuccess: #23: 2: Success after binutils/gcc: 56 commits new 26706bab1bc 214: onsuccess: #24: 2: Success after binutils/gcc: 37 commits new a9e5360b34c 215: onsuccess: #25: 2: Success after binutils/gcc: 36 commits new fb9178585a6 216: onsuccess: #26: 2: Success after binutils/gcc: 45 commits new 1cf3d52e233 217: onsuccess: #27: 2: Success after binutils/gcc: 33 commits new 897e8f46dec 218: onsuccess: #29: 2: Success after binutils/gcc: 43 commits new ae451a795c3 219: onsuccess: #30: 2: Success after binutils/gcc: 40 commits new 7759bae4b22 220: onsuccess: #31: 2: Success after binutils/gcc: 38 commits new 13104f561d1 221: onsuccess: #32: 2: Success after binutils/gcc: 32 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 (97ba2716937) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1884 -> 1956 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2528 bytes 04-build_abe-binutils/console.log.xz | Bin 49460 -> 48752 bytes 05-build_abe-bootstrap_O3/console.log.xz | Bin 468476 -> 468896 bytes 06-check_regression/console.log.xz | Bin 3184 -> 3128 bytes 07-update_baseline/console.log | 38 +++++++++++++++---------------- 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 | 20 ++++++++-------- 13 files changed, 35 insertions(+), 35 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_aosp-code_size-aosp/oriole-master updated (346a8da77b9 -> 4f264ec6e0e)

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_aosp-code_size-aosp/oriole-master in repository toolchain/ci/base-artifacts. from 346a8da77b9 0: init: #21: 2: Success after baseline build: no new commits new 4f264ec6e0e 1: onsuccess: #23: 2: Success after aosp_superproject: 125 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 2300 -> 2144 bytes 01-reset_artifacts/patch-env.sh | 2 - 02-build_aosp_toolchain/console.log.xz | Bin 200976 -> 197728 bytes 03-build_shadow_llvm/console.log.xz | Bin 130780 -> 130212 bytes 04-build_aosp/console.log.xz | Bin 1327780 -> 1269532 bytes 06-check_regression/binary.regressions | 2 + 06-check_regression/console.log.xz | Bin 2088 -> 45044 bytes 06-check_regression/mail-body.txt | 13 +- .../results-vs-first.csv | 3004 ++++++++++---------- .../results-vs-prev.csv | 3004 ++++++++++---------- 06-check_regression/results.regressions | 1 + 07-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- size.csv => first-size.csv | 1756 ++++++------ git/aosp_superproject_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 15 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +- results | 1 + size.csv | 1756 ++++++------ 21 files changed, 4804 insertions(+), 4782 deletions(-) delete mode 100644 01-reset_artifacts/patch-env.sh create mode 100644 06-check_regression/binary.regressions copy size.csv => 06-check_regression/results-vs-first.csv (73%) copy size.csv => 06-check_regression/results-vs-prev.csv (73%) create mode 100644 06-check_regression/results.regressions copy size.csv => first-size.csv (99%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/llvm-aarch64-master-O2 updated (8ea4fa94cf0 -> ad8746370ab)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/llvm-aarch64-master-O2 in repository toolchain/ci/base-artifacts. from 8ea4fa94cf0 8: onsuccess: #12: 1: [TCWG CI] No change after llvm: 166 commits new ad8746370ab 9: onsuccess: #13: 1: [TCWG CI] No change after llvm: 403 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 1764 -> 1868 bytes 02-build_bmk_llvm/console.log.xz | Bin 104284 -> 102036 bytes 03-benchmark/benchmark-build.log | 144 +- 03-benchmark/benchmark.log | 142 +- 03-benchmark/console.log.xz | Bin 3988 -> 3944 bytes .../compare-results-vs-first-internal.csv | 133 +- .../compare-results-vs-prev-internal.csv | 183 +- 04-check_regression/console.log.xz | Bin 12060 -> 12172 bytes .../csv-results-vs-first-1/md5sum.csv | 2084 +- .../csv-results-vs-first-1/perf.csv | 2529 +- .../csv-results-vs-first-1/results.csv | 2974 +- .../csv-results-vs-first-1/size.csv | 191402 +++++++++--------- 04-check_regression/csv-results-vs-first-1/sve.csv | 20 +- .../csv-results-vs-prev-0/md5sum.csv | 2074 +- 04-check_regression/csv-results-vs-prev-0/perf.csv | 2608 +- .../csv-results-vs-prev-0/results.csv | 2902 +- 04-check_regression/csv-results-vs-prev-0/size.csv | 143213 ++++++------- 04-check_regression/csv-results-vs-prev-0/sve.csv | 18 +- .../csv-results-vs-prev-1/md5sum.csv | 2084 +- 04-check_regression/csv-results-vs-prev-1/perf.csv | 2529 +- .../csv-results-vs-prev-1/results.csv | 2974 +- 04-check_regression/csv-results-vs-prev-1/size.csv | 191402 +++++++++--------- 04-check_regression/csv-results-vs-prev-1/sve.csv | 20 +- .../output-bmk-results/exe.improvement.diff | 0 .../output-bmk-results/exe.regression.diff | 0 .../output-bmk-results/symbol.improvement.diff | 0 .../output-bmk-results/symbol.regression.diff | 0 04-check_regression/results-vs-first-brief.csv | 46 +- 04-check_regression/results-vs-first-full.csv | 2532 +- 04-check_regression/results-vs-first-internal.csv | 179 +- 04-check_regression/results-vs-first.csv | 179 +- 04-check_regression/results-vs-first.log | 1004 +- 04-check_regression/results-vs-prev-brief.csv | 48 +- 04-check_regression/results-vs-prev-compare.csv | 7 +- 04-check_regression/results-vs-prev-full.csv | 2690 +- 04-check_regression/results-vs-prev-internal.csv | 183 +- 04-check_regression/results-vs-prev.csv | 183 +- 04-check_regression/results-vs-prev.log | 1268 +- dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 10 +- .../500.perlbench_r/results-metrics.json | 2 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 10 +- .../503.bwaves_r/results-metadata.json | 10 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 10 +- .../507.cactuBSSN_r/results-metadata.json | 10 +- .../508.namd_r/results-metadata.json | 10 +- .../510.parest_r/results-metadata.json | 10 +- .../511.povray_r/results-metadata.json | 10 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 10 +- .../520.omnetpp_r/results-metadata.json | 10 +- .../squad-vs-first/521.wrf_r/results-metadata.json | 10 +- .../523.xalancbmk_r/results-metadata.json | 10 +- .../525.x264_r/results-metadata.json | 10 +- .../526.blender_r/results-metadata.json | 10 +- .../526.blender_r/results-metrics.json | 2 +- .../527.cam4_r/results-metadata.json | 10 +- .../531.deepsjeng_r/results-metadata.json | 10 +- .../531.deepsjeng_r/results-metrics.json | 2 +- .../538.imagick_r/results-metadata.json | 10 +- .../541.leela_r/results-metadata.json | 10 +- .../541.leela_r/results-metrics.json | 2 +- .../squad-vs-first/544.nab_r/results-metadata.json | 10 +- .../548.exchange2_r/results-metadata.json | 10 +- .../549.fotonik3d_r/results-metadata.json | 10 +- .../554.roms_r/results-metadata.json | 10 +- .../squad-vs-first/557.xz_r/results-metadata.json | 10 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 98 +- git/llvm_rev | 2 +- mail/jira-body.txt | 12 +- mail/mail-body.txt | 12 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results_id | 2 +- 74 files changed, 279304 insertions(+), 278842 deletions(-) delete mode 100644 04-check_regression/output-bmk-results/exe.improvement.diff delete mode 100644 04-check_regression/output-bmk-results/exe.regression.diff delete mode 100644 04-check_regression/output-bmk-results/symbol.improvement.diff delete mode 100644 04-check_regression/output-bmk-results/symbol.regression.diff -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (3fbeff66684 -> c4792bd1de0)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 3fbeff66684 testsuite: Xfail gcc.dg/tree-ssa/ssa-fre-100.c for ! natura [...] new c4792bd1de0 c++: constexpr PMF conversion [PR105996] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/cp/typeck.cc | 13 +++++-------- gcc/testsuite/g++.dg/cpp0x/constexpr-pmf3.C | 13 +++++++++++++ 2 files changed, 18 insertions(+), 8 deletions(-) create mode 100644 gcc/testsuite/g++.dg/cpp0x/constexpr-pmf3.C -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 updated (676a2dfa36d -> 18ef91f53b5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. discards 676a2dfa36d 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 33718ff48c5 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] discards 721070651a2 212: force: #45: 1: Success after gdb: 22 commits discards 539c73cb306 211: onsuccess: #44: 1: Success after linux: 26 commits discards 6962c12b82c 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] discards 701f90ab597 209: force: #37: 1: Success after baseline build: no new commits discards 7be32c24106 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 22e65d17e09 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards cbea1943e07 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 7fff02c3986 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards e499f7417dd 204: force: #26: : Failure after baseline build: no new commits discards f3745e43e27 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 9e71045f64c 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 019b521e02b 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 946278acd1d 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 694230570eb 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards f056c7f47e1 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 84d926d61ec 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 79ab5101e64 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 476188ef4de 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 74c053a8bee 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 2dbd39bb04f 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 0a4a8bc03fd 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 26902ec3a71 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 6e3daaf7b70 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards fcd8a4b2917 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 262cc6b7eec 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 1f68f408ab1 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards ad17c45f65c 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 30dbb9aee64 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards f0da3e7328f 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards 47b1992225a 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards 43ee6fcc89e 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards ee67736bb8d 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards 29f71c22964 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 5ce72244020 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards 3d87b2db340 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards 2505dafe883 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards c1d69851206 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards 5b65896b44e 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards 64015d0dc2a 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards cbb43d36cfa 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards 22614ee11e7 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards ce75b2a183b 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards 051dd5e3a36 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards fce3267068d 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards a6219a56b74 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards ab52fe32c5e 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards 8b2b81cd674 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 06dc1fcc481 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards 2663595e16e 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards e07c3bc2bfb 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards 4906ae6a340 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards 6b6fa44af0b 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards 0aa2fb7ad9d 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards d44eb24f557 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards bc619a20956 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 5433fdc61e7 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards b76c8ad9732 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards 8f520848f10 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 78caa6228e8 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 8ebde80cf0e 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 349bd004bdf 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 54c8ba01985 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 19cd02866e4 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards a35b84a61e7 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 0c805a08450 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 444fbf48a89 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards e45b83f170f 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 860fe65dd60 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 60a558aea3d 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards a05f6cf5610 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 896aed9bbda 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 549309d4458 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards e74be90e5a5 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards e23bdc726a3 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards aec2af564ca 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 11ca4c3b4c7 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards a8c4c13884f 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards 56ff421ad70 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 3a44f0161ae 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards d3a603811aa 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 5e4f3ef0c73 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 6f43486b1f3 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 95099a9eb09 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 118459a6189 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 63903513700 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards bb768091813 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 6cc0d0095b7 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards a36e6ad46af 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 689d47bfbd5 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 8753f8c778a 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 615701c2141 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 5671b5e5d74 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 661e772f3ae 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 205a8838338 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 25106cb60fa 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards 32e437c5cf3 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 51a85d3aed1 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards d2da3e0b462 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards 83de2595818 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 22a47d12cd4 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new cade53577a7 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new 76355ca2b80 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new afc01a5b01b 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new a3e80ce3f49 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new df902dcd6e2 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 2ddb268ac6f 120: onsuccess: #906: 1: Success after binutils: 29 commits new 73b5da8069b 121: onsuccess: #908: 1: Success after glibc: 2 commits new abf49f44673 122: onsuccess: #909: 1: Success after linux: 2753 commits new 85ec7e4236e 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 30f832da262 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 82169dde470 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new ff48a6332a5 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new cd30544fd2c 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 2dc1de60b34 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new 5764bcbb781 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new a2f06de278f 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 55a9b670fe6 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 228577b307e 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 61ad241c838 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new eb8432b53ed 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new e19e90e1b58 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new af7f7440a44 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 690be2eb051 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new 6e84f35c0dc 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new fafe782c71c 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new ed8f21b6fdb 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 3c1c704fc5a 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 7adcdce2a41 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new d4b13c87f5d 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 2e2ebd917eb 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new ae91f9bdb7d 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new d17eb3d9426 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 73fac70e821 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 0bb3298d915 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 1401f628cfd 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new 2e9ba18105f 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 9f78f5f97f5 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 6dcbd252af5 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 440ca96b9eb 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 739e2b3ebfc 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 6670e1f7a12 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 2baebd3366b 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new 8ffb5614055 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new f87e2cfc7e6 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new b698ff1d522 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new ebf1bed6f87 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new e63a80b59a7 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new 676b6f69f76 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new 9767f2f672f 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new d4a7d1ad3c2 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 82314b40f99 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new 62ec148ed59 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new 634b2ea739e 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new 864111d0c08 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new 36575bf5ec9 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new e57e17dc9c2 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 1e6a126f686 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new 793a7a33c57 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new 34ccaf0c778 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new 107b68fa6bc 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new 05e015db8a2 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new ceca8e4d095 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new ae5d2bf3b86 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new 4fe1d664ed8 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new 3908c28994a 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new 1d9995defb2 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new b9cf47697e0 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new 9a3ded47ac0 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new 0583ad73333 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new 56886d4b072 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new b8f6d907682 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 7ab124697c5 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 27768347f89 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new a222430b63e 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new b21c6c7a2e5 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 9f58d783712 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new f8d68639201 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 5f43d80a534 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 1f07544583b 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 9e16e36e5f7 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 94f4ab9e978 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new cdd42bf3a92 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new cebaff9bad7 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new ee304813c8b 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 8b0c7566e8f 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 666ea3eb682 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 25a73719768 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 818e5235cf4 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 6d57b0bf7f6 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 8418e656d9b 204: force: #26: : Failure after baseline build: no new commits new 2815545b670 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 29b2264b6a2 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new b6dafcaeccf 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 39d4412a487 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new c48c466fede 209: force: #37: 1: Success after baseline build: no new commits new ffaac2e42c1 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] new 05891301e86 211: onsuccess: #44: 1: Success after linux: 26 commits new aa6ce71a295 212: force: #45: 1: Success after gdb: 22 commits new a6323b68c7f 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] new aa94305402a 214: onsuccess: #47: 1: Success after gdb: 21 commits new 18ef91f53b5 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (676a2dfa36d) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2088 -> 1964 bytes 02-prepare_abe/console.log.xz | Bin 2488 -> 2516 bytes 03-build_abe-binutils/console.log.xz | Bin 35468 -> 35124 bytes 04-build_abe-gcc/console.log.xz | Bin 203728 -> 203404 bytes 06-build_abe-linux/console.log.xz | Bin 8460 -> 8480 bytes 07-build_abe-glibc/console.log.xz | Bin 242400 -> 241456 bytes 08-build_abe-gdb/console.log.xz | Bin 35048 -> 34732 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3780 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3088 -> 2764 bytes 11-check_regression/console.log.xz | Bin 5072 -> 5216 bytes 11-check_regression/results.compare | 75 -------------------- 11-check_regression/results.compare2 | 129 ++++++---------------------------- 12-update_baseline/console.log | 42 +++++------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 ++++---- sumfiles/gdb.log.0.xz | Bin 1949228 -> 1954392 bytes sumfiles/gdb.log.1.xz | Bin 21000 -> 20480 bytes sumfiles/gdb.log.2.xz | Bin 5420 -> 5412 bytes sumfiles/gdb.log.3.xz | Bin 5408 -> 5204 bytes sumfiles/gdb.sum | 16 ++--- sumfiles/gdb.sum.0 | 12 ++-- sumfiles/gdb.sum.1 | 25 ++++--- sumfiles/gdb.sum.2 | 4 +- sumfiles/gdb.sum.3 | 4 +- 31 files changed, 104 insertions(+), 249 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (08981d59253 -> 3fbeff66684)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 08981d59253 testsuite: Compile-only gcc.dg/tree-ssa/pr100359.c if ! nat [...] new 3fbeff66684 testsuite: Xfail gcc.dg/tree-ssa/ssa-fre-100.c for ! natura [...] 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/testsuite/gcc.dg/tree-ssa/ssa-fre-100.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (f58cbbb7c90 -> 08981d59253)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from f58cbbb7c90 Don't force target of modulo into a distinct register. new 08981d59253 testsuite: Compile-only gcc.dg/tree-ssa/pr100359.c if ! nat [...] 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/testsuite/gcc.dg/tree-ssa/pr100359.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-allyesconfig updated (8328e79367b -> 72f5f1f467a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-allyesconfig in repository toolchain/ci/base-artifacts. from 8328e79367b 74: onsuccess: #12: 21738: Success after binutils/llvm/linu [...] new 72f5f1f467a 75: onsuccess: #13: 21757: Success after binutils/llvm/linu [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1760 -> 2000 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2548 bytes 03-build_abe-binutils/console.log.xz | Bin 27180 -> 27456 bytes 04-build_kernel_llvm/console.log.xz | Bin 65740 -> 67676 bytes 05-build_abe-qemu/console.log.xz | Bin 32496 -> 32248 bytes 06-build_linux/console.log.xz | Bin 3372 -> 3548 bytes 08-check_regression/console.log.xz | Bin 4296 -> 4372 bytes 08-check_regression/mail-body.txt | 4 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 18 files changed, 29 insertions(+), 29 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch devel/omp/gcc-12 updated (9c18db65914 -> a63735b8034)

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/omp/gcc-12 in repository gcc. from 9c18db65914 Fortran: Add attr.class_ok check for generate_callback_wrapper new a63735b8034 Fortran/OpenMP: Fix 'alloc' and 'from' mapping for allocata [...] 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/fortran/ChangeLog.omp | 10 + gcc/fortran/trans-openmp.cc | 96 +++++++- libgomp/ChangeLog.omp | 4 + .../testsuite/libgomp.fortran/map-alloc-comp-8.f90 | 268 +++++++++++++++++++++ 4 files changed, 371 insertions(+), 7 deletions(-) create mode 100644 libgomp/testsuite/libgomp.fortran/map-alloc-comp-8.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

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

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards dbc5073212b 217: force: #45: 1: Success after linux: 1 commits discards cea68b942a4 216: force: #43: : Failure after baseline build: no new commits discards dccbaa559f3 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 8813c32db2a 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 302668e1c18 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards f9f8982c2b5 212: force: #27: : Failure after baseline build: no new commits discards 04b556c6fb3 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards a1c90007f20 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards d69a4fb8410 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 1c8b6844941 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards b981d06063a 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 2035d505463 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 6fb4a917ca2 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 730d7183734 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards f195cbdabc4 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 658a050bbcf 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 4b92e48c7d0 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 53073807105 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 6578237e34d 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 99104153d1d 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards f9fdc598522 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards d2672609a02 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards bfc6f34fb37 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards bdddfa7fc04 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 2d1e0b70c6d 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 83d98c2003e 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 7b89455e4cb 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 855269bf32e 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards d7f54d47a60 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards f5fd2dfa67b 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards ff8498e15a1 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 6c6058087fe 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards ee9df97d53c 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 4674d6415b4 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 4fc2d29a3b3 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards e75fc50fe56 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards b1191216c65 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 380e835759b 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 2f228c7a769 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 2faaa2f20c7 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 385cd6e2bb7 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards e6923459dc6 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 450df6c9262 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 95dd4c137cd 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards ce5c7f2dab8 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 857fac578b3 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards cf04f0f8225 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 4e8675123d7 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 4fde1a9a861 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 4e8308f512b 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards ab7a7b57b8c 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards d8c13e21083 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards a64a02afc0b 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards cab8932a0e9 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 713160c3b36 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards dbbe76ca3a8 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 9db898fc279 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards a9c739d783e 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 5357cde04d4 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 3ce6f18626b 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards d848e759871 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards ae3c24242f0 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards c016ce70531 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards f9556580f41 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards dd986c21cf1 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 19b689ba175 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards a720be7faf1 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 3f227461658 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 1a2cc29f9c9 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 162406d4fef 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 3c705012138 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards 984b55a4637 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards dd27fec8ba9 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 78ff073c446 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards fad6b0e4d5c 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards dde21164eae 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 42ce2ece36b 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards b932f31eabd 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards cbed528318a 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 7c0bec45fc5 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 55f314e5164 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 8d9e5c1dce9 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 1da4e441907 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 12d9c15cfc7 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 7802b665f61 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards f2c5ce7d58b 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 6991b5a032b 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards 5d20dabb57c 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards 065d31a96dd 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 82ed24c3244 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 7beafd65c75 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 6b22387cc5b 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards c75049c19d9 125: onsuccess: #614: 1: Success after linux: 12 commits discards c1e1a55e356 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 806494f7699 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards fec1df42e43 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards ac62bd43247 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 7f959ee4577 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards e76e6f38b2c 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards a9683c63728 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 31b4b4475e0 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new 47d7fd1d2a7 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new 56273677dff 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 52da933907f 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new a494311d269 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new fce5f1de1c4 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 99e3ed9471d 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new f06846c43f1 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 3d3d5e4d78d 124: onsuccess: #612: 1: Success after binutils: 18 commits new 03ffe5282f3 125: onsuccess: #614: 1: Success after linux: 12 commits new c085cd8086c 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 2fba6caca25 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 79a8ce55444 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 0e63c9a6858 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 9083f3e0f4e 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 77bb5ef11fd 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 79c6ed89196 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new a01c9b2dbee 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 21ecad44f19 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new d8149f5fb54 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 73dd29645ea 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new a14b8ef6456 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new a9500d907d3 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new b7bc9540ae5 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new f4698b96506 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 92ba4e632c5 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 413b9f62e53 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 2e07691f6f5 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 5fc1e4434a5 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new b55569286e0 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 98dcd280626 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 3207ce33ad2 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 751b3ad64ad 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 755ca60d52a 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 7bc92d8fb16 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new fa1e3845820 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 6edc229b083 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 5d477027aa9 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 1b32280c654 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 5d658824bbb 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 398850b30f3 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new b5993977ab6 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 6b0ead88823 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new bdec28b4dfb 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 3a276f5a8fa 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new e41e06728de 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 0ab0913ff57 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new fe87c0cd3aa 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 499019f063b 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 07876f18cfc 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new f9331250c6b 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new b29d512f85e 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 85566a3e71f 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new a0a7a69afd0 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 3f419ba6e4e 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new aeced05fc0a 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 018523d28a0 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 5413b7fd8dc 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 1c4ad314abc 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 2967953e14c 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 2cc7edb7c14 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 739e511c99f 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 088a8ff2b4f 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 5897a440eb8 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 6a785fa0de1 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new de0f6357dcf 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 9e8639e8991 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 343536495d0 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new bf26db6d1d3 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new b846d337a88 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 971c14c6aff 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new a502e23b90c 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new fca3cb986a8 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new fb9b14c3116 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new d6fca64daca 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 8aec99d28fb 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new b6b68951c94 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new f659d2647e9 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new d6fd0eb84e2 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 6f747a4b221 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 9d23a72c38a 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 7077345b988 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 4cd9e67d6bd 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 21e5ae73e45 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new f7d18ce4028 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 212086d898d 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new af42457880a 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 0950df0dbd7 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new c10071aaaf3 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 9417e7729aa 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new fe36572d5da 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 8c2da54faaf 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new e699d1d3524 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 14650a91100 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 65e4da196bc 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 44eb6f0c344 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new f8e1dc6ade8 212: force: #27: : Failure after baseline build: no new commits new 5996526e2c7 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 27ce6313635 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new 942284f256c 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new 78b211587d0 216: force: #43: : Failure after baseline build: no new commits new d088f8cffb2 217: force: #45: 1: Success after linux: 1 commits new 4f442b10fe1 218: force: #48: 1: Success after gdb-13-branchpoint-1471-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 (dbc5073212b) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1968 -> 2236 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2488 bytes 03-build_abe-binutils/console.log.xz | Bin 49128 -> 49020 bytes 04-build_abe-gcc/console.log.xz | Bin 236016 -> 235568 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8760 -> 8824 bytes 07-build_abe-glibc/console.log.xz | Bin 233460 -> 233700 bytes 08-build_abe-gdb/console.log.xz | Bin 47104 -> 46584 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3776 -> 3768 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4724 -> 4416 bytes 11-check_regression/console.log.xz | Bin 2696 -> 3352 bytes 11-check_regression/mail-body.txt | 15 +- 11-check_regression/results.compare | 30 + 11-check_regression/results.compare2 | 1 + 12-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 17 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/gdb.log.0.xz | Bin 2936808 -> 2961736 bytes sumfiles/gdb.log.1.xz | Bin 143060 -> 139020 bytes sumfiles/gdb.log.10.xz | Bin 10356 -> 0 bytes sumfiles/gdb.log.11.xz | Bin 10340 -> 0 bytes sumfiles/gdb.log.12.xz | Bin 10144 -> 0 bytes sumfiles/gdb.log.13.xz | Bin 10120 -> 0 bytes sumfiles/gdb.log.2.xz | Bin 21016 -> 12340 bytes sumfiles/gdb.log.3.xz | Bin 19484 -> 10256 bytes sumfiles/gdb.log.4.xz | Bin 10264 -> 10240 bytes sumfiles/gdb.log.5.xz | Bin 10280 -> 10312 bytes sumfiles/gdb.log.6.xz | Bin 10204 -> 10184 bytes sumfiles/gdb.log.7.xz | Bin 10072 -> 0 bytes sumfiles/gdb.log.8.xz | Bin 10260 -> 0 bytes sumfiles/gdb.log.9.xz | Bin 10340 -> 0 bytes sumfiles/gdb.sum | 73 +- sumfiles/gdb.sum.0 | 88 +- sumfiles/gdb.sum.1 | 464 +++---- sumfiles/gdb.sum.10 | 2215 --------------------------------- sumfiles/gdb.sum.11 | 2164 -------------------------------- sumfiles/gdb.sum.12 | 2189 -------------------------------- sumfiles/gdb.sum.13 | 2173 -------------------------------- sumfiles/gdb.sum.2 | 490 +------- sumfiles/gdb.sum.3 | 537 ++------ sumfiles/gdb.sum.4 | 32 +- sumfiles/gdb.sum.5 | 27 +- sumfiles/gdb.sum.6 | 47 +- sumfiles/gdb.sum.7 | 2138 ------------------------------- sumfiles/gdb.sum.8 | 2179 -------------------------------- sumfiles/gdb.sum.9 | 2178 -------------------------------- 50 files changed, 456 insertions(+), 16667 deletions(-) create mode 100644 11-check_regression/results.compare create mode 100644 11-check_regression/results.compare2 delete mode 100644 sumfiles/gdb.log.10.xz delete mode 100644 sumfiles/gdb.log.11.xz delete mode 100644 sumfiles/gdb.log.12.xz delete mode 100644 sumfiles/gdb.log.13.xz delete mode 100644 sumfiles/gdb.log.7.xz delete mode 100644 sumfiles/gdb.log.8.xz delete mode 100644 sumfiles/gdb.log.9.xz delete mode 100644 sumfiles/gdb.sum.10 delete mode 100644 sumfiles/gdb.sum.11 delete mode 100644 sumfiles/gdb.sum.12 delete mode 100644 sumfiles/gdb.sum.13 delete mode 100644 sumfiles/gdb.sum.7 delete mode 100644 sumfiles/gdb.sum.8 delete mode 100644 sumfiles/gdb.sum.9 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits March 2023