Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-allmodconfig updated (927119a43a -> d1fa06a771)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-allmodconfig in repository toolchain/ci/base-artifacts. from 927119a43a 14: onsuccess: #500: boot: Success after v5.19.11-39055-g0d0 [...] new d1fa06a771 15: onsuccess: #501: boot: Success after binutils: 53 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 1668 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30360 -> 30528 bytes 04-build_kernel_llvm/console.log.xz | Bin 65452 -> 65376 bytes 05-build_abe-qemu/console.log.xz | Bin 31740 -> 31452 bytes 06-build_linux/console.log.xz | Bin 3256 -> 3360 bytes 07-boot_linux/console.log.xz | Bin 508 -> 508 bytes 08-check_regression/console.log.xz | Bin 2756 -> 2992 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 12 ++++++------ 14 files changed, 11 insertions(+), 11 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (37db4a2a63 -> ecafc414dd)

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 37db4a2a63 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards a03517cd64 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 525d731af4 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards cf7cdd3a38 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards d08238b13c 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 0f5af9d551 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 32efe5cb0a 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 7540ed7896 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards d0bbb791b6 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 0c35115542 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards b26880c3f5 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 2ebb594386 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards e7ffeeeb89 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 5efced6c89 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 5e0f2ac750 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 21ded787d4 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 2ba6eafa01 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards dea5ad64f9 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 6f73568d5c 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards daa552e0e6 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards a30e39b47a 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 8fa6506b97 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 45600e11ed 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 9b0b6e57d3 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards f520d1a030 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 59a90c74ea 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards f27ab951a2 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards c28eaa24ff 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 69c9ab6dd6 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 6ec8e2dd37 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards e1b78d3064 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 70b7848663 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 27705bee35 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 85c4fe614f 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 56f6717c70 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 166f14763a 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 22b9caf9af 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 4c731b7f53 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 8436782d4f 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards d7a03bdc90 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards f07314b4d0 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards e1dde4c011 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 5fbb2d8f16 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 35cbd6f0be 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 0ee8253d90 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 7f7a5f6c00 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 79d271f331 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 77ffa7695b 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 6634c8db87 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 2338b2312e 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 23b2c87b74 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 18b5aea4f5 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7dea4df532 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3286ee1a9c 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 88b0840b30 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a626c4e0bc 74: onsuccess: 1: Successful build after linux: 44 commits discards c59076a478 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards c58e923722 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d1e72b9153 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards c7727c1b79 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards a427bd0f34 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards cc43c09c2e 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e1c4b1ab86 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ce64403521 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a9f8b8aee1 65: onsuccess: 1: Successful build after gcc: 4 commits discards 9a0dfa4055 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 19ff1a2ffe 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ec1023d93a 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 35903c16ac 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 15810301a3 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 338ded01be 59: onsuccess: 1: Successful build after glibc: 2 commits discards d8d51a08c1 58: onsuccess: 1: Successful build after binutils: 2 commits discards 98752c4499 57: onsuccess: 1: Successful build after gcc: 7 commits discards 0610fe7263 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards da3f3aa9d6 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bbc11f4a1a 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards e75afee7c7 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 3698d80af8 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 0937ec848d 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ec9344bec5 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 129ea9a26c 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a05212822a 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 1083841824 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6a29596bcb 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 90b77665ce 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 79a0fb3b02 44: onsuccess: 1: Successful build after linux: 34 commits discards 47db9b9662 43: onsuccess: 1: Successful build after gcc: 2 commits discards e5c618844a 42: onsuccess: 1: Successful build after baseline build: no [...] discards 9e6246f5a1 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b5fb21eca5 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b930b2afb3 39: onsuccess: 1: Successful build after gcc: 2 commits discards b4f5d81d70 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7ae66a5e6c 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d26afd014e 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c52e1cab72 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 10c115c98a 34: onsuccess: 1: Successful build after gcc: 3 commits discards 6675b5edee 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ffbe4a2c32 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 9f1ae54a26 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 00456d2217 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards 3d157d49be 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ad3caf4037 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 410b227e87 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 394268c90b 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 7a863b7269 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 0ee43e11bb 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e2be69d981 34: onsuccess: 1: Successful build after gcc: 3 commits new d30516ef0c 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0eacda666f 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d2749e0e0a 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 092a8d59f9 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f9bf61470f 39: onsuccess: 1: Successful build after gcc: 2 commits new 3588de45bc 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0fd014a920 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 32ddef2b62 42: onsuccess: 1: Successful build after baseline build: no [...] new 2b05f0c2a5 43: onsuccess: 1: Successful build after gcc: 2 commits new 193c50b5ab 44: onsuccess: 1: Successful build after linux: 34 commits new 3eb48879c6 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e07301b0c7 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 818ef28b34 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f7da76ac15 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new b41786864f 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 05b547f523 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new dc08955d4b 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d42c7e5879 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 789e1d5906 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 5c85427cac 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 79a1ebd7f3 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 024417f60e 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ebcef19bfc 57: onsuccess: 1: Successful build after gcc: 7 commits new f7b3f02bf7 58: onsuccess: 1: Successful build after binutils: 2 commits new 083fcb7623 59: onsuccess: 1: Successful build after glibc: 2 commits new aacc4e5ae6 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new b8a7a25760 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new c229702f1b 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 1c9631906c 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f7a6dc9008 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c6e937f529 65: onsuccess: 1: Successful build after gcc: 4 commits new 6cb0a62fd4 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 53b4629172 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ae56273fe4 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2fcb355a8e 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new e394e875b6 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new b2910842b1 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 07a7ba7a56 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 50fc9d3711 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 0905b09dd1 74: onsuccess: 1: Successful build after linux: 44 commits new 03c1389e21 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 60a0431366 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new fb1a281379 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4f0bf57047 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new fdb33a2186 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 5d2d8edb39 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 6f664ea9f6 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 2daae6b96d 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 2677feccab 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new e508c0d157 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 0e5fd0c817 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 8c09d960fa 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 0c55d6f243 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new f0078f3026 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 35af870548 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 273cdf6382 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 9a3b5430cd 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 7b4dfaf1f8 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 4d3fe9fe4b 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 557a183705 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new ec98b8653a 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new df28a73a4e 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 2cc69b080e 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new db7c516e4a 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new c6c0e8cd5c 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 4811a72de1 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new cffbadc61a 101: onsuccess: #1693: 1: Success after glibc: 14 commits new ae231a65f3 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 4b2cb79166 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 0e154df4f1 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 1ec1f55daa 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 8a6b446bf7 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new dec8e033e1 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 0d5045e104 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new fb83898960 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 84bf42db5e 110: onsuccess: #1703: 1: Success after gcc: 6 commits new e7b7493690 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 7e3adfbcb9 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 23e85aff34 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new d65c66311a 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 21c52ad36c 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new b849b2f44e 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 1e656048fc 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new a83ddbae52 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 8aa951a37e 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 1044c1a0e5 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 72cca13661 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new ff50a187d3 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new ad7047889d 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 6d0dc37751 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 074ae5a59d 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 2da93c514b 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 4b4c9b7ce8 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 6697c9623a 128: onsuccess: #1723: 1: Success after linux: 12 commits new 1df35921e5 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new ecafc414dd 130: onsuccess: #1725: 1: Success after gcc/linux: 32 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 (37db4a2a63) \ 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 1668 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 29792 -> 29904 bytes 04-build_abe-stage1/console.log.xz | Bin 90704 -> 91260 bytes 06-build_abe-linux/console.log.xz | Bin 8660 -> 8956 bytes 07-build_abe-glibc/console.log.xz | Bin 233916 -> 234196 bytes 08-build_abe-stage2/console.log.xz | Bin 223848 -> 224268 bytes 09-build_abe-gdb/console.log.xz | Bin 37096 -> 37136 bytes 10-build_abe-qemu/console.log.xz | Bin 31132 -> 31040 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2592 -> 2888 bytes 13-check_regression/console.log.xz | Bin 5492 -> 6924 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 263 +++- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 26 - sumfiles/g++.log.xz | Bin 2657752 -> 2659916 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2230424 -> 2213044 bytes sumfiles/gcc.sum | 1986 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 888060 -> 882136 bytes sumfiles/gfortran.sum | 234 +++- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201140 -> 201260 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429208 -> 426372 bytes sumfiles/libstdc++.sum | 10 +- 41 files changed, 1598 insertions(+), 1195 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_llvm_apm/llvm-release-aarch64-spec2k6-Oz updated (ed39f98754 -> 5c196bffea)

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-Oz in repository toolchain/ci/base-artifacts. from ed39f98754 6: onsuccess: #114: 1: [TCWG CI] No change after binutils/gc [...] new 5c196bffea 7: onsuccess: #115: 1: [TCWG CI] No change after binutils/gc [...] 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 1760 -> 1920 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 30640 -> 30904 bytes 04-build_abe-stage1/console.log.xz | Bin 69776 -> 70588 bytes 06-build_abe-linux/console.log.xz | Bin 7856 -> 8600 bytes 07-build_abe-glibc/console.log.xz | Bin 237416 -> 237860 bytes 08-build_abe-stage2/console.log.xz | Bin 174028 -> 176952 bytes 09-build_llvm-true/console.log.xz | Bin 61748 -> 62572 bytes 10-benchmark/benchmark-build.log | 100 +- 10-benchmark/benchmark.log | 98 +- 10-benchmark/console.log.xz | Bin 3812 -> 3744 bytes 11-check_regression/console.log.xz | Bin 8668 -> 11476 bytes 11-check_regression/csv-results-0/md5sum.csv | 2087 +- 11-check_regression/csv-results-0/perf.csv | 2445 +- 11-check_regression/csv-results-0/results.csv | 357641 ++++++++--------- 11-check_regression/csv-results-0/size.csv | 353918 +++++++++-------- 11-check_regression/csv-results-0/vect.csv | 18371 +- 11-check_regression/csv-results-1/md5sum.csv | 1890 +- 11-check_regression/csv-results-1/perf.csv | 2579 +- 11-check_regression/csv-results-1/results.csv | 367966 +++++++++--------- 11-check_regression/csv-results-1/size.csv | 364271 ++++++++--------- 11-check_regression/csv-results-1/vect.csv | 18900 +- 11-check_regression/results-brief.csv | 38 +- 11-check_regression/results-compare.csv | 6 +- 11-check_regression/results-full.csv | 2619 +- 11-check_regression/results-internal.csv | 152 +- 11-check_regression/results.csv | 152 +- 11-check_regression/results.log | 797 +- 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/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/Mean/results-metadata.json | 18 +- dashboard/squad/Mean/results-metrics.json | 2 +- dashboard/squad/dashboard-push-squad.sh | 82 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 59 +- mail/mail-body.txt | 59 +- mail/mail-subject.txt | 2 +- manifest.sh | 41 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 1241964 -> 1248576 bytes save-temps/403.gcc.tar.xz | Bin 3445504 -> 3428512 bytes save-temps/429.mcf.tar.xz | Bin 32892 -> 33052 bytes save-temps/433.milc.tar.xz | Bin 146924 -> 146984 bytes save-temps/444.namd.tar.xz | Bin 179820 -> 179956 bytes save-temps/445.gobmk.tar.xz | Bin 2030444 -> 2031596 bytes save-temps/447.dealII.tar.xz | Bin 3340208 -> 3271820 bytes save-temps/450.soplex.tar.xz | Bin 505052 -> 497212 bytes save-temps/453.povray.tar.xz | Bin 1161264 -> 1149180 bytes save-temps/456.hmmer.tar.xz | Bin 336336 -> 336312 bytes save-temps/458.sjeng.tar.xz | Bin 150308 -> 150436 bytes save-temps/462.libquantum.tar.xz | Bin 51092 -> 51296 bytes save-temps/464.h264ref.tar.xz | Bin 581612 -> 580328 bytes save-temps/470.lbm.tar.xz | Bin 24924 -> 24940 bytes save-temps/471.omnetpp.tar.xz | Bin 854432 -> 837804 bytes save-temps/473.astar.tar.xz | Bin 73788 -> 73868 bytes save-temps/482.sphinx3.tar.xz | Bin 224500 -> 223872 bytes save-temps/483.xalancbmk.tar.xz | Bin 7360396 -> 7532256 bytes 97 files changed, 757911 insertions(+), 736774 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (53d946af28 -> ddd0c74138)

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 53d946af28 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards a3711e93cc 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards 10c7089309 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 9c5f36755d 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards 50698bd306 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards e0194d8fe9 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards d7f6483702 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards 8665bac49c 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards d9d0449dd7 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards e5079fd19e 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 9e4c70cee6 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 69917f9ee3 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards e4b6e6f284 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards fcc1dd7376 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards c36520b8bf 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 6f9d533bbf 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 5040589b9b 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards fc7994916e 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 625b9bf35e 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards a9a3b8c0bd 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards c6e145c010 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 6a7a0a131a 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards a11a903945 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards af574cb26a 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards e0b7d351da 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 07628522f4 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards a6e2b7b719 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards a9748c3db1 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 56d3aeb128 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 73f8323105 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards a9d2251f4a 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 59a14b5d03 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards eae5d75b4c 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 09d32cbbd4 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 78c45af23b 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards 46b6074af0 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 62f4042d0d 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards f151ff60f4 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards af5a9f33a8 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 4e42fa77bd 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards a8271e65c1 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 5b4b016c1d 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 3f330995c2 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 32e329ea04 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 781a46c8ec 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 865c4ee736 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 408029bc56 85: onsuccess: 7: Success after gcc: 9 commits discards 11be3c1f5e 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 2d294ab7e0 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 2cfd9c61e0 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 758b7b89ff 81: onsuccess: 7: Successful build after gcc: 2 commits discards e22adbd233 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 5f47f9a498 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards b8a276a6da 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 94569324a2 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 2b3e5046bb 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6b35f07894 75: onsuccess: 7: Successful build after linux: 44 commits discards 39d33b5b52 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards f5761fe857 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 31e38e44d8 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards da89b58989 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards e753b9f0a8 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 7e1325111f 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 94dc71ffc8 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0703adde91 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards a828ff0593 66: onsuccess: 7: Successful build after gcc: 3 commits discards 7d044deca1 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 221b15db2b 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ad841ad949 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 442576a561 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards bd9f414984 61: onsuccess: 4: Successful build after gcc: 15 commits discards 62de5c91ae 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards cd668fb2ec 59: force: 7: Successful build after gcc: 2 commits discards 5939679569 58: onsuccess: 7: Successful build after glibc: 2 commits discards a6d536ed4c 57: onsuccess: 7: Successful build after gcc: 7 commits discards dd436f2cc1 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards eee173cf6f 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 8e83c215e0 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 05d5babf0e 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards dd625d615e 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards dcad784a09 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 9b35556c26 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3f515510d7 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 160e3f1310 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 51277a49a4 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 00f09a090e 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 6c41c189c4 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 65e2884140 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards d297bfbcfc 43: onsuccess: 7: Successful build after gcc: 2 commits discards 2f083f1565 42: onsuccess: 7: Successful build after baseline build: no [...] discards 5533938f74 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 36c1b27012 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7823bb2a2b 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] discards be1517c511 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards 7eb295776f 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 3553f69bff 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 98eb8c69e1 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards ac22eea767 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards f76cfc0a5d 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b142479b31 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 1d6416748f 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new e7fbc1fc33 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 3f77f7fec6 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 6555a9bd9e 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 06067e6c6e 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 20b35b06a4 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 4cd1a7c1d8 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 13d22ab1f8 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 56ddc11bc7 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new 4e6f813e70 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] new 9f0455b084 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 32041ebfa6 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8295a10709 42: onsuccess: 7: Successful build after baseline build: no [...] new e20c429777 43: onsuccess: 7: Successful build after gcc: 2 commits new 05a1e1b8a2 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new 096cb3f63f 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new dd144527b4 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 5a5f963fa4 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 1fad5add8c 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 3565c0b346 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 586a772d1f 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new abf9d89550 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 9f1120f37c 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 725576d6a1 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new ec17e73dc4 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new f5096e32dd 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8591b8c931 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f516126792 57: onsuccess: 7: Successful build after gcc: 7 commits new ceefb9a1ce 58: onsuccess: 7: Successful build after glibc: 2 commits new b34ab59d3f 59: force: 7: Successful build after gcc: 2 commits new ffb7e8f75e 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new a707fc3802 61: onsuccess: 4: Successful build after gcc: 15 commits new af79c434a9 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new e4c27cdad0 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 57b97b5ae4 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 093806ef42 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 34618e25e7 66: onsuccess: 7: Successful build after gcc: 3 commits new f2d8ab3ab2 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 9e7634d129 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e5f22dfb95 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 653fe7b7c8 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new ad77716a52 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 7c067038f6 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 4de412238e 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 30a05b224a 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new c0908260b4 75: onsuccess: 7: Successful build after linux: 44 commits new 3d92f186b9 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 547e859590 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new c16d33be49 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new bf7687858f 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 1f8fab3f9a 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 1facdb4d51 81: onsuccess: 7: Successful build after gcc: 2 commits new c8db720098 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 6b10208729 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new d86b97dc9e 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 2c0d7a1948 85: onsuccess: 7: Success after gcc: 9 commits new af084dbeeb 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 0334121631 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 9208adc4ca 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new ec0745e7b1 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new a2c8d000b9 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new ce421b9133 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new c420d6992b 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new c89a73d5d8 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new 6d4881eb26 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 9ab6a08a19 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new aadf30f7ab 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 769bd8257a 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new a833e6161e 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 9ed09782e2 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 5978c5890f 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new f3e336ab11 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 940fe2538e 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 490d2b1d0c 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 88d2312559 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 2dba0a3822 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 4d0f3b6a86 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 4f1c2dab26 107: onsuccess: #1618: 7: Success after gcc: 2 commits new eef79c87d6 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new f92da29409 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 12f7358003 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new 03850a5c1b 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 14aec26531 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new f5bba27483 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 0ecfaf5eaa 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 33ccc14cc6 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 2a5c244b8f 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new b069915ed2 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new a18b179ace 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 4003c25cd2 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 738ad575cd 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 078dc744d1 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new 936e20ac50 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 111ae698d8 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new dde697a2e6 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 7e632c65d2 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new 9dadb4fc9e 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new 4cf0ee6e18 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 4b7057699b 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new e9b9fb29d9 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new c2ca83f703 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new a4936447d3 131: onsuccess: #1644: 7: Success after gcc: 10 commits new ddd0c74138 132: onsuccess: #1645: 7: Success after linux: 23 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 (53d946af28) \ 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 1672 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 29844 -> 29944 bytes 05-build_abe-stage1/console.log.xz | Bin 91032 -> 91220 bytes 07-build_abe-linux/console.log.xz | Bin 8904 -> 8816 bytes 08-build_abe-glibc/console.log.xz | Bin 236056 -> 234688 bytes 09-build_abe-stage2/console.log.xz | Bin 228760 -> 226212 bytes 10-build_abe-gdb/console.log.xz | Bin 37956 -> 37804 bytes 11-build_abe-qemu/console.log.xz | Bin 31116 -> 31460 bytes 12-check_regression/console.log.xz | Bin 3348 -> 3540 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +++++------ 17 files changed, 47 insertions(+), 47 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-allnoconfig updated (d368cee059 -> ca997e324f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-allnoconfig in repository toolchain/ci/base-artifacts. from d368cee059 11: onsuccess: #369: all: Success after binutils/gcc/linux/q [...] new ca997e324f 12: onsuccess: #370: all: 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 1720 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 31016 -> 29728 bytes 04-build_abe-stage1/console.log.xz | Bin 91076 -> 90820 bytes 05-build_abe-qemu/console.log.xz | Bin 31728 -> 31148 bytes 06-build_linux/console.log.xz | Bin 4148 -> 4140 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 3488 -> 4180 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 31 ++++++++++++++++--------------- 17 files changed, 24 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-norov-defconfig updated (e9385446db -> bdcd49325f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-norov-defconfig in repository toolchain/ci/base-artifacts. from e9385446db 11: onsuccess: #38: boot: Success after binutils/gcc/linux/q [...] new bdcd49325f 12: onsuccess: #39: boot: Success after binutils/gcc/qemu: 1 [...] 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 1896 -> 1888 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30100 -> 29900 bytes 04-build_abe-stage1/console.log.xz | Bin 91764 -> 91324 bytes 05-build_abe-qemu/console.log.xz | Bin 31644 -> 31056 bytes 06-build_linux/console.log.xz | Bin 5540 -> 5484 bytes 07-boot_linux/console.log.xz | Bin 5892 -> 5812 bytes 08-check_regression/console.log.xz | Bin 3408 -> 3808 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 27 ++++++++++++++------------- 16 files changed, 21 insertions(+), 20 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/release-arm-check_bootstrap updated (53e277b6a6 -> 521b9fb0cc)

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_bootstrap/release-arm-check_bootstrap in repository toolchain/ci/base-artifacts. from 53e277b6a6 14: onsuccess: #137: 1: Success after binutils/gcc: 13 commits new 521b9fb0cc 15: onsuccess: #138: 1: Success after binutils/gcc: 8 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 1720 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2704 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 51976 -> 51560 bytes 04-build_abe-bootstrap/console.log.xz | Bin 461260 -> 466552 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3888 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2532 -> 2348 bytes 07-check_regression/console.log.xz | Bin 4288 -> 4744 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 29 +- 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 | 19 +- sumfiles/g++.log.xz | Bin 2851260 -> 2850752 bytes sumfiles/g++.sum | 126 +- sumfiles/gcc.log.xz | Bin 2459756 -> 2455212 bytes sumfiles/gcc.sum | 4934 +++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 949364 -> 947636 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2304 -> 2300 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 206652 -> 206920 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2724 -> 2724 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 470460 -> 444596 bytes sumfiles/libstdc++.sum | 10 +- 30 files changed, 2606 insertions(+), 2612 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_debug updated (930769b422 -> 64b64828c4)

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/release-arm-bootstrap_debug in repository toolchain/ci/base-artifacts. from 930769b422 14: onsuccess: #137: 2: Success after binutils/gcc: 13 commits new 64b64828c4 15: onsuccess: #138: 2: Success after binutils/gcc: 8 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 1688 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 53224 -> 51528 bytes 05-build_abe-bootstrap_debug/console.log.xz | Bin 461900 -> 461272 bytes 06-check_regression/console.log.xz | Bin 2236 -> 2796 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 | 19 ++++++++++--------- 12 files changed, 16 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (0daa36de3f -> 5f740c78c1)

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 0daa36de3f 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] discards d84dbfc90b 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] discards 61181a0d65 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] discards e11c5dd9c1 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] discards 1915c31028 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits discards 1d4caea48e 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits discards 195df60e5e 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits discards 6049ec773a 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits discards 5f43e84a95 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits discards 35bfddd1b9 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits discards a0ff9079ca 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits discards 00f37837e0 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits discards d84aaccda7 117: onsuccess: #2034: 1: Success after binutils: 2 commits discards 2e38bd8660 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits discards 5b3807caab 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits discards d2995299a8 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits discards fca37ef769 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits discards 660413227c 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits discards 86a59839ba 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits discards 70f78f42bb 110: onsuccess: #2027: 1: Success after gcc: 5 commits discards 8bcc4fc1f3 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits discards 45df73c9b5 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits discards b0567bc643 107: onsuccess: #2024: 1: Success after gcc: 3 commits discards 666a057af4 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits discards ff628fb505 105: onsuccess: #2022: 1: Success after gcc: 4 commits discards 9b46339a33 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards 059b8d1360 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards 970ce71f2d 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] discards 9e0f47ca44 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards fe24636272 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards b499303f15 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards 0c156ffc45 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards e6ed07a0c7 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards 5853566c8c 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] discards 03fa3d9424 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] discards 4b7c8c33cb 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards a20198cd3c 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] discards b7f5f2f693 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards cc24a19dd4 91: onsuccess: 1: Success after gcc: Daily bump. discards 89cc730c2f 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards ede56da734 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards fe7be717f5 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards 690535218a 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards 92e2fdcadf 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards 28298dafdb 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards 4df2e793cd 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards 398f5db1cd 83: onsuccess: 1: Success after gcc: 8 commits discards 08af9004ba 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards fc811521a9 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards 92d030d93b 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards 7219ba2830 79: onsuccess: 1: Successful build after gcc: Daily bump. discards e1d1b1980c 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards e4a60680b4 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 05f897a2d3 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards d64d684080 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 0281dd607f 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards 75a7b795f1 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards 48c1f268f3 72: onsuccess: 1: Successful build after gcc: 2 commits discards cc71b9ab48 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 1f748d7e39 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards e6307eaae0 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 7522114864 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 99dde8191c 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 4a6cc09f30 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 8a1d53db9f 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards ff47e9d0ce 64: onsuccess: 1: Successful build after gcc: 5 commits discards bc2dbdeed6 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 238037393b 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards bb2d3dabeb 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits discards 6b100e2f3f 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 12d656ec84 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits discards 219c4f2d5a 58: onsuccess: 1: Successful build after binutils: 2 commits discards 66b37fe1fe 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards 3fefc5353a 56: onsuccess: 1: Successful build after gcc: Daily bump. discards 203004daae 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 6bc12be663 54: onsuccess: 1: Successful build after gcc: 7 commits discards 1b6d31714d 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards ced51ba694 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 3d235afe5c 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 4130feff05 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 8036d2f1c9 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 206cfdb072 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 802544c946 47: onsuccess: 1: Successful build after binutils: 2 commits discards db426a9829 46: onsuccess: 1: Successful build after gcc: Daily bump. discards e5685a5429 45: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 00ab1c4b8c 44: onsuccess: 1: Successful build after gcc: 2 commits discards 41e24d8414 43: onsuccess: 1: Successful build after gcc: Daily bump. discards 96ef3fea4b 42: onsuccess: 1: Successful build after binutils: Automatic [...] discards cc392f8f96 41: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 2f936400ce 40: onsuccess: 1: Successful build after gcc: 2 commits discards 6c20f38ed0 39: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 0fc90a2877 38: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 360169de83 37: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards d6bfba3fbb 36: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 5e2e64702c 35: onsuccess: 1: Successful build after gcc: 4 commits discards 9f44539b3a 34: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 2d8b670a33 33: onsuccess: 1: Successful build after gcc: 10 commits discards 0f3499df64 32: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards 78999999a7 31: onsuccess: 1: Successful build after gcc: 2 commits discards 992232a776 30: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 54358d6918 29: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 8e6a7688f0 29: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 37f5e4d926 30: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 6132e4ea51 31: onsuccess: 1: Successful build after gcc: 2 commits new de0b13e3c3 32: onsuccess: 1: Successful build after binutils/gcc: 9 commits new 8c0f44e9d0 33: onsuccess: 1: Successful build after gcc: 10 commits new c67bb1da1e 34: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 08bb56e189 35: onsuccess: 1: Successful build after gcc: 4 commits new 7df1f2fcbe 36: onsuccess: 1: Successful build after binutils/gcc: 11 commits new fb2814b45f 37: onsuccess: 1: Successful build after binutils/gcc: 12 commits new c0de4d9dfc 38: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 3383758043 39: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 5f9dd9363c 40: onsuccess: 1: Successful build after gcc: 2 commits new 3b638131ff 41: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 6dcfabf86a 42: onsuccess: 1: Successful build after binutils: Automatic [...] new cc0ea86df2 43: onsuccess: 1: Successful build after gcc: Daily bump. new c0b0dd5caf 44: onsuccess: 1: Successful build after gcc: 2 commits new 7b3db3e508 45: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 82310a0f61 46: onsuccess: 1: Successful build after gcc: Daily bump. new 428dc65a4f 47: onsuccess: 1: Successful build after binutils: 2 commits new 796413d55f 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 67b69f376b 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 3a7c187fda 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 4c23f8e33f 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 273ccdf3df 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 4b8786cd32 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new d74ce299bd 54: onsuccess: 1: Successful build after gcc: 7 commits new 349ec6fbd2 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 7522ce189e 56: onsuccess: 1: Successful build after gcc: Daily bump. new 4c465af4d9 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits new 6f4c9c80ef 58: onsuccess: 1: Successful build after binutils: 2 commits new ee51441798 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits new beb730478b 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 06a8b3aea8 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits new 3c0e6bfc60 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 19c5768086 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits new f5ac7442a1 64: onsuccess: 1: Successful build after gcc: 5 commits new b0ab9d5219 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 00dc4589aa 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new b5953850f7 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 9c5c3cea40 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 845d6d1aa1 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] new c524646b7d 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new 2ed3288c7f 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 7df8fd0a9c 72: onsuccess: 1: Successful build after gcc: 2 commits new 9c59b29489 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 6994339b08 74: onsuccess: 1: Successful build after binutils: Automatic [...] new 2abe13a462 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 172d157738 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 6fbeac0965 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 8b56ae876b 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 962fa32b63 79: onsuccess: 1: Successful build after gcc: Daily bump. new 7189c965ae 80: onsuccess: 1: Success after binutils/gcc: 14 commits new 3aa513bcfa 81: onsuccess: 1: Success after binutils/gcc: 27 commits new efd5e6a217 82: onsuccess: 1: Success after binutils/gcc: 10 commits new 36a5276082 83: onsuccess: 1: Success after gcc: 8 commits new 129d26a705 84: onsuccess: 1: Success after binutils/gcc: 9 commits new c27d768649 85: onsuccess: 1: Success after binutils/gcc: 9 commits new 2bfd611b4c 86: onsuccess: 1: Success after binutils/gcc: 13 commits new 3804899bfb 87: onsuccess: 1: Success after binutils/gcc: 4 commits new 9c13f329f5 88: onsuccess: 1: Success after binutils/gcc: 16 commits new 6b7c786b86 89: onsuccess: 1: Success after binutils/gcc: 9 commits new 3a72296571 90: onsuccess: 1: Success after binutils/gcc: 6 commits new 023b4c2a84 91: onsuccess: 1: Success after gcc: Daily bump. new c88a77b5d3 92: onsuccess: #1965: 1: Success after gcc: 2 commits new 6354c6cb3b 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] new b6bc3da6b1 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new 47218a26e4 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] new 4575046e16 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] new 2edac7c820 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new 6aa085de27 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new 8db248d8c5 99: onsuccess: #1974: 1: Success after gcc: 14 commits new e173864f26 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new 6b10a1e2b2 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new cf52846bf4 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] new 4482f46649 103: onsuccess: #2020: 1: Success after gcc: 2 commits new e76574951c 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new 3cd128722b 105: onsuccess: #2022: 1: Success after gcc: 4 commits new 5c9a8d7c76 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits new 70e089eca5 107: onsuccess: #2024: 1: Success after gcc: 3 commits new cd2424ed03 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits new 9acfe1c987 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits new 4ed1c42af1 110: onsuccess: #2027: 1: Success after gcc: 5 commits new 08e53a7732 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits new ebcd32be66 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits new 3dab632f59 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits new a0a2ab0d70 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits new 89f2668e6c 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits new 32ff918d0c 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits new 34a8c801b4 117: onsuccess: #2034: 1: Success after binutils: 2 commits new 22656ecd49 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits new a2cc6aea8d 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits new 7d3fe0afec 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits new 9e543abc15 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits new 69821145cb 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits new 624841d271 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits new 18d4d5c4df 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits new 9ea98c3fcc 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits new aae077ff8d 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] new 2b21342394 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] new 52ea879e3c 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] new 9937e6d092 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] new 5f740c78c1 130: onsuccess: #2049: 1: Success after gcc: 9 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (0daa36de3f) \ 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 1744 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2712 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 37676 -> 39012 bytes 04-build_abe-gcc/console.log.xz | Bin 212548 -> 214896 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3860 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2544 -> 2768 bytes 07-check_regression/console.log.xz | Bin 4788 -> 5552 bytes 07-check_regression/mail-body.txt | 27 - 07-check_regression/results.compare | 31 +- 07-check_regression/results.compare2 | 263 +- 08-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- sumfiles/g++.log.xz | Bin 3596980 -> 3566184 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 3106092 -> 3132112 bytes sumfiles/gcc.sum | 5082 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1039776 -> 1043996 bytes sumfiles/gfortran.sum | 272 +- sumfiles/libatomic.log.xz | Bin 2192 -> 2192 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207128 -> 207268 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2540 -> 2540 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 451964 -> 436520 bytes sumfiles/libstdc++.sum | 10 +- 31 files changed, 3160 insertions(+), 2788 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (67fdf9162b -> 6fcff0e2c4)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. from 67fdf9162b 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 6fcff0e2c4 50: onsuccess: #523: 1: Success after binutils/gcc/linux/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 1748 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 52656 -> 52096 bytes 04-build_abe-gcc/console.log.xz | Bin 234768 -> 234744 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8688 -> 8816 bytes 07-build_abe-glibc/console.log.xz | Bin 232416 -> 232372 bytes 08-build_abe-gdb/console.log.xz | Bin 49188 -> 50160 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3816 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2592 -> 2048 bytes 11-check_regression/console.log.xz | Bin 19528 -> 20752 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 60 +- 11-check_regression/mail-body.txt | 218 +- 11-check_regression/results.compare | 108 +- 11-check_regression/results.compare2 | 1112 ++- 11-check_regression/results.regressions | 112 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 220 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 112 +- sumfiles/gdb.log.xz | Bin 1726808 -> 1685144 bytes sumfiles/gdb.sum | 11773 ++++++++++++++++++++++-------- 29 files changed, 10219 insertions(+), 3544 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022