Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-allmodconfig updated (88e3cd5f3c -> e5ca1f735d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-allmodconfig in repository toolchain/ci/base-artifacts. from 88e3cd5f3c 14: onsuccess: #478: 33: Success after binutils/gcc/linux/qe [...] new e5ca1f735d 15: onsuccess: #479: 33: Success after binutils/gcc/linux/qe [...] 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 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30184 -> 30008 bytes 04-build_abe-stage1/console.log.xz | Bin 91208 -> 91940 bytes 05-build_abe-qemu/console.log.xz | Bin 31028 -> 31076 bytes 06-build_linux/console.log.xz | Bin 4776 -> 4860 bytes 08-check_regression/console.log.xz | Bin 3376 -> 4376 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 31 ++++++++++++++++--------------- 17 files changed, 28 insertions(+), 27 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap updated (19c0dfe7c4 -> 38d436c58e)

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 19c0dfe7c4 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards 6940becd96 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards d45da22d02 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards c78a70f23f 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards a63b544f31 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards cd7c8cc0a7 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards 31261f210e 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards ec3b4cafa0 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 005570d02e 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards 0fac49f830 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards bcf64758fd 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards 9d466aeef9 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards b2982b85ac 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 129ccd7d84 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 3d1234d50e 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards 3d04c2bce9 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 713cf762e9 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards 128c7d0fa6 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards f2041c1abd 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 4e437e24fa 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 8808f6cc6b 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 5316f21afd 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards 49730ebb75 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards bd68bd3ba6 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards d087588ae4 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards 177a1c0901 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards 4ca02e6e2b 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards f18df5c867 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards 7415404eff 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards c52f7c4b61 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards e4382d550f 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards cfde09da5b 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards b23d6f0244 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards dfc55e0a56 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards ea94878c38 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 51000b4404 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 34325e7539 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards ce8fe5ed09 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 0cb46d33f9 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards b9d6dd219c 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 0c851d61a2 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 31f362796e 88: onsuccess: 1: Success after gcc: 20 commits discards a1515db011 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards 20caa68148 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards 36b17149d3 85: onsuccess: 2: Success after binutils: 4 commits discards 4cd2ba6571 84: onsuccess: 2: Success after gcc: 9 commits discards 2feb2bf694 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards c3d1de1a09 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 321b753b78 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards e89a517092 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards f6d8c56cb0 79: onsuccess: 1: Successful build after gcc: 3 commits discards 91d9b54725 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards fb51292843 77: force: 2: Successful build after gcc: 32 commits discards 3baf76d471 76: onsuccess: 2: Successful build after binutils: 10 commits discards 4cab012423 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards c80b7fef62 74: onsuccess: 2: Successful build after gcc: 13 commits discards 48f290c17c 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 69df022946 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 659ed174f8 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 38e7e7f932 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 4522abdb46 69: onsuccess: 2: Successful build after baseline build: no [...] discards dc96905d78 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards fa82cf329f 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 6191d61db0 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 0accc213e8 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards fbfd390f72 64: onsuccess: 2: Successful build after gcc: 7 commits discards 020888584d 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 5487eb0f33 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards a62f112db0 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards b5499cea69 60: onsuccess: 1: Successful build after gcc: 15 commits discards c17f9fe3e2 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards d300844388 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards ea5e3c5d1e 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 8660cbdee6 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards fefccd4083 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 8ec56fca6f 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 7a2ff40eac 53: onsuccess: 2: Successful build after gcc: 5 commits discards e74fb5bfa1 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 2fdbbbb4fd 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 67e60b0b09 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 34a1f273ef 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 2730c8fba6 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 4751d85f20 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 95db510202 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards b513e35914 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards c9fac6a9ee 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 6b7f5e5397 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards 8c5460ea16 42: onsuccess: 2: Successful build after gcc: 2 commits discards fc65ddd2ea 41: onsuccess: 2: Successful build after baseline build: no [...] discards 4585a77b4b 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 234da48bc4 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards c10a1fcb9c 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 7962871003 37: onsuccess: 2: Successful build after gcc: 2 commits discards 1dee1b6ef8 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 6fa792cb37 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards bbc1643cfb 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards bc50e00fb7 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 48f9e1686b 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards d7ee3d6869 31: onsuccess: 2: Successful build after gcc: 8 commits discards 4a2f71f633 30: onsuccess: 2: Successful build after gcc: 7 commits discards c98e6cb567 29: onsuccess: 2: Successful build after binutils: 5 commits new f23869f0a3 29: onsuccess: 2: Successful build after binutils: 5 commits new 9a26ec367b 30: onsuccess: 2: Successful build after gcc: 7 commits new c247ad79d0 31: onsuccess: 2: Successful build after gcc: 8 commits new 571e23bb7d 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 32e24b3040 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits new b2c1835a5b 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 86e5773715 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits new afc452c3c6 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits new cde3af7e76 37: onsuccess: 2: Successful build after gcc: 2 commits new e6a49c3c0d 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 9dfea5890b 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new cb08266bd8 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new ab5dbacf7a 41: onsuccess: 2: Successful build after baseline build: no [...] new d57f9fbf34 42: onsuccess: 2: Successful build after gcc: 2 commits new 7265243ca3 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new 9079eb6153 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 7dc8d3ad0c 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 99414ffb58 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 9aaae91f17 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 783c0a95c6 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 23c0093c7f 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 7b1eabe879 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new e0e6b93d1e 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new e395d01525 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new d7fb3b1bae 53: onsuccess: 2: Successful build after gcc: 5 commits new cbb10b069d 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 7ea9f74759 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 9fb14eb516 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 0287519306 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 642e925d0b 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new 7c9f5431b8 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 45c0982a55 60: onsuccess: 1: Successful build after gcc: 15 commits new 2acb023cd7 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 568124093a 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new fd380a846d 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 96dfbb09b2 64: onsuccess: 2: Successful build after gcc: 7 commits new ce2f15b886 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new c2c62e42d3 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 72b8c6ba0b 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 08039a1d95 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 996bb27a4d 69: onsuccess: 2: Successful build after baseline build: no [...] new b33c8c1179 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 059ce9ed9b 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 4ab963fc8f 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new c0d812344d 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 6759deea25 74: onsuccess: 2: Successful build after gcc: 13 commits new c304604157 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 473f39f96f 76: onsuccess: 2: Successful build after binutils: 10 commits new edf9a5d3e8 77: force: 2: Successful build after gcc: 32 commits new 390b05b763 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 382f4385b5 79: onsuccess: 1: Successful build after gcc: 3 commits new 118a251837 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new c56192c0e8 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 65af30eaf0 82: onsuccess: 2: Success after binutils/gcc: 26 commits new a3f38e23c4 83: onsuccess: 2: Success after binutils/gcc: 7 commits new e0a0bf5ab0 84: onsuccess: 2: Success after gcc: 9 commits new ba17908229 85: onsuccess: 2: Success after binutils: 4 commits new 8cc79ed589 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new 6a7a9ece7b 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new 28473a9e1d 88: onsuccess: 1: Success after gcc: 20 commits new 758defe244 89: onsuccess: 2: Success after binutils/gcc: 39 commits new ab8631dbec 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 70325ee7ec 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 070c49eee1 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 9df746e28e 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new 23d965b120 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new a1d5a7b0d8 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 986d2f10fd 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 45d029a8a0 97: onsuccess: #1481: 2: Success after gcc: 8 commits new c5a30e5165 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 689e01f8d3 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new fef9c66a8c 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new 27401e0b22 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new 1a7056d6a8 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 60e317c33a 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 6097baf243 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 4b89932f99 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 69acec3b3a 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 57daae923c 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new 42ca8858aa 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 7b345b8bca 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 5f07e7e53d 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 4faa51dd38 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 6bbbf0e3e6 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 1f7107c5ed 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new 4b032b4264 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new ba649c2ed0 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 21d5b5bff8 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new ed9de38f17 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new f0a73ca4be 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 58fe5df83c 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new 4e5eaba729 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 112567d1ed 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new 62279aa9ea 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new d09294dea1 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 5c8b362a8e 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new 1f0ffb622f 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new 35d0158942 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new 0f7ab13959 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new 98766bb3bf 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new e9013dc6ca 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new 38d436c58e 130: onsuccess: #1554: 2: Success after gcc: 9 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (19c0dfe7c4) \ 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 1704 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2704 bytes 04-build_abe-binutils/console.log.xz | Bin 38480 -> 37872 bytes 05-build_abe-bootstrap/console.log.xz | Bin 269656 -> 270644 bytes 06-check_regression/console.log.xz | Bin 2544 -> 2652 bytes 07-update_baseline/console.log | 64 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 ++++---- 12 files changed, 44 insertions(+), 44 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

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

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 2497bdd529 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards 772a97f10a 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 6752428391 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards ca288f599c 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 86d564aea0 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 9ed3b0bca4 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards f8eb5b43b1 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards cf831a875c 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards e66628799f 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 8325c31952 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards e4d87b6994 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 55f333a68f 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 8cd74f83c9 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 57033a3ba8 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 9e19967eec 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 52f5d6b51d 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 4e664056b3 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 53a8685fb5 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 15382952af 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 19b9ce2758 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 2c37ffa5b6 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards cf47aa6649 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 0a8dcd6199 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 277585c6c0 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 140eea1175 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 7dd8362d91 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 8c633eb6a8 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 88a64f7c6c 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards ef76209f77 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 2294bcbb6a 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards f47c003318 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 4769ead859 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 9b5a4d338e 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 05c1c9f9b3 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards c69f894461 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 985658f8b2 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards 7e978551e9 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 2d6a1740e4 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards a7154827cc 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 62820e8a4c 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 118c92c166 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 9e99e7016a 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 380bef85d6 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 3e04d6afee 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 2f61d36b8e 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards d65e6ec9c4 85: onsuccess: 7: Success after gcc: 9 commits discards 0f6dde9cc8 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 1a23392a68 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards c972943ce6 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 99f845d3e2 81: onsuccess: 7: Successful build after gcc: 2 commits discards c7ed6593a2 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 643c78a01c 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 03e057c6f5 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e85cea04ce 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 5c50d9431d 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9e5c751bb9 75: onsuccess: 7: Successful build after linux: 44 commits discards 50f74377af 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 69f8dee4c7 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 2eda71f8e0 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 8586ae4981 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 6bf1546b05 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards ff3671aa0e 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 2880e03ceb 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 45db088d30 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 0dfe2f10a9 66: onsuccess: 7: Successful build after gcc: 3 commits discards 88c936e152 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9eb0d11084 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3d50205a63 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards c9c5e2f701 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 4ad7165232 61: onsuccess: 4: Successful build after gcc: 15 commits discards 8827000a17 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards eebbc26355 59: force: 7: Successful build after gcc: 2 commits discards 3cd2ca20af 58: onsuccess: 7: Successful build after glibc: 2 commits discards 2c543d59d2 57: onsuccess: 7: Successful build after gcc: 7 commits discards 3723cd04ad 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 20c8c359d0 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards eb51c54de8 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 26cc08f049 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 692d6e6a39 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 2f090fbf4d 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 0fec386dc2 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3f613d92b2 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 86f02aa171 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 49fdc0ab9c 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a381ba8387 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 88b0db44a8 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 1462e386cd 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards c620ed0149 43: onsuccess: 7: Successful build after gcc: 2 commits discards 9477a0aa3c 42: onsuccess: 7: Successful build after baseline build: no [...] discards 757b2e4881 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0e6b3cc20f 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5429d1bf4c 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] discards 7497439294 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards 2da5d325dc 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 93c351a8e8 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 615e76c186 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 4c1a952953 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 19fff32746 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 041863610f 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 4ee07e3586 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards d413b578d2 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 1e9740ce7a 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 1d6416748f 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new b142479b31 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new f76cfc0a5d 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ac22eea767 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 98eb8c69e1 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 3553f69bff 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7eb295776f 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new be1517c511 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new 7823bb2a2b 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] new 36c1b27012 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5533938f74 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2f083f1565 42: onsuccess: 7: Successful build after baseline build: no [...] new d297bfbcfc 43: onsuccess: 7: Successful build after gcc: 2 commits new 65e2884140 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new 6c41c189c4 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 00f09a090e 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 51277a49a4 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 160e3f1310 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 3f515510d7 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 9b35556c26 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new dcad784a09 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new dd625d615e 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 05d5babf0e 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 8e83c215e0 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new eee173cf6f 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new dd436f2cc1 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a6d536ed4c 57: onsuccess: 7: Successful build after gcc: 7 commits new 5939679569 58: onsuccess: 7: Successful build after glibc: 2 commits new cd668fb2ec 59: force: 7: Successful build after gcc: 2 commits new 62de5c91ae 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new bd9f414984 61: onsuccess: 4: Successful build after gcc: 15 commits new 442576a561 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new ad841ad949 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 221b15db2b 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7d044deca1 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a828ff0593 66: onsuccess: 7: Successful build after gcc: 3 commits new 0703adde91 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 94dc71ffc8 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7e1325111f 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new e753b9f0a8 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new da89b58989 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 31e38e44d8 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new f5761fe857 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 39d33b5b52 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 6b35f07894 75: onsuccess: 7: Successful build after linux: 44 commits new 2b3e5046bb 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 94569324a2 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new b8a276a6da 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5f47f9a498 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new e22adbd233 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 758b7b89ff 81: onsuccess: 7: Successful build after gcc: 2 commits new 2cfd9c61e0 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 2d294ab7e0 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 11be3c1f5e 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 408029bc56 85: onsuccess: 7: Success after gcc: 9 commits new 865c4ee736 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 781a46c8ec 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 32e329ea04 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 3f330995c2 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 5b4b016c1d 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new a8271e65c1 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 4e42fa77bd 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new af5a9f33a8 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new f151ff60f4 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 62f4042d0d 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 46b6074af0 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 78c45af23b 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 09d32cbbd4 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new eae5d75b4c 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 59a14b5d03 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new a9d2251f4a 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 73f8323105 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 56d3aeb128 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new a9748c3db1 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new a6e2b7b719 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 07628522f4 106: onsuccess: #1617: 7: Success after gcc: 2 commits new e0b7d351da 107: onsuccess: #1618: 7: Success after gcc: 2 commits new af574cb26a 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new a11a903945 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 6a7a0a131a 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new c6e145c010 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new a9a3b8c0bd 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 625b9bf35e 113: onsuccess: #1624: 7: Success after gcc: 6 commits new fc7994916e 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 5040589b9b 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 6f9d533bbf 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new c36520b8bf 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new fcc1dd7376 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new e4b6e6f284 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 69917f9ee3 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 9e4c70cee6 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new e5079fd19e 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new d9d0449dd7 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 8665bac49c 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new d7f6483702 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new e0194d8fe9 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new 50698bd306 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 9c5f36755d 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 10c7089309 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new a3711e93cc 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 53d946af28 131: onsuccess: #1644: 7: Success after gcc: 10 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 (2497bdd529) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1684 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2752 bytes 04-build_abe-binutils/console.log.xz | Bin 29916 -> 29844 bytes 05-build_abe-stage1/console.log.xz | Bin 90664 -> 91032 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8680 -> 8904 bytes 08-build_abe-glibc/console.log.xz | Bin 234080 -> 236056 bytes 09-build_abe-stage2/console.log.xz | Bin 222984 -> 228760 bytes 10-build_abe-gdb/console.log.xz | Bin 37056 -> 37956 bytes 11-build_abe-qemu/console.log.xz | Bin 30924 -> 31116 bytes 12-check_regression/console.log.xz | Bin 3900 -> 3348 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +++++++------- 18 files changed, 51 insertions(+), 51 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto_lean updated (b0acb2ad2d -> 1e7e197974)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto_lean in repository toolchain/ci/base-artifacts. from b0acb2ad2d 43: onsuccess: #420: 2: Success after binutils/gcc: 134 commits new 1e7e197974 44: onsuccess: #421: 2: Success after binutils/gcc: 11 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 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 50252 -> 50080 bytes .../console.log.xz | Bin 946072 -> 941532 bytes 06-check_regression/console.log.xz | Bin 3124 -> 3076 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 12 files changed, 15 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-lts-defconfig updated (d92b61de57 -> 0f71275924)

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-lts-defconfig in repository toolchain/ci/base-artifacts. from d92b61de57 11: onsuccess: #413: boot: Success after binutils/gcc/linux/ [...] new 0f71275924 12: onsuccess: #414: boot: Success after binutils/gcc/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1680 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30032 -> 29884 bytes 04-build_abe-stage1/console.log.xz | Bin 87080 -> 86288 bytes 05-build_abe-qemu/console.log.xz | Bin 31292 -> 31048 bytes 06-build_linux/console.log.xz | Bin 3352 -> 3308 bytes 07-boot_linux/console.log.xz | Bin 5792 -> 5796 bytes 08-check_regression/console.log.xz | Bin 3120 -> 4148 bytes 09-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 31 ++++++++++++++++--------------- 18 files changed, 24 insertions(+), 32 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-norov-allmodconfig updated (da63b00dc9 -> 92237214a6)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-norov-allmodconfig in repository toolchain/ci/base-artifacts. from da63b00dc9 12: onsuccess: #49: boot: Success after binutils/gcc/qemu: 1 [...] new 92237214a6 13: onsuccess: #50: boot: Success after linux: 4 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 1708 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 30244 -> 30740 bytes 04-build_abe-stage1/console.log.xz | Bin 68316 -> 68852 bytes 05-build_abe-qemu/console.log.xz | Bin 31408 -> 31264 bytes 06-build_linux/console.log.xz | Bin 3552 -> 3312 bytes 07-boot_linux/console.log.xz | Bin 508 -> 508 bytes 08-check_regression/console.log.xz | Bin 3656 -> 2824 bytes dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +++++++++----------- 14 files changed, 14 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_apm/gnu-release-arm-spec2k6-Os updated (dea382b285 -> 812389e44a)

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_apm/gnu-release-arm-spec2k6-Os in repository toolchain/ci/base-artifacts. from dea382b285 11: onsuccess: #93: 1: [TCWG CI] No change after binutils/gc [...] new 812389e44a 12: onsuccess: #94: 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 1940 -> 1912 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 30224 -> 31440 bytes 04-build_abe-stage1/console.log.xz | Bin 88496 -> 90480 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-linux/console.log.xz | Bin 7872 -> 8672 bytes 07-build_abe-glibc/console.log.xz | Bin 231780 -> 233300 bytes 08-build_abe-stage2/console.log.xz | Bin 209472 -> 217288 bytes 09-benchmark/benchmark-build.log | 102 +- 09-benchmark/benchmark.log | 100 +- 09-benchmark/console.log.xz | Bin 3800 -> 3716 bytes 10-check_regression/console.log.xz | Bin 10032 -> 13760 bytes 10-check_regression/csv-results-0/md5sum.csv | 44562 +- 10-check_regression/csv-results-0/perf.csv | 3983 +- 10-check_regression/csv-results-0/results.csv | 741108 +++++++++-------- 10-check_regression/csv-results-0/size.csv | 740034 ++++++++--------- 10-check_regression/csv-results-0/vect.csv | 38 +- 10-check_regression/csv-results-1/md5sum.csv | 44542 +- 10-check_regression/csv-results-1/perf.csv | 3743 +- 10-check_regression/csv-results-1/results.csv | 741134 +++++++++--------- 10-check_regression/csv-results-1/size.csv | 740239 ++++++++--------- 10-check_regression/csv-results-1/vect.csv | 34 +- 10-check_regression/results-brief.csv | 60 +- 10-check_regression/results-compare.csv | 9 +- 10-check_regression/results-full.csv | 3903 +- 10-check_regression/results-internal.csv | 245 +- 10-check_regression/results.csv | 245 +- 10-check_regression/results.log | 1598 +- 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-metadata.json | 16 +- dashboard/squad/403.gcc/results-metrics.json | 2 +- 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 | 2 +- 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-metadata.json | 16 +- dashboard/squad/Mean/results-metrics.json | 2 +- dashboard/squad/dashboard-push-squad.sh | 122 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 47 +- mail/mail-body.txt | 47 +- mail/mail-subject.txt | 2 +- manifest.sh | 35 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 1262608 -> 1267252 bytes save-temps/401.bzip2.tar.xz | Bin 92092 -> 91900 bytes save-temps/403.gcc.tar.xz | Bin 3564200 -> 3556012 bytes save-temps/410.bwaves.tar.xz | Bin 15112 -> 15168 bytes save-temps/416.gamess.tar.xz | Bin 4122724 -> 4119896 bytes save-temps/429.mcf.tar.xz | Bin 36204 -> 36352 bytes save-temps/433.milc.tar.xz | Bin 163852 -> 163844 bytes save-temps/434.zeusmp.tar.xz | Bin 128060 -> 128052 bytes save-temps/435.gromacs.tar.xz | Bin 952420 -> 951240 bytes save-temps/436.cactusADM.tar.xz | Bin 710488 -> 711824 bytes save-temps/437.leslie3d.tar.xz | Bin 47756 -> 47636 bytes save-temps/444.namd.tar.xz | Bin 198896 -> 198696 bytes save-temps/445.gobmk.tar.xz | Bin 1819228 -> 1836960 bytes save-temps/447.dealII.tar.xz | Bin 6562852 -> 6333984 bytes save-temps/450.soplex.tar.xz | Bin 704024 -> 690936 bytes save-temps/453.povray.tar.xz | Bin 1389996 -> 1393800 bytes save-temps/454.calculix.tar.xz | Bin 1233680 -> 1232540 bytes save-temps/456.hmmer.tar.xz | Bin 368656 -> 368712 bytes save-temps/458.sjeng.tar.xz | Bin 145608 -> 145996 bytes save-temps/459.GemsFDTD.tar.xz | Bin 148708 -> 148696 bytes save-temps/462.libquantum.tar.xz | Bin 61104 -> 61316 bytes save-temps/464.h264ref.tar.xz | Bin 561196 -> 559848 bytes save-temps/465.tonto.tar.xz | Bin 2030404 -> 2034344 bytes save-temps/470.lbm.tar.xz | Bin 26840 -> 26792 bytes save-temps/471.omnetpp.tar.xz | Bin 1074688 -> 1048080 bytes save-temps/473.astar.tar.xz | Bin 85804 -> 86132 bytes save-temps/481.wrf.tar.xz | Bin 1545148 -> 1562624 bytes save-temps/482.sphinx3.tar.xz | Bin 247656 -> 247160 bytes save-temps/483.xalancbmk.tar.xz | Bin 11545220 -> 11777560 bytes 128 files changed, 1491893 insertions(+), 1574591 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-stable-allyesconfig updated (da139251af -> e3028dd695)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-stable-allyesconfig in repository toolchain/ci/base-artifacts. from da139251af 9: onsuccess: #363: all: Success after binutils/gcc/linux/qe [...] new e3028dd695 10: onsuccess: #364: all: Success after binutils/gcc/linux/q [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1720 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30192 -> 30132 bytes 04-build_abe-stage1/console.log.xz | Bin 69036 -> 68192 bytes 05-build_abe-qemu/console.log.xz | Bin 31748 -> 31196 bytes 06-build_linux/console.log.xz | Bin 3340 -> 3308 bytes 07-boot_linux/console.log.xz | Bin 576 -> 576 bytes 08-check_regression/console.log.xz | Bin 3200 -> 4136 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 31 ++++++++++++++++--------------- 18 files changed, 28 insertions(+), 27 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (e012b164c2 -> ca95f79b66)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards e012b164c2 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 0d6f3b3424 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards d407511537 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 90a70b1978 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 9f0ca6bf5a 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards f8a8a85fa2 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards 0713343689 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards e5be7010b4 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards 8e6bf4eca3 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards 71e888742c 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 485ad4feaa 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards ba167c833d 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 800b3ee5cc 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards db045e698f 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards 48a99dbf40 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards 009e64ff58 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards bdea128f5c 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards e69c08385e 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards c7f7d11ce2 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 2ee80e4ede 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards acfa5aec58 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 207dac4f62 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards b107429fe3 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards b9b81590d3 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards e90ad43acf 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards e3120cc6e1 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards b25bb63059 102: force: #1551: 1: Failure after gcc: 306 commits discards 918407a6ef 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 40cfb2b101 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards caf407d243 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 85bc4c940d 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 961141b493 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards dc5a2c6223 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards a11120507e 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards c4ebecb362 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 7b5f27fd8d 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 5b09d97acb 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards ac74e5c3ee 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards bbbfbf0f7f 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards c42e170ff4 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 7862f3fa7c 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards c05344c47f 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 83ca9fe1d5 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards a996d1dbe3 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards de2f9cce79 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards e2765fff6e 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 246d8c5b77 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 09440bdee7 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a0d9d16504 80: onsuccess: 7: Successful build after linux: 44 commits discards 5e150d264b 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards f317006cbc 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards 820008639b 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards df34a10de3 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 6207947940 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 074a7fce57 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards a4dfdfa28f 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c7e23ccdda 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 942925e369 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 1a613c3dc7 70: onsuccess: 7: Successful build after gcc: 4 commits discards c09b91b69f 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 45dd3679af 68: onsuccess: 7: Successful build after linux: 6 commits discards 6af0b033a0 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards af166dcda4 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards b27a9d6c5e 65: onsuccess: 7: Successful build after binutils: 3 commits discards 900925efdb 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 27fe076dea 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 7c85e6f84d 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 299779bc47 61: onsuccess: 4: Successful build after gcc: 5 commits discards b7b929baf6 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 5345fade0f 59: force: 7: Successful build after gcc: 3 commits discards 91790c1855 58: onsuccess: 7: Successful build after glibc: 2 commits discards 36087ee4c5 57: onsuccess: 7: Successful build after gcc: 7 commits discards aa1449e144 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 1eb2693228 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ac8a632bff 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards 7ba4c1c9ca 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards b088786332 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] discards 186e8a99f1 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 461067f3c9 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0c343a96d1 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards c24d70ac6d 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 81c8caac9e 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 377b6d738f 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards d540c29a91 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5edea25a56 44: onsuccess: 7: Successful build after linux: 34 commits discards 6768f59394 43: onsuccess: 7: Successful build after gcc: 2 commits discards 97ba4d8fe2 42: onsuccess: 7: Successful build after baseline build: no [...] discards 8183ac159b 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards da6f8f290e 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d739cfd2b8 39: onsuccess: 7: Successful build after gcc: 2 commits discards 765cdb81c9 38: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 8025da8073 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards d11fe8d159 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0ae8ec12d1 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 0202adb888 34: onsuccess: 7: Successful build after gcc: 3 commits discards fe616a910d 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b5a243faf0 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 5dafa82cf2 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards fd7c8609d1 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits discards 51c1b7b10e 29: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f40536a059 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 74d85347ed 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 7509970261 29: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 300cc8ef9a 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits new 20c4ca05c7 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 4693c26590 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new eeb3f12dee 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 09bb872183 34: onsuccess: 7: Successful build after gcc: 3 commits new cfe409366f 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 9790ede080 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new abcbcc7983 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 13e13a66a0 38: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4e6b5e90f0 39: onsuccess: 7: Successful build after gcc: 2 commits new b20dc5da0e 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8dbc407ac2 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b0d4c7dbbb 42: onsuccess: 7: Successful build after baseline build: no [...] new 61322deda4 43: onsuccess: 7: Successful build after gcc: 2 commits new 98ef612f7d 44: onsuccess: 7: Successful build after linux: 34 commits new f8b694b370 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5e2d07df28 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new d548316637 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 11794c82de 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new f8b6dbd747 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 404e200bde 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 3fa194aa93 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 3803799d9f 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new 3502aec9aa 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new aec412c1ee 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new d58144880b 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 1074e6abea 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8b77e21ed5 57: onsuccess: 7: Successful build after gcc: 7 commits new aded931c18 58: onsuccess: 7: Successful build after glibc: 2 commits new d78bfabca5 59: force: 7: Successful build after gcc: 3 commits new 477134ca9a 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 674c36fedf 61: onsuccess: 4: Successful build after gcc: 5 commits new e0928092ce 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 1f0312533c 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new f088c290b2 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 258ead2995 65: onsuccess: 7: Successful build after binutils: 3 commits new db2e32df52 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new f6539e43ab 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new c511bcf010 68: onsuccess: 7: Successful build after linux: 6 commits new 074e2da577 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 3d29203a29 70: onsuccess: 7: Successful build after gcc: 4 commits new dbbc7c0320 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 5b6f11a82c 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7c02988889 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ea99c540ae 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new a267410d39 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 4df4603892 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 87542fdc29 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new db86134b9d 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new 86eae7364e 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 9f5d07bd5d 80: onsuccess: 7: Successful build after linux: 44 commits new 92ad34e23e 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new da43a8af34 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 342837637d 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 3ee17bf7d4 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new a931702704 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 1b1798a004 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 56fb1791ff 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 33ab75e1a1 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 48227aaf6d 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 39a377caae 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 273ea26576 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new bc8e598c8a 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new c7c78534a7 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 62d34196c7 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new de8971b835 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new fd9d7805ab 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new e497999000 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 7f860b0fd0 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 3753a522cc 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new a6e9a67308 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 1b5bf776bb 101: onsuccess: #1547: 7: Success after binutils: 82 commits new e70c2e82fc 102: force: #1551: 1: Failure after gcc: 306 commits new 1c929846b0 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 44fe3356b9 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new ef078aaea6 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 1d5037c066 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 638ed799d2 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new 0d9f32df1c 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new f3c7b27641 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new e4495326bd 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 1443b52311 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new 7ddbb56819 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 64595bbe6b 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new 12039e9c13 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 0791a31bf4 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 1497af804d 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 3d65a29e1e 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new ed586d4e0f 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new 1591a2e593 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new 7e35c0e1be 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 1edd83242b 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new b93a5fd338 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 8065e496e9 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new 3b2671ca84 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 0a22702575 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 6f5c726a02 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 6da3aadaa4 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new 19a676d4d5 128: onsuccess: #1579: 7: Success after linux: 12 commits new ca95f79b66 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] 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 (e012b164c2) \ 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 1632 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 30776 -> 30432 bytes 05-build_abe-stage1/console.log.xz | Bin 73132 -> 72836 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 8764 -> 8708 bytes 08-build_abe-glibc/console.log.xz | Bin 242192 -> 240056 bytes 09-build_abe-stage2/console.log.xz | Bin 205320 -> 203056 bytes 10-build_abe-gdb/console.log.xz | Bin 37584 -> 37452 bytes 11-build_abe-qemu/console.log.xz | Bin 32068 -> 31532 bytes 12-check_regression/console.log.xz | Bin 3668 -> 3280 bytes 13-update_baseline/console.log | 68 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 ++++++------ 18 files changed, 50 insertions(+), 50 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allmodconfig updated (d6628e3f4b -> 866ea98f4d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allmodconfig in repository toolchain/ci/base-artifacts. from d6628e3f4b 15: onsuccess: #477: 23109: Success after binutils/llvm/linu [...] new 866ea98f4d 16: onsuccess: #480: 23121: Success after linux: 1668 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 1700 -> 1648 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30060 -> 30240 bytes 04-build_kernel_llvm/console.log.xz | Bin 63308 -> 63644 bytes 05-build_abe-qemu/console.log.xz | Bin 31040 -> 31084 bytes 06-build_linux/console.log.xz | Bin 5528 -> 5640 bytes 08-check_regression/console.log.xz | Bin 3472 -> 3100 bytes 08-check_regression/mail-body.txt | 4 ++-- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 24 +++++++++++------------- results | 2 +- 15 files changed, 21 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022