Tcwg-commits April 2023

tcwg-commits@lists.linaro.org

5 participants
5583 discussions

[toolchain/ci/interesting-commits] branch master updated (2e491a89 -> 5bd3d445)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from 2e491a89 Add entry 9d1a6119590ef828f9782a7083d03e535bc2f2cf from https [...] new 5bd3d445 Add entry b8d1a3a8ef9aff015ae963522287f7785bc552ec from https [...] 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: .../tcwg_gnu_native_fast_check_gcc/master-arm/build_url | 2 +- .../master-arm}/last_good | 0 .../master-arm/summary.txt | 8 ++++---- .../tcwg_gnu_native_fast_check_gcc/status.txt | 17 +++++++++++++++++ 4 files changed, 22 insertions(+), 5 deletions(-) copy {gcc/sha1/040e64b09d4422c7d3c51bee098043782112b924 => gdb/sha1/b8d1a3a8ef9aff [...] copy {binutils/sha1/b8d1a3a8ef9aff015ae963522287f7785bc552ec/tcwg_gnu_native_check [...] copy {binutils/sha1/aa2306fbfe2748854439c1ace9ec733560a0746c => gdb/sha1/b8d1a3a8e [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[linux] branch x86-rep-insns updated (fd1374c9159d -> 20f6aee7b9d8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch x86-rep-insns in repository linux. from fd1374c9159d x86: inline the 'rep movs' in user copies for the FSRM case new 20f6aee7b9d8 x86: improve on the non-rep 'clear_user_original' 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: arch/x86/lib/clear_page_64.S | 107 ++++++++++++++++++++++++++----------------- 1 file changed, 65 insertions(+), 42 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (309bd39bb7 -> 83b6a2b80c)

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_binutils/master-arm in repository toolchain/ci/base-artifacts. discards 309bd39bb7 248: force: #75: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 6d53a789ab 247: force: #73: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards aa961c5b1b 246: force: #71: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards c05311f281 245: force: #69: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards ab12e2bd51 244: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 41895bb8b0 243: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards f0c4b22271 242: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards d12cacb3e4 241: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 39fb20bdf7 240: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards c7fb670091 239: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 54a78566a7 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards a72005d506 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards d355fd2bae 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 25ca38c404 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards cb37ce116c 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 301eedfb2d 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 0d985a800a 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards e781e7107f 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 128a09f086 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards aaea2c3f66 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 6a4eee6b03 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 8401314823 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 78d0ad2cee 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 6b870d9a08 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 1ba84a5087 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards f7346eeead 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards a996b59210 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 3146e5dd79 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards c5dedb3ceb 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 7ec363cd07 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 6d18ad2dc9 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards c2eda3e002 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards edb9607183 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards bb13d76dc3 215: onsuccess: #26: 1: Success after binutils: 10 commits discards b99037b9be 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards 567b985742 213: force: #24: 1: Success after binutils: 2 commits discards 1b38460793 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 290c15db65 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards d0b0c10317 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 69940a9525 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 512ed9accc 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 348d1c9f43 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards ea0f926028 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 8037e2538e 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 9ed9fcfd55 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards c43f5c842f 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 879583d7dd 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 255ba2fe5d 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 0c5631c2a3 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 504d827368 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 37b9cc08ac 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 663cc90c26 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards dee6eadc86 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 10cf2fed88 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 4be9668621 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 64319d3aff 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards ea7180b4d7 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards f15523b955 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] discards 1c81c7cb72 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards b108fd72a7 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] discards 196454ffb0 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards f8d7ec36ee 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] discards db87077a07 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards ca119e66d7 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards 436b51afdf 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] discards 60bcdd7160 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] discards 71256d7d58 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards b3d090ad4b 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards 854cce361d 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 49e9de4cff 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 2b183975c3 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards 3afcf16661 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 7c41040aa6 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 38f8743834 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] discards 949075c6c0 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 8552cdd657 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 2e13f74486 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 92c8501f45 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 9051e34d0d 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 5c0f4816e6 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] discards 9c75bd0a71 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 5f0122fc85 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 4435ccb89c 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards f664c4a982 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 94107cf0c4 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 9be4746625 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards d361f64ba7 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 8829b12242 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards 78e0a8ce87 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] discards 8cc918ec39 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards de02894e14 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] discards 8152a31b4a 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] discards 3f3145c6f1 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 6187ac1ddb 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards 64913b94f5 154: onsuccess: #583: 1: Success after linux: 10 commits discards 5716b5d767 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 4c37fea7e2 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 4961baeb5f 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 4b54560dcb 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards 0453b831c4 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 10cf5bbecd 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] new b631bcf862 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] new 694fe34280 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 7f9283ab2e 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new 4da7b9c326 151: onsuccess: #579: 1: Success after binutils: 21 commits new 2a66cf80f1 152: onsuccess: #580: 1: Success after gcc: 6 commits new 99dbf2b33b 153: onsuccess: #582: 1: Success after glibc: 9 commits new c6b6cfd9b0 154: onsuccess: #583: 1: Success after linux: 10 commits new 4898e58c39 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 6edcf80389 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new cd5a561181 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] new 74aec838d7 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] new 8d43954360 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 62499ff55e 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] new d0c7c7366b 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new 39df231958 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 3516b3731d 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new df1c755510 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 2b72bf3cf5 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 2cce78aec4 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 208aa3b61f 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 575142ebc4 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 6e7635db19 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] new 2149edb8ff 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new e580a7c33d 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new d4aba83262 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 463f3120fe 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 0af535a3a1 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new e916411dec 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] new e6ec3a13fa 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new fc41437b3f 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new f6406c5e76 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new 511a4a63be 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 05e05d9408 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new cd3b899cd4 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 7d504bb486 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new 3b7e247cad 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] new c96d7866e9 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] new 7461c9fb50 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new 3be69ca391 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 4028dd7266 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] new f4c34b7b04 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 6f397c7ee1 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] new 19505d2d72 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new c9331f8c59 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] new 4ec2737b13 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new 66bd46dc73 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 04157d48a1 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new e390d6fe4b 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new b58eeb10b2 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new cdc754228c 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new a86c202ffd 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 4a3da0ddb2 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 40f9c29ef0 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 6a162d52c9 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 6554e40b83 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 038cf473d7 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 1758e12d58 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 325efbaa60 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 3e592d1a47 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 1a35ce5dfd 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new a7d351353c 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 0a16087592 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 521b6fff39 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 6a3032ed2b 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 50bc5c9b86 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 69d37bf945 213: force: #24: 1: Success after binutils: 2 commits new 760ec4ade7 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new 6712e46fd0 215: onsuccess: #26: 1: Success after binutils: 10 commits new 73477a20e1 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new a13ae36960 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 3d3285a84e 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 9abe526e7e 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 1ce91139cf 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 9c265420b1 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 5e028adf82 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 22de5621f8 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new b99095e4be 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new d776e286a9 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 38034d95b5 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new df34bbdb8c 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 577ac73690 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new b8fa45fead 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 65128ff563 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 24ccbb987a 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 3de9622c78 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 999339f6d3 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new bb245d1452 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 2021e88521 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 2d19a099ea 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 46099b92e8 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 581a0025f6 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new cd6e0e3f31 239: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 1f69833b7d 240: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new d69347f3d0 241: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new e202ab24f5 242: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 97c4ac6767 243: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 9701dd5508 244: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 40c485718c 245: force: #69: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 3da8fa08fa 246: force: #71: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 5b90718909 247: force: #73: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new a701f84b62 248: force: #75: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 83b6a2b80c 249: force: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] 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 (309bd39bb7) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] 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 2184 -> 2212 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 49392 -> 49456 bytes 04-build_abe-gcc/console.log.xz | Bin 238376 -> 235704 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8680 -> 8632 bytes 07-build_abe-glibc/console.log.xz | Bin 232572 -> 232764 bytes 08-build_abe-gdb/console.log.xz | Bin 47144 -> 46600 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3824 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2456 -> 2424 bytes 11-check_regression/console.log.xz | Bin 1604 -> 1604 bytes 11-check_regression/results.compare | 8 +++--- 11-check_regression/results.regressions | 8 +++--- 11-check_regression/trigger-bisect | 4 +-- 12-update_baseline/console.log | 44 ++++++++++++++--------------- git/gcc_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 8 +++--- mail/results.regressions | 8 +++--- manifest.sh | 8 +++--- results | 8 +++--- sumfiles/binutils.log.xz | Bin 62456 -> 62084 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100584 -> 100672 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132312 -> 132312 bytes sumfiles/ld.sum | 2 +- 27 files changed, 54 insertions(+), 54 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/interesting-commits] branch master updated (ccb167f0 -> 2e491a89)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from ccb167f0 Add entry 2ab0d83e8880fe747af3f137aef382d2d4c09e4c from https [...] new 2e491a89 Add entry 9d1a6119590ef828f9782a7083d03e535bc2f2cf from https [...] 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/basepoints/gcc-13-7178-g9d1a6119590 | 1 + .../master-arm/build_url | 2 +- .../master-arm/last_good | 1 + .../master-arm/summary.txt | 6 +- .../tcwg_gnu_native_check_binutils/status.txt | 79 ++++++++++++++++++++++ 5 files changed, 85 insertions(+), 4 deletions(-) create mode 120000 gcc/basepoints/gcc-13-7178-g9d1a6119590 copy {binutils/sha1/b8d1a3a8ef9aff015ae963522287f7785bc552ec => gcc/sha1/9d1a61195 [...] create mode 100644 gcc/sha1/9d1a6119590ef828f9782a7083d03e535bc2f2cf/tcwg_gnu_nati [...] copy gcc/sha1/{2134fcfee8b338a6f10273457145fc071dc8f092 => 9d1a6119590ef828f9782a7 [...] create mode 100644 gcc/sha1/9d1a6119590ef828f9782a7083d03e535bc2f2cf/tcwg_gnu_nati [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-cpu2017fast/gnu-aarch64-master-O3 updated (631f1f3696 -> 8cf52cded7)

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_size-cpu2017fast/gnu-aarch64-master-O3 in repository toolchain/ci/base-artifacts. from 631f1f3696 4: onsuccess: #7: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new 8cf52cded7 5: onsuccess: #8: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] 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 2152 -> 2136 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2536 bytes 03-build_abe-binutils/console.log.xz | Bin 27340 -> 27108 bytes 04-build_abe-stage1/console.log.xz | Bin 71148 -> 71092 bytes 06-build_abe-linux/console.log.xz | Bin 7572 -> 8356 bytes 07-build_abe-glibc/console.log.xz | Bin 242436 -> 241760 bytes 08-build_abe-stage2/console.log.xz | Bin 175168 -> 176324 bytes 09-benchmark/benchmark-build.log | 117 +- 09-benchmark/benchmark.log | 115 +- 09-benchmark/console.log.xz | Bin 4124 -> 4120 bytes 10-check_regression/bmk-specific-variability.csv | 103 +- 10-check_regression/console.log.xz | Bin 10152 -> 11620 bytes .../results_id.first | 0 git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 32 +- results-vs-first/compare-results-internal.csv | 206 +- results-vs-first/csv-results-0/md5sum.csv | 1868 +- results-vs-first/csv-results-0/results.csv | 1003738 ++++++++-------- results-vs-first/csv-results-0/size.csv | 1003880 ++++++++--------- results-vs-first/csv-results-0/sve.csv | 29458 +- results-vs-first/csv-results-0/vect.csv | 10626 +- results-vs-first/csv-results-1/md5sum.csv | 2737 +- results-vs-first/csv-results-1/perf.csv | 2656 +- results-vs-first/csv-results-1/results.csv | 1000500 ++++++++-------- results-vs-first/csv-results-1/size.csv | 1000546 ++++++++-------- results-vs-first/csv-results-1/sve.csv | 29666 +- results-vs-first/csv-results-1/vect.csv | 9352 +- results-vs-first/interesting-symbols.csv | 18 +- results-vs-first/results-brief.csv | 52 +- results-vs-first/results-full.csv | 2776 +- results-vs-first/results-internal.csv | 204 +- results-vs-first/results.csv | 204 +- results-vs-first/tcwg-benchmark-results.log | 2280 +- results-vs-prev/compare-results-internal.csv | 197 +- results-vs-prev/compare-results.csv | 31 +- results-vs-prev/csv-results-0/md5sum.csv | 2328 +- results-vs-prev/csv-results-0/perf.csv | 2553 +- results-vs-prev/csv-results-0/results.csv | 947824 ++++++++-------- results-vs-prev/csv-results-0/size.csv | 947789 ++++++++-------- results-vs-prev/csv-results-0/sve.csv | 29268 +- results-vs-prev/csv-results-0/vect.csv | 10636 +- results-vs-prev/csv-results-1/md5sum.csv | 2737 +- results-vs-prev/csv-results-1/perf.csv | 2656 +- results-vs-prev/csv-results-1/results.csv | 1000500 ++++++++-------- results-vs-prev/csv-results-1/size.csv | 1000546 ++++++++-------- results-vs-prev/csv-results-1/sve.csv | 29666 +- results-vs-prev/csv-results-1/vect.csv | 9352 +- results-vs-prev/interesting-symbols.csv | 18 +- results-vs-prev/results-brief.csv | 52 +- results-vs-prev/results-full.csv | 2980 +- results-vs-prev/results-internal.csv | 206 +- results-vs-prev/results.csv | 206 +- results-vs-prev/tcwg-benchmark-results.log | 2654 +- results_id | 2 +- 58 files changed, 4103582 insertions(+), 3989763 deletions(-) rename results_id.first => 10-check_regression/results_id.first (100%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gcc/master-aarch64 updated (fd2d23a431 -> f5a6b9e1bb)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. from fd2d23a431 43: force: #70: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new f5a6b9e1bb 44: force: #72: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] 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 2116 -> 2208 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2520 bytes 03-build_abe-binutils/console.log.xz | Bin 36128 -> 36048 bytes 04-build_abe-gcc/console.log.xz | Bin 204060 -> 203828 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8616 -> 8680 bytes 07-build_abe-glibc/console.log.xz | Bin 241368 -> 241152 bytes 08-build_abe-gdb/console.log.xz | Bin 35568 -> 35624 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3824 bytes 10-build_abe-check_gcc/console.log.xz | Bin 9848 -> 9604 bytes 11-check_regression/console.log.xz | Bin 1696 -> 1664 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.regressions | 16 +- 11-check_regression/trigger-bisect | 4 +- .../trigger-notify | 0 git/gcc_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 16 +- mail/results.regressions | 16 +- manifest.sh | 8 +- results | 16 +- sumfiles/g++.log.sep.xz | Bin 1436 -> 1436 bytes sumfiles/g++.log.xz | Bin 1408 -> 1408 bytes sumfiles/g++.sum | 2 +- sumfiles/g++.sum.sep | 4 +- sumfiles/gcc.log.sep.xz | Bin 4988 -> 6044 bytes sumfiles/gcc.log.xz | Bin 370624 -> 371968 bytes sumfiles/gcc.sum | 2 +- sumfiles/gcc.sum.sep | 746 ++++++++++++--------- sumfiles/gfortran.log.sep.xz | Bin 1444 -> 1444 bytes sumfiles/gfortran.log.xz | Bin 55328 -> 55304 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 4 +- sumfiles/libatomic.log.xz | Bin 436 -> 436 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 432 -> 432 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 432 -> 432 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 440 -> 440 bytes sumfiles/libstdc++.log.xz | Bin 424 -> 424 bytes sumfiles/libstdc++.sum.sep | 2 +- 42 files changed, 501 insertions(+), 363 deletions(-) copy 12-update_baseline/console.log => 11-check_regression/trigger-notify (100%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/interesting-commits] branch master updated (254b78b2 -> ccb167f0)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from 254b78b2 Add entry e10d82fc3ed03ee03f7c831a5b1e73c6c5ed3722 from https [...] new ccb167f0 Add entry 2ab0d83e8880fe747af3f137aef382d2d4c09e4c from https [...] 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/basepoints/gcc-13-7185-g2ab0d83e888 | 1 + .../master-aarch64/build_url | 2 +- .../master-aarch64/last_good | 1 + .../master-aarch64/summary.txt | 15 +++++++++ .../tcwg_gnu_native_fast_check_gcc/status.txt | 37 ++++++++++++++++++++++ 5 files changed, 55 insertions(+), 1 deletion(-) create mode 120000 gcc/basepoints/gcc-13-7185-g2ab0d83e888 copy {binutils/gcc/linux/glibc/gdb/sha1 => gcc/sha1/2ab0d83e8880fe747af3f137aef382 [...] create mode 100644 gcc/sha1/2ab0d83e8880fe747af3f137aef382d2d4c09e4c/tcwg_gnu_nati [...] create mode 100644 gcc/sha1/2ab0d83e8880fe747af3f137aef382d2d4c09e4c/tcwg_gnu_nati [...] create mode 100644 gcc/sha1/2ab0d83e8880fe747af3f137aef382d2d4c09e4c/tcwg_gnu_nati [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto updated (71e583d19c -> 0876cec337)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto in repository toolchain/ci/base-artifacts. discards 71e583d19c 236: onsuccess: #56: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards 6ed3acfb2f 235: onsuccess: #55: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards 90930e3d16 234: onsuccess: #54: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards 29d6f72a1c 233: onsuccess: #53: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards bfa8b7008f 232: onsuccess: #52: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards 199a43b957 231: onsuccess: #51: 2: [TCWG CI] Success after binutils/gcc [...] discards a3d27d2709 230: onsuccess: #50: 2: [TCWG CI] Success after binutils/gcc [...] discards 49ca37ec66 229: onsuccess: #49: 2: [TCWG CI] Success after binutils/gcc [...] discards 25a61ec183 228: onsuccess: #48: 2: [TCWG CI] Success after binutils/gcc [...] discards 046a2ea828 227: onsuccess: #46: 2: [TCWG CI] Success after binutils/gcc [...] discards 21a960d2a7 226: onsuccess: #45: 2: [TCWG CI] Success after binutils/gcc [...] discards bdcfcd0dd6 225: onsuccess: #44: 2: [TCWG CI] Success after binutils/gcc [...] discards 371b1cfa0b 224: onsuccess: #43: 2: [TCWG CI] Success after binutils/gcc [...] discards 54b17a89f0 223: onsuccess: #42: 2: [TCWG CI] Success after binutils/gcc [...] discards e608eb0f10 222: onsuccess: #41: 2: [TCWG CI] Success after binutils/gcc [...] discards 8119cfccad 221: onsuccess: #40: 2: [TCWG CI] Success after binutils/gcc [...] discards 3eba9efc11 220: onsuccess: #39: 1: [TCWG CI] Success after gcc: 2 commits discards 8a1fd96ac3 219: force: #38: 1: [TCWG CI] Failure after basepoints/gcc-1 [...] discards e19b7de71e 218: force: #37: 2: [TCWG CI] Success after gcc: 40 commits discards 284b908ae6 217: onsuccess: #35: 2: [TCWG CI] Success after binutils: 59 [...] discards 71f8002911 216: onsuccess: #32: 2: Success after binutils/gcc: 5 commits discards 58d3138282 215: onsuccess: #31: 2: Success after binutils/gcc: 7 commits discards 190d5cfd51 214: onsuccess: #30: 2: Success after binutils/gcc: 34 commits discards fdc139d2b9 213: onsuccess: #29: 2: Success after binutils/gcc: 36 commits discards c6f49fc142 212: onsuccess: #28: 2: Success after binutils/gcc: 34 commits discards a3035fc15c 211: onsuccess: #27: 2: Success after binutils/gcc: 41 commits discards b1749a0615 210: onsuccess: #26: 2: Success after binutils/gcc: 27 commits discards c1a2e45866 209: onsuccess: #25: 2: Success after binutils/gcc: 12 commits discards fb3de89e00 208: onsuccess: #24: 2: Success after binutils/gcc: 44 commits discards 6f0cfc6c62 207: onsuccess: #23: 2: Success after binutils/gcc: 75 commits discards 30631b0a07 206: onsuccess: #21: 2: Success after binutils/gcc: 38 commits discards f6a2c90f2b 205: onsuccess: #20: 2: Success after binutils/gcc: 59 commits discards 150b9aaed2 204: onsuccess: #19: 2: Success after binutils/gcc: 39 commits discards 75e8c096ce 203: onsuccess: #18: 2: Success after binutils/gcc: 9 commits discards 1b8f263f23 202: onsuccess: #17: 2: Success after binutils/gcc: 25 commits discards cec58905b4 201: onsuccess: #16: 2: Success after binutils/gcc: 55 commits discards e06cd8ce41 200: onsuccess: #15: 2: Success after binutils/gcc: 26 commits discards 24612b44af 199: onsuccess: #14: 2: Success after binutils/gcc: 31 commits discards e3e3f454f7 198: onsuccess: #13: 2: Success after binutils/gcc: 58 commits discards ecae16bdf6 197: onsuccess: #12: 2: Success after binutils/gcc: 29 commits discards 115e44913a 196: onsuccess: #11: 2: Success after binutils/gcc: 16 commits discards fba6c3ac01 195: onsuccess: #10: 2: Success after binutils/gcc: 28 commits discards 49b440e482 194: onsuccess: #9: 2: Success after binutils/gcc: 48 commits discards a7e2c9ba2c 193: onsuccess: #8: 2: Success after binutils/gcc: 37 commits discards 06cb1e47e0 192: onsuccess: #7: 2: Success after binutils/gcc: 22 commits discards b988b8b11c 191: onsuccess: #6: 2: Success after binutils/gcc: 65 commits discards 00dfb33839 190: onsuccess: #5: 2: Success after binutils/gcc: 23 commits discards dd9d8f281a 189: onsuccess: #4: 2: Success after binutils/gcc: 8 commits discards 692761bd12 188: onsuccess: #3: 2: Success after binutils/gcc: 5 commits discards 80c90a9cfe 187: onsuccess: #2: 2: Success after binutils/gcc: 22 commits discards d8106a2249 186: onsuccess: #1: 2: Success after binutils/gcc: 54 commits discards 406ac0dc76 185: onsuccess: #605: 2: Success after binutils/gcc: 38 commits discards e28357c90c 184: onsuccess: #604: 2: Success after binutils/gcc: 138 commits discards 3a59221dd2 183: onsuccess: #603: 2: Success after binutils/gcc: 33 commits discards 796c44b096 182: onsuccess: #602: 2: Success after binutils/gcc: 32 commits discards 0d1ccf7e34 181: onsuccess: #601: 2: Success after binutils/gcc: 13 commits discards be0a1c5eba 180: onsuccess: #600: 2: Success after binutils/gcc: 32 commits discards 8b73e12a1f 179: onsuccess: #599: 2: Success after binutils/gcc: 27 commits discards 7773671915 178: onsuccess: #598: 2: Success after binutils/gcc: 54 commits discards 7b76c0b607 177: onsuccess: #597: 2: Success after binutils/gcc: 86 commits discards b285546852 176: onsuccess: #596: 2: Success after binutils/gcc: 84 commits discards 29fd2630b5 175: onsuccess: #595: 2: Success after binutils/gcc: 30 commits discards b5c29b0c48 174: onsuccess: #594: 2: Success after binutils/gcc: 147 commits discards 3451d80251 173: onsuccess: #593: 2: Success after binutils/gcc: 74 commits discards e5a20c3906 172: onsuccess: #592: 2: Success after binutils/gcc: 57 commits discards 9301eecca7 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits discards 5d78635571 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits discards a0bd0f9e45 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits discards 74806f8b1d 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits discards 61debeba6a 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits discards ff13040191 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits discards 818cd9a470 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits discards faa14de529 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits discards 7dd92ee079 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits discards 3c6fb6eb15 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits discards b3ec531838 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits discards b77ed91c2e 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits discards ac76525dc8 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits discards e1a181c3b5 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits discards 524f97c362 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits discards 93a4469623 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits discards 093a474a93 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits discards 3427fd365c 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits discards 41ad5b28d3 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits discards b3ca726f28 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits discards 37bf410bf1 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits discards be08664c7f 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits discards cd1bcb6cf6 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits discards b07c9aa82f 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits discards 4815f895dd 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits discards 14f9cd45a0 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits discards fa12caae9c 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits discards 28fe3c2fba 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits discards 50b1b1ef95 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits discards 46e9660450 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits discards ff81131963 141: onsuccess: #559: 1: Success after gcc: 4 commits discards a42da5c1e4 140: force: #558: 1: Failure after basepoints/gcc-13-4953-g3 [...] discards 024272cb75 139: force: #557: 2: Success after gcc: 6 commits discards 3f9308cbc0 138: onsuccess: #554: 2: Success after binutils: 10 commits discards d07515bcb5 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits discards 0b98afbe95 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits new 909ac2d029 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits new 2391b98547 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits new 270c9c6e9c 138: onsuccess: #554: 2: Success after binutils: 10 commits new c55e21e687 139: force: #557: 2: Success after gcc: 6 commits new c5f4b27372 140: force: #558: 1: Failure after basepoints/gcc-13-4953-g3 [...] new 452bafcb05 141: onsuccess: #559: 1: Success after gcc: 4 commits new b22d6f4f86 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits new 8fc5896143 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits new e4619181b1 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits new 531ad85036 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits new 1162083a6a 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits new 32360328bc 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits new 731a569301 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits new 20c200cc3b 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits new c0de17c3d2 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits new e7cf9467ff 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits new e5715e4cfe 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits new 7521ff299d 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits new b0e566aecb 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits new c48a97d12c 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits new 4690a9ff50 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits new c68401cd8e 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits new ce37965519 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits new db8c7ea93d 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits new 014cc964be 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits new 73ff9ea33e 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits new a619bcfd2b 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits new b49b5abcc5 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits new 0b8e82d472 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits new 1d430b076e 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits new 398a146128 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits new b51f234011 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits new 074329087c 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits new 9317f0e265 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits new 3ab21c6021 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits new 300492d74b 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits new 01e898079b 172: onsuccess: #592: 2: Success after binutils/gcc: 57 commits new 1a8e9336c9 173: onsuccess: #593: 2: Success after binutils/gcc: 74 commits new ce172dd76d 174: onsuccess: #594: 2: Success after binutils/gcc: 147 commits new 06e2005998 175: onsuccess: #595: 2: Success after binutils/gcc: 30 commits new 27dab17c7e 176: onsuccess: #596: 2: Success after binutils/gcc: 84 commits new 63158a4939 177: onsuccess: #597: 2: Success after binutils/gcc: 86 commits new b98791736b 178: onsuccess: #598: 2: Success after binutils/gcc: 54 commits new 8eb4cf417e 179: onsuccess: #599: 2: Success after binutils/gcc: 27 commits new 36ddb52bd5 180: onsuccess: #600: 2: Success after binutils/gcc: 32 commits new 0f626cd23e 181: onsuccess: #601: 2: Success after binutils/gcc: 13 commits new 3aa770267f 182: onsuccess: #602: 2: Success after binutils/gcc: 32 commits new 16f7d925d3 183: onsuccess: #603: 2: Success after binutils/gcc: 33 commits new 05aeea373c 184: onsuccess: #604: 2: Success after binutils/gcc: 138 commits new a86bb8a9fd 185: onsuccess: #605: 2: Success after binutils/gcc: 38 commits new aaff27d88e 186: onsuccess: #1: 2: Success after binutils/gcc: 54 commits new 935d590f4b 187: onsuccess: #2: 2: Success after binutils/gcc: 22 commits new 84a9e87d4b 188: onsuccess: #3: 2: Success after binutils/gcc: 5 commits new dff5775b48 189: onsuccess: #4: 2: Success after binutils/gcc: 8 commits new 75cda5640c 190: onsuccess: #5: 2: Success after binutils/gcc: 23 commits new ceff2f4220 191: onsuccess: #6: 2: Success after binutils/gcc: 65 commits new 9265e03bd5 192: onsuccess: #7: 2: Success after binutils/gcc: 22 commits new ebeee59320 193: onsuccess: #8: 2: Success after binutils/gcc: 37 commits new d9fa44d930 194: onsuccess: #9: 2: Success after binutils/gcc: 48 commits new 34558349a5 195: onsuccess: #10: 2: Success after binutils/gcc: 28 commits new 5c84b9b77f 196: onsuccess: #11: 2: Success after binutils/gcc: 16 commits new 1dca8ea8e5 197: onsuccess: #12: 2: Success after binutils/gcc: 29 commits new aa2d5c74c3 198: onsuccess: #13: 2: Success after binutils/gcc: 58 commits new c7cdee6588 199: onsuccess: #14: 2: Success after binutils/gcc: 31 commits new 1e29e45aa7 200: onsuccess: #15: 2: Success after binutils/gcc: 26 commits new 95267e45c2 201: onsuccess: #16: 2: Success after binutils/gcc: 55 commits new 0282c55550 202: onsuccess: #17: 2: Success after binutils/gcc: 25 commits new 70ff8bac5a 203: onsuccess: #18: 2: Success after binutils/gcc: 9 commits new b7cbe25977 204: onsuccess: #19: 2: Success after binutils/gcc: 39 commits new ccf0672f75 205: onsuccess: #20: 2: Success after binutils/gcc: 59 commits new deba2c503a 206: onsuccess: #21: 2: Success after binutils/gcc: 38 commits new 528217fe18 207: onsuccess: #23: 2: Success after binutils/gcc: 75 commits new 5baa271297 208: onsuccess: #24: 2: Success after binutils/gcc: 44 commits new bb821c9209 209: onsuccess: #25: 2: Success after binutils/gcc: 12 commits new 6f6ede555f 210: onsuccess: #26: 2: Success after binutils/gcc: 27 commits new 0596df8f36 211: onsuccess: #27: 2: Success after binutils/gcc: 41 commits new 0e1da93a62 212: onsuccess: #28: 2: Success after binutils/gcc: 34 commits new 6fc0f20291 213: onsuccess: #29: 2: Success after binutils/gcc: 36 commits new 19cd75f4b1 214: onsuccess: #30: 2: Success after binutils/gcc: 34 commits new 7a1cc91599 215: onsuccess: #31: 2: Success after binutils/gcc: 7 commits new b9b023bf52 216: onsuccess: #32: 2: Success after binutils/gcc: 5 commits new 551b005fe4 217: onsuccess: #35: 2: [TCWG CI] Success after binutils: 59 [...] new 35070480bb 218: force: #37: 2: [TCWG CI] Success after gcc: 40 commits new f69cdeb77c 219: force: #38: 1: [TCWG CI] Failure after basepoints/gcc-1 [...] new 1f1d2dfdb4 220: onsuccess: #39: 1: [TCWG CI] Success after gcc: 2 commits new c2f3d02be9 221: onsuccess: #40: 2: [TCWG CI] Success after binutils/gcc [...] new 6aa973e2cc 222: onsuccess: #41: 2: [TCWG CI] Success after binutils/gcc [...] new c6b52bcfee 223: onsuccess: #42: 2: [TCWG CI] Success after binutils/gcc [...] new 418dae0e67 224: onsuccess: #43: 2: [TCWG CI] Success after binutils/gcc [...] new 240d2d3eff 225: onsuccess: #44: 2: [TCWG CI] Success after binutils/gcc [...] new f91caefa13 226: onsuccess: #45: 2: [TCWG CI] Success after binutils/gcc [...] new f0ea86aa74 227: onsuccess: #46: 2: [TCWG CI] Success after binutils/gcc [...] new 2c282dd7d2 228: onsuccess: #48: 2: [TCWG CI] Success after binutils/gcc [...] new 6763f2f03b 229: onsuccess: #49: 2: [TCWG CI] Success after binutils/gcc [...] new 9847f13b29 230: onsuccess: #50: 2: [TCWG CI] Success after binutils/gcc [...] new c305584803 231: onsuccess: #51: 2: [TCWG CI] Success after binutils/gcc [...] new 51dd179485 232: onsuccess: #52: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new 2e34920545 233: onsuccess: #53: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new b6b933e097 234: onsuccess: #54: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new 4d7e1990c8 235: onsuccess: #55: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new da1c474419 236: onsuccess: #56: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new 0876cec337 237: onsuccess: #57: 2: [TCWG CI] https://ci.linaro.org/job/ [...] 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 (71e583d19c) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2116 -> 1964 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2516 bytes 04-build_abe-binutils/console.log.xz | Bin 35492 -> 35016 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 305088 -> 306272 bytes 06-check_regression/console.log.xz | Bin 552 -> 552 bytes 07-update_baseline/console.log | 70 ++++++++++----------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 16 ++--- 10 files changed, 46 insertions(+), 46 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-defconfig updated (c55e65591b -> 53d169e340)

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-lts-defconfig in repository toolchain/ci/base-artifacts. from c55e65591b 54: onsuccess: #12: boot: [TCWG CI] https://ci.linaro.org/jo [...] new 53d169e340 55: onsuccess: #13: boot: [TCWG CI] https://ci.linaro.org/jo [...] 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 2000 -> 2008 bytes 02-prepare_abe/console.log.xz | Bin 2540 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 27280 -> 27100 bytes 04-build_kernel_llvm/console.log.xz | Bin 66492 -> 67116 bytes 05-build_abe-qemu/console.log.xz | Bin 32012 -> 30768 bytes 06-build_linux/console.log.xz | Bin 3112 -> 3652 bytes 07-boot_linux/console.log.xz | Bin 6096 -> 6092 bytes 08-check_regression/console.log.xz | Bin 1228 -> 528 bytes dashboard/dashboard-generate.sh | 17 ------------- dashboard/dashboard-push.sh | 7 ------ dashboard/squad-vs-first/results-functional.json | 1 - git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- jenkins/dashboard-push.sh | 7 ------ jenkins/notify.sh | 2 +- manifest.sh | 30 +++++++++++------------ 18 files changed, 19 insertions(+), 53 deletions(-) delete mode 100755 dashboard/dashboard-generate.sh delete mode 100755 dashboard/dashboard-push.sh delete mode 100644 dashboard/squad-vs-first/results-functional.json delete mode 100755 jenkins/dashboard-push.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm updated (2c7d2820bf -> afba3a23de)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards 2c7d2820bf 249: onsuccess: #52: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 8d5ed4e298 248: onsuccess: #51: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards dd24f8f35b 247: onsuccess: #50: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards db3c924610 246: onsuccess: #49: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 83056220f3 245: onsuccess: #48: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards f6d3cca898 244: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 49e09c2b3f 243: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards c1f857cba2 242: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 29356ef2f6 241: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards c5feacc42e 240: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 93ebaa1fef 239: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards ab613728cc 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards b6dfc6d4de 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/gcc [...] discards ba8df922a3 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/gcc [...] discards d5be216f8c 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/gcc [...] discards 3d215ab402 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/gcc [...] discards b74b7daff8 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/gcc [...] discards 3b7b85aa26 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards f273081f87 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 0c8ce54090 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards ece6b7410f 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards b1ca2db8f4 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards 2bdd60f597 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards d48cf739f9 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards fc1fa6d24a 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] discards 5204e259e8 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards cafa919df1 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 94cbcd5424 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 9779eb9e3b 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb [...] discards bdca74d0a7 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] discards 32e0299d8c 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards b71fa5b427 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards 4156b015d9 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards add0fb9180 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 71ea3ef48a 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 156500cf06 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 52a08ec67b 213: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] discards 0573ba4a68 212: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards b50efc2788 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards 615975c8ea 210: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 3da66f5422 209: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards d611b4849a 208: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards 6f7d9e0ec3 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb: [...] discards 5e05c9757d 206: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards a6a865ae8f 205: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards f6c69c4031 204: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards 50f7c1e326 203: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards f89bd90404 202: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards bded01be57 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards bfe7b77ba6 200: onsuccess: #663: 1: Success after binutils/gcc/linux/gl [...] discards f8f0ceb809 199: onsuccess: #662: 1: Success after binutils/gcc/linux/gl [...] discards 4d4551b0ce 198: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards f9a40285d3 197: onsuccess: #660: 1: Success after binutils/gcc/linux/gl [...] discards 58be240257 196: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards a75379dd91 195: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards fa7665c75f 194: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards e7ca1bad47 193: onsuccess: #655: 1: Success after binutils/gcc/linux/gd [...] discards b0c00d1a9c 192: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards a686cfc147 191: onsuccess: #653: 1: Success after binutils/gcc/linux/gl [...] discards 0dbd65ec0a 190: onsuccess: #652: 1: Success after binutils/gcc/linux/gl [...] discards ff14be7b19 189: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards df517dbe67 188: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 3b15b7b414 187: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 7274b6805b 186: onsuccess: #648: 1: Success after binutils/gcc/linux/gd [...] discards c5689eba0b 185: onsuccess: #647: 1: Success after binutils/gcc/linux/gd [...] discards 7dc63ee081 184: onsuccess: #646: 1: Success after binutils/gcc/linux/gl [...] discards d1cece9495 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 203 [...] discards 2987e9666c 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 commits discards bc8581db12 181: onsuccess: #643: 1: Success after binutils/gcc/linux/gl [...] discards 24f07dda8c 180: onsuccess: #642: 1: Success after binutils/gcc/linux/gl [...] discards 54a1c136f1 179: onsuccess: #641: 1: Success after binutils/gcc/linux/gd [...] discards 946061a379 178: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards 2ee70a8ad1 177: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards 5039f46a86 176: onsuccess: #638: 1: Success after binutils/gcc/linux/gd [...] discards 720bd37daa 175: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards 80cf034933 174: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards 3fc75e40ff 173: onsuccess: #635: 1: Success after binutils/gcc/linux/gl [...] discards 1ff6dc1807 172: onsuccess: #634: 1: Success after binutils/gcc/linux/gd [...] discards 6351cdd969 171: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards 50d2612778 170: onsuccess: #632: 1: Success after binutils/gcc/linux/gl [...] discards 3a7761abac 169: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards c98c74d721 168: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards 783bcfc3c8 167: onsuccess: #629: 1: Success after binutils/gcc/linux/gd [...] discards 5d9a5e5be7 166: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards f83805f69a 165: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards fc94645178 164: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards f3a4cbc3f1 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/gd [...] discards bc22b743e5 162: onsuccess: #624: 1: Success after linux: 10 commits discards 3c5a953eb0 161: onsuccess: #623: 1: Success after glibc: 9 commits discards d2ec48c6f3 160: onsuccess: #621: 1: Success after gcc: 11 commits discards b303e6910d 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 7ee4a2365f 158: onsuccess: #618: 1: Success after binutils/gcc/linux/gd [...] discards fbe3d400d9 157: onsuccess: #617: 1: Success after binutils/gcc/linux/gd [...] discards eb0ead03b8 156: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards d1ca5035d9 155: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards d3ce4b4009 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 commits discards 1b8cb2e997 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 commits discards d436b254eb 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 commits discards c1a4e50a7c 151: onsuccess: #611: 1: Success after binutils/gcc/linux/gd [...] discards e5c520f15a 150: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 8af7cffe42 149: onsuccess: #609: 1: Success after binutils/gcc/linux/gd [...] new d31ab1bf6f 149: onsuccess: #609: 1: Success after binutils/gcc/linux/gd [...] new 8499932745 150: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new c3f6b54295 151: onsuccess: #611: 1: Success after binutils/gcc/linux/gd [...] new 2acacd0887 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 commits new 1716234821 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 commits new b89a1ce85a 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 commits new 8234cf40ad 155: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new 5d41900e29 156: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 0db14c58f9 157: onsuccess: #617: 1: Success after binutils/gcc/linux/gd [...] new 8a69e30a8a 158: onsuccess: #618: 1: Success after binutils/gcc/linux/gd [...] new 7c9557e99b 159: onsuccess: #620: 1: Success after binutils: 12 commits new 9a4320dc2d 160: onsuccess: #621: 1: Success after gcc: 11 commits new 8abb73dc20 161: onsuccess: #623: 1: Success after glibc: 9 commits new 6661b5d4b3 162: onsuccess: #624: 1: Success after linux: 10 commits new 848c3587b5 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/gd [...] new d73f243bb7 164: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new 9a75919265 165: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new c96cad0c97 166: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 852d4971ae 167: onsuccess: #629: 1: Success after binutils/gcc/linux/gd [...] new 63696f1fac 168: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new e6e75db4a5 169: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new fa1992ca38 170: onsuccess: #632: 1: Success after binutils/gcc/linux/gl [...] new 38aa7aed29 171: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new 0c3128194d 172: onsuccess: #634: 1: Success after binutils/gcc/linux/gd [...] new 511a5e9216 173: onsuccess: #635: 1: Success after binutils/gcc/linux/gl [...] new 511ee1a50a 174: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new 736ff300ef 175: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new 94291e4708 176: onsuccess: #638: 1: Success after binutils/gcc/linux/gd [...] new a3ce6297db 177: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new a3bfb68605 178: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new ee5730b267 179: onsuccess: #641: 1: Success after binutils/gcc/linux/gd [...] new 118c0246c8 180: onsuccess: #642: 1: Success after binutils/gcc/linux/gl [...] new 0c5cc987d8 181: onsuccess: #643: 1: Success after binutils/gcc/linux/gl [...] new 728ea53d77 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 commits new e386a1ddca 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 203 [...] new 4202361b50 184: onsuccess: #646: 1: Success after binutils/gcc/linux/gl [...] new bc060d7660 185: onsuccess: #647: 1: Success after binutils/gcc/linux/gd [...] new 4ec1854ea3 186: onsuccess: #648: 1: Success after binutils/gcc/linux/gd [...] new 1684a55d74 187: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 80dd281dfd 188: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new ca2cc0cc7f 189: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new a414148ba2 190: onsuccess: #652: 1: Success after binutils/gcc/linux/gl [...] new 87e367ed57 191: onsuccess: #653: 1: Success after binutils/gcc/linux/gl [...] new fee9622044 192: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new edd5696951 193: onsuccess: #655: 1: Success after binutils/gcc/linux/gd [...] new 9417f6c009 194: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 158577db0a 195: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 460b04f94d 196: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 2d0dd701f3 197: onsuccess: #660: 1: Success after binutils/gcc/linux/gl [...] new d85dfda4eb 198: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new 57e04a56ae 199: onsuccess: #662: 1: Success after binutils/gcc/linux/gl [...] new 43716b053c 200: onsuccess: #663: 1: Success after binutils/gcc/linux/gl [...] new 6ddcdaf696 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new c417323a16 202: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new 0901ae86d6 203: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new 922882d376 204: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new d2b434eedf 205: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new b80ebab182 206: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 5ffbe6276c 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb: [...] new 04c61ab530 208: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new cd925fcf5c 209: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 78c74e39d1 210: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 2890b77fbe 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 9da30d4b94 212: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new d48a7e6467 213: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] new c34e06536c 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new ff39a8b64d 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 9217ab302a 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new b5ad77dd31 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 8ea1e89ee1 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new 3266981e20 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 2bd07b2c80 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] new bb37178788 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb [...] new 3f5ff80515 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 45fef6eae2 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 509f42c72e 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new 2ec87ce179 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new e798873753 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 4026a93688 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new baf4a12134 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new 1cdea2322d 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 7f2d84891b 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new cec48f591a 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 04dda7cf5c 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 02f02c6e77 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/gcc [...] new b529b7625e 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/gcc [...] new 9b831ddb62 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/gcc [...] new 0fd770adfc 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/gcc [...] new 08f7aade2a 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/gcc [...] new 842a8c76f7 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 16a16da982 239: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 999e72c9cf 240: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new cdad366e36 241: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 8c43773b85 242: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new eb14009d9d 243: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 77f86c7533 244: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 3a2eac592f 245: onsuccess: #48: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 827b4febda 246: onsuccess: #49: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 4dbffb6096 247: onsuccess: #50: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new b4b26ec75d 248: onsuccess: #51: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 60c3c7fef3 249: onsuccess: #52: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new afba3a23de 250: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] 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 (2c7d2820bf) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2252 -> 2216 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 48824 -> 48752 bytes 04-build_abe-gcc/console.log.xz | Bin 237628 -> 236992 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8548 -> 8524 bytes 07-build_abe-glibc/console.log.xz | Bin 233172 -> 232776 bytes 08-build_abe-gdb/console.log.xz | Bin 46320 -> 46616 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3804 bytes 10-build_abe-check_gcc/console.log.xz | Bin 10012 -> 11048 bytes 11-check_regression/console.log.xz | Bin 1904 -> 1660 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 64 +- 11-check_regression/results.regressions | 16 +- 12-update_baseline/console.log | 48 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 16 +- mail/results.regressions | 16 +- manifest.sh | 30 +- results | 16 +- sumfiles/g++.log.sep.xz | Bin 79932 -> 54584 bytes sumfiles/g++.log.xz | Bin 2892496 -> 2902128 bytes sumfiles/g++.sum | 2 +- sumfiles/g++.sum.sep | 8308 ++++++++++++++----------------- sumfiles/gcc.log.sep.xz | Bin 49976 -> 49804 bytes sumfiles/gcc.log.xz | Bin 2472748 -> 2479816 bytes sumfiles/gcc.sum | 2 +- sumfiles/gcc.sum.sep | 3512 +++++-------- sumfiles/gfortran.log.sep.xz | Bin 21444 -> 20736 bytes sumfiles/gfortran.log.xz | Bin 962860 -> 963668 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 2087 ++++---- sumfiles/libatomic.log.xz | Bin 2284 -> 2280 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 230884 -> 231020 bytes sumfiles/libgomp.sum | 14 +- sumfiles/libitm.log.xz | Bin 2688 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 13412 -> 6892 bytes sumfiles/libstdc++.log.xz | Bin 469252 -> 472252 bytes sumfiles/libstdc++.sum.sep | 104 +- 45 files changed, 6192 insertions(+), 8075 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits April 2023