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/master-arm updated (dce3436e04c -> d17bf86c044)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-arm in repository toolchain/ci/base-artifacts. discards dce3436e04c 239: onsuccess: #1968: 7: Success after binutils/gcc/gdb: 3 [...] discards fb5d7a0b15f 238: onsuccess: #1967: 7: Success after binutils/gcc/linux/ [...] discards f3251b87cbb 237: onsuccess: #1966: 7: Success after gcc/linux: 3 commits discards 4498aaec39b 236: onsuccess: #1965: 7: Success after binutils/gcc/gdb: 1 [...] discards 12ff3f0be44 235: onsuccess: #1964: 7: Success after binutils/linux/glib [...] discards be8d26762b9 234: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 7 [...] discards a7a3adbed34 233: onsuccess: #1962: 7: Success after gcc: 6 commits discards 3a934da095c 232: onsuccess: #1961: 7: Success after binutils/gcc/linux/ [...] discards df1c6dc43c4 231: onsuccess: #1960: 7: Success after binutils/gcc/glibc/ [...] discards dccfb2e16de 230: onsuccess: #1958: 7: Success after binutils/gcc/linux/ [...] discards 47a27fdc182 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc/ [...] discards a77baa95bb9 228: onsuccess: #1956: 7: Success after gcc: 5 commits discards af5fc89d8a3 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits discards 47c670e4bd4 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc/ [...] discards e74861c77f2 225: onsuccess: #1953: 7: Success after binutils/gcc/linux/ [...] discards 2aae919c9ed 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/qe [...] discards 748c6b2d3d7 223: onsuccess: #1951: 3: Success after binutils/gcc/linux: [...] discards 2e7029e2862 222: onsuccess: #1950: 3: Success after basepoints/gcc-13-4 [...] discards 12bf1ae42a9 221: force: #1949: 3: Failure after basepoints/gcc-13-4492- [...] discards 4418c3b51f7 220: force: #1948: 5: Success after gcc: 4 commits discards 419e84c397e 219: onsuccess: #1945: 5: Success after binutils: 8 commits discards aae7ba107fd 218: onsuccess: #1943: 5: Success after gdb: 3 commits discards 6879566d913 217: force: #1942: 5: Failure after gdb-12-branchpoint-2943 [...] discards eecf188cc2a 216: onsuccess: #1940: 7: Success after linux: 12 commits discards 35e04258b4a 215: onsuccess: #1938: 7: Success after gcc: 4 commits discards 689c828b7b2 214: onsuccess: #1937: 7: Success after binutils: 4 commits discards e7649856b3e 213: onsuccess: #1935: 7: Success after gcc: 2 commits discards 630d72c9763 212: onsuccess: #1934: 7: Success after gcc: 3 commits discards 95e00e91663 211: onsuccess: #1933: 7: Success after binutils/gcc/linux/ [...] discards 1ea26610aee 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: 7 [...] discards 4cc3851cf87 209: onsuccess: #1931: 7: Success after binutils/gcc/linux/ [...] discards 92a8b00b29b 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits discards 4ac23a7705e 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: 2 [...] discards 95d373cb6c7 206: onsuccess: #1927: 7: Success after binutils/gcc/linux/ [...] discards 8de896b4962 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 4 [...] discards b7535967170 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 1 [...] discards 7c53154f342 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 1 [...] discards 3754e156960 202: onsuccess: #1923: 7: Success after binutils/gcc/linux/ [...] discards 39047464c09 201: onsuccess: #1905: 7: Success after binutils/gcc/linux/ [...] discards 45b05964a58 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/ [...] discards 3115b2bc586 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/ [...] discards 49c4c2688fb 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/ [...] discards 3539d6ce237 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/ [...] discards f979017a082 196: onsuccess: #1855: 4: Success after gcc: 30 commits discards da34a83726c 195: force: #1854: 4: Failure after basepoints/gcc-13-3918- [...] discards 95d226fab57 194: force: #1853: 7: Success after gcc: 26 commits discards 4e81afd4262 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint- [...] discards d236ebffa68 192: onsuccess: #1848: 7: Success after linux: 213 commits discards f55a7d76181 191: onsuccess: #1846: 7: Success after binutils: 4 commits discards 3bc688ffa39 190: onsuccess: #1834: 7: Success after binutils: 25 commits discards 63d2a0e9c2c 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/ [...] discards fc9b1837ded 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/ [...] discards cafa2b851e3 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/ [...] discards ac52244dbcc 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/ [...] discards 89e6256a72c 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/ [...] discards 0735d232dd4 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/ [...] discards 4da42c2aee7 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/ [...] discards 0abb73595f0 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 [...] discards 957ef343e9f 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/ [...] discards 5b4f9ea60cc 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/ [...] discards 8341c5b64e8 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/ [...] discards ed5b223d009 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/ [...] discards 8f2b6a3fa93 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/ [...] discards f8cbfd9527b 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/ [...] discards c374a7e12bf 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 1 [...] discards 297bc892e91 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/ [...] discards 8b2cd116c1d 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qem [...] discards 8df6c487081 172: onsuccess: #1687: 7: Success after gcc: 11 commits discards bf0d436621a 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/ [...] discards 7fb609cdef1 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/ [...] discards 20daf912ec2 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/ [...] discards f518151a042 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 3 [...] discards 42cbbd94612 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits discards 7594416fae4 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/ [...] discards 5dab61a4373 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/ [...] discards 0b25d541be7 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 1 [...] discards 0176dbdb2bb 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 [...] discards ead2235ed14 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/ [...] discards 05776d24514 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/ [...] discards ecceed0ace9 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 1 [...] discards 432c0eb8826 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/ [...] discards 979cd527e59 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards 1c1fcb4d46a 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards 1f651e3dbd8 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards 51df7295ca1 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/ [...] discards 2178536eab1 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/ [...] discards 8fbf86b5e5f 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 2 [...] discards b3cdf79eb76 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/ [...] discards fb6444a2305 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/ [...] discards 49d50f1de55 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/ [...] discards d64f5860e34 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 3 [...] discards b4de8304ec2 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 3526d793cdd 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/ [...] discards 70711835fb7 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/ [...] discards 6e120498714 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 1 [...] discards b1a529360f9 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 [...] discards cdffac1ba63 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/ [...] discards f5decfec3ae 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/ [...] discards a596beb53a8 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards a9cf7c590a4 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/ [...] discards e2f25556f10 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 5cd6c23b026 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 0244bfc8abb 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/ [...] new 3b0bb93fc0e 141: onsuccess: #1656: 7: Success after gcc: 7 commits new aa4ddc4628f 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/ [...] new 04e81cf2caa 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/ [...] new 0ddba40df8b 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 [...] new 6fee6955973 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 1 [...] new 2c3f1cb2393 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/ [...] new 857467f7b80 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/ [...] new e8e0aed2dc9 148: onsuccess: #1663: 7: Success after glibc: 2 commits new b7f151adba2 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 3 [...] new 8b5123e1d1a 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/ [...] new f40869e2b1f 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/ [...] new 7d512bd8a8f 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/ [...] new 25f5953a1c6 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 2 [...] new 17546da2416 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/ [...] new 46f4b507b74 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/ [...] new 119f06ff7af 156: onsuccess: #1671: 7: Success after gcc: 3 commits new 763fd3fed79 157: onsuccess: #1672: 7: Success after gcc: 2 commits new d480a412cba 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new c411ed7a3d7 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/ [...] new 0fe73ee0b75 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 1 [...] new 8c304241eb0 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/ [...] new 3a04e440592 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/ [...] new ab2cba525de 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 [...] new 4893f1c183b 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 1 [...] new 4f9dd48149a 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/ [...] new 2d709b57ca1 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/ [...] new 13272b517e4 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits new c89d294150c 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 3 [...] new 95b1e2e4ebf 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/ [...] new f90693ae904 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/ [...] new 28233d53184 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/ [...] new e478208bfbe 172: onsuccess: #1687: 7: Success after gcc: 11 commits new 711f32a781c 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qem [...] new 42465582db3 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/ [...] new 15700c98567 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 1 [...] new 9c7cde47e7a 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/ [...] new 960c315941b 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/ [...] new 4f965d9781f 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/ [...] new 25f4204a8b2 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/ [...] new 9e4cf65c617 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/ [...] new 055666ba127 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/ [...] new 3089325b9a9 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 [...] new 3cf135ae781 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/ [...] new deff1335caa 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/ [...] new b71469a5408 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/ [...] new bdd78836fff 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/ [...] new 2a553b74d1b 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/ [...] new fcad29d6846 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/ [...] new 6f790e76a5f 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/ [...] new 5a229b33895 190: onsuccess: #1834: 7: Success after binutils: 25 commits new 76f8d76cb29 191: onsuccess: #1846: 7: Success after binutils: 4 commits new e70c59b4ecc 192: onsuccess: #1848: 7: Success after linux: 213 commits new 78f9f78985b 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint- [...] new 881d8d86eae 194: force: #1853: 7: Success after gcc: 26 commits new 0630853d5fc 195: force: #1854: 4: Failure after basepoints/gcc-13-3918- [...] new b991a44920a 196: onsuccess: #1855: 4: Success after gcc: 30 commits new db887f5596e 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/ [...] new d88e97397b8 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/ [...] new 1df269e8381 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/ [...] new 7a1630325b5 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/ [...] new fc41cd259fb 201: onsuccess: #1905: 7: Success after binutils/gcc/linux/ [...] new 8d4181daeb1 202: onsuccess: #1923: 7: Success after binutils/gcc/linux/ [...] new 45c02e318b9 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 1 [...] new dbf4e96cba1 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 1 [...] new ed14634d8e9 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 4 [...] new 4c1f25cd7c0 206: onsuccess: #1927: 7: Success after binutils/gcc/linux/ [...] new 37aefddb4e5 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: 2 [...] new 1eb3dd693c9 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits new 8f27c139d0d 209: onsuccess: #1931: 7: Success after binutils/gcc/linux/ [...] new 587580fa295 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: 7 [...] new 483f7762071 211: onsuccess: #1933: 7: Success after binutils/gcc/linux/ [...] new 7515c76057d 212: onsuccess: #1934: 7: Success after gcc: 3 commits new b041836b67e 213: onsuccess: #1935: 7: Success after gcc: 2 commits new 387c1fbc899 214: onsuccess: #1937: 7: Success after binutils: 4 commits new 295a6ebab49 215: onsuccess: #1938: 7: Success after gcc: 4 commits new da63e5ea0d3 216: onsuccess: #1940: 7: Success after linux: 12 commits new 64bcabdc6e4 217: force: #1942: 5: Failure after gdb-12-branchpoint-2943 [...] new ef53f115626 218: onsuccess: #1943: 5: Success after gdb: 3 commits new 3c32edbe4fd 219: onsuccess: #1945: 5: Success after binutils: 8 commits new c945d9bdef0 220: force: #1948: 5: Success after gcc: 4 commits new 4b042976b6d 221: force: #1949: 3: Failure after basepoints/gcc-13-4492- [...] new 00e95b4d9b3 222: onsuccess: #1950: 3: Success after basepoints/gcc-13-4 [...] new 2ae8da8cab5 223: onsuccess: #1951: 3: Success after binutils/gcc/linux: [...] new a79c03dede0 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/qe [...] new f49c1eafe7e 225: onsuccess: #1953: 7: Success after binutils/gcc/linux/ [...] new 193eaae46bd 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc/ [...] new 2928c0fbd70 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits new 46eb90f9249 228: onsuccess: #1956: 7: Success after gcc: 5 commits new ecfcee4aed7 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc/ [...] new d047cd39bd3 230: onsuccess: #1958: 7: Success after binutils/gcc/linux/ [...] new d1950bb0455 231: onsuccess: #1960: 7: Success after binutils/gcc/glibc/ [...] new be36e66be48 232: onsuccess: #1961: 7: Success after binutils/gcc/linux/ [...] new 8aa1066eb6d 233: onsuccess: #1962: 7: Success after gcc: 6 commits new 48acd1a2eed 234: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 7 [...] new 9ce6a1401dc 235: onsuccess: #1964: 7: Success after binutils/linux/glib [...] new 916f046850e 236: onsuccess: #1965: 7: Success after binutils/gcc/gdb: 1 [...] new cb423841bfc 237: onsuccess: #1966: 7: Success after gcc/linux: 3 commits new 5f9daadcfa2 238: onsuccess: #1967: 7: Success after binutils/gcc/linux/ [...] new fce800786bd 239: onsuccess: #1968: 7: Success after binutils/gcc/gdb: 3 [...] new d17bf86c044 240: onsuccess: #1969: 7: Success after gcc/linux: 9 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 (dce3436e04c) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1800 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2764 bytes 04-build_abe-binutils/console.log.xz | Bin 31556 -> 31440 bytes 05-build_abe-stage1/console.log.xz | Bin 91588 -> 91664 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8788 -> 8532 bytes 08-build_abe-glibc/console.log.xz | Bin 234944 -> 235516 bytes 09-build_abe-stage2/console.log.xz | Bin 224204 -> 225080 bytes 10-build_abe-gdb/console.log.xz | Bin 38888 -> 38752 bytes 11-build_abe-qemu/console.log.xz | Bin 30360 -> 30852 bytes 12-check_regression/console.log.xz | Bin 3332 -> 3604 bytes 13-update_baseline/console.log | 38 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 ++++++++++++------------ 19 files changed, 38 insertions(+), 38 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allmodconfig updated (415bfee3382 -> c43555711ed)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allmodconfig in repository toolchain/ci/base-artifacts. from 415bfee3382 40: force: #512: boot: Success after linux: 943 commits new c43555711ed 41: onsuccess: #515: boot: Success after binutils/llvm/qemu [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1888 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32552 -> 31556 bytes 04-build_kernel_llvm/console.log.xz | Bin 65016 -> 63980 bytes 05-build_abe-qemu/console.log.xz | Bin 30964 -> 30284 bytes 06-build_linux/console.log.xz | Bin 3352 -> 3496 bytes 07-boot_linux/console.log.xz | Bin 480 -> 480 bytes 08-check_regression/console.log.xz | Bin 2928 -> 3804 bytes 09-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 ++++++++++++++++-------------- 17 files changed, 24 insertions(+), 22 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch master updated (d9d8c9674ad -> 8f72249ff4c)

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 d9d8c9674ad d: Fix internal compiler error: in visit, at d/imports.cc:7 [...] new 8f72249ff4c Fortran: fix ICE on bad use of statement function [PR107995] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/fortran/interface.cc | 6 ++++++ gcc/testsuite/gfortran.dg/pr107995.f90 | 10 ++++++++++ 2 files changed, 16 insertions(+) create mode 100644 gcc/testsuite/gfortran.dg/pr107995.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (8341db6a540 -> 9d0dfa00c25)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-aarch64 in repository toolchain/ci/base-artifacts. discards 8341db6a540 405: onsuccess: #2367: 1: Success after basepoints/gcc-13-4 [...] discards aff635e2d74 404: onsuccess: #2366: 1: Success after basepoints/gcc-13-4 [...] discards 4ad13c51c20 403: onsuccess: #2365: 1: Success after binutils/gcc: 2 commits discards 93ec8eb2779 402: onsuccess: #2364: 1: Success after binutils/gcc: 19 commits discards 69f26d071b3 401: onsuccess: #2363: 1: Success after gdb-12-branchpoint- [...] discards 3897eb94f9e 400: onsuccess: #2362: 1: Success after binutils/gcc: 6 commits discards 8d49e31e058 399: onsuccess: #2361: 1: Success after gcc: 10 commits discards 9bacf0a88c1 398: onsuccess: #2360: 1: Success after binutils/gcc: 9 commits discards f2f01411ff6 397: onsuccess: #2359: 1: Success after binutils/gcc: 10 commits discards c5df159c460 396: onsuccess: #2358: 1: Success after binutils/gcc: 9 commits discards b9571bbbdf6 395: onsuccess: #2357: 1: Success after binutils/gcc: 3 commits discards d66ab1c59f6 394: onsuccess: #2356: 1: Success after binutils/gcc: 6 commits discards 88cf6d0d352 393: onsuccess: #2355: 1: Success after binutils/gcc: 8 commits discards 97e9d128d19 392: onsuccess: #2354: 1: Success after gcc: 5 commits discards 35c320ae13c 391: onsuccess: #2353: 1: Success after binutils/gcc: 8 commits discards 9a8cc0c1bf8 390: onsuccess: #2352: 1: Success after binutils/gcc: 15 commits discards aac86f87a88 389: onsuccess: #2351: 1: Success after binutils/gcc: 12 commits discards b4ab918cddc 388: onsuccess: #2350: 1: Success after binutils/gcc: 13 commits discards 0dd2ad1bda2 387: onsuccess: #2349: 1: Success after binutils/gcc: 6 commits discards da0971040f4 386: onsuccess: #2348: 1: Success after binutils/gcc: 10 commits discards 63ed829b342 385: onsuccess: #2347: 1: Success after binutils/gcc: 12 commits discards a0247d79a83 384: onsuccess: #2346: 1: Success after binutils/gcc: 8 commits discards 907fb9a3de5 383: onsuccess: #2345: 1: Success after binutils/gcc: 3 commits discards 5a1cd637775 382: onsuccess: #2344: 1: Success after binutils/gcc: 7 commits discards 07c4afb5ad2 381: onsuccess: #2343: 1: Success after gcc: 2 commits discards 4926d13b485 380: onsuccess: #2342: 1: Success after gcc: 3 commits discards 84b73a6a5c4 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-4 [...] discards 109bd74ca5a 378: onsuccess: #2340: 1: Success after binutils: 2 commits discards 131e82a9470 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits discards c78da191292 376: onsuccess: #2338: 1: Success after gcc: 2 commits discards e933b68b41d 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits discards 36d04e62a87 374: onsuccess: #2336: 1: Success after gcc: 4 commits discards 0bd59ed4e2c 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits discards 01f8f088238 372: onsuccess: #2334: 1: Success after gcc: 5 commits discards 8ca80085bf7 371: onsuccess: #2333: 1: Success after binutils: 5 commits discards 5c92bbd7748 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits discards 2b352a6777b 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits discards b0d193f56ac 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits discards be53887e08d 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits discards 469f53e6389 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits discards e318bbd48d8 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits discards 2a55d8673f2 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits discards 829ab84af5c 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits discards 52060a1e277 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits discards dd7da16be2f 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits discards e16f027df63 360: onsuccess: #2317: 1: Success after binutils: 4 commits discards d443ca7c11e 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint- [...] discards 79fe13fa194 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits discards ea46e115584 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits discards 66a26a9e67b 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits discards b20a7bf07cf 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits discards 345fb347932 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits discards 23bc04e1e5d 353: onsuccess: #2309: 1: Success after gcc: 7 commits discards 062a133221a 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits discards 454aa64ad73 351: onsuccess: #2307: 1: Success after binutils: 2 commits discards 91755e6e1c9 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits discards 0e8767b6996 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits discards 57e08423a2a 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits discards 91519db67ac 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits discards 88420e7ab56 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits discards 80d3915841d 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits discards dda1342707d 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits discards 67f25f122c7 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits discards 1fe88242843 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits discards 999e0daae32 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits discards 7b563c01171 340: onsuccess: #2296: 1: Success after gcc: 3 commits discards dac34cee18d 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits discards 79ea7d7f6e4 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits discards 2fbc4525b97 337: onsuccess: #2293: 1: Success after gcc: 21 commits discards 00e3d352c9a 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits discards 592b11981e0 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits discards b5f79544d2b 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits discards b65a58cdfba 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-4 [...] discards ba0a09127d7 332: onsuccess: #2288: 1: Success after gcc: 2 commits discards 581598285fa 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint- [...] discards a828e68ae5c 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits discards 33844bd4d35 329: onsuccess: #2285: 1: Success after gcc: 8 commits discards d752d47214b 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint- [...] discards 8d270b0a5b8 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits discards b99bc408a12 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits discards 3276e06327f 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits discards e8229d2c9d1 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits discards 6fcfef45d26 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits discards 5e4f59745c2 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits discards c4be27fe0d9 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits discards 2b5c8a60b86 320: onsuccess: #2274: 1: Success after gcc: 5 commits discards b63bba14e2f 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits discards 359ba06f3b9 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits discards dd919d25c3e 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits discards 735dfc35238 316: onsuccess: #2270: 1: Success after gcc: 2 commits discards f8c8356b005 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits discards 3e16d02214e 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits discards 935931681bf 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits discards 5f8d0a2e88e 312: onsuccess: #2265: 1: Success after binutils: 2 commits discards 21513c7743c 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint- [...] discards d6e9e967fa0 310: onsuccess: #2259: 1: Success after binutils: 2 commits discards 8cb878fe8e1 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint- [...] discards 5c836031f17 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint- [...] discards 3f9fc0a1fb6 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint- [...] discards ec562495100 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint- [...] discards f524b1f780e 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits new 3b32aba5813 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits new bd7e311b528 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint- [...] new c46138e7b54 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint- [...] new 3435e672209 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint- [...] new 28c5593045c 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint- [...] new de2aba00df7 310: onsuccess: #2259: 1: Success after binutils: 2 commits new e4ef2f8fcb9 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint- [...] new 9388d65b573 312: onsuccess: #2265: 1: Success after binutils: 2 commits new 02a9214ab0b 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits new 5b87c67fbaf 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits new 14fdd51f912 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits new 18d53d86204 316: onsuccess: #2270: 1: Success after gcc: 2 commits new f303b480525 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits new 6f811dbcfd7 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits new 29a6ed98c82 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits new 33203e7d66e 320: onsuccess: #2274: 1: Success after gcc: 5 commits new 465b987b260 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits new f33dcd36e7e 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits new 6e4cab3668b 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits new 9f364985ce7 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits new 9f9aa31e504 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits new 2d47ab86e30 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits new a4ff7afea46 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits new c931ddad2ea 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint- [...] new 6c5a5774562 329: onsuccess: #2285: 1: Success after gcc: 8 commits new 73908b5cee2 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits new f06938df153 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint- [...] new 671665d2e73 332: onsuccess: #2288: 1: Success after gcc: 2 commits new bf88fa775b3 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-4 [...] new 88096d66eae 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits new c51c0f2f5a0 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits new 789e9909ee3 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits new 0c7ee5402d7 337: onsuccess: #2293: 1: Success after gcc: 21 commits new a61dd49f6d8 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits new 81a62f00221 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits new 5b1e1599f68 340: onsuccess: #2296: 1: Success after gcc: 3 commits new ae69efd1a78 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits new 64f95c4986f 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits new f0b647dcd05 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits new b5b68f024fe 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits new c746d6635a6 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits new 5103c43db3c 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits new cc0bd006748 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits new 33b94b95e14 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits new e1e71ce246c 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits new cabccff2a2b 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits new 5f6458d260a 351: onsuccess: #2307: 1: Success after binutils: 2 commits new 1ff0ff1fb01 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits new 80c481f7bf0 353: onsuccess: #2309: 1: Success after gcc: 7 commits new 9e44200361d 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits new 79556670f13 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits new 3b79fb87c61 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits new b77bc7bc082 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits new 1e66477796c 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits new 6da32d81326 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint- [...] new 61d97b15b2f 360: onsuccess: #2317: 1: Success after binutils: 4 commits new 59a5970108b 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits new 5e18cbcb3f4 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits new e913cf7f3a3 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits new 72ec146635f 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits new 50214a5f297 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits new 8f4d3cd9c8b 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits new 432d24ed550 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits new f52411fab19 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits new eb66ebda4ca 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits new 8f53afcf813 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits new 10e73ec3ed1 371: onsuccess: #2333: 1: Success after binutils: 5 commits new 47d1b073044 372: onsuccess: #2334: 1: Success after gcc: 5 commits new 45c0b152a8d 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits new 23bf2a5b336 374: onsuccess: #2336: 1: Success after gcc: 4 commits new 4547b4c9613 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits new f292a898232 376: onsuccess: #2338: 1: Success after gcc: 2 commits new 2ec4104452a 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits new 4e185734522 378: onsuccess: #2340: 1: Success after binutils: 2 commits new 2231f9b5096 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-4 [...] new 91869f8cfaf 380: onsuccess: #2342: 1: Success after gcc: 3 commits new 90bc2b23f4a 381: onsuccess: #2343: 1: Success after gcc: 2 commits new 8b4b12ec795 382: onsuccess: #2344: 1: Success after binutils/gcc: 7 commits new 3f013aacf79 383: onsuccess: #2345: 1: Success after binutils/gcc: 3 commits new f305ee54dda 384: onsuccess: #2346: 1: Success after binutils/gcc: 8 commits new 211b5701be4 385: onsuccess: #2347: 1: Success after binutils/gcc: 12 commits new 2b385900b37 386: onsuccess: #2348: 1: Success after binutils/gcc: 10 commits new f5a53dcb39b 387: onsuccess: #2349: 1: Success after binutils/gcc: 6 commits new 7fe48cd02ef 388: onsuccess: #2350: 1: Success after binutils/gcc: 13 commits new 9ee0c181ba0 389: onsuccess: #2351: 1: Success after binutils/gcc: 12 commits new 9c012dde600 390: onsuccess: #2352: 1: Success after binutils/gcc: 15 commits new ac2325da377 391: onsuccess: #2353: 1: Success after binutils/gcc: 8 commits new 2bf91b1b0b6 392: onsuccess: #2354: 1: Success after gcc: 5 commits new b1444f30bfa 393: onsuccess: #2355: 1: Success after binutils/gcc: 8 commits new 66db2e1be99 394: onsuccess: #2356: 1: Success after binutils/gcc: 6 commits new de3e267770c 395: onsuccess: #2357: 1: Success after binutils/gcc: 3 commits new af8ea23872b 396: onsuccess: #2358: 1: Success after binutils/gcc: 9 commits new 88eaa42b8a4 397: onsuccess: #2359: 1: Success after binutils/gcc: 10 commits new 3fe8c28557d 398: onsuccess: #2360: 1: Success after binutils/gcc: 9 commits new 4e593caae17 399: onsuccess: #2361: 1: Success after gcc: 10 commits new d08b66c3ffb 400: onsuccess: #2362: 1: Success after binutils/gcc: 6 commits new a9d5bf52fae 401: onsuccess: #2363: 1: Success after gdb-12-branchpoint- [...] new c4a48f50731 402: onsuccess: #2364: 1: Success after binutils/gcc: 19 commits new ddaf0cd44b6 403: onsuccess: #2365: 1: Success after binutils/gcc: 2 commits new 67deada495c 404: onsuccess: #2366: 1: Success after basepoints/gcc-13-4 [...] new b567542b737 405: onsuccess: #2367: 1: Success after basepoints/gcc-13-4 [...] new 9d0dfa00c25 406: onsuccess: #2368: 1: Success after binutils/gcc: 8 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 (8341db6a540) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-aarch64 [...] 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 1760 -> 1820 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 39480 -> 40272 bytes 04-build_abe-gcc/console.log.xz | Bin 213452 -> 215376 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3848 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2648 -> 2684 bytes 07-check_regression/console.log.xz | Bin 4632 -> 5008 bytes 07-check_regression/results.compare | 35 +- 07-check_regression/results.compare2 | 49 +- 08-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 3606024 -> 3639980 bytes sumfiles/g++.sum | 138 +- sumfiles/gcc.log.xz | Bin 3162144 -> 3135212 bytes sumfiles/gcc.sum | 4882 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1051864 -> 1049264 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2184 -> 2184 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 220072 -> 219792 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2548 -> 2540 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 453748 -> 444176 bytes sumfiles/libstdc++.sum | 10 +- 31 files changed, 2627 insertions(+), 2625 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allnoconfig updated (ae641d30adf -> 17b8e6623e8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allnoconfig in repository toolchain/ci/base-artifacts. from ae641d30adf 25: onsuccess: #481: boot: Success after binutils/llvm/linu [...] new 17b8e6623e8 26: onsuccess: #482: boot: Success after binutils/llvm/linu [...] 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 1740 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31776 -> 31676 bytes 04-build_kernel_llvm/console.log.xz | Bin 65980 -> 65088 bytes 05-build_abe-qemu/console.log.xz | Bin 31116 -> 30660 bytes 06-build_linux/console.log.xz | Bin 3376 -> 3360 bytes 08-check_regression/console.log.xz | Bin 4352 -> 3952 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 15 files changed, 21 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (b41d8e61372 -> 119abe8043a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards b41d8e61372 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-4 [...] discards 1a5b883c410 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/ [...] discards eab424be912 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 1 [...] discards 0edaf816585 220: onsuccess: #1898: 7: Success after binutils/linux/glib [...] discards 540479fa716 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 [...] discards fd13cb2b809 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/ [...] discards 748b15253be 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 1 [...] discards a0347e10d2d 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits discards c0e1183a364 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/ [...] discards 78d1c54b30c 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/ [...] discards 11a20b8a3d5 213: onsuccess: #1889: 7: Success after gcc: 5 commits discards 0a1980b6298 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/ [...] discards c203da1f2cb 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/ [...] discards df496dab06b 210: onsuccess: #1868: 7: Success after binutils: 7 commits discards 5f66a4467c4 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qe [...] discards bb1c44834a4 208: onsuccess: #1865: 7: Success after linux: 12 commits discards a9e68a6f21e 207: onsuccess: #1862: 7: Success after binutils: 4 commits discards 2aed475f994 206: onsuccess: #1860: 7: Success after gcc: 2 commits discards b726dcf86b3 205: onsuccess: #1859: 7: Success after gcc: 3 commits discards 7ee95f4b661 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/ [...] discards bccddc0a60d 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 [...] discards fd71fd379f9 202: onsuccess: #1856: 7: Success after gcc: 2 commits discards f2d2fa5bb62 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/ [...] discards 14eac4cba08 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits discards 703b6274be7 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 1 [...] discards 61be4066ca7 198: onsuccess: #1852: 7: Success after gcc: 5 commits discards 92e803b41bf 197: onsuccess: #1851: 7: Success after binutils/gcc/linux/ [...] discards 4cc89c5fd17 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 4 [...] discards d6258a93d58 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 1 [...] discards ee312f34757 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 1 [...] discards e56db2dbbf9 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/ [...] discards 36b03acc248 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/ [...] discards a8ebbbd0868 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/ [...] discards d5642d6ab4e 190: onsuccess: #1774: 7: Success after binutils: 10 commits discards 0a95d1fb1ed 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 3 [...] discards a033b735065 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/ [...] discards 96fb57278b4 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/ [...] discards 1e4e61b1572 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/ [...] discards b5c9769e9be 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] discards 4e6ec60aed0 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/ [...] discards cf5bc3bda29 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/ [...] discards 178d9614a3c 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/ [...] discards 56a9e3f2230 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/ [...] discards 91c92c2381b 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] discards bd9387755a4 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/ [...] discards db11d3af036 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/ [...] discards a048ef6884a 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/ [...] discards 7a4ce94261e 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/ [...] discards c41093b160f 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/ [...] discards b82b2e3dad8 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 1 [...] discards f627f039d8d 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/ [...] discards 84f1314f3c0 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qem [...] discards 2cf451c7ed4 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 1 [...] discards 005d613fef8 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/ [...] discards c24d48b00bb 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/ [...] discards a198a35aeb5 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/ [...] discards 6576ecc34dd 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 2 [...] discards 2f5696c74a0 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits discards 4cb53f906f8 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/ [...] discards 154f7c21201 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/ [...] discards 8a16c10de82 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 1 [...] discards 3cd4e3f67cc 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 [...] discards 24f6175e5a6 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/ [...] discards ed59f6b34af 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/ [...] discards c504334e128 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards 9be2d0621f0 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/ [...] discards 056555b9080 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards be9c0de5f16 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards 434f54e33ba 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb [...] discards 1284aadd8ba 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards cf0eceb19d1 153: force: #1606: 1: Failure after basepoints/gcc-13-3004- [...] discards cf75b1b5185 152: force: #1605: 7: Success after gcc: 9 commits discards a14ffdcd438 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint- [...] discards 5cb817022c9 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/ [...] discards af081d268b9 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 2 [...] discards a92639a678e 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/ [...] discards 1b6abd24155 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/ [...] discards a010ed8385a 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/ [...] discards fdc289b6551 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 3 [...] discards b167eb6ab8d 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 4ff92ca7766 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/ [...] discards 20f304f1103 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/ [...] discards 43e13a2cd68 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 [...] discards 36949647138 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 [...] discards 4e3f3bf1c59 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/ [...] discards 50e28ed6510 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/ [...] discards ae6cb9b44eb 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 0e2c7936340 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 1 [...] discards 134a1104aec 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/ [...] discards 68ef42e438d 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/ [...] discards b0063970cac 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 2 [...] discards a514a491be8 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 1 [...] discards 7f8086fc444 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/ [...] discards 7dbec4fe114 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 406fe924b05 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-2 [...] discards 8cd4cef5507 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 62d3dd85ab9 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 [...] discards 6e8a3631be8 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards b9339167f49 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 [...] discards 5bbace39418 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards fd3ac353d21 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/ [...] new abcf38bbbe6 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/ [...] new 1ae1e36a397 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new c13b13c11a8 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 [...] new f3920ed4cb9 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 7d6ec30f34a 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 [...] new c577d21458e 128: onsuccess: #1579: 7: Success after linux: 12 commits new b9a65a6e5dd 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-2 [...] new 9f3bd0ea78d 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 12f642729f6 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/ [...] new e0ee3e5ff24 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 1 [...] new 42f475a100e 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 2 [...] new 09374391b9e 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/ [...] new 4b2dd4327e9 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/ [...] new f7d98f40aef 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 1 [...] new 200361908e5 137: onsuccess: #1588: 7: Success after gcc: 5 commits new b1a4e4c3e26 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/ [...] new d79f1785de8 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/ [...] new 445cf8a5b92 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 [...] new 63802fc2f58 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 [...] new b895a5d2b8a 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/ [...] new 2ef8be67a50 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/ [...] new 9027563686f 144: onsuccess: #1595: 7: Success after glibc: 2 commits new 9f132e0d269 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 3 [...] new bbfba91b1a0 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/ [...] new 6b0b2bfd2e8 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/ [...] new b7ea5832d2e 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/ [...] new e90c8ae7c58 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 2 [...] new ab19b16082d 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/ [...] new d3a97a4e322 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint- [...] new e3bc2b52c05 152: force: #1605: 7: Success after gcc: 9 commits new 7c937bfcfab 153: force: #1606: 1: Failure after basepoints/gcc-13-3004- [...] new 70d976950d7 154: onsuccess: #1607: 1: Success after gcc: 2 commits new e9ebf114f7b 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb [...] new ad3842eb569 156: onsuccess: #1609: 7: Success after gcc: 2 commits new 1033e0dd01e 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new f396d0527ea 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/ [...] new 77ea5376539 159: onsuccess: #1612: 7: Success after gcc: 4 commits new 2eef357ffab 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/ [...] new 32d97799c3e 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/ [...] new 30298d3580e 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 [...] new ded1d82f664 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 1 [...] new fed31eae54a 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/ [...] new d36a2db3981 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/ [...] new 61bbeab6111 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits new b791c3fb986 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 2 [...] new 83d40d599d1 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/ [...] new e2640930f95 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/ [...] new 8e215c11d3a 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/ [...] new a2e678cd7ec 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 1 [...] new f5cbf1e8351 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qem [...] new c04ee1e31c7 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/ [...] new 1358533f02b 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 1 [...] new 35166de9250 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/ [...] new dcace31d80f 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/ [...] new bab78376b0a 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/ [...] new 2697a2e256f 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/ [...] new 6a07f5705b6 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/ [...] new 1d7c49ab28a 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] new 793fdd43bc6 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/ [...] new 0a72cb3c2c8 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/ [...] new 12e7ac5fdb7 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/ [...] new 43accf806c4 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/ [...] new 7d22e72f9af 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] new 70ada66b45c 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/ [...] new 93759d707b8 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/ [...] new caa4a2dbdb4 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/ [...] new 8d55cec4368 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 3 [...] new d121d4dee9f 190: onsuccess: #1774: 7: Success after binutils: 10 commits new 60ab90f3e31 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/ [...] new 4b93437c1d1 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/ [...] new cfc9b9a208c 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/ [...] new 7fa1edea51d 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 1 [...] new 3f7326d9f86 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 1 [...] new 711c63d4742 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 4 [...] new 9da4d6e158b 197: onsuccess: #1851: 7: Success after binutils/gcc/linux/ [...] new 0830e909bd5 198: onsuccess: #1852: 7: Success after gcc: 5 commits new b8e8ee754b0 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 1 [...] new 0c9c1d69ad9 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits new 6e7f47c6920 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/ [...] new c89cc9fd9e5 202: onsuccess: #1856: 7: Success after gcc: 2 commits new f883dfe4c33 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 [...] new 495dffa61ab 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/ [...] new 72d3e71e579 205: onsuccess: #1859: 7: Success after gcc: 3 commits new 5bbbca03993 206: onsuccess: #1860: 7: Success after gcc: 2 commits new 9128c9ea0f6 207: onsuccess: #1862: 7: Success after binutils: 4 commits new 06af0b9b653 208: onsuccess: #1865: 7: Success after linux: 12 commits new a0f686551c6 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qe [...] new 3a11aa2da9d 210: onsuccess: #1868: 7: Success after binutils: 7 commits new 6ab9251572c 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/ [...] new 84335aed284 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/ [...] new 6a236baf500 213: onsuccess: #1889: 7: Success after gcc: 5 commits new bbaf888bc70 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/ [...] new f4b9e1929dd 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/ [...] new 3844d3f3422 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits new 5753772a310 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 1 [...] new d89964ab1eb 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/ [...] new 9a27801ec3d 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 [...] new 5d0d0b86658 220: onsuccess: #1898: 7: Success after binutils/linux/glib [...] new 0981a9e2f51 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 1 [...] new 7e6bca82306 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/ [...] new 813ae47a79b 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-4 [...] new 119abe8043a 224: onsuccess: #1902: 7: 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 (b41d8e61372) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1696 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2776 bytes 04-build_abe-binutils/console.log.xz | Bin 31664 -> 31860 bytes 05-build_abe-stage1/console.log.xz | Bin 72904 -> 72920 bytes 07-build_abe-linux/console.log.xz | Bin 8780 -> 8492 bytes 08-build_abe-glibc/console.log.xz | Bin 243196 -> 243272 bytes 09-build_abe-stage2/console.log.xz | Bin 203972 -> 204088 bytes 10-build_abe-gdb/console.log.xz | Bin 38696 -> 39052 bytes 11-build_abe-qemu/console.log.xz | Bin 31208 -> 30764 bytes 12-check_regression/console.log.xz | Bin 3156 -> 3856 bytes 13-update_baseline/console.log | 44 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++++++-------------- 20 files changed, 47 insertions(+), 47 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-mainline-defconfig updated (27c86eeea19 -> bb22da37046)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-mainline-defconfig in repository toolchain/ci/base-artifacts. from 27c86eeea19 28: onsuccess: #418: boot: Success after binutils/linux/qem [...] new bb22da37046 29: onsuccess: #419: boot: Success after binutils/linux: 15 [...] 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 1768 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 30136 -> 30060 bytes 04-build_kernel_llvm/console.log.xz | Bin 63008 -> 63520 bytes 05-build_abe-qemu/console.log.xz | Bin 30528 -> 30748 bytes 06-build_linux/console.log.xz | Bin 3252 -> 3204 bytes 07-boot_linux/console.log.xz | Bin 5716 -> 5668 bytes 08-check_regression/console.log.xz | Bin 3832 -> 3260 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 ++++++++++++------------ 15 files changed, 18 insertions(+), 18 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (d8af86504eb -> 756ea08df3e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards d8af86504eb 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 8ec7cb9396e 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 552745f33ab 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 442f27dc8f3 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 7ce67313949 125: onsuccess: #614: 1: Success after linux: 12 commits discards cff2eeeb47f 124: onsuccess: #612: 1: Success after binutils: 18 commits discards e8ec33a3d45 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 8826f6cbbf1 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards e840c55256d 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 3a305a487e0 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 8d0af9850a7 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards b5f5a3b6b22 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 8b8aad00ac3 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards acd8c174beb 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 4df25fad158 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 882d17e013d 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 4cde328a0ff 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards dbad9db02db 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] discards 4b70834fafc 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] discards faa5b1b5b29 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards b045f2f5053 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 2e34da8e4c0 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 20c706ae68e 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards c7d8f3a3bb4 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards fb054a64773 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards ede098ada1c 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 087995466d1 103: onsuccess: #589: 1: Success after binutils: 3 commits discards afa7e624ceb 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 40d98676a9e 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] discards e4c0d364d02 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] discards 0a9a89fa43d 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] discards e1840532879 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards 45772ec1f55 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] discards 8c2f31829cf 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] discards fba59eeb478 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] discards 3ae5a52d4da 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards eba9f7e85e2 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] discards cb334886def 92: onsuccess: #575: 1: Success after linux: 34 commits discards 096823115bb 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 341345e9576 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 5d902fb50f3 89: onsuccess: #570: 1: Success after linux: 11 commits discards d065eecda32 88: onsuccess: #569: 1: Success after glibc: 10 commits discards bc649c36a1c 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 31f098b72aa 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 3004915bac7 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards 0e567237de3 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards cda16d1a66a 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] discards 5ce1f147c56 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] discards 135bc2e86a5 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards f2928573b20 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] discards 7f59760188e 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] discards 47c0286c6a0 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] discards 61d750cd08c 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] discards 953b631c355 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] discards e7e9376dd95 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] discards d03c2e8f8bf 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] discards 90197f5d9c7 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 42f9107cad7 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 96b7a9a145c 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] discards 3c6d2c6426e 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 70dd22bd3e0 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] discards bd45df9258a 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] discards 2d60a20b0f7 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] discards 34109cdc706 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 07afee32e2f 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] discards ccd9ac96714 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 8178bc363e7 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards 46ca40b6b10 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards 0fed59e4d57 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 06129bdbb0c 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] discards 0f5d0f087a9 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards e5771a1f699 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards 8bfd3f39764 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] discards 343629b03b4 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards 1a6eaf361a3 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 431b8c04d36 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] discards 0c4520e257f 53: onsuccess: #531: 1: Success after binutils: 12 commits discards dd6b7cde8d8 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 44266698458 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 9ad21c706bb 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] discards 6e7f79f2cc9 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] discards 50fa373a22b 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] discards c5f8a97b822 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] discards 94ba5836851 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] discards ff65439e889 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] discards 029a7c8e86c 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] discards 78e5cad11ea 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] discards 3dd861d52dd 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] discards 0ff0c5c4aae 41: onsuccess: #514: 1: Success after linux: 64 commits discards 4b85fb2dd13 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] discards d5189c6854d 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 0a1165967bc 38: onsuccess: #508: 1: Success after binutils: 3 commits discards 92306d3b866 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] discards 8d0fe10e55f 36: onsuccess: #505: 1: Success after glibc: 3 commits discards 5425d96f445 35: onsuccess: #503: 1: Success after binutils: 11 commits discards 4d602aa24d2 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards 32c94737c2f 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gd [...] discards 8b8ab81312a 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] discards 034f61fcfac 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] discards c101b778b9c 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards 2db5185d0b1 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new 615c2b134af 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new 5a51e615c6d 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new 9cfe52709a4 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] new ab437ec1d42 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] new 47b985e5616 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gd [...] new 7e397a8fa44 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new 86ca0478af8 35: onsuccess: #503: 1: Success after binutils: 11 commits new ab8afc396a2 36: onsuccess: #505: 1: Success after glibc: 3 commits new ece6a82d700 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] new a224b669d8b 38: onsuccess: #508: 1: Success after binutils: 3 commits new c88e812e420 39: onsuccess: #511: 1: Success after binutils: 8 commits new af376ce57cd 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] new e72e59009aa 41: onsuccess: #514: 1: Success after linux: 64 commits new bef20a55546 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] new 95569e849ad 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] new 677ce29bbd7 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] new 4fccd257fbb 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] new ad48da5763f 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] new ac0e18baafa 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] new 3ab2a66ea57 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] new d0686461d74 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] new 060afb1be8b 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] new 4be074ccd95 51: onsuccess: #525: 1: Success after binutils: 8 commits new 19a2ff52fca 52: onsuccess: #528: 1: Success after binutils: 8 commits new abfee12cc79 53: onsuccess: #531: 1: Success after binutils: 12 commits new 138c27af25d 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] new bc728935c32 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new 60a95116f9c 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new b625f34fd4b 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] new d2272ce2041 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new d9da7e81b29 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new 91999e65e7c 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] new 5bb59b75bbe 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new 7c68f3c6fe2 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new 341cda16a68 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 70937f1069f 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new dfdaeb2322f 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] new 08f9391a30e 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new 727875fad6a 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] new e732e8a14ad 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] new 766d9539d2b 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] new 93474bd1cc9 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 3a094cd60f5 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] new c3e1b5ecc01 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new f772a4a96db 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 029b2a63487 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] new e5af1537016 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] new 68e3968bb74 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] new 26db97f63bc 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] new 4fd018ce7be 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] new b9ae6f5b611 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] new 9bdd0f0ecfc 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] new 15eae813160 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new c2f6d04f803 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] new 89514cfcf41 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] new d830d1afb3d 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 9ace1b4fb91 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new 746827601f1 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new b6fc72bd4d8 87: onsuccess: #567: 1: Success after binutils: 8 commits new 4dbebe73e6f 88: onsuccess: #569: 1: Success after glibc: 10 commits new 7bbe15285bf 89: onsuccess: #570: 1: Success after linux: 11 commits new 98c1eb66299 90: onsuccess: #572: 1: Success after binutils: 15 commits new 2b110957a77 91: onsuccess: #574: 1: Success after glibc: 3 commits new ed632e30b6a 92: onsuccess: #575: 1: Success after linux: 34 commits new 2715b5652ce 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] new 8fb9b351876 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new e6eb54f9c4c 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] new 07435630422 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] new 143fd64b0d2 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] new 8fbb9895195 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new c30e55ebd0b 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] new 1a886d36f5a 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] new f0835cd8eff 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] new e4c0953a619 102: onsuccess: #586: 1: Success after binutils: 5 commits new 6458b112001 103: onsuccess: #589: 1: Success after binutils: 3 commits new d53b3203b04 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 1dab559cf1a 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 828132268d4 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new fddd7416659 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new a60ed5b7756 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 6a2e04f7b0a 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 96f8e7f155f 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new f2418a244e5 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new 89bca9d1187 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new feecf0b5c4d 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 7b71759c27d 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 4dae73bb9ec 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 16c8fd6b244 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new c0240410245 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new 0e4c9fdea2e 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 66ec278072e 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new d6cc7f2cfd5 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 7e40de9d5a4 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new debd31a0222 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 1d27cd0017f 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 78719dcf306 124: onsuccess: #612: 1: Success after binutils: 18 commits new b7b05aadd65 125: onsuccess: #614: 1: Success after linux: 12 commits new 108956fd648 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new dd125bddf0c 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 7a7717ae2a1 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new e65908dce68 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 756ea08df3e 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (d8af86504eb) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1740 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 55436 -> 52684 bytes 04-build_abe-gcc/console.log.xz | Bin 238108 -> 236580 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8656 -> 8984 bytes 07-build_abe-glibc/console.log.xz | Bin 237256 -> 235908 bytes 08-build_abe-gdb/console.log.xz | Bin 53084 -> 52168 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2868 -> 2308 bytes 11-check_regression/console.log.xz | Bin 18684 -> 15260 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 47 +- 11-check_regression/mail-body.txt | 198 +- 11-check_regression/results.compare | 106 +- 11-check_regression/results.compare2 | 4378 ++++++--------- 11-check_regression/results.regressions | 100 +- 12-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 200 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 100 +- sumfiles/gdb.log.xz | Bin 1799256 -> 1704064 bytes sumfiles/gdb.sum | 9120 +++++++++---------------------- 30 files changed, 4539 insertions(+), 9822 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (ab3a1a083c9 -> 32b4b7af398)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards ab3a1a083c9 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards 44a12eb49b2 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards df2a105daed 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards 9732ae991ce 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards 72107ed7e91 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards 9517f36bcd9 118: onsuccess: #863: 1: Success after linux: 12 commits discards 7e5285c5a0c 117: onsuccess: #861: 1: Success after binutils: 18 commits discards dc150b63e53 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards 63b6118131a 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards 1f68281be45 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards d359075888a 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 8ed5b4aad74 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 84e22835941 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 55de3c32fcc 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards a1bace73a0e 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards d9d0e128416 108: onsuccess: #850: 1: Success after gcc: 2 commits discards a9896b54606 107: onsuccess: #849: 1: Success after binutils: 5 commits discards b98586d07fc 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 88692dd9af0 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards f442979a116 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards bbc1f3b0e82 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards 272374766f5 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards c5c64363150 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 233b971d221 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards e3f7b6fe8ee 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards fa08fe43712 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 35741088f3e 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards 43bf52d2df1 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards 9cedaf07b84 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 175e971e1fa 94: onsuccess: #832: 1: Success after binutils: 5 commits discards ad94dd08559 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 9db5d71fdeb 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 9530e295a7c 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 28661c6f2ec 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 0c56b52c463 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 1c074dd7873 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards 6dcf0fd6f9d 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards dea4ebc72c8 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards d3095f7faa2 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 2d65dab67bd 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards ed0bfaebdae 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards bad95a8ff1a 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards d4cff3d7ce4 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards 6552f26c582 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards 84d0c747935 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards f1a21856f55 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards b534ce783e1 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards ba6ff964bf2 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 8ce2aef2ff5 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards 23aa4a90e51 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 28dc1a6c60d 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards a6f071dd773 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards a5e629ec68f 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards 2a739d4289b 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 0593d0b9818 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards ee1e5725c1e 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards c58f2e77347 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards 062899f6706 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards f59c195227a 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards 41b1704513e 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 1179e8defef 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 3d66f9b4517 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards 6f4fc559576 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 32218a20000 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards ebaabae2ae0 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 82d9fca4652 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards 998a1cdfafb 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards 749a03992fa 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards e098201f4f6 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards fa72cc6ec65 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards cddb027a6c8 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards 8c93c3fe343 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards a6c51a43560 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards 3daa8721be9 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards be4ff11c5f2 49: onsuccess: #785: 1: Success after binutils: 12 commits discards aac840c5c3d 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 72f4b4cef61 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards 300b53841b6 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards ac8b68c6ce7 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards 2c359fdb6cc 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards 2a29fe50bb6 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards a3f5baf2a78 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards 45a8e815368 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards 4d7dd4ce2eb 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards 1bd2edd4eea 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards 6f698f40101 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards 2995d0b121f 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards 65e4aac64c2 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 7d4fe4da526 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards 9ffc0159b6b 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards bf71170c46a 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards fc01f82c50b 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards 7d71c7d84d7 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards 0d0633aed66 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards c900bbd4aaa 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards 55b89fbcae3 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards bbc968b4898 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] discards 81b23c4926c 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] discards 3b179209147 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] discards 1cc54c70492 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards 9bba33ec773 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 2256e45dbfb 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 43f8b49e701 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 9da6ce213a6 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] new 625deb0b995 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new 19f756f55c6 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new 1990cf1dda1 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new dba2c009ca2 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new ced712ad465 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new 0b2e615da22 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new a03fbae1c98 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new 312a9aeae0e 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new b04abee7888 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new f679be996dd 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new 493d82a3ebf 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 0cd9f3abf1c 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new b02b14fed6e 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new 35ca6eb00b8 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new 0ea89b2d20f 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new e8dd4b8c477 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new 01a9feb2ad5 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new c9663a302af 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new fd5f5a82565 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new 4fdf42e6926 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new a56f3ae0426 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new db6dd868562 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new c10c66aadbb 48: onsuccess: #782: 1: Success after binutils: 8 commits new 678af8acbbd 49: onsuccess: #785: 1: Success after binutils: 12 commits new 0939e71583a 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new a83de673e57 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new 8426be54da5 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new 6a65a7921fd 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new 2977aa5dc2e 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new a4ade735f3b 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new decf7953860 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new e902a49b42e 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new 18b6e505b7c 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new 7cf41d7f833 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 303089687ad 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new a3685f0a56b 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 0173aee81f9 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 38a4f7e9c51 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 875edf783f7 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new f978f7412db 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 1476c57689d 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new d22cadfcc6e 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new 952d92d07dd 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new 99862e9b51d 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new 7990df4c0cb 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 0d19e70d6c5 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new f9882b14d04 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new 226bb53c5cc 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new eac8eabf9e2 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new e01f7a6e5ba 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new 78fa218f3b0 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new f374dfe171c 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new 6dafa09174d 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new 125093ac8b7 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new 847d38d1af4 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new efb0d9b32a7 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new c79a32c9e88 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new 162cb65f090 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new c049761930a 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 3748e692210 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 66bcce70455 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new 4381553d94d 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 38d7132799b 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new 77bdab4351e 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 70e44b63b1b 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 856aa737e08 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 6bc57bf1199 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 17aef3d756e 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 6855798af83 94: onsuccess: #832: 1: Success after binutils: 5 commits new 7104ef88470 95: onsuccess: #835: 1: Success after binutils: 3 commits new ab4b56ae5eb 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 4677aa5bc46 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new eb4109ad615 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new bf17e3ddd47 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new b2210c401c7 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new ab11f232bc8 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new cb211320a60 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 745c50c5f0c 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new 32a17c9d05f 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new f770b18ae36 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new abfe64ecacb 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new aea6580a9f1 107: onsuccess: #849: 1: Success after binutils: 5 commits new bfabcb49132 108: onsuccess: #850: 1: Success after gcc: 2 commits new 946a26b1052 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 2cfaf2312ee 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 6c7a97b3b12 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new 659cb837376 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new f20cfaca5bd 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new fb53133d9a4 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new c5569a93524 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 12eae6e69ce 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 841fc5c7246 117: onsuccess: #861: 1: Success after binutils: 18 commits new 7dd42c26314 118: onsuccess: #863: 1: Success after linux: 12 commits new f41fb9d5aa0 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new c6edf3e6497 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new e4c4554f594 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new 174cf10e11d 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new e763aa905f3 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new 32b4b7af398 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (ab3a1a083c9) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1760 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 41168 -> 39684 bytes 04-build_abe-gcc/console.log.xz | Bin 216220 -> 214340 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8764 -> 8740 bytes 07-build_abe-glibc/console.log.xz | Bin 246468 -> 243588 bytes 08-build_abe-gdb/console.log.xz | Bin 40500 -> 39268 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3884 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3024 -> 2680 bytes 11-check_regression/console.log.xz | Bin 7520 -> 6428 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 11 - 11-check_regression/mail-body.txt | 61 +- 11-check_regression/results.compare | 38 +- 11-check_regression/results.compare2 | 132 +- 11-check_regression/results.regressions | 46 - 12-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 63 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 46 - sumfiles/g++.log.xz | Bin 3781660 -> 3762216 bytes sumfiles/g++.sum | 138 +- sumfiles/gcc.log.xz | Bin 3307336 -> 3307240 bytes sumfiles/gcc.sum | 4792 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1079296 -> 1087176 bytes sumfiles/gfortran.sum | 69 +- sumfiles/libatomic.log.xz | Bin 2280 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 233012 -> 231992 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 457880 -> 447864 bytes sumfiles/libstdc++.sum | 10 +- 42 files changed, 2667 insertions(+), 2858 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-lts-allnoconfig updated (a25342e1b1f -> 29bd374e0ed)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-lts-allnoconfig in repository toolchain/ci/base-artifacts. from a25342e1b1f 26: onsuccess: #249: all: Success after binutils/linux/qemu [...] new 29bd374e0ed 27: onsuccess: #250: all: Success after binutils/linux: 127 [...] 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 1752 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30128 -> 30176 bytes 04-build_kernel_llvm/console.log.xz | Bin 62676 -> 63384 bytes 05-build_abe-qemu/console.log.xz | Bin 30672 -> 30876 bytes 06-build_linux/console.log.xz | Bin 3444 -> 3432 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 3664 -> 3228 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 ++++++++++++------------ 15 files changed, 18 insertions(+), 18 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022