Tcwg-commits April 2023

tcwg-commits@lists.linaro.org

5 participants
5583 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-mainline-defconfig updated (e820be74ae -> 1006302171)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-mainline-defconfig in repository toolchain/ci/base-artifacts. from e820be74ae 61: onsuccess: #11: boot: [TCWG CI] Success after binutils/g [...] new 1006302171 62: onsuccess: #12: 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 1996 -> 1988 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2616 bytes 03-build_abe-binutils/console.log.xz | Bin 26864 -> 26956 bytes 04-build_abe-stage1/console.log.xz | Bin 89048 -> 90196 bytes 05-build_abe-qemu/console.log.xz | Bin 29632 -> 31196 bytes 06-build_linux/console.log.xz | Bin 4536 -> 4576 bytes 07-boot_linux/console.log.xz | Bin 5644 -> 5680 bytes 08-check_regression/console.log.xz | Bin 3720 -> 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/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_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 | 30 --------------------- mail/short-diag.txt | 1 - manifest.sh | 32 +++++++++++------------ 23 files changed, 24 insertions(+), 104 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 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.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-mainline-allyesconfig updated (0bdbd80316 -> be29c8e432)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from 0bdbd80316 59: onsuccess: #15: 21863: [TCWG CI] Success after binutils/ [...] new be29c8e432 60: onsuccess: #16: 21863: [TCWG CI] https://ci.linaro.org/j [...] 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 2016 -> 2228 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2608 bytes 03-build_abe-binutils/console.log.xz | Bin 27228 -> 27252 bytes 04-build_abe-stage1/console.log.xz | Bin 71464 -> 71580 bytes 05-build_abe-qemu/console.log.xz | Bin 29704 -> 31240 bytes 06-build_linux/console.log.xz | Bin 8612 -> 8624 bytes 08-check_regression/console.log.xz | Bin 3780 -> 608 bytes dashboard/dashboard-generate.sh | 17 ------------ dashboard/dashboard-push.sh | 7 ----- dashboard/squad-vs-first/results-functional.json | 1 - git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_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 | 30 --------------------- mail/short-diag.txt | 1 - manifest.sh | 32 +++++++++++------------ 22 files changed, 24 insertions(+), 104 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 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.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (7b255f7e49 -> 01a90bdfe8)

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-aarch64 in repository toolchain/ci/base-artifacts. discards 7b255f7e49 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards c04868c68c 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 0301592aac 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 50a86bf897 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards a55a38df90 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 2004039a15 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards a8ba507bc8 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 6a9fe2d06c 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards e36dad6d2b 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 36c43a09e3 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards ab61398480 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 529e9efb58 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards c315a88445 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 6a9d9b26d0 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 8d06c30eca 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 3ca8ddd844 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 641ad2237f 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards f6ca78e8bb 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards aeb6f4fcd2 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards e8f2825433 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 7ee7a55fb9 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 07aacaa227 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards dc44d03275 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards a3deecde31 214: onsuccess: #26: 1: Success after binutils: 12 commits discards fc04355cf5 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards 4b34f7f971 212: force: #24: 1: Success after binutils: 2 commits discards 8d8a1d7a28 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 83c9fdffab 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards bef5fc07c1 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards f0667b322f 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards c5a6650567 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards b25cd886d4 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 2b10d4ab7f 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 96f9f116aa 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 51d28e781a 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards ec3c3df5ac 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 3eb9d01a68 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards a89264eebd 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 1ee8d9b4a5 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 6c5c7e219c 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards bcc2d6e981 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 7fd56c999b 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 9ddd511398 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 69c000f9b8 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 293adaf642 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 18437ddf22 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 2dbd87e9b3 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards dbe46556ca 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] discards e5edfff3c5 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] discards 4c2496fc4f 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] discards 420e50a5ba 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] discards 75b65b402f 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] discards 795e95c6e3 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] discards e5a70c8cc1 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] discards 4588b31493 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits discards fc26bd237a 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] discards 8e13ea9c37 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] discards f934b24eed 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] discards d007227315 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] discards 59a7bbeb18 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] discards 4c307114c8 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] discards b280853fc4 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] discards 1b791059d5 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] discards 46bf4abded 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] discards 43e4240afd 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] discards d1b225bc3c 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] discards 6133710ec6 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] discards 27de1f7264 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] discards 3d55ef9487 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] discards 653baa1696 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] discards 7b3b3a3583 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] discards 1297e55ac9 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] discards dd1a30cea1 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] discards 0dfe255d41 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] discards 7d927e6c47 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] discards 27a8786428 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] discards e3130af25d 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] discards 265919ca78 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards 3ea0de44bb 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards d692de8eb1 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards 147df9c1e1 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards 400f27cc2b 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards 00e9e153fb 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards 98e83ce646 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards 9b1cecda75 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards fd73865c90 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards f7d89a6181 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] discards 60be757728 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] discards bc1d4a3224 149: onsuccess: #684: 1: Success after linux: 10 commits discards f24b26e492 148: onsuccess: #683: 1: Success after glibc: 9 commits discards d3b3d55c8e 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 8167447ede 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 905b6d7ac0 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards 6042daa425 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards 3c9d8ba120 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards 87270439b4 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 24f2ee4a8a 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards ca86dca35e 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards fe014d3a5d 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits discards be1f12251c 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards 07563da0c1 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new e078c1fa16 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new 269ecb41c4 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new 473fa7a18c 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new b7689a5a8f 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new dd7a61f698 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new 2274f90981 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 4110bdaea3 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new 628ed674b3 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new 66a0e93b77 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new eb8581fdcd 146: onsuccess: #680: 1: Success after binutils: 20 commits new 3ab3f1030b 147: onsuccess: #681: 1: Success after gcc: 6 commits new a5e26a5c3b 148: onsuccess: #683: 1: Success after glibc: 9 commits new 24c2a0f1fe 149: onsuccess: #684: 1: Success after linux: 10 commits new 89807a0918 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] new ded6d7bdb8 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new 9d78542b4c 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new 6a220f59c2 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new b1b6b96e52 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new 2adea9569a 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new 6dd7f77d06 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new aa9548655b 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new 0f7082ca18 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new ecf3a365d4 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new 5f8ab177a9 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new 25b201dbb7 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] new 5f8428bafa 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] new f3776cac88 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] new 133ef91e53 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] new a002e81d64 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] new aa514a2ac7 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] new 8a4a6bcbfd 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] new 11a493e1de 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] new b12219e948 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] new afd08caa07 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] new 291380c3ba 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] new eb59c8c5c2 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] new 4cd4b4528f 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] new 3ee8fc0167 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] new 917b878635 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] new 721ce62f49 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] new 818db47945 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] new 6338a3caef 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] new b2794b914c 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] new 2c019ebe14 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] new af18931f1e 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] new e3e8700102 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] new eeccf744ea 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits new 83fe7883f4 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] new c2081ecd33 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] new 74878d05d8 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] new 64c4394a7a 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] new 58242b6369 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] new 4e9fbbd593 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] new 53fb198ab9 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] new 8f54b138a2 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new bfcf25f2a2 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new f324dd4bc0 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 4dab8cde34 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new b1edfa63a5 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 7945d16315 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new acdba97a20 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 05bcdd6b5f 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 8bf36a90f0 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 1bc2e45792 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 38b3c8d9c0 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 7b952122a1 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new c43691aeb0 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 3fb31344ce 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 920c0f2832 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 0581798fc8 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new cf9f3520cd 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 2846b8c7dd 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 8b191ab1d7 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new e44e1f0031 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new c6ffb36079 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 69aa214247 212: force: #24: 1: Success after binutils: 2 commits new d74f8af8df 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new ccb716707c 214: onsuccess: #26: 1: Success after binutils: 12 commits new cf83afac92 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 7d108f8890 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 64aac079a1 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 3fca9304c0 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new dccd08e1ae 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 7d4a38a6e3 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new e63ac78405 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 40ec49ecb6 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new d23ae55eeb 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 2d3a40caa5 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new b6b05b460f 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new c2a7658ee8 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new f3f6b0f04a 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 0a2f5ec9a4 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 7db112eccc 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new a213393dbb 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 236e1fab14 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new d29fa24ff9 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 105c9b291a 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 4290c2a278 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new af44b296e3 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 81a9ba9aec 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new df423d537a 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 01a90bdfe8 238: onsuccess: #55: 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 (7b255f7e49) \ 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 2020 -> 2048 bytes 02-prepare_abe/console.log.xz | Bin 2584 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 35052 -> 35076 bytes 04-build_abe-gcc/console.log.xz | Bin 203304 -> 203764 bytes 06-build_abe-linux/console.log.xz | Bin 8588 -> 8788 bytes 07-build_abe-glibc/console.log.xz | Bin 240716 -> 240980 bytes 08-build_abe-gdb/console.log.xz | Bin 34652 -> 34656 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3856 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2180 -> 2156 bytes 11-check_regression/console.log.xz | Bin 1320 -> 1320 bytes 11-check_regression/results.compare | 4 +-- 11-check_regression/results.compare2 | 4 +-- 12-update_baseline/console.log | 42 ++++++++++++++--------------- 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/results.compare | 4 +-- manifest.sh | 32 +++++++++++----------- sumfiles/binutils.log.xz | Bin 63144 -> 62676 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150608 -> 150684 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122620 -> 122584 bytes sumfiles/ld.sum | 4 +-- 27 files changed, 54 insertions(+), 54 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[gcc] branch master updated (edc6659c97c -> 9d1a6119590)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from edc6659c97c testsuite: filter out warning noise for CWE-1341 test new 2134fcfee8b loop-iv: Fix up bounds computation new 9d1a6119590 combine: Fix AND handling for WORD_REGISTER_OPERATIONS targ [...] The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/combine.cc | 9 ++++++--- gcc/loop-iv.cc | 2 +- gcc/simplify-rtx.cc | 8 +++++++- gcc/testsuite/gcc.c-torture/execute/pr109040.c | 23 +++++++++++++++++++++++ gcc/testsuite/gcc.dg/pr108947.c | 21 +++++++++++++++++++++ 5 files changed, 58 insertions(+), 5 deletions(-) create mode 100644 gcc/testsuite/gcc.c-torture/execute/pr109040.c create mode 100644 gcc/testsuite/gcc.dg/pr108947.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-coremark/gnu_eabi-arm_eabi-master-O2 updated (43e1bd3634 -> 3a57e3e23d)

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 in repository toolchain/ci/base-artifacts. from 43e1bd3634 59: onsuccess: #13: 1: [TCWG CI] Success after binutils/gcc: [...] new 3a57e3e23d 60: onsuccess: #15: 1: [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 1976 -> 1960 bytes 02-prepare_abe/console.log.xz | Bin 2564 -> 2628 bytes 03-build_abe-binutils/console.log.xz | Bin 26940 -> 27032 bytes 04-build_abe-stage1/console.log.xz | Bin 87048 -> 87700 bytes 06-build_abe-newlib/console.log.xz | Bin 12380 -> 12500 bytes 07-build_abe-stage2/console.log.xz | Bin 161904 -> 162584 bytes 08-benchmark/benchmark-build.log | 104 ++++++++++++++-------------- 08-benchmark/benchmark.log | 102 +++++++++++++-------------- 08-benchmark/console.log.xz | Bin 4060 -> 3972 bytes 09-check_regression/console.log.xz | Bin 7184 -> 4476 bytes 09-check_regression/mail-body.txt | 13 ---- 09-check_regression/mail-subject.txt | 1 - dashboard/dashboard-generate.sh | 17 ----- dashboard/dashboard-push.sh | 7 -- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/newlib_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 | 30 -------- mail/short-diag.txt | 1 - manifest.sh | 30 ++++---- results-vs-first/tcwg-benchmark-results.log | 2 +- results-vs-prev/tcwg-benchmark-results.log | 4 +- results_id | 2 +- 28 files changed, 127 insertions(+), 218 deletions(-) delete mode 100644 09-check_regression/mail-body.txt delete mode 100644 09-check_regression/mail-subject.txt delete mode 100755 dashboard/dashboard-generate.sh delete mode 100755 dashboard/dashboard-push.sh 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.

