Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[glibc] branch master updated (e5672763c4 -> 2f47198b04)

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 glibc. from e5672763c4 x86-64 strncpy: Properly handle the length parameter [BZ# 29839] new 2f47198b04 powerpc64: Remove old strncmp optimization 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: sysdeps/powerpc/powerpc64/multiarch/Makefile | 3 +- .../powerpc/powerpc64/multiarch/ifunc-impl-list.c | 2 - .../powerpc/powerpc64/multiarch/strncmp-power4.S | 23 --- sysdeps/powerpc/powerpc64/multiarch/strncmp.c | 5 +- sysdeps/powerpc/powerpc64/power4/strncmp.S | 225 --------------------- 5 files changed, 2 insertions(+), 256 deletions(-) delete mode 100644 sysdeps/powerpc/powerpc64/multiarch/strncmp-power4.S delete mode 100644 sysdeps/powerpc/powerpc64/power4/strncmp.S -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm updated (679bc164bcc -> 6a449c2b606)

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_fast_check_gdb/master-arm in repository toolchain/ci/base-artifacts. from 679bc164bcc 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 6a449c2b606 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] 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 1696 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2716 bytes 03-build_abe-binutils/console.log.xz | Bin 52488 -> 52396 bytes 04-build_abe-gcc/console.log.xz | Bin 234536 -> 234044 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8588 -> 8740 bytes 07-build_abe-glibc/console.log.xz | Bin 235620 -> 235588 bytes 08-build_abe-gdb/console.log.xz | Bin 51732 -> 51316 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3836 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3068 -> 2648 bytes 11-check_regression/console.log.xz | Bin 5748 -> 5768 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++++++++++----------------- sumfiles/gdb.log.xz | Bin 14504 -> 14496 bytes sumfiles/gdb.sum | 34 +++++++++++++++--------------- 25 files changed, 50 insertions(+), 50 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[gcc] branch master updated (d19aa6af663 -> 1998db0fa1f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from d19aa6af663 c++: Set the locus of the function result decl new 1998db0fa1f testsuite: Adjust dg-error for -fimplicit-constexpr The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/testsuite/g++.dg/cpp0x/constexpr-ex1.C | 6 +++--- gcc/testsuite/g++.dg/cpp23/constexpr-nonlit10.C | 4 ++-- gcc/testsuite/g++.dg/cpp23/constexpr-nonlit11.C | 4 ++-- gcc/testsuite/g++.dg/cpp2a/spaceship-eq3.C | 1 + 4 files changed, 8 insertions(+), 7 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (0bae2da739c -> 1f9b8e8fe26)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-arm in repository toolchain/ci/base-artifacts. discards 0bae2da739c 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: 2 [...] discards 15ac7539cb2 206: onsuccess: #1927: 7: Success after binutils/gcc/linux/ [...] discards 47657a9feb1 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 4 [...] discards 4f1e2162cc2 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 1 [...] discards 52e63e89830 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 1 [...] discards d99c75ad580 202: onsuccess: #1923: 7: Success after binutils/gcc/linux/ [...] discards dd874d44553 201: onsuccess: #1905: 7: Success after binutils/gcc/linux/ [...] discards 77789bbd8a0 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/ [...] discards 484d886223a 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/ [...] discards 3ae1e43c3b9 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/ [...] discards 4e626ed0dfe 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/ [...] discards c3f7484c71f 196: onsuccess: #1855: 4: Success after gcc: 30 commits discards 1046a679af0 195: force: #1854: 4: Failure after basepoints/gcc-13-3918- [...] discards 7d42f8779f5 194: force: #1853: 7: Success after gcc: 26 commits discards 4bad4b56b8a 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint- [...] discards e10aa361c65 192: onsuccess: #1848: 7: Success after linux: 213 commits discards 69fb2f2ed0f 191: onsuccess: #1846: 7: Success after binutils: 4 commits discards e6725ac9164 190: onsuccess: #1834: 7: Success after binutils: 25 commits discards 3c314f40313 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/ [...] discards 21fc2b85c5d 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/ [...] discards 5f2c1d73c6d 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/ [...] discards 4a52dd77102 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/ [...] discards bc87f7991d7 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/ [...] discards 3ed83aa1b86 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/ [...] discards 9729e7531cd 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/ [...] discards 0077f6989dd 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 [...] discards d2138dc2604 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/ [...] discards 6a18df66a1f 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/ [...] discards d2980843fc9 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/ [...] discards 4d64a52323e 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/ [...] discards e03c866cd29 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/ [...] discards f68a7189cfe 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/ [...] discards 2b088becfec 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 1 [...] discards 68b821c706a 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/ [...] discards 4926adf57e6 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qem [...] discards 2772443c65c 172: onsuccess: #1687: 7: Success after gcc: 11 commits discards 40ea08d39eb 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/ [...] discards 90252108732 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/ [...] discards cb4055b737e 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/ [...] discards 877f37ae60c 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 3 [...] discards 507cd3b39c3 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits discards 19003569757 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/ [...] discards 0d175e00565 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/ [...] discards e5af50c6474 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 1 [...] discards 116c22740f3 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 [...] discards e2cc0542295 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/ [...] discards e52604338ed 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/ [...] discards 457a5ef0368 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 1 [...] discards 4d33ce06404 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/ [...] discards 002d334b45c 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards c5ad5e2e070 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards 5e551ff4fd6 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards 5b6e6db6879 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/ [...] discards 5c421bcdd06 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/ [...] discards a0fc9882f89 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 2 [...] discards b8b0509bbe0 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/ [...] discards 1e20f2c4b3d 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/ [...] discards add24a69067 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/ [...] discards 4118d8e6e89 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 3 [...] discards 6c665010372 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards f607b489ec3 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/ [...] discards 2f5e0c0da45 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/ [...] discards c1fa37bbdd0 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 1 [...] discards 1b7662755cf 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 [...] discards ce5accfc234 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/ [...] discards ca3ed807631 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/ [...] discards 8b5af430b61 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards 66bd9249706 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/ [...] discards e5d3b7b5f7b 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards e8b680ce5b5 138: force: #1653: 1: Failure after basepoints/gcc-13-2871- [...] discards e2f41779dc9 137: force: #1652: 7: Success after basepoints/gcc-13-2870- [...] discards 83a04681b26 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards b6e8b22dd51 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 2 [...] discards b3990b028b0 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 1 [...] discards 0b2f68e7d6c 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/ [...] discards dbb40b85d4b 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 0cbadada04b 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 40f5a8dfe27 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/ [...] discards 0e176963f04 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 9737d4dc090 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 [...] discards e4b74eacef8 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 5375f3cdaba 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/ [...] discards f12b6b9d1d7 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/ [...] discards 31f1b7194ca 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/ [...] discards 5d8ca3ae5ca 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/ [...] discards b71897739ef 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/ [...] discards 6d5d5262f48 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 1 [...] discards fcb1ead8b33 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qe [...] discards 8a36fbaf7a7 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/ [...] discards ec26253d879 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 1 [...] discards 7dec500f978 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 7f4ffed68bb 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/ [...] discards f483a1c1884 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/ [...] discards 24304185998 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/ [...] discards ca25db00412 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 4a1dfba4ddf 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 [...] discards 6f2e9d3e0ef 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 [...] discards 0d8757b91ad 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/ [...] discards 939ec017f24 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/ [...] discards 3d036a5c386 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38edde [...] discards b7f0c1c11cc 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 3cd5d4de9a3 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 8c4a62e658e 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38edde [...] new 36cbe339856 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/ [...] new 82abaf27efa 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/ [...] new 7afd1145bdf 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 [...] new 2d6a52baa96 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 [...] new 6f046f5d196 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 3895406a19f 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/ [...] new 4fd041be2e0 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/ [...] new b0331f09285 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/ [...] new c85725f9046 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new f0042171a8c 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 1 [...] new 34a1ba4d79d 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/ [...] new 1a99561bf7f 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qe [...] new 243fffcfa36 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 1 [...] new 8b18a1719b9 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/ [...] new 69d4e3ee329 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/ [...] new 09dc28faa56 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/ [...] new 01bc26f239c 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/ [...] new a83e6cedee8 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/ [...] new 0bc4e035a94 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 2c0f239288f 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 [...] new 73188494bbe 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 5107ac7a29d 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/ [...] new e25162e8c10 131: onsuccess: #1644: 7: Success after gcc: 10 commits new bdce2fe20bf 132: onsuccess: #1645: 7: Success after linux: 23 commits new 755cb2495ff 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/ [...] new dcdac21f408 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 1 [...] new 8beb4c3abac 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 2 [...] new 31f8dd96067 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 5a7285f3345 137: force: #1652: 7: Success after basepoints/gcc-13-2870- [...] new 642bde1bc22 138: force: #1653: 1: Failure after basepoints/gcc-13-2871- [...] new 72bd91f5573 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 8537fdafabc 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/ [...] new d1ed46e22c2 141: onsuccess: #1656: 7: Success after gcc: 7 commits new e4703ffe810 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/ [...] new 0e0df639815 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/ [...] new a1c6c5cab02 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 [...] new 65c4eeadc6d 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 1 [...] new 14ec44e0dd0 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/ [...] new 6c27261ccde 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/ [...] new 35f8ec24bb9 148: onsuccess: #1663: 7: Success after glibc: 2 commits new a1793471daf 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 3 [...] new aaa104f256d 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/ [...] new 927254cd057 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/ [...] new 243272930af 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/ [...] new 5318f0e587e 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 2 [...] new 860909b07f0 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/ [...] new b329109105d 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/ [...] new d83a951a211 156: onsuccess: #1671: 7: Success after gcc: 3 commits new e4298787717 157: onsuccess: #1672: 7: Success after gcc: 2 commits new 58e70ce482c 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new a6a91b78d74 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/ [...] new 1eb3592c2b7 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 1 [...] new ca8f40f7340 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/ [...] new 4b6fbecfb2a 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/ [...] new 2de9bdce022 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 [...] new 01e44f6194d 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 1 [...] new 0aa1b72ba73 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/ [...] new b902378de64 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/ [...] new 8071a6800b1 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits new b92f9d80533 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 3 [...] new 55c36256f84 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/ [...] new f665a64e68c 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/ [...] new 41a676d0a60 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/ [...] new 70d80ef0b94 172: onsuccess: #1687: 7: Success after gcc: 11 commits new 97a64df3bb1 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qem [...] new 211beb55608 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/ [...] new 8095d15fff9 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 1 [...] new 1e373bd4e44 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/ [...] new 8e74c957871 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/ [...] new 176c018938d 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/ [...] new 11176db4d08 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/ [...] new de9bd3a6096 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/ [...] new 4a05feeacc9 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/ [...] new 4fea49dc8d5 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 [...] new 00347b70430 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/ [...] new a082e4a407c 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/ [...] new 1152a393377 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/ [...] new b411947156a 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/ [...] new 0440ae21ee3 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/ [...] new dac2bcd778d 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/ [...] new 5c545851b1c 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/ [...] new 989e19b79fc 190: onsuccess: #1834: 7: Success after binutils: 25 commits new c1459877edc 191: onsuccess: #1846: 7: Success after binutils: 4 commits new e5f4adc71c8 192: onsuccess: #1848: 7: Success after linux: 213 commits new 568e0e7b7e5 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint- [...] new d7c1b28b378 194: force: #1853: 7: Success after gcc: 26 commits new dceaba3392c 195: force: #1854: 4: Failure after basepoints/gcc-13-3918- [...] new 5df054c87cd 196: onsuccess: #1855: 4: Success after gcc: 30 commits new fa8c09c7699 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/ [...] new 34395140041 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/ [...] new 6e0d250308c 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/ [...] new f90b02dba13 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/ [...] new 1d96b067a04 201: onsuccess: #1905: 7: Success after binutils/gcc/linux/ [...] new 223bbf4c2f8 202: onsuccess: #1923: 7: Success after binutils/gcc/linux/ [...] new bfd11fac9ef 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 1 [...] new 9cd190db6a5 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 1 [...] new f50ddd14916 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 4 [...] new fca90046fa6 206: onsuccess: #1927: 7: Success after binutils/gcc/linux/ [...] new 395fe1076d0 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: 2 [...] new 1f9b8e8fe26 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (0bae2da739c) \ 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 1684 -> 1632 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 31400 -> 31368 bytes 05-build_abe-stage1/console.log.xz | Bin 91276 -> 91360 bytes 07-build_abe-linux/console.log.xz | Bin 8724 -> 8700 bytes 08-build_abe-glibc/console.log.xz | Bin 235980 -> 235284 bytes 09-build_abe-stage2/console.log.xz | Bin 225200 -> 225484 bytes 10-build_abe-gdb/console.log.xz | Bin 38652 -> 38488 bytes 11-build_abe-qemu/console.log.xz | Bin 30344 -> 30640 bytes 12-check_regression/console.log.xz | Bin 3788 -> 3392 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 ++++++++-------- 18 files changed, 54 insertions(+), 54 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-defconfig updated (24d8e6aadc0 -> ee13ad8700d)

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-defconfig in repository toolchain/ci/base-artifacts. from 24d8e6aadc0 30: onsuccess: #511: boot: Success after binutils/gcc/linux [...] new ee13ad8700d 31: onsuccess: #512: boot: Success after binutils/gcc/qemu: [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1728 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 32660 -> 31648 bytes 04-build_abe-stage1/console.log.xz | Bin 73340 -> 72952 bytes 05-build_abe-qemu/console.log.xz | Bin 31580 -> 30892 bytes 06-build_linux/console.log.xz | Bin 6264 -> 6212 bytes 07-boot_linux/console.log.xz | Bin 6276 -> 6220 bytes 08-check_regression/console.log.xz | Bin 4644 -> 3924 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 17 files changed, 25 insertions(+), 25 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[binutils-gdb] branch master updated (ac57bf55472 -> f9f593ddb2d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from ac57bf55472 Add Jan Beulich as an x86_64 maintainer. new e26d0dab101 gdb: merge solib-frv aix-solib debug options into "set/show [...] new f8baaa2b0bf gdb: add some debug statements to solib-svr4.c new f9f593ddb2d gdb/linux-nat: add pid parameter to linux_proc_xfer_memory_partial The 3 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: gdb/NEWS | 12 +++++++ gdb/doc/gdb.texinfo | 18 +++------- gdb/linux-nat.c | 18 +++++----- gdb/solib-aix.c | 39 ++++------------------ gdb/solib-frv.c | 95 +++++++++++++---------------------------------------- gdb/solib-svr4.c | 14 +++++++- gdb/solib.c | 16 +++++---- gdb/solib.h | 12 +++++++ 8 files changed, 90 insertions(+), 134 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (b19dd8dbb28 -> 1957c885b33)

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 b19dd8dbb28 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits discards d8291df0545 372: onsuccess: #2334: 1: Success after gcc: 5 commits discards 9313a05e468 371: onsuccess: #2333: 1: Success after binutils: 5 commits discards d2b69c0201b 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits discards 90ce832385b 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits discards 59efef9aadf 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits discards a429f78ee31 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits discards 9cbe2637126 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits discards 836e55c53c1 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits discards e8c04b4bd7a 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits discards 24aa79089c1 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits discards 2fc072c3a0f 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits discards f7ad32b87db 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits discards 3d040875574 360: onsuccess: #2317: 1: Success after binutils: 4 commits discards d6e2d2ced7a 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint- [...] discards 6aadbbc5c32 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits discards d4e605edba5 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits discards 99d3986fe01 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits discards 20b69b940d5 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits discards d8b389ac79e 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits discards acc252b3ea1 353: onsuccess: #2309: 1: Success after gcc: 7 commits discards 865c50b10da 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits discards 1e957013191 351: onsuccess: #2307: 1: Success after binutils: 2 commits discards 235c6f42bd1 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits discards 378d090a7b6 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits discards 71e60ee467f 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits discards 32c80a53dfd 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits discards 6b603755c9f 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits discards 857755cf2cf 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits discards 05b736de055 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits discards 9edc592eedb 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits discards b30d04d5f36 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits discards 9ee9af8a1ef 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits discards 6412f5bc512 340: onsuccess: #2296: 1: Success after gcc: 3 commits discards d9d2518ffc2 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits discards 016d272950d 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits discards 5ac1624d590 337: onsuccess: #2293: 1: Success after gcc: 21 commits discards 92a2527f54f 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits discards 82b823f01b5 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits discards 954b8695087 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits discards c034b29c5a5 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-4 [...] discards 86c6ae06ced 332: onsuccess: #2288: 1: Success after gcc: 2 commits discards 84afaf3c642 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint- [...] discards 868ca0d5ae7 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits discards ffaaccd5834 329: onsuccess: #2285: 1: Success after gcc: 8 commits discards 3b679789d97 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint- [...] discards 01ad9a1b136 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits discards 155222cc629 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits discards 7eed3ca27a4 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits discards e789693344e 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits discards 53078cd0680 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits discards 225dab05503 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits discards 68f26cfe863 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits discards 0d8f5ce1bc9 320: onsuccess: #2274: 1: Success after gcc: 5 commits discards 33d9c4512c5 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits discards b3fa8ee8d79 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits discards fb33c657845 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits discards 1992aa3683e 316: onsuccess: #2270: 1: Success after gcc: 2 commits discards 9e448d4e402 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits discards f5971f31efd 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits discards e227a73e9e1 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits discards a75ff06600d 312: onsuccess: #2265: 1: Success after binutils: 2 commits discards 73bb83063c9 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint- [...] discards 5f258302ebf 310: onsuccess: #2259: 1: Success after binutils: 2 commits discards 3f5fc9d48b3 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint- [...] discards 5689b98a787 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint- [...] discards 508ff4400e4 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint- [...] discards 0fdbacb39a0 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint- [...] discards a3116493a7f 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits discards 7a295071a62 304: onsuccess: #2243: 1: Success after binutils/gcc: 23 commits discards d2795259ccb 303: onsuccess: #2242: 1: Success after binutils/gcc: 17 commits discards 1454ac53be1 302: onsuccess: #2241: 1: Success after binutils/gcc: 10 commits discards 5bd0d4dd962 301: onsuccess: #2240: 1: Success after binutils/gcc: 10 commits discards c440f39c334 300: onsuccess: #2239: 1: Success after binutils/gcc: 20 commits discards 5245726e440 299: onsuccess: #2238: 1: Success after binutils/gcc: 12 commits discards f5eaa399978 298: onsuccess: #2237: 1: Success after binutils/gcc: 9 commits discards fbd70531709 297: onsuccess: #2236: 1: Success after binutils/gcc: 9 commits discards 7afa2e4951a 296: onsuccess: #2235: 1: Success after binutils/gcc: 14 commits discards da5672f5465 295: onsuccess: #2234: 1: Success after binutils/gcc: 33 commits discards 6123294328d 294: onsuccess: #2233: 1: Success after binutils/gcc: 4 commits discards 940064cf06b 293: onsuccess: #2232: 1: Success after binutils/gcc: 5 commits discards 34cf650503a 292: onsuccess: #2231: 1: Success after binutils/gcc: 19 commits discards 19808d166b8 291: onsuccess: #2230: 1: Success after binutils/gcc: 31 commits discards cab8a10804f 290: onsuccess: #2229: 1: Success after binutils/gcc: 12 commits discards 440adf29d95 289: onsuccess: #2228: 1: Success after binutils/gcc: 11 commits discards c4a74abaff6 288: onsuccess: #2227: 1: Success after binutils/gcc: 16 commits discards 21b808ebb01 287: onsuccess: #2226: 1: Success after binutils/gcc: 38 commits discards 1d00fcdf674 286: onsuccess: #2225: 1: Success after binutils/gcc: 7 commits discards 67085e329aa 285: onsuccess: #2224: 1: Success after binutils/gcc: 2 commits discards 9f8d33bc9e7 284: onsuccess: #2223: 1: Success after binutils/gcc: 5 commits discards 42eabb9b833 283: onsuccess: #2222: 1: Success after gcc: 4 commits discards bd1fb212904 282: onsuccess: #2221: 1: Success after gcc: 2 commits discards a3bf11f4bd1 281: onsuccess: #2220: 1: Success after binutils/gcc: 4 commits discards 3fdc5f17555 280: onsuccess: #2219: 1: Success after binutils/gcc: 10 commits discards 0fe544986b2 279: onsuccess: #2218: 1: Success after basepoints/gcc-13-3 [...] discards ec84ced2b97 278: onsuccess: #2217: 1: Success after binutils: 7 commits discards de4435a2db8 277: onsuccess: #2216: 1: Success after binutils: 2 commits discards fb29833fa7d 276: onsuccess: #2215: 1: Success after binutils/gcc: 44 commits discards 3144c772a69 275: onsuccess: #2214: 1: Success after binutils/gcc: 14 commits discards 92e10ba3a59 274: onsuccess: #2213: 1: Success after binutils/gcc: 12 commits discards 4c120597f46 273: onsuccess: #2212: 1: Success after binutils/gcc: 13 commits new 05a2f5c2cc9 273: onsuccess: #2212: 1: Success after binutils/gcc: 13 commits new d86329c5fad 274: onsuccess: #2213: 1: Success after binutils/gcc: 12 commits new 2bab5c6efa7 275: onsuccess: #2214: 1: Success after binutils/gcc: 14 commits new a1fae772b12 276: onsuccess: #2215: 1: Success after binutils/gcc: 44 commits new 9d7559dfaca 277: onsuccess: #2216: 1: Success after binutils: 2 commits new 9dcbf4903f6 278: onsuccess: #2217: 1: Success after binutils: 7 commits new 38d118138a7 279: onsuccess: #2218: 1: Success after basepoints/gcc-13-3 [...] new 1b68cd350a1 280: onsuccess: #2219: 1: Success after binutils/gcc: 10 commits new 65c4b997f3c 281: onsuccess: #2220: 1: Success after binutils/gcc: 4 commits new c415de57b33 282: onsuccess: #2221: 1: Success after gcc: 2 commits new c5123773f51 283: onsuccess: #2222: 1: Success after gcc: 4 commits new a8b87fac8b2 284: onsuccess: #2223: 1: Success after binutils/gcc: 5 commits new 178fde2cd2c 285: onsuccess: #2224: 1: Success after binutils/gcc: 2 commits new d0e076a36bb 286: onsuccess: #2225: 1: Success after binutils/gcc: 7 commits new 98c87019b25 287: onsuccess: #2226: 1: Success after binutils/gcc: 38 commits new c92ab42db60 288: onsuccess: #2227: 1: Success after binutils/gcc: 16 commits new 320448090ea 289: onsuccess: #2228: 1: Success after binutils/gcc: 11 commits new 4dee8d10d1f 290: onsuccess: #2229: 1: Success after binutils/gcc: 12 commits new 2645722819e 291: onsuccess: #2230: 1: Success after binutils/gcc: 31 commits new 781ff1d8f30 292: onsuccess: #2231: 1: Success after binutils/gcc: 19 commits new 72bb31f186e 293: onsuccess: #2232: 1: Success after binutils/gcc: 5 commits new f669c219e6b 294: onsuccess: #2233: 1: Success after binutils/gcc: 4 commits new 07d9a7c4d70 295: onsuccess: #2234: 1: Success after binutils/gcc: 33 commits new 1dc829b623b 296: onsuccess: #2235: 1: Success after binutils/gcc: 14 commits new e09a75d01b1 297: onsuccess: #2236: 1: Success after binutils/gcc: 9 commits new 8cdc7edfadf 298: onsuccess: #2237: 1: Success after binutils/gcc: 9 commits new 224944b4f82 299: onsuccess: #2238: 1: Success after binutils/gcc: 12 commits new cac35ce4e34 300: onsuccess: #2239: 1: Success after binutils/gcc: 20 commits new 479c02d4192 301: onsuccess: #2240: 1: Success after binutils/gcc: 10 commits new 82527f0cba5 302: onsuccess: #2241: 1: Success after binutils/gcc: 10 commits new 63bf531d225 303: onsuccess: #2242: 1: Success after binutils/gcc: 17 commits new 3a07f0f4322 304: onsuccess: #2243: 1: Success after binutils/gcc: 23 commits new cbd46290134 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits new 622046a3c4b 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint- [...] new 5c50858d84f 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint- [...] new 39fe21e5b4e 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint- [...] new 7e3669cc883 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint- [...] new a9911cd40eb 310: onsuccess: #2259: 1: Success after binutils: 2 commits new 7cc07295e4a 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint- [...] new 660f2da5c29 312: onsuccess: #2265: 1: Success after binutils: 2 commits new 25e3318c6ea 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits new 978d9efad95 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits new d92b0cb974e 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits new 0ab1a65f8d6 316: onsuccess: #2270: 1: Success after gcc: 2 commits new ecd7f63e84e 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits new 4c842e1eba6 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits new 8bed044ab82 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits new 7c30338ccc6 320: onsuccess: #2274: 1: Success after gcc: 5 commits new 3f3c0b54273 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits new 6ef9b58244e 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits new 2c2d959989c 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits new 91faf16f009 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits new 3284ed0b2fc 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits new 8995de3ab2e 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits new 215ecd0cecf 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits new b0b100271ee 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint- [...] new 58f79471b8d 329: onsuccess: #2285: 1: Success after gcc: 8 commits new febdc2c3bd0 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits new be26d1fd2fb 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint- [...] new 8d77e018649 332: onsuccess: #2288: 1: Success after gcc: 2 commits new cc96c3116af 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-4 [...] new 4bee78cf34f 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits new 7e68a7e3302 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits new 41d2a16ee4e 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits new 83b16bfb8c3 337: onsuccess: #2293: 1: Success after gcc: 21 commits new 9651d368f16 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits new 562ac5711b7 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits new 6a5357ecc9c 340: onsuccess: #2296: 1: Success after gcc: 3 commits new 21ff4410726 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits new 9a0d419e6be 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits new a8fd19989b5 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits new 0750c96df9a 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits new fecfb421b83 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits new 069bb5bdc69 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits new 0ecfa6a6deb 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits new 4372cb4179a 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits new 95480962d75 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits new 377aa28892c 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits new de180bf5cfc 351: onsuccess: #2307: 1: Success after binutils: 2 commits new e3270349c67 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits new 68a34f82f8b 353: onsuccess: #2309: 1: Success after gcc: 7 commits new 6bee70f8b0d 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits new c9fdcdc2c64 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits new 0822cd2be95 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits new f4f0bc8dbac 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits new b7b0b5c19d5 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits new 697f28b4c7d 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint- [...] new 41ae02cc048 360: onsuccess: #2317: 1: Success after binutils: 4 commits new bb93aa32588 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits new 79743bb27cb 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits new 79422068b0b 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits new ae9aa00132a 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits new a5301771f5b 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits new abe98ebb4a2 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits new 5b1f194b024 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits new 744564f9494 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits new 7aaa8a79758 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits new a0067c600b8 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits new 1199d306ba9 371: onsuccess: #2333: 1: Success after binutils: 5 commits new a7fdf9658ce 372: onsuccess: #2334: 1: Success after gcc: 5 commits new 392993f881c 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits new 1957c885b33 374: onsuccess: #2336: 1: Success after gcc: 4 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (b19dd8dbb28) \ 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 1720 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2700 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 39288 -> 40016 bytes 04-build_abe-gcc/console.log.xz | Bin 214868 -> 214476 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3824 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2432 -> 2604 bytes 07-check_regression/console.log.xz | Bin 5312 -> 4456 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 84 +- 08-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- sumfiles/g++.log.xz | Bin 3615700 -> 3602504 bytes sumfiles/g++.sum | 118 +- sumfiles/gcc.log.xz | Bin 3147728 -> 3139092 bytes sumfiles/gcc.sum | 4644 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1051508 -> 1048884 bytes sumfiles/gfortran.sum | 96 +- sumfiles/libatomic.log.xz | Bin 2184 -> 2188 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 219028 -> 219212 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 450776 -> 450176 bytes sumfiles/libstdc++.sum | 12 +- 30 files changed, 2506 insertions(+), 2578 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[gcc] branch master updated (76dd48f8956 -> d19aa6af663)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 76dd48f8956 Fix a few incorrect accesses. new d19aa6af663 c++: Set the locus of the function result decl The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/cp/decl.cc | 25 ++++++++++++++++++++-- gcc/cp/method.cc | 2 +- gcc/cp/semantics.cc | 15 ++++++------- gcc/function.cc | 3 ++- gcc/testsuite/g++.dg/diagnostic/return-type-loc1.C | 20 +++++++++++++++++ 5 files changed, 53 insertions(+), 12 deletions(-) create mode 100644 gcc/testsuite/g++.dg/diagnostic/return-type-loc1.C -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (d8e06da0ac7 -> 3ed632bae76)

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 d8e06da0ac7 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 6a6e32e8635 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards bc77f92bb49 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 731f2e8cf22 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards 1cc1cc64982 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards cc22b968e2a 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards a1cd67ebd97 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 1ce5deaee27 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards e9781e8846a 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] discards 60e7c63366c 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] discards 5cde44e88bf 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards fd7a4447ffa 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards d29f747289d 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards e30a8a2d0d5 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 80d3d624336 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 6c4340bd6dc 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 969d92eb3ce 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 7f3904959fa 103: onsuccess: #589: 1: Success after binutils: 3 commits discards fb4c8e26cd6 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 9c6efa4a6c3 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] discards f76672fb573 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] discards 34697d0099b 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] discards fa6b260fcdc 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards 7ed31a3849d 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] discards 3eec881711d 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] discards 9e84ab16b1e 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] discards 7e2581b91f4 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards d2e9cfbb464 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] discards ddd0c38bef0 92: onsuccess: #575: 1: Success after linux: 34 commits discards 3347b5785da 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 9a0adca8a7d 90: onsuccess: #572: 1: Success after binutils: 15 commits discards adca18a829f 89: onsuccess: #570: 1: Success after linux: 11 commits discards e2e4791a3ab 88: onsuccess: #569: 1: Success after glibc: 10 commits discards fa07b5eefeb 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 11c7444207d 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 640cccd8a36 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards fe48b1d0be2 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards b090926bd58 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] discards 459a0c65792 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] discards ad85f005d5d 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 3af66f696e5 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] discards c9ff3b3d4d1 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] discards c6b85cb1549 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] discards ab8edc1e231 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] discards 36c1d4ca818 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] discards 2d050553466 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] discards 1a41a12c743 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] discards 628ac3ff68d 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards ea25c7e9e18 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 14ad3535bf5 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] discards b72496cbce3 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards b5a8e238c47 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] discards c4cec629d04 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] discards 1631b021c3e 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] discards 69794520dbc 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 4f46a69cb6e 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] discards a7e80f71f9f 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 3e14d79f8d8 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards a6c4099264c 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards 64fae7aae07 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 614e56f1a96 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] discards 9162ed79f62 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards ef7d19d6748 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards f12cd0ad84e 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] discards 855b3502015 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards 04e46e59305 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 883a47e2a9f 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] discards d42ee0bf323 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 35da88ce0c1 52: onsuccess: #528: 1: Success after binutils: 8 commits discards b4e40ed0899 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 5d36a788b7a 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] discards ca6ccdfa3f1 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] discards 63fe280cae4 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] discards fc0c464507f 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] discards bf8285f4526 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] discards 2e3252bee16 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] discards d8a8593b8eb 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] discards 9305223a266 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] discards a5d1d0f89b5 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] discards 281a336b4ed 41: onsuccess: #514: 1: Success after linux: 64 commits discards 6f47c459617 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] discards c28275edd27 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 49a12818bd6 38: onsuccess: #508: 1: Success after binutils: 3 commits discards a7ed7ebb988 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] discards c3b3b2b633f 36: onsuccess: #505: 1: Success after glibc: 3 commits discards a156927e9ce 35: onsuccess: #503: 1: Success after binutils: 11 commits discards dcf00e71f92 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards ec7a3e21a2b 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gd [...] discards d0727c23f47 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] discards 4a89e4b522d 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] discards aae26873d44 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards 81525d6c6f8 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards 966fe82dd0e 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gd [...] discards a5e610842d9 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] discards f1a246b2e2a 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gl [...] discards 3d45c83153f 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] discards 4f0e5e3c9de 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards 6afe49af6ed 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards ce8943468eb 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 17d1ff2e52d 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards cf14c162743 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new e1719779d69 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new ad573a86c97 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 3dd53e81bde 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new d3dbdf7fd00 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 8f46a2c789d 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 1432182e357 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] new bfde8daa300 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gl [...] new 40fd8d18c6d 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] new de9ed32d184 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gd [...] new c53568fab64 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new dac3f3c4556 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new c28a3573b50 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] new c6410390c25 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] new c2e77101c75 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gd [...] new 7e8494cafcf 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new 4e2174c5abe 35: onsuccess: #503: 1: Success after binutils: 11 commits new 25ef3f7b488 36: onsuccess: #505: 1: Success after glibc: 3 commits new 597dd9d0115 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] new 248cba77148 38: onsuccess: #508: 1: Success after binutils: 3 commits new 11a89a55d1d 39: onsuccess: #511: 1: Success after binutils: 8 commits new 8643eeb5a40 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] new 7f7581495ba 41: onsuccess: #514: 1: Success after linux: 64 commits new f94233b5afa 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] new 32c3406e43b 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] new 640c1d32935 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] new f3122399d66 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] new be991b7475b 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] new 28db7282d0f 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] new 51dbf5c3a0b 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] new 157ad65a4a7 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] new 2f289ed4a71 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] new a6d3c289d9f 51: onsuccess: #525: 1: Success after binutils: 8 commits new c8b13e320e6 52: onsuccess: #528: 1: Success after binutils: 8 commits new 96b6dc26030 53: onsuccess: #531: 1: Success after binutils: 12 commits new 7006f9e889e 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] new a8170f4bebe 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new 5e84ec83185 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new 5df29e5af59 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] new 6b487be0af3 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new 3208658a21e 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new 5ff0b1d028f 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] new 6f90e77e6e3 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new b6f7854e6d2 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new 5f1dea21984 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 8806d069cac 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new deed754e87c 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] new 2b18e6ea468 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new 64ef2076678 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] new 8c21f1733db 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] new f7b5d6bdf8c 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] new d4bdb73f412 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new a1448df8122 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] new 843e08d6335 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new ff7c7650418 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 62e7c83ed47 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] new 25e3852dc62 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] new 5bb7ef3e388 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] new 79035441b72 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] new e9787b91d8c 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] new dd89d44836a 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] new 3c6cc9bd8fa 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] new 6182c064e0c 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 856800cd7f0 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] new 2d967c89e30 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] new 3f5c9f61723 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 7dcd0fecb91 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new aed2b07212d 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new b660cbdadb7 87: onsuccess: #567: 1: Success after binutils: 8 commits new 307aad4be1a 88: onsuccess: #569: 1: Success after glibc: 10 commits new 971e89d33c1 89: onsuccess: #570: 1: Success after linux: 11 commits new 6d7380231f4 90: onsuccess: #572: 1: Success after binutils: 15 commits new 0135baf38c5 91: onsuccess: #574: 1: Success after glibc: 3 commits new 4a8ea8d5b11 92: onsuccess: #575: 1: Success after linux: 34 commits new 836d8b75d70 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] new 903f39cdbc1 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new 7eb4902c4fe 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] new 3c086d1f001 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] new 47daeafeea1 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] new 8bea0b7bdfb 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new c2a4f087a43 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] new 78ee75f7a20 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] new 9ed539d33ef 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] new 94a18eb4ad9 102: onsuccess: #586: 1: Success after binutils: 5 commits new 3940c47dd0a 103: onsuccess: #589: 1: Success after binutils: 3 commits new 9511e77d0a2 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new f44e34635cf 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 8995cf3f62d 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 1d0ebf620e9 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 1f9abe783d0 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new bb7ecff74d7 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 80dd64f415e 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new bd04c4d6f48 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new 215c3a5d815 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new f909ae522d2 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 26863f28792 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 67a20d21ac5 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 803df02227a 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 8fc9b663026 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new f0ba207f11c 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 49dbf33d658 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 3ffde4ee914 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 3ed632bae76 121: onsuccess: #608: 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 (d8e06da0ac7) \ 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 1700 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 53700 -> 52008 bytes 04-build_abe-gcc/console.log.xz | Bin 235064 -> 237172 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8644 -> 8780 bytes 07-build_abe-glibc/console.log.xz | Bin 238336 -> 236752 bytes 08-build_abe-gdb/console.log.xz | Bin 51896 -> 51708 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3816 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2464 -> 2044 bytes 11-check_regression/console.log.xz | Bin 10236 -> 20544 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 41 +- 11-check_regression/mail-body.txt | 201 +- 11-check_regression/results.compare | 102 +- 11-check_regression/results.compare2 | 6518 +++++++++++++++-- 11-check_regression/results.regressions | 100 +- 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 | 203 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 100 +- sumfiles/gdb.log.xz | Bin 1690736 -> 1761932 bytes sumfiles/gdb.sum | 11332 +++++++++++++++++++++++------- 31 files changed, 15246 insertions(+), 3451 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (bf821814c1e -> b63a3b3360e)

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 bf821814c1e 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 99b53d913f1 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 85495f19447 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 7727024eefd 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 012ec58fd15 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 6e53e0eb9c0 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 9b41b2fc0ee 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 45f3172cc98 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 7a35473ee68 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards efc0f8c87a1 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards e6b57419b5b 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards 04d3172313c 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards 4e1a3f8b8f4 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards a1e8ebdc7a4 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards 673fb598222 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards ad7a31bb3ed 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 77854e6853a 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards cc386ea880e 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards 058e05cdc95 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 06b13d68289 94: onsuccess: #832: 1: Success after binutils: 5 commits discards a21fd4371e0 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 6c1733e319c 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards ab3a4ae433b 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards ae3a52c56f1 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 9b1434a4670 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards bd446d3b576 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards 8a2fe9ae128 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards a6cf2e8aa4f 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards e19c0fb45df 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards a7e64d8646d 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards a0855d1da59 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards f8d2aff0c9f 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards 506dac2fd90 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards 8e7a119a077 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards a69f9086003 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards 2dbe31d59dc 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards a7cbb745dec 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards 05623ff9f97 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 7b0fb269f28 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards 54692b276c1 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 2700dc4e63a 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards 84e7852e2bc 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards 05accb5ee09 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards 51d80fce8ef 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards a93adb8dc14 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards 8649f800044 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards ca5cab9ed3e 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards c852cb8ac79 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 8540e3b620c 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards 2b0e6f42306 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 5dbb18dcdd0 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 7ee009bb2a8 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards b3478d9bddc 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards f7331f59c4b 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards 630f33c5b98 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards b8f5a7509ea 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards 22a3aa0d2b0 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards bc6a333fc07 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards c3d890b9bde 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 0a17d01fd5d 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards 843376e126f 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards 40149b5a9ad 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards 00c9e3d5c1b 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards 8bac9b076fb 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards 9591b435fad 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 52809ab3596 48: onsuccess: #782: 1: Success after binutils: 8 commits discards bdabebc7eda 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards de4da114b44 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards 94fc7633003 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards 408fe86ea2c 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards d0d57b3b87a 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards f220b01bee3 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards fbe076f66da 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards 150bb87e51d 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards dc9b82d2e99 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards a7c05f4cabf 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards eef7dfff45e 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards e777fca9230 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards a62c633942b 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards dc4d724f3f6 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards 8d1dea8b1b1 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards 66fc3e40740 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards bc44c70ba6f 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards a79242072a3 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards 1f7d7c191b9 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards 9cc317864a4 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards 16ce15476de 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] discards bf43249444a 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] discards 2dfc72e8658 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] discards a271892f75f 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards e3409d61b03 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 4e933ebd5f1 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 57f4505a14c 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 02a311b77b0 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards d6a2ac76e6f 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards d17854b80fd 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 9a00729e868 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards bdd84efc398 16: onsuccess: 1: Successful build after binutils: 4 commits discards 25c272d2e45 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 14b86d7e08c 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 128a279faf9 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] new d2c5f7d8ab0 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 64f8e7b4147 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new d62144261d4 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 91a484dee8e 16: onsuccess: 1: Successful build after binutils: 4 commits new f44f19d094d 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] new ed7262575c6 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 8aad06f750d 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 0a5996f9f18 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 626a0fec65a 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new cbc8dadb101 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 67508e1f2c1 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new c4e8d0ca025 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 2b8d4deffcd 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] new 17aaa4f16f1 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new 1345927d62e 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new 53ba6ab2d1c 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new c15deca5b6e 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new c02cb654980 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new e8746e57edc 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new 7c127f1cc5b 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new ae037d49a03 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new a748113b361 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new 0c091c80c0a 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new 1d094f8b2af 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new d66e58d030d 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new 86192a74d11 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new bb4f8653718 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new bbf61966ad2 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new 6b9311f974e 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new a11e5f0f836 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 41b870f7f40 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new 210627e9a24 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new 05bb1e94c42 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new f8c3b814a05 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new 774b7e23dc8 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new 2d3340dd2be 48: onsuccess: #782: 1: Success after binutils: 8 commits new a82a59f8062 49: onsuccess: #785: 1: Success after binutils: 12 commits new 0c7c072d40e 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new 6d9685e3065 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new 0bbc244e290 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new d9f6215df13 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new 699357f77e7 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new 51ffe1af45b 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new d292a1ca4ca 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new b72e8e455e2 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new 4d10d3d1b1b 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new 2e7fda5e00b 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new ebb0f78c985 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new c6f12f6db2b 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 7d99b927e73 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 940eb0216cf 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 4cb24f460c9 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 41705b0a9fd 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 5bb925b9c3c 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 00e49b69ef8 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new 7f13056d8e9 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new f7a8a05e17a 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new eaf9845afa6 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 8ee72e80c5e 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new 67f4713483e 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new 2f0a3b84860 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new 31074a04498 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 537d76c01a8 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new 1f5fa162150 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new dcc6657bc17 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new d688db2bdbd 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new 486f93017ad 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new b9c0196b6e1 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new 0ac6b561627 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new 00a5fd8fbde 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new 296791af455 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 7505a55e63f 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new aba16e62cef 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 28b3434932b 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new 672cfd0a830 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 061a02eb474 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new 9b3f71de24b 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 8ff6de6b88b 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 65c150ee69c 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new d60db611484 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 92bb328b4c5 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new f3fa1b38c05 94: onsuccess: #832: 1: Success after binutils: 5 commits new db36c72cff4 95: onsuccess: #835: 1: Success after binutils: 3 commits new d027896f2f1 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 4dc1621e2c9 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new 20cd329f146 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 2f96a9a03c3 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new 91567e7972e 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new a26899f7d6e 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new c6798c2192e 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 2b3a48b5098 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new 2a7c1245ff8 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new 8f06d55a9d6 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new cbacae92809 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 7b054ea04c8 107: onsuccess: #849: 1: Success after binutils: 5 commits new 2ea43c1d010 108: onsuccess: #850: 1: Success after gcc: 2 commits new 7572a51d1d0 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 71a87bc82b1 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new a0af8d81a1b 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new 36ca3dfbe3d 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 98cc57cd9c0 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new b63a3b3360e 114: onsuccess: #857: 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 (bf821814c1e) \ 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 1688 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 39820 -> 39084 bytes 04-build_abe-gcc/console.log.xz | Bin 213872 -> 214544 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8536 -> 8684 bytes 07-build_abe-glibc/console.log.xz | Bin 244332 -> 243288 bytes 08-build_abe-gdb/console.log.xz | Bin 39160 -> 38824 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3832 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2920 -> 2596 bytes 11-check_regression/console.log.xz | Bin 8732 -> 7792 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 8 +- 11-check_regression/mail-body.txt | 59 +- 11-check_regression/results.compare | 31 +- 11-check_regression/results.compare2 | 573 +--- 11-check_regression/results.regressions | 31 +- 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 | 61 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 31 +- sumfiles/g++.log.xz | Bin 3756372 -> 3748248 bytes sumfiles/g++.sum | 177 +- sumfiles/gcc.log.xz | Bin 3285492 -> 3297028 bytes sumfiles/gcc.sum | 4675 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1085980 -> 1084188 bytes sumfiles/gfortran.sum | 96 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 230816 -> 231112 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 451508 -> 453260 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 2865 insertions(+), 3025 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022