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 (13feacb3c8 -> 8ff27634e5)

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 13feacb3c8 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards a19862f1a5 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards e1195e7de9 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 1d964898a5 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards ccff8378bb 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards 9e50349633 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 25ff68ab4b 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards e0614f4de8 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards ec6c51e0bd 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 2d47028d76 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 2911b55b0c 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 6160462ad6 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 57fd0f8f5a 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards d05ba7cff6 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards a1045d4d30 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards d93df53363 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards a45eabbf20 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 932877a815 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards a678badfba 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 0c05a56482 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 048ec7e01f 92: onsuccess: #575: 1: Success after linux: 34 commits discards f40929d240 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 40eac092ae 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 17e28a33cf 89: onsuccess: #570: 1: Success after linux: 11 commits discards 1fc1980622 88: onsuccess: #569: 1: Success after glibc: 10 commits discards be861f57e4 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 2d9a0ddf7b 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards cdde8c4e3c 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 7a52f62dc7 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards d47b8f67e8 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 7b65859a54 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards af5ac270bd 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 5430830ab5 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards fa61a72d9c 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards bb7676e737 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards a631e234d8 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 3f88f8ff95 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 2f5e13bdab 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 48d42f087b 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards b4b36c6d18 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 77b38a423d 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 28c858f50d 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 157a94751e 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards a90080056b 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 98daabbd21 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards e3817d0cdc 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 39373e0c00 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 81e887f4fd 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 4c52c12a94 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 76cd1eb9a6 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards ed423cd68f 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards a2d5ab94fb 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 24a57c6eb4 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards d86595d132 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards ac20560c93 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards cd95816f00 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards 78970aeb97 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards bfe8122561 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards ab57ee66ed 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards acb79ddd2b 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 00d55e1457 52: onsuccess: #528: 1: Success after binutils: 8 commits discards a9a06523ca 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 4df44f6d52 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards 4c3cfed0d8 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards 5f943db743 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards 9c591286ab 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards 8df84a6499 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards d20715cf27 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards 8c1a159a7a 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 56583c61a9 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 7268775d02 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] discards dbd1e6ec60 41: onsuccess: #514: 1: Success after linux: 64 commits discards 2f43f4d929 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] discards e4efde7a9d 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 252d6d4cee 38: onsuccess: #508: 1: Success after binutils: 3 commits discards 31d10e038d 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards 7703277c07 36: onsuccess: #505: 1: Success after glibc: 3 commits discards 257277f42f 35: onsuccess: #503: 1: Success after binutils: 11 commits discards 7bcf5fda01 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 32e2a524fb 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] discards 318ed568c3 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 88adf7ae0e 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards 6d5a5b9e09 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards a35dd90d72 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards bc582dc3a3 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] discards 5d47ca2bf8 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 3b3d9994cd 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] discards 9a945ad416 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards be7f5bdd4b 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards e2b2c40b56 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 736b16a6cf 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 796303b3ea 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fe418183c1 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cd5cf240d9 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dd5a1a9eb7 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4069185045 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 198184b02a 16: onsuccess: 1: Successful build after binutils: 4 commits discards 0e4c4649cb 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bb727c5c0d 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 417bca2070 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 06840521ff 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 05e6341e18 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c435f1f287 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9c91487718 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 028ce2c26e 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 887fc2a2ec 16: onsuccess: 1: Successful build after binutils: 4 commits new fbb29c4cf8 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3b2089211e 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ce53188256 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b4ef6daa8e 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5ce576918d 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e41e4b4a32 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 9ae4e2dc58 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 5930c03987 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new a12afc12b9 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 068e7ff370 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] new ecf3032d6c 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 91290ef0ff 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] new d31a3ed36f 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new c80a7004f4 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 96705b4954 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new da01324472 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 2f94156d64 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] new 413ba11147 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new ede1dd8526 35: onsuccess: #503: 1: Success after binutils: 11 commits new 956525e549 36: onsuccess: #505: 1: Success after glibc: 3 commits new 876a8cb3a6 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 17bb21b3ad 38: onsuccess: #508: 1: Success after binutils: 3 commits new 986a2224c7 39: onsuccess: #511: 1: Success after binutils: 8 commits new 165d0d236f 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] new 2b48ce5997 41: onsuccess: #514: 1: Success after linux: 64 commits new 2957a77c8f 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new 29e48d2682 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 77209f524c 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 5e86e29e10 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new f45d1b4e48 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new ec68993817 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new 7bbd764588 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new c5f827d215 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 926698864e 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new 5a99df54bb 51: onsuccess: #525: 1: Success after binutils: 8 commits new 6559e6bdc1 52: onsuccess: #528: 1: Success after binutils: 8 commits new 92280a2415 53: onsuccess: #531: 1: Success after binutils: 12 commits new 1fcf2b954c 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new 8073d0897c 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 18843227cc 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 9e5e1702ed 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new fefe85f5f3 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new d7ec2cd875 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 2a27919237 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new a55638cc7e 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 078a9c0b0d 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 56217eacf5 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new fab90fb8f8 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 843d73a9a2 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 6aaea03175 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 3b0d2472d7 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 610709e496 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new ed9173ca1b 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new e7e0b168d7 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 80f815dcba 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new e6bdcc0d5e 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new b08ff49f9b 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new c6d606d2ac 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 3c2c6c27d3 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 77d39aa2c0 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 8a6d52d2b0 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 8f073a9baa 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 139a0275ec 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 3ebf4da571 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 8a971d0743 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new e848d52b98 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 4cb808ebf3 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 13118e7fe5 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 196dec1bb9 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 03f7252cfd 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new f61579a8f6 87: onsuccess: #567: 1: Success after binutils: 8 commits new eadf489dd4 88: onsuccess: #569: 1: Success after glibc: 10 commits new 8d80aecce3 89: onsuccess: #570: 1: Success after linux: 11 commits new 63c252ddd6 90: onsuccess: #572: 1: Success after binutils: 15 commits new 8a66f8f75b 91: onsuccess: #574: 1: Success after glibc: 3 commits new 83d06ad6cb 92: onsuccess: #575: 1: Success after linux: 34 commits new 8e8220d55d 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 21c24872ac 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 8931a772f3 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new ba994ebfeb 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new b3bf3aac53 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new e17de61114 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new d008f6538a 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 7629f65d19 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new c8968012f4 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new e31cde74eb 102: onsuccess: #586: 1: Success after binutils: 5 commits new 11baa7ffbe 103: onsuccess: #589: 1: Success after binutils: 3 commits new 720bf16da1 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new bf1846730d 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 9e115977d8 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new fd10c9d537 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 416eacd448 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 1f08cec5c2 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new c04bc4c5c2 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new 5043dab7c8 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new c7a043e9f7 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 8ff27634e5 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] 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 (13feacb3c8) \ 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 1672 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 53476 -> 53192 bytes 04-build_abe-gcc/console.log.xz | Bin 236372 -> 236040 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8320 -> 8656 bytes 07-build_abe-glibc/console.log.xz | Bin 235400 -> 236392 bytes 08-build_abe-gdb/console.log.xz | Bin 52104 -> 51660 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3820 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2332 -> 2176 bytes 11-check_regression/console.log.xz | Bin 13148 -> 12508 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 70 +- 11-check_regression/mail-body.txt | 234 +- 11-check_regression/results.compare | 103 +- 11-check_regression/results.compare2 | 1728 ++------ 11-check_regression/results.regressions | 102 +- 12-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 236 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 102 +- sumfiles/gdb.log.xz | Bin 1786760 -> 1711952 bytes sumfiles/gdb.sum | 6949 +++++++++++++++++++------------ 30 files changed, 5196 insertions(+), 4440 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_kernel/gnu-master-aarch64-lts-allnoconfig updated (48e3db9f97 -> fccdfa02f9)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-allnoconfig in repository toolchain/ci/base-artifacts. from 48e3db9f97 23: onsuccess: #465: boot: Success after binutils/gcc/qemu: [...] new fccdfa02f9 24: onsuccess: #466: boot: Success after binutils/gcc/qemu: [...] 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 1716 -> 1892 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 32096 -> 31900 bytes 04-build_abe-stage1/console.log.xz | Bin 73784 -> 73128 bytes 05-build_abe-qemu/console.log.xz | Bin 31244 -> 31900 bytes 06-build_linux/console.log.xz | Bin 3320 -> 3308 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3980 -> 3884 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 16 files changed, 21 insertions(+), 21 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_kernel/llvm-master-arm-stable-allmodconfig updated (44a7bccb26 -> 693b67a485)

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-stable-allmodconfig in repository toolchain/ci/base-artifacts. from 44a7bccb26 40: onsuccess: #512: 23023: Success after binutils/llvm/qemu [...] new 693b67a485 41: onsuccess: #513: 23023: Success after binutils/llvm/qemu [...] 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 1700 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 31468 -> 31436 bytes 04-build_kernel_llvm/console.log.xz | Bin 65856 -> 65576 bytes 05-build_abe-qemu/console.log.xz | Bin 30712 -> 31544 bytes 06-build_linux/console.log.xz | Bin 5224 -> 5900 bytes 08-check_regression/console.log.xz | Bin 4084 -> 3928 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 15 files changed, 21 insertions(+), 21 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_bmk_gnu_eabi_stm32/gnu_eabi-release-arm_eabi-coremark-O3 updated (1e7c66f8b9 -> 1fab01612a)

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_eabi_stm32/gnu_eabi-release-arm_eabi-coremark-O3 in repository toolchain/ci/base-artifacts. from 1e7c66f8b9 13: onsuccess: #153: 1: [TCWG CI] No change after binutils/g [...] new 1fab01612a 14: onsuccess: #154: 1: [TCWG CI] No change after binutils/g [...] 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 1708 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30044 -> 30248 bytes 04-build_abe-stage1/console.log.xz | Bin 85584 -> 85464 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-newlib/console.log.xz | Bin 16768 -> 16664 bytes 07-build_abe-stage2/console.log.xz | Bin 159752 -> 159640 bytes 08-benchmark/benchmark-build.log | 102 ++++++++++----------- 08-benchmark/benchmark.log | 100 ++++++++++---------- 08-benchmark/console.log.xz | Bin 3792 -> 3804 bytes 09-check_regression/console.log.xz | Bin 4484 -> 4780 bytes 09-check_regression/results-vs-first.log | 80 ++++++++-------- 09-check_regression/results-vs-prev.log | 82 ++++++++--------- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/Mean/results-metadata.json | 12 +-- .../squad-vs-first/coremark/results-metadata.json | 12 +-- dashboard/squad-vs-first/dashboard-push-squad.sh | 10 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/newlib_rev | 2 +- mail/jira-body.txt | 29 +++--- mail/mail-body.txt | 29 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++--- results_id | 2 +- 25 files changed, 252 insertions(+), 246 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_kernel/llvm-release-arm-stable-allnoconfig updated (e3bdb12b3a -> a7906d586b)

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-release-arm-stable-allnoconfig in repository toolchain/ci/base-artifacts. from e3bdb12b3a 23: onsuccess: #248: all: Success after binutils/qemu: 12 commits new a7906d586b 24: onsuccess: #249: all: Success after binutils/llvm/qemu: [...] 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 1692 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30000 -> 29960 bytes 04-build_kernel_llvm/console.log.xz | Bin 64952 -> 64868 bytes 05-build_abe-qemu/console.log.xz | Bin 30608 -> 31224 bytes 06-build_linux/console.log.xz | Bin 3400 -> 3424 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 3308 -> 3500 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 16 files changed, 21 insertions(+), 21 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_fast_check_gdb/master-aarch64 updated (3dd527c9c5 -> 86bbbf3345)

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 3dd527c9c5 18: onsuccess: #23: 1: Success after binutils/gcc/gdb: 64 commits new 86bbbf3345 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb: [...] 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 1684 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 39544 -> 39416 bytes 04-build_abe-gcc/console.log.xz | Bin 214868 -> 213756 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8408 -> 8604 bytes 07-build_abe-glibc/console.log.xz | Bin 245156 -> 245556 bytes 08-build_abe-gdb/console.log.xz | Bin 39424 -> 39408 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3920 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2688 -> 2536 bytes 11-check_regression/console.log.xz | Bin 5364 -> 7552 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 258 +++++++++++++++++++++++++++++++- 12-update_baseline/console.log | 9 -- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 ++--- sumfiles/gdb.log.xz | Bin 14492 -> 14676 bytes sumfiles/gdb.sum | 269 +++++++++++++++++----------------- 25 files changed, 414 insertions(+), 176 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[binutils-gdb] branch master updated (f9e2163a3e4 -> cbff1430f8a)

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 f9e2163a3e4 gdb: fix typo in debug output message new cbff1430f8a sframe/doc: remove usage of xrefautomaticsectiontitle 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: libsframe/doc/sframe-spec.texi | 7 ++----- 1 file changed, 2 insertions(+), 5 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_kernel/gnu-master-arm-lts-allmodconfig updated (7ee453ad44 -> 8718e748c5)

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-lts-allmodconfig in repository toolchain/ci/base-artifacts. from 7ee453ad44 27: onsuccess: #488: 33: Success after binutils/gcc/qemu: 12 [...] new 8718e748c5 28: onsuccess: #489: 33: Success after binutils/gcc/qemu: 23 [...] 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 1704 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32012 -> 31944 bytes 04-build_abe-stage1/console.log.xz | Bin 91428 -> 92420 bytes 05-build_abe-qemu/console.log.xz | Bin 30512 -> 31856 bytes 06-build_linux/console.log.xz | Bin 5180 -> 5220 bytes 08-check_regression/console.log.xz | Bin 4008 -> 3948 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 15 files changed, 21 insertions(+), 21 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_check/master-arm updated (2e1f936075 -> d099b46fb0)

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_check/master-arm in repository toolchain/ci/base-artifacts. discards 2e1f936075 346: onsuccess: #1982: 1: Success after binutils/gcc: 19 commits discards 00933e2d7f 345: onsuccess: #1981: 1: Success after binutils/gcc: 8 commits discards 3396a6df1d 344: onsuccess: #1980: 1: Success after gcc: 3 commits discards a669b37b7e 343: onsuccess: #1979: 1: Success after binutils/gcc: 8 commits discards 7985f7cfdd 342: onsuccess: #1978: 1: Success after binutils/gcc: 6 commits discards 95452805e1 341: onsuccess: #1977: 1: Success after binutils/gcc: 14 commits discards 6f43fd1ac9 340: onsuccess: #1976: 1: Success after binutils/gcc: 22 commits discards fa03302277 339: onsuccess: #1975: 1: Success after binutils/gcc: 10 commits discards aadac125a7 338: onsuccess: #1974: 1: Success after binutils/gcc: 5 commits discards e0e4df6e8c 337: onsuccess: #1973: 1: Success after binutils/gcc: 10 commits discards 692617273d 336: onsuccess: #1972: 1: Success after binutils/gcc: 11 commits discards 72862e1eb6 335: onsuccess: #1971: 1: Success after binutils/gcc: 14 commits discards 8b19e2017b 334: onsuccess: #1970: 1: Success after gcc: 20 commits discards 4c64400450 333: onsuccess: #1969: 1: Success after binutils/gcc: 5 commits discards 4b8ca6c9b2 332: onsuccess: #1968: 1: Success after gcc: 3 commits discards db95a981ef 331: onsuccess: #1967: 1: Success after binutils/gcc: 4 commits discards 17a45b7a87 330: onsuccess: #1966: 1: Success after binutils/gcc: 3 commits discards fda0bf73e2 329: onsuccess: #1965: 1: Success after gcc: 2 commits discards cc4413af20 328: onsuccess: #1964: 1: Success after binutils/gcc: 8 commits discards 4be855c610 327: onsuccess: #1963: 1: Success after gcc: 3 commits discards 67b8c6699c 326: onsuccess: #1962: 1: Success after binutils/gcc: 5 commits discards fe229b4c23 325: onsuccess: #1961: 1: Success after binutils/gcc: 16 commits discards b3c12f3f8b 324: onsuccess: #1960: 1: Success after binutils/gcc: 14 commits discards e92b6ed451 323: onsuccess: #1959: 1: Success after binutils/gcc: 11 commits discards 61f20a9600 322: onsuccess: #1957: 1: Success after binutils/gcc: 9 commits discards d5cf237d44 321: onsuccess: #1956: 1: Success after binutils/gcc: 12 commits discards 9f9e97117a 320: onsuccess: #1955: 1: Success after binutils/gcc: 11 commits discards 5f2b8cff05 319: onsuccess: #1954: 1: Success after binutils/gcc: 9 commits discards aba5d033a1 318: onsuccess: #1953: 1: Success after gcc: 11 commits discards 73fd32d18c 317: onsuccess: #1952: 1: Success after binutils/gcc: 22 commits discards f081711771 316: onsuccess: #1951: 1: Success after binutils/gcc: 8 commits discards d40822f0ea 315: onsuccess: #1950: 1: Success after basepoints/gcc-13-40 [...] discards 68257e3e71 314: onsuccess: #1949: 1: Success after binutils/gcc: 17 commits discards f2c427b10e 313: onsuccess: #1948: 1: Success after binutils/gcc: 105 commits discards a9ac4837a7 312: onsuccess: #1947: 1: Success after gcc: 87 commits discards 247d3c30cb 311: onsuccess: #1945: 1: Success after binutils: 3 commits discards 6adef0ad51 310: onsuccess: #1941: 1: Success after binutils: 2 commits discards 086abc608d 309: onsuccess: #1938: 1: Success after gdb-12-branchpoint-2 [...] discards aac6c8db0e 308: onsuccess: #1934: 1: Success after gdb-12-branchpoint-2 [...] discards 4bbffc987b 307: onsuccess: #1931: 1: Success after binutils: 2 commits discards 49c69ed686 306: onsuccess: #1928: 1: Success after gdb-12-branchpoint-2 [...] discards 323ca0f06a 305: onsuccess: #1926: 1: Success after binutils/gcc: 8 commits discards d95cba967e 304: onsuccess: #1925: 1: Success after binutils/gcc: 21 commits discards 1e889a277c 303: onsuccess: #1924: 1: Success after binutils/gcc: 23 commits discards 79f0ca7d69 302: onsuccess: #1923: 1: Success after binutils/gcc: 6 commits discards f2f0d33346 301: onsuccess: #1922: 1: Success after binutils/gcc: 13 commits discards ee66e991b2 300: onsuccess: #1921: 1: Success after binutils/gcc: 18 commits discards e3309f8eb7 299: onsuccess: #1920: 1: Success after binutils/gcc: 12 commits discards c24b77e1c7 298: onsuccess: #1919: 1: Success after binutils/gcc: 7 commits discards 96ed39fe9b 297: onsuccess: #1918: 1: Success after binutils/gcc: 12 commits discards 5d5b158362 296: onsuccess: #1917: 1: Success after binutils/gcc: 14 commits discards f35094023a 295: onsuccess: #1916: 1: Success after binutils/gcc: 29 commits discards c9e4bf61e7 294: onsuccess: #1915: 1: Success after binutils/gcc: 6 commits discards 7229be18dd 293: onsuccess: #1914: 1: Success after binutils/gcc: 12 commits discards 18763d7a27 292: onsuccess: #1913: 1: Success after binutils/gcc: 11 commits discards 46466041e3 291: onsuccess: #1912: 1: Success after binutils/gcc: 30 commits discards e3b986848b 290: onsuccess: #1911: 1: Success after binutils/gcc: 15 commits discards d286ead1fc 289: onsuccess: #1910: 1: Success after binutils/gcc: 8 commits discards 16580f4989 288: onsuccess: #1909: 1: Success after binutils/gcc: 18 commits discards 407851499a 287: onsuccess: #1908: 1: Success after gcc: 36 commits discards 31eb75f48c 286: onsuccess: #1907: 1: Success after binutils/gcc: 8 commits discards 1eb6f2e956 285: onsuccess: #1906: 1: Success after basepoints/gcc-13-37 [...] discards ffb1c54791 284: onsuccess: #1905: 1: Success after binutils/gcc: 8 commits discards 3d295d2010 283: onsuccess: #1904: 1: Success after basepoints/gcc-13-37 [...] discards 07afd0b5d3 282: onsuccess: #1903: 1: Success after binutils/gcc: 4 commits discards c7a69e28b1 281: onsuccess: #1902: 1: Success after gcc: 2 commits discards fa596716a4 280: onsuccess: #1901: 1: Success after binutils/gcc: 10 commits discards 2da9f76277 279: onsuccess: #1900: 1: Success after basepoints/gcc-13-36 [...] discards ed52f6d1fc 278: onsuccess: #1899: 1: Success after binutils: 9 commits discards 9706c2de36 277: onsuccess: #1898: 1: Success after gcc: 4 commits discards 5e6b43418c 276: onsuccess: #1897: 1: Success after binutils/gcc: 42 commits discards 7261458314 275: onsuccess: #1896: 1: Success after binutils/gcc: 12 commits discards b4f787c93e 274: onsuccess: #1895: 1: Success after binutils/gcc: 13 commits discards fdf994de21 273: onsuccess: #1894: 1: Success after binutils/gcc: 20 commits discards d22258886e 272: onsuccess: #1893: 1: Success after binutils/gcc: 12 commits discards 20d14fc0ec 271: onsuccess: #1892: 1: Success after binutils/gcc: 7 commits discards acaa47b09e 270: onsuccess: #1891: 1: Success after binutils/gcc: 3 commits discards a06e6b7d01 269: onsuccess: #1890: 1: Success after binutils/gcc: 8 commits discards a8044a1811 268: onsuccess: #1889: 1: Success after binutils/gcc: 11 commits discards f708704cd8 267: onsuccess: #1888: 1: Success after binutils/gcc: 6 commits discards 16bfe608e9 266: onsuccess: #1887: 1: Success after binutils/gcc: 8 commits discards 16282ee963 265: onsuccess: #1886: 1: Success after gcc: 5 commits discards da390066c1 264: onsuccess: #1885: 1: Success after binutils/gcc: 9 commits discards 378259effb 263: onsuccess: #1884: 1: Success after binutils/gcc: 5 commits discards 6d55e38541 262: onsuccess: #1883: 1: Success after binutils/gcc: 7 commits discards 2c0f2c9d5f 261: onsuccess: #1882: 1: Success after binutils/gcc: 6 commits discards cdf35eb2b5 260: onsuccess: #1881: 1: Success after binutils/gcc: 19 commits discards bd8d515456 259: onsuccess: #1880: 1: Success after binutils/gcc: 8 commits discards 1ca8f5f281 258: onsuccess: #1879: 1: Success after binutils/gcc: 6 commits discards 614223361c 257: onsuccess: #1878: 1: Success after gdb-12-branchpoint-2 [...] discards 5102829a5c 256: onsuccess: #1877: 1: Success after binutils/gcc: 2 commits discards 365923d562 255: onsuccess: #1876: 1: Success after binutils/gcc: 4 commits discards 19371a8ee9 254: onsuccess: #1875: 1: Success after binutils/gcc: 13 commits discards 783dbc7030 253: onsuccess: #1874: 1: Success after binutils/gcc: 10 commits discards 51e62bf585 252: onsuccess: #1873: 1: Success after binutils/gcc: 4 commits discards 965d0dd35c 251: onsuccess: #1872: 1: Success after binutils/gcc: 10 commits discards 3426b61ac3 250: onsuccess: #1871: 1: Success after binutils/gcc: 11 commits discards 15999c5225 249: onsuccess: #1870: 1: Success after binutils/gcc: 9 commits discards 0b9e9d71ea 248: onsuccess: #1869: 1: Success after gcc: 4 commits discards 2ba6422dfb 247: onsuccess: #1868: 1: Success after binutils/gcc: 7 commits discards 6cf6b51ce3 246: onsuccess: #1867: 1: Success after binutils/gcc: 8 commits new 48f98618c9 246: onsuccess: #1867: 1: Success after binutils/gcc: 8 commits new 22c26b0879 247: onsuccess: #1868: 1: Success after binutils/gcc: 7 commits new f5e31d469a 248: onsuccess: #1869: 1: Success after gcc: 4 commits new 53ce04a85a 249: onsuccess: #1870: 1: Success after binutils/gcc: 9 commits new 170f05c8e7 250: onsuccess: #1871: 1: Success after binutils/gcc: 11 commits new e5a8c34ba9 251: onsuccess: #1872: 1: Success after binutils/gcc: 10 commits new 1d8366f532 252: onsuccess: #1873: 1: Success after binutils/gcc: 4 commits new 1cc0fea7a8 253: onsuccess: #1874: 1: Success after binutils/gcc: 10 commits new 9bd95df01d 254: onsuccess: #1875: 1: Success after binutils/gcc: 13 commits new 60aadd43fb 255: onsuccess: #1876: 1: Success after binutils/gcc: 4 commits new 1a756be235 256: onsuccess: #1877: 1: Success after binutils/gcc: 2 commits new f2ab8833bb 257: onsuccess: #1878: 1: Success after gdb-12-branchpoint-2 [...] new 956b83fdf5 258: onsuccess: #1879: 1: Success after binutils/gcc: 6 commits new cd4d1a2633 259: onsuccess: #1880: 1: Success after binutils/gcc: 8 commits new 531b8f14af 260: onsuccess: #1881: 1: Success after binutils/gcc: 19 commits new 04d7db2b75 261: onsuccess: #1882: 1: Success after binutils/gcc: 6 commits new 4c383f87d9 262: onsuccess: #1883: 1: Success after binutils/gcc: 7 commits new 037b227bdd 263: onsuccess: #1884: 1: Success after binutils/gcc: 5 commits new a95eab4c7d 264: onsuccess: #1885: 1: Success after binutils/gcc: 9 commits new c4ec678af9 265: onsuccess: #1886: 1: Success after gcc: 5 commits new 73d1e5804b 266: onsuccess: #1887: 1: Success after binutils/gcc: 8 commits new 1be0f0e2d9 267: onsuccess: #1888: 1: Success after binutils/gcc: 6 commits new 2b991e955b 268: onsuccess: #1889: 1: Success after binutils/gcc: 11 commits new 126dd16506 269: onsuccess: #1890: 1: Success after binutils/gcc: 8 commits new 3cb893f585 270: onsuccess: #1891: 1: Success after binutils/gcc: 3 commits new 3d0798b94b 271: onsuccess: #1892: 1: Success after binutils/gcc: 7 commits new 4798b39cbe 272: onsuccess: #1893: 1: Success after binutils/gcc: 12 commits new da36ebcd7a 273: onsuccess: #1894: 1: Success after binutils/gcc: 20 commits new ad7f82326b 274: onsuccess: #1895: 1: Success after binutils/gcc: 13 commits new 170a67d06f 275: onsuccess: #1896: 1: Success after binutils/gcc: 12 commits new 421568368c 276: onsuccess: #1897: 1: Success after binutils/gcc: 42 commits new 65ac6f2393 277: onsuccess: #1898: 1: Success after gcc: 4 commits new 0ee2b3294e 278: onsuccess: #1899: 1: Success after binutils: 9 commits new c69be68d7f 279: onsuccess: #1900: 1: Success after basepoints/gcc-13-36 [...] new 6e5d4ab755 280: onsuccess: #1901: 1: Success after binutils/gcc: 10 commits new e5026e7f5c 281: onsuccess: #1902: 1: Success after gcc: 2 commits new ea97a96226 282: onsuccess: #1903: 1: Success after binutils/gcc: 4 commits new 9080451f01 283: onsuccess: #1904: 1: Success after basepoints/gcc-13-37 [...] new e377e7b685 284: onsuccess: #1905: 1: Success after binutils/gcc: 8 commits new 01fc299c93 285: onsuccess: #1906: 1: Success after basepoints/gcc-13-37 [...] new 894b4a7501 286: onsuccess: #1907: 1: Success after binutils/gcc: 8 commits new 9a993a3b07 287: onsuccess: #1908: 1: Success after gcc: 36 commits new 38ccb7d837 288: onsuccess: #1909: 1: Success after binutils/gcc: 18 commits new f7c8e2f8e8 289: onsuccess: #1910: 1: Success after binutils/gcc: 8 commits new 58419348f2 290: onsuccess: #1911: 1: Success after binutils/gcc: 15 commits new a6e1a3e637 291: onsuccess: #1912: 1: Success after binutils/gcc: 30 commits new c4dadae40a 292: onsuccess: #1913: 1: Success after binutils/gcc: 11 commits new 05db83fd80 293: onsuccess: #1914: 1: Success after binutils/gcc: 12 commits new d3df8c34e2 294: onsuccess: #1915: 1: Success after binutils/gcc: 6 commits new 78ab8efecd 295: onsuccess: #1916: 1: Success after binutils/gcc: 29 commits new 2e191fb641 296: onsuccess: #1917: 1: Success after binutils/gcc: 14 commits new 389fff0045 297: onsuccess: #1918: 1: Success after binutils/gcc: 12 commits new 260b4fccbc 298: onsuccess: #1919: 1: Success after binutils/gcc: 7 commits new 146f28f041 299: onsuccess: #1920: 1: Success after binutils/gcc: 12 commits new da31ee9e6d 300: onsuccess: #1921: 1: Success after binutils/gcc: 18 commits new c3bdb9d764 301: onsuccess: #1922: 1: Success after binutils/gcc: 13 commits new cb9fc2ae9d 302: onsuccess: #1923: 1: Success after binutils/gcc: 6 commits new 4759554d7a 303: onsuccess: #1924: 1: Success after binutils/gcc: 23 commits new 58f89471da 304: onsuccess: #1925: 1: Success after binutils/gcc: 21 commits new ae1f740a28 305: onsuccess: #1926: 1: Success after binutils/gcc: 8 commits new d8767e2356 306: onsuccess: #1928: 1: Success after gdb-12-branchpoint-2 [...] new 9da3d19fe8 307: onsuccess: #1931: 1: Success after binutils: 2 commits new 321e85561c 308: onsuccess: #1934: 1: Success after gdb-12-branchpoint-2 [...] new e717c24b1f 309: onsuccess: #1938: 1: Success after gdb-12-branchpoint-2 [...] new 5e00545f89 310: onsuccess: #1941: 1: Success after binutils: 2 commits new e86e824353 311: onsuccess: #1945: 1: Success after binutils: 3 commits new bb62bdddad 312: onsuccess: #1947: 1: Success after gcc: 87 commits new 708ec73408 313: onsuccess: #1948: 1: Success after binutils/gcc: 105 commits new 1abbe8a8a9 314: onsuccess: #1949: 1: Success after binutils/gcc: 17 commits new a50832916a 315: onsuccess: #1950: 1: Success after basepoints/gcc-13-40 [...] new c6c99cb095 316: onsuccess: #1951: 1: Success after binutils/gcc: 8 commits new 9164ff0ae4 317: onsuccess: #1952: 1: Success after binutils/gcc: 22 commits new 565c5984c4 318: onsuccess: #1953: 1: Success after gcc: 11 commits new 222a2120d8 319: onsuccess: #1954: 1: Success after binutils/gcc: 9 commits new 619b832be6 320: onsuccess: #1955: 1: Success after binutils/gcc: 11 commits new 826bc28ee9 321: onsuccess: #1956: 1: Success after binutils/gcc: 12 commits new 61dc8086a1 322: onsuccess: #1957: 1: Success after binutils/gcc: 9 commits new 55bbe195ab 323: onsuccess: #1959: 1: Success after binutils/gcc: 11 commits new 3f5bdd6a81 324: onsuccess: #1960: 1: Success after binutils/gcc: 14 commits new a0982f8ed0 325: onsuccess: #1961: 1: Success after binutils/gcc: 16 commits new c92e6de641 326: onsuccess: #1962: 1: Success after binutils/gcc: 5 commits new 8d605404c6 327: onsuccess: #1963: 1: Success after gcc: 3 commits new dec7e005fc 328: onsuccess: #1964: 1: Success after binutils/gcc: 8 commits new 97c2959255 329: onsuccess: #1965: 1: Success after gcc: 2 commits new da51b549c7 330: onsuccess: #1966: 1: Success after binutils/gcc: 3 commits new 33e9f13c8d 331: onsuccess: #1967: 1: Success after binutils/gcc: 4 commits new 5068592eed 332: onsuccess: #1968: 1: Success after gcc: 3 commits new b4effe24b9 333: onsuccess: #1969: 1: Success after binutils/gcc: 5 commits new 3aa390eda4 334: onsuccess: #1970: 1: Success after gcc: 20 commits new eff04bb687 335: onsuccess: #1971: 1: Success after binutils/gcc: 14 commits new 131fcbe89e 336: onsuccess: #1972: 1: Success after binutils/gcc: 11 commits new 26559e3e07 337: onsuccess: #1973: 1: Success after binutils/gcc: 10 commits new d5f62d8889 338: onsuccess: #1974: 1: Success after binutils/gcc: 5 commits new ba363fb70e 339: onsuccess: #1975: 1: Success after binutils/gcc: 10 commits new 1913980400 340: onsuccess: #1976: 1: Success after binutils/gcc: 22 commits new e13b288ffd 341: onsuccess: #1977: 1: Success after binutils/gcc: 14 commits new d2c7f96f1b 342: onsuccess: #1978: 1: Success after binutils/gcc: 6 commits new f01c9e626e 343: onsuccess: #1979: 1: Success after binutils/gcc: 8 commits new 18455632ba 344: onsuccess: #1980: 1: Success after gcc: 3 commits new adadecb754 345: onsuccess: #1981: 1: Success after binutils/gcc: 8 commits new 3ea814319b 346: onsuccess: #1982: 1: Success after binutils/gcc: 19 commits new d099b46fb0 347: onsuccess: #1983: 1: Success after binutils/gcc: 19 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 (2e1f936075) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (d0 [...] 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 1664 -> 1656 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 52772 -> 52256 bytes 04-build_abe-gcc/console.log.xz | Bin 235572 -> 234636 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3880 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2768 -> 2668 bytes 07-check_regression/console.log.xz | Bin 5704 -> 5216 bytes 07-check_regression/extra-bisect-params | 1 - 07-check_regression/fails.sum | 7 - 07-check_regression/mail-body.txt | 62 +- 07-check_regression/results.compare | 37 +- 07-check_regression/results.compare2 | 77 +- 07-check_regression/results.regressions | 41 - 08-update_baseline/console.log | 44 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/mail-body.txt | 62 +- manifest.sh | 20 +- results | 41 - sumfiles/g++.log.xz | Bin 2864056 -> 2826420 bytes sumfiles/g++.sum | 130 +- sumfiles/gcc.log.xz | Bin 2387560 -> 2413260 bytes sumfiles/gcc.sum | 5352 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 913384 -> 906868 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2172 -> 2176 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 216392 -> 216476 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2536 -> 2532 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 471608 -> 474912 bytes sumfiles/libstdc++.sum | 10 +- 34 files changed, 2878 insertions(+), 3080 deletions(-) delete mode 100644 07-check_regression/extra-bisect-params delete mode 100644 07-check_regression/fails.sum delete mode 100644 07-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_gnu_native_build/master-arm updated (fb704aac4a -> 1b08522441)

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_build/master-arm in repository toolchain/ci/base-artifacts. discards fb704aac4a 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 commits discards a1a04017c8 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 commits discards 48e637f610 121: onsuccess: #530: 6: Success after binutils/gcc/linux/gl [...] discards cb2d9ad4fc 120: onsuccess: #529: 6: Success after binutils/gcc/linux/gd [...] discards be35f6e168 119: onsuccess: #528: 6: Success after binutils/gcc/linux/gd [...] discards f2263040d9 118: onsuccess: #527: 6: Success after binutils/gcc/linux/gl [...] discards fd4f7f18a5 117: onsuccess: #526: 6: Success after binutils/gcc/linux/gd [...] discards b54299b675 116: onsuccess: #525: 6: Success after binutils/gcc/linux/gd [...] discards fea4cf21a3 115: onsuccess: #524: 6: Success after binutils/gcc/linux/gl [...] discards a336d6a76e 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits discards cac3f367d7 113: onsuccess: #522: 1: Success after gcc: 12 commits discards 731c26c560 112: force: #521: 1: Failure after basepoints/gcc-13-3918-gb [...] discards 7d80c47265 111: force: #520: 6: Success after gcc: 9 commits discards 8f2a9b411f 110: onsuccess: #518: 6: Success after binutils: 5 commits discards 4a6b912add 109: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] discards 49040fcaba 108: onsuccess: #514: 6: Success after binutils/gcc/linux/gl [...] discards 143c8bc4ff 107: onsuccess: #513: 6: Success after binutils/gcc/linux/gl [...] discards 9ac8c845c9 106: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] discards 7947e3f24d 105: onsuccess: #511: 6: Success after binutils/gcc/linux/gd [...] discards 996be10fae 104: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] discards 28310684f9 103: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] discards ee67810b8c 102: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] discards f1bfb87b21 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] discards d0cad4c032 100: onsuccess: #506: 4: Success after baseline build: no ne [...] discards 1657378148 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] discards 44e794c433 98: force: #504: 6: Success after gcc: 18 commits discards 0c8ec3d523 97: onsuccess: #503: 6: Success after linux: 11 commits discards d8da99dd9c 96: onsuccess: #502: 6: Success after glibc: 10 commits discards f92a003951 95: onsuccess: #500: 6: Success after binutils: 8 commits discards 4a5fe44aa5 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] discards 4fd082cadd 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] discards e515628048 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] discards 058b60fda3 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] discards 4724f638b8 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] discards 03ffb5288b 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] discards edf2cd1dff 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] discards 0d3534d545 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] discards 4f292abf57 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] discards cc3b4dacfe 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] discards 2f85a0e90d 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] discards cda273193f 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] discards e803762e46 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] discards 46fc088198 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] discards 1b7485a8c3 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] discards 7c6deb26e9 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] discards 0b248e85a2 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] discards 39f34bdabc 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] discards 26a0ef4b7b 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gli [...] discards 3593696ab1 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gli [...] discards d98d4947e6 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] discards 1ba534536b 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] discards 8cdd175bba 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] discards 9766b26769 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gdb [...] discards c071c98b00 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] discards 3598940ee0 69: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] discards c1ffda0c7c 68: onsuccess: #471: 6: Success after binutils/gcc/linux/gli [...] discards 9aa4f7825c 67: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] discards 5e521ce60b 66: onsuccess: #469: 6: Success after binutils/gcc/linux/gli [...] discards caf78b7f09 65: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] discards eb0d8a08bc 64: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] discards ec88d8ffc4 63: onsuccess: #466: 6: Success after binutils/gcc/linux/gli [...] discards 47c013ef89 62: onsuccess: #465: 1: Success after binutils/gcc: 27 commits discards 57e8b8bf39 61: onsuccess: #464: 1: Success after binutils/gcc: 30 commits discards 4360d18d18 60: onsuccess: #463: 1: Success after gcc: 10 commits discards 785322171a 59: force: #462: 1: Failure after basepoints/gcc-13-2871-g1b [...] discards 0bd420647a 58: force: #461: 6: Success after gcc: 29 commits discards 5de105eee9 57: onsuccess: #459: 6: Success after binutils: 8 commits discards edf80f1a29 56: onsuccess: #457: 6: Success after binutils/gcc/linux/gdb [...] discards f205c03be9 55: onsuccess: #456: 6: Success after binutils/gcc/linux/gdb [...] discards ad3845a689 54: onsuccess: #455: 6: Success after binutils/gcc/linux/gli [...] discards 682eb6c0a0 53: onsuccess: #454: 6: Success after binutils/gcc/glibc/gdb [...] discards f15d48938a 52: onsuccess: #453: 6: Success after binutils/gcc/linux/gli [...] discards 5cee5694e9 51: onsuccess: #452: 6: Success after binutils/gcc/glibc/gdb [...] discards 29ecd53201 50: onsuccess: #451: 6: Success after binutils/gcc/linux/gli [...] discards 772de48309 49: onsuccess: #450: 6: Success after binutils/gcc/linux/gli [...] discards 8c09b4d1a9 48: onsuccess: #449: 6: Success after binutils/gcc/linux/gli [...] discards ce99594304 47: onsuccess: #448: 4: Success after binutils/gcc/linux/gli [...] discards 68d4ee2a50 46: onsuccess: #447: 4: Success after binutils/gcc: 19 commits discards 3665f7dd54 45: onsuccess: #446: 4: Success after gcc: 13 commits discards ef7a51684d 44: force: #445: 4: Failure after basepoints/gcc-13-2658-g64 [...] discards 844be24d69 43: force: #444: 6: Success after gcc: 5 commits discards 371d841110 42: onsuccess: #443: 6: Success after v6.0-rc5-25-g3245cb65f [...] discards 7a35444eca 41: onsuccess: #442: 6: Success after glibc: 3 commits discards 96d526d21e 40: onsuccess: #440: 6: Success after binutils: 11 commits discards c539f43196 39: onsuccess: #438: 6: Success after binutils/gcc/linux/gli [...] discards 639226a9b9 38: onsuccess: #437: 6: Success after binutils/gcc/linux/gdb [...] discards 24b8f6b9e1 37: onsuccess: #436: 6: Success after binutils/gcc/linux/gli [...] discards d97dff999f 36: onsuccess: #435: 6: Success after binutils/gcc/linux/gdb [...] discards 8a41474f71 35: onsuccess: #434: 6: Success after binutils/gcc/linux/gli [...] discards a3edad9379 34: onsuccess: #433: 6: Success after binutils/gcc/linux/gli [...] discards 48301f7ed3 33: onsuccess: #432: 6: Success after binutils/gcc/linux/gdb [...] discards 3c4f15a865 32: onsuccess: #431: 6: Success after binutils/gcc/linux/gli [...] discards 0c4af1c4dd 31: onsuccess: #430: 6: Success after binutils/gcc/linux/gli [...] discards 7d7a6a0e0d 30: onsuccess: #428: 6: Success after binutils/gcc/linux/gdb [...] discards b1d27209d4 29: onsuccess: 6: Success after binutils/gcc/linux/gdb: 117 commits discards 076c1999a8 28: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] discards a794bc14fb 27: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] discards 5e1f7c8c45 26: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards b70ce2e391 25: onsuccess: 6: Successful build after linux: 72 commits discards 0764b38483 24: onsuccess: 6: Successful build after binutils: Automatic [...] discards aee3d3f858 23: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new f8dfe575ce 23: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 469469b271 24: onsuccess: 6: Successful build after binutils: Automatic [...] new b053f6e984 25: onsuccess: 6: Successful build after linux: 72 commits new 53a3dc87dd 26: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 3a962f1f58 27: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] new f12a67b3ad 28: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] new 32bba5e981 29: onsuccess: 6: Success after binutils/gcc/linux/gdb: 117 commits new 7678df0894 30: onsuccess: #428: 6: Success after binutils/gcc/linux/gdb [...] new f1c84d4ad3 31: onsuccess: #430: 6: Success after binutils/gcc/linux/gli [...] new 74a1f12967 32: onsuccess: #431: 6: Success after binutils/gcc/linux/gli [...] new 1702278523 33: onsuccess: #432: 6: Success after binutils/gcc/linux/gdb [...] new d191e08095 34: onsuccess: #433: 6: Success after binutils/gcc/linux/gli [...] new c60704b835 35: onsuccess: #434: 6: Success after binutils/gcc/linux/gli [...] new 2a13f39590 36: onsuccess: #435: 6: Success after binutils/gcc/linux/gdb [...] new a9d12c4624 37: onsuccess: #436: 6: Success after binutils/gcc/linux/gli [...] new cd6b6e6950 38: onsuccess: #437: 6: Success after binutils/gcc/linux/gdb [...] new 69b6c4fb4b 39: onsuccess: #438: 6: Success after binutils/gcc/linux/gli [...] new a7cc1f1e58 40: onsuccess: #440: 6: Success after binutils: 11 commits new eb48e75c69 41: onsuccess: #442: 6: Success after glibc: 3 commits new 5a115cd24c 42: onsuccess: #443: 6: Success after v6.0-rc5-25-g3245cb65f [...] new 922737040d 43: force: #444: 6: Success after gcc: 5 commits new 2ea42bb75e 44: force: #445: 4: Failure after basepoints/gcc-13-2658-g64 [...] new ebc5ad6872 45: onsuccess: #446: 4: Success after gcc: 13 commits new 9ba67eaaaf 46: onsuccess: #447: 4: Success after binutils/gcc: 19 commits new 69ca664c29 47: onsuccess: #448: 4: Success after binutils/gcc/linux/gli [...] new 8885d5a2b6 48: onsuccess: #449: 6: Success after binutils/gcc/linux/gli [...] new 211d942f2b 49: onsuccess: #450: 6: Success after binutils/gcc/linux/gli [...] new 6293594232 50: onsuccess: #451: 6: Success after binutils/gcc/linux/gli [...] new 383d5ee820 51: onsuccess: #452: 6: Success after binutils/gcc/glibc/gdb [...] new e55b954d26 52: onsuccess: #453: 6: Success after binutils/gcc/linux/gli [...] new 3f16683874 53: onsuccess: #454: 6: Success after binutils/gcc/glibc/gdb [...] new b798ca9d9e 54: onsuccess: #455: 6: Success after binutils/gcc/linux/gli [...] new eeada618f6 55: onsuccess: #456: 6: Success after binutils/gcc/linux/gdb [...] new dfa1e50da6 56: onsuccess: #457: 6: Success after binutils/gcc/linux/gdb [...] new d3b6e991eb 57: onsuccess: #459: 6: Success after binutils: 8 commits new e98a9ebda8 58: force: #461: 6: Success after gcc: 29 commits new ed39c5e53a 59: force: #462: 1: Failure after basepoints/gcc-13-2871-g1b [...] new 755514c877 60: onsuccess: #463: 1: Success after gcc: 10 commits new 2331d84e31 61: onsuccess: #464: 1: Success after binutils/gcc: 30 commits new cec5db7346 62: onsuccess: #465: 1: Success after binutils/gcc: 27 commits new 249e7b78e0 63: onsuccess: #466: 6: Success after binutils/gcc/linux/gli [...] new 07dbf2ac99 64: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] new 0e0ed44686 65: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] new 7df91abcb2 66: onsuccess: #469: 6: Success after binutils/gcc/linux/gli [...] new 3ad25ca03a 67: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] new 0a6e65f532 68: onsuccess: #471: 6: Success after binutils/gcc/linux/gli [...] new b525fbb54a 69: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] new 3e888190ab 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] new 53e177dbbf 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gdb [...] new 62ee7f0a7b 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] new 71c71d63d5 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] new 9a3a7fc228 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] new df65449540 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gli [...] new 16e77331fb 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gli [...] new 9c6cde4517 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] new b18a91a462 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] new ea25b46882 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] new 6c2b68cde9 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] new 98d760c57f 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] new acda5a8470 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] new d837fd4e2e 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] new 7b01b6f2c4 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] new a81ae73773 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] new e4f93d24fa 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] new f53b3eb957 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] new e0b0dbd158 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] new 9dd99cadfc 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] new 78aadbd6f1 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] new 67022e775a 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] new b51f97d057 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] new 3623b57943 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] new 7276e5717e 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] new b267fd6e65 95: onsuccess: #500: 6: Success after binutils: 8 commits new 4cec5b29a7 96: onsuccess: #502: 6: Success after glibc: 10 commits new 94fbf97c76 97: onsuccess: #503: 6: Success after linux: 11 commits new 312f911cd0 98: force: #504: 6: Success after gcc: 18 commits new 9f9408f355 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] new 4bfe0f1798 100: onsuccess: #506: 4: Success after baseline build: no ne [...] new e8ed4caeab 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] new 248ffc4af2 102: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] new 8e8ddf8b8e 103: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] new 632d4584ed 104: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] new 588e1d7b90 105: onsuccess: #511: 6: Success after binutils/gcc/linux/gd [...] new 40f7a2588d 106: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] new d0e28f3c1d 107: onsuccess: #513: 6: Success after binutils/gcc/linux/gl [...] new 6dfef19eb2 108: onsuccess: #514: 6: Success after binutils/gcc/linux/gl [...] new a23e5b2c90 109: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] new e360b73cf1 110: onsuccess: #518: 6: Success after binutils: 5 commits new 5262f3287d 111: force: #520: 6: Success after gcc: 9 commits new 3a8287cd73 112: force: #521: 1: Failure after basepoints/gcc-13-3918-gb [...] new d5c8c17c87 113: onsuccess: #522: 1: Success after gcc: 12 commits new 422eead596 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits new b14b64c668 115: onsuccess: #524: 6: Success after binutils/gcc/linux/gl [...] new 48f3c3418d 116: onsuccess: #525: 6: Success after binutils/gcc/linux/gd [...] new df507c7475 117: onsuccess: #526: 6: Success after binutils/gcc/linux/gd [...] new 9747208296 118: onsuccess: #527: 6: Success after binutils/gcc/linux/gl [...] new 9786df9101 119: onsuccess: #528: 6: Success after binutils/gcc/linux/gd [...] new 0463de5314 120: onsuccess: #529: 6: Success after binutils/gcc/linux/gd [...] new 080e0531fb 121: onsuccess: #530: 6: Success after binutils/gcc/linux/gl [...] new b03dbc3240 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 commits new 0feb9901af 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 commits new 1b08522441 124: onsuccess: #533: 6: Success after binutils/gcc/linux/gd [...] 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 (fb704aac4a) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...] 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 1692 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 53824 -> 52220 bytes 05-build_abe-gcc/console.log.xz | Bin 234332 -> 233804 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 8316 -> 8568 bytes 08-build_abe-glibc/console.log.xz | Bin 235096 -> 236112 bytes 09-build_abe-gdb/console.log.xz | Bin 51992 -> 50944 bytes 10-check_regression/console.log.xz | Bin 3632 -> 4020 bytes 11-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++---------- 19 files changed, 57 insertions(+), 57 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