Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-next-allyesconfig updated (2da0363e09 -> 77cfdac707)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-next-allyesconfig in repository toolchain/ci/base-artifacts. from 2da0363e09 14: onsuccess: #676: all: Success after binutils/gcc/qemu: 1 [...] new 77cfdac707 15: onsuccess: #678: 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 1648 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 29864 -> 29948 bytes 04-build_abe-stage1/console.log.xz | Bin 87116 -> 86364 bytes 05-build_abe-qemu/console.log.xz | Bin 29768 -> 31464 bytes 06-build_linux/console.log.xz | Bin 4132 -> 4216 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 3696 -> 4244 bytes 08-check_regression/mail-body.txt | 2 +- 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 | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 33 +++++++++++++++++---------------- results | 2 +- 19 files changed, 28 insertions(+), 27 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap updated (a3311858f0 -> 2c39ab20f0)

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 a3311858f0 162: onsuccess: #1589: 2: Success after binutils/gcc: 11 commits discards 4a320b0c27 161: onsuccess: #1588: 2: Success after binutils/gcc: 10 commits discards 5b0fdc0660 160: onsuccess: #1587: 2: Success after binutils/gcc: 5 commits discards ee644eee02 159: onsuccess: #1586: 2: Success after binutils/gcc: 18 commits discards ab8f490e16 158: onsuccess: #1585: 2: Success after binutils/gcc: 12 commits discards 017672ba89 157: onsuccess: #1584: 2: Success after binutils/gcc: 5 commits discards f7aba427da 156: onsuccess: #1583: 2: Success after binutils/gcc: 2 commits discards 3748036804 155: onsuccess: #1582: 2: Success after binutils/gcc: 15 commits discards 962c7eed6b 154: onsuccess: #1581: 2: Success after binutils/gcc: 11 commits discards d26e71ed08 153: onsuccess: #1580: 2: Success after binutils/gcc: 2 commits discards 490f1fc372 152: onsuccess: #1579: 2: Success after gcc: 2 commits discards fe53696427 151: onsuccess: #1578: 2: Success after gcc: 2 commits discards dcdedf4923 150: onsuccess: #1577: 2: Success after gcc: 3 commits discards 91e755d044 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 commits discards 07b2f3f5d7 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits discards 1c848ae5ec 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits discards bc78c03d9a 146: onsuccess: #1573: 2: Success after binutils: 7 commits discards 15f91b5250 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits discards 29ff3df466 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits discards f8d6401d9c 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits discards b95374992a 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] discards d633295f3c 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits discards 0ad46646d7 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits discards 27ab205282 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards e06a57f545 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] discards 2c952b23d2 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards 0c857618fd 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards a493e7e640 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards f5a3a01745 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards 5e6c2425be 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards a376482f65 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards 795c6ff714 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards c3251ae5fe 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards 27d3fd8501 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards 01f5f4c8b3 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards 9d52cfe9c0 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards 0ae45bd467 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards cffc3bc797 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards 739b10181a 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards 68a5124a51 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards f9a0e498a7 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 7223ad4741 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards 3d8c305be8 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards d75f652f65 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards ccd9e73512 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards c45121d686 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards a9d36f5435 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards e65e34655e 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards 3d76e9132e 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards f3644f1776 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards 6df25e8244 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards c418a8fc57 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 148c65553d 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 1b7dbb8df0 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards ca5be9ec37 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards b4240f5d64 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 5ada7184c6 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards e34810ecba 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards 7da27feccf 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards 2eaab8a87c 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 7eefd2febe 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards f17488a59b 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards fd63eb72da 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards b95ab6fa8f 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards c45b108c00 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 8c1a15d037 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 28a67950ca 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards 3b1b722676 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 3082a7b221 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 63487bf02f 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards ccf3a19069 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 421799f185 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards f0e0a6660b 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 6f7c990179 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 72d68abd5c 88: onsuccess: 1: Success after gcc: 20 commits discards 1806615038 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards 60e459c983 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards e6e90b0af0 85: onsuccess: 2: Success after binutils: 4 commits discards 5f978ee0a8 84: onsuccess: 2: Success after gcc: 9 commits discards e55e1a621a 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 45fe7e3b7e 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 06242a701e 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 62bef17d70 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 996eba55ec 79: onsuccess: 1: Successful build after gcc: 3 commits discards cffe189882 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 20ee781103 77: force: 2: Successful build after gcc: 32 commits discards 03a6407039 76: onsuccess: 2: Successful build after binutils: 10 commits discards c237eb3ea6 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards ffacf0e842 74: onsuccess: 2: Successful build after gcc: 13 commits discards daa73af600 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards e72b08bf2a 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 209c2e7e64 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 62ce22d3e0 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 75eacc7af5 69: onsuccess: 2: Successful build after baseline build: no [...] discards 341f1acd0b 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards f82584269b 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 0058aff82a 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards a83abc9a7a 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 5fa9015d07 64: onsuccess: 2: Successful build after gcc: 7 commits discards ca6427eb97 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 7153d31344 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new b718269ad9 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ce26f27325 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new d48f7c4aa6 64: onsuccess: 2: Successful build after gcc: 7 commits new 9c031d4cd5 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 26d3e68367 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 2aa8789c49 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new b7e490b255 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new f366fb3a7c 69: onsuccess: 2: Successful build after baseline build: no [...] new e8581edca8 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 4945dca0dc 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 068e2b66fd 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new da336a6009 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new a7595aa75d 74: onsuccess: 2: Successful build after gcc: 13 commits new 440bd8284c 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 40d64a4abb 76: onsuccess: 2: Successful build after binutils: 10 commits new af51ad4d4b 77: force: 2: Successful build after gcc: 32 commits new 77ae0a9cab 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 90459f7735 79: onsuccess: 1: Successful build after gcc: 3 commits new 0ce85891b6 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new fa7aee4bdc 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 54876bbbea 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 5bbf39fa49 83: onsuccess: 2: Success after binutils/gcc: 7 commits new e5a7d0ebaf 84: onsuccess: 2: Success after gcc: 9 commits new c061754a20 85: onsuccess: 2: Success after binutils: 4 commits new 024c8aab44 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new 6c5c87ed12 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new d1148b6643 88: onsuccess: 1: Success after gcc: 20 commits new 398085b1b4 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 2a2fc8b07e 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 70ae596f10 91: onsuccess: #1473: 2: Success after gcc: 2 commits new ccc255cf3c 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 5702bf1ed2 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new 1b77762e57 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new 3a17a8ea29 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new bdd533b8ed 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 5e1b6f28cd 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 90ebfb9e58 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 9827d61380 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 013ebc9523 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new e70fde5d31 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new 8c453a8456 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new a9ef05664e 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 895a17f865 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 94020bb7ec 105: onsuccess: #1526: 2: Success after gcc: 2 commits new b1780df18a 106: onsuccess: #1527: 2: Success after gcc: 2 commits new d1532f87f7 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new 2d408ae3b1 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new e440f15ad0 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new aaefe96cfe 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new e0598441c7 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 3fdbfc325e 112: onsuccess: #1533: 2: Success after gcc: 5 commits new c278f2209d 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new 84afc90fd8 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 5d9facde3f 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new bdccec2605 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 3ed3d95330 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new 6b70437286 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new a40d332558 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new 0746bad5b6 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 848966aa4f 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new 4655d079e6 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 2d68b2bd0b 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 7180715638 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new e3df221055 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new b28aa10f8d 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new 2f8cc0febf 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new e28574f23f 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new aaa83d2df3 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new 459a360ef6 130: onsuccess: #1554: 2: Success after gcc: 9 commits new d03696423b 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new ba4d287bce 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new 444f23d7da 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new c2e9edc916 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new f14d126a03 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new b6ee8280b4 136: onsuccess: #1561: 2: Success after binutils: 3 commits new 1d08939e66 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new 1e982121ec 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] new df06a6f1dd 139: onsuccess: #1566: 1: Success after gcc: 5 commits new 896438641c 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits new 1dae9180c4 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits new f84c17098f 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] new f1342c19c6 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits new 683f1fffa4 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits new f167dfd64f 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits new bd88a8e2e9 146: onsuccess: #1573: 2: Success after binutils: 7 commits new 62db3d31ac 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits new f8c384e625 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits new 303c62317f 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 commits new 36a58c0aee 150: onsuccess: #1577: 2: Success after gcc: 3 commits new d091adbb8e 151: onsuccess: #1578: 2: Success after gcc: 2 commits new edac2d14ce 152: onsuccess: #1579: 2: Success after gcc: 2 commits new 1c6e9c0b37 153: onsuccess: #1580: 2: Success after binutils/gcc: 2 commits new c56f745a87 154: onsuccess: #1581: 2: Success after binutils/gcc: 11 commits new dec3171131 155: onsuccess: #1582: 2: Success after binutils/gcc: 15 commits new 30e3f7c4d5 156: onsuccess: #1583: 2: Success after binutils/gcc: 2 commits new f8b2acb73d 157: onsuccess: #1584: 2: Success after binutils/gcc: 5 commits new f047adc9dc 158: onsuccess: #1585: 2: Success after binutils/gcc: 12 commits new dc11a65cf8 159: onsuccess: #1586: 2: Success after binutils/gcc: 18 commits new 31ae64e42d 160: onsuccess: #1587: 2: Success after binutils/gcc: 5 commits new eaf2e69777 161: onsuccess: #1588: 2: Success after binutils/gcc: 10 commits new 2195175d05 162: onsuccess: #1589: 2: Success after binutils/gcc: 11 commits new 2c39ab20f0 163: onsuccess: #1590: 2: Success after binutils/gcc: 15 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 (a3311858f0) \ 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 1728 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 37628 -> 37944 bytes 05-build_abe-bootstrap/console.log.xz | Bin 272792 -> 268932 bytes 06-check_regression/console.log.xz | Bin 3128 -> 2972 bytes 07-update_baseline/console.log | 38 +++++++++++++++++----------------- 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 | 18 ++++++++-------- 13 files changed, 34 insertions(+), 34 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 8 months