1 year, 7 months

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

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards efd2597b5f 491: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 4fc6ed20c7 490: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 9bb2669ec6 489: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 07994f1e4a 488: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 6da4e898da 487: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 14b9c388ab 486: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards e2e34717c7 485: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 1a81ec3f0b 484: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 2b71f3f9c6 483: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 314d7ba3a1 482: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 050b6f1bf7 481: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 0386a73972 480: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards a889280f52 479: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards a2fee5e96d 478: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards d6a277832e 477: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 375534ae87 476: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards aa28b890df 475: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards d4b148fc66 474: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards d5308207d9 473: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards c3443271da 472: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards f5148ec526 471: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards c6d7a60eff 470: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards e0b3fd9a66 469: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards f465322743 468: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards b4bf0d0d13 467: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 5037b6d81e 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 84c84ea6c2 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards e70a0d3075 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] discards a2418adeb1 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] discards 484c593384 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gli [...] discards 8588f7fceb 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] discards 5eaffac57e 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards dfa7181294 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] discards baf6ed05e1 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 2df08873cb 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards ee70d20550 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] discards bbda505962 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards de9f0e6d28 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards ec6ef46c8b 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] discards 9b8310ef02 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 71b223079f 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards a707085288 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards ba71978c77 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] discards 2f960e9db7 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 7c4a23fdb9 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 0cefda9574 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards 9626ef43c5 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards fc5222e97e 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards cd88847824 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 2b427d12f1 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 544e8483ed 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] discards 750ce3cb49 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] discards 93b36a90ef 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] discards 70ef9fa5ef 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] discards b4ee0d899b 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] discards 925bbecb13 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards 9dbedd91f7 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] discards f62f685277 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] discards 96fae93a8a 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] discards 0cc4407708 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards f08e39fd67 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards 54cd6876d1 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards fddc5be74e 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards 6c084be00d 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards a12268f43e 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards 2518b7f836 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards e491321b73 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards 7b38804c23 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 52cc30f98f 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards a8753a19e6 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards 594ec5c0d8 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 2e0830aec0 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 78c125008c 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 3046269378 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards ebc95ffa05 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 6cb067cf6a 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 1f53e8040a 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 15bac24046 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards cb865b7c85 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards e5b65ad049 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 086401961e 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 5a1a36108e 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards a6ff98a2b0 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards e459a52550 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 21ad5ade42 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards cb72455820 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 5859d4b613 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards c45e44863e 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 5281c97c7e 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 880ac8a9f3 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 65ca8263c1 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 395ade6c7a 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards e69e2be914 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards cdb5b6338d 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 70ae682fe7 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 53255884ac 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards b6fbb9fda3 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards ecad27eb97 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 8c422d4ecb 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards a317b39906 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards fa8e63653f 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new b43079dda3 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new be8d3a7f9b 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new efa60157f9 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 7108cca9bc 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 6571e6a909 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 1951283217 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 0dbdb5b560 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 2988fecdbb 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 6f9a9c98eb 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 259c43a279 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 5c8cbb5117 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new c569239b62 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new ac2e230383 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 9fcf3c4a9b 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new a5f66f0110 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new b595e0d509 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 13418ccd03 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 39f749e802 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 534dd6e1ba 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 6766031e5d 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new bf407d41d9 411: onsuccess: #2232: 1: Success after gcc: 3 commits new c455652d1d 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 95fbec0672 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 8b9defb311 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new bb5555c849 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 9733328ccc 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new 41c79d3ee8 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 9921761de1 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new ce78988f13 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new f6d3f6f43a 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new e570082f82 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 04ad71b8ae 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new b6ab650ad0 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 722565f2a6 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 4fac64a7f7 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new 949e6306ee 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new edeba2fe56 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new ed1b7a1be2 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 88c669e428 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new a3f8975644 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new a0731a0ed4 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new d90bd117ba 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new 3a690c420f 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] new 2f16c46e03 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] new 75904e8335 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] new e583d768b1 436: onsuccess: #2260: 1: Success after gcc: 7 commits new 061700385d 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] new 8c6063762c 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] new a50f810894 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] new f8c41e5d55 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] new 8f7ecdc8b2 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] new 4654befb07 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] new 12aafe2a85 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new e2ba3fc674 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new a21974dcb0 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 73d6c59b91 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new 8144faab61 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new fac10ce1e5 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 070bcc0acc 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] new cbc952a1e2 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new fad537f7c4 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 37aa3d970c 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 2bb055e643 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] new a069d22647 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new a06253118d 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new 73601a9e22 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] new 3baa16e636 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new b2ac35566d 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 45ba148c6f 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] new 365c685837 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new 98eef8809a 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] new 0108d11b70 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gli [...] new 4b945d0184 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] new fc3d976f2f 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] new 59d23d738c 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new cd943d3863 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 8492ef73fb 467: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 7934ae0d8b 468: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 86a2a74b19 469: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new d8a684d500 470: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new e95c77f899 471: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new bcddcee951 472: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 3c8c8a9b3b 473: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 067b1be37b 474: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new daa4c942c3 475: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 839d66ef72 476: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 8ae6ec86c5 477: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 936e2fd590 478: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 90b265e671 479: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new e0243eca6b 480: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 3829535097 481: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 229331d181 482: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new ca2d985ba6 483: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new ac73bed98e 484: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 88b5ef1653 485: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 56feafdf19 486: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 13b0d1999b 487: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 60d1783c79 488: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 55b3d256c9 489: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 4e298d1be0 490: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new b03c6912fd 491: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new e428c54886 492: onsuccess: #55: 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 (efd2597b5f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2132 -> 2096 bytes 02-prepare_abe/console.log.xz | Bin 2540 -> 2612 bytes 03-build_abe-binutils/console.log.xz | Bin 27184 -> 26808 bytes 04-build_abe-stage1/console.log.xz | Bin 88676 -> 89864 bytes 06-build_abe-linux/console.log.xz | Bin 8616 -> 8776 bytes 07-build_abe-glibc/console.log.xz | Bin 233160 -> 232404 bytes 08-build_abe-stage2/console.log.xz | Bin 225060 -> 225124 bytes 09-build_abe-gdb/console.log.xz | Bin 34624 -> 34324 bytes 10-build_abe-qemu/console.log.xz | Bin 31628 -> 30596 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3852 bytes 12-build_abe-check_gcc/console.log.xz | Bin 6784 -> 6740 bytes 13-check_regression/console.log.xz | Bin 3012 -> 2480 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 10 + 13-check_regression/results.compare | 37 +- 13-check_regression/results.compare2 | 140 +- 13-check_regression/results.regressions | 44 + 14-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 17 - dashboard/dashboard-push.sh | 7 - .../squad-vs-first/score/results-functional.json | 1 - git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- jenkins/dashboard-push.sh | 7 - jenkins/notify.sh | 2 +- {13-check_regression => mail}/results.compare | 37 +- mail/results.regressions | 44 + manifest.sh | 46 +- results | 44 + sumfiles/g++.log.sep.xz | Bin 175244 -> 115452 bytes sumfiles/g++.log.xz | Bin 2685960 -> 2665504 bytes sumfiles/g++.sum | 17 +- sumfiles/g++.sum.sep | 11669 ++----------------- sumfiles/gcc.log.sep.xz | Bin 118144 -> 152120 bytes sumfiles/gcc.log.xz | Bin 2226624 -> 2237916 bytes sumfiles/gcc.sum | 19 +- sumfiles/gcc.sum.sep | 10809 +++++++++-------- sumfiles/gfortran.log.sep.xz | Bin 40700 -> 46160 bytes sumfiles/gfortran.log.xz | Bin 906160 -> 900128 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 5523 +++++---- sumfiles/libatomic.log.xz | Bin 2284 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217320 -> 217492 bytes sumfiles/libgomp.sum | 8 +- sumfiles/libitm.log.xz | Bin 2688 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 14704 -> 11560 bytes sumfiles/libstdc++.log.xz | Bin 447600 -> 447388 bytes sumfiles/libstdc++.sum | 8 +- sumfiles/libstdc++.sum.sep | 552 +- 55 files changed, 10210 insertions(+), 18896 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions 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 copy {13-check_regression => mail}/results.compare (80%) create mode 100644 mail/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-allnoconfig updated (60f50d69d8 -> 02fdf83898)

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-stable-allnoconfig in repository toolchain/ci/base-artifacts. from 60f50d69d8 58: onsuccess: #11: boot: [TCWG CI] Success after binutils/l [...] new 02fdf83898 59: onsuccess: #12: 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 1996 -> 1996 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2564 bytes 03-build_abe-binutils/console.log.xz | Bin 26916 -> 27260 bytes 04-build_kernel_llvm/console.log.xz | Bin 65608 -> 67156 bytes 05-build_abe-qemu/console.log.xz | Bin 29848 -> 31316 bytes 06-build_linux/console.log.xz | Bin 2916 -> 2928 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3312 -> 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 | 3 +++ mail/changes-list-long.txt | 14 ---------- mail/changes-list-short.txt | 1 - mail/check-regression-status.txt | 1 + mail/last_good.sh | 30 --------------------- mail/short-diag.txt | 1 - manifest.sh | 32 +++++++++++------------ 23 files changed, 24 insertions(+), 98 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 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.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-fujitsu_speed-cpu2017speed/gnu-aarch64-master-O2 updated (3bd84eced1 -> e0053d315c)

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-fujitsu_speed-cpu2017speed/gnu-aarch64-master-O2 in repository toolchain/ci/base-artifacts. from 3bd84eced1 4: onsuccess: #11: 1: [TCWG CI] 620.omnetpp_s speeds up by - [...] new e0053d315c 5: onsuccess: #35: 1: [TCWG CI] https://ci.linaro.org/job/tc [...] 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 -> 2156 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2624 bytes 03-build_abe-binutils/console.log.xz | Bin 31228 -> 27500 bytes 04-build_abe-stage1/console.log.xz | Bin 71708 -> 71344 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8676 -> 8376 bytes 07-build_abe-glibc/console.log.xz | Bin 245796 -> 241648 bytes 08-build_abe-stage2/console.log.xz | Bin 177360 -> 175724 bytes 09-benchmark/benchmark-build.log | 120 +- 09-benchmark/benchmark.log | 118 +- 09-benchmark/console.log.xz | Bin 3988 -> 4160 bytes 10-check_regression/620.omnetpp_s.symbols-skipped | 1 + 10-check_regression/621.wrf_s.symbols-regression | 3 + 10-check_regression/628.pop2_s.symbols-regression | 2 + 10-check_regression/bmk-specific-variability.csv | 49 + .../compare-results-vs-first-internal.csv | 79 - .../compare-results-vs-prev-internal.csv | 79 - 10-check_regression/console.log.xz | Bin 13432 -> 11044 bytes .../csv-results-vs-first-1/md5sum.csv | 1681 - .../csv-results-vs-prev-0/md5sum.csv | 1732 - 10-check_regression/csv-results-vs-prev-0/perf.csv | 1933 - 10-check_regression/csv-results-vs-prev-1/perf.csv | 1842 - 10-check_regression/exe.improvement | 2 - 10-check_regression/extra-bisect-params | 2 +- 10-check_regression/jira-body.txt | 5 - 10-check_regression/mail-body.txt | 17 - 10-check_regression/mail-subject.txt | 1 - .../output-bmk-results/error_code-1 | 0 .../output-bmk-results/exe.improvement | 2 - .../output-bmk-results/extra-bisect-params | 1 + .../output-bmk-results/symbol.regression.diff | 1 + 10-check_regression/results-vs-first-brief.csv | 26 - 10-check_regression/results-vs-first-full.csv | 1839 - 10-check_regression/results-vs-first-internal.csv | 80 - 10-check_regression/results-vs-first.csv | 80 - 10-check_regression/results-vs-first.log | 2398 - 10-check_regression/results-vs-prev-brief.csv | 26 - 10-check_regression/results-vs-prev-full.csv | 1839 - 10-check_regression/results-vs-prev-internal.csv | 80 - 10-check_regression/results-vs-prev.csv | 80 - 10-check_regression/results-vs-prev.log | 2398 - 10-check_regression/symbol.regression | 5 + dashboard/dashboard-generate.sh | 17 - dashboard/dashboard-push.sh | 7 - .../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 | 4 - .../607.cactuBSSN_s/results-functional.json | 4 - .../607.cactuBSSN_s/results-metadata.json | 12 - .../607.cactuBSSN_s/results-metrics.json | 5 - .../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 | 5 - .../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 | 5 - .../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 | 5 - dashboard/squad-vs-first/dashboard-push-squad.sh | 179 - dashboard/squad-vs-first/summary-annotation.txt | 1 - 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/check-regression-status.txt | 1 + mail/exe.regression | 2 + mail/jira-body.txt | 29 - mail/mail-body.txt | 41 - mail/mail-subject.txt | 1 - mail/symbol.regression | 5 + manifest.sh | 36 +- results-vs-first/compare-results-internal.csv | 75 + .../csv-results-0}/md5sum.csv | 1262 +- .../csv-results-0}/perf.csv | 0 .../csv-results-0}/results.csv | 1280 +- .../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 | 1767 + results-vs-first/csv-results-1/perf.csv | 1935 + .../csv-results-1}/results.csv | 764871 +++++++++--------- .../csv-results-1}/size.csv | 70057 +- .../csv-results-1}/sve.csv | 0 .../csv-results-1}/vect.csv | 0 results-vs-first/interesting-symbols.csv | 73 + results-vs-first/results-brief.csv | 26 + results-vs-first/results-full.csv | 1936 + results-vs-first/results-internal.csv | 78 + results-vs-first/results.csv | 78 + results-vs-first/tcwg-benchmark-results.log | 5232 + results-vs-prev/compare-results-internal.csv | 75 + .../compare-results.csv | 23 +- .../csv-results-0}/md5sum.csv | 1280 +- .../csv-results-0}/perf.csv | 0 .../csv-results-0}/results.csv | 1304 +- .../csv-results-0}/size.csv | 0 .../csv-results-0}/sve.csv | 0 .../csv-results-0}/vect.csv | 0 results-vs-prev/csv-results-1/md5sum.csv | 1767 + results-vs-prev/csv-results-1/perf.csv | 1935 + .../csv-results-1}/results.csv | 764666 ++++++++--------- .../csv-results-1}/size.csv | 70478 +- .../csv-results-1}/sve.csv | 0 .../csv-results-1}/vect.csv | 0 results-vs-prev/interesting-symbols.csv | 73 + results-vs-prev/results-brief.csv | 26 + results-vs-prev/results-full.csv | 1936 + results-vs-prev/results-internal.csv | 78 + results-vs-prev/results.csv | 78 + results-vs-prev/tcwg-benchmark-results.log | 5232 + results_id | 2 +- 162 files changed, 861555 insertions(+), 853361 deletions(-) create mode 100644 10-check_regression/620.omnetpp_s.symbols-skipped create mode 100644 10-check_regression/621.wrf_s.symbols-regression create mode 100644 10-check_regression/628.pop2_s.symbols-regression 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-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/perf.csv delete mode 100644 10-check_regression/exe.improvement delete mode 100644 10-check_regression/jira-body.txt delete mode 100644 10-check_regression/mail-body.txt delete mode 100644 10-check_regression/mail-subject.txt create mode 100644 10-check_regression/output-bmk-results/error_code-1 delete mode 100644 10-check_regression/output-bmk-results/exe.improvement create mode 100644 10-check_regression/output-bmk-results/extra-bisect-params create mode 100644 10-check_regression/output-bmk-results/symbol.regression.diff 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 create mode 100644 10-check_regression/symbol.regression delete mode 100755 dashboard/dashboard-generate.sh delete mode 100755 dashboard/dashboard-push.sh 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 create mode 100644 mail/check-regression-status.txt create mode 100644 mail/exe.regression delete mode 100644 mail/jira-body.txt delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/symbol.regression create mode 100644 results-vs-first/compare-results-internal.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 [...] 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-1 => 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-first-1 => results-vs-first/csv-results [...] rename {10-check_regression/csv-results-vs-first-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- [...] 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- [...] 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-0 [...] rename {10-check_regression/csv-results-vs-prev-0 => results-vs-prev/csv-results-0 [...] 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-0 => results-vs-prev/csv-results-1 [...] rename {10-check_regression/csv-results-vs-prev-0 => results-vs-prev/csv-results-1 [...] rename {10-check_regression/csv-results-vs-prev-1 => results-vs-prev/csv-results-1 [...] rename {10-check_regression/csv-results-vs-prev-1 => 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.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-allnoconfig updated (a796cd7e7c -> 9ab28204b6)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-allnoconfig in repository toolchain/ci/base-artifacts. from a796cd7e7c 59: onsuccess: #11: boot: [TCWG CI] Success after binutils/l [...] new 9ab28204b6 60: onsuccess: #12: 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 2016 -> 1988 bytes 02-prepare_abe/console.log.xz | Bin 2564 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 27284 -> 27092 bytes 04-build_kernel_llvm/console.log.xz | Bin 67480 -> 64748 bytes 05-build_abe-qemu/console.log.xz | Bin 31308 -> 30204 bytes 06-build_linux/console.log.xz | Bin 3488 -> 2960 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3332 -> 524 bytes 09-update_baseline/console.log | 9 ------- 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 | 3 +++ mail/changes-list-long.txt | 14 ---------- mail/changes-list-short.txt | 1 - mail/check-regression-status.txt | 1 + mail/last_good.sh | 30 --------------------- mail/short-diag.txt | 1 - manifest.sh | 32 +++++++++++------------ results | 2 +- 25 files changed, 25 insertions(+), 108 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 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.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (92056cca51 -> 4cad7cbd18)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 92056cca51 261: onsuccess: #145: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 44bf547454 260: force: #144: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards e8623bebd5 259: onsuccess: #143: 1: [TCWG CI] https://ci.linaro.org/job [...] discards f812cec5e2 258: onsuccess: #136: 1: [TCWG CI] Success after binutils/gc [...] discards 85e1bb7570 257: onsuccess: #135: 1: [TCWG CI] Success after binutils/gc [...] discards 2f9c564649 256: onsuccess: #134: 1: [TCWG CI] Success after binutils/gc [...] discards 015036ee8c 255: force: #133: 1: [TCWG CI] Success after baseline build: [...] discards ec1c0bf7fb 254: onsuccess: #132: 1: [TCWG CI] Success after gdb: 2 commits discards 580f0a8cf3 253: force: #131: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 1d279a5731 252: force: #130: 1: [TCWG CI] Success after gdb: 15 commits discards 7d05a14667 251: onsuccess: #129: 1: [TCWG CI] Success after linux: 121 commits discards a20b982810 250: onsuccess: #128: 1: [TCWG CI] Success after glibc: 2 commits discards ec9243c4cc 249: onsuccess: #127: 1: [TCWG CI] Success after gcc: 98 commits discards 829cedf8a1 248: onsuccess: #121: 1: [TCWG CI] Success after binutils/gc [...] discards 9a238533dc 247: force: #120: 1: [TCWG CI] Success after baseline build: [...] discards 7a28114591 246: onsuccess: #118: 1: [TCWG CI] Success after glibc: 7 commits discards e0c78517ef 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 commits discards 047dd6403e 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] discards 5a02994ae2 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] discards 7881e47dcf 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits discards 63321a3ea1 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] discards c4a0060fe5 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] discards 7eccf91f24 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] discards 9f84d4b2d6 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 3c5e399ee7 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits discards a4f1c477a0 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] discards 78000fc687 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 76d76c0d6f 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 1e7ef6700a 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards aa6bc727e0 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 59fbfb24be 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards c3c907d17a 230: onsuccess: #78: 1: Success after gdb: 2 commits discards 3122be3ef1 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] discards 52158c1843 228: force: #74: 1: Success after gdb: 53 commits discards 2089509951 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards b35939f825 226: force: #70: 1: Success after baseline build: no new commits discards 2ef5d437b4 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] discards bc633d1322 224: force: #65: 1: Success after gdb: 50 commits discards 86f5b9db6d 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] discards 439f1fbab5 222: force: #60: 1: Success after gdb: 16 commits discards 6dfc0a4bf5 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] discards 431a52b16b 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] discards e71d59d6e8 219: force: #50: 1: Failure after linux: 2520 commits discards 24786a3b8f 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] discards 48ec898a73 217: force: #45: 1: Success after linux: 1 commits discards a97bf604c0 216: force: #43: : Failure after baseline build: no new commits discards d0a68ee44c 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards 9bf5e445dc 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards 421b4ac76c 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 4e8d743627 212: force: #27: : Failure after baseline build: no new commits discards 26efc28fb3 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 521af4495e 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards d30c20a219 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards f18149be59 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 05ef00619d 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 5161a36e7b 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards c3f95974f9 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards ca1b93c0ca 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 742a49ce6a 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards cfc7808381 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards d47f4a0681 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards e5b3f1742d 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards fe6c761310 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards a0bf22c033 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 55b3cdc067 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 88cbeb574e 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards f043781cb8 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards dcae95f7f2 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 219f0188fe 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 7640f62133 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards 90bfcf90be 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] discards 17d5169ee4 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards abf878087d 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] discards a25d09e63d 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] discards 654046f218 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] discards ccc48cdf66 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] discards c621abf057 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] discards 180c65dc05 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] discards b212377d43 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] discards 5e7354f0af 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] discards 47935918e6 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 12facb15a0 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] discards 62ef393995 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] discards 5853fd9b87 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards bfa0f85490 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] discards c3ee8a5a55 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards 1f3ecd5474 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 494192fe5e 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards c63f98eb6f 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] discards 9e423ce10f 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] discards 43000780eb 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards dc35182fec 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] discards 346b997147 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards a1b3ad99e9 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 70cb13a813 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards b1ad46f737 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards ccc64192d2 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 868153fcaa 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards 132b0e0131 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards b6c891137e 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards de69265ded 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new 9269d05394 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new 41d1789fe8 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new b3029a1d60 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 088c6d47f8 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new 8ae5422150 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 5b97b0c705 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new dccd764cd6 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new 6cd956dc33 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new 62b2e421de 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new d92c755392 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] new e16cf6face 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 8881cf9f05 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] new d96be700d2 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] new 419cad3ceb 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new cd3eb183b5 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new 399b79de69 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new 180634be04 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] new 16110c4dfb 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new 6c3db44a11 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] new e0414e7435 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] new aaabde51d5 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 031af1cd23 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] new bce220d40f 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] new 5ab3b0e76b 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] new c59619e85e 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] new 8b41d16a32 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] new 9bf50f8336 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] new fca21a05e2 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] new 3cc369ebdf 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] new 550601a974 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 1dda38ccdb 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] new 7733d3c03e 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new 7f9043a18a 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new b0a612466a 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 9f56f800fd 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 439b7c2e0c 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new ecb41a768e 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new a7c1248837 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 20aa76be9b 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 8d11759a4e 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 7a6e18a926 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new f8b4985722 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new e4197181a4 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new e71f09b653 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new a072d24006 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 2557e03e9b 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new d9c35036bb 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 13a510bfee 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 87fcba9517 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new e0217bf1c3 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new a0c5d9827e 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 8790286f05 212: force: #27: : Failure after baseline build: no new commits new b0283c3652 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 03a8fcb880 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new ff579b89fc 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new e93624ee8c 216: force: #43: : Failure after baseline build: no new commits new c6052df0f5 217: force: #45: 1: Success after linux: 1 commits new 8aba1bc236 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] new 566a757485 219: force: #50: 1: Failure after linux: 2520 commits new 2ef88fd04f 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] new e4b824a38e 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] new e0a41820aa 222: force: #60: 1: Success after gdb: 16 commits new a260ce8cdd 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] new 4692fc98c7 224: force: #65: 1: Success after gdb: 50 commits new bf6feabfe8 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] new fe0f4ff61b 226: force: #70: 1: Success after baseline build: no new commits new 822bc39eaf 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new b54760a82d 228: force: #74: 1: Success after gdb: 53 commits new 579b611da4 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] new 0401382cfb 230: onsuccess: #78: 1: Success after gdb: 2 commits new 6b5365541a 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new 1a7b397367 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 2f0fdb5722 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 93dd450bcc 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 121698b95b 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new 3bcbff7897 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] new 49b51b48f8 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits new a859efe946 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new d388227a38 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] new a3e96a42a7 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] new a99d686999 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] new 7f1c753fde 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits new 58356a0c7f 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] new a533d6d3e8 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] new f82732eb98 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 commits new 7a75054eb7 246: onsuccess: #118: 1: [TCWG CI] Success after glibc: 7 commits new e3a09bcb76 247: force: #120: 1: [TCWG CI] Success after baseline build: [...] new da85863419 248: onsuccess: #121: 1: [TCWG CI] Success after binutils/gc [...] new c2f9f2ab15 249: onsuccess: #127: 1: [TCWG CI] Success after gcc: 98 commits new 7bcab078de 250: onsuccess: #128: 1: [TCWG CI] Success after glibc: 2 commits new e581edf48a 251: onsuccess: #129: 1: [TCWG CI] Success after linux: 121 commits new 76715b3994 252: force: #130: 1: [TCWG CI] Success after gdb: 15 commits new 13444a85f7 253: force: #131: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 3060029853 254: onsuccess: #132: 1: [TCWG CI] Success after gdb: 2 commits new 673d8d10ab 255: force: #133: 1: [TCWG CI] Success after baseline build: [...] new d66d5f19ba 256: onsuccess: #134: 1: [TCWG CI] Success after binutils/gc [...] new e7b268344e 257: onsuccess: #135: 1: [TCWG CI] Success after binutils/gc [...] new 04faba9a20 258: onsuccess: #136: 1: [TCWG CI] Success after binutils/gc [...] new 62c3fdd224 259: onsuccess: #143: 1: [TCWG CI] https://ci.linaro.org/job [...] new 8013bb438d 260: force: #144: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new 51b6d3b185 261: onsuccess: #145: 1: [TCWG CI] https://ci.linaro.org/job [...] new 4cad7cbd18 262: onsuccess: #146: 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 (92056cca51) \ 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 2068 -> 2020 bytes 02-prepare_abe/console.log.xz | Bin 2520 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 48676 -> 48596 bytes 04-build_abe-gcc/console.log.xz | Bin 235716 -> 235188 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8576 -> 8772 bytes 07-build_abe-glibc/console.log.xz | Bin 232132 -> 232524 bytes 08-build_abe-gdb/console.log.xz | Bin 47828 -> 47144 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3804 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4812 -> 4608 bytes 11-check_regression/console.log.xz | Bin 2676 -> 3548 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 338 ++++++++-- 12-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 17 - dashboard/dashboard-push.sh | 7 - .../squad-vs-first/score/results-functional.json | 1 - git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/dashboard-push.sh | 7 - jenkins/notify.sh | 2 +- {11-check_regression => mail}/results.compare | 4 +- manifest.sh | 36 +- sumfiles/gdb.log.0.xz | Bin 2951740 -> 2915808 bytes sumfiles/gdb.log.1.xz | Bin 142564 -> 133340 bytes sumfiles/gdb.log.10.xz | Bin 0 -> 9988 bytes sumfiles/gdb.log.11.xz | Bin 0 -> 9972 bytes sumfiles/gdb.log.12.xz | Bin 0 -> 10036 bytes sumfiles/gdb.log.13.xz | Bin 0 -> 10028 bytes sumfiles/gdb.log.14.xz | Bin 0 -> 10072 bytes sumfiles/gdb.log.15.xz | Bin 0 -> 9856 bytes sumfiles/gdb.log.2.xz | Bin 20488 -> 11608 bytes sumfiles/gdb.log.3.xz | Bin 19460 -> 10072 bytes sumfiles/gdb.log.4.xz | Bin 15148 -> 9888 bytes sumfiles/gdb.log.5.xz | Bin 9828 -> 9864 bytes sumfiles/gdb.log.6.xz | Bin 10072 -> 9924 bytes sumfiles/gdb.log.7.xz | Bin 9904 -> 10048 bytes sumfiles/gdb.log.8.xz | Bin 9976 -> 10076 bytes sumfiles/gdb.log.9.xz | Bin 0 -> 9984 bytes sumfiles/gdb.sum | 273 ++------ sumfiles/gdb.sum.0 | 282 ++------ sumfiles/gdb.sum.1 | 745 ++++----------------- sumfiles/{gdb.sum.7 => gdb.sum.10} | 32 +- sumfiles/{gdb.sum.7 => gdb.sum.11} | 76 ++- sumfiles/{gdb.sum.6 => gdb.sum.12} | 18 +- sumfiles/{gdb.sum.6 => gdb.sum.13} | 21 +- sumfiles/{gdb.sum.7 => gdb.sum.14} | 42 +- sumfiles/{gdb.sum.6 => gdb.sum.15} | 32 +- sumfiles/gdb.sum.2 | 503 +------------- sumfiles/gdb.sum.3 | 491 +------------- sumfiles/gdb.sum.4 | 309 +-------- sumfiles/gdb.sum.5 | 52 +- sumfiles/gdb.sum.6 | 39 +- sumfiles/gdb.sum.7 | 44 +- sumfiles/gdb.sum.8 | 49 +- sumfiles/{gdb.sum.6 => gdb.sum.9} | 41 +- 59 files changed, 879 insertions(+), 2654 deletions(-) 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 copy {11-check_regression => mail}/results.compare (75%) create mode 100644 sumfiles/gdb.log.10.xz create mode 100644 sumfiles/gdb.log.11.xz create mode 100644 sumfiles/gdb.log.12.xz create mode 100644 sumfiles/gdb.log.13.xz create mode 100644 sumfiles/gdb.log.14.xz create mode 100644 sumfiles/gdb.log.15.xz create mode 100644 sumfiles/gdb.log.9.xz copy sumfiles/{gdb.sum.7 => gdb.sum.10} (99%) copy sumfiles/{gdb.sum.7 => gdb.sum.11} (98%) copy sumfiles/{gdb.sum.6 => gdb.sum.12} (99%) copy sumfiles/{gdb.sum.6 => gdb.sum.13} (99%) copy sumfiles/{gdb.sum.7 => gdb.sum.14} (99%) copy sumfiles/{gdb.sum.6 => gdb.sum.15} (99%) copy sumfiles/{gdb.sum.6 => gdb.sum.9} (99%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits April 2023