Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (1f312c2286 -> 3292116eaf)

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 1f312c2286 154: onsuccess: #583: 1: Success after linux: 10 commits discards 2d82d340b5 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 9ac07b4d0d 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 16ca4a973a 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 3fea68e398 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards 4c0ead684b 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards dfc1e11b1f 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] discards 894a828974 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards ada7782e88 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits discards b9b891a1fa 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits discards f4fcb19e97 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits discards 3b14cdb975 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards f1084c64d0 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits discards 45d546c293 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] discards 719d43361c 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards ee3e29b90a 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards 621caaae9d 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 3996f801d7 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards 203add1bda 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] discards 3a769123f0 135: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards ee0ccbe4e5 134: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards 258255004d 133: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 67d225c63f 132: onsuccess: #559: 1: Success after binutils/gcc/linux/gd [...] discards 074963bad5 131: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] discards a7159e72b7 130: onsuccess: #557: 1: Success after binutils/gcc/linux/gl [...] discards 086ce4fd3a 129: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] discards ed1128e8f6 128: onsuccess: #555: 1: Success after binutils/gcc/linux/gd [...] discards a1af37695a 127: onsuccess: #554: 1: Success after binutils/gcc/linux/gl [...] discards c3f58d7704 126: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] discards b6d36ef750 125: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 1a9bbc190e 124: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards d4e11304d2 123: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] discards 6f33ad7afc 122: onsuccess: #549: 1: Success after binutils/gcc/linux/gd [...] discards dc2b3b518a 121: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] discards 8e3d87a2d3 120: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] discards b5d2a4b6fc 119: onsuccess: #546: 1: Success after binutils/gcc/linux/gd [...] discards 5de10ad370 118: onsuccess: #545: 1: Success after binutils/gcc/linux/gd [...] discards 246ba20ba9 117: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] discards 343c022ee2 116: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 77c2b27422 115: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards 59e7bf3762 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...] discards 91a68c4c66 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards c25d6d52ab 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] discards ba644e5407 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits discards f60638e091 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards 7858a596f0 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] discards 2dc216c808 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] discards c74765f668 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards ce162f641a 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] discards b35c8ca898 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] discards fe0f63daf2 104: onsuccess: #530: 1: Success after gcc: 7 commits discards bb966886ed 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards 5fbc4c8808 102: onsuccess: #527: 1: Success after binutils: 5 commits discards c7327b86c9 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 0cc655633c 100: onsuccess: #521: 1: Success after binutils: 10 commits discards ad5ec0e1d2 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 4afea52503 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards dd3bbafca6 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards df72beb132 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 1251dfd9a2 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards 67ffa71bf9 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards bf3e6d42f8 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards f6e9a99919 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards c48bd1438d 91: onsuccess: #511: 1: Success after linux: 27 commits discards cad6dbfb62 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 1385041c4c 89: onsuccess: #508: 1: Success after binutils: 12 commits discards cb1f91e355 88: onsuccess: #506: 1: Success after linux: 34 commits discards 8e96f4a061 87: onsuccess: #505: 1: Success after glibc: 7 commits discards ca690bd223 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 96de34560a 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 7ff2dc2a2e 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 982400a09d 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards f19e057866 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards 5bda662eb0 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 245bee61e1 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards ff19b1f673 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards d300306144 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 9f6999b19f 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards 2349211d27 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards 1f49751c08 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 79d9e28aaa 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards 1bc22a08f9 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards 0716e41e84 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards 9fc7a9ee76 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards 787491495d 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards 773cda7508 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 142c75bcf7 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards b5b09a8146 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 660622d673 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards 6a3f5705fe 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards d8915a7b6d 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards ac356a0dab 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards 0368b989a3 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards 0df1ed774f 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards 85d5bcec07 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards bcbda35f88 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards f7fbdcba5a 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards d671fffc89 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards 8a01dff62e 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards 2d6e756764 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards 3a96c0189a 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new a2a0752493 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new fd17103a09 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new 3c4d585835 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new fe6f1558bc 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new 929267984f 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new 493ea321dc 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new a6daca09ff 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new ff34a97f07 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new 44b2ffbea9 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new 45f32e0c64 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new 269300e128 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new fdab6528f7 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new 621c26df40 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new c51a487a84 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 187fe17778 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new cb9f904f68 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new c82b2f09b2 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new 6ea04ae89e 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new 07a5e6981a 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new 7f7239e4ce 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new 678023dcef 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new 84a10cf986 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 5e42fba0fc 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new 94deda1533 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new 55865626ed 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 179af18a89 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 36dfbd52d4 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 162cd992c7 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new fc1954db78 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new 2af0a2e6a9 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new 9d641a2ed9 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 744547eed4 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new df5e2d92ef 86: onsuccess: #503: 1: Success after binutils: 12 commits new e9f77f4682 87: onsuccess: #505: 1: Success after glibc: 7 commits new 31f3c8528d 88: onsuccess: #506: 1: Success after linux: 34 commits new c8b29adc60 89: onsuccess: #508: 1: Success after binutils: 12 commits new c5f51c0d27 90: onsuccess: #510: 1: Success after glibc: 5 commits new 350c860d3b 91: onsuccess: #511: 1: Success after linux: 27 commits new c7b05583bb 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new 54e4404aa4 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 3b3f573e53 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new ea0c0d91b8 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new 81071ea676 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 8d7800c3bf 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 68f222ca44 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new 258dbd44b4 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new a8294e0fdf 100: onsuccess: #521: 1: Success after binutils: 10 commits new 9c30f6d7ee 101: onsuccess: #524: 1: Success after binutils: 2 commits new 52b3bcb2f8 102: onsuccess: #527: 1: Success after binutils: 5 commits new 206c411303 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new dea1ccba02 104: onsuccess: #530: 1: Success after gcc: 7 commits new 0712fbdb92 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] new 106fd6ea11 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] new 7ed5ac9f2b 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 418779a73e 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] new c31e7fc39e 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] new 7ee928bfbd 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 2539f61ae4 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits new 19c3a96e46 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] new cd7c153bb8 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new c9391c3aec 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...] new 783f32cd3d 115: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 469ac3b73d 116: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 416dfa49a3 117: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] new c9b5719202 118: onsuccess: #545: 1: Success after binutils/gcc/linux/gd [...] new 2b33f317cf 119: onsuccess: #546: 1: Success after binutils/gcc/linux/gd [...] new 3fa9fa9392 120: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] new e7f98983af 121: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] new 7db722aef1 122: onsuccess: #549: 1: Success after binutils/gcc/linux/gd [...] new 94f812a420 123: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] new c4d4de88f1 124: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new aa4f5de7c9 125: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 29cab2d864 126: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] new 5f6bf562cb 127: onsuccess: #554: 1: Success after binutils/gcc/linux/gl [...] new 87e9840dcc 128: onsuccess: #555: 1: Success after binutils/gcc/linux/gd [...] new 0578598868 129: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] new 482d9fe3df 130: onsuccess: #557: 1: Success after binutils/gcc/linux/gl [...] new 1f0e2eaa3b 131: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] new be6b356895 132: onsuccess: #559: 1: Success after binutils/gcc/linux/gd [...] new 60550aed9b 133: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new d5ccb3c255 134: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 2ff115b0d8 135: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new a8faaaad93 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] new d63b6ea0f1 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new d047ee68dd 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new aaf8297d0b 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new 36479e3b19 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 9fae00e3b0 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] new 186004b246 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits new d8ecefbaf4 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new 025064081f 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits new 4aee37a597 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits new 64fb9bfe0c 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits new 361b57ccf8 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 1483de65af 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] new b59d386139 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new d897707822 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new ed3604a7a5 151: onsuccess: #579: 1: Success after binutils: 21 commits new 2b7013a4e1 152: onsuccess: #580: 1: Success after gcc: 6 commits new e0144e23f9 153: onsuccess: #582: 1: Success after glibc: 9 commits new 005b7c1cea 154: onsuccess: #583: 1: Success after linux: 10 commits new 3292116eaf 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (1f312c2286) \ 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 1664 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 52944 -> 53400 bytes 04-build_abe-gcc/console.log.xz | Bin 238896 -> 239428 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8824 -> 8812 bytes 07-build_abe-glibc/console.log.xz | Bin 238084 -> 237308 bytes 08-build_abe-gdb/console.log.xz | Bin 50864 -> 51884 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3812 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2708 -> 2200 bytes 11-check_regression/console.log.xz | Bin 4772 -> 5532 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 38 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +-- sumfiles/binutils.log.xz | Bin 62612 -> 62520 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 100456 -> 100544 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 132284 -> 132288 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 29 files changed, 390 insertions(+), 386 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-next-allyesconfig updated (95b0469ca5 -> b743b3131b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-next-allyesconfig in repository toolchain/ci/base-artifacts. from 95b0469ca5 43: onsuccess: #718: 21894: Success after binutils/gcc/linux [...] new b743b3131b 44: onsuccess: #719: 21894: Success after binutils/gcc: 13 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1756 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30444 -> 30604 bytes 04-build_abe-stage1/console.log.xz | Bin 68236 -> 68776 bytes 05-build_abe-qemu/console.log.xz | Bin 31836 -> 31492 bytes 06-build_linux/console.log.xz | Bin 3176 -> 3172 bytes 08-check_regression/console.log.xz | Bin 3692 -> 3252 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 ++++++++++++------------ 14 files changed, 18 insertions(+), 18 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/release-aarch64 updated (974e0d8292 -> 6eff9eb52c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/release-aarch64 in repository toolchain/ci/base-artifacts. from 974e0d8292 46: onsuccess: #249: 1: Success after binutils/gcc: 9 commits new 6eff9eb52c 47: onsuccess: #250: 1: Success after binutils/gcc: 4 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1716 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 38080 -> 38060 bytes 04-build_abe-gcc/console.log.xz | Bin 206704 -> 206640 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3844 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2352 -> 2344 bytes 07-check_regression/console.log.xz | Bin 5576 -> 5356 bytes 07-check_regression/fails.sum | 9 +- 07-check_regression/mail-body.txt | 69 +- 07-check_regression/results.compare | 35 +- 07-check_regression/results.compare2 | 73 +- 07-check_regression/results.regressions | 35 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 71 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 35 +- sumfiles/g++.log.xz | Bin 3492456 -> 3517668 bytes sumfiles/g++.sum | 138 +- sumfiles/gcc.log.xz | Bin 3011580 -> 3001524 bytes sumfiles/gcc.sum | 4408 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1036800 -> 1034712 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2188 -> 2180 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202440 -> 202724 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2548 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 437444 -> 433728 bytes sumfiles/libstdc++.sum | 10 +- 34 files changed, 2508 insertions(+), 2471 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[gcc] branch master updated (44baa34157c -> 345dffd0d4e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 44baa34157c Initial Emeraldrapids Support new 8692b15ae7c ubsan: Avoid narrowing of multiply for -fsanitize=signed-in [...] new 345dffd0d4e generic-match-head: Don't assume GENERIC folding is done on [...] 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: gcc/convert.cc | 8 ++++++++ gcc/fold-const.cc | 4 +++- gcc/generic-match-head.cc | 5 +++-- gcc/testsuite/c-c++-common/ubsan/pr108256.c | 27 ++++++++++++++++++++++++++ gcc/testsuite/gcc.c-torture/compile/pr108237.c | 14 +++++++++++++ 5 files changed, 55 insertions(+), 3 deletions(-) create mode 100644 gcc/testsuite/c-c++-common/ubsan/pr108256.c create mode 100644 gcc/testsuite/gcc.c-torture/compile/pr108237.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-next-allmodconfig updated (3901d6bdb7 -> c07dc4b291)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-next-allmodconfig in repository toolchain/ci/base-artifacts. from 3901d6bdb7 38: onsuccess: #732: all: Success after binutils/gcc/linux: [...] new c07dc4b291 39: onsuccess: #733: all: Success after binutils/gcc: 13 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1748 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 30380 -> 30840 bytes 04-build_abe-stage1/console.log.xz | Bin 68948 -> 68708 bytes 05-build_abe-qemu/console.log.xz | Bin 31608 -> 31884 bytes 06-build_linux/console.log.xz | Bin 3080 -> 3072 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3528 -> 3188 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 ++++++++++++------------ 16 files changed, 22 insertions(+), 22 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap updated (8cf8bf8b19 -> e9614b57d7)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap in repository toolchain/ci/base-artifacts. discards 8cf8bf8b19 491: onsuccess: #1923: 2: Success after binutils/gcc: 7 commits discards 0aa472a132 490: onsuccess: #1922: 2: Success after binutils/gcc: 17 commits discards a84a850c26 489: onsuccess: #1921: 2: Success after binutils/gcc: 26 commits discards 7c1eaf2d6f 488: onsuccess: #1920: 2: Success after binutils: 4 commits discards 2a78bd24be 487: onsuccess: #1919: 2: Success after binutils/gcc: 12 commits discards 7634937897 486: onsuccess: #1918: 2: Success after binutils/gcc: 7 commits discards 44bb1ca9a7 485: onsuccess: #1917: 2: Success after binutils/gcc: 3 commits discards 60390c0f0b 484: onsuccess: #1916: 2: Success after binutils/gcc: 8 commits discards 2841db3f24 483: onsuccess: #1915: 2: Success after binutils/gcc: 5 commits discards 5551fb6fe3 482: onsuccess: #1914: 2: Success after binutils/gcc: 5 commits discards 08944178da 481: onsuccess: #1913: 2: Success after binutils/gcc: 8 commits discards 273c606fae 480: onsuccess: #1912: 2: Success after binutils/gcc: 3 commits discards 0aeab0b33b 479: onsuccess: #1911: 2: Success after gcc: 2 commits discards 24669a6abe 478: onsuccess: #1910: 2: Success after binutils: 9 commits discards e26ac673a5 477: onsuccess: #1909: 2: Success after binutils: 4 commits discards 536080b787 476: onsuccess: #1908: 2: Success after binutils/gcc: 2 commits discards 9d25bfbe47 475: onsuccess: #1907: 2: Success after binutils/gcc: 4 commits discards 99fcfcd939 474: onsuccess: #1906: 2: Success after binutils/gcc: 4 commits discards e09b6bb2fb 473: onsuccess: #1905: 2: Success after basepoints/gcc-13-49 [...] discards f78b9b293a 472: onsuccess: #1904: 2: Success after binutils/gcc: 2 commits discards 8e4e9ee138 471: onsuccess: #1903: 2: Success after gcc: 17 commits discards 1e26176dba 470: onsuccess: #1902: 2: Success after gdb-13-branchpoint-2 [...] discards 6e41654f14 469: onsuccess: #1901: 2: Success after binutils/gcc: 2 commits discards 2be0316f6a 468: onsuccess: #1900: 2: Success after binutils/gcc: 4 commits discards 54146c37d0 467: onsuccess: #1899: 2: Success after basepoints/gcc-13-49 [...] discards e12af7489f 466: onsuccess: #1898: 2: Success after basepoints/gcc-13-49 [...] discards dd90f6bbe5 465: onsuccess: #1897: 2: Success after binutils/gcc: 5 commits discards 8911e3bc9e 464: onsuccess: #1896: 2: Success after binutils/gcc: 15 commits discards b0f0682e1c 463: onsuccess: #1895: 2: Success after basepoints/gcc-13-48 [...] discards 01508de9e1 462: onsuccess: #1894: 2: Success after binutils: 9 commits discards 02b9e13c4a 461: onsuccess: #1893: 2: Success after binutils/gcc: 3 commits discards a55722f376 460: onsuccess: #1892: 2: Success after basepoints/gcc-13-48 [...] discards 4a7317ee42 459: onsuccess: #1891: 2: Success after binutils: 2 commits discards 4bb646251b 458: onsuccess: #1890: 2: Success after binutils/gcc: 3 commits discards 8553e511fb 457: onsuccess: #1889: 2: Success after binutils: 2 commits discards 1a62144967 456: onsuccess: #1888: 2: Success after basepoints/gcc-13-48 [...] discards 35fe29834d 455: onsuccess: #1887: 2: Success after binutils: 13 commits discards c4f8e28433 454: onsuccess: #1886: 2: Success after binutils/gcc: 9 commits discards ae4544be69 453: onsuccess: #1885: 2: Success after binutils/gcc: 4 commits discards 5c5d816f01 452: onsuccess: #1884: 2: Success after binutils/gcc: 8 commits discards 9cb52e2080 451: onsuccess: #1883: 2: Success after binutils/gcc: 4 commits discards 8448cb9715 450: onsuccess: #1882: 2: Success after binutils/gcc: 40 commits discards c59e880b00 449: onsuccess: #1881: 2: Success after binutils/gcc: 19 commits discards 641d5f5a36 448: onsuccess: #1880: 2: Success after binutils/gcc: 24 commits discards 91dd2d8f51 447: onsuccess: #1879: 2: Success after binutils/gcc: 9 commits discards fa54c20797 446: onsuccess: #1878: 2: Success after binutils/gcc: 10 commits discards a14313e35f 445: onsuccess: #1877: 2: Success after binutils: 18 commits discards 2fef5b73c4 444: onsuccess: #1876: 2: Success after binutils/gcc: 5 commits discards c4ed5f2fdb 443: onsuccess: #1875: 2: Success after binutils/gcc: 5 commits discards a009b838bc 442: onsuccess: #1874: 2: Success after binutils/gcc: 11 commits discards ba24b36de9 441: onsuccess: #1873: 2: Success after binutils/gcc: 41 commits discards b097f42677 440: onsuccess: #1872: 2: Success after binutils/gcc: 9 commits discards 8daa8b87e2 439: onsuccess: #1871: 2: Success after binutils/gcc: 3 commits discards 5d02af9a2d 438: onsuccess: #1870: 2: Success after binutils/gcc: 13 commits discards 954d518c78 437: onsuccess: #1869: 1: Success after gcc: 5 commits discards cee4d57ad1 436: force: #1868: 1: Failure after basepoints/gcc-13-4795-g [...] discards 762ada186c 435: force: #1867: 2: Success after gcc: 2 commits discards 873b26eae3 434: onsuccess: #1860: 2: Success after binutils: 6 commits discards a4896a9615 433: onsuccess: #1858: 2: Success after binutils/gcc: 27 commits discards e67dfc4561 432: onsuccess: #1857: 2: Success after binutils/gcc: 9 commits discards 65776e6ec3 431: onsuccess: #1856: 2: Success after binutils/gcc: 2 commits discards 886e426e31 430: onsuccess: #1855: 2: Success after basepoints/gcc-13-47 [...] discards 8d2909b679 429: onsuccess: #1854: 2: Success after binutils/gcc: 3 commits discards e542c29158 428: onsuccess: #1853: 2: Success after binutils/gcc: 3 commits discards f54f05b13c 427: onsuccess: #1852: 2: Success after binutils/gcc: 3 commits discards c4e28bb769 426: onsuccess: #1851: 2: Success after basepoints/gcc-13-47 [...] discards 566da5c0d2 425: onsuccess: #1850: 2: Success after binutils: 9 commits discards 0973ffaaff 424: onsuccess: #1849: 2: Success after binutils/gcc: 10 commits discards e8c29314fb 423: onsuccess: #1848: 2: Success after binutils/gcc: 9 commits discards d533ce68a3 422: onsuccess: #1847: 2: Success after binutils/gcc: 14 commits discards 5d436a3718 421: onsuccess: #1846: 2: Success after binutils/gcc: 5 commits discards b6076f4f4a 420: onsuccess: #1845: 2: Success after binutils/gcc: 12 commits discards baf29aba53 419: onsuccess: #1844: 2: Success after binutils/gcc: 9 commits discards 2934f1e5b0 418: onsuccess: #1843: 2: Success after binutils/gcc: 13 commits discards 28461e21d8 417: onsuccess: #1842: 2: Success after gcc: 2 commits discards 8685c4ea34 416: onsuccess: #1841: 2: Success after binutils/gcc: 3 commits discards a5abdfa003 415: onsuccess: #1840: 2: Success after gcc: 6 commits discards 522eb99b14 414: onsuccess: #1839: 2: Success after binutils/gcc: 23 commits discards b9c67e219c 413: onsuccess: #1838: 2: Success after binutils/gcc: 6 commits discards 4f814d6016 412: onsuccess: #1837: 2: Success after binutils/gcc: 12 commits discards b98a8a3f2a 411: onsuccess: #1836: 2: Success after binutils/gcc: 11 commits discards 3677069bb5 410: onsuccess: #1835: 2: Success after binutils/gcc: 52 commits discards 653da12557 409: onsuccess: #1834: 2: Success after binutils/gcc: 4 commits discards 244df3f316 408: onsuccess: #1833: 2: Success after binutils/gcc: 6 commits discards 13f6dd760b 407: onsuccess: #1832: 2: Success after binutils/gcc: 11 commits discards 777cf3bbf7 406: onsuccess: #1831: 2: Success after binutils/gcc: 24 commits discards 7c258ea348 405: onsuccess: #1830: 2: Success after binutils/gcc: 8 commits discards eab75fc541 404: onsuccess: #1829: 2: Success after binutils/gcc: 2 commits discards ddc219fd1b 403: onsuccess: #1828: 2: Success after gcc: 5 commits discards 8e197b889c 402: onsuccess: #1827: 2: Success after binutils/gcc: 5 commits discards 95c91831f7 401: onsuccess: #1826: 2: Success after binutils/gcc: 3 commits discards 1631d4d4fe 400: onsuccess: #1825: 2: Success after binutils/gcc: 13 commits discards 32b751a600 399: onsuccess: #1824: 2: Success after binutils: 6 commits discards 6bad1df79b 398: onsuccess: #1823: 2: Success after binutils/gcc: 6 commits discards cd850e0539 397: onsuccess: #1822: 2: Success after basepoints/gcc-13-45 [...] discards 80ff1f9c3a 396: onsuccess: #1821: 2: Success after binutils/gcc: 13 commits discards c1e5d10137 395: onsuccess: #1820: 2: Success after binutils/gcc: 25 commits discards 0aa8b8469d 394: onsuccess: #1818: 2: Success after binutils/gcc: 6 commits discards 003ea13dbe 393: onsuccess: #1817: 2: Success after binutils/gcc: 11 commits discards 4e1e76e3f3 392: onsuccess: #1816: 2: Success after gcc: 3 commits discards 0fd2fcf97c 391: onsuccess: #1815: 2: Success after binutils/gcc: 6 commits new bd3d3555c4 391: onsuccess: #1815: 2: Success after binutils/gcc: 6 commits new e530a60e11 392: onsuccess: #1816: 2: Success after gcc: 3 commits new 289ff0d9df 393: onsuccess: #1817: 2: Success after binutils/gcc: 11 commits new 16323175b4 394: onsuccess: #1818: 2: Success after binutils/gcc: 6 commits new ff224f7389 395: onsuccess: #1820: 2: Success after binutils/gcc: 25 commits new e1e868ab22 396: onsuccess: #1821: 2: Success after binutils/gcc: 13 commits new 645ee5d356 397: onsuccess: #1822: 2: Success after basepoints/gcc-13-45 [...] new 8482a4e536 398: onsuccess: #1823: 2: Success after binutils/gcc: 6 commits new 2d36d30876 399: onsuccess: #1824: 2: Success after binutils: 6 commits new b69f66245c 400: onsuccess: #1825: 2: Success after binutils/gcc: 13 commits new 8a2ae8490e 401: onsuccess: #1826: 2: Success after binutils/gcc: 3 commits new 909e0b0e4b 402: onsuccess: #1827: 2: Success after binutils/gcc: 5 commits new 0314a9fa6c 403: onsuccess: #1828: 2: Success after gcc: 5 commits new 7d809bad8f 404: onsuccess: #1829: 2: Success after binutils/gcc: 2 commits new ae45588ab6 405: onsuccess: #1830: 2: Success after binutils/gcc: 8 commits new dc278f8b78 406: onsuccess: #1831: 2: Success after binutils/gcc: 24 commits new 234727be9d 407: onsuccess: #1832: 2: Success after binutils/gcc: 11 commits new 2105d1265c 408: onsuccess: #1833: 2: Success after binutils/gcc: 6 commits new 9b27cea93c 409: onsuccess: #1834: 2: Success after binutils/gcc: 4 commits new 88cf28d734 410: onsuccess: #1835: 2: Success after binutils/gcc: 52 commits new e34a0f37d1 411: onsuccess: #1836: 2: Success after binutils/gcc: 11 commits new 4cfcc736d0 412: onsuccess: #1837: 2: Success after binutils/gcc: 12 commits new 8a68ae5cf7 413: onsuccess: #1838: 2: Success after binutils/gcc: 6 commits new 26116b395d 414: onsuccess: #1839: 2: Success after binutils/gcc: 23 commits new 31b3b13a67 415: onsuccess: #1840: 2: Success after gcc: 6 commits new 7051ce33d2 416: onsuccess: #1841: 2: Success after binutils/gcc: 3 commits new b1ed491aef 417: onsuccess: #1842: 2: Success after gcc: 2 commits new 70ab557187 418: onsuccess: #1843: 2: Success after binutils/gcc: 13 commits new 3a6afa0fc6 419: onsuccess: #1844: 2: Success after binutils/gcc: 9 commits new 25d0832ffb 420: onsuccess: #1845: 2: Success after binutils/gcc: 12 commits new 244e8451d1 421: onsuccess: #1846: 2: Success after binutils/gcc: 5 commits new b6a1745255 422: onsuccess: #1847: 2: Success after binutils/gcc: 14 commits new 189ff37f66 423: onsuccess: #1848: 2: Success after binutils/gcc: 9 commits new 1498f0be58 424: onsuccess: #1849: 2: Success after binutils/gcc: 10 commits new 3b4fd4c1bc 425: onsuccess: #1850: 2: Success after binutils: 9 commits new ed70f2bd5e 426: onsuccess: #1851: 2: Success after basepoints/gcc-13-47 [...] new 571907a7b5 427: onsuccess: #1852: 2: Success after binutils/gcc: 3 commits new 8cc7f27241 428: onsuccess: #1853: 2: Success after binutils/gcc: 3 commits new 5f3f173eff 429: onsuccess: #1854: 2: Success after binutils/gcc: 3 commits new deaa3a6f7d 430: onsuccess: #1855: 2: Success after basepoints/gcc-13-47 [...] new ee608cf699 431: onsuccess: #1856: 2: Success after binutils/gcc: 2 commits new 459e732cfb 432: onsuccess: #1857: 2: Success after binutils/gcc: 9 commits new 80b766915f 433: onsuccess: #1858: 2: Success after binutils/gcc: 27 commits new 20a7e5cedf 434: onsuccess: #1860: 2: Success after binutils: 6 commits new 6ce7a4c89b 435: force: #1867: 2: Success after gcc: 2 commits new 505d2a1458 436: force: #1868: 1: Failure after basepoints/gcc-13-4795-g [...] new bf1c6fdd62 437: onsuccess: #1869: 1: Success after gcc: 5 commits new ea07da0dc9 438: onsuccess: #1870: 2: Success after binutils/gcc: 13 commits new c8261d0908 439: onsuccess: #1871: 2: Success after binutils/gcc: 3 commits new bb94deb76d 440: onsuccess: #1872: 2: Success after binutils/gcc: 9 commits new ae3f072de0 441: onsuccess: #1873: 2: Success after binutils/gcc: 41 commits new 59c7a57ae2 442: onsuccess: #1874: 2: Success after binutils/gcc: 11 commits new 6f44b0bd9b 443: onsuccess: #1875: 2: Success after binutils/gcc: 5 commits new 7ac4dbff3b 444: onsuccess: #1876: 2: Success after binutils/gcc: 5 commits new ccee8f802b 445: onsuccess: #1877: 2: Success after binutils: 18 commits new af478d53b1 446: onsuccess: #1878: 2: Success after binutils/gcc: 10 commits new f33f951d6c 447: onsuccess: #1879: 2: Success after binutils/gcc: 9 commits new c8a93ce2ce 448: onsuccess: #1880: 2: Success after binutils/gcc: 24 commits new 60f6554855 449: onsuccess: #1881: 2: Success after binutils/gcc: 19 commits new 89aa467e64 450: onsuccess: #1882: 2: Success after binutils/gcc: 40 commits new 3c41bb0052 451: onsuccess: #1883: 2: Success after binutils/gcc: 4 commits new 5e7ec2dbf6 452: onsuccess: #1884: 2: Success after binutils/gcc: 8 commits new 47d653bd54 453: onsuccess: #1885: 2: Success after binutils/gcc: 4 commits new 303243e703 454: onsuccess: #1886: 2: Success after binutils/gcc: 9 commits new afcff311e0 455: onsuccess: #1887: 2: Success after binutils: 13 commits new 6d064a0ac3 456: onsuccess: #1888: 2: Success after basepoints/gcc-13-48 [...] new 038a2c27a2 457: onsuccess: #1889: 2: Success after binutils: 2 commits new b9c34b20fd 458: onsuccess: #1890: 2: Success after binutils/gcc: 3 commits new 90048381b8 459: onsuccess: #1891: 2: Success after binutils: 2 commits new 052c08d7ce 460: onsuccess: #1892: 2: Success after basepoints/gcc-13-48 [...] new 423ee3ebbf 461: onsuccess: #1893: 2: Success after binutils/gcc: 3 commits new 39a5a9af48 462: onsuccess: #1894: 2: Success after binutils: 9 commits new f357f679a2 463: onsuccess: #1895: 2: Success after basepoints/gcc-13-48 [...] new 1f76004c22 464: onsuccess: #1896: 2: Success after binutils/gcc: 15 commits new 8397bbec64 465: onsuccess: #1897: 2: Success after binutils/gcc: 5 commits new 4282dbd079 466: onsuccess: #1898: 2: Success after basepoints/gcc-13-49 [...] new cbb49cbd3c 467: onsuccess: #1899: 2: Success after basepoints/gcc-13-49 [...] new 8bcaa9e865 468: onsuccess: #1900: 2: Success after binutils/gcc: 4 commits new 3d52222b80 469: onsuccess: #1901: 2: Success after binutils/gcc: 2 commits new dd2438b2d9 470: onsuccess: #1902: 2: Success after gdb-13-branchpoint-2 [...] new 2733e46bb4 471: onsuccess: #1903: 2: Success after gcc: 17 commits new d1636e8ffa 472: onsuccess: #1904: 2: Success after binutils/gcc: 2 commits new c579bc55dc 473: onsuccess: #1905: 2: Success after basepoints/gcc-13-49 [...] new 54f1cdcd46 474: onsuccess: #1906: 2: Success after binutils/gcc: 4 commits new 1724e7a8b1 475: onsuccess: #1907: 2: Success after binutils/gcc: 4 commits new 680b21be19 476: onsuccess: #1908: 2: Success after binutils/gcc: 2 commits new b93c021134 477: onsuccess: #1909: 2: Success after binutils: 4 commits new 2f5109d327 478: onsuccess: #1910: 2: Success after binutils: 9 commits new e68c528258 479: onsuccess: #1911: 2: Success after gcc: 2 commits new be3ff159f0 480: onsuccess: #1912: 2: Success after binutils/gcc: 3 commits new cfb8bb203c 481: onsuccess: #1913: 2: Success after binutils/gcc: 8 commits new 39761397d1 482: onsuccess: #1914: 2: Success after binutils/gcc: 5 commits new 22934f47aa 483: onsuccess: #1915: 2: Success after binutils/gcc: 5 commits new dfbde4ae21 484: onsuccess: #1916: 2: Success after binutils/gcc: 8 commits new 3730edc716 485: onsuccess: #1917: 2: Success after binutils/gcc: 3 commits new d8396787a3 486: onsuccess: #1918: 2: Success after binutils/gcc: 7 commits new 0f5ba80552 487: onsuccess: #1919: 2: Success after binutils/gcc: 12 commits new e77befb60f 488: onsuccess: #1920: 2: Success after binutils: 4 commits new 80d0b5a13e 489: onsuccess: #1921: 2: Success after binutils/gcc: 26 commits new 442b196477 490: onsuccess: #1922: 2: Success after binutils/gcc: 17 commits new a82efad73b 491: onsuccess: #1923: 2: Success after binutils/gcc: 7 commits new e9614b57d7 492: onsuccess: #1924: 2: Success after binutils: 2 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 (8cf8bf8b19) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1724 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2752 bytes 04-build_abe-binutils/console.log.xz | Bin 52240 -> 53384 bytes 05-build_abe-bootstrap/console.log.xz | Bin 473188 -> 471764 bytes 06-check_regression/console.log.xz | Bin 2788 -> 2440 bytes 07-update_baseline/console.log | 40 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 ++++++------ 12 files changed, 32 insertions(+), 32 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_apm/gnu-master-aarch64-spec2k6-Os updated (30edea9e87 -> 343090e4e9)

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_apm/gnu-master-aarch64-spec2k6-Os in repository toolchain/ci/base-artifacts. from 30edea9e87 50: onsuccess: #345: 1: [TCWG CI] No change after binutils/g [...] new 343090e4e9 51: onsuccess: #1: 1: [TCWG CI] No change after binutils/gcc [...] 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 -> 1836 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32880 -> 32564 bytes 04-build_abe-stage1/console.log.xz | Bin 75012 -> 73448 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8696 -> 8704 bytes 07-build_abe-glibc/console.log.xz | Bin 246720 -> 244664 bytes 08-build_abe-stage2/console.log.xz | Bin 183348 -> 178236 bytes 09-benchmark/benchmark-build.log | 88 +- 09-benchmark/benchmark.log | 86 +- 09-benchmark/console.log.xz | Bin 3876 -> 3948 bytes 10-check_regression/console.log.xz | Bin 14752 -> 13952 bytes .../csv-results-vs-first-0/md5sum.csv | 3144 +- .../csv-results-vs-first-0/results.csv | 458566 ++++++------ .../csv-results-vs-first-0/size.csv | 574198 +++++++------- .../csv-results-vs-first-0/vect.csv | 46 +- .../csv-results-vs-first-1/md5sum.csv | 2920 +- .../csv-results-vs-first-1/perf.csv | 3510 +- .../csv-results-vs-first-1/results.csv | 696199 +++++++++-------- .../csv-results-vs-first-1/size.csv | 698980 +++++++++--------- .../csv-results-vs-first-1/vect.csv | 40 +- .../csv-results-vs-prev-0/md5sum.csv | 3275 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 3655 +- .../csv-results-vs-prev-0/results.csv | 695255 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/size.csv | 698038 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/vect.csv | 38 +- .../csv-results-vs-prev-1/md5sum.csv | 2920 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 3510 +- .../csv-results-vs-prev-1/results.csv | 696199 +++++++++-------- 10-check_regression/csv-results-vs-prev-1/size.csv | 698980 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/vect.csv | 40 +- 10-check_regression/mail-body.txt | 5 - 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 3508 +- 10-check_regression/results-vs-first-internal.csv | 253 +- 10-check_regression/results-vs-first.csv | 253 +- 10-check_regression/results-vs-first.log | 1116 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 7 +- 10-check_regression/results-vs-prev-full.csv | 3762 +- 10-check_regression/results-vs-prev-internal.csv | 253 +- 10-check_regression/results-vs-prev.csv | 253 +- 10-check_regression/results-vs-prev.log | 1332 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 14 +- .../400.perlbench/results-metrics.json | 2 +- .../squad-vs-first/401.bzip2/results-metadata.json | 14 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 14 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../410.bwaves/results-metadata.json | 14 +- .../416.gamess/results-metadata.json | 14 +- .../squad-vs-first/429.mcf/results-metadata.json | 14 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 14 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 14 +- .../squad-vs-first/434.zeusmp/results-metrics.json | 2 +- .../435.gromacs/results-metadata.json | 14 +- .../435.gromacs/results-metrics.json | 2 +- .../436.cactusADM/results-metadata.json | 14 +- .../436.cactusADM/results-metrics.json | 2 +- .../437.leslie3d/results-metadata.json | 14 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 14 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../squad-vs-first/445.gobmk/results-metadata.json | 14 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 14 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 14 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 14 +- .../454.calculix/results-metadata.json | 14 +- .../squad-vs-first/456.hmmer/results-metadata.json | 14 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 14 +- .../459.GemsFDTD/results-metadata.json | 14 +- .../462.libquantum/results-metadata.json | 14 +- .../464.h264ref/results-metadata.json | 14 +- .../squad-vs-first/465.tonto/results-metadata.json | 14 +- .../squad-vs-first/465.tonto/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 14 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 14 +- .../squad-vs-first/473.astar/results-metadata.json | 14 +- .../squad-vs-first/481.wrf/results-metadata.json | 14 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 14 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 14 +- .../squad-vs-first/Mean/results-metadata.json | 14 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 126 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 36 +- mail/mail-body.txt | 41 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 2929656 -> 0 bytes save-temps/401.bzip2.tar.xz | Bin 301040 -> 0 bytes save-temps/403.gcc.tar.xz | Bin 7625560 -> 0 bytes save-temps/410.bwaves.tar.xz | Bin 53080 -> 0 bytes save-temps/416.gamess.tar.xz | Bin 17149476 -> 0 bytes save-temps/429.mcf.tar.xz | Bin 71796 -> 0 bytes save-temps/433.milc.tar.xz | Bin 370604 -> 0 bytes save-temps/434.zeusmp.tar.xz | Bin 530532 -> 0 bytes save-temps/435.gromacs.tar.xz | Bin 2368288 -> 0 bytes save-temps/436.cactusADM.tar.xz | Bin 1833968 -> 0 bytes save-temps/437.leslie3d.tar.xz | Bin 176528 -> 0 bytes save-temps/444.namd.tar.xz | Bin 674188 -> 0 bytes save-temps/445.gobmk.tar.xz | Bin 2723592 -> 0 bytes save-temps/447.dealII.tar.xz | Bin 11643184 -> 0 bytes save-temps/450.soplex.tar.xz | Bin 1472664 -> 0 bytes save-temps/453.povray.tar.xz | Bin 2672576 -> 0 bytes save-temps/454.calculix.tar.xz | Bin 3557816 -> 0 bytes save-temps/456.hmmer.tar.xz | Bin 988732 -> 0 bytes save-temps/458.sjeng.tar.xz | Bin 322344 -> 0 bytes save-temps/459.GemsFDTD.tar.xz | Bin 640068 -> 0 bytes save-temps/462.libquantum.tar.xz | Bin 116332 -> 0 bytes save-temps/464.h264ref.tar.xz | Bin 3324868 -> 0 bytes save-temps/465.tonto.tar.xz | Bin 8355464 -> 0 bytes save-temps/470.lbm.tar.xz | Bin 52176 -> 0 bytes save-temps/471.omnetpp.tar.xz | Bin 1522300 -> 0 bytes save-temps/473.astar.tar.xz | Bin 160528 -> 0 bytes save-temps/481.wrf.tar.xz | Bin 9113560 -> 0 bytes save-temps/482.sphinx3.tar.xz | Bin 586712 -> 0 bytes save-temps/483.xalancbmk.tar.xz | Bin 17713580 -> 0 bytes 130 files changed, 2624358 insertions(+), 2626908 deletions(-) delete mode 100644 save-temps/400.perlbench.tar.xz delete mode 100644 save-temps/401.bzip2.tar.xz delete mode 100644 save-temps/403.gcc.tar.xz delete mode 100644 save-temps/410.bwaves.tar.xz delete mode 100644 save-temps/416.gamess.tar.xz delete mode 100644 save-temps/429.mcf.tar.xz delete mode 100644 save-temps/433.milc.tar.xz delete mode 100644 save-temps/434.zeusmp.tar.xz delete mode 100644 save-temps/435.gromacs.tar.xz delete mode 100644 save-temps/436.cactusADM.tar.xz delete mode 100644 save-temps/437.leslie3d.tar.xz delete mode 100644 save-temps/444.namd.tar.xz delete mode 100644 save-temps/445.gobmk.tar.xz delete mode 100644 save-temps/447.dealII.tar.xz delete mode 100644 save-temps/450.soplex.tar.xz delete mode 100644 save-temps/453.povray.tar.xz delete mode 100644 save-temps/454.calculix.tar.xz delete mode 100644 save-temps/456.hmmer.tar.xz delete mode 100644 save-temps/458.sjeng.tar.xz delete mode 100644 save-temps/459.GemsFDTD.tar.xz delete mode 100644 save-temps/462.libquantum.tar.xz delete mode 100644 save-temps/464.h264ref.tar.xz delete mode 100644 save-temps/465.tonto.tar.xz delete mode 100644 save-temps/470.lbm.tar.xz delete mode 100644 save-temps/471.omnetpp.tar.xz delete mode 100644 save-temps/473.astar.tar.xz delete mode 100644 save-temps/481.wrf.tar.xz delete mode 100644 save-temps/482.sphinx3.tar.xz delete mode 100644 save-temps/483.xalancbmk.tar.xz -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[binutils-gdb] branch master updated (8819b23615c -> 502c7218da3)

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 8819b23615c Avoid unaligned pointer reads in PEP .idata section new 502c7218da3 Fix AArch64 linker testsuite failures trigeered by differen [...] 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: ld/ChangeLog | 7 +++++++ ld/testsuite/ld-aarch64/bti-plt-5.d | 8 ++++---- ld/testsuite/ld-aarch64/tls-relax-gdesc-le-now.d | 2 +- 3 files changed, 12 insertions(+), 5 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[binutils-gdb] branch binutils-2_40-branch updated (2ebe33ffd1e -> f4e184b2747)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch binutils-2_40-branch in repository binutils-gdb. from 2ebe33ffd1e Avoid unaligned pointer reads in PEP .idata section new f4e184b2747 Fix AArch64 linker testsuite failures triggered by differen [...] 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: ld/ChangeLog | 7 +++++++ ld/testsuite/ld-aarch64/bti-plt-5.d | 8 ++++---- ld/testsuite/ld-aarch64/tls-relax-gdesc-le-now.d | 2 +- 3 files changed, 12 insertions(+), 5 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (7c7b237566 -> 7569be7a88)

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 7c7b237566 149: onsuccess: #684: 1: Success after linux: 10 commits discards c9cc9a823e 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 07d6e89092 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 9c7cfff0a6 146: onsuccess: #680: 1: Success after binutils: 20 commits discards df5f4fb8d8 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards 75e23eee8d 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards dfa9a1868e 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards 9f2096a760 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards ef9a745953 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards ae942da606 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards 67e3fc7c7f 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits discards 2494e2e71c 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards ce4a1ffc40 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits discards e4a4e49e08 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 30864f7b66 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards ef9447a9fe 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] discards ac087c2575 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] discards 73adfdd010 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 9e605b4eac 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards 8e6b7fa9ff 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards bea5aba815 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards a2b0df4dce 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] discards 921d220da7 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 5890482986 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 660d8cd3f5 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 93eef8075c 124: onsuccess: #657: 1: Success after glibc: 2 commits discards d773a6f889 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 0951b0ceea 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards c8c2eec6e2 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 943d7865b1 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards a29309395c 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 20d79c8247 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 77386678ef 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] discards 965e599d85 116: onsuccess: #647: 1: Success after linux: 3 commits discards 9c62034470 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 418dbf47b7 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards 3d1dd73832 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards a84d611504 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards a1c22ceef2 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards ca520f765e 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards e612a54c64 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] discards f20e33f173 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards 6dc0a56ebd 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards f9439deb26 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards adcd0543cb 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards 98ad6fb2c4 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards 6e63afe1f0 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits discards a7b2174a15 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards 30e7645e98 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards c9d840be87 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards ca4f56cf60 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards 723ce5f84b 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards 32fa88338f 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards ba9a3e8237 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards f8cf6ce7cb 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 275e87e503 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 28cfb0c4c9 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 4e5234ea41 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] discards 4f2ebe1be2 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] discards 0eff5e3409 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] discards f92111fc71 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] discards 86fb5c78af 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] discards 4119b4faf6 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] discards 3baeefa3e7 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] discards cce2c2b32f 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] discards 35a94324d0 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] discards eb95da2b63 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] discards 98b6317ef0 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] discards 656b35d998 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] discards 1e33408cb1 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] discards 08d847b40e 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] discards e381e90f3b 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] discards e10a689312 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] discards 1ff3901591 76: onsuccess: #592: 1: Success after linux: 63 commits discards 21e7c1e04e 75: onsuccess: #591: 1: Success after gcc: 25 commits discards c59e93ba87 74: onsuccess: #590: 1: Success after binutils: 16 commits discards c6cfdb8568 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] discards f43a13125b 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] discards 427943c82f 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] discards f2a2d70029 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] discards 1b16c4a7b9 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] discards 58a28be3fb 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] discards 1b15149740 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] discards 49787ac233 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 10b5430342 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] discards 4d031ada17 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] discards a921425aca 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 90a8d8547f 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] discards 15d8369590 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] discards 70c51aeb9a 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] discards 6675d63655 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] discards 61da56fe21 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] discards ed51ba3735 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] discards 8b4b9fd9b9 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] discards 651dd347b3 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] discards 3951e07ae2 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] discards bda206a040 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] discards 29445af624 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] discards 82ff3c7c79 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards d12a4b34fc 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] discards f2f9a32438 49: onsuccess: #562: 1: Success after binutils: 9 commits new 7c0c2fe03e 49: onsuccess: #562: 1: Success after binutils: 9 commits new 6fd1388619 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] new 52c775e708 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new f89ed86a95 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] new c474e4b760 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] new 346e0f5a62 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] new 871788bf9e 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] new 1abb56c8a4 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] new 9af6fd53ab 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] new 49bf5ed686 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] new b74780f06d 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] new 4fc195825b 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new c9bdaac156 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] new 597f795b20 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] new 981f37dffb 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 445bdc89b9 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] new b970b99a69 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] new d5b1032fc1 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 038f8daa22 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] new 2b737694e8 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] new 8e08029c9f 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] new d2b7d95ab9 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] new 7e20beb39d 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] new 76e957954f 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] new 1e21542630 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] new 87ab3fae93 74: onsuccess: #590: 1: Success after binutils: 16 commits new efe2ca83ff 75: onsuccess: #591: 1: Success after gcc: 25 commits new 7edd6c2e5c 76: onsuccess: #592: 1: Success after linux: 63 commits new df7d70bcab 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] new 55d20cb896 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] new 283637c932 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] new 1a7a6ae37f 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] new d07e2132ca 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] new 400166dd34 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] new 9d09dafc29 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] new 32a8cf529d 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] new 8ab504ee27 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] new dd31525a7e 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] new 92c53c8165 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] new 1022b2d7cd 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] new 7cbed8b2fc 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] new d24fd19d67 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] new 5396b9c8f0 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] new 03ddd07315 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] new 0b9edac26e 93: onsuccess: #613: 1: Success after binutils: 19 commits new 32497e89ac 94: onsuccess: #616: 1: Success after binutils: 2 commits new 8066c4880d 95: onsuccess: #619: 1: Success after binutils: 5 commits new 7f31cd1954 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new 3dfb588daf 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 909562acb2 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new 98948757fd 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new ca13ab93dd 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new 7b8b797ea6 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new d97af6bb6b 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new b8234ba2af 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits new 714c991b14 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new e183b6a942 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new d166845bfa 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new ee5ae88bb0 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new 079e506487 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new a735ce2ee0 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] new e24ac889da 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new db3fdd019f 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new 1027e7221b 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new fbf2739141 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 1f904f0ed5 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new a2bfd25b44 115: onsuccess: #645: 1: Success after binutils: 27 commits new b32bd66d8d 116: onsuccess: #647: 1: Success after linux: 3 commits new 34ce2f98d6 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] new 596cd6b1a1 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new f2136e1245 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 7d91bcc705 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 33acae7e25 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new f1f29dec33 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 3e9c0d41b2 123: onsuccess: #655: 1: Success after binutils: 22 commits new 8976adb2b3 124: onsuccess: #657: 1: Success after glibc: 2 commits new 955222e2ed 125: onsuccess: #658: 1: Success after linux: 3224 commits new a55f3ced4a 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 592edf24ea 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new c89b22e2db 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] new ce7b9c865c 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new 84c64ffdc7 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 6f3f264736 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new 208807da27 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 0c2ddee2fe 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] new 0ad595eb12 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] new ad26feda33 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new cd6b4d8e7f 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new e5bbef1331 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new 6d297ba0fb 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new 24e2ccdc73 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new a197f064da 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new 7f84400575 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new c80c6d0d66 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new e6e29adeac 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new 4823d56e38 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new 8a31a88799 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new 8529eec3c6 146: onsuccess: #680: 1: Success after binutils: 20 commits new 80e052fe9b 147: onsuccess: #681: 1: Success after gcc: 6 commits new 32c7b83aad 148: onsuccess: #683: 1: Success after glibc: 9 commits new 184bf23dc3 149: onsuccess: #684: 1: Success after linux: 10 commits new 7569be7a88 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (7c7b237566) \ 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 1668 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 40684 -> 40848 bytes 04-build_abe-gcc/console.log.xz | Bin 217104 -> 215064 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8852 -> 8844 bytes 07-build_abe-glibc/console.log.xz | Bin 244588 -> 245052 bytes 08-build_abe-gdb/console.log.xz | Bin 40152 -> 40212 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3848 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2192 -> 2688 bytes 11-check_regression/console.log.xz | Bin 4844 -> 5672 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 60 ++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +-- sumfiles/binutils.log.xz | Bin 63096 -> 62844 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83880 -> 83928 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 122168 -> 122396 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 29 files changed, 401 insertions(+), 397 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits January 2023