[binutils-gdb] branch master updated (8ba677d3560 -> 27e602128ba)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 8ba677d3560 [gdb/symtab] Don't complain about function decls new 27e602128ba gas: NEWS: Mention the T-Head extensions that were recently added 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: gas/NEWS | 5 +++++ 1 file changed, 5 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (f2c848fffb -> 689c09a1e6)

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 f2c848fffb 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards 98c83c1291 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards bd63c3f3ac 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards 7935331b89 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards 4dfdfd64de 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 739f5ebf25 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 738db955d9 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards f6d252c968 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards 96a52fb236 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 3cbe051dc8 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards d28e17d771 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 87ebda3d91 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 1d6fc392b2 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 6e7a3ee799 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards afde9137b3 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 122e109062 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 8b824eb4f9 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards c675cbc154 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards fb9b70e9de 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 1db93cf34c 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 536336db4b 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 4eaa9c5730 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 840a813c92 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 88e1401e84 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 6deb68fd54 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 9401618ec8 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards e2e1a3c2a9 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 421f788183 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards c9fe0195c6 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 1bdf408fb5 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards ed68f415b2 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards b9e1076c77 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 03175318a1 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 2bacb8e1c5 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards ba429452c8 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 39a3371ad9 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards e099c2408b 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 45f8d4f44e 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 4dd7a206bb 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 70caa0ecfe 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 426b74dc4e 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 52d98df9fa 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 39121bb457 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards cc8f029cb7 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 4afd045c83 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 97531635db 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards e2fa023722 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards ff312dbbe8 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards bbb7a76b48 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 9e8b3c2a66 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards d8e8787f17 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards de71a8f997 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 5b89b729eb 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 9e1138302c 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards ae0ec6d099 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 1177425c3c 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 6425a8391e 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 0cfb705a19 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards f695dcf072 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 586ab21c66 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 4489b554a8 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 57208266ab 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards d2b4976c05 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 38dbb2acd1 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 0a1fe02b36 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 9f00223304 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 9784a18677 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 163ce16f60 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards b470bfbc3a 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 7038229704 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards bf26233056 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 0f99751928 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 44638ad445 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards aeb383503a 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 32869c1956 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards e4cc7e43f1 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 43c29eb70a 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 968326432c 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards ad3242200c 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards ae68286378 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards aafa20102a 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 253d959aa0 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 2d3b2cb469 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 1689c3d468 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 4dcffd2c2e 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards fcec1814c2 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 0627b90040 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 5d35a015f6 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5b2c699948 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 78444ae301 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9bf1417551 74: onsuccess: 1: Successful build after linux: 44 commits discards f33dbd38fa 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards d9dffeba62 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards eac7b2b8f0 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards c3501b72dd 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 8d81ed5110 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 478af8add7 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d74a3d2fee 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9941270645 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3d476c5362 65: onsuccess: 1: Successful build after gcc: 4 commits discards 444ceba509 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 10a3bd36df 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bbbcd697e1 65: onsuccess: 1: Successful build after gcc: 4 commits new 8788292721 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new cfcf3b36fa 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5ba7d61d48 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 00c4fe41db 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 31fe049bcd 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 4ed787c3d4 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 3f8305d43d 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 09e65853c9 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 2b4894484d 74: onsuccess: 1: Successful build after linux: 44 commits new 00c89a963d 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 59ec10231c 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 83400720ed 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 88fcc66b3a 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 88ad7b89c4 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 145a42c9ac 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new f55269aff1 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new ef02335826 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new ee62204c31 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 83b26c7940 84: onsuccess: 1: Success after gcc/glibc: 9 commits new a190e8a0bd 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new b671f02d33 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new e9237c8182 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new e8466b10f7 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 43c078976d 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 709cea2b94 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 3168a256eb 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new d062271954 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 3e8af37cb3 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new e028cbfbb7 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new b9b5b1e83f 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 682cadfd75 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 9e263e7891 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new e83833ab14 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 6dc605bce0 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 42f7d70b5b 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 412ecdd15c 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 49ed296544 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 7ac523ab45 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 51c5243516 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 858d0417e5 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 29b5e30497 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 4eabc0d07c 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new d543e5f93a 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 0c0486e13f 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 82c95b5b07 110: onsuccess: #1703: 1: Success after gcc: 6 commits new f22b86bf04 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 89a5ee5945 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 9589e26ea1 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new f3ac79a304 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new f168ea5bbe 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 4aabf6a5f1 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 4735780cee 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 7a35833dd9 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 31fc15ff04 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 72d7450930 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new e5c432383b 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new ceae208f02 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new ad6c604268 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 93d648441b 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 3cfc77c290 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 38da561415 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 9e0841a9f1 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 3d9cde6214 128: onsuccess: #1723: 1: Success after linux: 12 commits new 9ff876506a 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 03f37de322 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 636d94e0bb 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 00d4a57690 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new b92273fbed 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new c74a6ee741 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 9632f23ffe 135: onsuccess: #1733: 1: Success after binutils: 5 commits new bd682250ac 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 37661e68e8 137: onsuccess: #1736: 1: Success after gcc: 5 commits new f50f67269f 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 94bb29cfda 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 6f64060a08 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new fe7b50c7ad 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 38a453ad3c 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new c181afc983 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new f51f99cd8e 144: onsuccess: #1743: 1: Success after glibc: 2 commits new f38b35e470 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 74d7bed634 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new d0d8238e60 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new d9fa3077ea 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new 0e418815a5 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new fc6dda2b5a 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 343ec42f94 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 95a7ce1673 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new b28c2de0f8 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 7eeac5432c 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 1bcce449de 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new e077f9405c 156: onsuccess: #1757: 1: Success after gcc: 4 commits new a252262c83 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 84d336be4b 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 560a94d92f 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new 90e54ce055 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 339dbad657 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new a41687fddd 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new 61811b3db9 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new e578650742 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new 689c09a1e6 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (f2c848fffb) \ 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 1700 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30024 -> 30436 bytes 04-build_abe-stage1/console.log.xz | Bin 90620 -> 90960 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9152 -> 8496 bytes 07-build_abe-glibc/console.log.xz | Bin 233800 -> 233264 bytes 08-build_abe-stage2/console.log.xz | Bin 224084 -> 224672 bytes 09-build_abe-gdb/console.log.xz | Bin 37640 -> 37660 bytes 10-build_abe-qemu/console.log.xz | Bin 31844 -> 31628 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3852 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2608 -> 2752 bytes 13-check_regression/console.log.xz | Bin 6412 -> 6840 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 40 +- 13-check_regression/results.compare2 | 202 +-- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- sumfiles/g++.log.xz | Bin 2690272 -> 2661780 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 2212152 -> 2199188 bytes sumfiles/gcc.sum | 2498 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 884764 -> 886428 bytes sumfiles/gfortran.sum | 56 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201500 -> 201408 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 432940 -> 429724 bytes sumfiles/libstdc++.sum | 18 +- 41 files changed, 1491 insertions(+), 1649 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_sq/gnu-release-aarch64-spec2k6-Os updated (818835e9e8 -> 278269b151)

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_gnu_sq/gnu-release-aarch64-spec2k6-Os in repository toolchain/ci/base-artifacts. from 818835e9e8 6: onsuccess: #14: 1: [TCWG CI] No change after binutils/gcc [...] new 278269b151 7: onsuccess: #16: 1: [TCWG CI] No change after binutils/gcc [...] 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 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30412 -> 30632 bytes 04-build_abe-stage1/console.log.xz | Bin 68532 -> 70328 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8640 -> 8616 bytes 07-build_abe-glibc/console.log.xz | Bin 235468 -> 238348 bytes 08-build_abe-stage2/console.log.xz | Bin 173616 -> 178800 bytes 09-benchmark/benchmark-build.log | 94 +- 09-benchmark/benchmark.log | 92 +- 09-benchmark/console.log.xz | Bin 3696 -> 3640 bytes 10-check_regression/console.log.xz | Bin 10192 -> 13864 bytes 10-check_regression/csv-results-0/md5sum.csv | 3546 +- 10-check_regression/csv-results-0/perf.csv | 3742 +- 10-check_regression/csv-results-0/results.csv | 689118 ++++++++--------- 10-check_regression/csv-results-0/size.csv | 691855 ++++++++--------- 10-check_regression/csv-results-0/vect.csv | 40 +- 10-check_regression/csv-results-1/md5sum.csv | 3580 +- 10-check_regression/csv-results-1/perf.csv | 3800 +- 10-check_regression/csv-results-1/results.csv | 689380 ++++++++--------- 10-check_regression/csv-results-1/size.csv | 692087 +++++++++--------- 10-check_regression/csv-results-1/vect.csv | 40 +- 10-check_regression/results-brief.csv | 64 +- 10-check_regression/results-compare.csv | 14 +- 10-check_regression/results-full.csv | 4031 +- 10-check_regression/results-internal.csv | 249 +- 10-check_regression/results.csv | 249 +- 10-check_regression/results.log | 1104 +- dashboard/dashboard-generate.sh | 2 +- .../squad/400.perlbench/results-metadata.json | 16 +- dashboard/squad/400.perlbench/results-metrics.json | 2 +- dashboard/squad/401.bzip2/results-metadata.json | 16 +- dashboard/squad/401.bzip2/results-metrics.json | 2 +- dashboard/squad/403.gcc/results-functional.json | 2 +- dashboard/squad/403.gcc/results-metadata.json | 16 +- dashboard/squad/403.gcc/results-metrics.json | 1 - dashboard/squad/410.bwaves/results-metadata.json | 16 +- dashboard/squad/410.bwaves/results-metrics.json | 2 +- dashboard/squad/416.gamess/results-metadata.json | 16 +- dashboard/squad/416.gamess/results-metrics.json | 2 +- dashboard/squad/429.mcf/results-metadata.json | 16 +- dashboard/squad/429.mcf/results-metrics.json | 2 +- dashboard/squad/433.milc/results-metadata.json | 16 +- dashboard/squad/433.milc/results-metrics.json | 2 +- dashboard/squad/434.zeusmp/results-metadata.json | 16 +- dashboard/squad/434.zeusmp/results-metrics.json | 2 +- dashboard/squad/435.gromacs/results-metadata.json | 16 +- dashboard/squad/435.gromacs/results-metrics.json | 2 +- .../squad/436.cactusADM/results-metadata.json | 16 +- dashboard/squad/436.cactusADM/results-metrics.json | 2 +- dashboard/squad/437.leslie3d/results-metadata.json | 16 +- dashboard/squad/437.leslie3d/results-metrics.json | 2 +- dashboard/squad/444.namd/results-metadata.json | 16 +- dashboard/squad/444.namd/results-metrics.json | 2 +- dashboard/squad/445.gobmk/results-metadata.json | 16 +- dashboard/squad/445.gobmk/results-metrics.json | 2 +- dashboard/squad/447.dealII/results-metadata.json | 16 +- dashboard/squad/447.dealII/results-metrics.json | 2 +- dashboard/squad/450.soplex/results-metadata.json | 16 +- dashboard/squad/450.soplex/results-metrics.json | 2 +- dashboard/squad/453.povray/results-metadata.json | 16 +- dashboard/squad/453.povray/results-metrics.json | 4 +- dashboard/squad/454.calculix/results-metadata.json | 16 +- dashboard/squad/454.calculix/results-metrics.json | 2 +- dashboard/squad/456.hmmer/results-metadata.json | 16 +- dashboard/squad/456.hmmer/results-metrics.json | 2 +- dashboard/squad/458.sjeng/results-metadata.json | 16 +- dashboard/squad/458.sjeng/results-metrics.json | 2 +- dashboard/squad/459.GemsFDTD/results-metadata.json | 16 +- dashboard/squad/459.GemsFDTD/results-metrics.json | 2 +- .../squad/462.libquantum/results-metadata.json | 16 +- .../squad/462.libquantum/results-metrics.json | 2 +- dashboard/squad/464.h264ref/results-metadata.json | 16 +- dashboard/squad/464.h264ref/results-metrics.json | 2 +- dashboard/squad/465.tonto/results-metadata.json | 16 +- dashboard/squad/465.tonto/results-metrics.json | 2 +- dashboard/squad/470.lbm/results-metadata.json | 16 +- dashboard/squad/470.lbm/results-metrics.json | 2 +- dashboard/squad/471.omnetpp/results-metadata.json | 16 +- dashboard/squad/471.omnetpp/results-metrics.json | 2 +- dashboard/squad/473.astar/results-metadata.json | 16 +- dashboard/squad/473.astar/results-metrics.json | 2 +- dashboard/squad/481.wrf/results-metadata.json | 16 +- dashboard/squad/481.wrf/results-metrics.json | 2 +- dashboard/squad/482.sphinx3/results-metadata.json | 16 +- dashboard/squad/482.sphinx3/results-metrics.json | 2 +- .../squad/483.xalancbmk/results-metadata.json | 16 +- dashboard/squad/483.xalancbmk/results-metrics.json | 2 +- dashboard/squad/Mean/results-functional.json | 4 - dashboard/squad/Mean/results-metadata.json | 12 - dashboard/squad/Mean/results-metrics.json | 5 - dashboard/squad/dashboard-push-squad.sh | 125 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 46 +- mail/mail-body.txt | 46 +- mail/mail-subject.txt | 2 +- manifest.sh | 35 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 1269288 -> 1269780 bytes save-temps/401.bzip2.tar.xz | Bin 94336 -> 94484 bytes save-temps/403.gcc.tar.xz | Bin 3516000 -> 3527052 bytes save-temps/410.bwaves.tar.xz | Bin 15084 -> 15072 bytes save-temps/416.gamess.tar.xz | Bin 4200272 -> 4200328 bytes save-temps/429.mcf.tar.xz | Bin 36532 -> 36660 bytes save-temps/433.milc.tar.xz | Bin 167744 -> 167216 bytes save-temps/434.zeusmp.tar.xz | Bin 125948 -> 125388 bytes save-temps/435.gromacs.tar.xz | Bin 972028 -> 974112 bytes save-temps/436.cactusADM.tar.xz | Bin 724376 -> 725748 bytes save-temps/437.leslie3d.tar.xz | Bin 46428 -> 46392 bytes save-temps/444.namd.tar.xz | Bin 207864 -> 168764 bytes save-temps/445.gobmk.tar.xz | Bin 1822216 -> 1820716 bytes save-temps/447.dealII.tar.xz | Bin 6135200 -> 6154596 bytes save-temps/450.soplex.tar.xz | Bin 686416 -> 701052 bytes save-temps/453.povray.tar.xz | Bin 1410036 -> 1319420 bytes save-temps/454.calculix.tar.xz | Bin 1223536 -> 1224328 bytes save-temps/456.hmmer.tar.xz | Bin 379076 -> 378968 bytes save-temps/458.sjeng.tar.xz | Bin 147832 -> 148436 bytes save-temps/459.GemsFDTD.tar.xz | Bin 144840 -> 145160 bytes save-temps/462.libquantum.tar.xz | Bin 61996 -> 62148 bytes save-temps/464.h264ref.tar.xz | Bin 565952 -> 564308 bytes save-temps/465.tonto.tar.xz | Bin 2043412 -> 2040696 bytes save-temps/470.lbm.tar.xz | Bin 26324 -> 26364 bytes save-temps/471.omnetpp.tar.xz | Bin 1052676 -> 1030660 bytes save-temps/473.astar.tar.xz | Bin 89212 -> 88908 bytes save-temps/481.wrf.tar.xz | Bin 1564140 -> 1551696 bytes save-temps/482.sphinx3.tar.xz | Bin 255284 -> 255512 bytes save-temps/483.xalancbmk.tar.xz | Bin 10858424 -> 10893592 bytes 130 files changed, 1392182 insertions(+), 1391715 deletions(-) delete mode 100644 dashboard/squad/Mean/results-functional.json delete mode 100644 dashboard/squad/Mean/results-metadata.json delete mode 100644 dashboard/squad/Mean/results-metrics.json -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_llvm_tk1/llvm-master-arm-spec2k6-O2 updated (d146ef5a4e -> 1a1c3249ae)

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_tk1/llvm-master-arm-spec2k6-O2 in repository toolchain/ci/base-artifacts. from d146ef5a4e 5: onsuccess: #372: 1: [TCWG CI] No change after binutils/gc [...] new 1a1c3249ae 6: onsuccess: #375: 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 1740 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30168 -> 30880 bytes 04-build_abe-stage1/console.log.xz | Bin 91412 -> 93536 bytes 06-build_abe-linux/console.log.xz | Bin 8660 -> 8748 bytes 07-build_abe-glibc/console.log.xz | Bin 232728 -> 235136 bytes 08-build_abe-stage2/console.log.xz | Bin 209760 -> 214940 bytes 09-build_llvm-true-false-/console.log.xz | Bin 0 -> 63208 bytes 09-build_llvm-true/console.log.xz | Bin 63184 -> 0 bytes 10-benchmark/benchmark-build.log | 128 +- 10-benchmark/benchmark.log | 126 +- 10-benchmark/console.log.xz | Bin 3988 -> 3868 bytes 11-check_regression/console.log.xz | Bin 13332 -> 12848 bytes 11-check_regression/csv-results-0/md5sum.csv | 1717 +- 11-check_regression/csv-results-0/perf.csv | 2052 +- 11-check_regression/csv-results-0/results.csv | 209192 +++++++------ 11-check_regression/csv-results-0/size.csv | 221910 +++++++------- 11-check_regression/csv-results-0/vect.csv | 20380 +- 11-check_regression/csv-results-1/md5sum.csv | 1701 +- 11-check_regression/csv-results-1/perf.csv | 2054 +- 11-check_regression/csv-results-1/results.csv | 197771 ++++++------- 11-check_regression/csv-results-1/size.csv | 276912 +++++++++--------- 11-check_regression/csv-results-1/vect.csv | 20904 +- 11-check_regression/results-brief.csv | 40 +- 11-check_regression/results-compare.csv | 4 +- 11-check_regression/results-full.csv | 2155 +- 11-check_regression/results-internal.csv | 156 +- 11-check_regression/results.csv | 156 +- 11-check_regression/results.log | 1066 +- 11-check_regression/skipped-symbols.txt | 50 + dashboard/dashboard-generate.sh | 2 +- .../squad/400.perlbench/results-metadata.json | 14 +- dashboard/squad/401.bzip2/results-metadata.json | 14 +- dashboard/squad/401.bzip2/results-metrics.json | 2 +- dashboard/squad/403.gcc/results-metadata.json | 14 +- dashboard/squad/403.gcc/results-metrics.json | 2 +- dashboard/squad/429.mcf/results-metadata.json | 14 +- dashboard/squad/429.mcf/results-metrics.json | 2 +- dashboard/squad/433.milc/results-metadata.json | 14 +- dashboard/squad/433.milc/results-metrics.json | 2 +- dashboard/squad/444.namd/results-metadata.json | 14 +- dashboard/squad/445.gobmk/results-metadata.json | 14 +- dashboard/squad/445.gobmk/results-metrics.json | 2 +- dashboard/squad/447.dealII/results-metadata.json | 14 +- dashboard/squad/447.dealII/results-metrics.json | 2 +- dashboard/squad/450.soplex/results-metadata.json | 14 +- dashboard/squad/450.soplex/results-metrics.json | 2 +- dashboard/squad/453.povray/results-metadata.json | 14 +- dashboard/squad/453.povray/results-metrics.json | 2 +- dashboard/squad/456.hmmer/results-metadata.json | 14 +- dashboard/squad/456.hmmer/results-metrics.json | 2 +- dashboard/squad/458.sjeng/results-metadata.json | 14 +- dashboard/squad/458.sjeng/results-metrics.json | 2 +- .../squad/462.libquantum/results-metadata.json | 14 +- .../squad/462.libquantum/results-metrics.json | 2 +- dashboard/squad/464.h264ref/results-metadata.json | 14 +- dashboard/squad/470.lbm/results-metadata.json | 14 +- dashboard/squad/470.lbm/results-metrics.json | 2 +- dashboard/squad/471.omnetpp/results-metadata.json | 14 +- dashboard/squad/471.omnetpp/results-metrics.json | 2 +- dashboard/squad/473.astar/results-metadata.json | 14 +- dashboard/squad/473.astar/results-metrics.json | 2 +- dashboard/squad/482.sphinx3/results-metadata.json | 14 +- dashboard/squad/482.sphinx3/results-metrics.json | 2 +- .../squad/483.xalancbmk/results-metadata.json | 14 +- dashboard/squad/483.xalancbmk/results-metrics.json | 2 +- dashboard/squad/dashboard-push-squad.sh | 78 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 46 +- mail/mail-body.txt | 46 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 2 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 1343776 -> 1343452 bytes save-temps/401.bzip2.tar.xz | Bin 105128 -> 105432 bytes save-temps/403.gcc.tar.xz | Bin 3748732 -> 3765624 bytes save-temps/429.mcf.tar.xz | Bin 34868 -> 34520 bytes save-temps/433.milc.tar.xz | Bin 155732 -> 155168 bytes save-temps/444.namd.tar.xz | Bin 212008 -> 211768 bytes save-temps/445.gobmk.tar.xz | Bin 2101536 -> 2087892 bytes save-temps/447.dealII.tar.xz | Bin 3437328 -> 3321980 bytes save-temps/450.soplex.tar.xz | Bin 529560 -> 533312 bytes save-temps/453.povray.tar.xz | Bin 1262540 -> 1258204 bytes save-temps/456.hmmer.tar.xz | Bin 350772 -> 349248 bytes save-temps/458.sjeng.tar.xz | Bin 174136 -> 173576 bytes save-temps/462.libquantum.tar.xz | Bin 53320 -> 53124 bytes save-temps/464.h264ref.tar.xz | Bin 665716 -> 665212 bytes save-temps/470.lbm.tar.xz | Bin 25444 -> 25432 bytes save-temps/471.omnetpp.tar.xz | Bin 909736 -> 907232 bytes save-temps/473.astar.tar.xz | Bin 75752 -> 76020 bytes save-temps/482.sphinx3.tar.xz | Bin 237900 -> 237736 bytes save-temps/483.xalancbmk.tar.xz | Bin 7167388 -> 7182292 bytes 95 files changed, 469425 insertions(+), 489569 deletions(-) create mode 100644 09-build_llvm-true-false-/console.log.xz delete mode 100644 09-build_llvm-true/console.log.xz create mode 100644 11-check_regression/skipped-symbols.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (cd39d033bc -> 9e67bbbc60)

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 cd39d033bc 162: onsuccess: #2097: 1: Success after binutils/gcc: 16 commits discards f8911fdd59 161: onsuccess: #2096: 1: Success after gcc: 2 commits discards da8e9cb518 160: onsuccess: #2095: 1: Success after binutils/gcc: 4 commits discards 841eea304a 159: onsuccess: #2094: 1: Success after binutils/gcc: 23 commits discards 06ec7ebcd0 158: onsuccess: #2093: 1: Success after binutils/gcc: 9 commits discards 7628af9990 157: onsuccess: #2092: 1: Success after binutils/gcc: 3 commits discards 45286b1ac0 156: onsuccess: #2091: 1: Success after binutils/gcc: 2 commits discards d61bad794d 155: onsuccess: #2090: 1: Success after binutils/gcc: 22 commits discards c942cf0fbd 154: onsuccess: #2089: 1: Success after gcc: 4 commits discards cb03a46dc0 153: onsuccess: #2088: 1: Success after basepoints/gcc-13-30 [...] discards 38a642b8d4 152: onsuccess: #2087: 1: Success after gdb-12-branchpoint-2 [...] discards 4fc9623c9d 151: onsuccess: #2086: 1: Success after gcc: 2 commits discards 5ea83c42d4 150: onsuccess: #2085: 1: Success after gcc: 2 commits discards 17dfd1521c 149: onsuccess: #2084: 1: Success after gcc: 16 commits discards c64a413958 148: onsuccess: #2082: 1: Success after gdb-12-branchpoint-2 [...] discards 90873939f9 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 commits discards 2c5dc5812c 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits discards d25de95785 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits discards 08bf7a8d76 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits discards 2c54dab308 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits discards 3d7d59c712 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits discards f4e9bc147b 141: onsuccess: #2073: 1: Success after binutils: 3 commits discards df4dbcd58e 140: onsuccess: #2070: 1: Success after binutils: 4 commits discards e9ceca3d9a 139: onsuccess: #2067: 1: Success after binutils: 2 commits discards 386df4cec5 138: onsuccess: #2064: 1: Success after binutils: 4 commits discards 8ce6ea6416 137: onsuccess: #2061: 1: Success after binutils: 2 commits discards d1bdeb449c 136: onsuccess: #2056: 1: Success after binutils: 4 commits discards 8e914fd298 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits discards e61cbeaddb 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits discards 015454bf14 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits discards 3cf910ce07 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits discards 68dd7af46b 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] discards a61d2c4b00 130: onsuccess: #2049: 1: Success after gcc: 9 commits discards b65e580ab5 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] discards 6b77a952f4 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] discards 4fa3bfc186 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] discards ae63322767 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] discards 96c64cb326 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits discards 390e3f7a87 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits discards 7beecebfb1 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits discards 2f8a7df287 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits discards f61cc9e2ec 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits discards d097dadac5 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits discards 62420ae8d2 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits discards c1f3104df9 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits discards e42f784b2f 117: onsuccess: #2034: 1: Success after binutils: 2 commits discards e6d9cc99ec 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits discards 50a95187f6 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits discards 8d60e80a76 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits discards de2cae76a8 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits discards 56fad62644 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits discards 5f1cdd721a 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits discards b87a84f82d 110: onsuccess: #2027: 1: Success after gcc: 5 commits discards 87e850fb5d 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits discards b1067f3b72 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits discards 07ba1279a2 107: onsuccess: #2024: 1: Success after gcc: 3 commits discards ab73c6c372 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits discards 60fc966a24 105: onsuccess: #2022: 1: Success after gcc: 4 commits discards 6ed3b5edd6 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards 0ba7c9d647 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards 81d563ced5 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] discards 209da209cc 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards d220e53f48 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards 6e59dff35e 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards d6863250ea 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards 5fdb1a7841 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards eaf54c2b41 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] discards 17135d8bec 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] discards f0ac78177b 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards c1eec7c0c2 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] discards 9e251159ba 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards d8271c1954 91: onsuccess: 1: Success after gcc: Daily bump. discards cd3fc103ef 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards 8c825f5436 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards a0790efefa 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards b775e676b3 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards 0fc2ed63f4 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards 23f058da4b 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards 4baa8ea66d 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards 8e2c5204b8 83: onsuccess: 1: Success after gcc: 8 commits discards 9a19883661 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards f4dc5c40c4 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards 4389ef92d1 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards b77f5f53f8 79: onsuccess: 1: Successful build after gcc: Daily bump. discards 8dc5eb7a69 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 2628178b6c 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 935c64ec65 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards c485004715 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 2263d9f257 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards 4acebcd7d4 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards 8426ada97c 72: onsuccess: 1: Successful build after gcc: 2 commits discards c572f5e965 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 99891acb4d 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards d199ebd984 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards cd2f970e0a 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards f5b3ee85ab 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards a2f3b81ca8 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 0a374f81a5 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards f4601ee8e2 64: onsuccess: 1: Successful build after gcc: 5 commits discards 5d2dd94246 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 9c437a394c 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits new faf8ff291e 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 036c47b34a 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits new e71046f9d5 64: onsuccess: 1: Successful build after gcc: 5 commits new 8aef6c86bd 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 7b99718076 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 8b4f311bda 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new ebae4c391c 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 1ca21d4a3e 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 97b7a3ac2f 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new 5ef1cca934 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new b720c87797 72: onsuccess: 1: Successful build after gcc: 2 commits new e1e57ed51f 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] new d5bb4113c7 74: onsuccess: 1: Successful build after binutils: Automatic [...] new 963d45164a 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 386324adcc 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new ffc9262280 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new ba5449b3c8 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 1a16b25d33 79: onsuccess: 1: Successful build after gcc: Daily bump. new 978346138b 80: onsuccess: 1: Success after binutils/gcc: 14 commits new 432c8f6773 81: onsuccess: 1: Success after binutils/gcc: 27 commits new 9144042503 82: onsuccess: 1: Success after binutils/gcc: 10 commits new 659f42173a 83: onsuccess: 1: Success after gcc: 8 commits new e87e6d93e9 84: onsuccess: 1: Success after binutils/gcc: 9 commits new 43ff7f1954 85: onsuccess: 1: Success after binutils/gcc: 9 commits new 51518a1918 86: onsuccess: 1: Success after binutils/gcc: 13 commits new b2098d97c9 87: onsuccess: 1: Success after binutils/gcc: 4 commits new 4009834932 88: onsuccess: 1: Success after binutils/gcc: 16 commits new b9404ffb9f 89: onsuccess: 1: Success after binutils/gcc: 9 commits new 0702a19595 90: onsuccess: 1: Success after binutils/gcc: 6 commits new 5902c912a7 91: onsuccess: 1: Success after gcc: Daily bump. new 5706ac19e3 92: onsuccess: #1965: 1: Success after gcc: 2 commits new 63aba02e58 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] new 31c4cc38fd 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new 5ea6e58702 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] new 86fb2b3a9a 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] new 1dc4939562 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new bc98bc44dd 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new 2bf52c7c24 99: onsuccess: #1974: 1: Success after gcc: 14 commits new ff1ad101a4 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new c35b827684 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new 1715363931 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] new 6a75afc8dc 103: onsuccess: #2020: 1: Success after gcc: 2 commits new 9ac269352b 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new ef2d2b8415 105: onsuccess: #2022: 1: Success after gcc: 4 commits new 5941301f97 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits new 77aec1d4c1 107: onsuccess: #2024: 1: Success after gcc: 3 commits new c50a871df1 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits new e87aa6d3aa 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits new 90ec1329a4 110: onsuccess: #2027: 1: Success after gcc: 5 commits new e1fee187a8 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits new baccc5d610 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits new 2ab47ba00c 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits new cea5b47412 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits new d131977a5e 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits new 06ed45797f 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits new bed2b91696 117: onsuccess: #2034: 1: Success after binutils: 2 commits new 45ca3f30f8 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits new 9e8512600b 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits new 9ed8f15dad 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits new 8bb694aecb 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits new b534c160d3 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits new 3dc09a9433 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits new a276bdb967 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits new 25426019f4 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits new 1e20b3ae2e 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] new 0c4c5e13ec 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] new 998b51042d 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] new 191e7f5b00 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] new 1a9844e226 130: onsuccess: #2049: 1: Success after gcc: 9 commits new c266d362ab 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] new c94d30a017 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits new 3a41173f5d 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits new b591006606 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits new d7762a6e81 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits new 5cc5a3e5c5 136: onsuccess: #2056: 1: Success after binutils: 4 commits new f29df0c9cf 137: onsuccess: #2061: 1: Success after binutils: 2 commits new 7e04af3cc7 138: onsuccess: #2064: 1: Success after binutils: 4 commits new 64a62f62ec 139: onsuccess: #2067: 1: Success after binutils: 2 commits new 1a5afbf5d1 140: onsuccess: #2070: 1: Success after binutils: 4 commits new ab5d57043c 141: onsuccess: #2073: 1: Success after binutils: 3 commits new bdc9194bbe 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits new 7eb7de2317 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits new d8a704ae25 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits new dade483731 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits new e6ac4d76db 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits new 174c11089a 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 commits new 0e9e421e9a 148: onsuccess: #2082: 1: Success after gdb-12-branchpoint-2 [...] new ba1cd261c5 149: onsuccess: #2084: 1: Success after gcc: 16 commits new 73613e89a6 150: onsuccess: #2085: 1: Success after gcc: 2 commits new 5bd60dac44 151: onsuccess: #2086: 1: Success after gcc: 2 commits new 5508dcd017 152: onsuccess: #2087: 1: Success after gdb-12-branchpoint-2 [...] new 73af04efd1 153: onsuccess: #2088: 1: Success after basepoints/gcc-13-30 [...] new 084d18854d 154: onsuccess: #2089: 1: Success after gcc: 4 commits new 6b64c018fc 155: onsuccess: #2090: 1: Success after binutils/gcc: 22 commits new 6080302ddc 156: onsuccess: #2091: 1: Success after binutils/gcc: 2 commits new 2e0ecd34cd 157: onsuccess: #2092: 1: Success after binutils/gcc: 3 commits new 1ffa36af56 158: onsuccess: #2093: 1: Success after binutils/gcc: 9 commits new a25851dced 159: onsuccess: #2094: 1: Success after binutils/gcc: 23 commits new 87615e67b7 160: onsuccess: #2095: 1: Success after binutils/gcc: 4 commits new b609aa5b71 161: onsuccess: #2096: 1: Success after gcc: 2 commits new 7b100991d3 162: onsuccess: #2097: 1: Success after binutils/gcc: 16 commits new 9e67bbbc60 163: onsuccess: #2098: 1: Success after binutils/gcc: 18 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 (cd39d033bc) \ 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 1732 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 37376 -> 38812 bytes 04-build_abe-gcc/console.log.xz | Bin 213536 -> 215388 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3844 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2448 -> 2648 bytes 07-check_regression/console.log.xz | Bin 5524 -> 5164 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 169 +- 08-update_baseline/console.log | 38 +- 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 | 18 +- sumfiles/g++.log.xz | Bin 3588200 -> 3588208 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 3137520 -> 3091280 bytes sumfiles/gcc.sum | 4404 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1040412 -> 1042864 bytes sumfiles/gfortran.sum | 52 +- sumfiles/libatomic.log.xz | Bin 2188 -> 2184 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207380 -> 207700 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2548 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 461104 -> 450344 bytes sumfiles/libstdc++.sum | 16 +- 31 files changed, 2382 insertions(+), 2509 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (7916bdb1d9 -> 6bcf405e7d)

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 7916bdb1d9 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 34 [...] discards 483a41e597 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits discards 181989f7b9 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/g [...] discards c34b71d865 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/g [...] discards f49cec811a 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 [...] discards 29cda29c8b 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits discards 9d6c8a67d7 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/g [...] discards b389cd26d4 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/g [...] discards 0f74ab9b20 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] discards 44ec3ac4d7 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] discards a070442263 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards c81addd5ae 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards 52e91f528c 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards 1ea1fd5557 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] discards f6beac0da5 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] discards f68771a165 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] discards c7d105b795 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] discards a71a410464 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] discards 57b33ba598 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] discards dca19203e9 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards 9f24215075 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 6204c40cee 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards 477e5451be 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards 0dcf9b8f22 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards f86d9f98ec 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards 4e2b88a7dd 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards 1680a0c59c 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards d18a41130d 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards cebe390015 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards 65427ca7eb 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards d7d24d0b04 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards fc244a6abd 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards 92fbd2e814 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 3919b6b833 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards 0eb76adb52 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 1bf35d2569 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards e9f3412bc8 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 2eda6b179a 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 22eda25ba1 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards 07db132c7f 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 4b466b2c39 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards ae7d75d8fc 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards c75404c554 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards fa03036df1 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards 2ccd81ff7d 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 309646c7d9 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards 53c594459b 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards ce73ed9f0d 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards f154b78c64 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 9eef4e64b7 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 4ac182cf4d 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 2928439de8 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 40a2ac1971 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards d38a2b8b4b 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 8c1c5fbb98 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards d780e7e707 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards ed110970b3 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards e15d0f7d35 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards fe3410d281 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards b5114b80ba 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards a6dca3adb4 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards cb61147bb9 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 8a4f32be6b 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards db7a4ed6f9 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 24e20d6795 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 7063ed33e7 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards c951db21bf 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 8745f0d21c 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards a23b7774fc 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 904d372724 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards cd6d4f2493 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 09c4d220c1 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards 8bd52144b2 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards fceed7f37d 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards 9010195d46 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards e4a91aef1d 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 7825a0a551 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 97de3c590b 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 9d3dbfc19e 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 3d0b9c51d0 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 45a6e2049b 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 0bda718ab8 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards c14c97c0e5 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 9a43162e1e 85: onsuccess: 7: Success after gcc: 9 commits discards 2bb2482a94 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 7d1d83c5e5 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards aad4485783 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 21a072ab1c 81: onsuccess: 7: Successful build after gcc: 2 commits discards 63f8a1cc82 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 5579718ace 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 0a50d8d462 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c045768c7c 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards ffc1c1c6ae 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ef1523e1ec 75: onsuccess: 7: Successful build after linux: 44 commits discards d52a89d78b 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 7d4faefe3f 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 23f2216af2 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 1610c84fbb 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 510dfbd368 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 68f542be8c 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 445b360124 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 99990a5ce6 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4d84416658 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 12bc8e974e 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 5bf598167c 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new f17aa9114a 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 4f64efb946 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7b37b91a3a 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 15db557dbb 75: onsuccess: 7: Successful build after linux: 44 commits new 7f780a56d7 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f0927684a8 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 4d202d9ce5 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 82a9597394 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 34492082b3 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new d3515b99d3 81: onsuccess: 7: Successful build after gcc: 2 commits new d4ed812a07 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 57dfc24510 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new e4b3eb666b 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 5c8b5652e2 85: onsuccess: 7: Success after gcc: 9 commits new dfa6f5efbd 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new c67e08b75d 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 9ba1d2b7ba 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new fcf47a7461 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 2a981b2659 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 9e25744e5f 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new f19aee98fc 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new cd0e07f604 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new 05e5bec9c8 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new aef7d18fbf 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 5060ed48b7 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new cdea38c21f 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new a875756b30 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new ac3be0622e 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 621942071c 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new 6e01d9779a 101: onsuccess: #1609: 7: Success after binutils: 78 commits new febd5de86a 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new adf9e899c2 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 5b60fdd8cf 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 20f1ea1649 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 88a33d727c 106: onsuccess: #1617: 7: Success after gcc: 2 commits new b46e881a4e 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 103b7861b7 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new 1088f9d5e1 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 1eed38c418 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new fe1272aa52 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 110a8e2e61 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 9c17ee8e20 113: onsuccess: #1624: 7: Success after gcc: 6 commits new beb98cb2b2 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 70ecae80a5 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new a8506b2354 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 35c4fe17ca 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 9c7f9fc77c 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 226feceffd 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new b9ed681f54 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 73365d5b44 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new e2116505cc 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new ea0217cc83 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 83f247fc1e 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 7085a10ba0 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new f8ee0629d7 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new 9a05012651 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 10fcd4a22d 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 4f1a28f462 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new c5405e5f66 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 221edc33f1 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 5ee9dc4a17 132: onsuccess: #1645: 7: Success after linux: 23 commits new 4b54771236 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new 73cd6607a9 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new 5e7bc62d4f 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new ae94c790ba 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 7cfe451fbd 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new b41ee21bf5 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new 6783ea7366 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 9a02b47437 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new 36c6e29088 141: onsuccess: #1656: 7: Success after gcc: 7 commits new eb899e9c15 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new ea2644ac4b 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new 5ac778dde4 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new 63c180673f 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new 33da37b6a4 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new 9265fdc3d3 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new 0b16181fc0 148: onsuccess: #1663: 7: Success after glibc: 2 commits new a60a1b1d27 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new f2f64e6639 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] new 637d063897 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] new a462188ce3 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] new 5ab227d7c1 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] new 9242eb04bc 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] new 82628e11d8 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] new ebb664d0cf 156: onsuccess: #1671: 7: Success after gcc: 3 commits new d5206b3c16 157: onsuccess: #1672: 7: Success after gcc: 2 commits new 2d3d02b6d2 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new 525a62073d 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] new 45f96f6420 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] new 996ce2461a 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/g [...] new 6eb028e4ac 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/g [...] new be1c47d511 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits new f6c68c3237 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 [...] new 0a44863f43 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/g [...] new 45baf611fe 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/g [...] new 0a17bae472 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits new 6e43f14d34 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 34 [...] new 6bcf405e7d 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (7916bdb1d9) \ 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 1676 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 30096 -> 30328 bytes 05-build_abe-stage1/console.log.xz | Bin 90500 -> 90856 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 9188 -> 8484 bytes 08-build_abe-glibc/console.log.xz | Bin 234012 -> 234228 bytes 09-build_abe-stage2/console.log.xz | Bin 222780 -> 223888 bytes 10-build_abe-gdb/console.log.xz | Bin 37360 -> 37660 bytes 11-build_abe-qemu/console.log.xz | Bin 31680 -> 31636 bytes 12-check_regression/console.log.xz | Bin 4044 -> 4296 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +++++++++++------------ 22 files changed, 62 insertions(+), 62 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/release-arm-check_bootstrap updated (0aeb7159a4 -> 43277b3ea0)

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 0aeb7159a4 17: onsuccess: #140: 1: Success after binutils/gcc: 13 commits new 43277b3ea0 18: onsuccess: #141: 1: Success after binutils/gcc: 10 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 1672 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 51624 -> 50804 bytes 04-build_abe-bootstrap/console.log.xz | Bin 463132 -> 463608 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3816 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2432 -> 2340 bytes 07-check_regression/console.log.xz | Bin 5100 -> 5224 bytes 07-check_regression/extra-bisect-params | 1 + 07-check_regression/fails.sum | 6 + 07-check_regression/mail-body.txt | 26 + 07-check_regression/results.compare | 25 +- 07-check_regression/results.compare2 | 97 +- 07-check_regression/results.regressions | 26 + dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 26 + sumfiles/g++.log.xz | Bin 2854328 -> 2858872 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 2467268 -> 2462456 bytes sumfiles/gcc.sum | 4258 +++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 938708 -> 939736 bytes sumfiles/gfortran.sum | 68 +- sumfiles/libatomic.log.xz | Bin 2304 -> 2308 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 206532 -> 205516 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2720 -> 2724 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 468024 -> 461912 bytes sumfiles/libstdc++.sum | 10 +- 35 files changed, 2450 insertions(+), 2317 deletions(-) create mode 100644 07-check_regression/extra-bisect-params create mode 100644 07-check_regression/fails.sum create mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_debug updated (8344db5a28 -> c46a8bb5fe)

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 8344db5a28 17: onsuccess: #140: 2: Success after binutils/gcc: 15 commits new c46a8bb5fe 18: onsuccess: #141: 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 1716 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 52076 -> 51308 bytes 05-build_abe-bootstrap_debug/console.log.xz | Bin 461624 -> 463504 bytes 06-check_regression/console.log.xz | Bin 2968 -> 2820 bytes 07-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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 13 files changed, 25 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 8 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022