Tcwg-commits April 2023

tcwg-commits@lists.linaro.org

5 participants
5583 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (8416d5d20944 -> c3479ea69927)

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 8416d5d20944 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] discards 9e213107e120 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards a2ef64840363 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards 5339edd78e2a 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards c54267efea9e 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards 3ffb057434d9 222: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards 13e8f4135a06 221: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards 3e14b2949432 220: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards 39bcf1c93733 219: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards 5e782e88e8e1 218: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 7788c7ba84c3 217: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards 9decb6219dc2 216: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards fce842d7c0ca 215: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards 52464fe91346 214: onsuccess: #26: 1: Success after binutils: 12 commits discards c5f62bcb69a2 213: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] discards b7a79a4d098f 212: force: #24: 1: Success after binutils: 2 commits discards d1fac31991fa 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 7b7683ad2215 210: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 787f76bc7624 209: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards febc028b2acb 208: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 49632b6374c9 207: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards cf73b15bd8f2 206: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 6dc3edfdf5e6 205: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 381caee3170d 204: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 63bc921d172e 203: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards 70793a296438 202: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards ba80398f78db 201: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards ed87a3a8cbd8 200: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 30df575b0daf 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards c1f08ccfbb0a 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 773c25dfced8 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards 2068f026c1a4 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards 005855cb0e56 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards cea0a89f143a 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards 0066b0346d75 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 63c07f9b792d 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards 4bdfd55a1645 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 50ff725c65a9 190: onsuccess: #726: 1: Success after binutils/gcc/linux/ [...] discards 6f7fc63779b0 189: onsuccess: #725: 1: Success after binutils/gcc/linux/ [...] discards 92f145eb4c17 188: onsuccess: #724: 1: Success after binutils/gcc/linux/ [...] discards 81284f7aad5f 187: onsuccess: #723: 1: Success after binutils/gcc/linux/ [...] discards 51da5668163e 186: onsuccess: #722: 1: Success after binutils/gcc/linux/ [...] discards 824b9089dd3b 185: onsuccess: #721: 1: Success after binutils/gcc/linux/ [...] discards ad3a8589244e 184: onsuccess: #720: 1: Success after binutils/gcc/linux/ [...] discards 75a9a31212a9 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 2 [...] discards 458bcb8aa9a9 182: onsuccess: #718: 1: Success after binutils/gcc/linux/ [...] discards 169c9319b025 181: onsuccess: #717: 1: Success after binutils/gcc/linux/ [...] discards 67456e628b1d 180: onsuccess: #716: 1: Success after binutils/gcc/linux/ [...] discards 8495442fab08 179: onsuccess: #715: 1: Success after binutils/gcc/linux/ [...] discards 54d3c1556597 178: onsuccess: #714: 1: Success after binutils/gcc/linux/ [...] discards 9bc8e7a3a92b 177: onsuccess: #712: 1: Success after binutils/gcc/linux/ [...] discards 21dc3d3c224f 176: onsuccess: #711: 1: Success after binutils/gcc/linux/ [...] discards e813917963d6 175: onsuccess: #710: 1: Success after binutils/gcc/linux/ [...] discards 006e8117eab3 174: onsuccess: #709: 1: Success after binutils/gcc/linux/ [...] discards 91fd820044a4 173: onsuccess: #708: 1: Success after binutils/gcc/linux/ [...] discards 8e1016efe922 172: onsuccess: #707: 1: Success after binutils/gcc/linux/ [...] discards 469804a47934 171: onsuccess: #706: 1: Success after binutils/gcc/linux/ [...] discards b36ea5c59894 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/ [...] discards 24d10553aeec 169: onsuccess: #704: 1: Success after binutils/gcc/linux/ [...] discards 7fca25c814ae 168: onsuccess: #703: 1: Success after binutils/gcc/linux/ [...] discards 455b4e21b46b 167: onsuccess: #702: 1: Success after binutils/gcc/linux/ [...] discards d517d077f098 166: onsuccess: #701: 1: Success after binutils/gcc/linux/ [...] discards 66de428ae787 165: onsuccess: #700: 1: Success after binutils/gcc/linux/ [...] discards f7d329932637 164: onsuccess: #699: 1: Success after binutils/gcc/linux/ [...] discards b974d32a0046 163: onsuccess: #698: 1: Success after binutils/gcc/linux/ [...] discards 8165b4e5aa62 162: onsuccess: #697: 1: Success after binutils/gcc/linux/ [...] discards 0828ddf68fd4 161: onsuccess: #696: 1: Success after binutils/gcc/linux/ [...] discards 9cb90b441863 160: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] discards 521c2f4a4008 159: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] discards c0d694bee4c7 158: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] discards 9c7c0356826b 157: onsuccess: #692: 1: Success after binutils/gcc/linux/ [...] discards 4ef3024f809b 156: onsuccess: #691: 1: Success after binutils/gcc/linux/ [...] discards ddc3c25c05a3 155: onsuccess: #690: 1: Success after binutils/gcc/linux/ [...] discards 144404859f25 154: onsuccess: #689: 1: Success after binutils/gcc/linux/ [...] discards ed42158ab63c 153: onsuccess: #688: 1: Success after binutils/gcc/linux/ [...] discards 702b929a8e54 152: onsuccess: #687: 1: Success after binutils/gcc/linux/ [...] discards b84a0a39979b 151: onsuccess: #686: 1: Success after binutils/gcc/linux/ [...] discards a741d418782e 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/ [...] discards e54d705f3bd5 149: onsuccess: #684: 1: Success after linux: 10 commits discards 9bc85fe0ad79 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 0114b8f100a6 147: onsuccess: #681: 1: Success after gcc: 6 commits discards c1a684330d71 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 57bdcf06e9b5 145: onsuccess: #678: 1: Success after binutils/gcc/linux/ [...] discards aaa47151e280 144: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] discards 03bd401b5c57 143: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] discards abbb5b2aa1f9 142: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] discards 6be71bef8335 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 1 [...] discards af3bec595c7f 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 2 [...] discards 013f308b01a4 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 2 [...] discards d0bfce806364 138: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] discards 325e82948eea 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 4 [...] discards b2ae219c6b53 136: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] discards 74921897bd04 135: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] discards 348e9ae3dd65 134: onsuccess: #667: 1: Success after binutils/gcc/linux/ [...] discards fe765c7ef6cb 133: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] discards 5b568092ff27 132: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] discards c97f30624f2e 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] discards 2f5d75b7f330 130: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] discards 1706cdd3ee2f 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] discards 9298017b822b 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] discards b2551d0e29ca 127: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] new 35c4f87f08e1 127: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] new 5cd0b3d954af 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new 9d3dfab39fc7 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new 2854a5b47fa3 130: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] new cc47ff57d7cd 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] new 689c28f217b2 132: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] new dffc92e3742e 133: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] new b5857c44b63b 134: onsuccess: #667: 1: Success after binutils/gcc/linux/ [...] new 1fa9517392d9 135: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] new ed50c619c728 136: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] new 59581f825063 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 4 [...] new 790ba1f66a49 138: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] new ec1856e1cb5e 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 2 [...] new 5e777a8f04d1 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 2 [...] new 1077a84494b8 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 1 [...] new 46146bd99358 142: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] new e89b63bf92d4 143: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] new 83da85c8ca87 144: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] new 5a727817fb4a 145: onsuccess: #678: 1: Success after binutils/gcc/linux/ [...] new c7dbf5f344e7 146: onsuccess: #680: 1: Success after binutils: 20 commits new 52ff11b1c6f8 147: onsuccess: #681: 1: Success after gcc: 6 commits new 80de2316a9ee 148: onsuccess: #683: 1: Success after glibc: 9 commits new f108bda37dd8 149: onsuccess: #684: 1: Success after linux: 10 commits new a6d73c187d74 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/ [...] new 5e2fc803e7c2 151: onsuccess: #686: 1: Success after binutils/gcc/linux/ [...] new dab667874fef 152: onsuccess: #687: 1: Success after binutils/gcc/linux/ [...] new 8cfa0a7a3dcf 153: onsuccess: #688: 1: Success after binutils/gcc/linux/ [...] new c555f331c482 154: onsuccess: #689: 1: Success after binutils/gcc/linux/ [...] new 27a979e37bb7 155: onsuccess: #690: 1: Success after binutils/gcc/linux/ [...] new 75b181b2845e 156: onsuccess: #691: 1: Success after binutils/gcc/linux/ [...] new ec05e3fcea36 157: onsuccess: #692: 1: Success after binutils/gcc/linux/ [...] new 5c8cc60279c9 158: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] new 8dd67d3436fa 159: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] new 8649ef5391df 160: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] new c4165a5df61a 161: onsuccess: #696: 1: Success after binutils/gcc/linux/ [...] new f91a0ae498d3 162: onsuccess: #697: 1: Success after binutils/gcc/linux/ [...] new e1490f6f2bdd 163: onsuccess: #698: 1: Success after binutils/gcc/linux/ [...] new cb74982baf15 164: onsuccess: #699: 1: Success after binutils/gcc/linux/ [...] new 280517072a81 165: onsuccess: #700: 1: Success after binutils/gcc/linux/ [...] new a5490fa8f20d 166: onsuccess: #701: 1: Success after binutils/gcc/linux/ [...] new 57b5143a2818 167: onsuccess: #702: 1: Success after binutils/gcc/linux/ [...] new 6d553a239c5c 168: onsuccess: #703: 1: Success after binutils/gcc/linux/ [...] new 1b8337d77bb2 169: onsuccess: #704: 1: Success after binutils/gcc/linux/ [...] new 4ae57ee91f52 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/ [...] new 07d8ca2dde96 171: onsuccess: #706: 1: Success after binutils/gcc/linux/ [...] new 7eccc0c8db24 172: onsuccess: #707: 1: Success after binutils/gcc/linux/ [...] new f7866ccb9e54 173: onsuccess: #708: 1: Success after binutils/gcc/linux/ [...] new f94e1d68dd2d 174: onsuccess: #709: 1: Success after binutils/gcc/linux/ [...] new 7bea3839f387 175: onsuccess: #710: 1: Success after binutils/gcc/linux/ [...] new 5167ff319e78 176: onsuccess: #711: 1: Success after binutils/gcc/linux/ [...] new 335374cd94b6 177: onsuccess: #712: 1: Success after binutils/gcc/linux/ [...] new d07fca7149a1 178: onsuccess: #714: 1: Success after binutils/gcc/linux/ [...] new 24b150b2a5fe 179: onsuccess: #715: 1: Success after binutils/gcc/linux/ [...] new 7faec62ead26 180: onsuccess: #716: 1: Success after binutils/gcc/linux/ [...] new b07d06e62d2f 181: onsuccess: #717: 1: Success after binutils/gcc/linux/ [...] new 28bdf678160e 182: onsuccess: #718: 1: Success after binutils/gcc/linux/ [...] new 547bd354453e 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 2 [...] new fad378af9df1 184: onsuccess: #720: 1: Success after binutils/gcc/linux/ [...] new 52eae46336a1 185: onsuccess: #721: 1: Success after binutils/gcc/linux/ [...] new 1ea629ca6d29 186: onsuccess: #722: 1: Success after binutils/gcc/linux/ [...] new aaf251232397 187: onsuccess: #723: 1: Success after binutils/gcc/linux/ [...] new f4c9971cb576 188: onsuccess: #724: 1: Success after binutils/gcc/linux/ [...] new 0600e5be600c 189: onsuccess: #725: 1: Success after binutils/gcc/linux/ [...] new c394e3bfb62b 190: onsuccess: #726: 1: Success after binutils/gcc/linux/ [...] new 663c8cbca821 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new f6417a8b0135 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new 8afba0af14e0 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new cfdb55372c1b 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new 879f3e162567 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 6a67e5d7348d 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 6f46f329ae4f 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 0af1a99f6352 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 1a4913ab3910 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 549a1095c64c 200: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new ba2a9a9d97d7 201: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new daa6c37b4353 202: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new e4f2ca958626 203: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 971d855cfd07 204: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 009732f7e383 205: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new cd73ca51f2b4 206: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 28533e842f30 207: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 7bf34a79f9b1 208: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 762d86c5a82e 209: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 476607b3d615 210: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new a9b70b3c0cd3 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 3a88d06044c6 212: force: #24: 1: Success after binutils: 2 commits new 01143c900a51 213: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] new a34ca75ac229 214: onsuccess: #26: 1: Success after binutils: 12 commits new 0dfec8bc5903 215: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 92ac6507ce77 216: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 157498951aac 217: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new c006043b0ce6 218: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 5625bd16f505 219: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new 3d0a625571a3 220: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 739079da9ec3 221: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new 051bedb094dc 222: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new 9b10e501c6af 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new fc11a232d4b1 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new f9f4df06261c 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 96de7517a9fc 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new 5b2ff4abe190 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] new c3479ea69927 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (8416d5d20944) \ 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 2060 -> 2036 bytes 02-prepare_abe/console.log.xz | Bin 2520 -> 2536 bytes 03-build_abe-binutils/console.log.xz | Bin 35072 -> 34864 bytes 04-build_abe-gcc/console.log.xz | Bin 203704 -> 203492 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8644 -> 8168 bytes 07-build_abe-glibc/console.log.xz | Bin 240648 -> 241320 bytes 08-build_abe-gdb/console.log.xz | Bin 34784 -> 34508 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3788 -> 3780 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2104 -> 2100 bytes 11-check_regression/console.log.xz | Bin 4512 -> 4952 bytes 11-check_regression/results.compare | 10 +++--- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 44 +++++++++++++------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 48 +++++++++++++++++++---------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 +++++++++---------- manifest.sh | 36 +++++++++++----------- sumfiles/binutils.log.xz | Bin 62816 -> 62980 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150656 -> 150792 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122644 -> 122660 bytes sumfiles/ld.sum | 4 +-- 30 files changed, 107 insertions(+), 93 deletions(-) -- 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_size-cpu2017rate/llvm-arm-master-Oz updated (ebb60bd12f0e -> 081055bc9138)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_size-cpu2017rate/llvm-arm-master-Oz in repository toolchain/ci/base-artifacts. from ebb60bd12f0e 5: onsuccess: #6: 1: [TCWG CI] No change after llvm: 364 commits new 081055bc9138 6: onsuccess: #8: 1: [TCWG CI] Success after llvm: 890 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1880 -> 1912 bytes 02-build_bmk_llvm/console.log.xz | Bin 229804 -> 230804 bytes 03-benchmark/benchmark-build.log | 100 +- 03-benchmark/benchmark.log | 98 +- 03-benchmark/console.log.xz | Bin 3884 -> 3868 bytes .../compare-results-vs-first-internal.csv | 115 +- .../compare-results-vs-prev-internal.csv | 119 +- 04-check_regression/console.log.xz | Bin 10056 -> 10856 bytes .../csv-results-vs-first-1/md5sum.csv | 1236 +++++------ .../csv-results-vs-first-1/perf.csv | 1700 +++++++-------- .../csv-results-vs-first-1/results.csv | 2169 ++++++++++---------- .../csv-results-vs-first-1/size.csv | 174 +- .../csv-results-vs-prev-0/md5sum.csv | 1054 +++++----- 04-check_regression/csv-results-vs-prev-0/perf.csv | 1660 ++++++++------- .../csv-results-vs-prev-0/results.csv | 1934 +++++++++-------- 04-check_regression/csv-results-vs-prev-0/size.csv | 4 +- .../csv-results-vs-prev-1/md5sum.csv | 1236 +++++------ 04-check_regression/csv-results-vs-prev-1/perf.csv | 1700 +++++++-------- .../csv-results-vs-prev-1/results.csv | 2169 ++++++++++---------- 04-check_regression/csv-results-vs-prev-1/size.csv | 174 +- 04-check_regression/jira-body.txt | 1 - .../output-bmk-results/symbol.improvement | 2 + .../output-bmk-results/symbol.improvement.diff | 1 + .../output-bmk-results/symbol.regression | 3 +- .../output-bmk-results/symbol.regression.diff | 2 +- 04-check_regression/results-vs-first-brief.csv | 40 +- 04-check_regression/results-vs-first-full.csv | 1742 ++++++++-------- 04-check_regression/results-vs-first-internal.csv | 117 +- 04-check_regression/results-vs-first.csv | 117 +- 04-check_regression/results-vs-first.log | 732 +++---- 04-check_regression/results-vs-prev-brief.csv | 40 +- 04-check_regression/results-vs-prev-compare.csv | 13 +- 04-check_regression/results-vs-prev-full.csv | 1830 ++++++++--------- 04-check_regression/results-vs-prev-internal.csv | 119 +- 04-check_regression/results-vs-prev.csv | 119 +- 04-check_regression/results-vs-prev.log | 778 +++---- dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 10 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 10 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 10 +- .../squad-vs-first/505.mcf_r/results-metrics.json | 2 +- .../508.namd_r/results-metadata.json | 10 +- .../squad-vs-first/508.namd_r/results-metrics.json | 2 +- .../511.povray_r/results-metadata.json | 10 +- .../511.povray_r/results-metrics.json | 2 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 10 +- .../520.omnetpp_r/results-metadata.json | 10 +- .../523.xalancbmk_r/results-metadata.json | 10 +- .../525.x264_r/results-metadata.json | 10 +- .../526.blender_r/results-metadata.json | 10 +- .../531.deepsjeng_r/results-metadata.json | 10 +- .../531.deepsjeng_r/results-metrics.json | 2 +- .../538.imagick_r/results-metadata.json | 10 +- .../541.leela_r/results-metadata.json | 10 +- .../squad-vs-first/544.nab_r/results-metadata.json | 10 +- .../squad-vs-first/557.xz_r/results-metadata.json | 10 +- .../squad-vs-first/557.xz_r/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 66 +- git/llvm_rev | 2 +- mail/changes-list-long.txt | 8 + mail/changes-list-short.txt | 1 + mail/jira-body.txt | 7 - manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 19 - mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 14 +- results_id | 2 +- 69 files changed, 10775 insertions(+), 10816 deletions(-) delete mode 100644 04-check_regression/jira-body.txt create mode 100644 04-check_regression/output-bmk-results/symbol.improvement create mode 100644 04-check_regression/output-bmk-results/symbol.improvement.diff create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt delete mode 100644 mail/jira-body.txt copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create 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 (932432bfc0f2 -> 5faa8766c041)

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 932432bfc0f2 481: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] discards 01202a3940e7 480: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards 719a2df1ef8e 479: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards c00ea9ee494b 478: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards 409faad8ceea 477: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards 10b7988f0892 476: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] discards 5e8337ababbe 475: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards e61dab6a415e 474: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards 646a0e2a8bd8 473: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards 28f89eaadd55 472: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards 06e363910074 471: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 98cb1e202213 470: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards a7004cb09cbd 469: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards 56d7f653c902 468: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 213e67930709 467: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards c9d116425d93 466: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards cc317358f9f5 465: onsuccess: #26: 1: Success after binutils/gcc/linux/g [...] discards 628822c93b12 464: onsuccess: #25: 1: Success after binutils/gcc/linux/g [...] discards 1ee40a46bca0 463: onsuccess: #24: 1: Success after binutils/gcc/linux/g [...] discards c461c72ee9f5 462: onsuccess: #23: 1: Success after binutils/gcc/linux/g [...] discards afdc342a5249 461: onsuccess: #22: 1: Success after binutils/gcc/linux/g [...] discards d6a739d68a7c 460: onsuccess: #21: 1: Success after binutils/gcc/linux/g [...] discards d91183dde9b4 459: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards c03ce0a28f31 458: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 377b195d78a2 457: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 17d9e7d62b07 456: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards e583cb194f2f 455: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 37620a04f41f 454: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 5cacef9db903 453: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards a79cbbc83270 452: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards d0745489a686 451: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards 1913654b11ca 450: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards d5ac5c755dce 449: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 2210c8b06450 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards d80b4bb3b400 447: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 81f9e8515164 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards 18f7d1798591 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] discards 0c070cb004ae 444: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 23fa7615066b 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu [...] discards 9751ed7258e5 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gd [...] discards 69a09875a4bd 441: onsuccess: #2266: 1: Success after binutils/gcc/linux [...] discards 612c07a60e18 440: onsuccess: #2265: 1: Success after binutils/gcc/linux [...] discards f212a451d558 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: [...] discards 8cbc0bd4e5cd 438: onsuccess: #2263: 1: Success after binutils/gcc/linux [...] discards b0b5766aa551 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc [...] discards acc0a6594c5a 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards 85b13beb8992 435: onsuccess: #2259: 1: Success after binutils/gcc/linux [...] discards 6ddda43ad24d 434: onsuccess: #2258: 1: Success after binutils/gcc/linux [...] discards 3e217b74c734 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/q [...] discards f9185acb8224 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards 6e9fe938d609 431: onsuccess: #2255: 1: Success after binutils/gcc/linux [...] discards f679104d5e85 430: onsuccess: #2254: 1: Success after binutils/gcc/linux [...] discards e2198c3e08d7 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc [...] discards 6e55db1b6775 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards 4c44a5c3638b 427: onsuccess: #2251: 1: Success after binutils/gcc/linux [...] discards 1dd924eeb537 426: onsuccess: #2250: 1: Success after binutils/linux/gdb [...] discards eac4ee3e99d6 425: onsuccess: #2249: 1: Success after binutils/gcc/linux [...] discards f6b8762becfa 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 4948c21a7904 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards bfde0f860385 422: onsuccess: #2246: 1: Success after binutils/gcc/linux [...] discards 4dc30b66195c 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc [...] discards f0e245e7f556 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards e99f335e1ed8 419: onsuccess: #2243: 1: Success after binutils/gcc/linux [...] discards 40503fc33d2b 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: [...] discards b1067bd68f47 417: onsuccess: #2238: 1: Success after binutils/gcc/linux [...] discards 6756231ac8ca 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc [...] discards 04112f2975ec 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: [...] discards a6c96c6a113c 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: [...] discards be1df7ad952e 413: onsuccess: #2234: 1: Success after binutils/gcc/linux [...] discards 86e1d6dd51cd 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc [...] discards bb3980f5297c 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards a6ddae22c7cd 410: onsuccess: #2231: 1: Success after binutils/gcc/linux [...] discards 34a6ca515797 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc [...] discards bae352086dbb 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: [...] discards 6f4928165ddd 407: onsuccess: #2228: 1: Success after binutils/gcc/linux [...] discards 26918f734516 406: onsuccess: #2227: 1: Success after binutils/linux/gli [...] discards 0f640e105403 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 5b7f49f0d5c6 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: [...] discards 208b5ff9705f 403: onsuccess: #2224: 1: Success after binutils/gcc/linux [...] discards b8f3342b6226 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: [...] discards b703a992ac61 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: [...] discards df62a767d163 400: onsuccess: #2221: 1: Success after binutils/gcc/linux [...] discards a93e91f5fef1 399: onsuccess: #2220: 1: Success after binutils/gcc/linux [...] discards a6359e5f5ce1 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/q [...] discards 7e96f5c0b676 397: onsuccess: #2218: 1: Success after binutils/gcc/linux [...] discards 66b84560cc2a 396: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] discards cbe16513ebc9 395: onsuccess: #2216: 1: Success after binutils/gcc/linux [...] discards 648a4ab24011 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: [...] discards b9507d9463f4 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: [...] discards 30886599bde4 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc [...] discards aca77307d18f 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/q [...] discards 739c978751ae 390: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] discards 1565253a38de 389: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] discards 216476e27e56 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc [...] discards b1cacd9ce72b 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 97e766f4ee1b 386: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] discards 502187d4c797 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc [...] discards 18ba0c0d3710 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 25832bf35c6f 383: onsuccess: #2204: 1: Success after binutils/gcc/linux [...] discards 718a47492e3d 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 18e6e5419da7 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17 [...] new afa293404ec3 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17 [...] new 66047ba7d2d7 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 45b16deaa51e 383: onsuccess: #2204: 1: Success after binutils/gcc/linux [...] new bdd0fecbd43a 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 0ff27583b915 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc [...] new 627131998a4f 386: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] new 2cfdfc39f21e 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 55ab9c9e849d 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc [...] new b8a3c472ce17 389: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] new 0956830f2ef5 390: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] new d0ad5816f346 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/q [...] new 451f095f3794 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc [...] new 86e90c6e6d70 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: [...] new 08406a26f943 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: [...] new 754215d25e32 395: onsuccess: #2216: 1: Success after binutils/gcc/linux [...] new 0be1cdd63f46 396: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] new d20846613baf 397: onsuccess: #2218: 1: Success after binutils/gcc/linux [...] new 6f249f28fcfd 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/q [...] new 94fd5c8e0b9e 399: onsuccess: #2220: 1: Success after binutils/gcc/linux [...] new 78323d211c67 400: onsuccess: #2221: 1: Success after binutils/gcc/linux [...] new bab1aa27842a 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: [...] new f181ae1f91b7 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: [...] new b3ea9bd82f85 403: onsuccess: #2224: 1: Success after binutils/gcc/linux [...] new e847e00b6332 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: [...] new b7e2f786aca6 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 73e59bfe2e00 406: onsuccess: #2227: 1: Success after binutils/linux/gli [...] new 715f6aa16281 407: onsuccess: #2228: 1: Success after binutils/gcc/linux [...] new 144f0dab2d7d 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: [...] new d7e70d27133f 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc [...] new f94cd3b3a85b 410: onsuccess: #2231: 1: Success after binutils/gcc/linux [...] new 41b00ccf9ce0 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 069b43fee469 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc [...] new b3481552e52a 413: onsuccess: #2234: 1: Success after binutils/gcc/linux [...] new d9ebba7714bc 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: [...] new 29fe16792e16 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: [...] new 26a9ba6984ee 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc [...] new 47d725572b91 417: onsuccess: #2238: 1: Success after binutils/gcc/linux [...] new 99fb58960d66 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: [...] new 5deb57b5df78 419: onsuccess: #2243: 1: Success after binutils/gcc/linux [...] new 23575c09bf60 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 995e94bcc9c8 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc [...] new efa84e12a900 422: onsuccess: #2246: 1: Success after binutils/gcc/linux [...] new abe6438b3ec0 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 9ea933c25a8b 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 478e9b7ca719 425: onsuccess: #2249: 1: Success after binutils/gcc/linux [...] new 1208e3e18484 426: onsuccess: #2250: 1: Success after binutils/linux/gdb [...] new 42a44f753545 427: onsuccess: #2251: 1: Success after binutils/gcc/linux [...] new 2f2956d82807 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 0d2459ff68b1 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc [...] new fa19823b51db 430: onsuccess: #2254: 1: Success after binutils/gcc/linux [...] new a1f153dbc240 431: onsuccess: #2255: 1: Success after binutils/gcc/linux [...] new 5a899e3d90ad 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new c7dbe8b4cd01 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/q [...] new 5a751034edf0 434: onsuccess: #2258: 1: Success after binutils/gcc/linux [...] new 0d5e9bf2df34 435: onsuccess: #2259: 1: Success after binutils/gcc/linux [...] new 3063bf41314c 436: onsuccess: #2260: 1: Success after gcc: 7 commits new b288bb2878ad 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc [...] new a91a9e5b3391 438: onsuccess: #2263: 1: Success after binutils/gcc/linux [...] new 4fd0a2f1f4d9 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: [...] new ca11e6d96f9d 440: onsuccess: #2265: 1: Success after binutils/gcc/linux [...] new b268dfbfdb3f 441: onsuccess: #2266: 1: Success after binutils/gcc/linux [...] new d08c9eca6983 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gd [...] new b28cdfd68e07 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu [...] new 9d6defdabed1 444: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 2233c6056edc 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] new 544266aed89d 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new 6d89edea5190 447: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 542fad9f3d11 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 10f799293320 449: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new a07e26863aaa 450: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 5fcd9501d2b8 451: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 832e37775d81 452: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 3ffbc9f46ff0 453: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new f0bcfad58b0b 454: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new 606109ca357e 455: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 755fdc8fd1c9 456: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 569bc8114fb7 457: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 01c50914c1aa 458: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new c0e34facb2d8 459: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new c45e4a955e45 460: onsuccess: #21: 1: Success after binutils/gcc/linux/g [...] new b8192e8e7d16 461: onsuccess: #22: 1: Success after binutils/gcc/linux/g [...] new ede85e15d7ea 462: onsuccess: #23: 1: Success after binutils/gcc/linux/g [...] new 058a438273a5 463: onsuccess: #24: 1: Success after binutils/gcc/linux/g [...] new 8fed4434fc5a 464: onsuccess: #25: 1: Success after binutils/gcc/linux/g [...] new 478e66ac4029 465: onsuccess: #26: 1: Success after binutils/gcc/linux/g [...] new 8f2f89b972c9 466: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new e8c8e0362b24 467: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 90f7348611af 468: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new aef5caff1457 469: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 3cca4515a866 470: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new 715d302b2419 471: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new f3d849f341a2 472: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new d9c08946aa29 473: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 5996b6ab1e75 474: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new 50afbb90f111 475: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new 1350b8c7d8d0 476: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] new 99047e1b5d43 477: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new eda59dafd103 478: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new b7d5ac7bb717 479: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 2274e7909982 480: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new 2c3c478dc6b5 481: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] new 5faa8766c041 482: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (932432bfc0f2) \ 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 2096 -> 2080 bytes 02-prepare_abe/console.log.xz | Bin 2528 -> 2524 bytes 03-build_abe-binutils/console.log.xz | Bin 26804 -> 26636 bytes 04-build_abe-stage1/console.log.xz | Bin 88532 -> 88468 bytes 06-build_abe-linux/console.log.xz | Bin 8644 -> 8208 bytes 07-build_abe-glibc/console.log.xz | Bin 233368 -> 232368 bytes 08-build_abe-stage2/console.log.xz | Bin 224812 -> 223636 bytes 09-build_abe-gdb/console.log.xz | Bin 34408 -> 34132 bytes 10-build_abe-qemu/console.log.xz | Bin 32140 -> 31260 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3800 bytes 12-build_abe-check_gcc/console.log.xz | Bin 5992 -> 6440 bytes 13-check_regression/console.log.xz | Bin 5776 -> 5656 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/results.compare | 35 +- 13-check_regression/results.compare2 | 88 +- 13-check_regression/results.regressions | 40 - 14-update_baseline/console.log | 52 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 48 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 +- manifest.sh | 42 +- results | 40 - sumfiles/g++.log.sep.xz | Bin 133092 -> 142600 bytes sumfiles/g++.log.xz | Bin 2680352 -> 2683312 bytes sumfiles/g++.sum | 2 +- sumfiles/g++.sum.sep | 10837 ++---------------------- sumfiles/gcc.log.sep.xz | Bin 133460 -> 119612 bytes sumfiles/gcc.log.xz | Bin 2208316 -> 2210100 bytes sumfiles/gcc.sum | 2 +- sumfiles/gcc.sum.sep | 13394 +++++++++++++++--------------- sumfiles/gfortran.log.sep.xz | Bin 53016 -> 36784 bytes sumfiles/gfortran.log.xz | Bin 896432 -> 902176 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 5402 +++++------- sumfiles/libatomic.log.xz | Bin 2280 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217312 -> 217152 bytes sumfiles/libgomp.sum | 8 +- sumfiles/libitm.log.xz | Bin 2692 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 16168 -> 13084 bytes sumfiles/libstdc++.log.xz | Bin 450904 -> 447456 bytes sumfiles/libstdc++.sum | 10 +- sumfiles/libstdc++.sum.sep | 551 +- 51 files changed, 9546 insertions(+), 21070 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/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_bmk-code_size-spec2k6/gnu-arm-master-Os_LTO updated (f5c638fca480 -> 19c16a289832)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/gnu-arm-master-Os_LTO in repository toolchain/ci/base-artifacts. from f5c638fca480 59: onsuccess: #16: 1: [TCWG CI] No change after gcc: 74 commits new 19c16a289832 60: onsuccess: #18: 1: [TCWG CI] Success after binutils/gc [...] 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 2052 -> 2200 bytes 02-prepare_abe/console.log.xz | Bin 2548 -> 2540 bytes 03-build_abe-binutils/console.log.xz | Bin 27464 -> 27596 bytes 04-build_abe-stage1/console.log.xz | Bin 90124 -> 89816 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-linux/console.log.xz | Bin 7592 -> 7720 bytes 07-build_abe-glibc/console.log.xz | Bin 234708 -> 236176 bytes 08-build_abe-stage2/console.log.xz | Bin 210712 -> 215880 bytes 09-benchmark/benchmark-build.log | 104 +- 09-benchmark/benchmark.log | 102 +- 09-benchmark/console.log.xz | Bin 4152 -> 4056 bytes 10-check_regression/bmk-specific-variability.csv | 1 + .../compare-results-vs-first-internal.csv | 79 +- .../compare-results-vs-prev-internal.csv | 79 +- 10-check_regression/console.log.xz | Bin 8756 -> 11108 bytes .../csv-results-vs-first-1/perf.csv | 157 +- .../csv-results-vs-first-1/results.csv | 30961 +- .../csv-results-vs-first-1/size.csv | 30913 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 158 +- .../csv-results-vs-prev-0/results.csv | 892995 +++++++++--------- 10-check_regression/csv-results-vs-prev-0/size.csv | 892974 ++++++++--------- 10-check_regression/csv-results-vs-prev-1/perf.csv | 157 +- .../csv-results-vs-prev-1/results.csv | 30961 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 30913 +- 10-check_regression/jira-body.txt | 1 - .../output-bmk-results/exe.improvement | 1 + .../output-bmk-results/exe.improvement.diff | 1 + 10-check_regression/results-vs-first-brief.csv | 69 +- 10-check_regression/results-vs-first-full.csv | 179 +- 10-check_regression/results-vs-first-internal.csv | 82 +- 10-check_regression/results-vs-first.csv | 82 +- 10-check_regression/results-vs-first.log | 1494 +- 10-check_regression/results-vs-prev-brief.csv | 69 +- 10-check_regression/results-vs-prev-compare.csv | 4 + 10-check_regression/results-vs-prev-full.csv | 181 +- 10-check_regression/results-vs-prev-internal.csv | 82 +- 10-check_regression/results-vs-prev.csv | 82 +- 10-check_regression/results-vs-prev.log | 1542 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 16 +- .../squad-vs-first/401.bzip2/results-metadata.json | 16 +- .../squad-vs-first/403.gcc/results-metadata.json | 16 +- .../410.bwaves/results-metadata.json | 16 +- .../416.gamess/results-metadata.json | 16 +- .../squad-vs-first/429.mcf/results-metadata.json | 16 +- .../squad-vs-first/433.milc/results-metadata.json | 16 +- .../434.zeusmp/results-metadata.json | 16 +- .../435.gromacs/results-metadata.json | 16 +- .../435.gromacs/results-metrics.json | 2 +- .../436.cactusADM/results-metadata.json | 16 +- .../437.leslie3d/results-metadata.json | 16 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 16 +- .../squad-vs-first/445.gobmk/results-metadata.json | 16 +- .../447.dealII/results-metadata.json | 16 +- .../450.soplex/results-metadata.json | 16 +- .../453.povray/results-metadata.json | 16 +- .../454.calculix/results-metadata.json | 16 +- .../squad-vs-first/456.hmmer/results-metadata.json | 16 +- .../squad-vs-first/458.sjeng/results-metadata.json | 16 +- .../459.GemsFDTD/results-metadata.json | 16 +- .../462.libquantum/results-metadata.json | 16 +- .../464.h264ref/results-metadata.json | 16 +- .../squad-vs-first/465.tonto/results-metadata.json | 16 +- .../squad-vs-first/470.lbm/results-metadata.json | 16 +- .../471.omnetpp/results-metadata.json | 16 +- .../squad-vs-first/473.astar/results-metadata.json | 16 +- .../squad-vs-first/473.astar/results-metrics.json | 2 +- .../squad-vs-first/481.wrf/results-metadata.json | 16 +- .../482.sphinx3/results-metadata.json | 16 +- .../squad-vs-first/Mean/results-metadata.json | 16 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 343 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 26 + mail/changes-list-short.txt | 1 + mail/jira-body.txt | 7 - manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 19 - mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 35 +- results_id | 2 +- 85 files changed, 958418 insertions(+), 956920 deletions(-) create mode 100644 10-check_regression/bmk-specific-variability.csv delete mode 100644 10-check_regression/jira-body.txt create mode 100644 10-check_regression/output-bmk-results/exe.improvement create mode 100644 10-check_regression/output-bmk-results/exe.improvement.diff create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt delete mode 100644 mail/jira-body.txt copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create 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-arm-mainline-allyesconfig updated (8ae29da83af7 -> 1a64f3a84f5e)

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-allyesconfig in repository toolchain/ci/base-artifacts. from 8ae29da83af7 61: onsuccess: #15: 21198: Success after binutils/gcc/linu [...] new 1a64f3a84f5e 62: onsuccess: #16: 21198: [TCWG CI] Success after binutil [...] 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 -> 2004 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2544 bytes 03-build_abe-binutils/console.log.xz | Bin 26904 -> 26928 bytes 04-build_abe-stage1/console.log.xz | Bin 88800 -> 88680 bytes 05-build_abe-qemu/console.log.xz | Bin 30656 -> 30644 bytes 06-build_linux/console.log.xz | Bin 9144 -> 9136 bytes 08-check_regression/console.log.xz | Bin 4192 -> 4236 bytes 08-check_regression/mail-body.txt | 23 ----------------------- 08-check_regression/mail-subject.txt | 1 - dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 26 ++++++++++++++++++++++++++ mail/changes-list-short.txt | 1 + manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 23 ----------------------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 32 ++++++++++++++++---------------- 21 files changed, 49 insertions(+), 69 deletions(-) delete mode 100644 08-check_regression/mail-body.txt delete mode 100644 08-check_regression/mail-subject.txt create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create 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 (1280dad8b0f5 -> 350d5ed36b94)

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 1280dad8b0f5 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits discards 1f21e82ec164 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/ [...] discards c0b6a3c5db92 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/ [...] discards 15ad98b97e5d 239: force: #106: 1: [TCWG CI] Success after baseline buil [...] discards d9a3a1613eb5 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branch [...] discards 32dc3ce5e9aa 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits discards 8b472643ce96 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: [...] discards 891e26e1eb68 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/g [...] discards eb475f03ec03 234: force: #94: 1: [TCWG CI] Success after baseline build [...] discards 6eb992959f48 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards 399bfcc9639f 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards bb75227f40e7 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards bb734003ea02 230: onsuccess: #78: 1: Success after gdb: 2 commits discards 2fc4f364a248 229: force: #77: 1: Failure after gdb-13-branchpoint-1594- [...] discards b47c1525b2b6 228: force: #74: 1: Success after gdb: 53 commits discards b1e4d68c22d2 227: onsuccess: #72: 1: Success after binutils/gcc/linux/g [...] discards 3ab7f6009f98 226: force: #70: 1: Success after baseline build: no new commits discards 347c05a160de 225: force: #68: 1: Failure after gdb-13-branchpoint-1540- [...] discards 8481dc218b07 224: force: #65: 1: Success after gdb: 50 commits discards f0ee0afbfb6a 223: force: #63: 1: Failure after gdb-13-branchpoint-1489- [...] discards a6a890df7546 222: force: #60: 1: Success after gdb: 16 commits discards 68deca96dcf6 221: force: #53: 1: Success after gdb-13-branchpoint-1472- [...] discards bda358b9c267 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02d [...] discards 2df93864cdeb 219: force: #50: 1: Failure after linux: 2520 commits discards 79450f423f80 218: force: #48: 1: Success after gdb-13-branchpoint-1471- [...] discards 296407dbb7c7 217: force: #45: 1: Success after linux: 1 commits discards 3549cc53f5d0 216: force: #43: : Failure after baseline build: no new commits discards afd894fbc026 215: force: #41: 1: Failure after gdb-13-branchpoint-1470- [...] discards 78b75526eb3a 214: force: #39: 1: Failure after gdb-13-branchpoint-1470- [...] discards 42eb435ad131 213: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 4e41956df92a 212: force: #27: : Failure after baseline build: no new commits discards b51510cb9120 211: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 081705736b6f 210: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 33c6083022b0 209: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 65b52c2075fc 208: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 7981b76d5abf 207: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards c625022c47c9 206: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards bfa26872f9d0 205: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards a66734b5c7f3 204: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards 5419419fff2b 203: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 474eab177371 202: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 68a882c19b77 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 1c070d34c8f7 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 4959762fbc4a 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards d3bf6b9dde6e 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards 4d998bba4e5f 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 6a02496c692a 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards e4dccbb18bcd 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards ff97de47d642 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards 3366c3580327 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 0693265ef463 192: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] discards 3e598cf0e6de 191: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] discards 23ce7b956b8b 190: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] discards 52368f580a8c 189: onsuccess: #683: 1: Success after binutils/gcc/linux/ [...] discards 6629bc86a068 188: onsuccess: #682: 1: Success after binutils/gcc/linux/ [...] discards 03225de8e35c 187: onsuccess: #681: 1: Success after binutils/gcc/linux/ [...] discards 94d6bff4c36f 186: onsuccess: #680: 1: Success after binutils/gcc/linux/ [...] discards 59f51417ec1b 185: onsuccess: #679: 1: Success after binutils/gcc/linux/ [...] discards 6e5c5ced3ccd 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/ [...] discards c81ab7b2bfb4 183: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] discards f17e6fbcb22a 182: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] discards 73fe50a22d52 181: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] discards e9df17e45040 180: onsuccess: #674: 1: Success after binutils/gcc/linux/ [...] discards decc90f652f4 179: onsuccess: #673: 1: Success after binutils/gcc/linux/ [...] discards d2c579eb9478 178: onsuccess: #672: 1: Success after binutils/gcc/linux/ [...] discards 6af8eb12434d 177: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] discards 22fc13cbcd9b 176: onsuccess: #670: 1: Success after binutils/gcc/linux/ [...] discards fd93f404413c 175: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] discards 02d7733836be 174: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] discards 2e79bd935211 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 1 [...] discards 6633c7b2f3cb 172: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] discards 8a03b30a91d3 171: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] discards 2033a2c22071 170: onsuccess: #664: 1: Success after binutils/gcc/linux/ [...] discards cde3356298ac 169: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] discards 6e0d12498903 168: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] discards fddd08269c8a 167: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] discards 2bcf767f34e0 166: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] discards 6ab68ea966dc 165: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] discards f4e66f5a1c5f 164: onsuccess: #658: 1: Success after binutils/gcc/linux/ [...] discards 0cbbad04c3ec 163: onsuccess: #657: 1: Success after binutils/gcc/linux/ [...] discards be3e33879036 162: onsuccess: #656: 1: Success after binutils/gcc/linux/ [...] discards 5a28328d2ce3 161: onsuccess: #655: 1: Success after binutils/gcc/linux/ [...] discards 23789f793eef 160: onsuccess: #654: 1: Success after binutils/gcc/linux/ [...] discards 9ce0744ece69 159: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] discards 0cff5be1088a 158: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] discards 966077bd9fc4 157: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] discards 27eb61fbb81f 156: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] discards ac10d04e73c1 155: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] discards 034373e80212 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/ [...] discards 2683d254c76a 153: onsuccess: #647: 1: Success after binutils/gcc/linux/ [...] discards 7e781695e32d 152: onsuccess: #645: 1: Success after binutils/gcc/linux/ [...] discards c34780c10be8 151: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] discards c2dddb7a09ca 150: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] discards dd823e63328c 149: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] discards 035fd196566a 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 [...] discards 7209c32b8ce5 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 1 [...] discards ceb0f499e142 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 3 [...] discards b214b58dc613 145: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] discards 03ee6cadccd0 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 4 [...] discards 6101b8892181 143: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] discards f9dc01e562ed 142: onsuccess: #634: 1: Success after binutils/gcc/linux/ [...] new 68673f5f66c0 142: onsuccess: #634: 1: Success after binutils/gcc/linux/ [...] new 1a1a763979ca 143: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] new 1c7ae3c65ca6 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 4 [...] new e944abbcaa94 145: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] new c9413e4c1ad1 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 3 [...] new 54c5bc4ce803 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 1 [...] new 0a3a53164307 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 [...] new 5c7d8aeba162 149: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] new 1354f980f69e 150: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] new d6de9d536b1f 151: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] new 883109912c32 152: onsuccess: #645: 1: Success after binutils/gcc/linux/ [...] new d7138f146639 153: onsuccess: #647: 1: Success after binutils/gcc/linux/ [...] new 75174a8f5778 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/ [...] new ed9f9431ff9b 155: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] new 0c0d6151473c 156: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] new 21a41b9f7d4d 157: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] new c99c50523e16 158: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] new d52411e6b202 159: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] new b4c6ee128c60 160: onsuccess: #654: 1: Success after binutils/gcc/linux/ [...] new 2dfd4035d252 161: onsuccess: #655: 1: Success after binutils/gcc/linux/ [...] new 88ee0cd76724 162: onsuccess: #656: 1: Success after binutils/gcc/linux/ [...] new 4a4ac52745c8 163: onsuccess: #657: 1: Success after binutils/gcc/linux/ [...] new 6cd269ea950f 164: onsuccess: #658: 1: Success after binutils/gcc/linux/ [...] new 76db1a0584df 165: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] new 13f1ec7fcca4 166: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] new 2ecacd9beaba 167: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new 9541a2a6df5d 168: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new ee01939eb40a 169: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] new 05eff82d96b0 170: onsuccess: #664: 1: Success after binutils/gcc/linux/ [...] new e3f7de7551e5 171: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] new 984685fa6ea8 172: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] new e274e5aad057 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 1 [...] new e31b6c1ccb0f 174: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] new 26c092270b89 175: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] new 78dc5bdf80ac 176: onsuccess: #670: 1: Success after binutils/gcc/linux/ [...] new 8a0753e72dad 177: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] new 9d2ea7567bc4 178: onsuccess: #672: 1: Success after binutils/gcc/linux/ [...] new 222efcae78c8 179: onsuccess: #673: 1: Success after binutils/gcc/linux/ [...] new 4ee9b625065f 180: onsuccess: #674: 1: Success after binutils/gcc/linux/ [...] new da80978fd126 181: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] new fe7945ca1d1b 182: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] new 281230787283 183: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] new 21c01828f2e8 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/ [...] new a46d354c2c8d 185: onsuccess: #679: 1: Success after binutils/gcc/linux/ [...] new 2d1ffd769322 186: onsuccess: #680: 1: Success after binutils/gcc/linux/ [...] new bfd9a604a192 187: onsuccess: #681: 1: Success after binutils/gcc/linux/ [...] new 7443df49793f 188: onsuccess: #682: 1: Success after binutils/gcc/linux/ [...] new 6954e11857fe 189: onsuccess: #683: 1: Success after binutils/gcc/linux/ [...] new 952ed9b61986 190: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] new e53d24e12720 191: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] new 00657b41f59a 192: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] new 8497efeb35e3 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 121254983239 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new be7cb960e624 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new c93e09c78722 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new a7f5f360b980 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 55843e279c0d 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new a52b1f83a8b6 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 2a8382567de6 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new f26cc9c136e4 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 4ca2699c7264 202: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new db6d2a820956 203: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 47f7c474794a 204: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 8a687712876f 205: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new bba4cca6678e 206: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new 6aa4dc6134b7 207: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 222c55d485ef 208: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 954f6b069f69 209: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 9b2f3e3fa9e6 210: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new becb70efee1a 211: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new 063369527227 212: force: #27: : Failure after baseline build: no new commits new cb3bae422627 213: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new fcae2a9ae015 214: force: #39: 1: Failure after gdb-13-branchpoint-1470- [...] new fbc4bd4f4d47 215: force: #41: 1: Failure after gdb-13-branchpoint-1470- [...] new 3006a12c3ad2 216: force: #43: : Failure after baseline build: no new commits new a52caa7c3241 217: force: #45: 1: Success after linux: 1 commits new 6d70b2da0e58 218: force: #48: 1: Success after gdb-13-branchpoint-1471- [...] new 3981fe51cdf9 219: force: #50: 1: Failure after linux: 2520 commits new abd558397f72 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02d [...] new 2b2c8dd88237 221: force: #53: 1: Success after gdb-13-branchpoint-1472- [...] new daf6b8713d89 222: force: #60: 1: Success after gdb: 16 commits new 2d476e14701f 223: force: #63: 1: Failure after gdb-13-branchpoint-1489- [...] new 45a22d017d9d 224: force: #65: 1: Success after gdb: 50 commits new b510e12a88a2 225: force: #68: 1: Failure after gdb-13-branchpoint-1540- [...] new e75152999016 226: force: #70: 1: Success after baseline build: no new commits new 01508c3ee686 227: onsuccess: #72: 1: Success after binutils/gcc/linux/g [...] new cc275cb43f2b 228: force: #74: 1: Success after gdb: 53 commits new a45a30aaaeeb 229: force: #77: 1: Failure after gdb-13-branchpoint-1594- [...] new ee4d46dbcc0c 230: onsuccess: #78: 1: Success after gdb: 2 commits new 136f2e8464f1 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new 61fcbdf6aa7b 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchp [...] new eea33ee66d72 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchp [...] new e971bec7af40 234: force: #94: 1: [TCWG CI] Success after baseline build [...] new de500de892c0 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/g [...] new 76abcc47ee9f 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: [...] new da431698c4f5 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits new 9518d8a23819 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branch [...] new 03b589d41044 239: force: #106: 1: [TCWG CI] Success after baseline buil [...] new 2c3a538fcfab 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/ [...] new 9ed005b92190 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/ [...] new 38755fa998e4 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits new 350d5ed36b94 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/ [...] 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 (1280dad8b0f5) \ 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 2008 -> 2044 bytes 02-prepare_abe/console.log.xz | Bin 2492 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 49180 -> 49332 bytes 04-build_abe-gcc/console.log.xz | Bin 238512 -> 234752 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8712 -> 8188 bytes 07-build_abe-glibc/console.log.xz | Bin 233620 -> 232424 bytes 08-build_abe-gdb/console.log.xz | Bin 46396 -> 47016 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3760 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4356 -> 4156 bytes 11-check_regression/console.log.xz | Bin 4420 -> 6168 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 180 ++- 12-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 34 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 22 +- manifest.sh | 34 +- sumfiles/gdb.log.0.xz | Bin 2946564 -> 2929368 bytes sumfiles/gdb.log.1.xz | Bin 138656 -> 138736 bytes sumfiles/gdb.log.2.xz | Bin 11832 -> 16476 bytes sumfiles/gdb.log.3.xz | Bin 10088 -> 0 bytes sumfiles/gdb.log.4.xz | Bin 10136 -> 0 bytes sumfiles/gdb.log.5.xz | Bin 10240 -> 0 bytes sumfiles/gdb.log.6.xz | Bin 10300 -> 0 bytes sumfiles/gdb.log.7.xz | Bin 9996 -> 0 bytes sumfiles/gdb.log.8.xz | Bin 10076 -> 0 bytes sumfiles/gdb.sum | 116 +- sumfiles/gdb.sum.0 | 133 +- sumfiles/gdb.sum.1 | 229 ++-- sumfiles/gdb.sum.2 | 211 +++- sumfiles/gdb.sum.3 | 2178 -------------------------------- sumfiles/gdb.sum.4 | 2176 -------------------------------- sumfiles/gdb.sum.5 | 2215 --------------------------------- sumfiles/gdb.sum.6 | 2185 -------------------------------- sumfiles/gdb.sum.7 | 2153 -------------------------------- sumfiles/gdb.sum.8 | 2159 -------------------------------- 43 files changed, 627 insertions(+), 13456 deletions(-) delete mode 100644 sumfiles/gdb.log.3.xz delete mode 100644 sumfiles/gdb.log.4.xz delete mode 100644 sumfiles/gdb.log.5.xz delete mode 100644 sumfiles/gdb.log.6.xz delete mode 100644 sumfiles/gdb.log.7.xz delete mode 100644 sumfiles/gdb.log.8.xz delete mode 100644 sumfiles/gdb.sum.3 delete mode 100644 sumfiles/gdb.sum.4 delete mode 100644 sumfiles/gdb.sum.5 delete mode 100644 sumfiles/gdb.sum.6 delete mode 100644 sumfiles/gdb.sum.7 delete mode 100644 sumfiles/gdb.sum.8 -- 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-spec2k6/gnu-arm-master-O2 updated (d8a17be93cd0 -> 0a71248592a9)

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-spec2k6/gnu-arm-master-O2 in repository toolchain/ci/base-artifacts. from d8a17be93cd0 98: onsuccess: #37: 1: [TCWG CI] Success after binutils: 2 [...] new 0a71248592a9 99: onsuccess: #38: 1: [TCWG CI] Success after glibc: 26 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2052 -> 2304 bytes 02-prepare_abe/console.log.xz | Bin 2572 -> 2524 bytes 03-build_abe-binutils/console.log.xz | Bin 26984 -> 26956 bytes 04-build_abe-stage1/console.log.xz | Bin 89696 -> 90272 bytes 06-build_abe-linux/console.log.xz | Bin 8428 -> 8396 bytes 07-build_abe-glibc/console.log.xz | Bin 233300 -> 232888 bytes 08-build_abe-stage2/console.log.xz | Bin 210524 -> 210988 bytes 09-benchmark/benchmark-build.log | 126 +- 09-benchmark/benchmark.log | 124 +- 09-benchmark/console.log.xz | Bin 4116 -> 4124 bytes 10-check_regression/bmk-specific-variability.csv | 158 +- .../compare-results-vs-first-internal.csv | 241 +- .../compare-results-vs-prev-internal.csv | 251 +- 10-check_regression/console.log.xz | Bin 16932 -> 16772 bytes .../csv-results-vs-first-1/md5sum.csv | 2907 +- .../csv-results-vs-first-1/perf.csv | 3372 +- .../csv-results-vs-first-1/results.csv | 24172 +- .../csv-results-vs-first-1/size.csv | 619047 +++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 19666 +- .../csv-results-vs-first-1/vect.csv | 56 +- .../csv-results-vs-prev-0/md5sum.csv | 2782 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 3394 +- .../csv-results-vs-prev-0/results.csv | 22289 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 535494 +++++++-------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 21878 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 54 +- .../csv-results-vs-prev-1/md5sum.csv | 2907 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 3372 +- .../csv-results-vs-prev-1/results.csv | 24172 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 619047 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 19666 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 56 +- .../output-bmk-results/symbol.improvement | 6 - .../output-bmk-results/symbol.improvement.diff | 1 - .../output-bmk-results/symbol.regression | 12 +- 10-check_regression/results-vs-first-brief.csv | 64 +- 10-check_regression/results-vs-first-full.csv | 3192 +- 10-check_regression/results-vs-first-internal.csv | 245 +- 10-check_regression/results-vs-first.csv | 245 +- 10-check_regression/results-vs-first.log | 1526 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 15 +- 10-check_regression/results-vs-prev-full.csv | 3456 +- 10-check_regression/results-vs-prev-internal.csv | 251 +- 10-check_regression/results-vs-prev.csv | 251 +- 10-check_regression/results-vs-prev.log | 1834 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 8 +- .../400.perlbench/results-metrics.json | 2 +- .../squad-vs-first/401.bzip2/results-metadata.json | 8 +- .../squad-vs-first/403.gcc/results-metadata.json | 8 +- .../410.bwaves/results-metadata.json | 8 +- .../416.gamess/results-metadata.json | 8 +- .../squad-vs-first/416.gamess/results-metrics.json | 2 +- .../squad-vs-first/429.mcf/results-metadata.json | 8 +- .../squad-vs-first/433.milc/results-metadata.json | 8 +- .../434.zeusmp/results-metadata.json | 8 +- .../435.gromacs/results-metadata.json | 8 +- .../436.cactusADM/results-metadata.json | 8 +- .../437.leslie3d/results-metadata.json | 8 +- .../squad-vs-first/444.namd/results-metadata.json | 8 +- .../squad-vs-first/445.gobmk/results-metadata.json | 8 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 8 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 8 +- .../453.povray/results-metadata.json | 8 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../454.calculix/results-metadata.json | 8 +- .../squad-vs-first/456.hmmer/results-metadata.json | 8 +- .../squad-vs-first/458.sjeng/results-metadata.json | 8 +- .../459.GemsFDTD/results-metadata.json | 8 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 8 +- .../464.h264ref/results-metadata.json | 8 +- .../squad-vs-first/465.tonto/results-metadata.json | 8 +- .../squad-vs-first/470.lbm/results-metadata.json | 8 +- .../471.omnetpp/results-metadata.json | 8 +- .../squad-vs-first/473.astar/results-metadata.json | 8 +- .../squad-vs-first/481.wrf/results-metadata.json | 8 +- .../482.sphinx3/results-metadata.json | 8 +- .../483.xalancbmk/results-metadata.json | 8 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 8 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/glibc_rev | 2 +- mail/changes-list-long.txt | 14 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 18 +- manifest.sh | 18 +- results_id | 2 +- 91 files changed, 963348 insertions(+), 973483 deletions(-) delete mode 100644 10-check_regression/output-bmk-results/symbol.improvement delete mode 100644 10-check_regression/output-bmk-results/symbol.improvement.diff -- 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-arm-lts-allnoconfig updated (1de3c3806bb4 -> 6c6383bfa713)

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-arm-lts-allnoconfig in repository toolchain/ci/base-artifacts. from 1de3c3806bb4 54: onsuccess: #8: all: Success after binutils/llvm/qemu: [...] new 6c6383bfa713 55: onsuccess: #9: all: [TCWG CI] Success after binutils/l [...] 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 1988 -> 1996 bytes 02-prepare_abe/console.log.xz | Bin 2520 -> 2560 bytes 03-build_abe-binutils/console.log.xz | Bin 27076 -> 26920 bytes 04-build_kernel_llvm/console.log.xz | Bin 65020 -> 64644 bytes 05-build_abe-qemu/console.log.xz | Bin 32364 -> 32188 bytes 06-build_linux/console.log.xz | Bin 3000 -> 2992 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 3836 -> 4164 bytes 08-check_regression/mail-body.txt | 27 --------------------------- 08-check_regression/mail-subject.txt | 1 - 09-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 26 ++++++++++++++++++++++++++ mail/changes-list-short.txt | 1 + manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 27 --------------------------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 32 ++++++++++++++++---------------- 23 files changed, 49 insertions(+), 86 deletions(-) delete mode 100644 08-check_regression/mail-body.txt delete mode 100644 08-check_regression/mail-subject.txt create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create 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-code_size-cpu2017fast/llvm-aarch64-master-Oz_LTO updated (78296a841660 -> 816c60047a81)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_size-cpu2017fast/llvm-aarch64-master-Oz_LTO in repository toolchain/ci/base-artifacts. from 78296a841660 7: onsuccess: #8: 1: [TCWG CI] No change after llvm: 375 commits new 816c60047a81 8: onsuccess: #10: 1: [TCWG CI] Success after llvm: 891 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1996 -> 1924 bytes 02-build_bmk_llvm/console.log.xz | Bin 99408 -> 100028 bytes 03-benchmark/benchmark-build.log | 106 +- 03-benchmark/benchmark.log | 104 +- 03-benchmark/console.log.xz | Bin 3860 -> 3844 bytes .../compare-results-vs-first-internal.csv | 52 +- .../compare-results-vs-prev-internal.csv | 52 +- 04-check_regression/console.log.xz | Bin 6092 -> 6272 bytes .../csv-results-vs-first-1/perf.csv | 100 +- .../csv-results-vs-first-1/results.csv | 83609 +++++++++++++------ .../csv-results-vs-first-1/size.csv | 83531 ++++++++++++------ 04-check_regression/csv-results-vs-first-1/sve.csv | 2 + 04-check_regression/csv-results-vs-prev-0/perf.csv | 82 +- .../csv-results-vs-prev-0/results.csv | 18687 +++-- 04-check_regression/csv-results-vs-prev-0/size.csv | 18601 +++-- 04-check_regression/csv-results-vs-prev-1/perf.csv | 100 +- .../csv-results-vs-prev-1/results.csv | 83609 +++++++++++++------ 04-check_regression/csv-results-vs-prev-1/size.csv | 83531 ++++++++++++------ 04-check_regression/csv-results-vs-prev-1/sve.csv | 2 + 04-check_regression/jira-body.txt | 1 - 04-check_regression/results-vs-first-brief.csv | 36 +- 04-check_regression/results-vs-first-full.csv | 102 +- 04-check_regression/results-vs-first-internal.csv | 41 +- 04-check_regression/results-vs-first.csv | 41 +- 04-check_regression/results-vs-first.log | 850 +- 04-check_regression/results-vs-prev-brief.csv | 36 +- 04-check_regression/results-vs-prev-full.csv | 104 +- 04-check_regression/results-vs-prev-internal.csv | 41 +- 04-check_regression/results-vs-prev.csv | 41 +- 04-check_regression/results-vs-prev.log | 946 +- dashboard/dashboard-generate.sh | 2 +- .../508.namd_r/results-metadata.json | 10 +- .../510.parest_r/results-functional.json | 2 +- .../510.parest_r/results-metadata.json | 10 +- .../510.parest_r/results-metrics.json | 3 +- .../511.povray_r/results-metadata.json | 10 +- .../511.povray_r/results-metrics.json | 2 +- .../526.blender_r/results-metadata.json | 10 +- .../526.blender_r/results-metrics.json | 2 +- .../600.perlbench_s/results-metadata.json | 10 +- .../600.perlbench_s/results-metrics.json | 2 +- .../squad-vs-first/602.gcc_s/results-metadata.json | 10 +- .../squad-vs-first/602.gcc_s/results-metrics.json | 2 +- .../603.bwaves_s/results-metadata.json | 10 +- .../squad-vs-first/605.mcf_s/results-metadata.json | 10 +- .../squad-vs-first/605.mcf_s/results-metrics.json | 2 +- .../607.cactuBSSN_s/results-metadata.json | 10 +- .../squad-vs-first/619.lbm_s/results-metadata.json | 10 +- .../squad-vs-first/619.lbm_s/results-metrics.json | 2 +- .../620.omnetpp_s/results-functional.json | 4 +- .../620.omnetpp_s/results-metadata.json | 10 +- .../620.omnetpp_s/results-metrics.json | 1 + .../squad-vs-first/621.wrf_s/results-metadata.json | 10 +- .../623.xalancbmk_s/results-functional.json | 4 +- .../623.xalancbmk_s/results-metadata.json | 10 +- .../623.xalancbmk_s/results-metrics.json | 1 + .../625.x264_s/results-metadata.json | 10 +- .../squad-vs-first/625.x264_s/results-metrics.json | 2 +- .../627.cam4_s/results-metadata.json | 10 +- .../628.pop2_s/results-metadata.json | 10 +- .../631.deepsjeng_s/results-metadata.json | 10 +- .../631.deepsjeng_s/results-metrics.json | 2 +- .../638.imagick_s/results-metadata.json | 10 +- .../638.imagick_s/results-metrics.json | 2 +- .../641.leela_s/results-functional.json | 2 +- .../641.leela_s/results-metadata.json | 10 +- .../641.leela_s/results-metrics.json | 1 + .../squad-vs-first/644.nab_s/results-metadata.json | 10 +- .../squad-vs-first/644.nab_s/results-metrics.json | 2 +- .../648.exchange2_s/results-metadata.json | 10 +- .../649.fotonik3d_s/results-metadata.json | 10 +- .../654.roms_s/results-metadata.json | 10 +- .../squad-vs-first/657.xz_s/results-metadata.json | 10 +- .../squad-vs-first/657.xz_s/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 102 +- git/llvm_rev | 2 +- mail/changes-list-long.txt | 8 + mail/changes-list-short.txt | 1 + mail/jira-body.txt | 7 - manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 19 - mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 16 +- results_id | 2 +- 86 files changed, 244661 insertions(+), 130197 deletions(-) delete mode 100644 04-check_regression/jira-body.txt create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt delete mode 100644 mail/jira-body.txt copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create 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-code_speed-cpu2017rate/gnu-aarch64-master-O2_LTO updated (a031674544ea -> 73e9047faa88)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/gnu-aarch64-master-O2_LTO in repository toolchain/ci/base-artifacts. from a031674544ea 13: onsuccess: #19: 1: [TCWG CI] 521.wrf_r speeds up by -5 [...] new 73e9047faa88 14: onsuccess: #21: 1: [TCWG CI] Success after binutils/gc [...] 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 2080 -> 2056 bytes 02-prepare_abe/console.log.xz | Bin 2592 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 27696 -> 27144 bytes 04-build_abe-stage1/console.log.xz | Bin 71384 -> 70872 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 7520 -> 8288 bytes 07-build_abe-glibc/console.log.xz | Bin 242944 -> 241720 bytes 08-build_abe-stage2/console.log.xz | Bin 175580 -> 175280 bytes 09-benchmark/benchmark-build.log | 155 +- 09-benchmark/benchmark.log | 153 +- 09-benchmark/console.log.xz | Bin 4148 -> 4104 bytes 10-check_regression/bmk-specific-variability.csv | 1 + .../compare-results-vs-first-internal.csv | 66 +- .../compare-results-vs-prev-internal.csv | 66 +- 10-check_regression/console.log.xz | Bin 9276 -> 9820 bytes .../csv-results-vs-first-0/results.csv | 639512 ++++++++--------- .../csv-results-vs-first-0/size.csv | 632818 ++++++++--------- 10-check_regression/csv-results-vs-first-0/sve.csv | 39484 +- .../csv-results-vs-first-0/vect.csv | 496 +- .../csv-results-vs-first-1/perf.csv | 146 +- .../csv-results-vs-first-1/results.csv | 646422 +++++++++-------- .../csv-results-vs-first-1/size.csv | 649913 +++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 39922 +- .../csv-results-vs-first-1/vect.csv | 454 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 146 +- .../csv-results-vs-prev-0/results.csv | 638743 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/size.csv | 642206 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 39994 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 494 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 146 +- .../csv-results-vs-prev-1/results.csv | 646422 +++++++++-------- 10-check_regression/csv-results-vs-prev-1/size.csv | 649913 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 39922 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 454 +- 10-check_regression/exe.improvement | 1 - 10-check_regression/extra-bisect-params | 2 +- 10-check_regression/jira-body.txt | 4 - 10-check_regression/mail-body.txt | 3 - 10-check_regression/mail-subject.txt | 2 +- .../output-bmk-results/exe.improvement.diff | 1 - .../output-bmk-results/exe.regression | 2 + .../output-bmk-results/exe.regression.diff | 1 + 10-check_regression/results-vs-first-brief.csv | 56 +- 10-check_regression/results-vs-first-full.csv | 160 +- 10-check_regression/results-vs-first-internal.csv | 66 +- 10-check_regression/results-vs-first.csv | 66 +- 10-check_regression/results-vs-first.log | 1406 +- 10-check_regression/results-vs-prev-brief.csv | 56 +- 10-check_regression/results-vs-prev-compare.csv | 2 +- 10-check_regression/results-vs-prev-full.csv | 162 +- 10-check_regression/results-vs-prev-internal.csv | 66 +- 10-check_regression/results-vs-prev.csv | 66 +- 10-check_regression/results-vs-prev.log | 1626 +- dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 16 +- .../500.perlbench_r/results-metrics.json | 4 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 16 +- .../503.bwaves_r/results-metadata.json | 16 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 16 +- .../507.cactuBSSN_r/results-metadata.json | 16 +- .../508.namd_r/results-metadata.json | 16 +- .../squad-vs-first/508.namd_r/results-metrics.json | 2 +- .../510.parest_r/results-metadata.json | 16 +- .../511.povray_r/results-metadata.json | 16 +- .../511.povray_r/results-metrics.json | 4 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 16 +- .../520.omnetpp_r/results-metadata.json | 16 +- .../520.omnetpp_r/results-metrics.json | 2 +- .../squad-vs-first/521.wrf_r/results-metadata.json | 16 +- .../squad-vs-first/521.wrf_r/results-metrics.json | 2 +- .../523.xalancbmk_r/results-metadata.json | 16 +- .../523.xalancbmk_r/results-metrics.json | 2 +- .../525.x264_r/results-metadata.json | 16 +- .../squad-vs-first/525.x264_r/results-metrics.json | 2 +- .../526.blender_r/results-metadata.json | 16 +- .../527.cam4_r/results-metadata.json | 16 +- .../531.deepsjeng_r/results-metadata.json | 16 +- .../531.deepsjeng_r/results-metrics.json | 4 +- .../538.imagick_r/results-metadata.json | 16 +- .../538.imagick_r/results-metrics.json | 2 +- .../541.leela_r/results-metadata.json | 16 +- .../541.leela_r/results-metrics.json | 2 +- .../squad-vs-first/544.nab_r/results-metadata.json | 16 +- .../squad-vs-first/544.nab_r/results-metrics.json | 2 +- .../548.exchange2_r/results-metadata.json | 16 +- .../549.fotonik3d_r/results-metadata.json | 16 +- .../549.fotonik3d_r/results-metrics.json | 2 +- .../554.roms_r/results-metadata.json | 16 +- .../squad-vs-first/554.roms_r/results-metrics.json | 2 +- .../squad-vs-first/557.xz_r/results-metadata.json | 16 +- .../squad-vs-first/Mean/results-metadata.json | 16 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 104 +- dashboard/squad-vs-first/summary-annotation.txt | 1 - git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 26 + mail/changes-list-short.txt | 1 + mail/jira-body.txt | 23 - manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 35 - mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 36 +- results_id | 2 +- 106 files changed, 2648367 insertions(+), 2664085 deletions(-) create mode 100644 10-check_regression/bmk-specific-variability.csv delete mode 100644 10-check_regression/exe.improvement delete mode 100644 10-check_regression/jira-body.txt delete mode 100644 10-check_regression/output-bmk-results/exe.improvement.diff create mode 100644 10-check_regression/output-bmk-results/exe.regression create mode 100644 10-check_regression/output-bmk-results/exe.regression.diff create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt delete mode 100644 mail/jira-body.txt copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create 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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits April 2023