Tcwg-commits April 2023

tcwg-commits@lists.linaro.org

5 participants
5583 discussions

[toolchain/ci/interesting-commits] branch master updated (f54a7535 -> d612bad9)

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 f54a7535 Add entry 05fe3ecffff485032e904f0a3ea709e24d9188eb from https [...] new d612bad9 Add entry 5a961061de7d70bd3568270185c3189e20958e68 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: newlib/newlib-4.3.0-140-g5a961061d | 1 + .../gnu_eabi-arm_eabi-master-O3_LTO/build_url | 2 +- .../gnu_eabi-arm_eabi-master-O3_LTO/last_good | 1 + .../gnu_eabi-arm_eabi-master-O3_LTO/summary.txt | 8 ++++---- .../tcwg_bmk-code_speed-coremark/status.txt | 22 ++++++++++------------ 5 files changed, 17 insertions(+), 17 deletions(-) create mode 120000 newlib/newlib-4.3.0-140-g5a961061d copy {binutils/sha1/ca26b8030e8c184bdeca7280e31c10c6e9fc3f78 => newlib/sha1/5a9610 [...] create mode 100644 newlib/sha1/5a961061de7d70bd3568270185c3189e20958e68/tcwg_bmk-c [...] copy {binutils/sha1/fade906daab13c99fc329c1e08447f2aac168b62 => newlib/sha1/5a9610 [...] copy {gcc/sha1/d339e9802f758e051b0a1ef6db732ff846cbf4e3 => newlib/sha1/5a961061de7 [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (0bb35817ca -> dd6509194e)

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 0bb35817ca 245: force: #69: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 03eabc8612 244: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 241b3cde06 243: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 9bb00689bd 242: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 621c5217e4 241: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 9935f54e1e 240: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards f468e97df1 239: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 9c6200e28d 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards d1ff5a1701 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards d04efd8d08 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards cce7974c35 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 6e97d37adb 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 8a3553d21c 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards cb3e9434a6 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 80d1bce8f3 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 4cf641c927 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 122dd0fea8 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 62bd4d9f02 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 5061e3b32e 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 636a5769dc 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 2acdebf8cd 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 8fd29c8d9d 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 4359045ddf 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards d60fbb2142 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 019c4a90af 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 2feb3abf54 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards d139091008 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 8dcc69ef0c 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 5d5d3c11f6 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards ea1f0ad520 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 0afb9b2ac2 215: onsuccess: #26: 1: Success after binutils: 10 commits discards edef5d9e23 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards cd57c3a1d9 213: force: #24: 1: Success after binutils: 2 commits discards 9f1fa06563 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards cbc0552718 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards ac8356fb0b 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 6775a9b849 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 28c6b12c91 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 3ed6ad1931 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 3444912d07 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards b9deaa7ce2 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 3d3e397580 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 5473745f86 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 5ddb5d2053 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 9aedd52016 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 3478fc51e7 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 7cee1e7e55 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards b5b65e72e1 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 5df59305b9 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards d9ae31f508 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards ab6e4a6a91 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards ab1fa5c67c 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 37d7bfc418 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 5ba61248ab 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards 5264db53af 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] discards 49e4af9238 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards c91cb5a28e 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] discards 5368493d87 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 37eb70d953 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] discards edf383f2a4 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 108037dee7 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards 47cd4cb4a0 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] discards cc2df30792 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] discards 3ac680d793 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards 8a89fe8265 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards f9a92b1caa 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 627e2a7fc5 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 0d6156464f 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards 10797f6ad7 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 0675747126 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 440c50da59 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] discards d6e323ddc0 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 4b27908834 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 4be5b3cdd1 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards f0922276ec 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 0031962786 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards b2fc717f30 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] discards 102167b781 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards d9988f4ee3 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards f1dc25349f 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 9af0c53823 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards faee1b6fa3 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards fcffee7505 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards 2c8f7f62ac 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 777f1a9dcd 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards 49a5d234ef 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] discards 162a8bf2fe 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards fc83516b97 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] discards 6de8609fc5 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] discards b3f581f891 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 1bf75da0dc 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards b9c7fedff4 154: onsuccess: #583: 1: Success after linux: 10 commits discards 60384422f3 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 2739b529cc 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 207c1ac366 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 0f9d009edc 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards 6c566c3494 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 0081ca521f 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] discards c5d5841e03 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 568360e043 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits discards 0baae35c96 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits new 1fdd8fad47 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits new 112767566d 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits new a47adae52b 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new c0ae4eaf3e 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] new cc36d97248 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 2933373142 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new 81c23818fc 151: onsuccess: #579: 1: Success after binutils: 21 commits new 37407e5b8c 152: onsuccess: #580: 1: Success after gcc: 6 commits new 067efedf5e 153: onsuccess: #582: 1: Success after glibc: 9 commits new 3ef349755e 154: onsuccess: #583: 1: Success after linux: 10 commits new 9ef483523a 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 080dc01032 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new e9224c610e 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] new 62e4484f11 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] new 18e4cb064d 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 5f0ed490f4 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] new 63f6991d8d 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new dc4c181f71 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 40bbc163ee 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new 4240e2c4f1 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 8e6567f5c4 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new a53234d880 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 0a6e1fd5b9 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 77b4e92f1a 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new e617704f0f 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] new 84ce8c71ec 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new cde544a557 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 1f6e66ae9f 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 039988bd09 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 2b6e0e6701 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 0c20b7a9ed 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] new a9bfb64525 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 6658036b96 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 2ce68e69f6 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new 002fe33f91 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 5601757da4 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new dec0370690 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new d16c830344 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new f9e69914a0 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] new 84464af58d 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] new 2954b0ad71 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new 292de8d5c6 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new c28d19fd9b 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] new 744d4e6f81 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 58fba2e194 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] new b36e83f026 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 679d693685 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] new 228918992e 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new b6e01d76eb 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 2f817ec218 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 4972c3600d 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 3711205e3e 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new be080f2156 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 0d7819a838 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 8b1998b158 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 1bcf26606a 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 6bf580f2e0 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 90091272bf 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 52217405b5 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new ef172d07ad 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new b00dbb07f1 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 8569a11881 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new aa0babff5e 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 9b9a30f747 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new f9a200d3a7 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new cbe337e5d5 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new a0c3df7331 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 82ec1b1ddc 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 37499bd8c9 213: force: #24: 1: Success after binutils: 2 commits new e984254795 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new 685d6bc7c3 215: onsuccess: #26: 1: Success after binutils: 10 commits new 602fb276a6 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new a16f3f6c06 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 9e8aee0805 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 1d7edb03af 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 0061ec2492 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 4236fa1d82 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new b22bac0436 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 539b5e1a9f 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 1143adf112 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 25cfc9942e 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new fc1b1eaff8 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 1d57a72885 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new f955690905 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 00b0f1b260 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 13ae4bf4d8 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 600eeaea0f 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 51d1250fcd 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new ce1349acaf 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new d30dc5202f 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 97d3a4ff58 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new c915062bc1 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 703a023dfc 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new a46d683f8b 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 7012bb50e4 239: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new c45038c6ce 240: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 1fa5bca92d 241: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new fbe28e706a 242: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 65b0f5d23d 243: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 7c4b52e4b6 244: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 5148015449 245: force: #69: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new dd6509194e 246: force: #71: 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 (0bb35817ca) \ 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 2028 -> 2080 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2552 bytes 03-build_abe-binutils/console.log.xz | Bin 49928 -> 49912 bytes 04-build_abe-gcc/console.log.xz | Bin 236400 -> 236744 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8952 -> 8960 bytes 07-build_abe-glibc/console.log.xz | Bin 232592 -> 232104 bytes 08-build_abe-gdb/console.log.xz | Bin 46532 -> 46692 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3816 bytes 10-build_abe-check_binutils/console.log.xz | Bin 3004 -> 3012 bytes 11-check_regression/console.log.xz | Bin 1600 -> 1600 bytes 11-check_regression/results.compare | 8 +++--- 11-check_regression/results.regressions | 8 +++--- 11-check_regression/trigger-bisect | 4 +-- 12-update_baseline/console.log | 40 ++++++++++++++--------------- git/glibc_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 8 +++--- mail/results.regressions | 8 +++--- manifest.sh | 12 ++++----- results | 8 +++--- sumfiles/binutils.log.xz | Bin 62456 -> 62028 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100632 -> 100944 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132344 -> 132348 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, 2 months

[toolchain/ci/interesting-commits] branch master updated (0fa2dabe -> f54a7535)

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 0fa2dabe Add entry a37783de23c067d6a26374ff29c014e49604035c from https [...] new f54a7535 Add entry 05fe3ecffff485032e904f0a3ea709e24d9188eb 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: .../master-arm/build_url | 2 +- .../master-arm/last_good | 0 .../master-arm/summary.txt | 8 ++++---- .../tcwg_gnu_native_check_binutils/status.txt | 19 +++++++++++++++++++ 4 files changed, 24 insertions(+), 5 deletions(-) copy {binutils/sha1/b8d1a3a8ef9aff015ae963522287f7785bc552ec => glibc/sha1/05fe3ec [...] copy glibc/sha1/05fe3ecffff485032e904f0a3ea709e24d9188eb/{tcwg_gnu_native_fast_che [...] copy {gcc/sha1/2134fcfee8b338a6f10273457145fc071dc8f092 => glibc/sha1/05fe3ecffff4 [...] create mode 100644 glibc/sha1/05fe3ecffff485032e904f0a3ea709e24d9188eb/tcwg_gnu_na [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 updated (671d351a9c -> 321360b1b2)

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 671d351a9c 250: force: #132: : [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 9d24192c08 249: onsuccess: #124: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 2962936a3d 248: onsuccess: #123: 1: [TCWG CI] https://ci.linaro.org/job [...] discards cb6340b40a 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...] discards b51e5e7d3a 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 16b47a6876 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] discards efe7608150 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits discards b4b2626ee4 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] discards def04463da 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] discards 42b82d2f89 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits discards b3eaac0aaa 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] discards 1b7aa2911e 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] discards 8815210958 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits discards 0a28866d11 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards 96c644c572 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards 66964d60ad 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 3056af79a1 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards ddcd307aa2 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards 7c6b862e1b 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 88acd0f0aa 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards 4352f091b5 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards e3780dce65 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards a8450e9767 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards c7fe0e64f5 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards 8088a6e317 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards a050002093 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards ad97a8b973 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 82dab9e8e2 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards f7db60c256 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards 19e8654640 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards d730f456f6 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 37cee54de7 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 22eb44a0fb 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards d41dee6a04 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards 4d22a73613 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards 0797c5d045 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards ee2bbd36ff 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 3980f0b41e 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards 8aec1c19bb 212: force: #45: 1: Success after gdb: 22 commits discards 6fc94c45b7 211: onsuccess: #44: 1: Success after linux: 26 commits discards 324de733b0 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards 56d3f6edca 209: force: #37: 1: Success after baseline build: no new commits discards 27448b1d95 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards d008ad4f3e 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 6c1db24b48 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 8166f6db4f 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards d064bdd438 204: force: #26: : Failure after baseline build: no new commits discards 097583790b 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards ac3d05e40f 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 88718bbdc9 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards d23b3e9caa 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards e595483111 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards a3bdb75686 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards c5de27f1ad 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 4dbc2f49ae 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 5310a79cb9 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 777dc16c24 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 7bf76fc37e 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards dbe1c23194 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 2d02578f08 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 11f69b7e9e 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards e67c8248f2 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 58c4393b7d 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 18ff9054eb 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 0a4e6eebf1 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 08c249317f 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards b1c36b39ba 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards f07f93c78b 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards 38a677702f 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards 10a598151f 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards afabd1b5eb 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards cb3d113a1b 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards 91bbac2b5b 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards d389a04625 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards c5dc6eb4b0 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards 6647c85707 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards 43ebb4d86f 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards 0fe194801d 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards a1840ef12b 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards 41232c3b23 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards 914a2c3b7d 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards 2a9d8063b8 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards 645a735863 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards e845b15af9 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards bb3a78d8bd 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards 1c5cae0886 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards c5fa89220f 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards f15646c3db 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards 9020bbbc6f 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards 012247d799 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards 219287dc2c 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards eb20aa4d43 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards 97c3f261a1 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 45e2cdd24c 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards 96eb6dabd4 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards abdc6b2ab9 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards bfdfff0e43 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards 2313a04edf 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards 7d1d2a732b 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards d789a6cece 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards 2ca24b1ec6 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new 81e2996b3f 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new d13b6856c6 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new a6d9368ee2 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 5d49f28948 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new 49e8bdaeaf 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 8e122f35e5 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new df0b27117a 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new 31d452cce6 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new 965e4fca45 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 474dbec886 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new 91a1b5ec8f 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new 750795d59d 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new 1adcc5fc19 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new 074af96f94 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new e63aa5634e 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new 7d106a3de5 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new 7125285621 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new f895b3a484 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new cbed4eae47 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new 79d0453118 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new 475aae6d23 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new f63b8f5dc9 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new ecbc2a8d9c 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new 5d9a1cb7b6 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new 7238b76d31 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new a83802da67 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new abbe2909c1 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new 2ab127d7d3 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new 72c96fee71 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new a8f05dc5a6 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new db07c3bea7 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new d3bfb7f724 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new 0dbf7848c2 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new 5a0b9a09a5 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new d2aec7fc5c 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new 5d5a8a9e27 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 6866d4e928 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 82bd0ee30d 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new f110557d63 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 182142ab83 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new b150c8f6b7 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new e53c7a66ec 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new e4d13a85f2 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 8db451edce 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 678c2f0e2b 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 8ed9f5f978 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 4174046e4b 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new b9bc3246b8 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 707607d9e5 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 8024aa1652 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 37e1afe9c9 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 776399b86a 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 62a9f85625 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 61de74e141 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 9a2bc18937 204: force: #26: : Failure after baseline build: no new commits new 0d8548db56 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 182660a3b6 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 932e3edca7 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new bbd5129d2c 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new f4de4cc258 209: force: #37: 1: Success after baseline build: no new commits new a7f34782ff 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new 2dd9799f5f 211: onsuccess: #44: 1: Success after linux: 26 commits new cf71606e33 212: force: #45: 1: Success after gdb: 22 commits new 8d89382597 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new c1218e3f86 214: onsuccess: #47: 1: Success after gdb: 21 commits new d0e868df67 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new eb789798b8 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new 3bee7b0d57 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new 2c09c1ec96 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new 740eeeffab 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 473f1fb63d 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 25bc5045fd 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 05ae5710ea 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new 2ee3cd642d 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new 9530e780e2 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 51265777b2 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new d3cad4521a 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new 7d2771858c 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new 60e07075af 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new b85565baf2 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new 4929c5fb8f 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new 9466ebf066 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new c9438b886f 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new 4d0db8c941 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new 94563731fe 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new f877a0fac6 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new 22ae56ee84 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new d065206c9b 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new 1da7430b6e 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits new 735c01b38b 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] new 59a3a9710f 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] new dc556e34ef 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits new b9de1b2034 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] new 2b8d759360 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] new e1083e2729 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits new b746e8a144 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] new 75614e42da 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new ab6ecbed4f 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...] new 365702f46b 248: onsuccess: #123: 1: [TCWG CI] https://ci.linaro.org/job [...] new 424b49498a 249: onsuccess: #124: 1: [TCWG CI] https://ci.linaro.org/job [...] new 8aa055c37f 250: force: #132: : [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 321360b1b2 251: onsuccess: #133: 0: [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 (671d351a9c) \ 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 2176 -> 2044 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 35028 -> 34996 bytes 04-build_abe-gcc/console.log.xz | Bin 203564 -> 202772 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8948 -> 8508 bytes 07-build_abe-glibc/console.log.xz | Bin 242400 -> 241504 bytes 08-build_abe-gdb/console.log.xz | Bin 34820 -> 34712 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3832 bytes 10-build_abe-check_gdb/console.log.xz | Bin 1328 -> 1328 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 976 -> 548 bytes 11-check_regression/results.regressions | 3 --- 12-update_baseline/console.log | 46 ++++++++++++++++---------------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- mail/check-regression-status.txt | 2 +- manifest.sh | 33 +++++++++++++---------- results | 3 --- 23 files changed, 50 insertions(+), 51 deletions(-) delete mode 100644 11-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_aosp-code_size-aosp/oriole-master updated (55d4ba4f67 -> fbca46772d)

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 55d4ba4f67 10: onsuccess: #56: 2: [TCWG CI] Success after aosp_superpro [...] new fbca46772d 11: onsuccess: #67: 2: [TCWG CI] https://ci.linaro.org/job/t [...] 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 1952 -> 1932 bytes 02-build_aosp_toolchain/console.log.xz | Bin 215508 -> 214596 bytes 03-build_shadow_llvm/console.log.xz | Bin 131336 -> 131040 bytes 04-build_aosp/console.log.xz | Bin 1267496 -> 1250044 bytes 06-check_regression/binary.regressions | 11 - 06-check_regression/console.log.xz | Bin 46656 -> 42440 bytes .../first-size.csv | 1752 +++++++++---------- 06-check_regression/results.regressions | 1 - dashboard/dashboard-generate.sh | 17 - dashboard/dashboard-push.sh | 7 - .../squad-vs-first/score/results-functional.json | 1 - git/toolchain_superproject_rev | 2 +- jenkins/dashboard-push.sh | 7 - jenkins/notify.sh | 3 + mail/changes-list-long.txt | 14 - mail/changes-list-short.txt | 1 - mail/check-regression-status.txt | 1 + mail/last_good.sh | 26 - mail/short-diag.txt | 1 - manifest.sh | 21 +- results | 1 - results-vs-first/results.csv | 1756 +++++++++---------- results-vs-prev/results.csv | 1764 +++++++++---------- size.csv | 1776 ++++++++++---------- 24 files changed, 3539 insertions(+), 3623 deletions(-) delete mode 100644 06-check_regression/binary.regressions rename first-size.csv => 06-check_regression/first-size.csv (99%) delete mode 100644 06-check_regression/results.regressions delete mode 100755 dashboard/dashboard-generate.sh delete mode 100755 dashboard/dashboard-push.sh delete mode 100644 dashboard/squad-vs-first/score/results-functional.json delete mode 100755 jenkins/dashboard-push.sh create mode 100755 jenkins/notify.sh delete mode 100644 mail/changes-list-long.txt delete mode 100644 mail/changes-list-short.txt create mode 100644 mail/check-regression-status.txt delete mode 100644 mail/last_good.sh delete mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-cpu2017fast/gnu-aarch64-master-O3_LTO updated (29cbce122a -> c13a849f25)

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_LTO in repository toolchain/ci/base-artifacts. from 29cbce122a 1: onsuccess: #4: 1: [TCWG CI] Success after binutils/gcc/gl [...] new c13a849f25 2: 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 2076 -> 2260 bytes 02-prepare_abe/console.log.xz | Bin 2576 -> 2552 bytes 03-build_abe-binutils/console.log.xz | Bin 29344 -> 27640 bytes 04-build_abe-stage1/console.log.xz | Bin 72332 -> 71528 bytes 06-build_abe-linux/console.log.xz | Bin 7628 -> 7612 bytes 07-build_abe-glibc/console.log.xz | Bin 243976 -> 243132 bytes 08-build_abe-stage2/console.log.xz | Bin 176824 -> 176400 bytes 09-benchmark/benchmark-build.log | 123 +- 09-benchmark/benchmark.log | 121 +- 09-benchmark/console.log.xz | Bin 3976 -> 4128 bytes 10-check_regression/bmk-specific-variability.csv | 1 + .../compare-results-vs-first-internal.csv | 42 - .../compare-results-vs-prev-internal.csv | 42 - 10-check_regression/console.log.xz | Bin 8168 -> 5512 bytes .../csv-results-vs-first-0/md5sum.csv | 1 - .../csv-results-vs-first-1/md5sum.csv | 1 - .../csv-results-vs-prev-0/md5sum.csv | 1 - 10-check_regression/csv-results-vs-prev-0/perf.csv | 87 - .../csv-results-vs-prev-1/md5sum.csv | 1 - 10-check_regression/csv-results-vs-prev-1/perf.csv | 89 - 10-check_regression/mail-body.txt | 13 - 10-check_regression/mail-subject.txt | 1 - 10-check_regression/results-vs-first-brief.csv | 30 - 10-check_regression/results-vs-first-full.csv | 93 - 10-check_regression/results-vs-first-internal.csv | 39 - 10-check_regression/results-vs-first.csv | 39 - 10-check_regression/results-vs-first.log | 3112 -- 10-check_regression/results-vs-prev-brief.csv | 30 - 10-check_regression/results-vs-prev-full.csv | 93 - 10-check_regression/results-vs-prev-internal.csv | 39 - 10-check_regression/results-vs-prev.csv | 39 - 10-check_regression/results-vs-prev.log | 3112 -- .../results_id.first | 0 dashboard/dashboard-generate.sh | 17 - dashboard/dashboard-push.sh | 7 - .../508.namd_r/results-functional.json | 4 - .../508.namd_r/results-metadata.json | 12 - .../squad-vs-first/508.namd_r/results-metrics.json | 5 - .../510.parest_r/results-functional.json | 4 - .../510.parest_r/results-metadata.json | 12 - .../510.parest_r/results-metrics.json | 5 - .../511.povray_r/results-functional.json | 4 - .../511.povray_r/results-metadata.json | 12 - .../511.povray_r/results-metrics.json | 5 - .../526.blender_r/results-functional.json | 4 - .../526.blender_r/results-metadata.json | 12 - .../526.blender_r/results-metrics.json | 5 - .../600.perlbench_s/results-functional.json | 4 - .../600.perlbench_s/results-metadata.json | 12 - .../600.perlbench_s/results-metrics.json | 5 - .../602.gcc_s/results-functional.json | 4 - .../squad-vs-first/602.gcc_s/results-metadata.json | 12 - .../squad-vs-first/602.gcc_s/results-metrics.json | 4 - .../603.bwaves_s/results-functional.json | 4 - .../603.bwaves_s/results-metadata.json | 12 - .../603.bwaves_s/results-metrics.json | 4 - .../605.mcf_s/results-functional.json | 4 - .../squad-vs-first/605.mcf_s/results-metadata.json | 12 - .../squad-vs-first/605.mcf_s/results-metrics.json | 5 - .../607.cactuBSSN_s/results-functional.json | 4 - .../607.cactuBSSN_s/results-metadata.json | 12 - .../607.cactuBSSN_s/results-metrics.json | 4 - .../619.lbm_s/results-functional.json | 4 - .../squad-vs-first/619.lbm_s/results-metadata.json | 12 - .../squad-vs-first/619.lbm_s/results-metrics.json | 4 - .../620.omnetpp_s/results-functional.json | 4 - .../620.omnetpp_s/results-metadata.json | 12 - .../620.omnetpp_s/results-metrics.json | 5 - .../621.wrf_s/results-functional.json | 4 - .../squad-vs-first/621.wrf_s/results-metadata.json | 12 - .../squad-vs-first/621.wrf_s/results-metrics.json | 4 - .../623.xalancbmk_s/results-functional.json | 4 - .../623.xalancbmk_s/results-metadata.json | 12 - .../623.xalancbmk_s/results-metrics.json | 5 - .../625.x264_s/results-functional.json | 4 - .../625.x264_s/results-metadata.json | 12 - .../squad-vs-first/625.x264_s/results-metrics.json | 5 - .../627.cam4_s/results-functional.json | 4 - .../627.cam4_s/results-metadata.json | 12 - .../squad-vs-first/627.cam4_s/results-metrics.json | 4 - .../628.pop2_s/results-functional.json | 4 - .../628.pop2_s/results-metadata.json | 12 - .../squad-vs-first/628.pop2_s/results-metrics.json | 4 - .../631.deepsjeng_s/results-functional.json | 4 - .../631.deepsjeng_s/results-metadata.json | 12 - .../631.deepsjeng_s/results-metrics.json | 5 - .../638.imagick_s/results-functional.json | 4 - .../638.imagick_s/results-metadata.json | 12 - .../638.imagick_s/results-metrics.json | 5 - .../641.leela_s/results-functional.json | 4 - .../641.leela_s/results-metadata.json | 12 - .../641.leela_s/results-metrics.json | 5 - .../644.nab_s/results-functional.json | 4 - .../squad-vs-first/644.nab_s/results-metadata.json | 12 - .../squad-vs-first/644.nab_s/results-metrics.json | 5 - .../648.exchange2_s/results-functional.json | 4 - .../648.exchange2_s/results-metadata.json | 12 - .../648.exchange2_s/results-metrics.json | 5 - .../649.fotonik3d_s/results-functional.json | 4 - .../649.fotonik3d_s/results-metadata.json | 12 - .../649.fotonik3d_s/results-metrics.json | 5 - .../654.roms_s/results-functional.json | 4 - .../654.roms_s/results-metadata.json | 12 - .../squad-vs-first/654.roms_s/results-metrics.json | 4 - .../657.xz_s/results-functional.json | 4 - .../squad-vs-first/657.xz_s/results-metadata.json | 12 - .../squad-vs-first/657.xz_s/results-metrics.json | 5 - .../squad-vs-first/Mean/results-functional.json | 4 - .../squad-vs-first/Mean/results-metadata.json | 12 - dashboard/squad-vs-first/Mean/results-metrics.json | 2 - dashboard/squad-vs-first/dashboard-push-squad.sh | 201 - dashboard/squad-vs-first/summary-annotation.txt | 0 git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/dashboard-push.sh | 7 - jenkins/notify.sh | 3 + mail/changes-list-long.txt | 20 - mail/changes-list-short.txt | 1 - mail/check-regression-status.txt | 1 + mail/last_good.sh | 34 - mail/short-diag.txt | 1 - manifest.sh | 36 +- results-vs-first/compare-results-internal.csv | 43 + results-vs-first/csv-results-0/md5sum.csv | 25 + .../csv-results-0}/perf.csv | 0 .../csv-results-0}/results.csv | 28 +- .../csv-results-0}/size.csv | 0 .../csv-results-0}/sve.csv | 0 .../csv-results-0}/vect.csv | 0 results-vs-first/csv-results-1/md5sum.csv | 25 + results-vs-first/csv-results-1/perf.csv | 86 + .../csv-results-1}/results.csv | 8307 ++-- .../csv-results-1}/size.csv | 8273 ++-- .../csv-results-1}/sve.csv | 1983 +- .../csv-results-1}/vect.csv | 876 +- results-vs-first/interesting-symbols.csv | 38 + results-vs-first/results-brief.csv | 30 + results-vs-first/results-full.csv | 90 + results-vs-first/results-internal.csv | 39 + results-vs-first/results.csv | 39 + results-vs-first/tcwg-benchmark-results.log | 6204 +++ results-vs-prev/compare-results-internal.csv | 43 + .../compare-results.csv | 0 results-vs-prev/csv-results-0/md5sum.csv | 25 + .../csv-results-0}/perf.csv | 0 .../csv-results-0}/results.csv | 7460 ++-- .../csv-results-0}/size.csv | 7440 ++-- .../csv-results-0}/sve.csv | 0 .../csv-results-0}/vect.csv | 0 results-vs-prev/csv-results-1/md5sum.csv | 25 + results-vs-prev/csv-results-1/perf.csv | 86 + .../csv-results-1}/results.csv | 6655 +--- .../csv-results-1}/size.csv | 6591 +--- .../csv-results-1}/sve.csv | 39324 ++++++++++--------- .../csv-results-1}/vect.csv | 774 +- results-vs-prev/interesting-symbols.csv | 38 + results-vs-prev/results-brief.csv | 30 + results-vs-prev/results-full.csv | 90 + results-vs-prev/results-internal.csv | 39 + results-vs-prev/results.csv | 39 + results-vs-prev/tcwg-benchmark-results.log | 6204 +++ results_id | 2 +- 164 files changed, 53672 insertions(+), 55278 deletions(-) create mode 100644 10-check_regression/bmk-specific-variability.csv delete mode 100644 10-check_regression/compare-results-vs-first-internal.csv delete mode 100644 10-check_regression/compare-results-vs-prev-internal.csv delete mode 100644 10-check_regression/csv-results-vs-first-0/md5sum.csv delete mode 100644 10-check_regression/csv-results-vs-first-1/md5sum.csv delete mode 100644 10-check_regression/csv-results-vs-prev-0/md5sum.csv delete mode 100644 10-check_regression/csv-results-vs-prev-0/perf.csv delete mode 100644 10-check_regression/csv-results-vs-prev-1/md5sum.csv delete mode 100644 10-check_regression/csv-results-vs-prev-1/perf.csv delete mode 100644 10-check_regression/mail-body.txt delete mode 100644 10-check_regression/mail-subject.txt delete mode 100644 10-check_regression/results-vs-first-brief.csv delete mode 100644 10-check_regression/results-vs-first-full.csv delete mode 100644 10-check_regression/results-vs-first-internal.csv delete mode 100644 10-check_regression/results-vs-first.csv delete mode 100644 10-check_regression/results-vs-first.log delete mode 100644 10-check_regression/results-vs-prev-brief.csv delete mode 100644 10-check_regression/results-vs-prev-full.csv delete mode 100644 10-check_regression/results-vs-prev-internal.csv delete mode 100644 10-check_regression/results-vs-prev.csv delete mode 100644 10-check_regression/results-vs-prev.log rename results_id.first => 10-check_regression/results_id.first (100%) delete mode 100755 dashboard/dashboard-generate.sh delete mode 100755 dashboard/dashboard-push.sh delete mode 100644 dashboard/squad-vs-first/508.namd_r/results-functional.json delete mode 100644 dashboard/squad-vs-first/508.namd_r/results-metadata.json delete mode 100644 dashboard/squad-vs-first/508.namd_r/results-metrics.json delete mode 100644 dashboard/squad-vs-first/510.parest_r/results-functional.json delete mode 100644 dashboard/squad-vs-first/510.parest_r/results-metadata.json delete mode 100644 dashboard/squad-vs-first/510.parest_r/results-metrics.json delete mode 100644 dashboard/squad-vs-first/511.povray_r/results-functional.json delete mode 100644 dashboard/squad-vs-first/511.povray_r/results-metadata.json delete mode 100644 dashboard/squad-vs-first/511.povray_r/results-metrics.json delete mode 100644 dashboard/squad-vs-first/526.blender_r/results-functional.json delete mode 100644 dashboard/squad-vs-first/526.blender_r/results-metadata.json delete mode 100644 dashboard/squad-vs-first/526.blender_r/results-metrics.json delete mode 100644 dashboard/squad-vs-first/600.perlbench_s/results-functional.json delete mode 100644 dashboard/squad-vs-first/600.perlbench_s/results-metadata.json delete mode 100644 dashboard/squad-vs-first/600.perlbench_s/results-metrics.json delete mode 100644 dashboard/squad-vs-first/602.gcc_s/results-functional.json delete mode 100644 dashboard/squad-vs-first/602.gcc_s/results-metadata.json delete mode 100644 dashboard/squad-vs-first/602.gcc_s/results-metrics.json delete mode 100644 dashboard/squad-vs-first/603.bwaves_s/results-functional.json delete mode 100644 dashboard/squad-vs-first/603.bwaves_s/results-metadata.json delete mode 100644 dashboard/squad-vs-first/603.bwaves_s/results-metrics.json delete mode 100644 dashboard/squad-vs-first/605.mcf_s/results-functional.json delete mode 100644 dashboard/squad-vs-first/605.mcf_s/results-metadata.json delete mode 100644 dashboard/squad-vs-first/605.mcf_s/results-metrics.json delete mode 100644 dashboard/squad-vs-first/607.cactuBSSN_s/results-functional.json delete mode 100644 dashboard/squad-vs-first/607.cactuBSSN_s/results-metadata.json delete mode 100644 dashboard/squad-vs-first/607.cactuBSSN_s/results-metrics.json delete mode 100644 dashboard/squad-vs-first/619.lbm_s/results-functional.json delete mode 100644 dashboard/squad-vs-first/619.lbm_s/results-metadata.json delete mode 100644 dashboard/squad-vs-first/619.lbm_s/results-metrics.json delete mode 100644 dashboard/squad-vs-first/620.omnetpp_s/results-functional.json delete mode 100644 dashboard/squad-vs-first/620.omnetpp_s/results-metadata.json delete mode 100644 dashboard/squad-vs-first/620.omnetpp_s/results-metrics.json delete mode 100644 dashboard/squad-vs-first/621.wrf_s/results-functional.json delete mode 100644 dashboard/squad-vs-first/621.wrf_s/results-metadata.json delete mode 100644 dashboard/squad-vs-first/621.wrf_s/results-metrics.json delete mode 100644 dashboard/squad-vs-first/623.xalancbmk_s/results-functional.json delete mode 100644 dashboard/squad-vs-first/623.xalancbmk_s/results-metadata.json delete mode 100644 dashboard/squad-vs-first/623.xalancbmk_s/results-metrics.json delete mode 100644 dashboard/squad-vs-first/625.x264_s/results-functional.json delete mode 100644 dashboard/squad-vs-first/625.x264_s/results-metadata.json delete mode 100644 dashboard/squad-vs-first/625.x264_s/results-metrics.json delete mode 100644 dashboard/squad-vs-first/627.cam4_s/results-functional.json delete mode 100644 dashboard/squad-vs-first/627.cam4_s/results-metadata.json delete mode 100644 dashboard/squad-vs-first/627.cam4_s/results-metrics.json delete mode 100644 dashboard/squad-vs-first/628.pop2_s/results-functional.json delete mode 100644 dashboard/squad-vs-first/628.pop2_s/results-metadata.json delete mode 100644 dashboard/squad-vs-first/628.pop2_s/results-metrics.json delete mode 100644 dashboard/squad-vs-first/631.deepsjeng_s/results-functional.json delete mode 100644 dashboard/squad-vs-first/631.deepsjeng_s/results-metadata.json delete mode 100644 dashboard/squad-vs-first/631.deepsjeng_s/results-metrics.json delete mode 100644 dashboard/squad-vs-first/638.imagick_s/results-functional.json delete mode 100644 dashboard/squad-vs-first/638.imagick_s/results-metadata.json delete mode 100644 dashboard/squad-vs-first/638.imagick_s/results-metrics.json delete mode 100644 dashboard/squad-vs-first/641.leela_s/results-functional.json delete mode 100644 dashboard/squad-vs-first/641.leela_s/results-metadata.json delete mode 100644 dashboard/squad-vs-first/641.leela_s/results-metrics.json delete mode 100644 dashboard/squad-vs-first/644.nab_s/results-functional.json delete mode 100644 dashboard/squad-vs-first/644.nab_s/results-metadata.json delete mode 100644 dashboard/squad-vs-first/644.nab_s/results-metrics.json delete mode 100644 dashboard/squad-vs-first/648.exchange2_s/results-functional.json delete mode 100644 dashboard/squad-vs-first/648.exchange2_s/results-metadata.json delete mode 100644 dashboard/squad-vs-first/648.exchange2_s/results-metrics.json delete mode 100644 dashboard/squad-vs-first/649.fotonik3d_s/results-functional.json delete mode 100644 dashboard/squad-vs-first/649.fotonik3d_s/results-metadata.json delete mode 100644 dashboard/squad-vs-first/649.fotonik3d_s/results-metrics.json delete mode 100644 dashboard/squad-vs-first/654.roms_s/results-functional.json delete mode 100644 dashboard/squad-vs-first/654.roms_s/results-metadata.json delete mode 100644 dashboard/squad-vs-first/654.roms_s/results-metrics.json delete mode 100644 dashboard/squad-vs-first/657.xz_s/results-functional.json delete mode 100644 dashboard/squad-vs-first/657.xz_s/results-metadata.json delete mode 100644 dashboard/squad-vs-first/657.xz_s/results-metrics.json delete mode 100644 dashboard/squad-vs-first/Mean/results-functional.json delete mode 100644 dashboard/squad-vs-first/Mean/results-metadata.json delete mode 100644 dashboard/squad-vs-first/Mean/results-metrics.json delete mode 100755 dashboard/squad-vs-first/dashboard-push-squad.sh delete mode 100644 dashboard/squad-vs-first/summary-annotation.txt delete mode 100755 jenkins/dashboard-push.sh create mode 100755 jenkins/notify.sh delete mode 100644 mail/changes-list-long.txt delete mode 100644 mail/changes-list-short.txt create mode 100644 mail/check-regression-status.txt delete mode 100644 mail/last_good.sh delete mode 100644 mail/short-diag.txt create mode 100644 results-vs-first/compare-results-internal.csv create mode 100644 results-vs-first/csv-results-0/md5sum.csv rename {10-check_regression/csv-results-vs-first-0 => results-vs-first/csv-results [...] rename {10-check_regression/csv-results-vs-first-0 => results-vs-first/csv-results [...] rename {10-check_regression/csv-results-vs-first-0 => results-vs-first/csv-results [...] rename {10-check_regression/csv-results-vs-first-0 => results-vs-first/csv-results [...] rename {10-check_regression/csv-results-vs-first-0 => results-vs-first/csv-results [...] create mode 100644 results-vs-first/csv-results-1/md5sum.csv create mode 100644 results-vs-first/csv-results-1/perf.csv rename {10-check_regression/csv-results-vs-prev-0 => results-vs-first/csv-results- [...] rename {10-check_regression/csv-results-vs-prev-0 => results-vs-first/csv-results- [...] rename {10-check_regression/csv-results-vs-prev-1 => results-vs-first/csv-results- [...] rename {10-check_regression/csv-results-vs-prev-1 => results-vs-first/csv-results- [...] create mode 100644 results-vs-first/interesting-symbols.csv create mode 100644 results-vs-first/results-brief.csv create mode 100644 results-vs-first/results-full.csv create mode 100644 results-vs-first/results-internal.csv create mode 100644 results-vs-first/results.csv create mode 100644 results-vs-first/tcwg-benchmark-results.log create mode 100644 results-vs-prev/compare-results-internal.csv rename 10-check_regression/results-vs-prev-compare.csv => results-vs-prev/compare- [...] create mode 100644 results-vs-prev/csv-results-0/md5sum.csv rename {10-check_regression/csv-results-vs-first-1 => results-vs-prev/csv-results- [...] rename {10-check_regression/csv-results-vs-first-1 => results-vs-prev/csv-results- [...] rename {10-check_regression/csv-results-vs-prev-1 => results-vs-prev/csv-results-0 [...] rename {10-check_regression/csv-results-vs-first-1 => results-vs-prev/csv-results- [...] rename {10-check_regression/csv-results-vs-first-1 => results-vs-prev/csv-results- [...] create mode 100644 results-vs-prev/csv-results-1/md5sum.csv create mode 100644 results-vs-prev/csv-results-1/perf.csv rename {10-check_regression/csv-results-vs-prev-1 => results-vs-prev/csv-results-1 [...] rename {10-check_regression/csv-results-vs-first-1 => results-vs-prev/csv-results- [...] rename {10-check_regression/csv-results-vs-prev-0 => results-vs-prev/csv-results-1 [...] rename {10-check_regression/csv-results-vs-prev-0 => results-vs-prev/csv-results-1 [...] create mode 100644 results-vs-prev/interesting-symbols.csv create mode 100644 results-vs-prev/results-brief.csv create mode 100644 results-vs-prev/results-full.csv create mode 100644 results-vs-prev/results-internal.csv create mode 100644 results-vs-prev/results.csv create mode 100644 results-vs-prev/tcwg-benchmark-results.log -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-coremark/gnu_eabi-arm_eabi-master-O2_LTO updated (2e71eb7c54 -> 5d082c88a4)

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-coremark/gnu_eabi-arm_eabi-master-O2_LTO in repository toolchain/ci/base-artifacts. from 2e71eb7c54 64: onsuccess: #23: 1: [TCWG CI] https://ci.linaro.org/job/t [...] new 5d082c88a4 65: force: #29: 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 1976 -> 2076 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 27136 -> 27500 bytes 04-build_abe-stage1/console.log.xz | Bin 87192 -> 87696 bytes 06-build_abe-newlib/console.log.xz | Bin 12348 -> 12568 bytes 07-build_abe-stage2/console.log.xz | Bin 162592 -> 162600 bytes 08-benchmark/benchmark-build.log | 96 +++++++++++---------- 08-benchmark/benchmark.log | 94 ++++++++++---------- 08-benchmark/console.log.xz | Bin 3940 -> 4084 bytes 09-check_regression/bmk-specific-variability.csv | 1 - 09-check_regression/console.log.xz | Bin 5072 -> 2744 bytes 09-check_regression/extra-bisect-params | 1 - .../results_id.first | 0 09-check_regression/trigger-bisect | 2 + .../trigger-notify | 0 dashboard/dashboard-generate.sh | 17 ---- dashboard/dashboard-push.sh | 7 -- git/gcc_rev | 2 +- jenkins/dashboard-push.sh | 7 -- jenkins/notify.sh | 2 +- mail/check-regression-status.txt | 2 +- manifest.sh | 26 +++--- results-vs-first/tcwg-benchmark-results.log | 2 +- results-vs-prev/compare-results.csv | 2 - results-vs-prev/tcwg-benchmark-results.log | 4 +- results_id | 2 +- 26 files changed, 117 insertions(+), 150 deletions(-) delete mode 100644 09-check_regression/bmk-specific-variability.csv delete mode 100644 09-check_regression/extra-bisect-params rename results_id.first => 09-check_regression/results_id.first (100%) create mode 100644 09-check_regression/trigger-bisect copy 10-update_baseline/console.log => 09-check_regression/trigger-notify (100%) delete mode 100755 dashboard/dashboard-generate.sh delete mode 100755 dashboard/dashboard-push.sh delete mode 100755 jenkins/dashboard-push.sh delete mode 100644 results-vs-prev/compare-results.csv -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/interesting-commits] branch master updated (c3dab4ff -> 0fa2dabe)

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 c3dab4ff Add entry b8d1a3a8ef9aff015ae963522287f7785bc552ec from https [...] new 0fa2dabe Add entry a37783de23c067d6a26374ff29c014e49604035c 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-7166-ga37783de23c | 1 + .../gnu_eabi-arm_eabi-master-O2_LTO}/build_url | 2 +- .../gnu_eabi-arm_eabi-master-O2_LTO/last_good | 1 + .../gnu_eabi-arm_eabi-master-O2_LTO}/summary.txt | 10 +++---- .../tcwg_bmk-code_speed-coremark/status.txt | 35 ++++++++++++++++++++++ 5 files changed, 43 insertions(+), 6 deletions(-) create mode 120000 gcc/basepoints/gcc-13-7166-ga37783de23c copy {binutils/sha1/ca26b8030e8c184bdeca7280e31c10c6e9fc3f78/tcwg_bmk-code_speed-c [...] create mode 100644 gcc/sha1/a37783de23c067d6a26374ff29c014e49604035c/tcwg_bmk-code [...] copy {binutils/sha1/fade906daab13c99fc329c1e08447f2aac168b62/tcwg_bmk-code_speed-c [...] create mode 100644 gcc/sha1/a37783de23c067d6a26374ff29c014e49604035c/tcwg_bmk-code [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gcc/master-aarch64 updated (a80aa001d7 -> 135610e7b8)

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 a80aa001d7 40: force: #64: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 135610e7b8 41: force: #66: 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 1980 -> 2124 bytes 02-prepare_abe/console.log.xz | Bin 2520 -> 2524 bytes 03-build_abe-binutils/console.log.xz | Bin 35804 -> 35888 bytes 04-build_abe-gcc/console.log.xz | Bin 203712 -> 203576 bytes 06-build_abe-linux/console.log.xz | Bin 8932 -> 8924 bytes 07-build_abe-glibc/console.log.xz | Bin 241708 -> 240788 bytes 08-build_abe-gdb/console.log.xz | Bin 34932 -> 35572 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3864 bytes 10-build_abe-check_gcc/console.log.xz | Bin 8164 -> 8360 bytes 11-check_regression/console.log.xz | Bin 1660 -> 1660 bytes 11-check_regression/trigger-bisect | 2 +- git/gdb_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 10 +- sumfiles/g++.log.sep.xz | Bin 1436 -> 1436 bytes sumfiles/g++.log.xz | Bin 1408 -> 1408 bytes sumfiles/g++.sum.sep | 2 +- sumfiles/gcc.log.sep.xz | Bin 4852 -> 4976 bytes sumfiles/gcc.log.xz | Bin 371972 -> 370812 bytes sumfiles/gcc.sum.sep | 580 +++++++++++++++++----------------- sumfiles/gfortran.log.sep.xz | Bin 3596 -> 3712 bytes sumfiles/gfortran.log.xz | Bin 55580 -> 55708 bytes sumfiles/gfortran.sum.sep | 322 +++++++++---------- sumfiles/libatomic.log.xz | Bin 436 -> 432 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 436 -> 432 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 436 -> 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 +- 32 files changed, 463 insertions(+), 465 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/interesting-commits] branch master updated (e4361c19 -> c3dab4ff)

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 e4361c19 Add entry 2134fcfee8b338a6f10273457145fc071dc8f092 from https [...] new c3dab4ff 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: {binutils => gdb}/gdb-13-branchpoint-1911-gb8d1a3a8ef9 | 0 .../tcwg_gnu_native_fast_check_gcc/master-aarch64/build_url | 2 +- .../tcwg_gnu_native_fast_check_gcc}/master-aarch64/last_good | 0 .../tcwg_gnu_native_fast_check_gcc/master-aarch64/summary.txt | 0 .../tcwg_gnu_native_fast_check_gcc/status.txt | 2 +- 5 files changed, 2 insertions(+), 2 deletions(-) copy {binutils => gdb}/gdb-13-branchpoint-1911-gb8d1a3a8ef9 (100%) copy {binutils/gcc/linux/glibc/gdb/sha1 => gdb/sha1/b8d1a3a8ef9aff015ae963522287f7 [...] copy {binutils/sha1/b8d1a3a8ef9aff015ae963522287f7785bc552ec/tcwg_gnu_native_check [...] copy {binutils => gdb}/sha1/b8d1a3a8ef9aff015ae963522287f7785bc552ec/tcwg_gnu_nati [...] copy {binutils => gdb}/sha1/b8d1a3a8ef9aff015ae963522287f7785bc552ec/tcwg_gnu_nati [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits April 2023