Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/release-arm updated (5d4473c6c422 -> e1382fcc906e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/release-arm in repository toolchain/ci/base-artifacts. from 5d4473c6c422 25: onsuccess: #146: 7: Success after binutils/gcc/linux/g [...] new e1382fcc906e 26: onsuccess: #147: 7: Success after binutils/gcc/linux/g [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1772 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2764 bytes 04-build_abe-binutils/console.log.xz | Bin 30224 -> 30264 bytes 05-build_abe-stage1/console.log.xz | Bin 87208 -> 87492 bytes 07-build_abe-linux/console.log.xz | Bin 8700 -> 8776 bytes 08-build_abe-glibc/console.log.xz | Bin 230332 -> 231804 bytes 09-build_abe-stage2/console.log.xz | Bin 224132 -> 224096 bytes 10-build_abe-gdb/console.log.xz | Bin 37924 -> 37328 bytes 11-build_abe-qemu/console.log.xz | Bin 31652 -> 30872 bytes 12-check_regression/console.log.xz | Bin 4648 -> 4404 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +++++++++++++++++------------------ 20 files changed, 29 insertions(+), 29 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (ec28f3e279fa -> c8c44bc171e3)

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 ec28f3e279fa 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/ [...] discards c3cd293aaa30 135: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...] discards a0cab2017bff 134: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] discards ef0016ddeace 133: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] discards 6d182c7ad4d1 132: onsuccess: #559: 1: Success after binutils/gcc/linux/ [...] discards ec954b1ba136 131: onsuccess: #558: 1: Success after binutils/gcc/linux/ [...] discards 7d5e389b8688 130: onsuccess: #557: 1: Success after binutils/gcc/linux/ [...] discards 705ae7edfe05 129: onsuccess: #556: 1: Success after binutils/gcc/linux/ [...] discards 8790bc273839 128: onsuccess: #555: 1: Success after binutils/gcc/linux/ [...] discards 4fc9cef0a9d8 127: onsuccess: #554: 1: Success after binutils/gcc/linux/ [...] discards 41ce5cc696de 126: onsuccess: #553: 1: Success after binutils/gcc/linux/ [...] discards b39197b38bfd 125: onsuccess: #552: 1: Success after binutils/gcc/linux/ [...] discards 5f384ccc0cb0 124: onsuccess: #551: 1: Success after binutils/gcc/linux/ [...] discards daa77acdab10 123: onsuccess: #550: 1: Success after binutils/gcc/linux/ [...] discards 3d7ae1f5dde1 122: onsuccess: #549: 1: Success after binutils/gcc/linux/ [...] discards 01fea0e62b84 121: onsuccess: #548: 1: Success after binutils/gcc/linux/ [...] discards b560f15cee8e 120: onsuccess: #547: 1: Success after binutils/gcc/linux/ [...] discards 901f1e640a8c 119: onsuccess: #546: 1: Success after binutils/gcc/linux/ [...] discards 77b41ff954e4 118: onsuccess: #545: 1: Success after binutils/gcc/linux/ [...] discards 66b5c8d250b4 117: onsuccess: #544: 1: Success after binutils/gcc/linux/ [...] discards 238801df883a 116: onsuccess: #543: 1: Success after binutils/gcc/linux/ [...] discards 2d12cd08c048 115: onsuccess: #542: 1: Success after binutils/gcc/linux/ [...] discards d3508cf47927 114: onsuccess: #541: 1: Success after binutils/gcc/linux/ [...] discards 5f1d9826fa69 113: onsuccess: #539: 1: Success after binutils/gcc/linux/ [...] discards 9c7e657f01de 112: onsuccess: #538: 1: Success after binutils/gcc/linux/ [...] discards d7b743a9cdbf 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 6 [...] discards c27c5b561bf2 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/ [...] discards 36760a9ba357 109: onsuccess: #535: 1: Success after binutils/gcc/linux/ [...] discards a292b57b8c7e 108: onsuccess: #534: 1: Success after binutils/gcc/linux/ [...] discards 3be30f738fc9 107: onsuccess: #533: 1: Success after binutils/gcc/linux/ [...] discards c2680b15d38f 106: onsuccess: #532: 1: Success after binutils/gcc/linux/ [...] discards 8f09862f1d4a 105: onsuccess: #531: 1: Success after binutils/gcc/linux/ [...] discards 195f31ea1550 104: onsuccess: #530: 1: Success after gcc: 7 commits discards 3c7cf7ba22ae 103: onsuccess: #529: 1: Success after binutils/gcc/linux/ [...] discards 6ed92b0a87a9 102: onsuccess: #527: 1: Success after binutils: 5 commits discards 9817a0c225ae 101: onsuccess: #524: 1: Success after binutils: 2 commits discards c8ecb12e9653 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 567c142bbb2b 99: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] discards 55f94f2c8843 98: onsuccess: #518: 1: Success after binutils/gcc/linux/g [...] discards 1adecb38bf7d 97: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] discards b09ca7315f12 96: onsuccess: #516: 1: Success after binutils/gcc/linux/g [...] discards 57e4e79153e7 95: onsuccess: #515: 1: Success after binutils/gcc/linux/g [...] discards f33f72c87465 94: onsuccess: #514: 1: Success after binutils/gcc/linux/g [...] discards fd61d3f41afd 93: onsuccess: #513: 1: Success after binutils/gcc/linux/g [...] discards ea0df8f82109 92: onsuccess: #512: 1: Success after binutils/gcc/linux/g [...] discards bcf9bb557fdf 91: onsuccess: #511: 1: Success after linux: 27 commits discards 978743f153d3 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 76c9ae7cdf2d 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 718bad62d41a 88: onsuccess: #506: 1: Success after linux: 34 commits discards ccd74f9ec89b 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 1f542935bfa5 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 0b67dadd7daf 85: onsuccess: #501: 1: Success after binutils/gcc/linux/g [...] discards c4c5669d6c77 84: onsuccess: #500: 1: Success after binutils/gcc/linux/g [...] discards 2d94790f7c86 83: onsuccess: #499: 1: Success after binutils/gcc/linux/g [...] discards f79045da077f 82: onsuccess: #498: 1: Success after binutils/gcc/linux/g [...] discards e1b9194cf20c 81: onsuccess: #497: 1: Success after binutils/gcc/linux/g [...] discards eca4a25c6649 80: onsuccess: #496: 1: Success after binutils/gcc/linux/g [...] discards 60b2f1d32901 79: onsuccess: #495: 1: Success after binutils/gcc/linux/g [...] discards 7b61f9a43b9c 78: onsuccess: #494: 1: Success after binutils/gcc/linux/g [...] discards 72dfc992ae6b 77: onsuccess: #493: 1: Success after binutils/gcc/linux/g [...] discards 52f62c15e11d 76: onsuccess: #492: 1: Success after binutils/gcc/linux/g [...] discards 8e4165cbc9c5 75: onsuccess: #491: 1: Success after binutils/gcc/linux/g [...] discards 5aae552fbaab 74: onsuccess: #490: 1: Success after binutils/gcc/linux/g [...] discards 786e22fc8be5 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/g [...] discards c47c1650fc05 72: onsuccess: #488: 1: Success after binutils/gcc/linux/g [...] discards 38cabde2400c 71: onsuccess: #487: 1: Success after binutils/gcc/linux/g [...] discards e818496f2630 70: onsuccess: #486: 1: Success after binutils/gcc/linux/g [...] discards 33754cbaa00f 69: onsuccess: #485: 1: Success after binutils/gcc/linux/g [...] discards dc6bbbeeb327 68: onsuccess: #484: 1: Success after binutils/gcc/linux/g [...] discards 715277249522 67: onsuccess: #483: 1: Success after binutils/gcc/linux/g [...] discards da79f8515f7a 66: onsuccess: #482: 1: Success after binutils/gcc/linux/g [...] discards 81be72cc9175 65: onsuccess: #481: 1: Success after binutils/gcc/linux/g [...] discards 29729adb6489 64: onsuccess: #480: 1: Success after binutils/gcc/linux/g [...] discards efe90f3ef6b6 63: onsuccess: #479: 1: Success after binutils/gcc/linux/g [...] discards ba7376a4826d 62: onsuccess: #478: 1: Success after binutils/gcc/linux/g [...] discards 4e36e0779324 61: onsuccess: #477: 1: Success after binutils/gcc/linux/g [...] discards 06cf450f99a2 60: onsuccess: #476: 1: Success after binutils/gcc/linux/g [...] discards 96b5f9ed7337 59: onsuccess: #475: 1: Success after binutils/gcc/linux/g [...] discards bf5c6e114d39 58: onsuccess: #474: 1: Success after binutils/gcc/linux/g [...] discards b26c6828d59b 57: onsuccess: #473: 1: Success after binutils/gcc/linux/g [...] discards 1c3276a7d33d 56: onsuccess: #472: 1: Success after binutils/gcc/linux/g [...] discards a268d19b6f78 55: onsuccess: #471: 1: Success after binutils/gcc/linux/g [...] discards e8a0fa9a428e 54: onsuccess: #470: 1: Success after binutils/gcc/linux/g [...] discards 8fbced2099b3 53: onsuccess: #469: 1: Success after binutils/gcc/linux/g [...] discards b557e5332a54 52: onsuccess: #467: 1: Success after binutils: 9 commits discards faeb43f7b53f 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 792d08ec9ce7 50: onsuccess: #461: 1: Success after binutils: 12 commits discards af07923b3867 49: onsuccess: #459: 1: Success after binutils/gcc/linux/g [...] discards 21f9e13a0f65 48: onsuccess: #458: 1: Success after binutils/gcc/linux/g [...] discards 4971bead3af0 47: onsuccess: #457: 1: Success after binutils/gcc/linux/g [...] discards 37ac922f5684 46: onsuccess: #455: 1: Success after binutils/gcc/linux/g [...] discards dde4c09e530a 45: onsuccess: #454: 1: Success after binutils/gcc/linux/g [...] discards 39931572c474 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/g [...] discards 5909889d0865 43: onsuccess: #452: 1: Success after binutils/gcc/linux/g [...] discards e19320b6ccce 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/g [...] discards 56e3032e9ac5 41: onsuccess: #450: 1: Success after binutils/gcc/linux/g [...] discards 9deb0ab2f462 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121- [...] discards 2680a2bae18d 39: onsuccess: #447: 1: Success after binutils: 5 commits discards e43eedf3b5d2 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120- [...] discards 6d8c762c5c34 37: onsuccess: #443: 1: Success after binutils: 2 commits discards faac4d38f24d 36: onsuccess: #441: 1: Success after binutils/gcc/linux/g [...] new b52fc27d59a0 36: onsuccess: #441: 1: Success after binutils/gcc/linux/g [...] new b53ee0e6e525 37: onsuccess: #443: 1: Success after binutils: 2 commits new 751279e885f7 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120- [...] new 951af30222f8 39: onsuccess: #447: 1: Success after binutils: 5 commits new 0e302a4e892a 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121- [...] new 5898f16a11aa 41: onsuccess: #450: 1: Success after binutils/gcc/linux/g [...] new 49884f8b591a 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/g [...] new abcadcd0f193 43: onsuccess: #452: 1: Success after binutils/gcc/linux/g [...] new 625f2bf7ade1 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/g [...] new b9180883f52c 45: onsuccess: #454: 1: Success after binutils/gcc/linux/g [...] new 5767c1f854a7 46: onsuccess: #455: 1: Success after binutils/gcc/linux/g [...] new c58ae4671805 47: onsuccess: #457: 1: Success after binutils/gcc/linux/g [...] new 574a03f60bbc 48: onsuccess: #458: 1: Success after binutils/gcc/linux/g [...] new 66ad428c8a63 49: onsuccess: #459: 1: Success after binutils/gcc/linux/g [...] new c43f432c26eb 50: onsuccess: #461: 1: Success after binutils: 12 commits new 78e881221b9c 51: onsuccess: #464: 1: Success after binutils: 6 commits new c8d281bf0480 52: onsuccess: #467: 1: Success after binutils: 9 commits new 183323b65bb5 53: onsuccess: #469: 1: Success after binutils/gcc/linux/g [...] new 22c2b6f1d54e 54: onsuccess: #470: 1: Success after binutils/gcc/linux/g [...] new 174b94961bb6 55: onsuccess: #471: 1: Success after binutils/gcc/linux/g [...] new cfecd5051030 56: onsuccess: #472: 1: Success after binutils/gcc/linux/g [...] new 0e8d71ca4888 57: onsuccess: #473: 1: Success after binutils/gcc/linux/g [...] new dd005179b90a 58: onsuccess: #474: 1: Success after binutils/gcc/linux/g [...] new a68dfd7ec33e 59: onsuccess: #475: 1: Success after binutils/gcc/linux/g [...] new e80a2a281840 60: onsuccess: #476: 1: Success after binutils/gcc/linux/g [...] new a860a946eb2e 61: onsuccess: #477: 1: Success after binutils/gcc/linux/g [...] new f92da1d87ab9 62: onsuccess: #478: 1: Success after binutils/gcc/linux/g [...] new 911a7ac1738e 63: onsuccess: #479: 1: Success after binutils/gcc/linux/g [...] new 233df5128843 64: onsuccess: #480: 1: Success after binutils/gcc/linux/g [...] new c4983f254340 65: onsuccess: #481: 1: Success after binutils/gcc/linux/g [...] new 14e25f7e6817 66: onsuccess: #482: 1: Success after binutils/gcc/linux/g [...] new f9bec8855c1d 67: onsuccess: #483: 1: Success after binutils/gcc/linux/g [...] new 85f1e7f0d03e 68: onsuccess: #484: 1: Success after binutils/gcc/linux/g [...] new d5a8ace01dbe 69: onsuccess: #485: 1: Success after binutils/gcc/linux/g [...] new ced905bbf702 70: onsuccess: #486: 1: Success after binutils/gcc/linux/g [...] new 88618a98020e 71: onsuccess: #487: 1: Success after binutils/gcc/linux/g [...] new b3dec44253de 72: onsuccess: #488: 1: Success after binutils/gcc/linux/g [...] new f0dddc34f088 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/g [...] new 14386884534c 74: onsuccess: #490: 1: Success after binutils/gcc/linux/g [...] new 3ea5e0c11272 75: onsuccess: #491: 1: Success after binutils/gcc/linux/g [...] new ba402309ac48 76: onsuccess: #492: 1: Success after binutils/gcc/linux/g [...] new d0022390ec53 77: onsuccess: #493: 1: Success after binutils/gcc/linux/g [...] new c25d54e2eb0a 78: onsuccess: #494: 1: Success after binutils/gcc/linux/g [...] new 21342b487a81 79: onsuccess: #495: 1: Success after binutils/gcc/linux/g [...] new 1d066409960c 80: onsuccess: #496: 1: Success after binutils/gcc/linux/g [...] new 83e795497c08 81: onsuccess: #497: 1: Success after binutils/gcc/linux/g [...] new 7f32bfb3f4dc 82: onsuccess: #498: 1: Success after binutils/gcc/linux/g [...] new 4302d75fa77b 83: onsuccess: #499: 1: Success after binutils/gcc/linux/g [...] new fc2dc07e1458 84: onsuccess: #500: 1: Success after binutils/gcc/linux/g [...] new a818fb73ccb3 85: onsuccess: #501: 1: Success after binutils/gcc/linux/g [...] new 8be92f57464e 86: onsuccess: #503: 1: Success after binutils: 12 commits new d461c5e50631 87: onsuccess: #505: 1: Success after glibc: 7 commits new d276829efd34 88: onsuccess: #506: 1: Success after linux: 34 commits new a39187929b18 89: onsuccess: #508: 1: Success after binutils: 12 commits new aacaf0a1346f 90: onsuccess: #510: 1: Success after glibc: 5 commits new c8567462abe6 91: onsuccess: #511: 1: Success after linux: 27 commits new 872b362d4e8c 92: onsuccess: #512: 1: Success after binutils/gcc/linux/g [...] new 6388da10c333 93: onsuccess: #513: 1: Success after binutils/gcc/linux/g [...] new 62b1d7996f17 94: onsuccess: #514: 1: Success after binutils/gcc/linux/g [...] new 1ef8428f751c 95: onsuccess: #515: 1: Success after binutils/gcc/linux/g [...] new b80d8c172ce7 96: onsuccess: #516: 1: Success after binutils/gcc/linux/g [...] new 76ee30049c6f 97: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] new ca5570ebfaff 98: onsuccess: #518: 1: Success after binutils/gcc/linux/g [...] new eaa7b66bc9b8 99: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] new a26eb4fd9c5c 100: onsuccess: #521: 1: Success after binutils: 10 commits new 183990b6460a 101: onsuccess: #524: 1: Success after binutils: 2 commits new 41a5bab5bb04 102: onsuccess: #527: 1: Success after binutils: 5 commits new 18f1052568f3 103: onsuccess: #529: 1: Success after binutils/gcc/linux/ [...] new 7e5c1be6b32a 104: onsuccess: #530: 1: Success after gcc: 7 commits new 3a9eec330c1d 105: onsuccess: #531: 1: Success after binutils/gcc/linux/ [...] new 07df3328b7ba 106: onsuccess: #532: 1: Success after binutils/gcc/linux/ [...] new cb5c20d59077 107: onsuccess: #533: 1: Success after binutils/gcc/linux/ [...] new 47a8b4c03e5d 108: onsuccess: #534: 1: Success after binutils/gcc/linux/ [...] new 166d2c6ec99e 109: onsuccess: #535: 1: Success after binutils/gcc/linux/ [...] new 70ce05933c3e 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/ [...] new beadfe229d42 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 6 [...] new 5b0870ee2b85 112: onsuccess: #538: 1: Success after binutils/gcc/linux/ [...] new 49cbf51c36cf 113: onsuccess: #539: 1: Success after binutils/gcc/linux/ [...] new 7e0334c77bb6 114: onsuccess: #541: 1: Success after binutils/gcc/linux/ [...] new a5b59a2d3371 115: onsuccess: #542: 1: Success after binutils/gcc/linux/ [...] new 459ed2146e64 116: onsuccess: #543: 1: Success after binutils/gcc/linux/ [...] new 1384fb027e0e 117: onsuccess: #544: 1: Success after binutils/gcc/linux/ [...] new 035ea0dcb21c 118: onsuccess: #545: 1: Success after binutils/gcc/linux/ [...] new 742cf655a560 119: onsuccess: #546: 1: Success after binutils/gcc/linux/ [...] new 178457252eb6 120: onsuccess: #547: 1: Success after binutils/gcc/linux/ [...] new c63d42df4b14 121: onsuccess: #548: 1: Success after binutils/gcc/linux/ [...] new 25ba14c7bf95 122: onsuccess: #549: 1: Success after binutils/gcc/linux/ [...] new 35a0a2d6f676 123: onsuccess: #550: 1: Success after binutils/gcc/linux/ [...] new 69ae87b2a2c8 124: onsuccess: #551: 1: Success after binutils/gcc/linux/ [...] new 7ae999efdc61 125: onsuccess: #552: 1: Success after binutils/gcc/linux/ [...] new b876a94256f6 126: onsuccess: #553: 1: Success after binutils/gcc/linux/ [...] new 8b462fdc64ed 127: onsuccess: #554: 1: Success after binutils/gcc/linux/ [...] new 2693dec1f1a4 128: onsuccess: #555: 1: Success after binutils/gcc/linux/ [...] new b9986bef2adb 129: onsuccess: #556: 1: Success after binutils/gcc/linux/ [...] new a85c838ddfdc 130: onsuccess: #557: 1: Success after binutils/gcc/linux/ [...] new b8e800d59a49 131: onsuccess: #558: 1: Success after binutils/gcc/linux/ [...] new e181f42628cb 132: onsuccess: #559: 1: Success after binutils/gcc/linux/ [...] new befe8ff7fa54 133: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] new e2a9963b3b94 134: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] new 36397ec97934 135: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...] new 1437d9d888ff 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/ [...] new c8c44bc171e3 137: onsuccess: #564: 1: Success after binutils/gcc/linux/ [...] 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 (ec28f3e279fa) \ 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 1756 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 52608 -> 52600 bytes 04-build_abe-gcc/console.log.xz | Bin 234688 -> 234248 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8624 -> 9200 bytes 07-build_abe-glibc/console.log.xz | Bin 236496 -> 237924 bytes 08-build_abe-gdb/console.log.xz | Bin 51912 -> 51904 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3812 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2088 -> 2236 bytes 11-check_regression/console.log.xz | Bin 5736 -> 6204 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 27 +-- 12-update_baseline/console.log | 64 +++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +-- sumfiles/binutils.log.xz | Bin 62664 -> 62704 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 100532 -> 100392 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 132168 -> 132136 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 30 files changed, 409 insertions(+), 422 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_llvm_fx/llvm-master-aarch64-cpu2017rate-O3 updated (618448361d9c -> 2cb6f84bf6ea)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_llvm_fx/llvm-master-aarch64-cpu2017rate-O3 in repository toolchain/ci/base-artifacts. from 618448361d9c 24: onsuccess: #133: 1: [TCWG CI] 520.omnetpp_r speeds up [...] new 2cb6f84bf6ea 25: force: #138: 1: [TCWG CI] 520.omnetpp_r slowed down by [...] 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 1812 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 32292 -> 32608 bytes 04-build_abe-stage1/console.log.xz | Bin 74064 -> 74692 bytes 06-build_abe-linux/console.log.xz | Bin 8880 -> 8792 bytes 07-build_abe-glibc/console.log.xz | Bin 245884 -> 245916 bytes 08-build_abe-stage2/console.log.xz | Bin 179084 -> 182936 bytes 09-build_llvm-true-false-cflags-/console.log.xz | Bin 65156 -> 62384 bytes 10-benchmark/benchmark-build.log | 86 +- 10-benchmark/benchmark.log | 84 +- 10-benchmark/console.log.xz | Bin 3948 -> 3956 bytes 11-check_regression/console.log.xz | Bin 11092 -> 10936 bytes .../csv-results-vs-first-0/md5sum.csv | 1536 +- .../csv-results-vs-first-0/results.csv | 434672 +++++++++--------- .../csv-results-vs-first-0/size.csv | 422216 ++++++++--------- .../csv-results-vs-first-0/vect.csv | 50404 +- .../csv-results-vs-first-1/md5sum.csv | 1663 +- .../csv-results-vs-first-1/perf.csv | 2031 +- .../csv-results-vs-first-1/results.csv | 410801 ++++++++--------- .../csv-results-vs-first-1/size.csv | 415060 ++++++++--------- .../csv-results-vs-prev-0/md5sum.csv | 1743 +- 11-check_regression/csv-results-vs-prev-0/perf.csv | 2014 +- .../csv-results-vs-prev-0/results.csv | 410840 +++++++++-------- 11-check_regression/csv-results-vs-prev-0/size.csv | 414780 ++++++++--------- .../csv-results-vs-prev-1/md5sum.csv | 1663 +- 11-check_regression/csv-results-vs-prev-1/perf.csv | 2031 +- .../csv-results-vs-prev-1/results.csv | 410801 ++++++++--------- 11-check_regression/csv-results-vs-prev-1/size.csv | 415060 ++++++++--------- 11-check_regression/exe.improvement | 1 - 11-check_regression/exe.regression | 6 + 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/jira-body.txt | 22 +- 11-check_regression/mail-body.txt | 22 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results-vs-first-brief.csv | 42 +- 11-check_regression/results-vs-first-full.csv | 1951 +- 11-check_regression/results-vs-first-internal.csv | 129 +- 11-check_regression/results-vs-first.csv | 129 +- 11-check_regression/results-vs-first.log | 696 +- 11-check_regression/results-vs-prev-brief.csv | 42 +- 11-check_regression/results-vs-prev-compare.csv | 25 +- 11-check_regression/results-vs-prev-full.csv | 2113 +- 11-check_regression/results-vs-prev-internal.csv | 131 +- 11-check_regression/results-vs-prev.csv | 131 +- 11-check_regression/results-vs-prev.log | 788 +- 11-check_regression/results.regressions | 22 + 11-check_regression/skipped-symbols.txt | 26 +- 11-check_regression/symbol.regression | 5 + 12-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 8 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 8 +- .../squad-vs-first/502.gcc_r/results-metrics.json | 2 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 8 +- .../squad-vs-first/505.mcf_r/results-metrics.json | 2 +- .../508.namd_r/results-metadata.json | 8 +- .../squad-vs-first/508.namd_r/results-metrics.json | 2 +- .../510.parest_r/results-metadata.json | 8 +- .../510.parest_r/results-metrics.json | 2 +- .../511.povray_r/results-metadata.json | 8 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 8 +- .../squad-vs-first/519.lbm_r/results-metrics.json | 2 +- .../520.omnetpp_r/results-metadata.json | 8 +- .../520.omnetpp_r/results-metrics.json | 2 +- .../523.xalancbmk_r/results-metadata.json | 8 +- .../523.xalancbmk_r/results-metrics.json | 2 +- .../525.x264_r/results-metadata.json | 8 +- .../526.blender_r/results-metadata.json | 8 +- .../526.blender_r/results-metrics.json | 2 +- .../531.deepsjeng_r/results-metadata.json | 8 +- .../531.deepsjeng_r/results-metrics.json | 2 +- .../538.imagick_r/results-metadata.json | 8 +- .../541.leela_r/results-metadata.json | 8 +- .../squad-vs-first/544.nab_r/results-metadata.json | 8 +- .../squad-vs-first/557.xz_r/results-metadata.json | 8 +- .../squad-vs-first/557.xz_r/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 8 +- dashboard/squad-vs-first/Mean/results-metrics.json | 2 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 74 +- dashboard/squad-vs-first/summary-annotation.txt | 2 +- mail/jira-body.txt | 30 +- mail/mail-body.txt | 30 +- mail/mail-subject.txt | 2 +- manifest.sh | 23 +- results | 22 + results_id | 2 +- 86 files changed, 1702142 insertions(+), 1701975 deletions(-) delete mode 100644 11-check_regression/exe.improvement create mode 100644 11-check_regression/exe.regression create mode 100644 11-check_regression/results.regressions create mode 100644 11-check_regression/symbol.regression -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-mainline-allmodconfig updated (bbd74f404f24 -> abd28cf33866)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-mainline-allmodconfig in repository toolchain/ci/base-artifacts. from bbd74f404f24 34: onsuccess: #573: 33: Success after binutils/gcc/linux/ [...] new abd28cf33866 35: onsuccess: #574: 33: Success after binutils/gcc/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2016 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 32428 -> 32364 bytes 04-build_abe-stage1/console.log.xz | Bin 73524 -> 73944 bytes 05-build_abe-qemu/console.log.xz | Bin 32020 -> 31636 bytes 06-build_linux/console.log.xz | Bin 3440 -> 3448 bytes 08-check_regression/console.log.xz | Bin 4552 -> 4388 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 16 files changed, 23 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/master-aarch64-check_bootstrap updated (7927544903c1 -> 15c1e418f455)

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_bootstrap/master-aarch64-check_bootstrap in repository toolchain/ci/base-artifacts. discards 7927544903c1 128: onsuccess: #672: 1: Success after binutils/gcc: 6 commits discards 8bc2b1f85614 127: onsuccess: #671: 1: Success after binutils/gcc: 10 commits discards 0fae32834953 126: onsuccess: #670: 1: Success after binutils/gcc: 43 commits discards 9bc60420165e 125: onsuccess: #669: 1: Success after binutils/gcc: 36 commits discards 702507d7e415 124: onsuccess: #668: 1: Success after binutils/gcc: 36 commits discards f617fcfb1b95 123: onsuccess: #667: 1: Success after binutils/gcc: 81 commits discards c213fd4d1564 122: onsuccess: #666: 1: Success after binutils/gcc: 50 commits discards 26d0aec4582a 121: onsuccess: #665: 1: Success after binutils/gcc: 12 commits discards f5ca56c69a21 120: onsuccess: #664: 1: Success after binutils/gcc: 3 commits discards 4f1180e3fa6a 119: onsuccess: #663: 1: Success after binutils/gcc: 26 commits discards 1e4300813cc7 118: onsuccess: #662: 1: Success after binutils/gcc: 38 commits discards ff3bbc80d66f 117: onsuccess: #661: 1: Success after binutils/gcc: 22 commits discards d19655f4fddc 116: onsuccess: #660: 1: Success after binutils/gcc: 48 commits discards 25e11cef13e2 115: onsuccess: #659: 1: Success after binutils/gcc: 36 commits discards 98eab7a6e6ab 114: onsuccess: #658: 1: Success after binutils/gcc: 15 commits discards 6905dc0250ca 113: onsuccess: #657: 1: Success after binutils/gcc: 6 commits discards 380233617eac 112: onsuccess: #656: 1: Success after binutils/gcc: 28 commits discards 07f199a10a49 111: onsuccess: #655: 1: Success after binutils/gcc: 43 commits discards 300dea994145 110: onsuccess: #654: 1: Success after binutils/gcc: 53 commits discards 16587e76b995 109: onsuccess: #653: 1: Success after binutils/gcc: 24 commits discards b8f6acd45cf7 108: onsuccess: #652: 1: Success after binutils/gcc: 115 commits discards f85645b2ea92 107: onsuccess: #651: 1: Success after binutils/gcc: 12 commits discards b23edc24e6a9 106: onsuccess: #650: 1: Success after binutils/gcc: 23 commits discards f9586d2bc890 105: onsuccess: #648: 1: Success after binutils: 2 commits discards 3d8c167c3bcb 104: onsuccess: #646: 1: Success after binutils/gcc: 39 commits discards d93d3eaaebdb 103: onsuccess: #645: 1: Success after binutils/gcc: 29 commits discards 158468730d26 102: onsuccess: #644: 1: Success after binutils/gcc: 51 commits discards 835cc32d11d2 101: onsuccess: #643: 1: Success after binutils/gcc: 56 commits discards 34496d372d7a 100: onsuccess: #642: 1: Success after binutils/gcc: 28 commits discards 25d20aae6451 99: onsuccess: #640: 1: Success after binutils/gcc: 40 commits discards 98e3299b9e04 98: onsuccess: #639: 1: Success after binutils/gcc: 36 commits discards 4cc28741c192 97: onsuccess: #638: 1: Success after binutils/gcc: 49 commits discards 3ef5d55cdccd 96: onsuccess: #637: 1: Success after binutils/gcc: 17 commits discards 1626a4ba07e9 95: onsuccess: #636: 1: Success after binutils/gcc: 220 commits discards 9719ca6ea730 94: onsuccess: #634: 1: Success after binutils: 5 commits discards 7841420fbf13 93: onsuccess: #631: 1: Success after binutils: 2 commits discards 369d92b916b8 92: onsuccess: #628: 1: Success after binutils: 25 commits discards 447038d69c99 91: onsuccess: #626: 1: Success after binutils/gcc: 52 commits discards 0cb716c472c6 90: onsuccess: #625: 1: Success after binutils/gcc: 61 commits discards fdbe89c96e0b 89: onsuccess: #624: 1: Success after binutils/gcc: 62 commits discards 979403d320d8 88: onsuccess: #623: 1: Success after binutils/gcc: 78 commits discards acedff0b27d3 87: onsuccess: #622: 1: Success after binutils/gcc: 18 commits discards 31bdd39b6706 86: onsuccess: #621: 1: Success after binutils/gcc: 17 commits discards f41a2261b94e 85: onsuccess: #620: 1: Success after binutils/gcc: 65 commits discards 33564d4117c4 84: onsuccess: #619: 1: Success after binutils/gcc: 53 commits discards f9e798afdf7b 83: onsuccess: #618: 1: Success after binutils/gcc: 26 commits discards 882c3c64b2bf 82: onsuccess: #617: 1: Success after binutils/gcc: 29 commits discards 9302cc615189 81: onsuccess: #616: 1: Success after binutils/gcc: 39 commits discards dfcbfce8e9de 80: onsuccess: #615: 1: Success after binutils/gcc: 9 commits discards e57972d24981 79: onsuccess: #614: 1: Success after binutils/gcc: 17 commits discards 990c28461500 78: onsuccess: #613: 1: Success after binutils/gcc: 34 commits discards 0efa0ae8b647 77: onsuccess: #612: 1: Success after binutils/gcc: 31 commits discards 0c28fb3f3a85 76: onsuccess: #611: 1: Success after binutils/gcc: 30 commits discards 27f3c9d7dff7 75: onsuccess: #610: 1: Success after binutils/gcc: 38 commits discards 35ce0b7467a4 74: onsuccess: #609: 1: Success after binutils/gcc: 43 commits discards 4c83c1e0f0cb 73: onsuccess: #608: 1: Success after binutils/gcc: 10 commits discards 2a0a4e003e0c 72: onsuccess: #607: 1: Success after binutils/gcc: 6 commits discards 0bdf7827fd9e 71: onsuccess: #606: 1: Success after binutils/gcc: 30 commits discards da907083023d 70: onsuccess: #605: 1: Success after binutils/gcc: 49 commits discards f019dc0a8a55 69: onsuccess: #604: 1: Success after binutils/gcc: 49 commits discards 9f4264c303ba 68: onsuccess: #603: 1: Success after binutils/gcc: 46 commits discards fe2ac85e12c8 67: onsuccess: #602: 1: Success after binutils/gcc: 45 commits discards 72e112c97aa3 66: onsuccess: #601: 1: Success after binutils/gcc: 10 commits discards eee590a9dda9 65: onsuccess: #600: 1: Success after binutils/gcc: 9 commits discards 4502b99d4b64 64: onsuccess: #599: 1: Success after binutils/gcc: 42 commits discards e1507b1f104a 63: onsuccess: #598: 1: Success after binutils/gcc: 37 commits discards b947c451a209 62: onsuccess: #597: 1: Success after binutils/gcc: 35 commits discards 7fd4a378d803 61: onsuccess: #596: 1: Success after binutils/gcc: 59 commits discards 3420772cfa87 60: onsuccess: #595: 1: Success after binutils/gcc: 58 commits discards 71f92a906269 59: onsuccess: #594: 1: Success after binutils/gcc: 6 commits discards c0b690339040 58: onsuccess: #593: 1: Success after binutils/gcc: 6 commits discards 85faf040a501 57: onsuccess: #592: 1: Success after binutils/gcc: 34 commits discards 01f073da20f3 56: onsuccess: #591: 1: Success after binutils/gcc: 50 commits discards 9fcde7f26714 55: onsuccess: #590: 1: Success after binutils/gcc: 36 commits discards a2184cda84d9 54: onsuccess: #589: 1: Success after binutils/gcc: 51 commits discards 1ae9855c4b74 53: onsuccess: #588: 1: Success after binutils/gcc: 38 commits discards bfa56baa5494 52: onsuccess: #587: 1: Success after binutils/gcc: 31 commits discards 0524f41c0abb 51: onsuccess: #586: 1: Success after binutils/gcc: 6 commits discards 221f4ec73c88 50: onsuccess: #585: 1: Success after binutils/gcc: 44 commits discards 616e91a243c0 49: onsuccess: #584: 1: Success after binutils/gcc: 148 commits discards 7108d7345c2c 48: onsuccess: #582: 1: Success after binutils: 9 commits discards 96b22f633e92 47: onsuccess: #579: 1: Success after binutils: 6 commits discards ad6d452dd0f3 46: onsuccess: #576: 1: Success after binutils: 12 commits discards 3bc636c18221 45: onsuccess: #574: 1: Success after binutils/gcc: 19 commits discards 651b95d97f27 44: onsuccess: #573: 1: Success after binutils/gcc: 6 commits discards ac43b8561da3 43: onsuccess: #572: 1: Success after binutils/gcc: 98 commits discards 02d6795ece1c 42: onsuccess: #570: 1: Success after binutils/gcc: 34 commits discards 4407d693d22c 41: onsuccess: #569: 1: Success after binutils/gcc: 41 commits discards 8dd3df08fed3 40: onsuccess: #568: 1: Success after binutils/gcc: 15 commits discards 12b7860275e4 39: onsuccess: #567: 1: Success after binutils/gcc: 5 commits discards 61eab437bb96 38: onsuccess: #566: 1: Success after binutils/gcc: 6 commits discards 24dd82cf1d70 37: onsuccess: #565: 1: Success after binutils/gcc: 25 commits discards 7454e9da0721 36: onsuccess: #564: 1: Success after binutils/gcc: 18 commits discards a3ef8347b67c 35: onsuccess: #563: 1: Success after binutils/gcc: 30 commits discards 6d930bda636c 34: onsuccess: #562: 1: Success after binutils/gcc: 31 commits discards e0380bde79fd 33: onsuccess: #561: 1: Success after binutils/gcc: 71 commits discards c64143840a45 32: onsuccess: #560: 1: Success after binutils/gcc: 5 commits discards 773f747f0d29 31: onsuccess: #559: 1: Success after binutils/gcc: 8 commits discards ccac051139f3 30: onsuccess: #558: 1: Success after binutils/gcc: 24 commits discards 0cac1eb3e513 29: onsuccess: #557: 1: Success after binutils/gcc: 30 commits discards 0c18d03e4ac6 28: onsuccess: #556: 1: Success after binutils/gcc: 27 commits new af854ab651e1 28: onsuccess: #556: 1: Success after binutils/gcc: 27 commits new 24945121ba5d 29: onsuccess: #557: 1: Success after binutils/gcc: 30 commits new eb81f997a20f 30: onsuccess: #558: 1: Success after binutils/gcc: 24 commits new 432ec75a34da 31: onsuccess: #559: 1: Success after binutils/gcc: 8 commits new 618c933fed19 32: onsuccess: #560: 1: Success after binutils/gcc: 5 commits new c13e6e508fa1 33: onsuccess: #561: 1: Success after binutils/gcc: 71 commits new 5eaddb5c5c2e 34: onsuccess: #562: 1: Success after binutils/gcc: 31 commits new 40bb4a82a82c 35: onsuccess: #563: 1: Success after binutils/gcc: 30 commits new 2c0db873c97c 36: onsuccess: #564: 1: Success after binutils/gcc: 18 commits new 64dfa80ad4a7 37: onsuccess: #565: 1: Success after binutils/gcc: 25 commits new e95d310861ed 38: onsuccess: #566: 1: Success after binutils/gcc: 6 commits new 44be20ae1f83 39: onsuccess: #567: 1: Success after binutils/gcc: 5 commits new f49f086979c8 40: onsuccess: #568: 1: Success after binutils/gcc: 15 commits new 2ee364582a68 41: onsuccess: #569: 1: Success after binutils/gcc: 41 commits new b7234ef2a599 42: onsuccess: #570: 1: Success after binutils/gcc: 34 commits new 510e3104a3e2 43: onsuccess: #572: 1: Success after binutils/gcc: 98 commits new 7240f8ae8df8 44: onsuccess: #573: 1: Success after binutils/gcc: 6 commits new 92176c16bbec 45: onsuccess: #574: 1: Success after binutils/gcc: 19 commits new f09086e0189f 46: onsuccess: #576: 1: Success after binutils: 12 commits new db697f0d0f32 47: onsuccess: #579: 1: Success after binutils: 6 commits new 7c7847a98a9e 48: onsuccess: #582: 1: Success after binutils: 9 commits new f52d4869d2e4 49: onsuccess: #584: 1: Success after binutils/gcc: 148 commits new 9a00b0460191 50: onsuccess: #585: 1: Success after binutils/gcc: 44 commits new 94a081a6abbe 51: onsuccess: #586: 1: Success after binutils/gcc: 6 commits new c6c9d5f6dcc1 52: onsuccess: #587: 1: Success after binutils/gcc: 31 commits new 97cf00c8b50e 53: onsuccess: #588: 1: Success after binutils/gcc: 38 commits new fd84d8a43002 54: onsuccess: #589: 1: Success after binutils/gcc: 51 commits new 834908187f70 55: onsuccess: #590: 1: Success after binutils/gcc: 36 commits new 06d118ff7475 56: onsuccess: #591: 1: Success after binutils/gcc: 50 commits new e86c2bed76a1 57: onsuccess: #592: 1: Success after binutils/gcc: 34 commits new f59779ed04df 58: onsuccess: #593: 1: Success after binutils/gcc: 6 commits new c6a86f96a41a 59: onsuccess: #594: 1: Success after binutils/gcc: 6 commits new e0e7ef3a7ef2 60: onsuccess: #595: 1: Success after binutils/gcc: 58 commits new 303fde59fa9f 61: onsuccess: #596: 1: Success after binutils/gcc: 59 commits new f8ba79f0f446 62: onsuccess: #597: 1: Success after binutils/gcc: 35 commits new 36cacdd30cc0 63: onsuccess: #598: 1: Success after binutils/gcc: 37 commits new cdb04522c1bf 64: onsuccess: #599: 1: Success after binutils/gcc: 42 commits new 5c615a3f2d86 65: onsuccess: #600: 1: Success after binutils/gcc: 9 commits new 287df227de1f 66: onsuccess: #601: 1: Success after binutils/gcc: 10 commits new a9e5e7eee6d1 67: onsuccess: #602: 1: Success after binutils/gcc: 45 commits new ced181287e61 68: onsuccess: #603: 1: Success after binutils/gcc: 46 commits new 09de01f099a9 69: onsuccess: #604: 1: Success after binutils/gcc: 49 commits new 21c7c987dad2 70: onsuccess: #605: 1: Success after binutils/gcc: 49 commits new c44e978a1d3d 71: onsuccess: #606: 1: Success after binutils/gcc: 30 commits new 97c8f12f4a6d 72: onsuccess: #607: 1: Success after binutils/gcc: 6 commits new 8acbbb166518 73: onsuccess: #608: 1: Success after binutils/gcc: 10 commits new 1d8a0c1ce14b 74: onsuccess: #609: 1: Success after binutils/gcc: 43 commits new 39a9d2a670fa 75: onsuccess: #610: 1: Success after binutils/gcc: 38 commits new 18f406b2c0d5 76: onsuccess: #611: 1: Success after binutils/gcc: 30 commits new 0bf0b569e876 77: onsuccess: #612: 1: Success after binutils/gcc: 31 commits new a68c9af7838f 78: onsuccess: #613: 1: Success after binutils/gcc: 34 commits new 4beb7bc8fbf2 79: onsuccess: #614: 1: Success after binutils/gcc: 17 commits new b7f09a0cbcb2 80: onsuccess: #615: 1: Success after binutils/gcc: 9 commits new 2652ec95222b 81: onsuccess: #616: 1: Success after binutils/gcc: 39 commits new a22ac51cac8c 82: onsuccess: #617: 1: Success after binutils/gcc: 29 commits new 648bfc7eb8ae 83: onsuccess: #618: 1: Success after binutils/gcc: 26 commits new c42371e5aa20 84: onsuccess: #619: 1: Success after binutils/gcc: 53 commits new daae9c1f88dd 85: onsuccess: #620: 1: Success after binutils/gcc: 65 commits new 5b0043b4fc86 86: onsuccess: #621: 1: Success after binutils/gcc: 17 commits new 0895f95fc2fa 87: onsuccess: #622: 1: Success after binutils/gcc: 18 commits new 2f1245a9795a 88: onsuccess: #623: 1: Success after binutils/gcc: 78 commits new e50caf53f322 89: onsuccess: #624: 1: Success after binutils/gcc: 62 commits new e528a9b5475c 90: onsuccess: #625: 1: Success after binutils/gcc: 61 commits new 429f29240054 91: onsuccess: #626: 1: Success after binutils/gcc: 52 commits new 3e246aecde9a 92: onsuccess: #628: 1: Success after binutils: 25 commits new e033fd4ce6f1 93: onsuccess: #631: 1: Success after binutils: 2 commits new 0566de162ff2 94: onsuccess: #634: 1: Success after binutils: 5 commits new 3e0e7aa2cbe6 95: onsuccess: #636: 1: Success after binutils/gcc: 220 commits new 3f3fd93b8586 96: onsuccess: #637: 1: Success after binutils/gcc: 17 commits new b9d16fb150ad 97: onsuccess: #638: 1: Success after binutils/gcc: 49 commits new f9b9f99ee579 98: onsuccess: #639: 1: Success after binutils/gcc: 36 commits new 3f1cb0c09dda 99: onsuccess: #640: 1: Success after binutils/gcc: 40 commits new 55f786bf17df 100: onsuccess: #642: 1: Success after binutils/gcc: 28 commits new 9a4384df6194 101: onsuccess: #643: 1: Success after binutils/gcc: 56 commits new 23dcf24374b3 102: onsuccess: #644: 1: Success after binutils/gcc: 51 commits new be3e1fb642a7 103: onsuccess: #645: 1: Success after binutils/gcc: 29 commits new d0931d1c1f91 104: onsuccess: #646: 1: Success after binutils/gcc: 39 commits new 8392ba070343 105: onsuccess: #648: 1: Success after binutils: 2 commits new aae698ae2304 106: onsuccess: #650: 1: Success after binutils/gcc: 23 commits new 0b93362538af 107: onsuccess: #651: 1: Success after binutils/gcc: 12 commits new 31e48984dc04 108: onsuccess: #652: 1: Success after binutils/gcc: 115 commits new 736a13228710 109: onsuccess: #653: 1: Success after binutils/gcc: 24 commits new 71a4a50396b2 110: onsuccess: #654: 1: Success after binutils/gcc: 53 commits new 0dc9b1a2912b 111: onsuccess: #655: 1: Success after binutils/gcc: 43 commits new 7ff8f5583f37 112: onsuccess: #656: 1: Success after binutils/gcc: 28 commits new dbc724859e62 113: onsuccess: #657: 1: Success after binutils/gcc: 6 commits new 13cbd6fd5055 114: onsuccess: #658: 1: Success after binutils/gcc: 15 commits new 7d940a4015e7 115: onsuccess: #659: 1: Success after binutils/gcc: 36 commits new 9e257e5367eb 116: onsuccess: #660: 1: Success after binutils/gcc: 48 commits new 7611eabb7473 117: onsuccess: #661: 1: Success after binutils/gcc: 22 commits new 7de3467417a6 118: onsuccess: #662: 1: Success after binutils/gcc: 38 commits new 7e90c2b42ab7 119: onsuccess: #663: 1: Success after binutils/gcc: 26 commits new 6af0ba845953 120: onsuccess: #664: 1: Success after binutils/gcc: 3 commits new e79068ec3b05 121: onsuccess: #665: 1: Success after binutils/gcc: 12 commits new 9118ce73a1ce 122: onsuccess: #666: 1: Success after binutils/gcc: 50 commits new a0b8746e9132 123: onsuccess: #667: 1: Success after binutils/gcc: 81 commits new b1efeb24c873 124: onsuccess: #668: 1: Success after binutils/gcc: 36 commits new adc4841e45dc 125: onsuccess: #669: 1: Success after binutils/gcc: 36 commits new 351b353e2e20 126: onsuccess: #670: 1: Success after binutils/gcc: 43 commits new 85cb8841ff58 127: onsuccess: #671: 1: Success after binutils/gcc: 10 commits new fe31d77d28a2 128: onsuccess: #672: 1: Success after binutils/gcc: 6 commits new 15c1e418f455 129: onsuccess: #673: 1: Success after binutils/gcc: 57 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 (7927544903c1) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check_bootstrap/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 1756 -> 1932 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 39760 -> 40448 bytes 04-build_abe-bootstrap/console.log.xz | Bin 272832 -> 272448 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3836 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2336 -> 2904 bytes 07-check_regression/console.log.xz | Bin 4584 -> 5456 bytes 07-check_regression/mail-body.txt | 27 - 07-check_regression/results.compare | 31 +- 07-check_regression/results.compare2 | 60 +- 08-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 3651216 -> 3655804 bytes sumfiles/g++.sum | 133 +- sumfiles/gcc.log.xz | Bin 3309404 -> 3308980 bytes sumfiles/gcc.sum | 5181 ++++++++++++++------------- sumfiles/gfortran.log.xz | Bin 1093588 -> 1089028 bytes sumfiles/gfortran.sum | 49 +- sumfiles/libatomic.log.xz | Bin 2352 -> 2352 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 225752 -> 225444 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2724 -> 2728 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 472760 -> 473312 bytes sumfiles/libstdc++.sum | 10 +- 32 files changed, 2828 insertions(+), 2804 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (766295035049 -> 2dbae0d63be6)

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 766295035049 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] discards 64c8f2cfc29c 130: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] discards 87d9ccb86d2a 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] discards b8eda383c99e 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] discards eef572e8a600 127: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] discards 7e0f8c219a3a 126: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] discards d7f9517b60f9 125: onsuccess: #658: 1: Success after linux: 3224 commits discards f7637c814c85 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 4849f5a59edc 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 3e6c5f2db956 122: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] discards fd5f483e00af 121: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] discards efc477c0e91a 120: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] discards 0e40727cbd79 119: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] discards 44a853aff1fe 118: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] discards 6edf1b2705b2 117: onsuccess: #648: 1: Success after binutils/gcc/linux/ [...] discards 2ec19ce1416c 116: onsuccess: #647: 1: Success after linux: 3 commits discards 12c123d02083 115: onsuccess: #645: 1: Success after binutils: 27 commits discards b60f3506d010 114: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] discards e5f8874ef003 113: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] discards 3fc17744dfe2 112: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] discards 7716603491d1 111: onsuccess: #640: 1: Success after binutils/gcc/linux/ [...] discards 23afd67168dd 110: onsuccess: #639: 1: Success after binutils/gcc/linux/ [...] discards 6c57689e2345 109: onsuccess: #638: 1: Success after binutils/gcc/linux/ [...] discards c3a21ca5db87 108: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] discards ac9a0019eea4 107: onsuccess: #636: 1: Success after binutils/gcc/linux/ [...] discards 1a9b58ef6f5e 106: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] discards 960a8ec92587 105: onsuccess: #631: 1: Success after binutils/gcc/linux/ [...] discards 7047b0a2283d 104: onsuccess: #630: 1: Success after binutils/gcc/linux/ [...] discards 6d3cdfa04b8e 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 6 [...] discards 2987078a2191 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/ [...] discards 08f77262610e 101: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] discards 91503f423f31 100: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] discards 8abfea436ee3 99: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards d9abb1338a72 98: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 6a4e83e093fc 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 1fe35031ca25 96: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards dca4608027de 95: onsuccess: #619: 1: Success after binutils: 5 commits discards e81dc12dccce 94: onsuccess: #616: 1: Success after binutils: 2 commits discards d5094ac6397f 93: onsuccess: #613: 1: Success after binutils: 19 commits discards a19666f8d756 92: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards dfef163f1230 91: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards d4f292b033bd 90: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards c8c26d26fafa 89: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 985ffc051e4f 88: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards ab902d319126 87: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 172f8a59d120 86: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards dbeb39b2f2d2 85: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 07782e0552d8 84: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 0a6ae4378c1e 83: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 49e0842d24ca 82: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards c83667f99d78 81: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 0c4ac9747c8f 80: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 884ed3200fb9 79: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards ab7d00375b11 78: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 5c901b77fa03 77: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 7dfa5c1f9bfa 76: onsuccess: #592: 1: Success after linux: 63 commits discards 6e7dbf42e700 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 859acebf987f 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 8aa5d48f9ff9 73: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards b7d71134aaf2 72: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards 26d937dc95ee 71: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards 972d07a90cab 70: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards 9a023f3d35d1 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards 4c2ad822ebed 68: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] discards 350875b4b851 67: onsuccess: #582: 1: Success after binutils/gcc/linux/g [...] discards d3e369ba5e39 66: onsuccess: #581: 1: Success after binutils/gcc/linux/g [...] discards cf65efee6ab9 65: onsuccess: #580: 1: Success after binutils/gcc/linux/g [...] discards f2c5edb6d31e 64: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards 0cba8671547b 63: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 0674746c39f9 62: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 64a8a982130e 61: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards deb08ddbf496 60: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards fa38a2c6a938 59: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] discards 68f7ec1dc488 58: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] discards 210c6b6e1f2e 57: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] discards 0a15426c35ed 56: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 8b2ed89057ea 55: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] discards 0875a840816a 54: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards d1f1f0eefac3 53: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 3e7dd98315c8 52: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards b96a9f50f42e 51: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 835e5e5d6f7f 50: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 6b4ddb5f84a5 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 28778f95f5f2 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 767367122681 47: onsuccess: #556: 1: Success after binutils: 12 commits discards a1c57f61255e 46: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards 63cb332ceb8c 45: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 088abfb9435a 44: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 67a7d980af99 43: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards a4e69ee0aea6 42: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 332cb82de57e 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/g [...] discards 7271e329983d 40: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 5e5d2266389e 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/g [...] discards 3f4949e4dfb3 38: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards 70dd465d1248 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/g [...] discards 319ce81d23c1 36: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards 5307b4cace41 35: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards 2a2931faa8a8 34: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards 233b84402dfa 33: onsuccess: #540: 1: Success after binutils/gcc/linux/g [...] discards 0234014e831a 32: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards c9808e2003d8 31: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new 3f24087a2e3a 31: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new b0504f8aa8b5 32: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new 29486ddad58e 33: onsuccess: #540: 1: Success after binutils/gcc/linux/g [...] new 9cd620fe602f 34: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new 3fb640a610cb 35: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new 40b142abd1c4 36: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 99ceea4e46a2 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/g [...] new 97e58c1b148e 38: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 5f1ff6d4385b 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/g [...] new 88ca3ef00d3c 40: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new dd50305d0d2c 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/g [...] new a69b7337a72f 42: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new a0fcedd90a39 43: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new c84a113e4c6e 44: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 74acb9b97824 45: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 033d378e6d57 46: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new 8e5e69edc420 47: onsuccess: #556: 1: Success after binutils: 12 commits new 2bbd36a82bc8 48: onsuccess: #559: 1: Success after binutils: 6 commits new cbb1ac8e5174 49: onsuccess: #562: 1: Success after binutils: 9 commits new 1187b5ae6fba 50: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new f9c3da3ecf34 51: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 5034236444b6 52: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new e9c148850f4e 53: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new cba5fbb5d643 54: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 368dfc116b9e 55: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] new 531b43164139 56: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new f0f3e836607b 57: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] new fc30157a368b 58: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] new 1d1d521e921a 59: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] new 2a413c9c5e0b 60: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new 4c89cdcdb448 61: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 993018ca0956 62: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 97099850f209 63: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 2a067db2154b 64: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new c61fc843b4a9 65: onsuccess: #580: 1: Success after binutils/gcc/linux/g [...] new 69f103fe739d 66: onsuccess: #581: 1: Success after binutils/gcc/linux/g [...] new f3191386759f 67: onsuccess: #582: 1: Success after binutils/gcc/linux/g [...] new c318535421f2 68: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] new 6e0a16899466 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new 5c4c276daa07 70: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new f304b181b0f2 71: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new e15b332a88fa 72: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 61491829b310 73: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 921bb297cb46 74: onsuccess: #590: 1: Success after binutils: 16 commits new 6ec3a88ea93e 75: onsuccess: #591: 1: Success after gcc: 25 commits new 2a8ec092ba94 76: onsuccess: #592: 1: Success after linux: 63 commits new 5cf167672653 77: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new e75d1d60fa23 78: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new f0775ee616a3 79: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 9fdcc5007247 80: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new d73157d3efe9 81: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 29e1a0ee12dd 82: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new 0dd98fdb7ab5 83: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new 97450b214fa0 84: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 5e19683635ea 85: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new eb32b20d85a7 86: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new d99a6836d9cf 87: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 849aa217f9e0 88: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new 30c1fce85ee8 89: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new a0f31d8b71f6 90: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 9c2ef716390c 91: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 162f8d53352a 92: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 515a419bbce2 93: onsuccess: #613: 1: Success after binutils: 19 commits new 1a59b4e3efab 94: onsuccess: #616: 1: Success after binutils: 2 commits new 59f5807df89d 95: onsuccess: #619: 1: Success after binutils: 5 commits new cb87c431a608 96: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 41999ff7c696 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 51e87b2c3edc 98: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new f0b0b8658f65 99: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new ccd6ee6b7bdd 100: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] new 2db369ec1357 101: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] new a106341a9bfb 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/ [...] new 8777d96d34e1 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 6 [...] new d08233613c70 104: onsuccess: #630: 1: Success after binutils/gcc/linux/ [...] new a2d74f495a95 105: onsuccess: #631: 1: Success after binutils/gcc/linux/ [...] new ad515de011b3 106: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] new 6d0bfad489e7 107: onsuccess: #636: 1: Success after binutils/gcc/linux/ [...] new c2d7b7085e30 108: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] new e2993caf0bd7 109: onsuccess: #638: 1: Success after binutils/gcc/linux/ [...] new bc6f5986e098 110: onsuccess: #639: 1: Success after binutils/gcc/linux/ [...] new 7bee06f972cf 111: onsuccess: #640: 1: Success after binutils/gcc/linux/ [...] new 4304dbccfd12 112: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] new bfc822b064a0 113: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] new b175c2d883c5 114: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] new 1e6aeb12aab3 115: onsuccess: #645: 1: Success after binutils: 27 commits new 04ada6d4cc58 116: onsuccess: #647: 1: Success after linux: 3 commits new 2b2054e3a61c 117: onsuccess: #648: 1: Success after binutils/gcc/linux/ [...] new e0de1b6d7796 118: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] new 32cd61b86119 119: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] new 4cd1e403be16 120: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] new 2e7b3737e7a9 121: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] new 7cbac490ccf0 122: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] new 581e45c32f8f 123: onsuccess: #655: 1: Success after binutils: 22 commits new 7219e4079e45 124: onsuccess: #657: 1: Success after glibc: 2 commits new 0a3b2ab81720 125: onsuccess: #658: 1: Success after linux: 3224 commits new fa1fdaacae88 126: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] new 4bba01e7c28e 127: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] new 8e932b6835f3 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new b89d9edd2207 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new 41ebe6951b2b 130: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] new be9655459fc2 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] new 2dbae0d63be6 132: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] 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 (766295035049) \ 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 1732 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 40332 -> 40076 bytes 04-build_abe-gcc/console.log.xz | Bin 213708 -> 215504 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8624 -> 9168 bytes 07-build_abe-glibc/console.log.xz | Bin 243628 -> 245040 bytes 08-build_abe-gdb/console.log.xz | Bin 39552 -> 39516 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3840 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2244 -> 2220 bytes 11-check_regression/console.log.xz | Bin 5704 -> 6192 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 27 +-- 12-update_baseline/console.log | 66 +++--- 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 63208 -> 63324 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83832 -> 83872 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 122320 -> 122520 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 30 files changed, 410 insertions(+), 423 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allmodconfig updated (507c9c5f2393 -> 11f1701b5fdb)

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-allmodconfig in repository toolchain/ci/base-artifacts. from 507c9c5f2393 34: onsuccess: #502: 33: Success after binutils/gcc/linux/ [...] new 11f1701b5fdb 35: onsuccess: #503: 33: Success after binutils/gcc/linux/ [...] 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 1772 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32672 -> 32000 bytes 04-build_abe-stage1/console.log.xz | Bin 73240 -> 73336 bytes 05-build_abe-qemu/console.log.xz | Bin 31500 -> 31484 bytes 06-build_linux/console.log.xz | Bin 3716 -> 3700 bytes 08-check_regression/console.log.xz | Bin 4396 -> 4336 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 16 files changed, 23 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (4cbba57de7d3 -> d2972e5ed009)

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 4cbba57de7d3 262: onsuccess: #2078: 1: Success after binutils/gcc/linux [...] discards 3c0794735ae3 261: onsuccess: #2077: 1: Success after binutils/gcc/linux [...] discards 4044a55242b9 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc [...] discards 45b68b7acf14 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards b939887bddd2 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc [...] discards 21129e7a3b90 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...] discards 1bf7ef45084d 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] discards 1ef383591eb7 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] discards 7e31934ce9d6 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] discards c2201a011842 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 70e7a6973b5d 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 34bbc5be0cf6 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] discards 999940d372c4 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] discards d850e92f788c 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] discards 6978ce351d69 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] discards 83ca901d5f16 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] discards 9b16a6036ecf 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] discards ba74d3454fb8 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] discards 8c6aca8da9d0 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] discards c4d4c5f5633b 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] discards bd8c58502fa2 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] discards bf46e71625fd 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] discards 7c3f15417252 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] discards df729fe13b59 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] discards e2e7a154d5d3 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] discards eddd493760fd 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] discards 9edb93435e3d 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] discards d6d497abf479 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] discards 3769a7412cd6 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] discards 3270e2bd0d36 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] discards 27dfe2bf72ee 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 72aa1d188f43 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards e936c6ece367 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] discards 4c1828a409ee 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] discards dd10d2482379 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] discards a73966e88299 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] discards eb455c3b1bb1 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] discards 513652e7f00d 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] discards 4223010f5699 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] discards d72c2686d888 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] discards 253ed7d688f6 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] discards 3215808c1f68 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards a488eef91a68 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] discards 05b5f39dd43a 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] discards 115445641038 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards b63373f2e042 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] discards 2ea9dedc1cb8 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] discards e3adeda0c438 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] discards 055718d3558e 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] discards 63ca4b101893 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 4044950ff12c 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 22eca23b0350 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 7b9868ed0068 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 8b21681b6535 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards cff84f7d1dc0 208: onsuccess: #2012: 1: Success after linux: 12 commits discards feb92b916a23 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 5004688fb720 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 8be432d18b63 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 7ac131054e9f 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] discards 59d4a9a28e69 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] discards 588750b2725e 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] discards 2fdacd8ff1e3 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards c7aadd737162 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] discards d0a5fa7fda55 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 1c33f2d97dac 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] discards 976e66f40434 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] discards 67ecbcd4ccd9 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] discards 89331b2439d8 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] discards 1fa3145f65b1 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 4861724d1fb4 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards dcf8c22cd659 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] discards 3d6ac1270692 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] discards a36b3228957a 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] discards 27b3f4aa793a 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] discards dff21db8153a 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] discards 341eb5a4637c 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] discards 279e8a7b5cc5 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] discards 277ec1c779e1 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] discards 75281ff687a2 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] discards 9661504be325 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] discards 984b5fcb17b5 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] discards 65dcbee153c8 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] discards 768139445723 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] discards 85de1d4fa604 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] discards acfe470e801e 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] discards 778f09be6523 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] discards e045bea8419c 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] discards b25bbee023d4 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] discards 8ef35b60ab1f 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] discards 9da47b3c35b1 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] discards 500311c31c65 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] discards d2150fb839a7 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] discards a64306f73563 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] discards 6318cca6e152 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] discards 46686bb998e8 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] discards 43e6cb01a217 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] discards 990dd7790ce2 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] discards 279c4773396c 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] discards 31151be724f6 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] discards d0d613b23ef2 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 743766e8d5a8 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] new 3ca1f69a45ba 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] new 8001247fdd52 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 88d713a0b485 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] new 8ef2dd080b19 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] new 63747928634e 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] new f23b71934b98 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] new dd526e59f021 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] new e49f2e428a9c 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] new 78f1fdab48d1 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] new 397fc95a7d7d 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] new 1d7ba1735c45 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] new 3945fd6d0342 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] new 623fdb5009e6 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] new 7348ae9eb5ea 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] new 813e71a80c0c 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] new 10a119e913ba 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] new 47ca10db0992 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] new 00f6356de04f 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] new f06f7b678338 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] new d1cd54583eef 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] new 393e6e5517a4 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] new 7d96c529f3c9 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] new ca1e0ba5f33b 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] new 6f53500b8a99 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] new 27ca640e2b4d 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] new c28300526abe 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] new d4cdf1b3d402 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] new 4ab98230e2bc 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] new 21b9f15b3dd9 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] new f696d2f2cbee 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] new 83f52e0a7ac8 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] new 9bbf1f7dfe42 193: onsuccess: #1992: 1: Success after binutils: 151 commits new c78c498594ac 194: onsuccess: #1995: 1: Success after linux: 517 commits new 44c0b7554674 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] new fd1b2eb997e2 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] new 49432efd3896 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] new c40461b98c48 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] new 1975716838b1 199: onsuccess: #2000: 1: Success after gcc: 5 commits new a2fb9428a139 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] new b00c79027a0f 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 6add64085e1f 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] new 2799ae5d9f03 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] new 24af50bf4aa1 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] new 17b95498132e 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 25f12be41b65 206: onsuccess: #2007: 1: Success after gcc: 2 commits new a2efd213938b 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 6fcc464bdab5 208: onsuccess: #2012: 1: Success after linux: 12 commits new cdac899720b0 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 7cede4f1e7f5 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 18134e5b6a84 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 772ed211fc5a 212: onsuccess: #2022: 1: Success after linux: 3 commits new 4f6267ab8722 213: onsuccess: #2024: 1: Success after binutils: 3 commits new be7adae18a0f 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] new 5c9aea790f0a 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] new 7b7e6d48ffd8 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] new c643f31197bb 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] new e2dd23dadb33 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 88bb5aeba80e 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] new fe58ce9642ec 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] new 11a2d6a79edb 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 15edb61dd5c3 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] new e23345300af1 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] new 107f09769b09 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] new b158112e50b0 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] new c3e6968ad634 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] new adc1112e4544 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] new 63458fd80ce5 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] new e46ade7344e8 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] new 4036938de0f8 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] new 0611aff54d6c 231: onsuccess: #2047: 1: Success after gcc: 4 commits new e68ac7af0699 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 535ac7dcc25e 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] new d61c6ddd9827 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] new afca2948ac69 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] new e662a23c60ef 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] new 227ed58e31fa 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] new 4b410fa456b6 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] new 5ea6db8bcf2c 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] new 3ad112dd93cd 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] new 1be99e1c47da 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] new 9ea40d7214d0 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] new 72c2e1692a31 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] new a461d4aba473 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] new 0e65dc6cbab8 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] new 5b31d6b7edd2 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] new 8525eabb8bf3 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] new 99878e815061 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] new 6617ad46dbff 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] new 56a7a31f2186 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] new 3b5fe8869081 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] new 240c5d033abb 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 641ce7f59168 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 7a3baba2b923 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] new d3fb5ee0c0ec 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] new 61586e97e8de 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] new 10e37d322156 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...] new b1345cdd40b1 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc [...] new 976bf5cf9653 259: onsuccess: #2075: 1: Success after glibc: 2 commits new f37bee922763 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc [...] new b26c9c8dc3ef 261: onsuccess: #2077: 1: Success after binutils/gcc/linux [...] new fb2c01bef3ee 262: onsuccess: #2078: 1: Success after binutils/gcc/linux [...] new d2972e5ed009 263: onsuccess: #2079: 1: Success after binutils/gcc/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 (4cbba57de7d3) \ 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 1772 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 32016 -> 31984 bytes 04-build_abe-stage1/console.log.xz | Bin 92028 -> 92892 bytes 06-build_abe-linux/console.log.xz | Bin 9260 -> 9224 bytes 07-build_abe-glibc/console.log.xz | Bin 237024 -> 236440 bytes 08-build_abe-stage2/console.log.xz | Bin 225160 -> 226256 bytes 09-build_abe-gdb/console.log.xz | Bin 40120 -> 38952 bytes 10-build_abe-qemu/console.log.xz | Bin 31004 -> 30684 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3940 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2508 -> 3072 bytes 13-check_regression/console.log.xz | Bin 6256 -> 5736 bytes 13-check_regression/mail-body.txt | 30 - 13-check_regression/results.compare | 26 +- 13-check_regression/results.compare2 | 41 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 32 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.xz | Bin 2660828 -> 2682368 bytes sumfiles/g++.sum | 18 +- sumfiles/gcc.log.xz | Bin 2267784 -> 2233816 bytes sumfiles/gcc.sum | 2430 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 895956 -> 890476 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214020 -> 214036 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 444692 -> 425724 bytes sumfiles/libstdc++.sum | 8 +- 38 files changed, 1321 insertions(+), 1384 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_eabi_stm32/gnu_eabi-master-arm_eabi-coremark-O3 updated (74613c2f1225 -> 65f8290757a5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_gnu_eabi_stm32/gnu_eabi-master-arm_eabi-coremark-O3 in repository toolchain/ci/base-artifacts. from 74613c2f1225 24: onsuccess: #345: 1: [TCWG CI] No change after binutils [...] new 65f8290757a5 25: onsuccess: #346: 1: [TCWG CI] No change after binutils [...] 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 2012 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2804 bytes 03-build_abe-binutils/console.log.xz | Bin 32384 -> 31916 bytes 04-build_abe-stage1/console.log.xz | Bin 89640 -> 90264 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-newlib/console.log.xz | Bin 16448 -> 15228 bytes 07-build_abe-stage2/console.log.xz | Bin 163056 -> 161868 bytes 08-benchmark/benchmark-build.log | 78 ++++++++++---------- 08-benchmark/benchmark.log | 76 ++++++++++--------- 08-benchmark/console.log.xz | Bin 3832 -> 3768 bytes 09-check_regression/console.log.xz | Bin 5020 -> 4956 bytes 09-check_regression/results-vs-first.log | 82 ++++++++++----------- 09-check_regression/results-vs-prev.log | 82 ++++++++++----------- 10-update_baseline/console.log | 8 +- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/Mean/results-metadata.json | 12 +-- .../squad-vs-first/coremark/results-metadata.json | 12 +-- dashboard/squad-vs-first/dashboard-push-squad.sh | 10 +-- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/newlib_rev | 2 +- mail/jira-body.txt | 34 ++++----- mail/mail-body.txt | 34 ++++----- mail/mail-subject.txt | 2 +- manifest.sh | 28 +++---- results_id | 2 +- 26 files changed, 232 insertions(+), 236 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[binutils-gdb] branch master updated (043f950abeb -> 9d099144928)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 043f950abeb sim: ppc: change spreg switch table generation to compile-time new b3737aadf1b Re: x86: remove i386-opc.c new 9d099144928 PR29915, bfdio.c does not compile with mingw.org's MinGW The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: bfd/bfdio.c | 11 +++++------ bfd/config.in | 4 ++++ bfd/configure | 12 ++++++++++++ bfd/configure.ac | 1 + opcodes/po/POTFILES.in | 1 - 5 files changed, 22 insertions(+), 7 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022