Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (7644fa5b624 -> b8b55c64d02)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm in repository toolchain/ci/base-artifacts. discards 7644fa5b624 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards abc92ec2ce4 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards 3d1f97d28c4 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards b8911df6dd9 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 2802c371ba1 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 51b0b522aaa 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards b896d0247d3 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards e4b41b51b4d 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards f4fddf5e40f 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 4f0a600fe5b 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 8025582d77c 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards 54d36940187 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards db28f693044 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards 118c3b94aaf 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards 8d6e7598256 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards ca4d9145bff 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards b79d6566ec8 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards fc70f18f031 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] discards 5d672d11162 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] discards 62001339582 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] discards e6f4224e1c4 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] discards b0c24aba53e 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] discards 2c35bfcad76 107: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] discards ac6a59ac20c 106: onsuccess: #532: 1: Success after binutils/gcc/linux/g [...] discards 54b52327dc8 105: onsuccess: #531: 1: Success after binutils/gcc/linux/g [...] discards 2efe3a59af5 104: onsuccess: #530: 1: Success after gcc: 7 commits discards 9226bd359ea 103: onsuccess: #529: 1: Success after binutils/gcc/linux/g [...] discards 10d31f93603 102: onsuccess: #527: 1: Success after binutils: 5 commits discards e2696d7b30d 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 7b912fbba60 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 649dd48cf5c 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] discards bed41f5914f 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gl [...] discards fddf108d1be 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] discards 13cb11ba860 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] discards 4ebeb85eb03 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gd [...] discards c98bed07a96 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gd [...] discards 0426eca7439 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] discards a911ba249f1 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gl [...] discards 5c36cfbdc2f 91: onsuccess: #511: 1: Success after linux: 27 commits discards 9123a311fba 90: onsuccess: #510: 1: Success after glibc: 5 commits discards eb6027ae77a 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 250c4318e1a 88: onsuccess: #506: 1: Success after linux: 34 commits discards 47ff28d2415 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 37088fa76ed 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 91e6334772a 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards e4aed33110a 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] discards f8b991eefe5 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gd [...] discards 4f49fb70324 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gl [...] discards fb1cd0588f1 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards e9759394596 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards 3c1d25a400c 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] discards c26e69775c0 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] discards 37d3fd1eb53 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gd [...] discards 475588c82c3 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gd [...] discards a59915b2959 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] discards 0a44ad45e40 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gl [...] discards 68f1c3a962e 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gd [...] discards dcd0f0a5a98 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gl [...] discards 0196c034d74 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gd [...] discards 9f686243bd1 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gl [...] discards 5f21d6b7308 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] discards 388603cc66b 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gl [...] discards 26a973c06e5 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] discards 6c7fd5bcf51 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gl [...] discards e76f894304c 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gd [...] discards dc5053d6092 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] discards 3841d96cd09 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gl [...] discards 856e6506e77 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gl [...] discards 9536a312f65 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gl [...] discards 07e2aca85ab 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gl [...] discards 74d8b2d82c0 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gl [...] discards 094cc1e1fe8 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gl [...] discards 38af421675b 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gl [...] discards 32c1a846ac1 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gd [...] discards a1d573cca0c 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gl [...] discards 0d50f756413 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gl [...] discards d691c33e2eb 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gl [...] discards 77d88a84ebf 52: onsuccess: #467: 1: Success after binutils: 9 commits discards 6e9d6cbcf5a 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 0f85ddde281 50: onsuccess: #461: 1: Success after binutils: 12 commits discards 5b8d1cce714 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gd [...] discards d85ef5131a8 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gd [...] discards f36c1b80c40 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gl [...] discards 6041d271a83 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gl [...] discards c84085ad7d8 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gl [...] discards 44d6fb6ad17 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gd [...] discards 31d256598df 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gd [...] discards 10bb9bcf452 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gd [...] discards 94a32a974d5 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gl [...] discards 0eb88dc2cef 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g [...] discards 4c67cc5392a 39: onsuccess: #447: 1: Success after binutils: 5 commits discards 1ed044adef3 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g [...] discards f770ef31530 37: onsuccess: #443: 1: Success after binutils: 2 commits discards cd2a4cc66d6 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gl [...] discards 1b59081e932 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gl [...] discards 810e67dc874 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gl [...] discards e109459a076 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gd [...] discards 2c9894e42c1 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gl [...] discards 3cfdce437be 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gl [...] discards d1bc3030328 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gd [...] discards b02c0a2a88c 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gl [...] new e6973ccc3ec 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gl [...] new 64579088d41 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gd [...] new 54fbae2e762 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gl [...] new 25461abb6df 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gl [...] new d65dc980400 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gd [...] new 688f7677eb4 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gl [...] new 19991ed7053 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gl [...] new 146204a4960 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gl [...] new 1277e2eed2a 37: onsuccess: #443: 1: Success after binutils: 2 commits new 9d412089dbe 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g [...] new a39b79142df 39: onsuccess: #447: 1: Success after binutils: 5 commits new db0ab6363c7 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g [...] new 4969bf8c8e2 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gl [...] new 6531c4a7354 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gd [...] new b222d6cf43d 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gd [...] new 4a320eab2a5 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gd [...] new 629d9da34b7 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gl [...] new b63b5d68bed 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gl [...] new 7150a964db9 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gl [...] new eb64747ff89 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gd [...] new 26d502b2fb6 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gd [...] new 1d5e5589c0b 50: onsuccess: #461: 1: Success after binutils: 12 commits new 8127c01720a 51: onsuccess: #464: 1: Success after binutils: 6 commits new 2f86f9d9e18 52: onsuccess: #467: 1: Success after binutils: 9 commits new 6b0acdb42e0 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gl [...] new ece988aa8d0 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gl [...] new 48c044aa565 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gl [...] new e74515a8fdb 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gd [...] new be644c4b0fe 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gl [...] new 41fa2d4adbd 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gl [...] new 1abb1212b4b 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gl [...] new e8a151ff2cc 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gl [...] new 090c4cdacd4 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gl [...] new ebb0bd3a0d1 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gl [...] new b31d529806e 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gl [...] new 9e3e4648254 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] new aca06e1ae05 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gd [...] new 14d3aefd315 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gl [...] new 6dbec0e924f 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] new 92fff65cf80 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gl [...] new f8acf1aea60 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] new 63e0a9ddeaf 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gl [...] new dd57802f150 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gd [...] new 837587e36c9 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gl [...] new 0798ddfe4b9 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gd [...] new d96c5e623f9 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gl [...] new 33df50fccea 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] new 2c3a5b0065f 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gd [...] new 79c4cb42cf3 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gd [...] new 9c2a6e28bb9 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] new d1c799df2e9 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] new 643ef70dc23 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new e9986713333 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new f1533ba8a94 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gl [...] new 5675dc84096 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gd [...] new e1b3eb9b684 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] new 0e11f197bfd 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new 7053fc31fda 86: onsuccess: #503: 1: Success after binutils: 12 commits new f5a96b9cdcd 87: onsuccess: #505: 1: Success after glibc: 7 commits new 4d85293dd56 88: onsuccess: #506: 1: Success after linux: 34 commits new 8a5d3975da6 89: onsuccess: #508: 1: Success after binutils: 12 commits new be21f6559b0 90: onsuccess: #510: 1: Success after glibc: 5 commits new 1dc56bf86a3 91: onsuccess: #511: 1: Success after linux: 27 commits new 523b07c17e2 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gl [...] new dfbf2007f22 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] new 21146357f4d 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gd [...] new bb49470920d 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gd [...] new 29e3ba870ff 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] new 7cec560d831 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] new e2581ea3276 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gl [...] new 72186876015 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] new 720f08b37ce 100: onsuccess: #521: 1: Success after binutils: 10 commits new 38f37d10d64 101: onsuccess: #524: 1: Success after binutils: 2 commits new 1e933842e71 102: onsuccess: #527: 1: Success after binutils: 5 commits new 9e92b07e77f 103: onsuccess: #529: 1: Success after binutils/gcc/linux/g [...] new 2f4fc5f33e1 104: onsuccess: #530: 1: Success after gcc: 7 commits new f33533aef5a 105: onsuccess: #531: 1: Success after binutils/gcc/linux/g [...] new 16b1035083a 106: onsuccess: #532: 1: Success after binutils/gcc/linux/g [...] new 6ab9113adce 107: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] new 3fc71ffd1bd 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] new d48c0362b28 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] new 58247b3d587 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] new 87812e4c383 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] new e8be2447332 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new 3cb47573cd8 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new dd8d299aa1d 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new 1e3b2c29123 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new 4c0db927a6d 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new d3a48f82909 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new e5180cc9e5b 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 77297420309 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new b782d067acb 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 3a95ae57d4d 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 6c5a3cdf03a 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 728e18e6d50 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new 7685dbed0f6 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 2d399b40687 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 6c4b6e3c617 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 6ea584978ff 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new cac14692472 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 961421a46ad 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new b8b55c64d02 130: onsuccess: #557: 1: 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 (7644fa5b624) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1724 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 52248 -> 54252 bytes 04-build_abe-gcc/console.log.xz | Bin 233660 -> 234116 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8300 -> 9392 bytes 07-build_abe-glibc/console.log.xz | Bin 235280 -> 234760 bytes 08-build_abe-gdb/console.log.xz | Bin 50928 -> 52260 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3812 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2164 -> 2544 bytes 11-check_regression/console.log.xz | Bin 5780 -> 6196 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 38 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +-- sumfiles/binutils.log.xz | Bin 62588 -> 62584 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 98068 -> 100400 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 131536 -> 131524 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 30 files changed, 393 insertions(+), 393 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 updated (5f0086d8c85 -> b4db6ef172c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. discards 5f0086d8c85 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 89dc8463e26 120: onsuccess: #906: 1: Success after binutils: 29 commits discards ebec379df26 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 0436a6d429b 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards 758e7ae794f 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 5d96a34065f 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards 33cabbbd02f 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards 5a77460876d 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards adf6f365723 113: onsuccess: #898: 1: Success after linux: 3 commits discards 15c28704dc7 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 7d219d01d47 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards ee036961aef 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 73bf7ddd55e 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards 4badecb2961 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 897520f62d9 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 90a2d903ef2 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 30701784059 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards d5024257414 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 2cdb2351a38 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 236ec7ea235 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards 3d30a88ed55 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards acc05e4d012 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 989c564a518 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 6ec8e6b2228 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] discards c09dc9d2d88 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] discards 4a0cafab124 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] discards 6fa9c27677f 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] discards 38e27e9315d 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] discards 146386d2ea1 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] discards ffadbb23fbd 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] discards 08560fb2b2a 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 98bf0199157 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 40ffc9b2c80 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 97509fe0d52 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] discards 4d9c2bda4b9 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] discards 5a473017cf4 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] discards 0dbcf2e1434 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] discards 36dedbfd5d0 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] discards df65491b8d8 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] discards 523f8b56847 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] discards d452d10667d 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 4d49b1b5852 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 497e23d7071 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 57eb331657a 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] discards ffc511d8dc8 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] discards 5955b1b223c 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] discards 57f7bb2f416 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] discards 1e82d4b6b8c 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] discards 1d90fd36ff7 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] discards 3854e619c19 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] discards c57bf026003 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] discards f1ff5eb4a0c 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] discards aaaca6c80b1 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] discards bdce056d614 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 2a8b22dee2f 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] discards b9d203400b4 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] discards ca783be11d8 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards ee55230920e 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] discards 6b31f069318 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] discards 2c41b57fedd 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] discards 749d83f6904 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] discards c7ef276a217 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] discards c1e46e10a5d 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] discards c16e1e0d559 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] discards e682e1604c2 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] discards d55b5201618 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards e9bdec05789 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 63deb501a80 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards b45d4ddadec 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards fbf823f2a0a 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards a04bfc6efbd 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards edd125336ef 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] discards 90b27cb5c06 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards b1e6d9c1455 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 2f9dfc8beeb 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards a4203360dcf 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 4c280e199f5 45: onsuccess: #815: 1: Success after binutils: 6 commits discards d7e1eb0ea70 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards f4954688cb8 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] discards ce95236926d 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 581e438c1de 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] discards 33fa7383ce1 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] discards 2926f2391ed 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 6b95852e74c 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] discards f772fea8f88 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] discards 6132ba97578 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] discards f9d70e0df1c 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 943a8c52135 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] discards 9e5fb3e978c 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards c7e74e7b23e 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 2a57c42ac93 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] discards a26448a710d 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 96349960dad 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] discards 9271a44c207 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards a0ae0b4b987 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] discards b3a757e503a 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] discards 5ebc5be6aad 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 46ce2168eb1 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards b25858bf1be 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] discards b775e8a527a 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] discards 5f284d0d6d1 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] new 2f9e27ea649 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] new f87daa07b40 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] new 03ffdbf9ac7 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] new 1de0d2c7efd 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new c127bfb5376 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new e589a2e7ce8 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] new fd374b5fd9f 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] new 9fbaae72a74 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 2177f645755 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] new c5b2d4f4868 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new cf450d5466d 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] new 28203277767 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 198f538161c 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new fae629941d6 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] new cb86af264c6 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new b51e9bf785f 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] new 719dff9c87a 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] new 832db14453d 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] new 04aa20cee7d 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 12537bedd7b 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] new 6df8bc54b87 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] new 6fcfefd4d1f 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new f6367b351ea 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] new f5eddae75c6 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new aea62e9ff13 45: onsuccess: #815: 1: Success after binutils: 6 commits new 1cdee43c7a5 46: onsuccess: #818: 1: Success after binutils: 10 commits new aa5473073ad 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new fdd8eab1bc7 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new b8ebbb7e940 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 5242fc7dc49 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] new a963805df66 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 467ca3efab8 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 740b6ae86d7 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new ced550a3e6e 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new e5ad7a046e4 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 703a455d8f0 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 62a89001e7f 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] new f02bc30540d 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] new acc332c2480 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] new 5afde210a32 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] new 22cdc92d568 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] new 49c8bab2591 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] new 72ab51f73fe 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] new 52f85dbbee0 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] new 3adca640f40 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 07d5ca83caa 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] new 332e162e886 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] new ef6e99e8720 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 6f9c68172e2 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] new 6ade667d860 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] new c16239c115a 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] new e0d2a994785 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] new 39426617120 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] new 35857718450 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] new 8392ab9bced 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] new b8d92aa6136 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] new c9fba1980ab 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] new 9db24e7741a 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] new fa6db29df3f 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 3691154d2e0 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 2059f510e1c 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 3be95eb7035 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] new fd320b420ed 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] new 74441ab6bec 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] new 73d46c078bd 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] new 73f8df6df60 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] new 4b182094900 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] new 3d4c7a483f8 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] new fb6a5cca091 89: onsuccess: #864: 1: Success after binutils: 25 commits new f35e80b7ddd 90: onsuccess: #867: 1: Success after binutils: 4 commits new 1c69e817bf0 91: onsuccess: #870: 1: Success after binutils: 5 commits new 24f9968fba4 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] new 7880959bb64 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] new fd5543767bf 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] new f7c265b111b 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] new bfb935c0704 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] new b7266caeea8 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] new 5970e712bd7 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] new 7c376090559 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 01c76d6444a 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 3adb3bacab0 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new df0f1cf143f 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 23458dd6a1f 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 3e7d21c1ec5 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 04edcda9646 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 6edf5fc0b30 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new a43c6db7e74 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new ccbb58e2659 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 83c649ac50c 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new f1207b3640f 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new c6682bb83d0 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new fdc3616ebb4 112: onsuccess: #896: 1: Success after binutils: 24 commits new de2d5018402 113: onsuccess: #898: 1: Success after linux: 3 commits new ebf5e903bc6 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new c7f29f2e7fc 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new 1754cbc45b5 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new 7a93a85cf4a 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new f2f74bbbbbd 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new 8f6b0eae5ed 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 1f23af32156 120: onsuccess: #906: 1: Success after binutils: 29 commits new 44a3d78503a 121: onsuccess: #908: 1: Success after glibc: 2 commits new b4db6ef172c 122: onsuccess: #909: 1: Success after linux: 2753 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 (5f0086d8c85) \ 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 1680 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 40884 -> 40556 bytes 04-build_abe-gcc/console.log.xz | Bin 216444 -> 217328 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8472 -> 9804 bytes 07-build_abe-glibc/console.log.xz | Bin 244300 -> 245772 bytes 08-build_abe-gdb/console.log.xz | Bin 38936 -> 39520 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3896 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2024 -> 2136 bytes 11-check_regression/console.log.xz | Bin 22700 -> 20152 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 24 +- 11-check_regression/mail-body.txt | 111 +- 11-check_regression/results.compare | 57 +- 11-check_regression/results.compare2 | 1869 ++--- 11-check_regression/results.regressions | 57 +- 12-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 113 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 57 +- sumfiles/gdb.log.xz | Bin 1972392 -> 1930420 bytes sumfiles/gdb.sum | 11042 ++++++------------------------ 27 files changed, 2837 insertions(+), 10563 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/release-aarch64 updated (d61651d34de -> 5b2ace80067)

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/release-aarch64 in repository toolchain/ci/base-artifacts. from d61651d34de 39: onsuccess: #242: 1: Success after binutils/gcc: 8 commits new 5b2ace80067 40: onsuccess: #243: 1: Success after binutils/gcc: 17 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 1720 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 38968 -> 37908 bytes 04-build_abe-gcc/console.log.xz | Bin 208500 -> 207340 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3876 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2412 -> 2404 bytes 07-check_regression/console.log.xz | Bin 5352 -> 5836 bytes 07-check_regression/extra-bisect-params | 2 +- 07-check_regression/fails.sum | 13 +- 07-check_regression/mail-body.txt | 78 +- 07-check_regression/results.compare | 35 +- 07-check_regression/results.compare2 | 108 +- 07-check_regression/results.regressions | 35 +- 08-update_baseline/console.log | 9 - dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 80 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 35 +- sumfiles/g++.log.xz | Bin 3529212 -> 3512488 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 3005832 -> 3018052 bytes sumfiles/gcc.sum | 4685 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1036692 -> 1038824 bytes sumfiles/gfortran.sum | 94 +- sumfiles/libatomic.log.xz | Bin 2192 -> 2192 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202404 -> 202600 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2548 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 438660 -> 431016 bytes sumfiles/libstdc++.sum | 10 +- 36 files changed, 2754 insertions(+), 2624 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap updated (7c083826f6c -> 2abbf562140)

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/master-arm-bootstrap in repository toolchain/ci/base-artifacts. discards 7c083826f6c 408: onsuccess: #1833: 2: Success after binutils/gcc: 6 commits discards 16ca7c2ea86 407: onsuccess: #1832: 2: Success after binutils/gcc: 11 commits discards 2420971928c 406: onsuccess: #1831: 2: Success after binutils/gcc: 24 commits discards 76e7687c5d3 405: onsuccess: #1830: 2: Success after binutils/gcc: 8 commits discards 60d59a0d02e 404: onsuccess: #1829: 2: Success after binutils/gcc: 2 commits discards f07b3e81ec7 403: onsuccess: #1828: 2: Success after gcc: 5 commits discards 436f5966065 402: onsuccess: #1827: 2: Success after binutils/gcc: 5 commits discards a54cb5618ef 401: onsuccess: #1826: 2: Success after binutils/gcc: 3 commits discards e5700a0bc2d 400: onsuccess: #1825: 2: Success after binutils/gcc: 13 commits discards 2888e91090c 399: onsuccess: #1824: 2: Success after binutils: 6 commits discards 2af43665d54 398: onsuccess: #1823: 2: Success after binutils/gcc: 6 commits discards 7490264a44f 397: onsuccess: #1822: 2: Success after basepoints/gcc-13-4 [...] discards f35a6c441ed 396: onsuccess: #1821: 2: Success after binutils/gcc: 13 commits discards f5cfba4b5dc 395: onsuccess: #1820: 2: Success after binutils/gcc: 25 commits discards 4ef21ac4b41 394: onsuccess: #1818: 2: Success after binutils/gcc: 6 commits discards 7303313f9d8 393: onsuccess: #1817: 2: Success after binutils/gcc: 11 commits discards 2ec91300bc1 392: onsuccess: #1816: 2: Success after gcc: 3 commits discards f1c230d3801 391: onsuccess: #1815: 2: Success after binutils/gcc: 6 commits discards 32b3deb93bf 390: onsuccess: #1814: 2: Success after binutils/gcc: 14 commits discards 9ede8797bab 389: onsuccess: #1813: 2: Success after binutils/gcc: 6 commits discards 13bcc70ef94 388: onsuccess: #1812: 2: Success after binutils/gcc: 22 commits discards e36774fc17b 387: onsuccess: #1811: 2: Success after binutils/gcc: 6 commits discards aa599263844 386: onsuccess: #1810: 2: Success after binutils/gcc: 12 commits discards 617d2e7afad 385: onsuccess: #1809: 2: Success after binutils/gcc: 3 commits discards 858782d236f 384: onsuccess: #1808: 2: Success after binutils/gcc: 15 commits discards b3cf632b882 383: onsuccess: #1807: 2: Success after binutils/gcc: 4 commits discards 1c8b563de1d 382: onsuccess: #1806: 2: Success after binutils/gcc: 5 commits discards 55175da08ba 381: onsuccess: #1805: 2: Success after gcc: 5 commits discards e3e857f7d89 380: onsuccess: #1804: 2: Success after gcc: 3 commits discards 9fdf5d17b08 379: onsuccess: #1803: 2: Success after binutils/gcc: 2 commits discards f162d7b7127 378: onsuccess: #1802: 2: Success after binutils/gcc: 4 commits discards f2ed51166c0 377: onsuccess: #1801: 2: Success after binutils/gcc: 7 commits discards 45b414208e3 376: onsuccess: #1800: 2: Success after binutils/gcc: 15 commits discards f615271822a 375: onsuccess: #1798: 2: Success after binutils/gcc: 7 commits discards 296cfecf925 374: onsuccess: #1797: 2: Success after binutils/gcc: 6 commits discards 9368a1e9c8f 373: onsuccess: #1796: 2: Success after binutils/gcc: 19 commits discards 313a2a25038 372: onsuccess: #1795: 2: Success after binutils/gcc: 16 commits discards 90c3c04e1d3 371: onsuccess: #1794: 2: Success after binutils/gcc: 6 commits discards c2f3d1b4937 370: onsuccess: #1793: 2: Success after binutils/gcc: 16 commits discards 82d1589a2c8 369: onsuccess: #1792: 2: Success after binutils/gcc: 12 commits discards df65e245969 368: onsuccess: #1791: 2: Success after binutils/gcc: 13 commits discards fe509b72f88 367: onsuccess: #1790: 2: Success after binutils/gcc: 9 commits discards d0c37ee18f6 366: onsuccess: #1789: 2: Success after binutils/gcc: 8 commits discards 8ed8ed3ef91 365: onsuccess: #1788: 2: Success after binutils/gcc: 7 commits discards fe3a6a4d56d 364: onsuccess: #1787: 2: Success after gcc: 6 commits discards 2842abb7d42 363: onsuccess: #1786: 2: Success after binutils/gcc: 3 commits discards 7f905ac2bff 362: onsuccess: #1785: 2: Success after binutils/gcc: 19 commits discards 561eadfbc8b 361: onsuccess: #1784: 2: Success after binutils/gcc: 31 commits discards c2268216938 360: onsuccess: #1783: 1: Success after binutils/gcc: 62 commits discards ff5f498262d 359: onsuccess: #1782: 1: Success after basepoints/gcc-13-4 [...] discards 85edac9430e 358: onsuccess: #1781: 1: Success after binutils/gcc: 8 commits discards eee5b90128a 357: onsuccess: #1780: 1: Success after binutils: 3 commits discards 4d99b0c9e7a 356: onsuccess: #1779: 1: Success after gdb-12-branchpoint- [...] discards c49ed004980 355: onsuccess: #1778: 1: Success after binutils/gcc: 2 commits discards e79eafebada 354: onsuccess: #1777: 1: Success after basepoints/gcc-13-4 [...] discards 23376e763e6 353: onsuccess: #1776: 1: Success after binutils: 4 commits discards 6af2b8b2e82 352: onsuccess: #1775: 1: Success after binutils/gcc: 124 commits discards 8134cbdca85 351: onsuccess: #1774: 1: Success after gcc: 8 commits discards e2bd045131c 350: force: #1773: 1: Failure after basepoints/gcc-13-4227- [...] discards 44a96bc5701 349: onsuccess: #1764: 2: Success after binutils: 3 commits discards f57e76a9950 348: onsuccess: #1762: 2: Success after binutils/gcc: 4 commits discards bc694513382 347: onsuccess: #1761: 2: Success after binutils/gcc: 13 commits discards e5c6da5109a 346: onsuccess: #1760: 2: Success after binutils/gcc: 14 commits discards 219fa490410 345: onsuccess: #1759: 2: Success after binutils/gcc: 23 commits discards c6652baecec 344: onsuccess: #1758: 2: Success after gcc: 3 commits discards 6f324dc34f4 343: onsuccess: #1757: 2: Success after binutils/gcc: 5 commits discards 765001477ae 342: onsuccess: #1756: 2: Success after gcc: 4 commits discards 6c819d34d84 341: onsuccess: #1755: 2: Success after binutils/gcc: 3 commits discards 90a09171740 340: onsuccess: #1754: 2: Success after binutils/gcc: 3 commits discards 64e54bee090 339: onsuccess: #1753: 2: Success after binutils/gcc: 7 commits discards f1bc6fddbb2 338: onsuccess: #1752: 2: Success after binutils/gcc: 5 commits discards 20bcde6c2fa 337: onsuccess: #1751: 2: Success after binutils/gcc: 2 commits discards 555e3b803c5 336: onsuccess: #1750: 2: Success after binutils/gcc: 5 commits discards d535b9d49a4 335: onsuccess: #1749: 2: Success after binutils/gcc: 22 commits discards ffa8d14e800 334: onsuccess: #1748: 2: Success after binutils/gcc: 9 commits discards 96813952b05 333: onsuccess: #1747: 2: Success after binutils/gcc: 4 commits discards 6b92998cbe2 332: onsuccess: #1746: 2: Success after binutils/gcc: 6 commits discards 70c20e98a51 331: onsuccess: #1745: 2: Success after binutils/gcc: 14 commits discards 3c8ed5276af 330: onsuccess: #1744: 2: Success after binutils/gcc: 11 commits discards 9298238ef61 329: onsuccess: #1743: 2: Success after binutils/gcc: 7 commits discards cbc73eb2cbf 328: onsuccess: #1742: 2: Success after binutils/gcc: 14 commits discards 12f38fe45ad 327: onsuccess: #1741: 2: Success after binutils/gcc: 12 commits discards da833ca3c6e 326: onsuccess: #1740: 2: Success after binutils/gcc: 19 commits discards 4b3df14e2fd 325: onsuccess: #1739: 2: Success after gcc: 4 commits discards d49e4d6ed7b 324: onsuccess: #1738: 2: Success after binutils/gcc: 18 commits discards 0b6132e653a 323: onsuccess: #1737: 2: Success after binutils/gcc: 84 commits discards e31709cd772 322: onsuccess: #1736: 2: Success after binutils/gcc: 22 commits discards b597f4d5012 321: onsuccess: #1735: 1: Success after binutils/gcc: 54 commits discards 2ec0d7c2a6d 320: onsuccess: #1734: 1: Success after binutils/gcc: 4 commits discards cf6ea12f612 319: onsuccess: #1733: 1: Success after binutils/gcc: 8 commits discards 3f91debb2ae 318: onsuccess: #1732: 1: Success after binutils/gcc: 2 commits discards 4f79ae0d0db 317: onsuccess: #1731: 1: Success after binutils/gcc: 8 commits discards 846f5970a87 316: onsuccess: #1730: 1: Success after binutils/gcc: 16 commits discards 5dc1e053f2f 315: onsuccess: #1729: 1: Success after baseline build: no [...] discards 36842cf3e5c 314: force: #1728: 1: Failure after basepoints/gcc-13-3918- [...] discards 48b2ef324cb 313: force: #1727: 2: Success after gcc: 6 commits discards a703f7cbdad 312: onsuccess: #1724: 2: Success after gdb-12-branchpoint- [...] discards 3ffe28d8620 311: onsuccess: #1722: 2: Success after binutils/gcc: 8 commits discards f3ab359f601 310: onsuccess: #1721: 2: Success after binutils/gcc: 27 commits discards c5a75cd338a 309: onsuccess: #1720: 2: Success after binutils/gcc: 14 commits discards 64245946372 308: onsuccess: #1719: 2: Success after binutils/gcc: 5 commits new 863f0be2ec8 308: onsuccess: #1719: 2: Success after binutils/gcc: 5 commits new ee299d75131 309: onsuccess: #1720: 2: Success after binutils/gcc: 14 commits new a9549d8cd8b 310: onsuccess: #1721: 2: Success after binutils/gcc: 27 commits new c676ead41da 311: onsuccess: #1722: 2: Success after binutils/gcc: 8 commits new 98f2437a48d 312: onsuccess: #1724: 2: Success after gdb-12-branchpoint- [...] new 7bb381ebe6d 313: force: #1727: 2: Success after gcc: 6 commits new 11930f90550 314: force: #1728: 1: Failure after basepoints/gcc-13-3918- [...] new e9b1c17e5db 315: onsuccess: #1729: 1: Success after baseline build: no [...] new bd657e53e75 316: onsuccess: #1730: 1: Success after binutils/gcc: 16 commits new ceccb36938e 317: onsuccess: #1731: 1: Success after binutils/gcc: 8 commits new 1bb3c12433f 318: onsuccess: #1732: 1: Success after binutils/gcc: 2 commits new a926b31cecb 319: onsuccess: #1733: 1: Success after binutils/gcc: 8 commits new 089480dd0b6 320: onsuccess: #1734: 1: Success after binutils/gcc: 4 commits new 8bf86057f1e 321: onsuccess: #1735: 1: Success after binutils/gcc: 54 commits new b5a0064e24c 322: onsuccess: #1736: 2: Success after binutils/gcc: 22 commits new efb4a049568 323: onsuccess: #1737: 2: Success after binutils/gcc: 84 commits new 597160a84bc 324: onsuccess: #1738: 2: Success after binutils/gcc: 18 commits new d2c38cf7a26 325: onsuccess: #1739: 2: Success after gcc: 4 commits new efd22b4c98e 326: onsuccess: #1740: 2: Success after binutils/gcc: 19 commits new 6b885ca9f9a 327: onsuccess: #1741: 2: Success after binutils/gcc: 12 commits new 14cf0fa5a9e 328: onsuccess: #1742: 2: Success after binutils/gcc: 14 commits new b8be94ddbc0 329: onsuccess: #1743: 2: Success after binutils/gcc: 7 commits new 56a13946d3a 330: onsuccess: #1744: 2: Success after binutils/gcc: 11 commits new c035f482f34 331: onsuccess: #1745: 2: Success after binutils/gcc: 14 commits new 17a8bb7d25e 332: onsuccess: #1746: 2: Success after binutils/gcc: 6 commits new ad04b397f2f 333: onsuccess: #1747: 2: Success after binutils/gcc: 4 commits new 28d101a639f 334: onsuccess: #1748: 2: Success after binutils/gcc: 9 commits new b4231ea8aff 335: onsuccess: #1749: 2: Success after binutils/gcc: 22 commits new 0f6bfefe408 336: onsuccess: #1750: 2: Success after binutils/gcc: 5 commits new ceff4a1b444 337: onsuccess: #1751: 2: Success after binutils/gcc: 2 commits new e9b0dd44e23 338: onsuccess: #1752: 2: Success after binutils/gcc: 5 commits new 16064dc18fd 339: onsuccess: #1753: 2: Success after binutils/gcc: 7 commits new a512e833e6b 340: onsuccess: #1754: 2: Success after binutils/gcc: 3 commits new 17125283466 341: onsuccess: #1755: 2: Success after binutils/gcc: 3 commits new 42da08b2e7b 342: onsuccess: #1756: 2: Success after gcc: 4 commits new 4879056d97e 343: onsuccess: #1757: 2: Success after binutils/gcc: 5 commits new 6f663941a43 344: onsuccess: #1758: 2: Success after gcc: 3 commits new 328d2c5d5cb 345: onsuccess: #1759: 2: Success after binutils/gcc: 23 commits new 79bf157d171 346: onsuccess: #1760: 2: Success after binutils/gcc: 14 commits new e21e326bcc1 347: onsuccess: #1761: 2: Success after binutils/gcc: 13 commits new cefab510471 348: onsuccess: #1762: 2: Success after binutils/gcc: 4 commits new fd6b72e5470 349: onsuccess: #1764: 2: Success after binutils: 3 commits new f6cd88f268b 350: force: #1773: 1: Failure after basepoints/gcc-13-4227- [...] new 33348c43205 351: onsuccess: #1774: 1: Success after gcc: 8 commits new edc4385f0ee 352: onsuccess: #1775: 1: Success after binutils/gcc: 124 commits new 00fbf78a194 353: onsuccess: #1776: 1: Success after binutils: 4 commits new c2dab8a1fda 354: onsuccess: #1777: 1: Success after basepoints/gcc-13-4 [...] new e0020d8cef5 355: onsuccess: #1778: 1: Success after binutils/gcc: 2 commits new cda897860df 356: onsuccess: #1779: 1: Success after gdb-12-branchpoint- [...] new c98e834fad2 357: onsuccess: #1780: 1: Success after binutils: 3 commits new daeb699dbe1 358: onsuccess: #1781: 1: Success after binutils/gcc: 8 commits new 34bd668fabb 359: onsuccess: #1782: 1: Success after basepoints/gcc-13-4 [...] new 101d4133c6e 360: onsuccess: #1783: 1: Success after binutils/gcc: 62 commits new 491e54d44b4 361: onsuccess: #1784: 2: Success after binutils/gcc: 31 commits new 698ea6119c8 362: onsuccess: #1785: 2: Success after binutils/gcc: 19 commits new 605e4b5ebb0 363: onsuccess: #1786: 2: Success after binutils/gcc: 3 commits new 9ce927b3432 364: onsuccess: #1787: 2: Success after gcc: 6 commits new a84d8e1f28c 365: onsuccess: #1788: 2: Success after binutils/gcc: 7 commits new 3bdb2601348 366: onsuccess: #1789: 2: Success after binutils/gcc: 8 commits new d30dc721354 367: onsuccess: #1790: 2: Success after binutils/gcc: 9 commits new 21f653bed26 368: onsuccess: #1791: 2: Success after binutils/gcc: 13 commits new 6771131d322 369: onsuccess: #1792: 2: Success after binutils/gcc: 12 commits new 4a23ac59b23 370: onsuccess: #1793: 2: Success after binutils/gcc: 16 commits new 5b91fecef18 371: onsuccess: #1794: 2: Success after binutils/gcc: 6 commits new f045d63ed84 372: onsuccess: #1795: 2: Success after binutils/gcc: 16 commits new 7097b737724 373: onsuccess: #1796: 2: Success after binutils/gcc: 19 commits new 0c0c4cfd671 374: onsuccess: #1797: 2: Success after binutils/gcc: 6 commits new acd84e61bf7 375: onsuccess: #1798: 2: Success after binutils/gcc: 7 commits new 7d0a01db059 376: onsuccess: #1800: 2: Success after binutils/gcc: 15 commits new b05b8c03e85 377: onsuccess: #1801: 2: Success after binutils/gcc: 7 commits new ad274387d2b 378: onsuccess: #1802: 2: Success after binutils/gcc: 4 commits new 5210a9c1db5 379: onsuccess: #1803: 2: Success after binutils/gcc: 2 commits new a67b1ff5658 380: onsuccess: #1804: 2: Success after gcc: 3 commits new 4d68f621a2d 381: onsuccess: #1805: 2: Success after gcc: 5 commits new 9395963e8da 382: onsuccess: #1806: 2: Success after binutils/gcc: 5 commits new b4e88f0d0e8 383: onsuccess: #1807: 2: Success after binutils/gcc: 4 commits new 8c400a530d3 384: onsuccess: #1808: 2: Success after binutils/gcc: 15 commits new ecc7c14b09a 385: onsuccess: #1809: 2: Success after binutils/gcc: 3 commits new c8bf6625c99 386: onsuccess: #1810: 2: Success after binutils/gcc: 12 commits new 891dc93a8cb 387: onsuccess: #1811: 2: Success after binutils/gcc: 6 commits new be04d19d19f 388: onsuccess: #1812: 2: Success after binutils/gcc: 22 commits new 442275d27f7 389: onsuccess: #1813: 2: Success after binutils/gcc: 6 commits new 5c65d23cc5b 390: onsuccess: #1814: 2: Success after binutils/gcc: 14 commits new 3e0d59bda7f 391: onsuccess: #1815: 2: Success after binutils/gcc: 6 commits new fbde027ba7b 392: onsuccess: #1816: 2: Success after gcc: 3 commits new 28da44f5325 393: onsuccess: #1817: 2: Success after binutils/gcc: 11 commits new aea68b0a085 394: onsuccess: #1818: 2: Success after binutils/gcc: 6 commits new e6b6c97e17c 395: onsuccess: #1820: 2: Success after binutils/gcc: 25 commits new 4d3713939df 396: onsuccess: #1821: 2: Success after binutils/gcc: 13 commits new c6be8b205dc 397: onsuccess: #1822: 2: Success after basepoints/gcc-13-4 [...] new 02f938538a3 398: onsuccess: #1823: 2: Success after binutils/gcc: 6 commits new 7c8b5cb7671 399: onsuccess: #1824: 2: Success after binutils: 6 commits new 27b56960081 400: onsuccess: #1825: 2: Success after binutils/gcc: 13 commits new ed145503594 401: onsuccess: #1826: 2: Success after binutils/gcc: 3 commits new e12280ad953 402: onsuccess: #1827: 2: Success after binutils/gcc: 5 commits new f09c417e0f1 403: onsuccess: #1828: 2: Success after gcc: 5 commits new 50a178ffa39 404: onsuccess: #1829: 2: Success after binutils/gcc: 2 commits new a90fa20848f 405: onsuccess: #1830: 2: Success after binutils/gcc: 8 commits new 338dae6ec20 406: onsuccess: #1831: 2: Success after binutils/gcc: 24 commits new 99475072e0e 407: onsuccess: #1832: 2: Success after binutils/gcc: 11 commits new 3b38b75e235 408: onsuccess: #1833: 2: Success after binutils/gcc: 6 commits new 2abbf562140 409: onsuccess: #1834: 2: Success after binutils/gcc: 4 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 (7c083826f6c) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] 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 1716 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 52908 -> 54584 bytes 05-build_abe-bootstrap/console.log.xz | Bin 469008 -> 468020 bytes 06-check_regression/console.log.xz | Bin 2728 -> 2648 bytes 07-update_baseline/console.log | 36 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 ++++++++--------- 13 files changed, 33 insertions(+), 33 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allnoconfig updated (fd365074c6e -> cdeca3422d2)

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-stable-allnoconfig in repository toolchain/ci/base-artifacts. from fd365074c6e 27: onsuccess: #477: boot: Success after binutils/gcc/linux [...] new cdeca3422d2 28: onsuccess: #478: boot: Success after binutils/gcc: 94 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 2032 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31760 -> 32268 bytes 04-build_abe-stage1/console.log.xz | Bin 73256 -> 73264 bytes 05-build_abe-qemu/console.log.xz | Bin 30860 -> 30916 bytes 06-build_linux/console.log.xz | Bin 5612 -> 4924 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4096 -> 3404 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +++++++++++----------- 15 files changed, 17 insertions(+), 17 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (0148f140f86 -> d7f050920d7)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. discards 0148f140f86 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards ddd5de85e2e 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 06d44619500 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards cabf97973d2 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 3209ba3be10 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 9e452f9e63f 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards ecae101fa1d 116: onsuccess: #647: 1: Success after linux: 3 commits discards 0914edb993e 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 5b8a96c25c4 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 33410e3fc50 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 967e9eac633 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 37520ee68ac 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 04a29a3728d 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 2abf080a614 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 30a01084d55 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 7d0fdfe9caf 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 272c09e5b7a 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards c2a0b45ce1c 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 3d2338c9e29 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 43285083fae 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] discards 545ea467e52 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] discards 29a69a99312 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards ec78f6e3cf0 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 25547c278b4 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 0a124ffd5b9 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] discards 772c91b45a3 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards bec0548abcf 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 6e2a468bbc4 95: onsuccess: #619: 1: Success after binutils: 5 commits discards a788c97e7c1 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 0f89b098b8b 93: onsuccess: #613: 1: Success after binutils: 19 commits discards ac05f571e59 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards b88f454caa5 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards 4b196923c97 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 0371a77329f 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] discards 5f1ec5ae754 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] discards ff5b7251a9e 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] discards 5a0b545fb2f 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 9f94230a326 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] discards bdd39ef0056 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 822eb304d54 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 6e799f8c9e7 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] discards c694d442e88 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 51aab7262c7 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards a85d1ac23d9 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 7fe6a0e74fe 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards f549e4229d6 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] discards 5d6fcb4285d 76: onsuccess: #592: 1: Success after linux: 63 commits discards 1ce0af1b34c 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 06b8187fac4 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 6283be7ebde 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards 003eff04049 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] discards e6c3fd27be0 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] discards fd4b78fabcf 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 98cab56be76 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards 98b33fbb426 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards eeeee479d2d 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] discards fcbb12a3694 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards aef00226385 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] discards db44bb5f8e3 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards 4d03e88aca2 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards 22b0d73d160 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 21abe7be7d7 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards a0a0019e0fa 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 24828ffd5bb 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] discards b15534157d1 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] discards 49fda707e77 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] discards 2b2aeda359e 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] discards cbb706427af 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] discards 285e58c05b6 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] discards 56dbeda40cd 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] discards b5c3a61cfda 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards 0a0094a6174 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 7ff981906c1 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards ac69b929e22 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 6dafadc4401 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 39eda2a001f 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 71216640ff6 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] discards a07cff8ae43 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards ce63803d666 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 6e0833ee1ed 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards 2d7aa0a99fe 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 195e878068e 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] discards e3aacf3ce71 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards 1c75bd0ab13 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] discards f469f13ab92 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards ba21419a314 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] discards c00b40ff0af 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards a5e8157810a 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards ccda2538e8d 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards e617f8a6881 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 8d4f5e9054a 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards 06dd3881291 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards c4e3e072b8c 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards 20492bb9d52 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards fbb3581703e 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards 71fbf073269 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 5f666c986ae 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards 5d888b7185e 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] discards fab754a3726 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] discards 7a4b6463ebd 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] discards 2c600e408a5 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 55872510524 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new eb8ce745967 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] new 36f80a3ddba 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] new 60c161eb042 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] new 80897cd1f1d 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 097ce42a209 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new a35670f4bd9 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new cf9adaa5b57 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 4c91566ad06 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new 23cae5747b8 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new 0bd7368b627 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 2a0953685fa 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new c27699b6a0a 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new 9f775600054 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new fbb1f41616b 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 094e25facb6 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] new cbfe0b49990 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new b247a1518fb 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] new fae4ed6c8da 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new 05148eb7956 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] new 26963704a92 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 5f5fa5a4960 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new febf286b901 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 4e5c82ca55e 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new 81910d1ea59 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] new d184a1752b5 47: onsuccess: #556: 1: Success after binutils: 12 commits new d2d4f90899f 48: onsuccess: #559: 1: Success after binutils: 6 commits new 8e43677529a 49: onsuccess: #562: 1: Success after binutils: 9 commits new cf948a99981 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new abd5833e995 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new a8bda0dff99 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new b44406d94bd 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] new 4c05a69d209 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] new 71b74bcf968 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] new 4bc62168469 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] new 621e58be2a4 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] new 6090598a904 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] new 2b0d9c25b8d 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] new 3e32f41a8a8 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new bec691f62e6 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new d9d8073852a 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 227112e9d91 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new 550dedece15 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new 18af4b32648 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] new e9ed271a931 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new 1cf0d393280 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] new 47f3607392f 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 498919013d0 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new b021c597435 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 7db02b2696a 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] new 9fc2f4960a7 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] new 7ebe25bb188 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new a77121ce2f5 74: onsuccess: #590: 1: Success after binutils: 16 commits new bf7bdaaf9b4 75: onsuccess: #591: 1: Success after gcc: 25 commits new 69694b78241 76: onsuccess: #592: 1: Success after linux: 63 commits new 4d9e6bc06a7 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] new 28b6d7783ea 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 9cae3801ab5 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 54cb1852248 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new 6c7dd4e7119 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 0123b9d90f0 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] new 10b075349f2 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new c467da40604 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new f959c92cbd6 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] new 6cd672a9b58 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 43ee4053539 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] new d8b57afbafb 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] new 5ecce8b8564 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] new 36e800ebc75 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 0fdeb9db46d 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 549a26d7375 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new a155247fd35 93: onsuccess: #613: 1: Success after binutils: 19 commits new b4e8450a0c7 94: onsuccess: #616: 1: Success after binutils: 2 commits new 22a30eb68d6 95: onsuccess: #619: 1: Success after binutils: 5 commits new 843e8c9e945 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 561368fd7d4 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 4b2ff870102 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] new 893d66c52ae 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new f245983f303 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 1c5cf0c79b3 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 34ae383d080 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] new c5508bd7a32 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] new f3404631584 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 606237b8030 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 0bc8816ca6e 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new b7c0a83f5e1 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new d70d191bc40 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 16c82c35a19 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new ef9509953bb 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new d5054c68df3 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 344e31b7ef2 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 8a1eb87367b 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 0a6e54501c4 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 23baae04a16 115: onsuccess: #645: 1: Success after binutils: 27 commits new d4b629f7187 116: onsuccess: #647: 1: Success after linux: 3 commits new 994b0b7e8d6 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new bebbc1b0bf4 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new a63858cf02b 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 3a0f17a0289 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 3f4a3abe95b 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 300eeb13560 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new d7f050920d7 123: onsuccess: #655: 1: Success after binutils: 22 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 (0148f140f86) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1736 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 40028 -> 39732 bytes 04-build_abe-gcc/console.log.xz | Bin 214504 -> 214128 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8304 -> 8600 bytes 07-build_abe-glibc/console.log.xz | Bin 243516 -> 245860 bytes 08-build_abe-gdb/console.log.xz | Bin 38900 -> 40232 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3908 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2144 -> 2568 bytes 11-check_regression/console.log.xz | Bin 5696 -> 4744 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 62 +++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +-- sumfiles/binutils.log.xz | Bin 62996 -> 63176 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 81864 -> 83780 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 121728 -> 121932 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 26 files changed, 394 insertions(+), 398 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-stable-allnoconfig updated (1fb0abf912d -> 0e4174c3613)

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-release-aarch64-stable-allnoconfig in repository toolchain/ci/base-artifacts. from 1fb0abf912d 29: onsuccess: #422: boot: Success after binutils/gcc/linux [...] new 0e4174c3613 30: onsuccess: #423: boot: Success after binutils/gcc: 21 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 1748 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 30876 -> 30316 bytes 04-build_abe-stage1/console.log.xz | Bin 69376 -> 68560 bytes 05-build_abe-qemu/console.log.xz | Bin 31000 -> 30800 bytes 06-build_linux/console.log.xz | Bin 3348 -> 3316 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3880 -> 3312 bytes 09-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +++++++++++----------- 16 files changed, 17 insertions(+), 26 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (3c249c1855e -> 17385458f0b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards 3c249c1855e 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/ [...] discards 9398e990627 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/ [...] discards ed7d02dc4c1 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards b5c008558a5 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards bcc9764e571 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/ [...] discards 166e7c1c301 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/ [...] discards 9e9d29e1417 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-4 [...] discards d7eed2fa1e3 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/ [...] discards d30249bbd3c 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 1 [...] discards 2735c5b98bf 225: onsuccess: #2039: 1: Success after binutils/linux/glib [...] discards 0eb8e751aa4 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/ [...] discards 2890e20ea79 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/ [...] discards 4fb25cfad90 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/ [...] discards 8c17777f1f2 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards fe8830cc86c 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/ [...] discards 161f7886b50 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/ [...] discards 74e3b68bbf1 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards ac25d691fd9 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/ [...] discards 911adb769df 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/ [...] discards e2e6c25bf31 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...] discards 80b7e191d45 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] discards 974a722cd85 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards a8ed82903af 212: onsuccess: #2022: 1: Success after linux: 3 commits discards c556ab850d8 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 0a6f36d204e 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 59116aa4a4f 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 054977e8f48 208: onsuccess: #2012: 1: Success after linux: 12 commits discards d8e1effbc5e 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 3018959e9b2 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards ee1238a847f 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards b204a2837ed 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards ed275d911ec 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards 9d2c5261708 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards 4f19531e8b5 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards c9209958329 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards 677bfee048d 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards dfa6fe87194 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards a880a0724ff 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards 025f6d748e0 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards 87d29ca653a 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards 7100d3c1d3b 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 255adfbe921 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 5e846d79ad0 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards df6538e93b5 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards b12d6e90365 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards c2b631be6da 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards fb5db6b4584 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards da0c9f60bc6 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards d6b84e97583 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards aca74c3bbe9 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards 7635d06b3e6 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards 7cd6e48b5bd 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards 16be45d6993 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards 4b49b13dae2 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards 3ba10caa1fc 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards bbd49bd07c2 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards 945d33c0d66 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards c66d5bf72ba 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards c88ee8ae1c5 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards 815ecdfa1ac 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards 088d1e9a34b 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards cd8d30806c1 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards ce643d33025 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards 97ffc6d1a2a 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards 6e3fea96f9f 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards 6218d12dd25 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards 6ad1b2265f9 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards 86ca7b153ee 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards 69bf63c6e71 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards 3e0f0ef6c05 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards 75a93e400c4 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards 407539b238d 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards df06a0e7ceb 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards 98b9312b317 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards bca582b147c 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards 2dd70f59557 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards b9b5a927eb4 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards 5d66015745c 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards af303e1b53a 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 91532ee7cb2 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards 760f6e79677 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 9e1687d6f84 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards beff4f2bb18 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards 95eb841cca3 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards a32d43403cd 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards 80738675b39 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards f7ccae6fed3 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards 8e9baae7689 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards 1211133727e 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards e8e98ac0302 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards 1edeb667003 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards cfc4ae03fd6 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards 0ca7d988a77 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards ab77b95704f 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards 212443d0476 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards fad121a32ff 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards 102df47d0db 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards 342bf71e857 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards e287d95d47e 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards 8588af01518 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards b89dbc0890b 134: onsuccess: #1730: 1: Success after binutils: 2 commits new aa9a8c2bb4a 134: onsuccess: #1730: 1: Success after binutils: 2 commits new e6e3f113647 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 6508e4398b0 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new 86e1e922a04 137: onsuccess: #1736: 1: Success after gcc: 5 commits new b02c8ab6d05 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new 615066049d2 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new 4c7406bca8d 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new 4422d30b840 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new 343b1fde56a 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new c5153a5fa63 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 35c5eb7f6ab 144: onsuccess: #1743: 1: Success after glibc: 2 commits new c5fa1b443e9 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new 155dcf97fed 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new 6bc0e6ef169 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new 3a58e65f7b2 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new b8c832fbb93 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new 4b9aa724b9c 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new 82dae94bd94 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new 67a1b798775 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new 597324c7f5d 153: onsuccess: #1754: 1: Success after gcc: 2 commits new e6d6bc31234 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new fa0b6279948 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new 8af9ed81cf6 156: onsuccess: #1757: 1: Success after gcc: 4 commits new ed5ee4b624e 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new 9776eb86457 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new fb0202a008b 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new fa057e55e44 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new 953cb8109e2 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new 72e80e8026d 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new 813b609723e 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 4ab4502d393 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new 5b1974b2123 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new 83af553ecaa 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new 45338047c0d 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new 7dca3db6c92 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new 05894f925e0 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new 298bfd3cddc 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new 64c1ef820d7 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new 75a2fead1e9 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new 3d59c0b0e59 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new 9853333728c 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new b39dc6fef14 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new 4fe68343c93 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new 5969eeb68f6 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new 8589972a673 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new 65d18c7c237 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new 36dd5f9d2c8 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new bb17384f9d3 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new ffbdf21f72d 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new 11b8ab2f5ca 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new 7105cbeac15 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new ce710b38be2 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new 6dceab75a80 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new c73c9524556 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new 6c687263155 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new 7d87255074c 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new ef9a5876f4e 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new b5093a7108e 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new fffb7277422 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new 88390872f3f 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 8811d68c277 194: onsuccess: #1995: 1: Success after linux: 517 commits new 3d20c0c2ad6 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new da652c59397 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new 987c7da930a 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new 96a3754cfaa 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new 07f9733cbdd 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 77ba9cb7227 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new 03c802ab843 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 1c2873b102f 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new de67682951b 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new 07ff71c688f 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new 9584a7468cd 205: onsuccess: #2006: 1: Success after gcc: 3 commits new a7ec4b3d75e 206: onsuccess: #2007: 1: Success after gcc: 2 commits new a010b75456a 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 18f69e0fd65 208: onsuccess: #2012: 1: Success after linux: 12 commits new 5c53c32d6e8 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 2b2355b5b64 210: onsuccess: #2017: 1: Success after binutils: 6 commits new cd994f28ba6 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 290d1a5c90a 212: onsuccess: #2022: 1: Success after linux: 3 commits new dfc690fd791 213: onsuccess: #2024: 1: Success after binutils: 3 commits new fce37e3a134 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] new f81407c0890 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...] new b302e1fcdbb 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/ [...] new 8172dfc487c 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/ [...] new 82ad0ebf157 218: onsuccess: #2030: 1: Success after gcc: 5 commits new aacd6ba54a9 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/ [...] new 0ae914cd80d 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/ [...] new 72ffc40f210 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 1cc6decd770 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/ [...] new d7cb18a7012 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/ [...] new 688d7d46f66 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/ [...] new 251d37c43fb 225: onsuccess: #2039: 1: Success after binutils/linux/glib [...] new cf2a06ff650 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 1 [...] new ca250aadce1 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/ [...] new 5f2985a3561 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-4 [...] new d95861022f6 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/ [...] new c03dfbb848f 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/ [...] new b0c3c020061 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 9700de180e2 232: onsuccess: #2048: 1: Success after glibc: 2 commits new d0ec4b961c9 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/ [...] new 9743161198c 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/ [...] new 17385458f0b 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] 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 (3c249c1855e) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1788 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31500 -> 31744 bytes 04-build_abe-stage1/console.log.xz | Bin 91216 -> 91436 bytes 06-build_abe-linux/console.log.xz | Bin 10544 -> 9412 bytes 07-build_abe-glibc/console.log.xz | Bin 235452 -> 235368 bytes 08-build_abe-stage2/console.log.xz | Bin 223912 -> 223964 bytes 09-build_abe-gdb/console.log.xz | Bin 38656 -> 38984 bytes 10-build_abe-qemu/console.log.xz | Bin 30240 -> 30256 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2480 -> 2484 bytes 13-check_regression/console.log.xz | Bin 6176 -> 5716 bytes 13-check_regression/results.compare | 16 +- 13-check_regression/results.compare2 | 57 +- 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_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 | 30 +- sumfiles/g++.log.xz | Bin 2682976 -> 2655376 bytes sumfiles/g++.sum | 20 +- sumfiles/gcc.log.xz | Bin 2235260 -> 2260612 bytes sumfiles/gcc.sum | 2168 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 887724 -> 894524 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213856 -> 213932 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 426616 -> 429408 bytes sumfiles/libstdc++.sum | 8 +- 37 files changed, 1178 insertions(+), 1207 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch master updated (8ad0a7df895 -> 0a43f7b1a73)

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 8ad0a7df895 rs6000: enable cbranchcc4 new 0a43f7b1a73 libsanitizer: Fix up libbacktrace build after r13-4547 [PR108072] 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: libsanitizer/libbacktrace/backtrace-rename.h | 1 + 1 file changed, 1 insertion(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (556d20a3ebf -> 9c3c9a557ee)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 556d20a3ebf 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards 70be6f71990 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards d58c7511c10 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards f8b35fa6291 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/ [...] discards 790f9dc4e76 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 2 [...] discards f76b1afeca3 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/ [...] discards 31ac16c791e 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards dc31cf8cc55 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 [...] discards bee4f2fca94 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/ [...] discards 200fd5c4a66 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 1 [...] discards e5f19b464e2 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/ [...] discards d011d47b8dc 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/ [...] discards ed73383bd41 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/ [...] discards 0bd79671f5c 204: onsuccess: #2435: 1: Success after linux: 3 commits discards 3bf88ae7110 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards 20f8e677efa 202: onsuccess: #2431: 1: Success after linux: 944 commits discards 5c69e9eaabb 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards 9e99ca7d30a 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 55b4ab740c1 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/ [...] discards dd6fc8f5418 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/ [...] discards 7341f5f1197 197: onsuccess: #2348: 1: Success after linux: 190 commits discards c0b8166922d 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 4 [...] discards 9e472b654b7 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/ [...] discards 65a1cea5ea9 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/ [...] discards 6f81d2d3358 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/ [...] discards 0fe409ab5db 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/ [...] discards 67aab595889 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 84b5eb86e5f 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/ [...] discards 7828c9be6aa 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/ [...] discards 21181538510 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/ [...] discards 31d5016d4e8 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/ [...] discards 0ab552f537d 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/ [...] discards cbf3aeca2f0 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/ [...] discards 685478782a7 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/ [...] discards f2fa06d7100 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/ [...] discards 3ca7ca6d371 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/ [...] discards 4b4e272c994 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/ [...] discards 1bb48dcb1a1 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/ [...] discards 3e1ec0ec8ea 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/ [...] discards 1974d3a9d06 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] discards 3c7bb87c7ea 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards 1e22e0d78d4 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] discards bbd8e223039 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] discards 48d8915f30c 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 2 [...] discards dfb9c991765 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 7642ef0dbb6 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] discards 2b026d61df3 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/ [...] discards 2f51acc3776 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/ [...] discards 3d268d25f22 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/ [...] discards fd29dc18146 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/ [...] discards 1bd7f32ebd7 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qem [...] discards 85da16c598d 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 1f5d9ac590f 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 6bf9c5a68e2 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/ [...] discards e2912bba8f7 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/ [...] discards b022dd2e3ff 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/ [...] discards a61b465f320 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/ [...] discards 72d5a201fa5 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/ [...] discards 7279f60d554 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 19 [...] discards ff804102c50 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] discards a33b0f5ab26 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 [...] discards 8394673b6bf 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/ [...] discards 821bd7d0b71 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] discards 1844139f3f8 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 1 [...] discards 98b927a8f54 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 [...] discards aca4b936587 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 [...] discards 0d60030fed6 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 3d81dd5e96b 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards cdda200ce62 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/ [...] discards 637852426e4 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 [...] discards fdf16d1d6dc 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 1 [...] discards fee36d99f4c 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards e3844e0ff1f 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/ [...] discards 5f9a8bbce00 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/ [...] discards 1e735cb596a 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qe [...] discards 6728e500f6d 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 5de74058572 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 [...] discards 42bfd166cdb 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/ [...] discards e450ae6e4a7 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 1 [...] discards 05b4348980c 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 [...] discards 138fc0d24d8 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/ [...] discards e4370819f47 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qe [...] discards 41a36f1812d 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 319ce893438 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 1 [...] discards c967073b3c3 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/ [...] discards ec60ebcd38f 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/ [...] discards 60d32987b0b 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 1 [...] discards 0696a0e9638 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 3 [...] discards 00eef466ef2 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/ [...] discards d4877347e84 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 054f6937ee5 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 57296b8517c 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-2 [...] discards 9de47e4184d 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/ [...] discards 03fe0bab001 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 1c243af707f 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-2 [...] discards 8889953889b 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 [...] discards ba6a5935c74 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/ [...] discards eb92bff6594 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/ [...] discards c252b5819f6 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/ [...] discards 3648780bf5c 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/ [...] discards 9490666224e 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/ [...] new f4c7e67e88c 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/ [...] new fb9655c2a8c 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/ [...] new 0f593dd630b 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/ [...] new 5cfe280b626 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/ [...] new ab8fc0a2397 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/ [...] new d4690bab3b7 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 [...] new aac69b65bb3 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-2 [...] new 13c20154667 124: onsuccess: #2159: 1: Success after linux: 23 commits new 070ff1f3513 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/ [...] new 1cb971aadde 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-2 [...] new 2be3cbe136c 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 9118cf8997b 128: onsuccess: #2163: 1: Success after linux: 23 commits new 12034112b46 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/ [...] new cb7b49ac384 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 3 [...] new c91ed522f34 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 1 [...] new f1a7173036f 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/ [...] new 518be109b05 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/ [...] new 24dcac8a708 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 1 [...] new c612ab2efe5 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new a2274432044 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qe [...] new d8d48d7be62 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/ [...] new bb8d8bb5ecf 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 [...] new e9841281c2a 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 1 [...] new 114579e448a 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/ [...] new 7d9d3a1c04d 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 [...] new 7c8844c2c57 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 52aef8cb0c9 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qe [...] new d74dfd7c8ff 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/ [...] new 854d58d069e 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/ [...] new 3be2fa77f91 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 3b6f8755cf8 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 1 [...] new dc675d2a1a4 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 [...] new c249ae872ce 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/ [...] new ffc6908f8d3 150: onsuccess: #2185: 1: Success after gcc: 3 commits new b38e16f1297 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 0a79e883210 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 [...] new 7104c515900 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 [...] new 19950386ad6 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 1 [...] new dfddd4cf8c5 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] new c899c0a0bf2 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/ [...] new 48913d451bc 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 [...] new 501228cece1 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] new ac95a589c33 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 19 [...] new 5caa12f1641 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/ [...] new 2f9547c091b 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/ [...] new c63144aec02 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/ [...] new aaf9d962e55 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/ [...] new c4b2a5b5008 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/ [...] new dbc1ef02b95 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new a3d20936159 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 364b4b2b357 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qem [...] new cc6cca60caf 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/ [...] new 938cbb98eb1 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/ [...] new 2eed1f3c5e6 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/ [...] new 3d65a8db29e 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/ [...] new db3bea873c9 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] new c9d042900f1 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 8659be34608 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 2 [...] new f00b8077104 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] new ce9f7b01459 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] new ec2aed1a5e7 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 1ed25c73ea9 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] new 2678905c2d4 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/ [...] new 073ace46f24 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/ [...] new 6f528ad6c55 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/ [...] new 85a4fab89a8 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/ [...] new 8e21943a754 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/ [...] new de0c1c4a227 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/ [...] new 907f44dd9cd 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/ [...] new df220e35d5f 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/ [...] new 0722388346f 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/ [...] new f7196740549 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/ [...] new f915d599285 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/ [...] new af375bb2764 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/ [...] new 04dc1902b08 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 60b0abd2857 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/ [...] new c9e677d5e7b 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/ [...] new a399866434b 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/ [...] new e8dbee9f67f 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/ [...] new 749a454feaf 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 4 [...] new a092f7a3057 197: onsuccess: #2348: 1: Success after linux: 190 commits new 614b6d9aab5 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/ [...] new d93d8f342ba 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/ [...] new 3d1ec4b08fe 200: onsuccess: #2427: 1: Success after binutils: 274 commits new cd702269c72 201: onsuccess: #2430: 1: Success after glibc: 26 commits new afbfc48a9c0 202: onsuccess: #2431: 1: Success after linux: 944 commits new cdae111449d 203: onsuccess: #2433: 1: Success after binutils: 27 commits new 6ad1fbca2d0 204: onsuccess: #2435: 1: Success after linux: 3 commits new 0d9e563b787 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/ [...] new 5cbc17dc1f6 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/ [...] new 472ddf2d6cf 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/ [...] new c59d6073665 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 1 [...] new e7990018a5a 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/ [...] new 4bdcea54554 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 [...] new 834e05363d7 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new 6e09fc100b5 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/ [...] new 4d000aa35c9 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 2 [...] new 3e63b7973c8 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/ [...] new aa1dd2dfd81 215: onsuccess: #2455: 1: Success after binutils: 3 commits new 7747894bd57 216: onsuccess: #2457: 1: Success after linux: 1736 commits new d2e495c61e5 217: onsuccess: #2459: 1: Success after binutils: 3 commits new 9c3c9a557ee 218: onsuccess: #2461: 1: Success after linux: 916 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 (556d20a3ebf) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1796 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 31788 -> 31896 bytes 04-build_abe-stage1/console.log.xz | Bin 73212 -> 73040 bytes 06-build_abe-linux/console.log.xz | Bin 9072 -> 9368 bytes 07-build_abe-glibc/console.log.xz | Bin 244432 -> 243780 bytes 08-build_abe-stage2/console.log.xz | Bin 204688 -> 204848 bytes 09-build_abe-gdb/console.log.xz | Bin 39428 -> 39444 bytes 10-build_abe-qemu/console.log.xz | Bin 30736 -> 30868 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3904 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2960 -> 2940 bytes 13-check_regression/console.log.xz | Bin 5588 -> 8468 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 61 +- 13-check_regression/mail-body.txt | 100 +- 13-check_regression/results.compare | 67 +- 13-check_regression/results.compare2 | 564 +++- 13-check_regression/results.regressions | 67 +- 14-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 102 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +- results | 67 +- sumfiles/g++.log.xz | Bin 3447856 -> 3433256 bytes sumfiles/g++.sum | 95 +- sumfiles/gcc.log.xz | Bin 3010372 -> 3001192 bytes sumfiles/gcc.sum | 5104 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1035916 -> 1034076 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214672 -> 214692 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2704 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 433816 -> 433752 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 3513 insertions(+), 2828 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022