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-aarch64 updated (bd3bd82c5cf -> 874cc1c597a)

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 bd3bd82c5cf 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 [...] discards df8ac746ce8 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/ [...] discards bc4f9f9d452 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 1 [...] discards 3f877bd41c8 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits discards 82b4e193df9 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/ [...] discards 1462ab77d99 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/ [...] discards 8ba9fb8e80c 213: onsuccess: #1889: 7: Success after gcc: 5 commits discards 133c5dd11a5 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/ [...] discards d4422331b6b 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/ [...] discards 13689469e5a 210: onsuccess: #1868: 7: Success after binutils: 7 commits discards b5a6e6b01f9 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qe [...] discards e02494c55e1 208: onsuccess: #1865: 7: Success after linux: 12 commits discards 4e14e60cda5 207: onsuccess: #1862: 7: Success after binutils: 4 commits discards c888a0ef5ec 206: onsuccess: #1860: 7: Success after gcc: 2 commits discards dbac152241d 205: onsuccess: #1859: 7: Success after gcc: 3 commits discards b42090359c0 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/ [...] discards 45392f9bc9d 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 [...] discards 4dcaf103898 202: onsuccess: #1856: 7: Success after gcc: 2 commits discards fa699c3e35f 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/ [...] discards ff1cc8666a9 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits discards 0ff354c1c8c 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 1 [...] discards bfca69f1636 198: onsuccess: #1852: 7: Success after gcc: 5 commits discards 737fba0ed9d 197: onsuccess: #1851: 7: Success after binutils/gcc/linux/ [...] discards 80fc8b9ff3c 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 4 [...] discards 9100f463cf4 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 1 [...] discards bd30556eb6b 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 1 [...] discards 4e807ad2b43 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/ [...] discards 63155c205fb 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/ [...] discards 91e19d01cd7 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/ [...] discards febf3884001 190: onsuccess: #1774: 7: Success after binutils: 10 commits discards 48df0e7f452 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 3 [...] discards 11f5486b65e 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/ [...] discards fd33451b068 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/ [...] discards a50d01ceca8 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/ [...] discards 97b2ea40c3d 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] discards 9a1926ede02 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/ [...] discards 1ea615a6aae 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/ [...] discards c53865c7d32 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/ [...] discards 083dea4623f 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/ [...] discards 0c9bc22b2a3 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] discards e0e7e7419cd 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/ [...] discards 9de460bfef7 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/ [...] discards e0c5c43daee 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/ [...] discards c34a38a1fe1 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/ [...] discards e796fc738a4 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/ [...] discards f80c9c65061 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 1 [...] discards 04db601ddca 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/ [...] discards b9b7ca0a6f3 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qem [...] discards d00f1b3708b 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 1 [...] discards 6dc81786cc0 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/ [...] discards 90c2b2fd27b 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/ [...] discards 072ad519322 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/ [...] discards 098ea09f6a1 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 2 [...] discards 11c70f6d881 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits discards 10cd5742db7 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/ [...] discards ae9edafd3c0 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/ [...] discards 209a9e10789 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 1 [...] discards 505f5c1e3e6 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 [...] discards daf2f30b47f 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/ [...] discards f02cbb88237 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/ [...] discards 6502178f505 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards 3e6268659a8 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/ [...] discards 3614edddc6c 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards 67402cf6033 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards 941f78cf4c1 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb [...] discards 268abde3c91 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards fab925f0afb 153: force: #1606: 1: Failure after basepoints/gcc-13-3004- [...] discards 93c418e62ad 152: force: #1605: 7: Success after gcc: 9 commits discards ba7fc12558d 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint- [...] discards 0a4236911f4 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/ [...] discards 1e11967be30 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 2 [...] discards c751f27a63e 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/ [...] discards 4714b42137d 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/ [...] discards 053ac5e3822 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/ [...] discards 9af80f20596 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 3 [...] discards 9be32343865 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 91b1b45fded 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/ [...] discards 57272aefeca 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/ [...] discards 0f7befeb44f 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 [...] discards 0854a6b37ab 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 [...] discards 22daf20b601 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/ [...] discards bde080b081a 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/ [...] discards b8d784d5bed 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 53fa0dd2ef0 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 1 [...] discards 5208ee85802 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/ [...] discards 306cbe17759 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/ [...] discards 6c0182a5f79 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 2 [...] discards 606160b9ea2 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 1 [...] discards 2b030c99ec1 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/ [...] discards 11c7639cf1a 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards acd9522cff3 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-2 [...] discards fed9b26625b 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 479145fe0af 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 [...] discards aca423c47aa 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 6f232f27fe6 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 [...] discards 730b87b9fcf 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 918bbaec215 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/ [...] discards ec33022f315 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/ [...] discards 33bded0ca9c 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/ [...] discards 89e8a3db1ce 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/ [...] discards 8452de13b99 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/ [...] new cc2364f45f5 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/ [...] new 46bb810c10e 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/ [...] new 3655e8d3232 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/ [...] new 7e8ca18a668 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/ [...] new a61c14898ed 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/ [...] new a9cd545eb40 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new a87dbea6dc9 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 [...] new af6adb63781 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 849f0e72c82 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 [...] new c456e16cc33 128: onsuccess: #1579: 7: Success after linux: 12 commits new 712c4161b88 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-2 [...] new e55c039603a 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new f2827341892 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/ [...] new d5ae118d7c7 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 1 [...] new eabd8038997 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 2 [...] new 843804b214f 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/ [...] new 8fa6c689a82 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/ [...] new fb7dbdf2792 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 1 [...] new 96046f85b66 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 1bc44b25265 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/ [...] new f36d1ab3e21 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/ [...] new caa5992a8a1 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 [...] new bee5a529c3d 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 [...] new 1e698b9d07c 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/ [...] new c79ac75f58f 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/ [...] new e297432f507 144: onsuccess: #1595: 7: Success after glibc: 2 commits new 33fa10e15a3 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 3 [...] new e30a8d4898f 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/ [...] new 439ab5b44d6 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/ [...] new e7f91fe9636 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/ [...] new f87f0610386 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 2 [...] new 2ca47225d37 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/ [...] new 6c822ef9f3e 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint- [...] new 1507599c244 152: force: #1605: 7: Success after gcc: 9 commits new f6a9cd26638 153: force: #1606: 1: Failure after basepoints/gcc-13-3004- [...] new b4619591f9d 154: onsuccess: #1607: 1: Success after gcc: 2 commits new c205bad087a 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb [...] new 14abb678e0d 156: onsuccess: #1609: 7: Success after gcc: 2 commits new ee2592e5017 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new fef6300a5c0 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/ [...] new dcc750fcc93 159: onsuccess: #1612: 7: Success after gcc: 4 commits new 3516b2e5754 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/ [...] new 1413980cfd9 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/ [...] new 769b8d9ff88 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 [...] new 2b76673aba1 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 1 [...] new 17da2a65138 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/ [...] new bc88cbbeecf 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/ [...] new e1cfc4d7a10 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits new 6ae4f40b928 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 2 [...] new d16c7d9a685 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/ [...] new b6c2da65473 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/ [...] new ce3176299b5 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/ [...] new 787efef80c9 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 1 [...] new 596358fec87 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qem [...] new 2d015af6a21 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/ [...] new a4df4b19948 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 1 [...] new eba70cdcf6a 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/ [...] new 1592bb96b28 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/ [...] new 2b15cc431b2 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/ [...] new 328f1c97f9f 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/ [...] new e9628da33b3 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/ [...] new 670714b1886 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] new e78b64a828f 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/ [...] new e6b960745fb 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/ [...] new 4a1067a804d 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/ [...] new d3aacbb356d 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/ [...] new ec5cdbd1ab6 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] new d289b7c76f8 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/ [...] new 14110b79a66 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/ [...] new cb935bb5e6a 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/ [...] new 0e57f63df21 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 3 [...] new 422157999a7 190: onsuccess: #1774: 7: Success after binutils: 10 commits new d8cd8c292e5 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/ [...] new 7f419cecfb7 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/ [...] new 87d3536a75e 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/ [...] new 9ccce98fe78 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 1 [...] new b3da80acb10 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 1 [...] new e3c79c891a7 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 4 [...] new b72d1c780c2 197: onsuccess: #1851: 7: Success after binutils/gcc/linux/ [...] new 637025dfc07 198: onsuccess: #1852: 7: Success after gcc: 5 commits new be210be48c2 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 1 [...] new f8011780e88 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits new 44c319e43e1 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/ [...] new db7d1e68dd9 202: onsuccess: #1856: 7: Success after gcc: 2 commits new 8adf9f15b23 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 [...] new f80aac19764 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/ [...] new 460b54d03dc 205: onsuccess: #1859: 7: Success after gcc: 3 commits new d07d01d6141 206: onsuccess: #1860: 7: Success after gcc: 2 commits new 13612881536 207: onsuccess: #1862: 7: Success after binutils: 4 commits new ef634133b4c 208: onsuccess: #1865: 7: Success after linux: 12 commits new 36b450c8a5b 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qe [...] new ee541750d9d 210: onsuccess: #1868: 7: Success after binutils: 7 commits new d0c5688465d 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/ [...] new 7e7868d7332 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/ [...] new 9a8b3aefca7 213: onsuccess: #1889: 7: Success after gcc: 5 commits new 7216cc9349a 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/ [...] new 8d4eeead57e 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/ [...] new 0e14b06cfd3 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits new 4151844bc20 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 1 [...] new 5a3e899c1ae 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/ [...] new 13159da644d 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 [...] new 874cc1c597a 220: onsuccess: #1898: 7: Success after binutils/linux/glib [...] 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 (bd3bd82c5cf) \ 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 1792 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2772 bytes 04-build_abe-binutils/console.log.xz | Bin 32588 -> 32196 bytes 05-build_abe-stage1/console.log.xz | Bin 73636 -> 73984 bytes 07-build_abe-linux/console.log.xz | Bin 8916 -> 8492 bytes 08-build_abe-glibc/console.log.xz | Bin 244608 -> 243956 bytes 09-build_abe-stage2/console.log.xz | Bin 204492 -> 206312 bytes 10-build_abe-gdb/console.log.xz | Bin 39440 -> 39120 bytes 11-build_abe-qemu/console.log.xz | Bin 31364 -> 30892 bytes 12-check_regression/console.log.xz | Bin 3676 -> 4172 bytes 13-update_baseline/console.log | 68 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++--------- 20 files changed, 59 insertions(+), 59 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-lts-allyesconfig updated (def57837627 -> 5f4b3dec9b3)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-lts-allyesconfig in repository toolchain/ci/base-artifacts. from def57837627 33: onsuccess: #408: all: Success after binutils/gcc/qemu: [...] new 5f4b3dec9b3 34: onsuccess: #409: all: Success after binutils/gcc/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1736 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 30032 -> 30084 bytes 04-build_abe-stage1/console.log.xz | Bin 86736 -> 86780 bytes 05-build_abe-qemu/console.log.xz | Bin 30364 -> 30100 bytes 06-build_linux/console.log.xz | Bin 3448 -> 4260 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 3548 -> 3800 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 18 files changed, 28 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allyesconfig updated (25a2505e078 -> 2140c4e177f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allyesconfig in repository toolchain/ci/base-artifacts. from 25a2505e078 32: onsuccess: #504: 33: Success after binutils/gcc/qemu: 9 [...] new 2140c4e177f 33: onsuccess: #505: 33: Success after binutils/gcc/linux/q [...] 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 1764 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 31848 -> 31932 bytes 04-build_abe-stage1/console.log.xz | Bin 73524 -> 73160 bytes 05-build_abe-qemu/console.log.xz | Bin 31088 -> 31040 bytes 06-build_linux/console.log.xz | Bin 3740 -> 3736 bytes 08-check_regression/console.log.xz | Bin 4160 -> 4276 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 16 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (cfad959d657 -> a1352ac9930)

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 cfad959d657 400: onsuccess: #2362: 1: Success after binutils/gcc: 6 commits discards 3e8594da11d 399: onsuccess: #2361: 1: Success after gcc: 10 commits discards a8b8ac9eb90 398: onsuccess: #2360: 1: Success after binutils/gcc: 9 commits discards cab5ea3f794 397: onsuccess: #2359: 1: Success after binutils/gcc: 10 commits discards 57131b6d12f 396: onsuccess: #2358: 1: Success after binutils/gcc: 9 commits discards 2a2df22e0d0 395: onsuccess: #2357: 1: Success after binutils/gcc: 3 commits discards 5c16db7953d 394: onsuccess: #2356: 1: Success after binutils/gcc: 6 commits discards a51968ed16a 393: onsuccess: #2355: 1: Success after binutils/gcc: 8 commits discards 83545f7233d 392: onsuccess: #2354: 1: Success after gcc: 5 commits discards 30789fcfda7 391: onsuccess: #2353: 1: Success after binutils/gcc: 8 commits discards ca348b79c86 390: onsuccess: #2352: 1: Success after binutils/gcc: 15 commits discards dba1c444814 389: onsuccess: #2351: 1: Success after binutils/gcc: 12 commits discards adf9c31a994 388: onsuccess: #2350: 1: Success after binutils/gcc: 13 commits discards 062549aa2e1 387: onsuccess: #2349: 1: Success after binutils/gcc: 6 commits discards babe97a1416 386: onsuccess: #2348: 1: Success after binutils/gcc: 10 commits discards 8a6da25bc90 385: onsuccess: #2347: 1: Success after binutils/gcc: 12 commits discards e6cc928c1eb 384: onsuccess: #2346: 1: Success after binutils/gcc: 8 commits discards 9eea81f702e 383: onsuccess: #2345: 1: Success after binutils/gcc: 3 commits discards b0edcaf2ffb 382: onsuccess: #2344: 1: Success after binutils/gcc: 7 commits discards ccc377c809b 381: onsuccess: #2343: 1: Success after gcc: 2 commits discards 9c25c1d9388 380: onsuccess: #2342: 1: Success after gcc: 3 commits discards 5a32924e68b 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-4 [...] discards 533a4769474 378: onsuccess: #2340: 1: Success after binutils: 2 commits discards 313dbf0a4b2 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits discards f80b74b2d7c 376: onsuccess: #2338: 1: Success after gcc: 2 commits discards 0e9b24f0b1b 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits discards c7f753dd39f 374: onsuccess: #2336: 1: Success after gcc: 4 commits discards 381e4391af2 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits discards df6dae62ca1 372: onsuccess: #2334: 1: Success after gcc: 5 commits discards 4842230d97f 371: onsuccess: #2333: 1: Success after binutils: 5 commits discards dbff8d9173e 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits discards cb3226c1a08 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits discards eb0a6451e44 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits discards 1dbd3b1ebf7 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits discards a151459ca71 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits discards 962045c4c73 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits discards 7083a36f8bd 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits discards 7807d670364 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits discards 2ad767ab693 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits discards 733c65bf750 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits discards 13627727c79 360: onsuccess: #2317: 1: Success after binutils: 4 commits discards f57f45be406 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint- [...] discards cd06d568eea 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits discards 6dfbb8a1260 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits discards f44aed6d590 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits discards 7c35cca8ec3 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits discards 262f19a5d71 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits discards 09788c26bd7 353: onsuccess: #2309: 1: Success after gcc: 7 commits discards 3bc6e7a6fe6 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits discards 92842f512c7 351: onsuccess: #2307: 1: Success after binutils: 2 commits discards e2b67b00682 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits discards 87c7597179e 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits discards 4fa038439bd 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits discards 3ae7e32a65d 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits discards b0b069533e5 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits discards fa2ec8abfb3 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits discards 7617e72f285 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits discards f7596c7d355 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits discards aae03bc468f 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits discards 080a81ba900 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits discards 503140db441 340: onsuccess: #2296: 1: Success after gcc: 3 commits discards d85692a1fda 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits discards 70eb7bf2ac1 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits discards 38d9a45abe8 337: onsuccess: #2293: 1: Success after gcc: 21 commits discards 08fb72af138 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits discards 796483746df 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits discards 90c99920ab2 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits discards 5aa6cf957dc 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-4 [...] discards e1c93ce8b6d 332: onsuccess: #2288: 1: Success after gcc: 2 commits discards 4883c1052e0 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint- [...] discards 690f6c72efc 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits discards 56397df0f63 329: onsuccess: #2285: 1: Success after gcc: 8 commits discards e9b23f1887c 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint- [...] discards 28c14879a11 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits discards ca6f272d05a 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits discards a6d8b881591 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits discards c04dd123135 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits discards 628d644eb7b 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits discards fd7a93cbf21 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits discards ca44a9ab825 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits discards c5c490a0b0c 320: onsuccess: #2274: 1: Success after gcc: 5 commits discards 09effda1070 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits discards 06025a46b04 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits discards 09b7080ec72 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits discards 45309087b5a 316: onsuccess: #2270: 1: Success after gcc: 2 commits discards 41ffa95ddad 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits discards c802e73f661 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits discards e93985b4f1e 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits discards 6d676a523d1 312: onsuccess: #2265: 1: Success after binutils: 2 commits discards 318188f4142 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint- [...] discards 020a75abedc 310: onsuccess: #2259: 1: Success after binutils: 2 commits discards fd3bd46130b 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint- [...] discards a9a7d1d6a3f 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint- [...] discards 33cc1ed657e 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint- [...] discards 01c7677ed66 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint- [...] discards 853049b6ffe 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits discards 16d826cd67a 304: onsuccess: #2243: 1: Success after binutils/gcc: 23 commits discards cd3ba86ae2a 303: onsuccess: #2242: 1: Success after binutils/gcc: 17 commits discards 0a66373decc 302: onsuccess: #2241: 1: Success after binutils/gcc: 10 commits discards 89b264813a5 301: onsuccess: #2240: 1: Success after binutils/gcc: 10 commits discards 7da58ecefc6 300: onsuccess: #2239: 1: Success after binutils/gcc: 20 commits new c0f30443ab2 300: onsuccess: #2239: 1: Success after binutils/gcc: 20 commits new 1eafd7303d5 301: onsuccess: #2240: 1: Success after binutils/gcc: 10 commits new 2ceec8e06d7 302: onsuccess: #2241: 1: Success after binutils/gcc: 10 commits new bf6e11b3f4c 303: onsuccess: #2242: 1: Success after binutils/gcc: 17 commits new 2ed40c5dc0c 304: onsuccess: #2243: 1: Success after binutils/gcc: 23 commits new 0af392be7cf 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits new 63309ef5811 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint- [...] new 80ef2e5fa5f 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint- [...] new d5828e85fc5 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint- [...] new 72e6f2f190f 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint- [...] new a88b8bf8f98 310: onsuccess: #2259: 1: Success after binutils: 2 commits new b140d2c832f 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint- [...] new 7406897dde7 312: onsuccess: #2265: 1: Success after binutils: 2 commits new 24dc327693c 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits new 2e50cea62a6 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits new ba452715645 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits new 2538c88bb24 316: onsuccess: #2270: 1: Success after gcc: 2 commits new 6faaca58576 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits new afe382a36ec 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits new 5ee9514aa35 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits new 7f257ed3478 320: onsuccess: #2274: 1: Success after gcc: 5 commits new 50915f678c2 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits new 5923b48a508 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits new 7517e217565 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits new f5e188d84e8 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits new 2a865cb3f76 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits new e1374e91b35 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits new 044b3091252 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits new 564f38103f7 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint- [...] new c339345f714 329: onsuccess: #2285: 1: Success after gcc: 8 commits new e45bdc23fdf 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits new 463413e4f5b 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint- [...] new a83ad0e2359 332: onsuccess: #2288: 1: Success after gcc: 2 commits new 38ee67803d8 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-4 [...] new 10da3251a2e 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits new 763440050d5 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits new 3b63f519891 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits new 66b42b71bad 337: onsuccess: #2293: 1: Success after gcc: 21 commits new f512a06fe39 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits new 1e28a0a0e32 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits new b82c172f564 340: onsuccess: #2296: 1: Success after gcc: 3 commits new b8d4e853501 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits new 64fd480c6b4 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits new 5084fd6c31e 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits new 1d8948cdefa 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits new d21f118ca99 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits new a1b4e100f25 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits new 10df72e1c68 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits new 935f6cf30ef 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits new 390f67245db 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits new e2c49174ba1 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits new 41c719580a8 351: onsuccess: #2307: 1: Success after binutils: 2 commits new c9e45a927d9 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits new fe1fac14456 353: onsuccess: #2309: 1: Success after gcc: 7 commits new 5b5341e5c1f 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits new 3b6972bf174 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits new 31ae611a6b5 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits new 5bb9367e227 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits new 6661248aadb 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits new 535d589c3f2 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint- [...] new f6045cdbef4 360: onsuccess: #2317: 1: Success after binutils: 4 commits new 9725f59d867 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits new a05cae3bcdf 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits new 98206e4fdda 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits new 849c3eb21cf 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits new 0e7c59010b3 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits new c3e7a678d79 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits new abd0c0ac792 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits new a3ba43414e6 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits new b077c2afc91 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits new 6193167601f 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits new aeead097209 371: onsuccess: #2333: 1: Success after binutils: 5 commits new 09d52680a55 372: onsuccess: #2334: 1: Success after gcc: 5 commits new df12acaf461 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits new 03c68fbf77d 374: onsuccess: #2336: 1: Success after gcc: 4 commits new 097c5c04d8b 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits new 546a76ab3e2 376: onsuccess: #2338: 1: Success after gcc: 2 commits new bcc5b6c6804 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits new 9bcb0f53f6f 378: onsuccess: #2340: 1: Success after binutils: 2 commits new 92236e3e0b1 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-4 [...] new 21da428a94a 380: onsuccess: #2342: 1: Success after gcc: 3 commits new 88bb83072b8 381: onsuccess: #2343: 1: Success after gcc: 2 commits new 303d6863f23 382: onsuccess: #2344: 1: Success after binutils/gcc: 7 commits new eafdb8ab78f 383: onsuccess: #2345: 1: Success after binutils/gcc: 3 commits new dec6f7c40b7 384: onsuccess: #2346: 1: Success after binutils/gcc: 8 commits new f74c973a3d0 385: onsuccess: #2347: 1: Success after binutils/gcc: 12 commits new 82658625089 386: onsuccess: #2348: 1: Success after binutils/gcc: 10 commits new fdce20743e0 387: onsuccess: #2349: 1: Success after binutils/gcc: 6 commits new c06579ee5f5 388: onsuccess: #2350: 1: Success after binutils/gcc: 13 commits new 48e4d486af1 389: onsuccess: #2351: 1: Success after binutils/gcc: 12 commits new 4db47a1c5cd 390: onsuccess: #2352: 1: Success after binutils/gcc: 15 commits new d550f451456 391: onsuccess: #2353: 1: Success after binutils/gcc: 8 commits new a015dcbdc1a 392: onsuccess: #2354: 1: Success after gcc: 5 commits new aa955d7939b 393: onsuccess: #2355: 1: Success after binutils/gcc: 8 commits new ecfea5f9958 394: onsuccess: #2356: 1: Success after binutils/gcc: 6 commits new 53d167c8a98 395: onsuccess: #2357: 1: Success after binutils/gcc: 3 commits new 70d816076ce 396: onsuccess: #2358: 1: Success after binutils/gcc: 9 commits new 5c925a19378 397: onsuccess: #2359: 1: Success after binutils/gcc: 10 commits new 732f0e92e83 398: onsuccess: #2360: 1: Success after binutils/gcc: 9 commits new 8c8a39f8cbc 399: onsuccess: #2361: 1: Success after gcc: 10 commits new e6f6ae2208d 400: onsuccess: #2362: 1: Success after binutils/gcc: 6 commits new a1352ac9930 401: onsuccess: #2363: 1: Success after gdb-12-branchpoint- [...] 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 (cfad959d657) \ 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 1776 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 40440 -> 41428 bytes 04-build_abe-gcc/console.log.xz | Bin 215568 -> 216656 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3876 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2648 -> 2716 bytes 07-check_regression/console.log.xz | Bin 4600 -> 4312 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 6 +- 08-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- sumfiles/g++.log.xz | Bin 3612120 -> 3611384 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 3158724 -> 3167780 bytes sumfiles/gcc.sum | 5052 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1043584 -> 1048044 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2204 -> 2184 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 218640 -> 219336 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 458096 -> 454852 bytes sumfiles/libstdc++.sum | 10 +- 30 files changed, 2681 insertions(+), 2681 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (eaea9d8dc85 -> f4cabb5ef32)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards eaea9d8dc85 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/ [...] discards 2e69a1ed6b8 204: onsuccess: #2435: 1: Success after linux: 3 commits discards fc4680c0eec 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards b3aad981ee6 202: onsuccess: #2431: 1: Success after linux: 944 commits discards 70133483d74 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards 9aae37828c2 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 116d098655a 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/ [...] discards 749a631f270 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/ [...] discards 53d442f39d7 197: onsuccess: #2348: 1: Success after linux: 190 commits discards aa5650d9a0e 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 4 [...] discards a9b38d58493 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/ [...] discards 8ad44362fe6 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/ [...] discards fdd8deb7dd7 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/ [...] discards 0b21cb4a83e 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/ [...] discards 386e2e21b59 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 1a8695cdaa4 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/ [...] discards d3b0567d0e5 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/ [...] discards fabd1edd71f 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/ [...] discards c6fbc907c5f 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/ [...] discards 386b5fa970d 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/ [...] discards 2a5dc136275 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/ [...] discards 9d156c09fc3 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/ [...] discards a0f853b97f2 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/ [...] discards cecb94a0d08 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/ [...] discards d693ff4a565 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/ [...] discards c439dc21404 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/ [...] discards 980cf91736f 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/ [...] discards f393c0630ef 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] discards 9e081c5757f 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards 44d44117db1 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] discards dc17541e05c 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] discards d6a7f33544a 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 2 [...] discards 0d3df11e02c 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards b7a1e8abaec 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] discards c5f77da51b7 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/ [...] discards 6479678861d 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/ [...] discards 14e8a0c0a24 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/ [...] discards af91b11bf52 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/ [...] discards 2a7bbd9bf36 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qem [...] discards e2a8c5c4d40 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards c51bc82e3a4 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 951982f031d 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/ [...] discards 17341af2bb5 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/ [...] discards 3ce2784c855 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/ [...] discards 4ee12ae2e5b 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/ [...] discards d25bbbb7b4c 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/ [...] discards e1f52b7d8eb 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 19 [...] discards d6df413e78e 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] discards 2e0701ad7a2 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 [...] discards 1bae9d44776 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/ [...] discards d6e2d6b1c84 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] discards 19b7a823ec1 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 1 [...] discards 5c8346f9011 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 [...] discards 7b570ea3f52 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 [...] discards 4cb0a6bb38e 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 95e29710333 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 40caf1971f6 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/ [...] discards 5d8f8d831c6 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 [...] discards 70e46190eed 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 1 [...] discards 91c3d6622fe 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 1b0bbb6651b 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/ [...] discards a9798a5b342 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/ [...] discards ab94f3dd498 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qe [...] discards 165312935ac 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards ce340ff5174 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 [...] discards 97f0fa53a4c 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/ [...] discards be28ad88ce4 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 1 [...] discards 10ac64cfbde 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 [...] discards 077c4b36d88 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/ [...] discards f6e69abea56 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qe [...] discards 813fc284883 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards a6e2fca1563 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 1 [...] discards c4ab765d7e9 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/ [...] discards 9f6e96bf472 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/ [...] discards 9dda70e82b4 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 1 [...] discards b18f3845b02 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 3 [...] discards 08fcd4eedd8 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/ [...] discards fa4e3d2fa62 128: onsuccess: #2163: 1: Success after linux: 23 commits discards bfcc51bae1e 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 55401f80870 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-2 [...] discards b26358bfa5a 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/ [...] discards 43abe47a7a0 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 89f8c237a12 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-2 [...] discards 5e00769b37e 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 [...] discards 6709324f99e 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/ [...] discards cb44e021b95 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/ [...] discards ef0222b0400 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/ [...] discards 415412cef50 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/ [...] discards 0a083487f0d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/ [...] discards b5f6d282b9e 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 [...] discards fbf87d6e58d 115: onsuccess: #2147: 1: Success after binutils/linux/glib [...] discards 180cb114090 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/ [...] discards 8b992291bab 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/ [...] discards f6fedfd1e24 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/ [...] discards 0e1cba9b572 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/ [...] discards 210ec7ef6c6 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/ [...] discards 4660259b4ff 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 882efdfefcc 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 [...] discards cbaa487e43e 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 [...] discards af56e6d03c8 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/ [...] discards b3df08b672b 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-2 [...] new 68dea9ed377 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-2 [...] new e38eefb0eaf 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/ [...] new ebf3f282cef 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 [...] new 3c0c6d0a452 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 [...] new 60ce40b5117 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 2e7b1dbbfcd 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/ [...] new 32bde74b07f 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/ [...] new c07d53e1408 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/ [...] new a8ad5401210 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/ [...] new 16a15887730 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/ [...] new e7e719f5c06 115: onsuccess: #2147: 1: Success after binutils/linux/glib [...] new 5a5e991ed65 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 [...] new 1adbc11ddf0 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/ [...] new 86d9050a8c2 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/ [...] new 2082eb8e2fe 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/ [...] new 90d516d34e1 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/ [...] new c117c7163fa 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/ [...] new d536ae933c4 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 [...] new e9b846dce15 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-2 [...] new 3544b108b1b 124: onsuccess: #2159: 1: Success after linux: 23 commits new 32411ef44b2 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/ [...] new 3b388511e26 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-2 [...] new 20837dd4ee5 127: onsuccess: #2162: 1: Success after gcc: 9 commits new d122e23325b 128: onsuccess: #2163: 1: Success after linux: 23 commits new 1bacd2dff70 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/ [...] new e6b9661f53e 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 3 [...] new 7fbeca6760d 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 1 [...] new 9704da47138 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/ [...] new 76f101f607d 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/ [...] new 7cad0ddfe74 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 1 [...] new 2dafb2f9c4e 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 23894730462 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qe [...] new 9b40b854dac 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/ [...] new cafd00070ed 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 [...] new 1085db7593a 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 1 [...] new 60508aa3a11 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/ [...] new 24a7fa23c78 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 [...] new a2c90cf9114 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 44a31c9c0fe 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qe [...] new 915a39511f0 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/ [...] new 93c53fa16aa 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/ [...] new 0b5b00e1a73 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new dc1d8556d32 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 1 [...] new a61f4e56fcd 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 [...] new fb8404304a6 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/ [...] new 827c7db0432 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 89168cc8a60 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 3863cee678c 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 [...] new c3616d6f186 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 [...] new ba2abe2a19d 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 1 [...] new 01438ce65fa 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] new 20709c0064b 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/ [...] new 75271f48d14 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 [...] new 58656e5c9e8 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] new 222fa0cfad8 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 19 [...] new 71afbc27708 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/ [...] new bf3cf6f45ea 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/ [...] new b6b4e148707 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/ [...] new 0fd4004fa13 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/ [...] new 45f14301215 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/ [...] new aa89eaa924f 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 75e0c14e6e1 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new f7c7e60de97 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qem [...] new 637a1c823d9 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/ [...] new d8d9ab3e6fd 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/ [...] new dee69d8bde8 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/ [...] new b53ff1bf3c1 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/ [...] new b58dc774f81 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] new 573cc6c06c4 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 9639742d807 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 2 [...] new b654249a91e 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] new a2d2b72bffc 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] new 5acbf14f778 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new b7df8acc9e6 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] new de94796374b 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/ [...] new e94060592bc 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/ [...] new c48a48879e3 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/ [...] new 3e688c4fadd 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/ [...] new f4e8b66fc58 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/ [...] new aae59b0df96 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/ [...] new 18dd76ae2ed 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/ [...] new 4e73a4ff04f 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/ [...] new d73e2ba2045 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/ [...] new 96df0bac828 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/ [...] new 98ba49e4a0f 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/ [...] new 81cd8932142 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/ [...] new 9f904180e99 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 9f6f82e1cc9 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/ [...] new 866731c6b31 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/ [...] new 1dfb20f7f31 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/ [...] new 813533868bd 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/ [...] new c4594be69be 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 4 [...] new 6ed5e8bc685 197: onsuccess: #2348: 1: Success after linux: 190 commits new de0907beab1 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/ [...] new 8f93f2f0ce5 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/ [...] new ff2976e8cdd 200: onsuccess: #2427: 1: Success after binutils: 274 commits new bed5c68d254 201: onsuccess: #2430: 1: Success after glibc: 26 commits new f68ad4971d6 202: onsuccess: #2431: 1: Success after linux: 944 commits new 2cd80e863df 203: onsuccess: #2433: 1: Success after binutils: 27 commits new 94368c5d0bb 204: onsuccess: #2435: 1: Success after linux: 3 commits new a6c3f0c8df6 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/ [...] new f4cabb5ef32 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/ [...] 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 (eaea9d8dc85) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1804 -> 1828 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 31968 -> 33348 bytes 04-build_abe-stage1/console.log.xz | Bin 73160 -> 73804 bytes 06-build_abe-linux/console.log.xz | Bin 8912 -> 9068 bytes 07-build_abe-glibc/console.log.xz | Bin 244776 -> 246360 bytes 08-build_abe-stage2/console.log.xz | Bin 204604 -> 206212 bytes 09-build_abe-gdb/console.log.xz | Bin 39168 -> 40700 bytes 10-build_abe-qemu/console.log.xz | Bin 30984 -> 31036 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3928 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2864 -> 2964 bytes 13-check_regression/console.log.xz | Bin 41552 -> 6608 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 61 +- 13-check_regression/mail-body.txt | 133 +- 13-check_regression/results.compare | 665 +-- 13-check_regression/results.compare2 | 7491 +------------------------------ 13-check_regression/results.regressions | 99 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 135 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 99 +- sumfiles/g++.log.xz | Bin 3409316 -> 3428088 bytes sumfiles/g++.sum | 91 +- sumfiles/gcc.log.xz | Bin 3036664 -> 3012088 bytes sumfiles/gcc.sum | 4443 +++++++++--------- sumfiles/gfortran.log.xz | Bin 1031528 -> 1041516 bytes sumfiles/gfortran.sum | 56 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213924 -> 213848 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429332 -> 431888 bytes sumfiles/libstdc++.sum | 7 +- 43 files changed, 2603 insertions(+), 10801 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 (2c2374dfd66 -> 32cd01e71e5)

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 2c2374dfd66 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 453d02c14dc 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 135485a0693 125: onsuccess: #614: 1: Success after linux: 12 commits discards 86225bfbc89 124: onsuccess: #612: 1: Success after binutils: 18 commits discards d3383d55057 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 3e5f3dd98ab 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards cb098a8151e 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards b695b094c76 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 6bdee3981a6 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards c8bdeeaf38b 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 78dbb507892 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards dee890956ed 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 4124ca8f15b 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 7f422d8c1df 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 305897747d2 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards d5869ad2fc3 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] discards c138a901fb4 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] discards f31fd64e318 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards bc5a550b975 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards debc72401f3 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 6cd10592337 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 53d561c4d21 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards bcf010d75d0 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards eaad4b49c73 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 907719d01cd 103: onsuccess: #589: 1: Success after binutils: 3 commits discards e36dc05bcb4 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 0fd51bc4b25 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] discards b8521d4897a 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] discards b9d545d9268 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] discards 192fd653300 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards b025e2ca802 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] discards 2190d569d8a 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] discards c332ed06598 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] discards 9f4c43160d9 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards a88ade51fd0 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] discards 365c3cb1bdf 92: onsuccess: #575: 1: Success after linux: 34 commits discards 88366a17d6e 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 733b7295cc5 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 247cf96fe78 89: onsuccess: #570: 1: Success after linux: 11 commits discards 4b2f5919a57 88: onsuccess: #569: 1: Success after glibc: 10 commits discards a0322a48bbb 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 34fa97ca2c0 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 510271a441c 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards af8adf3e05d 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 40ac4db1867 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] discards 38854cefa81 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] discards ab6ed98406c 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 6d7abb7f8e5 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] discards 765ab459eaa 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] discards c45fd36274f 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] discards e1160453018 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] discards 6de74ca9fc9 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] discards 62b53789c6d 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] discards 72a5c579d7b 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] discards 08350f9afbb 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards cb6a98d3595 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 17049668238 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] discards 1d30d3408b2 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards c8d85cb00a6 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] discards 85059d960f1 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] discards dfae4953443 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] discards 6dc0750916b 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 005afc7b27e 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] discards b0f4a6a0182 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 5830af80960 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards fe6e846c27b 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards 3bac0b689fd 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 53ebb0444c8 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] discards 50003c43af5 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards cb70bbb98ec 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards 9251431d905 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] discards 8995a6e2d40 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards e4c2d67a9d7 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards dc8a128c331 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] discards a243679d40e 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 28999ee0dce 52: onsuccess: #528: 1: Success after binutils: 8 commits discards ccca732e3f2 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 4c587fe9ce2 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] discards e5aefe94915 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] discards fa03b02958d 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] discards 54c452a96f6 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] discards 63b4cd18f70 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] discards e907136af55 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] discards 78d2af408ad 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] discards ad679065eb5 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] discards a0e67ab1bda 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] discards d2848274c4b 41: onsuccess: #514: 1: Success after linux: 64 commits discards bbdd880b179 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] discards 1265f3740c3 39: onsuccess: #511: 1: Success after binutils: 8 commits discards db30feb0485 38: onsuccess: #508: 1: Success after binutils: 3 commits discards 9209b336ed9 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] discards b0c2869c595 36: onsuccess: #505: 1: Success after glibc: 3 commits discards a2d3ecdc6af 35: onsuccess: #503: 1: Success after binutils: 11 commits discards edc3299bc4e 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards 6336ab8b148 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gd [...] discards 4ac0d4e11ec 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] discards ac31468dfe1 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] discards ebe8b26f622 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards 3ae7e646857 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards dd9957fdf0c 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gd [...] discards c8b3970c8da 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] new 2f0743b96d0 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] new 72b01856633 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gd [...] new a4e6d820937 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new 4c0c5ae9a1f 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new c4467da9776 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] new 17375f0d517 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] new 9225610186c 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gd [...] new 6f8663d9ece 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new 01ab6a5b618 35: onsuccess: #503: 1: Success after binutils: 11 commits new cc13176a485 36: onsuccess: #505: 1: Success after glibc: 3 commits new d2396ae268f 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] new 89d9c4a0200 38: onsuccess: #508: 1: Success after binutils: 3 commits new ac3d9e8a22d 39: onsuccess: #511: 1: Success after binutils: 8 commits new b9d8fd0e911 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] new daf89fb6fbe 41: onsuccess: #514: 1: Success after linux: 64 commits new d34e158ac3f 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] new 817b078d735 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] new 08a503a4937 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] new f1eda8da4cb 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] new 7e35d36ae29 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] new c778be0e8ac 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] new 10ef7e2d801 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] new c0c97dc97e1 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] new e045bc2e434 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] new 50760258bd7 51: onsuccess: #525: 1: Success after binutils: 8 commits new faac25f38f3 52: onsuccess: #528: 1: Success after binutils: 8 commits new bb5607902c5 53: onsuccess: #531: 1: Success after binutils: 12 commits new 65bb492b81a 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] new 3e8e97761e1 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new c9dcf2f5f5d 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new ac0f1a5be1b 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] new 0a6d4b82a72 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new 58d40176fc1 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new 5df1facb85d 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] new c5a5b9afb12 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new e91a7cb4423 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new b356ba1385c 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new d8ce8291483 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 267afe09cce 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] new 3dba6f2acce 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new f42f5cd7352 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] new 37ce545af90 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] new f30bb0589f6 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] new 0d5d97f1397 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new c7f0b396adc 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] new d461a0b4c8f 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 27bdf8e3a71 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 548bd548903 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] new 9a7c6bfcf2b 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] new f6094f26172 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] new 060e12a1758 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] new a27139648b1 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] new 8d2cd8829f6 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] new 6f62bd2abac 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] new 8e4650191d2 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 8d5df59ea2f 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] new 2d557ddaaad 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] new 987cb5e938b 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 46bf4389bd9 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new ea7539bc196 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new c48287db2d6 87: onsuccess: #567: 1: Success after binutils: 8 commits new 870d201dfc5 88: onsuccess: #569: 1: Success after glibc: 10 commits new d497862ceb7 89: onsuccess: #570: 1: Success after linux: 11 commits new b1db72f1fe5 90: onsuccess: #572: 1: Success after binutils: 15 commits new a155f350f25 91: onsuccess: #574: 1: Success after glibc: 3 commits new e0469a10ccf 92: onsuccess: #575: 1: Success after linux: 34 commits new cac1b5040ad 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] new 0b912b4c0fe 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new 3c9a8ef5867 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] new 7b79df4cd6e 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] new d346c4e9fed 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] new 8692ed667c3 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new b9944fa21f7 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] new eaf36046a5b 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] new 983e3cdc2e6 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] new 26962a09727 102: onsuccess: #586: 1: Success after binutils: 5 commits new 981c5d9551a 103: onsuccess: #589: 1: Success after binutils: 3 commits new 9a683f1b63c 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 3a69f0c2036 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new e73cc5d2de5 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new b4fa787af4f 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 02212f38317 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 5e59fadf726 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 5b3911bb6be 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new bda6e5ad778 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new 4976214f3ed 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new 96fee7438a9 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new b9b0eab93fb 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new fe49815732f 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 4a2a972fd4e 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 52f8b44a685 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new fe41e83a719 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 537b062f1d5 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 3e572c70e48 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 5bc5141cec1 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 67e96a5436a 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new a650e448d62 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 8677c703d42 124: onsuccess: #612: 1: Success after binutils: 18 commits new a8fe6db7ce0 125: onsuccess: #614: 1: Success after linux: 12 commits new bab8fe9f53d 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 505b2064b50 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 32cd01e71e5 128: onsuccess: #618: 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 (2c2374dfd66) \ 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 1796 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 53764 -> 54528 bytes 04-build_abe-gcc/console.log.xz | Bin 236120 -> 235808 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8600 -> 8940 bytes 07-build_abe-glibc/console.log.xz | Bin 235240 -> 236400 bytes 08-build_abe-gdb/console.log.xz | Bin 52000 -> 52532 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3880 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2392 -> 3040 bytes 11-check_regression/console.log.xz | Bin 20092 -> 19520 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 45 +- 11-check_regression/mail-body.txt | 180 +- 11-check_regression/results.compare | 88 +- 11-check_regression/results.compare2 | 6314 ++++++++++-------- 11-check_regression/results.regressions | 88 +- 12-update_baseline/console.log | 44 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 182 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 88 +- sumfiles/gdb.log.xz | Bin 1808684 -> 1738316 bytes sumfiles/gdb.sum | 10605 +++++++++++++++--------------- 31 files changed, 9364 insertions(+), 8326 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 (d04a13ae207 -> 938c8c2f5dd)

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 d04a13ae207 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards ac53ca3583f 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards 18a92f6494b 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards d1edaaeb629 118: onsuccess: #863: 1: Success after linux: 12 commits discards 75ae16f679b 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 795e13375ab 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards 08f94db2ecb 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards dbabd8cc56f 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 3a1cdf1a147 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 680343463d6 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 742a68a918e 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 16e733e634c 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 84ee35915ee 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards d455e0fc6fa 108: onsuccess: #850: 1: Success after gcc: 2 commits discards aee5cffd05a 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 6d7e069791a 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 059457bacdd 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards 395fb5addf4 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards cd82797f6a2 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards 8577c385c2d 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards ecc98a64c88 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 9abac687911 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards 8fa6ad95962 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards bb70f71dc60 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 7cfbb364a21 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards cc3d3f57c1a 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards e7c009c91d5 95: onsuccess: #835: 1: Success after binutils: 3 commits discards b4f5b9a7a35 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 7aaade82c24 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 3c708a5cb13 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 3ff8b02aa49 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards be62ad06e56 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards fc836ea4ecb 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 55a0f0ba1d4 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards 8876df3b2dd 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards a52c3c8e038 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards 84cecdc46a0 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards feab18af51e 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 1dbcb05d1e0 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 38fcd727b0c 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards 13856fffc15 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards 99e39120a9c 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards 334adb95c18 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards 9e9f635d719 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards bd106f71e95 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards d6a84952af9 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 75102afe700 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards c1ca7411af5 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards a53d1fe6c5a 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards 94d75eb4d63 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards ac6930b5466 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards 89a5c0738b3 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards cdc41291707 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards 0eaf5bad93f 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards 6cb1780ebe9 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards 146cb134aa5 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 9724e52a190 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards 85b5e42b8f9 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 01caf8b0701 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 101d34c5208 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards b4cb9742696 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 5da817e231d 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards db16fdc5df7 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 0e2f011b1df 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards bf302f382e9 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards 0d04972b3de 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards b27108279d3 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards a05f8e40ca0 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards f5b68dfe22b 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards d0dc6a5f499 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards 3acd5369329 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards 1a329a896d3 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards 755f69ad2ba 49: onsuccess: #785: 1: Success after binutils: 12 commits discards c4deaa5671f 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 623f6fffd32 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards c3e48d64dd9 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards 9148f6776f3 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards 851538ae099 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards a382d7ba1ac 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards afd9d778f2e 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards 0064ef484ba 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards b1456d77fa1 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards ad66afbb04e 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards fcd868f4a22 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards 14bdfe8c57e 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards 352da7305fb 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards c068f9ffd1e 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards 45290253906 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards 30d28ea9998 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards 6edeccbec08 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards 0814acfbb26 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards 40b3948168b 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards 8d90163205e 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards d0f3bd9e55d 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards 359a4253e35 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] discards 26f9a339173 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] discards 18ef88a2997 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] discards 1f437a786b0 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards 18c1b76b0eb 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards f239de4a29a 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 6e5c310f839 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 40170aebb3e 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new cffbe909eaa 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 2d99fcf2da6 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new aee9ae88126 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new e019796ea5a 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] new 35bacbd7022 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new 87da2a93fd0 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new 814639c6a0f 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new 0128510115d 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new 8e238301f88 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new 4478425bf59 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new 478733259e4 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new 710400165bb 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new bf722060785 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new b467311d5d0 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new 8439aa53fa5 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 4eb3fe35c48 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new e56a464e25a 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new d66341d0bd0 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new 67ce2b9c9b9 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new c35d11424dd 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new 8fead16106d 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 5ccbda5c7fe 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new 0b35e3c094a 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new f7544c7f766 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new 103d16e6ff8 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new 44b5aa0f94c 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new 15f45cec913 48: onsuccess: #782: 1: Success after binutils: 8 commits new 342dc70dec6 49: onsuccess: #785: 1: Success after binutils: 12 commits new 19ea697dc23 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new d4fdefa67b5 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new 266a19c752a 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new 874afaf62ea 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new e2597903787 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new 48e6b4d64ee 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new a336c841771 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 83bdbca7130 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new 92f3ac7119d 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new 07e85dfc293 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 68d6d6964c7 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new a678af267c6 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new c72451efbde 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 0da43428491 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new fc84cd0d4b0 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new c7794d5620c 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 6855073f9b9 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 2988d02f48c 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new 36661108391 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new 2c1a50cd5c4 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new 3efef04ece1 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new b9fc13c07be 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new b93aea0a697 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new 748df362bf8 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new 98dff52af97 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 30c650d9503 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new 3fe6b7fa737 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 221a4b254f2 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new e9272cc2ff2 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new d425672825a 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new e59b77d368f 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new 2d2b3722d60 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new f42cf02bb52 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new c1591ad500c 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 6d74a0ac510 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new d7ce545e822 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 43ebe76f54c 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new e3bfb65eaf9 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 6f4024cc56f 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new b94b5c8466c 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new ccbb5abc929 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 31878b09c53 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new f4f540b0c2f 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new a83a088a9b2 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new ea9c9e2bd4f 94: onsuccess: #832: 1: Success after binutils: 5 commits new 4769408e850 95: onsuccess: #835: 1: Success after binutils: 3 commits new 9d08d42163d 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new b43336b9f3c 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new 31934640ca3 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 81ae5437fd0 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new 585330ade68 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new 617107f8ef7 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new 65ec78064a8 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 4f3d71a62a2 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new 9325352def3 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new 8e9dd2f9f97 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new 2aba4dc57a2 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 971b1c040b3 107: onsuccess: #849: 1: Success after binutils: 5 commits new d05d5dbd5ec 108: onsuccess: #850: 1: Success after gcc: 2 commits new a76315a4bca 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new ea781c2d1cd 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 9885b361c0e 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new 06f43ddf6b4 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 1550a7e6edd 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new ac4bb239280 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new c60d51a2229 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 943ebf199f3 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new b1f047360f8 117: onsuccess: #861: 1: Success after binutils: 18 commits new ed5ba05234c 118: onsuccess: #863: 1: Success after linux: 12 commits new 8d707b2176c 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new 0c5493d2502 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new 11790d16ab0 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new 938c8c2f5dd 122: onsuccess: #867: 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 (d04a13ae207) \ 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 1740 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39676 -> 40060 bytes 04-build_abe-gcc/console.log.xz | Bin 212676 -> 214920 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8492 -> 8828 bytes 07-build_abe-glibc/console.log.xz | Bin 243216 -> 245532 bytes 08-build_abe-gdb/console.log.xz | Bin 39004 -> 39868 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3840 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2708 -> 2768 bytes 11-check_regression/console.log.xz | Bin 7728 -> 7896 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/mail-body.txt | 54 +- 11-check_regression/results.compare | 33 +- 11-check_regression/results.compare2 | 321 ++- 11-check_regression/results.regressions | 27 + 12-update_baseline/console.log | 56 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 56 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 27 + sumfiles/g++.log.xz | Bin 3728288 -> 3732384 bytes sumfiles/g++.sum | 162 +- sumfiles/gcc.log.xz | Bin 3303216 -> 3319476 bytes sumfiles/gcc.sum | 4788 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1075860 -> 1080408 bytes sumfiles/gfortran.sum | 50 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2272 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 231420 -> 231132 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 450116 -> 451804 bytes sumfiles/libstdc++.sum | 26 +- 43 files changed, 2911 insertions(+), 2775 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create 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/gnu-release-arm-mainline-allmodconfig updated (4b3e0696627 -> 87f9200b04f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-mainline-allmodconfig in repository toolchain/ci/base-artifacts. from 4b3e0696627 30: onsuccess: #438: boot: Success after binutils/gcc/linux [...] new 87f9200b04f 31: onsuccess: #439: boot: Success after binutils/gcc/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1844 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 30756 -> 30484 bytes 04-build_abe-stage1/console.log.xz | Bin 87352 -> 87448 bytes 05-build_abe-qemu/console.log.xz | Bin 30804 -> 30580 bytes 06-build_linux/console.log.xz | Bin 3332 -> 3400 bytes 07-boot_linux/console.log.xz | Bin 480 -> 480 bytes 08-check_regression/console.log.xz | Bin 4052 -> 3872 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 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-mainline-allnoconfig updated (acc35350a43 -> 1b809ec7a2f)

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-mainline-allnoconfig in repository toolchain/ci/base-artifacts. from acc35350a43 28: onsuccess: #441: all: Success after binutils: 39 commits new 1b809ec7a2f 29: onsuccess: #443: all: Success after binutils/llvm/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1764 -> 1968 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 32148 -> 32984 bytes 04-build_kernel_llvm/console.log.xz | Bin 64996 -> 65112 bytes 05-build_abe-qemu/console.log.xz | Bin 30752 -> 30588 bytes 06-build_linux/console.log.xz | Bin 3212 -> 3164 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 2988 -> 4404 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_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 | 31 +++++++++++++++++-------------- 17 files changed, 25 insertions(+), 22 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[linux] branch master updated (9857feb3f62a -> 3ecc37918c80)

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 linux. from 9857feb3f62a Merge tag 'soc-fixes-6.1-6' of git://git.kernel.org/pub/sc [...] new 5eef2141776d media: v4l2-dv-timings.c: fix too strict blanking sanity checks new 3ecc37918c80 Merge tag 'media/v6.1-4' of git://git.kernel.org/pub/scm/l [...] The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: drivers/media/v4l2-core/v4l2-dv-timings.c | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 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