Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-stable-allmodconfig updated (acecaa381 -> 60bb428a1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-stable-allmodconfig in repository toolchain/ci/base-artifacts. from acecaa381 13: onsuccess: #388: boot: Success after qemu: 118 commits new 60bb428a1 14: onsuccess: #389: boot: 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 1640 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 30300 -> 30080 bytes 04-build_abe-stage1/console.log.xz | Bin 68424 -> 68992 bytes 05-build_abe-qemu/console.log.xz | Bin 31464 -> 32172 bytes 06-build_linux/console.log.xz | Bin 3264 -> 3296 bytes 07-boot_linux/console.log.xz | Bin 508 -> 508 bytes 08-check_regression/console.log.xz | Bin 2932 -> 4208 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 | 31 +++++++++++++++++-------------- 18 files changed, 29 insertions(+), 26 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (b74d39392 -> 448523c6b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards b74d39392 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/gl [...] discards 82895fac5 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 commits discards 27ef7952c 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 87011e139 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/gd [...] discards ab5e303ca 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/gd [...] discards 124d728b8 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 4c297dba4 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/gd [...] discards 5b721136b 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards a239c2a75 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 242c1b21a 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 612c7de96 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-20 [...] discards 14ebd4dea 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/gl [...] discards b93cfc7a2 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 commits discards e493704e4 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/gd [...] discards d6dd8a4f1 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/gd [...] discards e5ad7a917 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/gd [...] discards 740364c92 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 commits discards 0ce2d2272 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards e59420cfe 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/gl [...] discards b98141647 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/gd [...] discards a51a71179 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 6650631b8 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards c38fc7a11 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/gl [...] discards 38ab38b6a 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/gd [...] discards c1d671b4d 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 4b9c64e43 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/gl [...] discards a05ba5fea 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards be6d05cc2 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards bae3f1ce4 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 commits discards ebd3206a5 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 commits discards 79b683ff6 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/gd [...] discards 395690f20 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 9260f645f 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-283 [...] discards 01d34e72d 128: onsuccess: #1723: 1: Success after linux: 12 commits discards c79e2cf4b 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 84b082ba0 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 451bba2ee 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 53ad23e56 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 2059f1cea 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/gd [...] discards 011079a9b 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/gl [...] discards 0c715d9d9 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/gl [...] discards 60f94800d 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/gd [...] discards aaa719dbc 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/gd [...] discards c1588f9fe 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 44aed818e 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...] discards 4687c5e83 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] discards a523e7c38 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits discards 7409c6387 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] discards 9046782d5 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] discards 4a99a5b9f 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] discards 53f68b475 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] discards c043aaf87 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 23fb3f119 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards c318e95af 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 61b51e626 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] discards 987407ff2 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] discards e0316cbff 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] discards 776f90f8e 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards fd37af66b 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards 99b7f4773 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards b7f6298f4 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 33d6e9da2 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards 7f4e24d03 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards eae63ebe7 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards 437fbd4bd 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 3f9a9c82d 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards c06cf3f0f 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards 09d171965 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards 30a364596 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 66585fda8 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards 89b28dc0b 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 1b84f1b6d 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards d8a7d91e8 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 781775bb0 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards d00ca8749 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 020510213 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards d2d3b61c3 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards f7f3babd3 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards e13b0bc9d 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 3f3bd064a 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 3d3243099 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards e7946da9e 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards af4d0eb2b 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards cac6a60ae 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards d9a118a6d 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 93e80a4ab 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards ab25b8b20 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 808ac298b 74: onsuccess: 1: Successful build after linux: 44 commits discards 89cdf6873 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards e0a932e7f 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1214b9d36 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards 3ca985185 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards 87e8698cb 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 303f7166a 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d0a797552 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 42d5634fe 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 6afa6e50c 65: onsuccess: 1: Successful build after gcc: 4 commits discards 31e00f93a 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 11272b5b9 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b8e2af196 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards e0eca1309 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 80c7ae608 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new a57a3312f 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new 020b1609d 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7309b681a 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 0aa8496de 65: onsuccess: 1: Successful build after gcc: 4 commits new 3ee619260 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 3932d7964 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d843aeda5 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 07720536b 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new 025c06a9b 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new ca130957d 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new bdf0798d6 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c71f78692 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 5f9d22e3e 74: onsuccess: 1: Successful build after linux: 44 commits new 7667a238f 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a5baac5fb 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new 5926ea552 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f7ece26da 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new a0e9b4c0a 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new a25f985d2 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new 9321d8493 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 0ee0d7292 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new ae00fa420 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new f6792a08a 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 4d60bc3f9 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 4ea909002 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 86cbd6a9a 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new e1eef48c9 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 336401f9a 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 72551749f 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 992ce7e3e 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new fe60781a4 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new 562c5b8fc 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 87761395f 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new 173090420 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new c2562eddf 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new b3ae8a9b2 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new df6a0a652 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new 48b3d93ff 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new 8e3f8f8ac 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new ab2ad20e7 101: onsuccess: #1693: 1: Success after glibc: 14 commits new bc99d97d1 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new c02670224 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new 031e6eb0c 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 51b172553 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] new 91381dadb 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] new c9e8c38af 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] new 9f2b051e3 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 6041ae469 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 1f3d43f67 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 0fbd499e3 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] new 372da95bc 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] new d2f351270 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] new d07bf19e3 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] new 6fb1ac766 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits new 13a95c827 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] new 9b9d032c4 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...] new 91c0e514c 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 2d454f75c 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/gd [...] new bdf41074d 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/gd [...] new c195caf4f 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/gl [...] new 7212fed5a 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/gl [...] new 65925a19e 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/gd [...] new de1749134 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 1c69d0d51 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 60bb9db1f 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new bdfce0e94 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 60b2c2afc 128: onsuccess: #1723: 1: Success after linux: 12 commits new d36f149b2 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-283 [...] new 2fcdfe63f 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new bcbac98e9 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/gd [...] new c48e2bf52 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 commits new 4fabfd359 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 commits new c2dd1cff4 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 810206989 135: onsuccess: #1733: 1: Success after binutils: 5 commits new f686d503b 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/gl [...] new 3d847f5e4 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 4e9200cf7 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/gd [...] new 8f68d325b 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/gl [...] new cc3dc1ef7 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new b4507beb6 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 13a94d557 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/gd [...] new a2ebcec63 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/gl [...] new f1995ad5d 144: onsuccess: #1743: 1: Success after glibc: 2 commits new a892add55 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 commits new fa0253125 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/gd [...] new 858c0fd28 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/gd [...] new f1bb16938 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/gd [...] new dd9b57b70 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 commits new d9d5dc595 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/gl [...] new b36030f1c 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-20 [...] new 7890eac7a 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 9dead4f25 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 6fc190c61 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new d46784894 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/gd [...] new e7535d5f6 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 992dca57e 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/gd [...] new 02f6d1a1d 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/gd [...] new 4d7b8ccbe 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new 1ed832791 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 commits new d0240683a 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/gl [...] new 448523c6b 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/gl [...] 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 (b74d39392) \ 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 1732 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30700 -> 30104 bytes 04-build_abe-stage1/console.log.xz | Bin 91184 -> 90592 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9188 -> 9956 bytes 07-build_abe-glibc/console.log.xz | Bin 235876 -> 234052 bytes 08-build_abe-stage2/console.log.xz | Bin 225680 -> 223476 bytes 09-build_abe-gdb/console.log.xz | Bin 37648 -> 37136 bytes 10-build_abe-qemu/console.log.xz | Bin 31604 -> 31632 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2704 -> 2420 bytes 13-check_regression/console.log.xz | Bin 8316 -> 6876 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 26 +- 13-check_regression/results.compare2 | 275 +--- 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 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 46 +- sumfiles/g++.log.xz | Bin 2652712 -> 2669836 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 2228744 -> 2193148 bytes sumfiles/gcc.sum | 2572 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 886832 -> 880740 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201464 -> 201484 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 424796 -> 428120 bytes sumfiles/libstdc++.sum | 16 +- 42 files changed, 1477 insertions(+), 1786 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_O1 updated (2d2b906e4 -> 3572b7b8e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_O1 in repository toolchain/ci/base-artifacts. from 2d2b906e4 53: onsuccess: #445: 2: Success after binutils/gcc: 28 commits new 3572b7b8e 54: onsuccess: #446: 2: Success after binutils/gcc: 40 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1680 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2712 -> 2716 bytes 04-build_abe-binutils/console.log.xz | Bin 38072 -> 37968 bytes 05-build_abe-bootstrap_O1/console.log.xz | Bin 271488 -> 271964 bytes 06-check_regression/console.log.xz | Bin 3152 -> 3164 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 12 files changed, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/release-aarch64 updated (db6062da9 -> 1bd39f2c6)

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_build/release-aarch64 in repository toolchain/ci/base-artifacts. from db6062da9 21: onsuccess: #130: 6: Success after binutils/gcc/linux/glib [...] new 1bd39f2c6 22: onsuccess: #131: 6: Success after binutils/gcc/glibc/gdb: [...] 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 1676 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 38516 -> 37988 bytes 05-build_abe-gcc/console.log.xz | Bin 209432 -> 207452 bytes 06-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 07-build_abe-linux/console.log.xz | Bin 8692 -> 8596 bytes 08-build_abe-glibc/console.log.xz | Bin 239676 -> 241456 bytes 09-build_abe-gdb/console.log.xz | Bin 37116 -> 37124 bytes 10-check_regression/console.log.xz | Bin 4300 -> 3808 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++++++++++----------------- 18 files changed, 25 insertions(+), 25 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (eaa613e11 -> 80d6046d0)

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 eaa613e11 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/gl [...] discards 2c87bf209 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 commits discards b094197cb 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits discards d680a2a54 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/gd [...] discards 6c61262fe 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/gd [...] discards 9dafe95e5 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 commits discards 02f4d5a1e 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/gd [...] discards 0209d3130 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards 59d4314b6 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards 9c74c8b93 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards 66a65819f 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/gl [...] discards 78ae16032 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/gl [...] discards 43a641d53 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 commits discards 88a1f5e1d 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/gd [...] discards 4d946869d 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/gd [...] discards cb3a73c9e 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/gd [...] discards e16dbb77d 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 commits discards ae60a5dbf 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 48d2fce68 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/gd [...] discards bf80c2279 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/gl [...] discards b3670b426 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 commits discards de9363999 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards c2f7c2d93 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/gl [...] discards 3babc960c 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/gd [...] discards e5d4a7d75 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards 0892eb4e5 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/gl [...] discards 4ce438e5c 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards 96f8c6609 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g1 [...] discards 90b8f2555 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g3 [...] discards 47df8c47e 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 9e4e10670 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 commits discards 5f8c37d4a 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 commits discards 2a41f9ba4 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/gd [...] discards fba03b8a5 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 00b976a4a 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards bff143764 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/gd [...] discards a847f9be7 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 77eda3d4a 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards 823ac393e 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 549691787 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/gd [...] discards f75e04d0f 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/gl [...] discards a75ef88e0 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/gl [...] discards 82cce1be1 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/gd [...] discards 5e17118c7 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/gd [...] discards 3145021e6 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 commits discards b55231639 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qemu [...] discards d41b5c7e0 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/gl [...] discards 28e3fdd0a 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 commits discards 15e8815cb 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: 1 [...] discards 808917b76 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/gd [...] discards 321953258 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/gl [...] discards 9f3ed885f 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/gd [...] discards 3838e1fff 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 17c1f9eef 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards fc4532b2b 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 248e871f1 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/gd [...] discards fb756e9af 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/gd [...] discards 1e3ee8f48 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] discards 2712ec309 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 0064f2098 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 5d3990d46 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] discards 5f219a9ce 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 50bfbd9a7 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] discards 496f24035 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] discards 03a400697 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards e4993b81b 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] discards cbe5173a4 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] discards 40456e72a 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 3d84596a8 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] discards 413f2b16d 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] discards 8d4695f04 95: onsuccess: #1529: 7: Success after baseline build: no new [...] discards fc122521a 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 12f90bdaf 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] discards f4ea703ae 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 96fbcd355 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards cf3028695 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 87f632c7c 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 804e637cc 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards f252ed8dc 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 97ae763ba 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 97717582b 85: onsuccess: 7: Success after gcc: 9 commits discards ff8657383 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 2a4ce68c4 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 428c764f9 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 4e79d9fa5 81: onsuccess: 7: Successful build after gcc: 2 commits discards c8fd90538 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards e0392c673 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 3521e1f8e 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 104e47e56 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards 03310f86e 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 5770405e3 75: onsuccess: 7: Successful build after linux: 44 commits discards 764740845 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards ab8033b42 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards eb5b97797 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards dc873df4d 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards c31cc43e5 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards a147de692 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 9366784c6 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards a1cc6c593 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 1589bf8c0 66: onsuccess: 7: Successful build after gcc: 3 commits discards 2cd032db1 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 18ab79eac 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 4e13e7ecd 66: onsuccess: 7: Successful build after gcc: 3 commits new 3455ec65c 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 36bf1b50f 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new a1f6dff55 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 41c0d7fae 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new bedb75b35 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new 8b6d1df9a 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 0cbafc0d7 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 006d9e713 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 886765de8 75: onsuccess: 7: Successful build after linux: 44 commits new 59ef84028 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new bdff6ce8a 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new 07fc5a532 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 02cb95b24 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 988eb5c4d 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new d9b31cbb0 81: onsuccess: 7: Successful build after gcc: 2 commits new 81c13e701 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 6b94a167d 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new b1603da1f 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new e740b624c 85: onsuccess: 7: Success after gcc: 9 commits new 50f8f8d22 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new e560058e7 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 000602ee4 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 1d9eca3bc 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 7fa8efbfe 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 997bb2127 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 156f803ae 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new b0a880c3c 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] new 300888307 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new c173017c3 95: onsuccess: #1529: 7: Success after baseline build: no new [...] new c410f800e 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] new 0dfeb2f51 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] new ba6f70046 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 4ca9103e2 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] new 2968f8b01 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] new f009cfbef 101: onsuccess: #1609: 7: Success after binutils: 78 commits new e22e5a79f 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] new 5ede47bc0 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] new 8373f7e83 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new a3cbc5edd 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] new 1025dff0b 106: onsuccess: #1617: 7: Success after gcc: 2 commits new c58f02e34 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 9157ab2e2 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] new f549b6895 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/gd [...] new 05709c4fe 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/gd [...] new db118a2ff 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 674d8b2fb 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 30c892b5a 113: onsuccess: #1624: 7: Success after gcc: 6 commits new bbb54436a 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/gd [...] new c04a263b9 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/gl [...] new 678755082 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/gd [...] new 64893528b 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: 1 [...] new 0bdede291 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 commits new 44d3733e2 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/gl [...] new eb4166b94 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qemu [...] new 5db80cea0 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 commits new 2946d2c25 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/gd [...] new b83e8910f 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/gd [...] new e8f9c05c6 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/gl [...] new 3e42be556 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/gl [...] new b0399192b 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/gd [...] new 145850c9d 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 66f130e53 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 534a9d352 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new e971c1928 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/gd [...] new 908ab4369 131: onsuccess: #1644: 7: Success after gcc: 10 commits new e1cc346b3 132: onsuccess: #1645: 7: Success after linux: 23 commits new 63c80b52b 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/gd [...] new 0e919beae 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 commits new 19a73c596 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 commits new 198f78b8e 136: onsuccess: #1650: 7: Success after binutils: 2 commits new ccb6699de 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g3 [...] new 7f6e2228d 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g1 [...] new a3c003169 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 4c2165421 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/gl [...] new a2463c912 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 03a3ec9a6 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/gd [...] new e446233b4 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/gl [...] new 41688fcd9 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new 0593f096f 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 commits new bfc39760e 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/gl [...] new 99f5eced4 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/gd [...] new 121c08251 148: onsuccess: #1663: 7: Success after glibc: 2 commits new 591868557 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 commits new 87cbde506 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/gd [...] new 103a75089 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/gd [...] new e501a04c1 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/gd [...] new f0dc79d4b 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 commits new ca0fefb94 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/gl [...] new 82c2a4503 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/gl [...] new 4c7f272bb 156: onsuccess: #1671: 7: Success after gcc: 3 commits new 4527e6bcf 157: onsuccess: #1672: 7: Success after gcc: 2 commits new 6bd2afb93 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new 63a8135e4 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/gd [...] new 149024f5e 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 commits new 8cb58b6c8 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/gd [...] new 7d94a0b8c 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/gd [...] new 1e6b0afeb 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits new fd9269e5b 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 commits new a0f4053b0 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/gl [...] new 80d6046d0 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/gl [...] 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 (eaa613e11) \ 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 1644 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 30788 -> 29976 bytes 05-build_abe-stage1/console.log.xz | Bin 90988 -> 90644 bytes 07-build_abe-linux/console.log.xz | Bin 9200 -> 9968 bytes 08-build_abe-glibc/console.log.xz | Bin 234144 -> 234064 bytes 09-build_abe-stage2/console.log.xz | Bin 223148 -> 223492 bytes 10-build_abe-gdb/console.log.xz | Bin 37488 -> 37196 bytes 11-build_abe-qemu/console.log.xz | Bin 32084 -> 31412 bytes 12-check_regression/console.log.xz | Bin 4300 -> 4824 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 46 ++++++++++++------------- 22 files changed, 65 insertions(+), 65 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (4fffcad657 -> 33cffa94b0)

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 4fffcad657 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/g [...] discards d21bd055c4 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 12 [...] discards 66796777c6 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 commits discards 5b6afa6f16 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/g [...] discards b0ed5b8496 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 5ef9c4b8b9 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards e2b60591a0 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] discards 94b5c0b78c 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards 3c99186719 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards adf26d7988 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] discards 51d870bca1 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards 674af21de5 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] discards 205686bab1 152: force: #1605: 7: Success after gcc: 9 commits discards 5769380519 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] discards be5aaf2de6 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] discards ebd99a485f 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards da63e939c6 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards f7a381880b 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards 5e658a3eb6 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards 37ec97d78e 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards 805878d09f 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 8d58c07bbf 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards 2f7b60d555 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards be4c2a6a7f 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 61a83cdf39 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards b32cdf8e5c 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards 5089020a9c 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards eac34904e4 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 3055557ec2 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards 390387e37c 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards fca983625f 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 31b6b9d995 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards 61eae1c7d5 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards 325b190bc9 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 612d7d3bfa 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 2d54435956 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards c7c9bef081 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 4a8346acfc 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 11d755de71 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 8c4039f375 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 1fdfab9c38 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 2ba414104e 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards 8c66213457 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 6e65f648a3 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards c7c0742121 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards a814657800 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards aba4be4fbd 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards 473d56b433 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 078ed70766 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 59de2e0cb5 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards 063b1f691e 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards c0002d7283 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards e322ae6c43 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards e4aec34f4f 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards c9ce91bd5a 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 5643404ba3 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards b0c909499a 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards b49dd085a4 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 8171433b9e 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards b26e398e08 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards dfc5f7afad 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards 2139db62bf 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 7039673970 102: force: #1551: 1: Failure after gcc: 306 commits discards 71a6d8939a 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 85a49e1960 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards f995d8e1b0 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards a3f080407c 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards d260e40f31 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 6725c406ca 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 5c3c7a0300 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards d29505355c 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 0dd82a31f0 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards ee7598c743 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 73d0f5aa71 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards a1515d6104 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards c895e01c3b 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards ece3278243 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 6eaad4e348 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards d0a6585bc6 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 156c5ec30e 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 1ae9e82a2b 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 5252f08cb4 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 379123e9bf 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards a66089cf2d 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d8c6d583a6 80: onsuccess: 7: Successful build after linux: 44 commits discards e476cf6332 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 39d061939a 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards 5f992c0e94 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c759254891 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards de2fd0373a 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards ce65c4c564 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 9748b0dd7a 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 33d966df8e 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d7cb23b9d5 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards e9767fc9ef 70: onsuccess: 7: Successful build after gcc: 4 commits discards 908ac4b7a3 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9587891556 68: onsuccess: 7: Successful build after linux: 6 commits discards 8aeec58ac6 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards 78335b6136 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards eb2fb1867d 65: onsuccess: 7: Successful build after binutils: 3 commits discards f2f3dea39e 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 1766decc08 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 2769a39d72 65: onsuccess: 7: Successful build after binutils: 3 commits new 98315c9a54 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 65d80e3654 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new faf774f522 68: onsuccess: 7: Successful build after linux: 6 commits new d45e712d3e 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2afe415bdc 70: onsuccess: 7: Successful build after gcc: 4 commits new 99e6ccfd38 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 69723ccc98 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 79107decea 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 117654ca00 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 0f82ac439c 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new ccb348acf7 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 47b631ccac 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 3ff1a09468 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new b9da41cc4b 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 82c159bbde 80: onsuccess: 7: Successful build after linux: 44 commits new 6f5e14f8ca 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new fe10938afa 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 1a462c4980 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b77a25a868 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 9f897395d3 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 537a732f08 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 4ab5bfe052 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new d57ae83927 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 24968535ba 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 964e84415e 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new dd57ede531 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new e68b7a9a19 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 2ee7eed984 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new d3328deb0c 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new b29b3f1b17 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 9a330d01e5 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 2f9eda5515 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new f77773861a 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new dce9e79507 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 9ed26c3336 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new b2938208a6 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 1adbc817cd 102: force: #1551: 1: Failure after gcc: 306 commits new 4c8e26ccf0 103: onsuccess: #1552: 1: Success after gcc: 5 commits new f07ecbba1d 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 17aca11468 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 24454ede1f 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new c1effc49ca 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new 31c0d11268 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new dbe51110c4 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 5355675d05 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 19851752c1 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new 47536be9cc 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 1a18e3544a 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new 34171a3120 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 816e7b7398 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 8535bcaeef 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 2cf394cb98 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new d393bade7e 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new 68184b9208 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new 4c334e04c1 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 39e94009b9 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 30c00420d0 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 2f3a092f84 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new aed98b94ac 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 608a4b2f3f 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new c7fa8da426 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 24d2509721 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new 15d2e3c945 128: onsuccess: #1579: 7: Success after linux: 12 commits new 5e9993bc2d 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new 58bdf8df42 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new b3c89b7590 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new c1a4598842 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new f0ef023150 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new 033025eb87 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new f8e26a7588 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new e4f3b6f5be 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new 643d272959 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 7e89d63a5f 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new 216b242f77 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 5cd80d0e60 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new b0b7341038 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new 0372e3af9c 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new 57bdc4170d 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new 07f83eb4e0 144: onsuccess: #1595: 7: Success after glibc: 2 commits new 54a7844a07 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new d67abe3e84 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new fe22340790 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new 14a5b8dfd4 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new a1a62b7d46 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new 4f94263d02 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] new a89e0beced 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] new 0a22d8916d 152: force: #1605: 7: Success after gcc: 9 commits new 8ff12322fd 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] new 6c0531bfe9 154: onsuccess: #1607: 1: Success after gcc: 2 commits new fe09f64a6b 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] new 1b015d12bb 156: onsuccess: #1609: 7: Success after gcc: 2 commits new 24b3b15b35 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new d759b0ef8f 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] new 13434f044c 159: onsuccess: #1612: 7: Success after gcc: 4 commits new 8e533d5c5e 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 9ca00b21c4 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/g [...] new 9884b7637b 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 commits new aafcfa0124 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 12 [...] new 97a8324369 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/g [...] new 33cffa94b0 165: onsuccess: #1618: 7: 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 (4fffcad657) \ 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 1700 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 31012 -> 30276 bytes 05-build_abe-stage1/console.log.xz | Bin 72680 -> 72312 bytes 07-build_abe-linux/console.log.xz | Bin 9188 -> 9916 bytes 08-build_abe-glibc/console.log.xz | Bin 239652 -> 239856 bytes 09-build_abe-stage2/console.log.xz | Bin 203244 -> 202952 bytes 10-build_abe-gdb/console.log.xz | Bin 37864 -> 37464 bytes 11-build_abe-qemu/console.log.xz | Bin 32172 -> 31892 bytes 12-check_regression/console.log.xz | Bin 4708 -> 4908 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 46 ++++++++++++------------ 22 files changed, 66 insertions(+), 66 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (69fd6dcc32c -> 70e3f71a279)

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 69fd6dcc32c Daily bump. new 70e3f71a279 diagnostics: Add test for fixed _Pragma location issue [PR91669] 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/c-c++-common/pr91669.c | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 gcc/testsuite/c-c++-common/pr91669.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (840efa550a -> 690d864a10)

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 840efa550a 159: onsuccess: #2094: 1: Success after binutils/gcc: 23 commits discards 8eb7067d20 158: onsuccess: #2093: 1: Success after binutils/gcc: 9 commits discards 0d13a666ae 157: onsuccess: #2092: 1: Success after binutils/gcc: 3 commits discards afd08df5c4 156: onsuccess: #2091: 1: Success after binutils/gcc: 2 commits discards 3344eee2fe 155: onsuccess: #2090: 1: Success after binutils/gcc: 22 commits discards 50bfa3acac 154: onsuccess: #2089: 1: Success after gcc: 4 commits discards 064861687f 153: onsuccess: #2088: 1: Success after basepoints/gcc-13-30 [...] discards 5526f6a46f 152: onsuccess: #2087: 1: Success after gdb-12-branchpoint-2 [...] discards 5ad1302ad1 151: onsuccess: #2086: 1: Success after gcc: 2 commits discards 5be82b867d 150: onsuccess: #2085: 1: Success after gcc: 2 commits discards e54bc19cd0 149: onsuccess: #2084: 1: Success after gcc: 16 commits discards 35c2748874 148: onsuccess: #2082: 1: Success after gdb-12-branchpoint-2 [...] discards 4e8265e148 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 commits discards 91e4447449 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits discards e32d8317b1 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits discards 3b36e1adb3 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits discards c23f0776a6 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits discards 4360ffb8a9 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits discards 2929f444da 141: onsuccess: #2073: 1: Success after binutils: 3 commits discards 783fab0b46 140: onsuccess: #2070: 1: Success after binutils: 4 commits discards 25e310285c 139: onsuccess: #2067: 1: Success after binutils: 2 commits discards 1384aaf333 138: onsuccess: #2064: 1: Success after binutils: 4 commits discards d49380fda1 137: onsuccess: #2061: 1: Success after binutils: 2 commits discards 1c0cf618d0 136: onsuccess: #2056: 1: Success after binutils: 4 commits discards 56c891e4a9 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits discards bfe1ea348b 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits discards 5741732168 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits discards 465f588f57 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits discards fc92d9cf55 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] discards add58202ef 130: onsuccess: #2049: 1: Success after gcc: 9 commits discards 698e88be05 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] discards 17e9a3efb1 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] discards 97df724ff6 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] discards ddc4206b22 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] discards 2ad64fb664 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits discards 3cd81ff45b 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits discards aa1ce838b9 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits discards 709c504283 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits discards 11443308a4 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits discards 10fa792a72 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits discards 19b2bc688e 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits discards 15b2e96705 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits discards cb5d8371ab 117: onsuccess: #2034: 1: Success after binutils: 2 commits discards 416d14a98d 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits discards d59bc2df1d 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits discards 5a45c90e2d 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits discards e4148f1793 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits discards f4f4ac99cb 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits discards 4801c4cc79 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits discards 201f4f486a 110: onsuccess: #2027: 1: Success after gcc: 5 commits discards 0e89f170e6 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits discards 0dd8a6003f 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits discards b636ff812b 107: onsuccess: #2024: 1: Success after gcc: 3 commits discards 240e32c25e 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits discards 69ffec60e6 105: onsuccess: #2022: 1: Success after gcc: 4 commits discards f0ff2b5e91 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards 0c02b0e867 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards a824f726a2 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] discards c9a499fe8f 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards 46b2aecd3d 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards 7f742c47b7 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards b692d5dc8c 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards 879940403b 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards 6c318fb60d 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] discards 29cf20d93a 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] discards 7659268a2c 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards 64b6ac6598 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] discards b5d9645736 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards 3465490608 91: onsuccess: 1: Success after gcc: Daily bump. discards 2bb9538ec3 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards a2228a0ad8 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards 6391ad2821 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards 228d7bd33d 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards 92f7ead9cb 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards c1ae26efb6 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards 2ff5b1ce71 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards a014e2ed25 83: onsuccess: 1: Success after gcc: 8 commits discards fa5b5ef1bb 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards 7cb11dad83 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards 76aa06d3a2 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards 8d6b282085 79: onsuccess: 1: Successful build after gcc: Daily bump. discards 49e4bac600 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 8d80583696 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 24200481a3 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards c546528101 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 5b4c40b717 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards e0aa636f88 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards 9814e5aab6 72: onsuccess: 1: Successful build after gcc: 2 commits discards 1b4e4f9b34 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 7b1ea11cc5 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards 4928e8b242 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 1d5906152c 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 86c018ceec 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards f06e8e5ee2 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards adcee56185 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 5b21503726 64: onsuccess: 1: Successful build after gcc: 5 commits discards 2960b23770 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards c4617f4a43 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 27bb2d3711 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits discards b694aaedb4 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards b397c1a436 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits new a94518f2a4 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits new f1e290fd0f 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 4b5ac678bd 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits new ea9a997b56 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits new d301c85049 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 236561259e 64: onsuccess: 1: Successful build after gcc: 5 commits new bcf18618e5 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 812d95c63a 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new dc1bd9a9b3 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 9073286a9d 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 7b5042a9ee 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 9f875cbff7 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new 73625e5fb7 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 414e3ae230 72: onsuccess: 1: Successful build after gcc: 2 commits new aa28810b62 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] new c3b24d08b4 74: onsuccess: 1: Successful build after binutils: Automatic [...] new e08ae54587 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 9859ae89cd 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new f41625d2e2 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new ea95c40228 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new b43ff27961 79: onsuccess: 1: Successful build after gcc: Daily bump. new b2acd625e1 80: onsuccess: 1: Success after binutils/gcc: 14 commits new 06f67a5604 81: onsuccess: 1: Success after binutils/gcc: 27 commits new 68ac3dfa50 82: onsuccess: 1: Success after binutils/gcc: 10 commits new 91f5ff1d80 83: onsuccess: 1: Success after gcc: 8 commits new 174dfcaa85 84: onsuccess: 1: Success after binutils/gcc: 9 commits new 942b55aef9 85: onsuccess: 1: Success after binutils/gcc: 9 commits new 0f809611e3 86: onsuccess: 1: Success after binutils/gcc: 13 commits new bd1e218b2f 87: onsuccess: 1: Success after binutils/gcc: 4 commits new 537f9874e6 88: onsuccess: 1: Success after binutils/gcc: 16 commits new f143e0c38b 89: onsuccess: 1: Success after binutils/gcc: 9 commits new 01dc7eb9ca 90: onsuccess: 1: Success after binutils/gcc: 6 commits new 25ef261c12 91: onsuccess: 1: Success after gcc: Daily bump. new 81ea507702 92: onsuccess: #1965: 1: Success after gcc: 2 commits new bc89df8acf 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] new bc87f2f9b3 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new 4df0c32c1e 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] new cb4e5308c0 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] new 88dbf0e0d2 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new c59d0c05e1 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new a283522b93 99: onsuccess: #1974: 1: Success after gcc: 14 commits new 877fe7b81f 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new b41980936c 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new befbb8eb70 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] new 7a3226e9d5 103: onsuccess: #2020: 1: Success after gcc: 2 commits new 65a54a0386 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new 1d79605bc2 105: onsuccess: #2022: 1: Success after gcc: 4 commits new 6b82d77f2c 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits new 32f739fa2f 107: onsuccess: #2024: 1: Success after gcc: 3 commits new c1eb2ea629 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits new c56353e195 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits new 61aaeed56b 110: onsuccess: #2027: 1: Success after gcc: 5 commits new 0015022b05 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits new 5a7825e29e 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits new 577a858d2f 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits new 9a6d13a48e 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits new 26771c946a 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits new 213bf2395c 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits new b779027f88 117: onsuccess: #2034: 1: Success after binutils: 2 commits new a77c768707 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits new 82a124abf8 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits new 90bb09dbdc 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits new 8c8c10ae8f 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits new d6133ab1b0 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits new 4668ae1739 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits new 1ccecef9aa 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits new 240c26a267 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits new c146795fa6 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] new 96206cc499 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] new d287acfa43 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] new 0e993430d8 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] new 822f304ca5 130: onsuccess: #2049: 1: Success after gcc: 9 commits new 8d2df2650f 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] new 12e8494a59 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits new 7cdb84662b 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits new feed0fec3c 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits new 7aee4a5b6e 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits new 4dbb312719 136: onsuccess: #2056: 1: Success after binutils: 4 commits new 81d0750a80 137: onsuccess: #2061: 1: Success after binutils: 2 commits new 1780e5f991 138: onsuccess: #2064: 1: Success after binutils: 4 commits new 4fc4789920 139: onsuccess: #2067: 1: Success after binutils: 2 commits new 24d8266d9a 140: onsuccess: #2070: 1: Success after binutils: 4 commits new 20045a12a4 141: onsuccess: #2073: 1: Success after binutils: 3 commits new 878b4536be 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits new a1775125c7 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits new f874282e5c 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits new 6a28787fa6 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits new cfe418d1d1 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits new 5a64bf8c0e 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 commits new ceb13ecf5d 148: onsuccess: #2082: 1: Success after gdb-12-branchpoint-2 [...] new 5deea10a7c 149: onsuccess: #2084: 1: Success after gcc: 16 commits new 7485a6f915 150: onsuccess: #2085: 1: Success after gcc: 2 commits new f0ec0fd0a3 151: onsuccess: #2086: 1: Success after gcc: 2 commits new 7eb2b8ebf0 152: onsuccess: #2087: 1: Success after gdb-12-branchpoint-2 [...] new 648e6caa5b 153: onsuccess: #2088: 1: Success after basepoints/gcc-13-30 [...] new adf838b67d 154: onsuccess: #2089: 1: Success after gcc: 4 commits new 98d40fecb0 155: onsuccess: #2090: 1: Success after binutils/gcc: 22 commits new 96676b9aa3 156: onsuccess: #2091: 1: Success after binutils/gcc: 2 commits new da5667c0b3 157: onsuccess: #2092: 1: Success after binutils/gcc: 3 commits new e63e618f5b 158: onsuccess: #2093: 1: Success after binutils/gcc: 9 commits new b16f681824 159: onsuccess: #2094: 1: Success after binutils/gcc: 23 commits new 690d864a10 160: onsuccess: #2095: 1: Success after binutils/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 (840efa550a) \ 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 1708 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 39172 -> 37568 bytes 04-build_abe-gcc/console.log.xz | Bin 214204 -> 212540 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3824 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2652 -> 2308 bytes 07-check_regression/console.log.xz | Bin 7024 -> 4896 bytes 07-check_regression/extra-bisect-params | 1 - 07-check_regression/fails.sum | 7 - 07-check_regression/mail-body.txt | 70 +- 07-check_regression/results.compare | 36 +- 07-check_regression/results.compare2 | 297 +- 07-check_regression/results.regressions | 42 - 08-update_baseline/console.log | 36 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 72 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 42 - sumfiles/g++.log.xz | Bin 3608300 -> 3570860 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 3098888 -> 3134120 bytes sumfiles/gcc.sum | 4736 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1041760 -> 1044604 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2184 -> 2192 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207924 -> 207700 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 444108 -> 447816 bytes sumfiles/libstdc++.sum | 10 +- 36 files changed, 2553 insertions(+), 3012 deletions(-) delete mode 100644 07-check_regression/extra-bisect-params delete mode 100644 07-check_regression/fails.sum delete mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_llvm_apm/llvm-release-aarch64-spec2k6-Os_LTO updated (34f41b438d -> 822732e782)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_llvm_apm/llvm-release-aarch64-spec2k6-Os_LTO in repository toolchain/ci/base-artifacts. from 34f41b438d 16: onsuccess: #123: 1: [TCWG CI] No change after binutils/g [...] new 822732e782 17: onsuccess: #124: 1: [TCWG CI] No change after binutils/g [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1776 -> 2016 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30476 -> 30824 bytes 04-build_abe-stage1/console.log.xz | Bin 68664 -> 70688 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 7872 -> 8656 bytes 07-build_abe-glibc/console.log.xz | Bin 237772 -> 237884 bytes 08-build_abe-stage2/console.log.xz | Bin 172796 -> 179164 bytes 09-build_llvm-true--/console.log.xz | Bin 0 -> 62544 bytes 09-build_llvm-true/console.log.xz | Bin 62200 -> 0 bytes 10-benchmark/benchmark-build.log | 98 +- 10-benchmark/benchmark.log | 96 +- 10-benchmark/console.log.xz | Bin 3768 -> 3736 bytes 11-check_regression/console.log.xz | Bin 7152 -> 7420 bytes 11-check_regression/csv-results-0/perf.csv | 152 +- 11-check_regression/csv-results-0/results.csv | 358298 ++++++++--------- 11-check_regression/csv-results-0/size.csv | 350580 ++++++++--------- 11-check_regression/csv-results-0/vect.csv | 21295 +- 11-check_regression/csv-results-1/perf.csv | 156 +- 11-check_regression/csv-results-1/results.csv | 363183 +++++++++--------- 11-check_regression/csv-results-1/size.csv | 355535 ++++++++--------- 11-check_regression/csv-results-1/vect.csv | 21804 +- 11-check_regression/results-brief.csv | 48 +- 11-check_regression/results-compare.csv | 4 + 11-check_regression/results-full.csv | 174 +- 11-check_regression/results-internal.csv | 58 +- 11-check_regression/results.csv | 58 +- 11-check_regression/results.log | 911 +- 12-update_baseline/console.log | 8 +- dashboard/dashboard-generate.sh | 2 +- .../squad/400.perlbench/results-metadata.json | 18 +- dashboard/squad/400.perlbench/results-metrics.json | 2 +- dashboard/squad/401.bzip2/results-metadata.json | 18 +- dashboard/squad/401.bzip2/results-metrics.json | 2 +- dashboard/squad/403.gcc/results-metadata.json | 18 +- dashboard/squad/403.gcc/results-metrics.json | 2 +- dashboard/squad/429.mcf/results-metadata.json | 18 +- dashboard/squad/429.mcf/results-metrics.json | 2 +- dashboard/squad/433.milc/results-metadata.json | 18 +- dashboard/squad/433.milc/results-metrics.json | 2 +- dashboard/squad/444.namd/results-metadata.json | 18 +- dashboard/squad/444.namd/results-metrics.json | 2 +- dashboard/squad/445.gobmk/results-metadata.json | 18 +- dashboard/squad/445.gobmk/results-metrics.json | 2 +- dashboard/squad/447.dealII/results-metadata.json | 18 +- dashboard/squad/447.dealII/results-metrics.json | 2 +- dashboard/squad/450.soplex/results-metadata.json | 18 +- dashboard/squad/450.soplex/results-metrics.json | 2 +- dashboard/squad/453.povray/results-metadata.json | 18 +- dashboard/squad/453.povray/results-metrics.json | 2 +- dashboard/squad/456.hmmer/results-metadata.json | 18 +- dashboard/squad/456.hmmer/results-metrics.json | 2 +- dashboard/squad/458.sjeng/results-metadata.json | 18 +- dashboard/squad/458.sjeng/results-metrics.json | 2 +- .../squad/462.libquantum/results-metadata.json | 18 +- .../squad/462.libquantum/results-metrics.json | 2 +- dashboard/squad/464.h264ref/results-metadata.json | 18 +- dashboard/squad/464.h264ref/results-metrics.json | 2 +- dashboard/squad/470.lbm/results-metadata.json | 18 +- dashboard/squad/470.lbm/results-metrics.json | 2 +- dashboard/squad/471.omnetpp/results-metadata.json | 18 +- dashboard/squad/471.omnetpp/results-metrics.json | 2 +- dashboard/squad/473.astar/results-metadata.json | 18 +- dashboard/squad/473.astar/results-metrics.json | 2 +- dashboard/squad/482.sphinx3/results-metadata.json | 18 +- dashboard/squad/482.sphinx3/results-metrics.json | 2 +- .../squad/483.xalancbmk/results-metadata.json | 18 +- dashboard/squad/483.xalancbmk/results-metrics.json | 2 +- dashboard/squad/dashboard-push-squad.sh | 78 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 56 +- mail/mail-body.txt | 56 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 2 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 403000 -> 402996 bytes save-temps/401.bzip2.tar.xz | Bin 43796 -> 43836 bytes save-temps/403.gcc.tar.xz | Bin 1214232 -> 1214416 bytes save-temps/429.mcf.tar.xz | Bin 22228 -> 22240 bytes save-temps/433.milc.tar.xz | Bin 58656 -> 58668 bytes save-temps/444.namd.tar.xz | Bin 46464 -> 46468 bytes save-temps/445.gobmk.tar.xz | Bin 620012 -> 620080 bytes save-temps/447.dealII.tar.xz | Bin 881804 -> 881644 bytes save-temps/450.soplex.tar.xz | Bin 209156 -> 209200 bytes save-temps/453.povray.tar.xz | Bin 464776 -> 464888 bytes save-temps/456.hmmer.tar.xz | Bin 124568 -> 124632 bytes save-temps/458.sjeng.tar.xz | Bin 52040 -> 52044 bytes save-temps/462.libquantum.tar.xz | Bin 23572 -> 23604 bytes save-temps/464.h264ref.tar.xz | Bin 175980 -> 176096 bytes save-temps/470.lbm.tar.xz | Bin 15492 -> 15484 bytes save-temps/471.omnetpp.tar.xz | Bin 320696 -> 320708 bytes save-temps/473.astar.tar.xz | Bin 43404 -> 43348 bytes save-temps/482.sphinx3.tar.xz | Bin 95032 -> 95016 bytes save-temps/483.xalancbmk.tar.xz | Bin 3341532 -> 3342184 bytes 99 files changed, 741574 insertions(+), 731514 deletions(-) create mode 100644 09-build_llvm-true--/console.log.xz delete mode 100644 09-build_llvm-true/console.log.xz -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[linux] branch master updated (d0989d01c66f -> 26b84401da84)

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 d0989d01c66f Merge tag 'hardening-v6.1-rc1' of git://git.kernel.org/pub [...] new 4ca165fc6c49 SMACK: Add sk_clone_security LSM hook new d3f84f5c9627 smack: lsm: remove the unneeded result variable new cc71271f5b79 smack: cleanup obsolete mount option flags new 74a0f84590ee Merge tag 'Smack-for-6.1' of https://github.com/cschaufler [...] new 5926586f291b ima: fix blocking of security.ima xattrs of unsupported al [...] new bab715bdaa9e efi: Correct Macmini DMI match in uefi cert quirk new eafb121ec0db Merge tag 'integrity-v6.1' of git://git.kernel.org/pub/scm [...] new 5698f08169b9 selinux: remove an unneeded variable in sel_make_class_dir [...] new c3fae2b2e690 selinux: use int arrays for boolean values new 6354324d8a3e selinux: declare read-only parameters const new 09b71adab095 selinux: remove the unneeded result variable new c969bb8dbaf2 selinux: use "grep -E" instead of "egrep" new 2fe2fb4ce60b selinux: remove runtime disable message in the install_pol [...] new e816da29bc0c Merge tag 'selinux-pr-20221003' of git://git.kernel.org/pu [...] new 4847c0eb663a lsm: clean up redundant NULL pointer check new 7cd4c5c2101c security, lsm: Introduce security_create_user_ns() new 401e64b3a4af bpf-lsm: Make bpf_lsm_userns_create() sleepable new d5810139cca3 selftests/bpf: Add tests verifying bpf lsm userns_create hook new ed5d44d42c95 selinux: Implement userns_create hook new abec3d015fdf userfaultfd: open userfaultfds with O_RDONLY new 1e7d8bcbe37d lockdown: ratelimit denial messages new 26b84401da84 Merge tag 'lsm-pr-20221003' of git://git.kernel.org/pub/sc [...] The 22 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: fs/userfaultfd.c | 4 +- include/linux/lsm_hook_defs.h | 1 + include/linux/lsm_hooks.h | 4 + include/linux/security.h | 6 ++ kernel/bpf/bpf_lsm.c | 1 + kernel/user_namespace.c | 5 + scripts/selinux/install_policy.sh | 5 +- security/integrity/ima/ima_appraise.c | 12 ++- security/integrity/platform_certs/load_uefi.c | 2 +- security/lockdown/lockdown.c | 2 +- security/lsm_audit.c | 14 +-- security/security.c | 5 + security/selinux/hooks.c | 33 ++++--- security/selinux/include/classmap.h | 2 + security/selinux/selinuxfs.c | 15 ++- security/selinux/ss/context.h | 17 ++-- security/selinux/ss/ebitmap.c | 21 +++-- security/selinux/ss/ebitmap.h | 18 ++-- security/selinux/ss/mls_types.h | 4 +- security/smack/smack.h | 9 -- security/smack/smack_lsm.c | 20 +++- .../selftests/bpf/prog_tests/deny_namespace.c | 102 +++++++++++++++++++++ .../selftests/bpf/progs/test_deny_namespace.c | 33 +++++++ 23 files changed, 246 insertions(+), 89 deletions(-) create mode 100644 tools/testing/selftests/bpf/prog_tests/deny_namespace.c create mode 100644 tools/testing/selftests/bpf/progs/test_deny_namespace.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022