Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap updated (c9521bc7a0 -> 648e07f959)

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-arm-bootstrap in repository toolchain/ci/base-artifacts. discards c9521bc7a0 161: onsuccess: #1566: 2: Success after binutils/gcc: 2 commits discards 2de2f6066d 160: onsuccess: #1565: 2: Success after binutils/gcc: 15 commits discards 29fd70da37 159: onsuccess: #1564: 2: Success after binutils/gcc: 11 commits discards c1dbb4e875 158: onsuccess: #1563: 2: Success after binutils/gcc: 2 commits discards 37f7a3da24 157: onsuccess: #1562: 2: Success after gcc: 2 commits discards 01205ddd8a 156: onsuccess: #1561: 2: Success after gcc: 2 commits discards 2e70f1f217 155: onsuccess: #1560: 2: Success after gcc: 3 commits discards f3887f593f 154: onsuccess: #1559: 2: Success after binutils/gcc: 12 commits discards 7987b737b7 153: onsuccess: #1558: 2: Success after binutils/gcc: 12 commits discards 4867669139 152: onsuccess: #1557: 2: Success after binutils/gcc: 12 commits discards 81a852fb32 151: onsuccess: #1556: 2: Success after binutils: 12 commits discards 42e50baa27 150: onsuccess: #1555: 2: Success after binutils/gcc: 14 commits discards 1fb07c6809 149: onsuccess: #1554: 2: Success after binutils/gcc: 15 commits discards 6bd2c665dc 148: onsuccess: #1553: 2: Success after binutils/gcc: 32 commits discards c0bf13e180 147: onsuccess: #1552: 1: Success after gcc: 2 commits discards d88a82677c 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 commits discards 8e8274f62a 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits discards 37cbbd4ccf 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits discards 0f801da1e2 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits discards e497e7663f 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits discards 79fd60db2e 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits discards ca23786e5d 140: onsuccess: #1545: 1: Success after gcc: 7 commits discards 7b135642d5 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits discards a1acfafe3b 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits discards b4e609c3a4 137: onsuccess: #1542: 1: Success after gcc: 4 commits discards c3241d4c94 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] discards 8a422d2d0f 135: force: #1540: 2: Success after gcc: 23 commits discards 16bad591c0 134: onsuccess: #1538: 2: Success after binutils: 2 commits discards 67a2f50978 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits discards 6af019b894 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits discards 227804fd0f 131: onsuccess: #1534: 2: Success after gcc: 9 commits discards cc285bd161 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] discards ab62ec4d7d 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits discards f96009b9ec 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 85c5f61fe0 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards 16a7502ef6 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards 6b802a3183 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards 62d3d34f26 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards 1475d6bf40 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards a9b2a63207 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards 4a3ef36387 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards a014648bee 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards 70afae9108 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards 805f98a0d3 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards 9cd08b874f 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards 0c0fce5d75 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards d58374f510 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards 79acadaa57 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 3014964907 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards bd19ef31f2 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards e363413c7d 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards 4a4393b3bf 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards a9dc0f981d 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards e651a7e53e 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 09a926fab5 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards e005aa9108 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards d6d90a6b89 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards 7a059f7734 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards 0899792e54 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 735eb8dc93 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards 442c81b74a 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards 835cea3e33 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards ddd1820217 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards 545dbbd213 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards 197017738d 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 7c6a02b086 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards e249e81c7e 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards 4874ca8536 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards d71f073562 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards d7650bc2e7 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards ae70d7f07b 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards f87c86867f 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards 4a809bc6e4 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards 09bc1f44be 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards 6a8f74609a 87: onsuccess: 2: Success after gcc: 4 commits discards 75850f42ef 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards 5d6d4e075d 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 1f4c4636e3 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 5a43e3042b 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 95591ee22e 82: onsuccess: 1: Successful build after gcc: 3 commits discards 245f7cf6c0 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 83df2da742 80: force: 2: Successful build after gcc: 14 commits discards c64e75dd7d 79: onsuccess: 2: Successful build after binutils: 5 commits discards 3be60eb1e9 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards 0f327a0fa4 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards c0f564ad91 76: onsuccess: 2: Successful build after gcc: 12 commits discards 39e56c4dc2 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards a1c53d15d3 74: onsuccess: 2: Successful build after baseline build: no [...] discards 761a8bbdf2 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 1f06bce12d 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 86e99085a3 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 1020e7095f 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards ca6cf57249 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 737fc8b36a 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards a03de94c71 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards e8e82662ea 66: onsuccess: 2: Successful build after gcc: 9 commits discards 7efb24a50a 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 9074656a0a 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 6a46e58cf0 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards e73d93a145 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards f9d1a765e8 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new 16c01062cb 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new 0f934c2a0a 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 06d6f69ecc 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 877974f396 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ae0e28f702 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new e43f11d642 66: onsuccess: 2: Successful build after gcc: 9 commits new 4ff1009081 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 16ae2bcf11 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 477eb41713 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new d7fb9c6ba2 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 3a6e81211c 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new cfdfd203e5 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 2bb802b183 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 0faf05200e 74: onsuccess: 2: Successful build after baseline build: no [...] new 156dbd5aa4 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 6530357d04 76: onsuccess: 2: Successful build after gcc: 12 commits new cac0dc71eb 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new cc82f61a19 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new 4d69d1abee 79: onsuccess: 2: Successful build after binutils: 5 commits new 22f82f4b70 80: force: 2: Successful build after gcc: 14 commits new d401b8b201 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 5b7e3bf6cd 82: onsuccess: 1: Successful build after gcc: 3 commits new 6a47f80743 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new a7e286ca39 84: onsuccess: 2: Success after binutils/gcc: 15 commits new 11370c5afa 85: onsuccess: 2: Success after binutils/gcc: 25 commits new f2e6d7c6e8 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 435df7710e 87: onsuccess: 2: Success after gcc: 4 commits new 77a8ecec0f 88: onsuccess: 2: Success after binutils/gcc: 25 commits new 15e2b61df5 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 3eb79fd984 90: onsuccess: 2: Success after binutils/gcc: 16 commits new 5f10e9a913 91: onsuccess: 2: Success after binutils/gcc: 7 commits new 9454ea9627 92: onsuccess: 2: Success after binutils/gcc: 9 commits new a97ca9201b 93: onsuccess: 2: Success after binutils/gcc: 3 commits new bcbc03e94c 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new 0dbbd34c94 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new 9d44eec807 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 446cc39b8f 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new 0d462a89ab 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new 1ab3be7b3a 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new 98ed7d4a13 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 77c1246f08 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new 42aecd1acd 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new a1a82e4e0a 103: onsuccess: #1504: 2: Success after gcc: 2 commits new f317b12308 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new d3a1349a31 105: onsuccess: #1506: 2: Success after gcc: 2 commits new b09bd179f5 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 48806cb592 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new d20f5a4df9 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new d89a89be15 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new 6fe1884b0f 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new 5c4f765ff3 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new 2ff8afb66c 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new dc6f2833e5 113: onsuccess: #1514: 2: Success after gcc: 5 commits new e5f924403d 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new 574c63206a 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new af230e1ab2 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new 50331b92f7 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new d6337214d6 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new b9631f9002 119: onsuccess: #1520: 2: Success after binutils: 8 commits new a6c4cd4e70 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new 3bc4ff2a89 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new ce0da8a83c 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new 506e579f13 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new 3d9bf1a76e 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new dfed6dd515 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new 680f8a0f58 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new d947ebb87b 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new 46b57f35de 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new ee602eccb9 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits new 8073ea944b 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] new 09858b59c2 131: onsuccess: #1534: 2: Success after gcc: 9 commits new 15a1ae721e 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits new d1c3d54120 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits new 781d07e63f 134: onsuccess: #1538: 2: Success after binutils: 2 commits new c660f987c5 135: force: #1540: 2: Success after gcc: 23 commits new 493a267b54 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] new fcd64f0ab7 137: onsuccess: #1542: 1: Success after gcc: 4 commits new 26aa35a16f 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits new 7d7c6b77d3 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits new 5dc9ce7e1f 140: onsuccess: #1545: 1: Success after gcc: 7 commits new 87d49e29f7 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits new fb17ef4c40 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits new 61893b77ad 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits new 39f997097d 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits new e9cf032ac6 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits new 609f403c51 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 commits new b8ea717265 147: onsuccess: #1552: 1: Success after gcc: 2 commits new 38d39ab756 148: onsuccess: #1553: 2: Success after binutils/gcc: 32 commits new 6943e4f093 149: onsuccess: #1554: 2: Success after binutils/gcc: 15 commits new a5ccdb0d12 150: onsuccess: #1555: 2: Success after binutils/gcc: 14 commits new 06197e2aba 151: onsuccess: #1556: 2: Success after binutils: 12 commits new 20e3ca8698 152: onsuccess: #1557: 2: Success after binutils/gcc: 12 commits new 5abd6298df 153: onsuccess: #1558: 2: Success after binutils/gcc: 12 commits new 69768896dd 154: onsuccess: #1559: 2: Success after binutils/gcc: 12 commits new b58c859a13 155: onsuccess: #1560: 2: Success after gcc: 3 commits new 8d919cf920 156: onsuccess: #1561: 2: Success after gcc: 2 commits new b3aba7e05b 157: onsuccess: #1562: 2: Success after gcc: 2 commits new ef78e28435 158: onsuccess: #1563: 2: Success after binutils/gcc: 2 commits new 2da06095da 159: onsuccess: #1564: 2: Success after binutils/gcc: 11 commits new 6ad39569b7 160: onsuccess: #1565: 2: Success after binutils/gcc: 15 commits new ea1bdcfbaa 161: onsuccess: #1566: 2: Success after binutils/gcc: 2 commits new 648e07f959 162: onsuccess: #1567: 2: Success after binutils/gcc: 5 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (c9521bc7a0) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] 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 -> 1656 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 52464 -> 51952 bytes 05-build_abe-bootstrap/console.log.xz | Bin 466508 -> 464788 bytes 06-check_regression/console.log.xz | Bin 2548 -> 2760 bytes 07-update_baseline/console.log | 40 +++++++++++++++++----------------- 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 ++++++++--------- 13 files changed, 36 insertions(+), 36 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_check_binutils/master-aarch64 updated (4891646b1d -> ee3772a636)

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_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. from 4891646b1d 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] new ee3772a636 53: onsuccess: #567: 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 1696 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 37932 -> 38916 bytes 04-build_abe-gcc/console.log.xz | Bin 212836 -> 214368 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8960 -> 8420 bytes 07-build_abe-glibc/console.log.xz | Bin 239852 -> 241712 bytes 08-build_abe-gdb/console.log.xz | Bin 37716 -> 38192 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3852 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2048 -> 2568 bytes 11-check_regression/console.log.xz | Bin 5748 -> 5832 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +-- sumfiles/binutils.log.xz | Bin 58576 -> 58468 bytes sumfiles/binutils.sum | 60 ++--- sumfiles/gas.log.xz | Bin 81100 -> 81112 bytes sumfiles/gas.sum | 268 +++++++++++----------- sumfiles/ld.log.xz | Bin 121420 -> 121200 bytes sumfiles/ld.sum | 342 ++++++++++++++--------------- 28 files changed, 367 insertions(+), 367 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_kernel/gnu-master-arm-mainline-defconfig updated (9bac876ccf -> 9ee7b9c5c4)

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-mainline-defconfig in repository toolchain/ci/base-artifacts. from 9bac876ccf 11: onsuccess: #449: boot: Success after binutils/gcc/linux/ [...] new 9ee7b9c5c4 12: onsuccess: #450: boot: Success after binutils/gcc/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1704 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30092 -> 30468 bytes 04-build_abe-stage1/console.log.xz | Bin 90736 -> 91336 bytes 05-build_abe-qemu/console.log.xz | Bin 32380 -> 31684 bytes 06-build_linux/console.log.xz | Bin 5128 -> 5060 bytes 07-boot_linux/console.log.xz | Bin 5844 -> 5852 bytes 08-check_regression/console.log.xz | Bin 4492 -> 4428 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 18 files changed, 28 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/master-aarch64-check_bootstrap updated (a7543dbc5e -> fb939b5b25)

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/master-aarch64-check_bootstrap in repository toolchain/ci/base-artifacts. from a7543dbc5e 51: onsuccess: #586: 1: Success after binutils/gcc: 6 commits new fb939b5b25 52: onsuccess: #587: 1: Success after binutils/gcc: 31 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 1732 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 37692 -> 38828 bytes 04-build_abe-bootstrap/console.log.xz | Bin 269200 -> 271340 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3820 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2436 -> 2876 bytes 07-check_regression/console.log.xz | Bin 5756 -> 5368 bytes 07-check_regression/extra-bisect-params | 1 - 07-check_regression/fails.sum | 7 - 07-check_regression/mail-body.txt | 49 +- 07-check_regression/results.compare | 42 +- 07-check_regression/results.compare2 | 85 +- 07-check_regression/results.regressions | 52 - 08-update_baseline/console.log | 9 - dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 51 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 52 - sumfiles/g++.log.xz | Bin 3657600 -> 3665756 bytes sumfiles/g++.sum | 148 +- sumfiles/gcc.log.xz | Bin 3207888 -> 3223760 bytes sumfiles/gcc.sum | 5070 +++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 1085028 -> 1090360 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2348 -> 2352 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213884 -> 213564 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2724 -> 2724 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 466836 -> 467728 bytes sumfiles/libstdc++.sum | 10 +- 36 files changed, 2713 insertions(+), 2959 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_gcc_bootstrap/master-aarch64-bootstrap updated (a5064c9491 -> deb90ab5d2)

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 in repository toolchain/ci/base-artifacts. discards a5064c9491 156: onsuccess: #1583: 2: Success after binutils/gcc: 2 commits discards 34bf312fab 155: onsuccess: #1582: 2: Success after binutils/gcc: 15 commits discards 41b2efd5d6 154: onsuccess: #1581: 2: Success after binutils/gcc: 11 commits discards 4ff5741477 153: onsuccess: #1580: 2: Success after binutils/gcc: 2 commits discards 4612c44eff 152: onsuccess: #1579: 2: Success after gcc: 2 commits discards ed86f52552 151: onsuccess: #1578: 2: Success after gcc: 2 commits discards 3632171a12 150: onsuccess: #1577: 2: Success after gcc: 3 commits discards 19874b6a1b 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 commits discards a60ef20c14 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits discards f9c6823e53 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits discards 133762c37c 146: onsuccess: #1573: 2: Success after binutils: 7 commits discards ba3a324c39 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits discards 9a44fa2c5b 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits discards a6a5c601d5 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits discards 40a66d6a04 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] discards 5d30816495 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits discards e08a76399e 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits discards f14ce9014b 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards 474c950d13 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] discards b956fd509b 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards 530ee89d19 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards 3c48bacbcb 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards 3188d3254b 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards db71d0e469 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards 959f55c932 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards 5a4d008e73 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards 9985739328 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards e84a64246b 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards 53830d380f 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards 00c66ba9a9 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards 5028d6c4d8 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards 27c25668ba 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards 32b32b5e74 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards 925ed3b7c4 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards 2c88ff6dba 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards e95f6b8e21 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards eed16b55ca 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards 8ba22f6d90 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards f9553d9f9b 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 023dd59954 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 0ab9b414de 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards b23835394f 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards d11979c189 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 2e3177cd50 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards 5427c205f4 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards d31a436b97 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards b8d0715ad7 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 2c2a5c3f5e 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 75c2243cde 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards 1c4f9c47bd 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 4c3f4da38a 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 17c8f564cf 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards c125bb1686 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards ccf99a1890 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards f876a1b751 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards c6f7cc5bf1 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards 82b5c863d7 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 818f8cdd23 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards a5e3b9d9e8 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 40c8ed80ba 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 540cad5fdf 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards 3933dd4eba 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards fc70fdda5d 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 0a228d838c 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 244c8c3190 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 242c8e60bb 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards a18773fd65 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards d8b82c983f 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 1693f6b625 88: onsuccess: 1: Success after gcc: 20 commits discards 91bdd27ccd 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards d545ffaf2b 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards 095fd49f0d 85: onsuccess: 2: Success after binutils: 4 commits discards 37af5167ee 84: onsuccess: 2: Success after gcc: 9 commits discards 3d0f269bf2 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 3996d2baaf 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 3e1a3416cf 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 980ecf0a1e 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 801e7b0ea7 79: onsuccess: 1: Successful build after gcc: 3 commits discards 7a264149d2 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 7934789539 77: force: 2: Successful build after gcc: 32 commits discards 3c8c524e43 76: onsuccess: 2: Successful build after binutils: 10 commits discards bc7e1483c6 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards bebdcc175b 74: onsuccess: 2: Successful build after gcc: 13 commits discards 9fa27d3b86 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 3ba1cca418 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards f4cef4f41a 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 4c4ca49e34 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards a4a8e14a26 69: onsuccess: 2: Successful build after baseline build: no [...] discards 2ebbe6e846 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards e117f81097 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards a376725ae7 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards ad2fa447d3 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 1aa884d671 64: onsuccess: 2: Successful build after gcc: 7 commits discards 07aa17c631 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 203725763d 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 69e36aa137 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 7e54dda585 60: onsuccess: 1: Successful build after gcc: 15 commits discards 6ffe8a7324 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 0f1337ced6 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards 34b836b439 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards f103ec288b 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new c025a7e444 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 87a511726f 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 9ea0060956 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new 508282512a 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 27763baca6 60: onsuccess: 1: Successful build after gcc: 15 commits new 181d491fad 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 90e93346f3 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 71cdb8aa3b 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 773d174335 64: onsuccess: 2: Successful build after gcc: 7 commits new a0836fb1b8 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 28f49a0995 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new e4f05af88f 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 23d61f05d9 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 7a11f856d8 69: onsuccess: 2: Successful build after baseline build: no [...] new bd82d065e0 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new b227b1d043 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new d6c3fcb7c7 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 7cc8891053 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 3c7de92275 74: onsuccess: 2: Successful build after gcc: 13 commits new 4289b2aad2 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 8a4c495915 76: onsuccess: 2: Successful build after binutils: 10 commits new 34d757afbf 77: force: 2: Successful build after gcc: 32 commits new 929fbaa0fe 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new d5622121a0 79: onsuccess: 1: Successful build after gcc: 3 commits new ca18d6b388 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new e876b84b1d 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 7a4912fec6 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 60aba6d8eb 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 300593e2d0 84: onsuccess: 2: Success after gcc: 9 commits new db0a84e2f6 85: onsuccess: 2: Success after binutils: 4 commits new adbc007c8c 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new a17cadbcc8 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new 54ed8ab4bb 88: onsuccess: 1: Success after gcc: 20 commits new 7c2f8f8602 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 962dac597f 90: onsuccess: #1472: 2: Success after gcc: 2 commits new c789d56a83 91: onsuccess: #1473: 2: Success after gcc: 2 commits new d4dc6232f3 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 264934e218 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new f6fb579842 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new ccbfe6acaa 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 2963174b2b 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 895e43c3bc 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 69b1879cf3 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 3505283da4 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new e22a081a57 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new b530bb0ca0 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new 8f15b629bc 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 6b413539f2 103: onsuccess: #1524: 2: Success after gcc: 2 commits new e2a53a3d9f 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 7edd081a3d 105: onsuccess: #1526: 2: Success after gcc: 2 commits new f555c96fe1 106: onsuccess: #1527: 2: Success after gcc: 2 commits new d19bf1ddd1 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new dbdaa87b07 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new b84052858b 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 0e63da8d03 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new a9c95f8e3e 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 58092943eb 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 56d197e275 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new f48fc45d83 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 32915688ad 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 4082906420 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 48068e91a5 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new f20020ff48 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 8f918e0da4 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new 0034417c61 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new eb303006dd 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new 851e6e9afa 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 6b5e4ba7ed 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 7fdd1811f5 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new 7fbbffdcd3 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new d480968fab 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new 0f88f310c5 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new 7fe548a6bc 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new 16cbab80a9 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new 836b138d1e 130: onsuccess: #1554: 2: Success after gcc: 9 commits new b865bc7784 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new 274b57ae2d 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new 7e6689913f 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new 41d0a40589 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new bb7dba196e 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new d814c622bc 136: onsuccess: #1561: 2: Success after binutils: 3 commits new e4d4abcfba 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new 8b421e1481 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] new 05e7c3e652 139: onsuccess: #1566: 1: Success after gcc: 5 commits new 1e9bb2550e 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits new c9d0f96de0 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits new e1b813d0bd 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] new 296333ba55 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits new c9b8a3361d 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits new bbf7529698 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits new c34816feb9 146: onsuccess: #1573: 2: Success after binutils: 7 commits new 4e2ce35ba2 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits new eb0bb539a2 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits new 1f8af9bc65 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 commits new d7ec7690c5 150: onsuccess: #1577: 2: Success after gcc: 3 commits new a04c6294dc 151: onsuccess: #1578: 2: Success after gcc: 2 commits new f9dad060c0 152: onsuccess: #1579: 2: Success after gcc: 2 commits new 18414c6111 153: onsuccess: #1580: 2: Success after binutils/gcc: 2 commits new bc98e3f42e 154: onsuccess: #1581: 2: Success after binutils/gcc: 11 commits new 30503d7309 155: onsuccess: #1582: 2: Success after binutils/gcc: 15 commits new a541e8b380 156: onsuccess: #1583: 2: Success after binutils/gcc: 2 commits new deb90ab5d2 157: onsuccess: #1584: 2: Success after binutils/gcc: 5 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (a5064c9491) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1720 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2704 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 38040 -> 38092 bytes 05-build_abe-bootstrap/console.log.xz | Bin 273804 -> 272220 bytes 06-check_regression/console.log.xz | Bin 2544 -> 2788 bytes 07-update_baseline/console.log | 40 +++++++++++++++++----------------- 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 ++++++++--------- 13 files changed, 36 insertions(+), 36 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 (e15e88bf49 -> 5561dc107c)

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 e15e88bf49 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards 25f2164948 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards c59556df9c 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 9d1dc356fe 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 925a8a560b 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 2a5e57ea64 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards fe48e7c890 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 4aff865394 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards 8ad02e3b94 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 5cd0b2f450 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 75f83f74b4 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards aa99bfc610 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 0dc460b26c 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 35caa48fcd 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 72fe913677 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards b2a329cfb2 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 8475f08899 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 819fb1c12d 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 7bafe31115 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 76126432a6 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 3d7f91d9f3 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards c5cefc6e94 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards bc1ec4c257 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 6ac4a37f71 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 56144f788d 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 2d18f90967 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards d38afdd9d1 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 4e5335cf78 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards d7f2ee2c71 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards b7d055c6f5 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 22d1c5eec8 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 2567b2ca5b 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 5b452361ba 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 03f3473f00 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 50bc5185c7 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 36f8fb7497 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards f3a0b8b8b6 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 23c24cc36e 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards a5e88d6eb2 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards c27b385a25 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 4285f47b30 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 12ee00998f 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards f928a27599 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 730a1ce55e 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards e36111d369 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 44ff92f8c6 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 0fbdb67eed 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 41f6fa258f 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 57e5f85fb7 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards ba11a374a0 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 66b5a9f6f2 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards a4f70a0634 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards a7a46cacdd 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards a7f8531766 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 5291ee5c0b 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 30de8ab6fc 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 31855f1630 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 87ffb2d6ca 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards f51e82156c 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 94a2e2a826 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards b3a2bc3dc4 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 4f3721f78e 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards cc561b533c 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 275b39ece5 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 3552225678 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 10ebe55e36 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 286de4b607 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards d3f385a531 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 0d0cbbe0db 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 0c16a7ff32 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards dd062f5b07 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 0e736ffff5 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards f160579397 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 2f0c757c49 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 073a7652f4 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 2f35e4f77e 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 984ca5fb8c 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 6b354ef39b 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards dafe4eb5a4 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards cd702b528b 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 82819dc76a 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d2a98f0fc3 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bedd8bcc18 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards faac05f0f4 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards edaabc8925 74: onsuccess: 1: Successful build after linux: 44 commits discards f9241ce0d6 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 28cd5942dd 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ee5858bb4c 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 1d1408cfff 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards e666bc676a 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards b38479dac8 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6a488f28b8 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 260296f590 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 55a0eb4f62 65: onsuccess: 1: Successful build after gcc: 4 commits discards 51b7aeb704 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards df657412f9 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b26aea5b43 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards ad5d390a5c 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards b0ee4d416e 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 02c6301c06 59: onsuccess: 1: Successful build after glibc: 2 commits discards 404b50d6e5 58: onsuccess: 1: Successful build after binutils: 2 commits new f3e6a9f700 58: onsuccess: 1: Successful build after binutils: 2 commits new 70a9c09306 59: onsuccess: 1: Successful build after glibc: 2 commits new c6b3e4d39a 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new b0b3e05670 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new a9641cb4a6 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new f9e37a679a 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 22081ddc61 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 90993edc03 65: onsuccess: 1: Successful build after gcc: 4 commits new f1195d6b66 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4cc05c2a6e 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8e8d0d088e 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 169d0eb5ef 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 2452a1aea4 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 5f7dceff80 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 32d8906bde 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 610b36eab7 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 7034cd1fd4 74: onsuccess: 1: Successful build after linux: 44 commits new e5e97be36d 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 65f7838c73 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 4633a41a03 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5071cd1da2 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 9c86f60d07 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 06469062ff 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 59a33b3ac2 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 488cd429b2 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 0f34f0c64e 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 0fdc820a1e 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 5877ab06ae 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new b2b14ef501 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 107df4093b 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 16e9b61638 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new fe4090ac83 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 991f6ec6ff 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new c3f7ef0c0d 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new b4db25a8b3 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 49a7c55995 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 14c5960623 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 92289b5f5f 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 29f865ff7a 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new ce1114733a 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new d38a5af1c6 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 31b427d2dc 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new b1ed3b0b61 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new fb3f7ad00a 101: onsuccess: #1693: 1: Success after glibc: 14 commits new c4d790673c 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new dd044e7a36 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 709351081b 104: onsuccess: #1697: 1: Success after gcc: 4 commits new d31dcb32f7 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new a7e1c1fd5b 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new e3aeba8184 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 7e16e613bc 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 177575c95e 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new fed6e0763d 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 5114f12ccf 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 82d67016e9 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 4feedf520a 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 69c036eb9d 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 6a83afe4e1 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 910405a806 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new b51f649b13 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 2f2abbe83b 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new b4be7a77bf 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 529c5b1075 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 96a8c734fc 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new bdaa81022a 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 9eb56a1e38 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 0f78343226 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 4742e7e4b9 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new d777dd5035 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 206e10aebd 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new e2ea50de6a 128: onsuccess: #1723: 1: Success after linux: 12 commits new d43d8954b9 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 19499d893d 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new cbe5af6c39 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new a1d9e01b9f 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 9beb51d3a8 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 43d315af10 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 3c65758f80 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 68c18d080e 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new c9a5979380 137: onsuccess: #1736: 1: Success after gcc: 5 commits new befcf4ccf3 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 116a01a3ec 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new a92b7e36cc 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new cc02d95ab9 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 72cd0010d8 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 889baf0cc0 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new a706b24f99 144: onsuccess: #1743: 1: Success after glibc: 2 commits new c900e456e9 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new cb8ce74e84 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 714500a00f 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 99d3d2bf2d 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new 280078f9e1 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new a97fccb798 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 514e56f611 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new eae6c43256 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 9039197c8d 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 782c79aa42 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 7428eca236 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 155e291c7e 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 2e792b60f5 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 1d79899b66 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 5561dc107c 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (e15e88bf49) \ 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 1680 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30012 -> 30328 bytes 04-build_abe-stage1/console.log.xz | Bin 90668 -> 91120 bytes 06-build_abe-linux/console.log.xz | Bin 8312 -> 8296 bytes 07-build_abe-glibc/console.log.xz | Bin 234208 -> 233868 bytes 08-build_abe-stage2/console.log.xz | Bin 223748 -> 224956 bytes 09-build_abe-gdb/console.log.xz | Bin 37144 -> 37380 bytes 10-build_abe-qemu/console.log.xz | Bin 31576 -> 31256 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2420 -> 2996 bytes 13-check_regression/console.log.xz | Bin 5564 -> 5296 bytes 13-check_regression/results.compare | 14 - 13-check_regression/results.compare2 | 20 +- 14-update_baseline/console.log | 36 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.xz | Bin 2675652 -> 2692488 bytes sumfiles/g++.sum | 30 +- sumfiles/gcc.log.xz | Bin 2222920 -> 2203488 bytes sumfiles/gcc.sum | 1924 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 891784 -> 883916 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201596 -> 201460 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429304 -> 425872 bytes sumfiles/libstdc++.sum | 2 +- 37 files changed, 1032 insertions(+), 1054 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_profiled_lto updated (6b19954b24 -> 65af247704)

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_profiled_lto in repository toolchain/ci/base-artifacts. from 6b19954b24 50: force: #452: 1: Failure after basepoints/gcc-13-2887-gb0 [...] new 65af247704 51: onsuccess: #453: 1: Success after gcc: 20 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 1748 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 38580 -> 38412 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 83660 -> 80036 bytes 06-check_regression/console.log.xz | Bin 3404 -> 2688 bytes 06-check_regression/jira-body.txt | 2 +- 06-check_regression/mail-body.txt | 20 +- 06-check_regression/mail-subject.txt | 2 +- 06-check_regression/results.regressions | 11 - 06-check_regression/trigger-bisect | 2 - 06-check_regression/trigger-notify | 0 07-update_baseline/console.log | 9 + dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 1061 -------------------- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 20 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 11 - 24 files changed, 42 insertions(+), 1127 deletions(-) delete mode 100644 06-check_regression/results.regressions delete mode 100644 06-check_regression/trigger-bisect delete mode 100644 06-check_regression/trigger-notify delete mode 100644 jenkins/jira-status.draft delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh -- 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_kernel/gnu-master-aarch64-norov-allnoconfig updated (5ae102fce0 -> 7ca9bc5a1d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-norov-allnoconfig in repository toolchain/ci/base-artifacts. from 5ae102fce0 10: onsuccess: #42: boot: Success after binutils/gcc/linux/q [...] new 7ca9bc5a1d 11: onsuccess: #43: 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 1700 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30592 -> 30556 bytes 04-build_abe-stage1/console.log.xz | Bin 73132 -> 72412 bytes 05-build_abe-qemu/console.log.xz | Bin 32796 -> 32340 bytes 06-build_linux/console.log.xz | Bin 4192 -> 4204 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4360 -> 4340 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto updated (b4c1c18191 -> 6b19954b24)

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_profiled_lto in repository toolchain/ci/base-artifacts. from b4c1c18191 49: force: #451: 2: Success after basepoints/gcc-13-2886-g8b [...] new 6b19954b24 50: force: #452: 1: Failure after basepoints/gcc-13-2887-gb0 [...] 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 1692 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 37744 -> 38580 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 524520 -> 83660 bytes 06-check_regression/console.log.xz | Bin 2544 -> 3404 bytes 06-check_regression/jira-body.txt | 2 +- 06-check_regression/mail-body.txt | 15 +- 06-check_regression/mail-subject.txt | 2 +- 06-check_regression/results.regressions | 11 + 06-check_regression/trigger-bisect | 2 + 06-check_regression/trigger-notify | 0 07-update_baseline/console.log | 9 - dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 1061 ++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 15 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 13 +- 24 files changed, 1134 insertions(+), 27 deletions(-) create mode 100644 06-check_regression/results.regressions create mode 100644 06-check_regression/trigger-bisect create mode 100644 06-check_regression/trigger-notify create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/interesting-commits] branch master updated (a52c50f -> a472fc4)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from a52c50f Add entry b04208895fed34171eac6bafb60c90048eb1cb0c from https [...] new a472fc4 Add entry b04208895fed34171eac6bafb60c90048eb1cb0c from https [...] 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: .../master-aarch64-bootstrap_profiled_lto}/build_url | 2 +- .../last_good | 0 .../summary.txt | 0 .../tcwg_gcc_bootstrap/status.txt | 3 +++ 4 files changed, 4 insertions(+), 1 deletion(-) copy gcc/sha1/{953e08fde44a596e4ec2491efd15cd645e1ddc48/tcwg_gcc_bootstrap/master- [...] copy gcc/sha1/b04208895fed34171eac6bafb60c90048eb1cb0c/tcwg_gcc_bootstrap/{master- [...] copy gcc/sha1/b04208895fed34171eac6bafb60c90048eb1cb0c/tcwg_gcc_bootstrap/{master- [...] -- 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