Tcwg-commits November 2022

tcwg-commits@lists.linaro.org

5 participants
4683 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (59d96d01f1 -> 4318ee56a4)

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 59d96d01f1 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 7c04fbb629 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 864bf7ea7d 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards 3ce19ad71f 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 36e1f562e7 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 571a23d9e2 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 66c9852a99 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 6a1eae0c85 103: onsuccess: #589: 1: Success after binutils: 3 commits discards eadea46d36 102: onsuccess: #586: 1: Success after binutils: 5 commits discards d3edc10c38 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 950c4279f1 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 3e4bbe4174 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 37b007eaa6 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 94421aba98 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 2b3672fe5c 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 027410a90e 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 4bd2792fce 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards d2b17d66fb 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 8d77db6a72 92: onsuccess: #575: 1: Success after linux: 34 commits discards bb4694c132 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 199299aafd 90: onsuccess: #572: 1: Success after binutils: 15 commits discards cef83e7fec 89: onsuccess: #570: 1: Success after linux: 11 commits discards f6331971a3 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 65b9a21bdb 87: onsuccess: #567: 1: Success after binutils: 8 commits discards ecff13d3a7 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards a991b79a69 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 3a0b11ac03 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 035c4488a3 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards a5883c40e8 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 592b5b350d 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards c5fa724f56 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 882447bf62 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards c3feea65b9 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 52e2f3b25f 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 3b1cdd16f7 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards fd7f4e035e 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 3ef87d0334 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 029f20e4f5 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 5d1b0b7873 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 8645036adc 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards c3d329262c 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards e389f41ff4 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 4f14e4b900 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards 82ef83415f 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 476015a6f4 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards d278fc6bff 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 6de3c1d820 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 66f03b681e 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 0c3f61bfe7 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards efa8b13e6b 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 846efb816e 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards 216cbdf4a7 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 4a00c19c6a 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 060651ef69 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards 0e716356ef 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards e7599ba8ab 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards d85ea5160c 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards b70f641e51 53: onsuccess: #531: 1: Success after binutils: 12 commits discards a1209fd78a 52: onsuccess: #528: 1: Success after binutils: 8 commits discards d645c9dfb1 51: onsuccess: #525: 1: Success after binutils: 8 commits discards bafb63c741 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards fdf2d46cfd 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards f3eeee8d2d 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards c4a3344285 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards 48abc8928d 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards afb52b33fc 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards 12fb5600f8 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 59beaf5503 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 30bd2bf4da 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] discards bbd7decf85 41: onsuccess: #514: 1: Success after linux: 64 commits discards 2b57ee9a32 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] discards d7c1276a26 39: onsuccess: #511: 1: Success after binutils: 8 commits discards eaccc989b8 38: onsuccess: #508: 1: Success after binutils: 3 commits discards 95ce16248f 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards 9c1e0c60a3 36: onsuccess: #505: 1: Success after glibc: 3 commits discards d977bd1b1b 35: onsuccess: #503: 1: Success after binutils: 11 commits discards dfc9fe24d2 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards e087290132 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] discards 1b67bd6dde 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards c54bccf383 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards ba592ce233 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards e8ee9b0fa4 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 6b93d54e47 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] discards b881389c6f 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 5a5dda1a0f 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] discards 1f9543003d 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards ff7a659082 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards d9f790fcda 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 91b35e5c13 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 0ba7a0c908 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ba3f5b4dd1 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f2fd2141bb 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 415d0f09e9 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 91b969a547 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b918d8b9fe 16: onsuccess: 1: Successful build after binutils: 4 commits discards 4bc2a77155 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c6025458f5 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0406d1e369 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b03608a669 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 17412a12af 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b1aa44d9d6 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a505e8e290 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c40bbecb30 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 26e36244d7 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 43df73ca6e 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 04d118b005 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new eb67c9817a 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d519a19aea 16: onsuccess: 1: Successful build after binutils: 4 commits new 78509f2bef 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a590987791 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3960f662d2 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f031d93e7f 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 30fc9b39aa 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f02345bfda 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new a22e96e43e 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 3ff06887d4 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 33310d0b45 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new fe9b1c94b5 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] new 7a9bb97761 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 979f092260 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] new 6e1e8be296 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new a71cd75b1f 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new f2d88c9e2c 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new bc9e639171 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 76e1ba1368 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] new 137b3ac8e9 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 40a9df4854 35: onsuccess: #503: 1: Success after binutils: 11 commits new 1c4253e83c 36: onsuccess: #505: 1: Success after glibc: 3 commits new 433bceae99 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] new a126fd6df3 38: onsuccess: #508: 1: Success after binutils: 3 commits new 35a8fd313c 39: onsuccess: #511: 1: Success after binutils: 8 commits new cd9eff205c 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] new 576a1361d6 41: onsuccess: #514: 1: Success after linux: 64 commits new ccd15bbc61 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new f128e8f3d3 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 18fddc6ddf 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new cb9e5c34d5 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new 18ba628880 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new efa5377d07 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new e3c23090a8 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new ce8e37978b 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new b65c7f0346 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new 1d3bf9895c 51: onsuccess: #525: 1: Success after binutils: 8 commits new 7ce083405f 52: onsuccess: #528: 1: Success after binutils: 8 commits new 57bcf7c5fd 53: onsuccess: #531: 1: Success after binutils: 12 commits new b5daebd29d 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new 9b768dc89f 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 321e576257 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 97d3afbf1d 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new d0cc0b7c30 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new fa40d61ef1 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 39d0cab296 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new 0403ce3cba 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 6b41f6c184 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 640aa964b9 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 53615dbaae 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 872bd0778f 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new db6ea9ab82 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 5550ce6512 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 30afb9cc4c 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new a5e8bfc948 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 476128a20f 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 60673d2cb9 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 97a2859a6a 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new d30d3b9e36 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new d51741dd79 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 413643601f 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 4c6a4f3871 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 02cee064a0 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 67bf73abbb 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new f597e76cd8 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 5bcde7f21d 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new a0b57e2352 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 691775881e 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 91ff65778f 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new e99fc2aa6b 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 6e39fa2fe0 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new d34e62fd19 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 81ce858efa 87: onsuccess: #567: 1: Success after binutils: 8 commits new dd0d0255dd 88: onsuccess: #569: 1: Success after glibc: 10 commits new d90a79557f 89: onsuccess: #570: 1: Success after linux: 11 commits new ad9f1e7972 90: onsuccess: #572: 1: Success after binutils: 15 commits new 53c9e35d18 91: onsuccess: #574: 1: Success after glibc: 3 commits new 9957efe169 92: onsuccess: #575: 1: Success after linux: 34 commits new cae9ae27fb 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 84050247d2 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new efb2c7241a 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 3d24384a18 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 821b0c27a7 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 1ddfdd0a60 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new e86092c79b 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new db897f52b7 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 97277fe67e 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 821854263b 102: onsuccess: #586: 1: Success after binutils: 5 commits new d86550e125 103: onsuccess: #589: 1: Success after binutils: 3 commits new 33b252df16 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 9a2414ea0e 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 28a359e06d 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 33cf365081 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new a814cb5c3f 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 0f83d2abfb 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 2bde17d3e7 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new 4318ee56a4 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (59d96d01f1) \ 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 1744 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 54272 -> 53092 bytes 04-build_abe-gcc/console.log.xz | Bin 236900 -> 236384 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8380 -> 8364 bytes 07-build_abe-glibc/console.log.xz | Bin 235784 -> 235632 bytes 08-build_abe-gdb/console.log.xz | Bin 52052 -> 51168 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3816 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2404 -> 2216 bytes 11-check_regression/console.log.xz | Bin 17288 -> 15048 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 37 +- 11-check_regression/mail-body.txt | 162 +- 11-check_regression/results.compare | 145 +- 11-check_regression/results.compare2 | 1389 +---- 11-check_regression/results.regressions | 102 +- 12-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 164 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results | 102 +- sumfiles/gdb.log.xz | Bin 1689220 -> 1718060 bytes sumfiles/gdb.sum | 9197 +++++++++++++++++++++---------- 29 files changed, 6944 insertions(+), 4462 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (2bba27d644 -> cc678af966)

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_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards 2bba27d644 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/g [...] discards 820c7eefc9 190: onsuccess: #1774: 7: Success after binutils: 10 commits discards ae26f9a271 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 37 [...] discards 1b7631ff2d 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/g [...] discards daf6e4a66d 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/g [...] discards 4f2b277d03 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/g [...] discards 02e94a26f0 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] discards 8720a4d9b1 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/g [...] discards 6da99c523a 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/g [...] discards fc36c44790 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/g [...] discards 159d4064aa 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/g [...] discards 3b88b59b24 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] discards 3c4c80c199 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards 23c1cae5ea 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/g [...] discards f0cc6f2c3f 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 7735d294a8 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/g [...] discards 9433dea2cf 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/g [...] discards 0b090b4f9a 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 15 [...] discards 75697008b7 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 5f22e3bda0 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qemu [...] discards 8d2a11b7e1 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 12 [...] discards a335fb1731 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/g [...] discards ab516c9303 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/g [...] discards 8348000655 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/g [...] discards 8489cfaaa4 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 28 [...] discards cc2a8f3fc6 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits discards 2b5ae3e7ac 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/g [...] discards 9a6bf78297 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/g [...] discards 14bbd5410a 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 12 [...] discards 57d7ec3d4d 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 commits discards 3ba1ea510e 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/g [...] discards f33033945c 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 4027706a19 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards c3228c292d 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] discards ac837ccc79 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards 1fe0a64945 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards 634a508d52 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] discards f7514d4aa6 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards ad74ee038f 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] discards 37861c45c6 152: force: #1605: 7: Success after gcc: 9 commits discards 2f1c72feea 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] discards a9455ae67a 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] discards 95b7a69051 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards 1e5777debf 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards 9dafee2802 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards 16219aef03 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards db9187ea66 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards e3513e31dc 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards d8071634cb 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards fe196725d5 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards e407657d5e 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 4929758594 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards 0168a1822f 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards 7007440f19 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards a0da331c92 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 6e2096d24c 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards 8e54b0f09f 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards ef0461ac56 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 422ed134d2 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards d6313430fc 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards a3f5d307e8 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 7d16046139 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards f86893f207 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards 04043b6e5f 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 2e4c35a7ff 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards ab7c339da7 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 75fb7d2144 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 0047da4d11 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards b533bb14b9 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards c8cbd7df83 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 3f4d963df4 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards 7fa0579ba7 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards e6ce996e9f 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 70d7c5b571 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards 72a50c390e 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 9d13770d1a 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards f6b082f990 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards e00869087a 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards 2c0217ca11 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards be9ecbc4cb 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards 279a250cba 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards f691bddb9c 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 50ff88aa11 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 14b51d12b0 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 28cf853378 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 562fe58678 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 3a9ad60fd9 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards b27686a40d 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards 34c8e4b375 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards e9e7176f06 102: force: #1551: 1: Failure after gcc: 306 commits discards e96d21c688 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 2d3c059442 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 855c257589 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 9e62a2cd96 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 21ac00d80a 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards a3292c12ab 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 413a33b9e2 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 8bd6bb8052 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards ccd64bf31a 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards cf3915b955 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 4c8fc32988 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 853f29b70e 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 9161e046a1 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 5264bf5ac3 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new d1c5b32337 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new b1c686e367 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new b94e190416 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 3418414d15 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new a5d26a7644 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 331f8a5291 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 3428f98585 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 37c5b04b19 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 22754f2804 102: force: #1551: 1: Failure after gcc: 306 commits new bd5a539e89 103: onsuccess: #1552: 1: Success after gcc: 5 commits new f643be014c 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 6e88142f7a 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new fa0476d0d8 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new e5eb8da61a 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new 7ae7e21a0e 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new 3d452d3a55 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new ac28ef729c 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 8a61cde472 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new c42cf84658 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new b6f7ab9c60 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new 204d99b0ef 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 0b0f5763c6 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 9e5e9fe1af 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 8898fee0d7 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new ea18fd6bc7 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new 07a3399915 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new db2a9ff852 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 5dcc1749f5 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 4fe15eb1ca 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 7b619e5d69 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new bbfeca0f8a 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new b902aea642 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 98e972f4dc 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 8409d8993c 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new 03668c1cfb 128: onsuccess: #1579: 7: Success after linux: 12 commits new a3fe997ef5 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new ffad5f532c 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new ed193161a7 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new 12e15b97cb 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 528040e20d 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new a6147b92b0 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new 4c17b3cf42 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new a8d995379d 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new affcceca24 137: onsuccess: #1588: 7: Success after gcc: 5 commits new b764c03378 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new 212edb9612 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 2607d19444 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new db48eb5887 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new e5cacc0de6 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new 4a83a6e6cb 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new 5d663ff78e 144: onsuccess: #1595: 7: Success after glibc: 2 commits new 8d6bb6048f 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new 75d7871fdf 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new 3d7c9d4f9d 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new a617841028 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new 32b36f03be 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new f3f99cc095 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] new 594269f1fc 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] new fb3aa281d9 152: force: #1605: 7: Success after gcc: 9 commits new 8abfde24a5 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] new f7ff423bc7 154: onsuccess: #1607: 1: Success after gcc: 2 commits new 06a2ff3eb5 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] new 0b8f2125f9 156: onsuccess: #1609: 7: Success after gcc: 2 commits new cf306e7712 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new f2585080a7 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] new f2985ce9f3 159: onsuccess: #1612: 7: Success after gcc: 4 commits new 11c07832b1 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new f458c3e53c 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/g [...] new b1811403a2 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 commits new 00549cfb7f 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 12 [...] new ad62dd77e2 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/g [...] new 6a95a6fcf8 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/g [...] new da0c1cbc10 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits new a04b40e792 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 28 [...] new 453d8d892b 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/g [...] new 7157b34b7c 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/g [...] new e9e4989e91 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/g [...] new 75743b0910 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 12 [...] new cb47d501a5 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qemu [...] new 241f8755c3 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 8191507778 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 15 [...] new 2555ab0eaf 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/g [...] new 69852ef840 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/g [...] new a02555ee5b 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 0767af3c4c 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/g [...] new 9a0f125819 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new ccb3778c56 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] new 3076b76f29 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/g [...] new 7addcc46b7 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/g [...] new 9691e9b11c 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/g [...] new b52f09945d 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/g [...] new 9bb1b390de 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] new 5ca3839e47 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/g [...] new 560acbe5c9 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/g [...] new 1ff7d14308 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/g [...] new d0b828ffd7 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 37 [...] new ddd04101ce 190: onsuccess: #1774: 7: Success after binutils: 10 commits new 90cf11a07a 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/g [...] new cc678af966 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/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 (2bba27d644) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 1680 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 32120 -> 31780 bytes 05-build_abe-stage1/console.log.xz | Bin 73616 -> 74100 bytes 07-build_abe-linux/console.log.xz | Bin 8656 -> 8292 bytes 08-build_abe-glibc/console.log.xz | Bin 243580 -> 243560 bytes 09-build_abe-stage2/console.log.xz | Bin 204476 -> 204824 bytes 10-build_abe-gdb/console.log.xz | Bin 39340 -> 38960 bytes 11-build_abe-qemu/console.log.xz | Bin 31220 -> 31368 bytes 12-check_regression/console.log.xz | Bin 5488 -> 5156 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ 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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +++++++++++++------------- 22 files changed, 66 insertions(+), 66 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (542c825371 -> 1aa97e7877)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 542c825371 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 74686a94ec 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards ea7f611b6a 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 9105e4f5fd 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards b548daea55 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards c5094bf867 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 9815fda0de 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 230b98331d 95: onsuccess: #835: 1: Success after binutils: 3 commits discards a9b58fd3db 94: onsuccess: #832: 1: Success after binutils: 5 commits discards dee562e0c6 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 6c789d69c1 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 44f85b7699 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards d0a8515d76 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards de0e7ed6ac 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 4650b30521 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 69606f4f32 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 6de8910eee 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 25350d600f 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 9a7d791fac 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards e851d7c1e5 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards fd9c7dd67a 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards b4293befd4 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 0d1856385d 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards d126e6cf38 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 9ba0507ce8 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 275b43698c 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards ad7003ee2b 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 90f2e14a37 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 3fa2c5f65c 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 4f4fda49fc 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 070248922f 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 1ecd899883 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 9db7857684 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards c9c37b1d5e 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 1ab05e8b87 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 673e669279 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 4e1688d34e 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 5483197a74 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards ec602f5fa0 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards e88bba9b91 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 2cd79b8ebf 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards c3841c6ed8 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards a3df40993d 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards e3e67e0081 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 46bf1fa0e4 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards 609f27ca18 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards bb6733085f 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards a97a0b91cf 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 40a578b0cb 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards 6c13dbdfa0 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 294ace5026 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards e536c9ea30 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards f4b78269a9 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards fb8f25be9f 49: onsuccess: #785: 1: Success after binutils: 12 commits discards f75d570d23 48: onsuccess: #782: 1: Success after binutils: 8 commits discards d81b3e6078 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 74ff3c86c1 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards d38dd8e5e9 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards f90ddf8895 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards 2d1203d8a3 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards cc21f650f3 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards 1afc206d9a 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards 1e6ef5be2a 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] discards 878d84e35a 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] discards 8a0af56acb 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] discards d6c360b462 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] discards 618dfb578c 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 511a098942 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] discards 159b7206e1 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] discards acd93bffe5 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] discards b75ab67353 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] discards 77c54cb69b 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] discards 50470632ec 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] discards 5339d37c1d 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] discards 690ad4d291 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] discards d76d65c3f6 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] discards e522ab0136 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] discards 006fefc06b 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] discards 662a6734f5 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards 443b438182 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards d21f16d48c 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 64ad0320f1 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 03c39c6fd0 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 081994ca2d 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1c3d4a2b86 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5bcdc44fa0 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 92104184f5 16: onsuccess: 1: Successful build after binutils: 4 commits discards 08acfdaff3 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5fedfddc0e 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f036af0085 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e3b48ef670 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 091568d807 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f463378b18 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1987156052 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a42de4047f 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 9dd60d73b4 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards cf3ed3347f 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 7984c39d25 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 1cad7a3833 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 30aa0973cd 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 143cceedd9 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new f348979073 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 4e305383e9 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new a744e2945b 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 820c096d57 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 360f240957 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new d055da0d61 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new bb7c2a77f8 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new f9ac8a25b5 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c52e383ff7 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new babdc3e24f 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fc64b540b4 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b961cf32d3 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4008500922 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new eb3733acc5 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 46e770d61e 16: onsuccess: 1: Successful build after binutils: 4 commits new dd0e9e8694 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9b6801d502 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 23e7013aa6 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f9a9a7e1fa 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bd377d7977 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 278aa2e01c 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 58e6585ba8 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 4a41bff458 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 6f6f49cb08 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] new e15491788f 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] new 1e55c22a2f 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] new dbac8a3727 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] new 8c90c4f542 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] new e9c11279fd 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] new 6cb1da5a7e 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] new 2d8b8de2dd 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] new 97beab0550 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] new 02ad3523f0 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] new 5f7ca5fbe6 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] new 151aa0675c 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new b444605a3d 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] new 5120ef8a5c 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] new 508fdd906e 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] new 984bf64465 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new 414ee26008 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new 0742c1eabe 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new 6769485d2c 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new 04f5ed61b5 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new 2ff4ece4ce 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new b49e1442d6 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new a0b219770b 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new 94b1480a6d 48: onsuccess: #782: 1: Success after binutils: 8 commits new 192ca53f30 49: onsuccess: #785: 1: Success after binutils: 12 commits new 66eaec6df4 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new 074a9a56f7 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new 5f5b1c57b8 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new c909221efa 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 4ac8cbc969 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 6eb190649d 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 254bb676f5 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new e37a93db85 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new 76230ebac7 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new a5bd5e330a 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 58e0cd5555 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new c312cdd3bb 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new d9330ad12d 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 8a4123f6da 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 5ad3a8e543 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 6ad83501f0 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new e21fdaacd6 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 451e23a9da 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 00f64bbc77 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new a1a9b991f7 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 7d687bb15e 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new f88324098e 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 7ebb5d6e0c 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 09b821d6b8 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new c9f49e297e 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 807d7eee5c 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 394c4ef349 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 56a0131452 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 82ca3839d1 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 6e877311c3 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 55976fa96f 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 34481c3b05 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new 37cb8ca0dc 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new c0cf4d4bfd 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new f58ac3ef1c 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 5ab54f4819 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 5ddc199adc 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 4eaf51b755 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new c02e8263bb 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 19eca28185 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 7aafccf583 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new be84b88f36 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 32568b3ce4 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 081fa0f078 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new a1efc2d8c7 94: onsuccess: #832: 1: Success after binutils: 5 commits new c5b3d84293 95: onsuccess: #835: 1: Success after binutils: 3 commits new 89390fc79e 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 8dcaeebb6d 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 09d3ad869b 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 48dedfb3b2 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 5bd70d0f45 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new ae322eefb1 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new f3b86bba50 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 1aa97e7877 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (542c825371) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1696 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2716 bytes 03-build_abe-binutils/console.log.xz | Bin 39796 -> 39184 bytes 04-build_abe-gcc/console.log.xz | Bin 214372 -> 214444 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8288 -> 8296 bytes 07-build_abe-glibc/console.log.xz | Bin 244648 -> 244028 bytes 08-build_abe-gdb/console.log.xz | Bin 39888 -> 39000 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3832 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2836 -> 2684 bytes 11-check_regression/console.log.xz | Bin 8152 -> 6680 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 6 + 11-check_regression/mail-body.txt | 26 + 11-check_regression/results.compare | 25 +- 11-check_regression/results.compare2 | 492 +-- 11-check_regression/results.regressions | 26 + 12-update_baseline/console.log | 36 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results | 26 + sumfiles/g++.log.xz | Bin 3778280 -> 3768964 bytes sumfiles/g++.sum | 167 +- sumfiles/gcc.log.xz | Bin 3304204 -> 3295056 bytes sumfiles/gcc.sum | 4936 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1081064 -> 1080092 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 231396 -> 230512 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 455508 -> 446520 bytes sumfiles/libstdc++.sum | 13 +- 41 files changed, 2885 insertions(+), 3005 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_tx1/gnu-master-aarch64-cpu2017rate-O2 updated (1943fce594 -> 747e41f5c9)

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_gnu_tx1/gnu-master-aarch64-cpu2017rate-O2 in repository toolchain/ci/base-artifacts. from 1943fce594 10: force: #27: 1: [TCWG CI] 526.blender_r failed to build a [...] new 747e41f5c9 11: force: #29: 1: [TCWG CI] 527.cam4_r failed to build afte [...] 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 1736 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 31812 -> 31644 bytes 04-build_abe-stage1/console.log.xz | Bin 73876 -> 72692 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 7976 -> 8716 bytes 07-build_abe-glibc/console.log.xz | Bin 245428 -> 243724 bytes 08-build_abe-stage2/console.log.xz | Bin 178804 -> 177004 bytes 09-benchmark/benchmark-build.log | 126 +- 09-benchmark/benchmark.log | 124 +- 09-benchmark/console.log.xz | Bin 3864 -> 3808 bytes 10-check_regression/console.log.xz | Bin 13440 -> 12224 bytes .../csv-results-vs-first-0/md5sum.csv | 2504 +- .../csv-results-vs-first-0/results.csv | 161436 +++--- .../csv-results-vs-first-0/size.csv | 543748 +++++++++--------- .../csv-results-vs-first-0/vect.csv | 600 +- .../csv-results-vs-first-1/md5sum.csv | 2181 +- .../csv-results-vs-first-1/perf.csv | 2484 +- .../csv-results-vs-first-1/results.csv | 188321 +++--- .../csv-results-vs-first-1/size.csv | 414313 +++++++------ .../csv-results-vs-first-1/vect.csv | 575 +- .../csv-results-vs-prev-0/md5sum.csv | 2081 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 2622 +- .../csv-results-vs-prev-0/results.csv | 93872 +-- 10-check_regression/csv-results-vs-prev-0/size.csv | 475541 +++++++-------- 10-check_regression/csv-results-vs-prev-0/vect.csv | 634 +- .../csv-results-vs-prev-1/md5sum.csv | 2181 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 2484 +- .../csv-results-vs-prev-1/results.csv | 188321 +++--- 10-check_regression/csv-results-vs-prev-1/size.csv | 414313 +++++++------ 10-check_regression/csv-results-vs-prev-1/vect.csv | 575 +- 10-check_regression/exe.improvement | 1 + 10-check_regression/exe.regression | 3 +- 10-check_regression/extra-bisect-params | 2 +- 10-check_regression/jira-body.txt | 5 +- 10-check_regression/mail-body.txt | 5 +- 10-check_regression/mail-subject.txt | 2 +- 10-check_regression/results-vs-first-brief.csv | 48 +- 10-check_regression/results-vs-first-full.csv | 2383 +- 10-check_regression/results-vs-first-internal.csv | 166 +- 10-check_regression/results-vs-first.csv | 166 +- 10-check_regression/results-vs-first.log | 1020 +- 10-check_regression/results-vs-prev-brief.csv | 56 +- 10-check_regression/results-vs-prev-compare.csv | 11 +- 10-check_regression/results-vs-prev-full.csv | 2533 +- 10-check_regression/results-vs-prev-internal.csv | 176 +- 10-check_regression/results-vs-prev.csv | 176 +- 10-check_regression/results-vs-prev.log | 1334 +- 10-check_regression/results.regressions | 7 +- 10-check_regression/skipped-symbols.txt | 4 +- 10-check_regression/trigger-bisect | 3 - 10-check_regression/trigger-notify | 0 dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 8 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 8 +- .../503.bwaves_r/results-metadata.json | 8 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 8 +- .../507.cactuBSSN_r/results-metadata.json | 8 +- .../507.cactuBSSN_r/results-metrics.json | 2 +- .../508.namd_r/results-metadata.json | 8 +- .../squad-vs-first/508.namd_r/results-metrics.json | 2 +- .../510.parest_r/results-metadata.json | 8 +- .../511.povray_r/results-metadata.json | 8 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 8 +- .../520.omnetpp_r/results-metadata.json | 8 +- .../squad-vs-first/521.wrf_r/results-metadata.json | 8 +- .../squad-vs-first/521.wrf_r/results-metrics.json | 2 +- .../523.xalancbmk_r/results-metadata.json | 8 +- .../525.x264_r/results-metadata.json | 8 +- .../526.blender_r/results-metadata.json | 8 +- .../527.cam4_r/results-functional.json | 4 +- .../527.cam4_r/results-metadata.json | 8 +- .../squad-vs-first/527.cam4_r/results-metrics.json | 3 - .../531.deepsjeng_r/results-metadata.json | 8 +- .../531.deepsjeng_r/results-metrics.json | 2 +- .../538.imagick_r/results-metadata.json | 8 +- .../541.leela_r/results-metadata.json | 8 +- .../541.leela_r/results-metrics.json | 2 +- .../squad-vs-first/544.nab_r/results-metadata.json | 8 +- .../548.exchange2_r/results-metadata.json | 8 +- .../549.fotonik3d_r/results-functional.json | 4 +- .../549.fotonik3d_r/results-metadata.json | 8 +- .../549.fotonik3d_r/results-metrics.json | 3 + .../554.roms_r/results-metadata.json | 8 +- .../squad-vs-first/554.roms_r/results-metrics.json | 2 +- .../squad-vs-first/557.xz_r/results-metadata.json | 8 +- .../squad-vs-first/Mean/results-metadata.json | 8 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 100 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 129 - jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 10 +- mail/mail-body.txt | 10 +- mail/mail-subject.txt | 2 +- manifest.sh | 15 +- results | 7 +- results_id | 2 +- 99 files changed, 1188537 insertions(+), 1319104 deletions(-) create mode 100644 10-check_regression/exe.improvement delete mode 100644 10-check_regression/trigger-bisect delete mode 100644 10-check_regression/trigger-notify delete mode 100644 jenkins/jira-status.draft delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 updated (63ea4b6621 -> 3a6851bb94)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. from 63ea4b6621 16: onsuccess: #21: 1: Success after binutils/gcc/linux/glib [...] new 3a6851bb94 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 52 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 1688 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2716 bytes 03-build_abe-binutils/console.log.xz | Bin 39672 -> 39592 bytes 04-build_abe-gcc/console.log.xz | Bin 214604 -> 213688 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8388 -> 8444 bytes 07-build_abe-glibc/console.log.xz | Bin 245428 -> 245976 bytes 08-build_abe-gdb/console.log.xz | Bin 40068 -> 39964 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3972 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2744 -> 2648 bytes 11-check_regression/console.log.xz | Bin 6124 -> 5760 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- 12-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- sumfiles/gdb.log.xz | Bin 14516 -> 14484 bytes sumfiles/gdb.sum | 34 +++++++++++++++++----------------- 24 files changed, 45 insertions(+), 45 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[gcc] branch master updated (55cb8c5c9ab -> 936d40b9ba9)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 55cb8c5c9ab Fix wrong array type conversion with different storage orde new 936d40b9ba9 testsuite: Fix missing EFFECTIVE_TARGETS variable errors The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/testsuite/lib/target-supports.exp | 41 ++++++++++++++++++++--------------- 1 file changed, 23 insertions(+), 18 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[binutils-gdb] branch master updated (d7229d6a561 -> f3f7ecc942f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from d7229d6a561 binutils/configure.ac: integrate last change new f3f7ecc942f gdb/arm: Fix obvious typo in b0b23e06c3a 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: gdb/arm-tdep.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-aarch64-bootstrap_profiled_lto_lean updated (d93edb850b -> 3a41cd009b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/release-aarch64-bootstrap_profiled_lto_lean in repository toolchain/ci/base-artifacts. from d93edb850b 32: onsuccess: #141: 2: Success after binutils: 3 commits new 3a41cd009b 33: onsuccess: #142: 2: Success after gcc: 7 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 1872 -> 1636 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 37968 -> 38052 bytes .../console.log.xz | Bin 509016 -> 508244 bytes 06-check_regression/console.log.xz | Bin 2408 -> 2620 bytes 07-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +++++++------- 12 files changed, 21 insertions(+), 12 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[gcc] branch master updated (dfc1ea414e0 -> 55cb8c5c9ab)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from dfc1ea414e0 libstdc++: Replace std::isdigit and std::isxdigit in <forma [...] new 55cb8c5c9ab Fix wrong array type conversion with different storage orde The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/testsuite/gnat.dg/sso18.adb | 21 +++++++++++++++++++++ gcc/tree-loop-distribution.cc | 7 ++++++- 2 files changed, 27 insertions(+), 1 deletion(-) create mode 100644 gcc/testsuite/gnat.dg/sso18.adb -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[gcc] branch devel/modula-2 updated (1e33c0019ba -> 7b0ef381ac5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch devel/modula-2 in repository gcc. from 1e33c0019ba Revert sphinx and reintroduce texinfo make rules. new 7b0ef381ac5 Improve detection of python. 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: configure | 14 +-- gcc/aclocal.m4 | 286 ++++++++++++++++++++++++++++++++++++++++++++ gcc/configure | 239 +++++++++++++++++++++++++++++++++++- gcc/configure.ac | 70 +++++------ libgm2/Makefile.in | 1 - libgm2/configure | 18 +-- libgm2/libm2cor/Makefile.in | 1 - libgm2/libm2iso/Makefile.in | 1 - libgm2/libm2log/Makefile.in | 1 - libgm2/libm2min/Makefile.in | 1 - libgm2/libm2pim/Makefile.in | 1 - 11 files changed, 561 insertions(+), 72 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits November 2022