Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (0d66c74d98 -> 55599fee0a)

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 0d66c74d98 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qemu [...] discards 42adcf985a 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 12 [...] discards d24d4122bd 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/g [...] discards 371ed52910 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/g [...] discards 1eb1a28ea8 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/g [...] discards a6035a464f 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 28 [...] discards 6d76e31ed7 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits discards 584b98605c 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/g [...] discards 14f70486e4 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/g [...] discards 758a0b6626 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 12 [...] discards 4406b269b2 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 commits discards 15e07e8ec6 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/g [...] discards ea82f78840 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 3a52d47428 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards 1003bcb93c 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] discards 999146f1a8 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards 59bdecb743 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards 76e68331e8 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] discards 610f7d7fff 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards a77990f9c2 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] discards 83c1f6d599 152: force: #1605: 7: Success after gcc: 9 commits discards df9ba1d28b 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] discards 8ec53698af 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] discards 17c4004119 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards 4f8edbb851 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards b993efa7ed 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards aac116e446 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards c7d1c06283 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards 641b50a005 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 5a5a263d09 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards a9c3668fb7 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards 83446e7ac1 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 720a19f7b4 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards be2ee38b6b 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards 6c90f1ee79 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards aedf058e53 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards fca823aaed 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards 79ab32c562 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards 28c3ede4e5 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 2a334b9a89 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards cdf75d7ae4 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards 822c6f6d74 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 6cd7d8a043 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards ff0cc1391e 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards d74682edf8 128: onsuccess: #1579: 7: Success after linux: 12 commits discards a8de92bd4d 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards ee4d13ac70 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 5e5111e521 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 9b308789e2 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 95d406b44b 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards 1fd4bd05d5 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards e0c591815e 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards 76d10da40b 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards 884f1be649 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards a3d6615167 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards a2c09bc795 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 1fd7e50042 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 23120c93ce 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards 2c0ab98b82 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards a18cf9bd5b 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards c8c3a29e38 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards 65119e6c65 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 1b1997cfb1 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 79d9768f6a 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 4173202296 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 0fda713328 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards f9285ad0f7 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 065985731f 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards ea9870a6bc 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards 1acfd10450 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards d934383981 102: force: #1551: 1: Failure after gcc: 306 commits discards 497015c96a 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards f2e1168d91 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 2a2a2cc916 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards d13234e16b 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards b6cfa2dffd 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards ff4601da5e 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 043710de68 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 85daf3ca66 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 1932e916d6 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 465857824c 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 29f9cd9903 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 19feae01c1 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 4de2315300 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 265e70cdb0 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 80b38628c6 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 38193ff04e 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards f1b730501a 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 288bcf3a5e 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards d89b024d4f 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b8d2bc38cd 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards e14697528b 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e79db04bd9 80: onsuccess: 7: Successful build after linux: 44 commits discards 0d3e755bdb 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards fa27a6787d 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards ab54c9b753 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ad369033a5 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 1694f0a2c1 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 9cce23a7c3 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 08f205557b 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7bc5b0545b 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 46812b4404 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5711e65bfb 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 0c4cdfc886 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 46b22b25a1 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 96cf1860c3 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new cd2e11361b 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 66bdb8bcff 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new 2f7a66c464 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 77873f1952 80: onsuccess: 7: Successful build after linux: 44 commits new de73a30ae5 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 43137fcca5 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 5fb47d9bdd 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6c6eb1f5d2 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new d5f1f00dd9 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new be7da74736 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 563b680a6f 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 283b4df5db 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new aea60206eb 89: onsuccess: 7: Success after gcc/glibc: 8 commits new a5cee26123 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 423aed9ba2 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new f9630ab2ca 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 97674b7637 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new ff37ba14c7 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 311d83b597 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 495e60c264 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new a9955bb08b 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 7dbec5fdaa 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new ad553417fe 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 6bcf73b5a7 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new a017bf66f7 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 6e47ff6b85 102: force: #1551: 1: Failure after gcc: 306 commits new 83c0b44f54 103: onsuccess: #1552: 1: Success after gcc: 5 commits new e1484e19ce 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new c40c5643b9 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 342bd2ec83 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 85845c5981 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new 7d4285f078 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new 22972762da 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 49be4203a5 110: onsuccess: #1559: 7: Success after gcc: 4 commits new e41bdef7ec 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new c154ab3f5b 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 4249da771b 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new c137ec8e0c 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 3870116403 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 82670c4393 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new e931a8c75d 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 904babfa9c 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new bff0b11d34 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new 5b7ac27b2f 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 97c07b57f0 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 81432bdc99 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 0d059a7146 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new 2033bf66d6 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 256b90d01c 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 188170e654 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new e27cffdc6e 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new bfa63fc8ab 128: onsuccess: #1579: 7: Success after linux: 12 commits new 841ddaea60 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new b6a796295b 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new bc20f0408c 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new b7a6ff54b6 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 71d8269688 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new 02da0d748b 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new 2975f36bfb 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new 7c057d15a4 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new 269ad3878d 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 2a1b6f18be 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new eefcbc64fc 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new c363410d26 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new 5f2e2798d0 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new 7d37d0a046 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new 0deb2976b4 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new ce029eacdd 144: onsuccess: #1595: 7: Success after glibc: 2 commits new bbcfae936f 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new 16d2b53831 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new 11e80116b6 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new 0b1810b112 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new 419ae3b2b1 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new 57382b3a0b 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] new db1913afaa 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] new 6e82a9815e 152: force: #1605: 7: Success after gcc: 9 commits new 51205d8fde 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] new 37ac34866c 154: onsuccess: #1607: 1: Success after gcc: 2 commits new 8480a03eab 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] new 6c4149ec97 156: onsuccess: #1609: 7: Success after gcc: 2 commits new 7479e50169 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new f075061a41 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] new ee52547fe1 159: onsuccess: #1612: 7: Success after gcc: 4 commits new 9464ed7eef 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 3aa548932a 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/g [...] new 7b67bfefbe 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 commits new 31d98f9783 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 12 [...] new cc8051803f 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/g [...] new 349a1e0920 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/g [...] new 49e3317ef8 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits new 61928365cf 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 28 [...] new ecb122c206 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/g [...] new 0f9f2e4845 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/g [...] new 3cbf8c61ca 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/g [...] new 28ef16bae6 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 12 [...] new a1a13316ee 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qemu [...] new 55599fee0a 173: onsuccess: #1626: 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 (0d66c74d98) \ 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 1680 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30900 -> 30264 bytes 05-build_abe-stage1/console.log.xz | Bin 73488 -> 72408 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 11232 -> 9432 bytes 08-build_abe-glibc/console.log.xz | Bin 240268 -> 239956 bytes 09-build_abe-stage2/console.log.xz | Bin 207028 -> 203392 bytes 10-build_abe-gdb/console.log.xz | Bin 38008 -> 37428 bytes 11-build_abe-qemu/console.log.xz | Bin 31520 -> 31128 bytes 12-check_regression/console.log.xz | Bin 4640 -> 4588 bytes 13-update_baseline/console.log | 42 +++++++++++++++++------------------ 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, 51 insertions(+), 51 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (13682e4d8e -> ec2e0f0968)

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 13682e4d8e 166: onsuccess: #2102: 1: Success after gcc: 11 commits discards 563c0f907d 165: onsuccess: #2101: 1: Success after binutils/gcc: 8 commits discards d8a58a110f 164: onsuccess: #2100: 1: Success after binutils/gcc: 15 commits discards 2626c4923e 163: onsuccess: #2098: 1: Success after binutils/gcc: 18 commits discards 79bd4078f4 162: onsuccess: #2097: 1: Success after binutils/gcc: 16 commits discards 56746cf791 161: onsuccess: #2096: 1: Success after gcc: 2 commits discards ea1235e66f 160: onsuccess: #2095: 1: Success after binutils/gcc: 4 commits discards 190accb14d 159: onsuccess: #2094: 1: Success after binutils/gcc: 23 commits discards 8beca4be58 158: onsuccess: #2093: 1: Success after binutils/gcc: 9 commits discards aad57b1a49 157: onsuccess: #2092: 1: Success after binutils/gcc: 3 commits discards 1ed6c636c4 156: onsuccess: #2091: 1: Success after binutils/gcc: 2 commits discards 9eb6317f96 155: onsuccess: #2090: 1: Success after binutils/gcc: 22 commits discards 4f99d6df7f 154: onsuccess: #2089: 1: Success after gcc: 4 commits discards 28bd083238 153: onsuccess: #2088: 1: Success after basepoints/gcc-13-30 [...] discards 1097c597ef 152: onsuccess: #2087: 1: Success after gdb-12-branchpoint-2 [...] discards fda1035a62 151: onsuccess: #2086: 1: Success after gcc: 2 commits discards 826105a016 150: onsuccess: #2085: 1: Success after gcc: 2 commits discards 2763a3e15b 149: onsuccess: #2084: 1: Success after gcc: 16 commits discards 4549d215ad 148: onsuccess: #2082: 1: Success after gdb-12-branchpoint-2 [...] discards b68d725af7 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 commits discards 18bdd24f41 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits discards 5dfccc1c94 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits discards 2537375ca3 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits discards c3fd0712a6 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits discards 2a620b38fd 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits discards 185a6f7dfa 141: onsuccess: #2073: 1: Success after binutils: 3 commits discards a176ade7fc 140: onsuccess: #2070: 1: Success after binutils: 4 commits discards 5cba473ac4 139: onsuccess: #2067: 1: Success after binutils: 2 commits discards 6e1310aff3 138: onsuccess: #2064: 1: Success after binutils: 4 commits discards 7fc5914fb9 137: onsuccess: #2061: 1: Success after binutils: 2 commits discards 1e3117b0ab 136: onsuccess: #2056: 1: Success after binutils: 4 commits discards d3ddf74d0d 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits discards b2fbe20a09 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits discards 25ddaded79 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits discards 7c1c064ae6 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits discards 8c0ac09782 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] discards 9f0ffd90ad 130: onsuccess: #2049: 1: Success after gcc: 9 commits discards 4f54b9499e 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] discards db63aed447 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] discards 9b226d8b7b 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] discards cbc456a34c 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] discards 6c1a5cde85 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits discards 7f6da0e2a8 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits discards 8c7ebf4d16 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits discards 085b25861d 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits discards 5d54539033 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits discards 8299775811 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits discards 1633aeff83 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits discards 4a6b589d13 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits discards 356bbd3f9e 117: onsuccess: #2034: 1: Success after binutils: 2 commits discards 5021d1c364 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits discards 2a136f7eef 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits discards f0a10104be 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits discards b3c7819701 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits discards 16b5f6eb21 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits discards c620ccf87f 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits discards 30c62311fc 110: onsuccess: #2027: 1: Success after gcc: 5 commits discards c723c29cf5 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits discards 070ef53c2d 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits discards f4b8218ee5 107: onsuccess: #2024: 1: Success after gcc: 3 commits discards baacadffb4 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits discards 953789f22d 105: onsuccess: #2022: 1: Success after gcc: 4 commits discards 777bb3f15f 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards 33774ff7a3 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards b7fadd13a3 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] discards 20d3e368ef 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards 69c15dc90d 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards 46bc40e336 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards 8d0ddd832f 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards 2bc0c185db 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards 5a7e2bc616 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] discards c591ce7415 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] discards 67536003c3 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards f50fc082f2 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] discards 5f3963b973 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards d460eee54e 91: onsuccess: 1: Success after gcc: Daily bump. discards 1385fe03b2 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards ed246ac1e2 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards 5666f51e10 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards d300f6bfb4 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards 10670e1ecd 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards 212f872325 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards b979e56696 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards efedee2560 83: onsuccess: 1: Success after gcc: 8 commits discards 7e2560c085 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards 26dc460e09 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards 142f565d9b 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards 1c63cf44db 79: onsuccess: 1: Successful build after gcc: Daily bump. discards ae7803ddcb 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 3b8a90afa2 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards ab0b00db2e 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards ea23d2cff5 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 72a3fc0378 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards b9779963bc 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards 60c22fc52d 72: onsuccess: 1: Successful build after gcc: 2 commits discards e534d62e8b 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 4877101bc3 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards f8a7c14854 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 2ac15fa939 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards f10eb45a3c 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards d4338b740c 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new c69db19f0d 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 8296a313a4 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 7dac6353db 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 5e5e50ec5c 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 26d1563831 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new b3e137d4d0 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 239103796c 72: onsuccess: 1: Successful build after gcc: 2 commits new ec349cf804 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 2e340fab8f 74: onsuccess: 1: Successful build after binutils: Automatic [...] new b33e1b47df 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 7e723ae3ed 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 9b23aa4834 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new d56fc9edac 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new cf1ba3976e 79: onsuccess: 1: Successful build after gcc: Daily bump. new 756c3924cc 80: onsuccess: 1: Success after binutils/gcc: 14 commits new 68240b34c9 81: onsuccess: 1: Success after binutils/gcc: 27 commits new f672dab2d0 82: onsuccess: 1: Success after binutils/gcc: 10 commits new e8817049a9 83: onsuccess: 1: Success after gcc: 8 commits new e310e3d447 84: onsuccess: 1: Success after binutils/gcc: 9 commits new ac196ea8d3 85: onsuccess: 1: Success after binutils/gcc: 9 commits new 7cf2f546d9 86: onsuccess: 1: Success after binutils/gcc: 13 commits new 6529c519f7 87: onsuccess: 1: Success after binutils/gcc: 4 commits new 43caae07eb 88: onsuccess: 1: Success after binutils/gcc: 16 commits new 85d68ca7bc 89: onsuccess: 1: Success after binutils/gcc: 9 commits new f23e810148 90: onsuccess: 1: Success after binutils/gcc: 6 commits new f320e1ddaa 91: onsuccess: 1: Success after gcc: Daily bump. new 3949eddcf3 92: onsuccess: #1965: 1: Success after gcc: 2 commits new 4e8ccd7998 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] new ba9cd522ab 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new 799bd00b6f 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] new 8ccbcf7224 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] new 0acd6ebdb5 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new c87cb072d1 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new 3e39128471 99: onsuccess: #1974: 1: Success after gcc: 14 commits new 617e44960b 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new 2e5a62a515 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new c2bbe1db11 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] new accf8d944c 103: onsuccess: #2020: 1: Success after gcc: 2 commits new 81cb20c7d4 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new 2f95eedc83 105: onsuccess: #2022: 1: Success after gcc: 4 commits new aacbc9badd 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits new f8491bfd96 107: onsuccess: #2024: 1: Success after gcc: 3 commits new 9a98edec35 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits new 8701e29893 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits new 1b0ef01c03 110: onsuccess: #2027: 1: Success after gcc: 5 commits new e38eb3197f 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits new a2cc443eef 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits new d31c9dc506 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits new 17792c452c 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits new 6a55260880 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits new ec5170e40c 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits new a3c8277f70 117: onsuccess: #2034: 1: Success after binutils: 2 commits new 3331ccabfb 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits new 4cde5436b9 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits new dd225465d5 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits new 16d35e3169 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits new 46ddb2edc1 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits new ed53194cf5 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits new d23bac384b 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits new 54f9401551 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits new 5f981abc99 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] new 3ab939f35a 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] new b11827488c 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] new eecacd2fbf 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] new c182acb131 130: onsuccess: #2049: 1: Success after gcc: 9 commits new 56bef2c3c2 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] new a2f413a9fa 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits new dac25c6dca 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits new 881ff57f99 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits new 04f3ee8a71 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits new dbaad9e384 136: onsuccess: #2056: 1: Success after binutils: 4 commits new b601f17fa2 137: onsuccess: #2061: 1: Success after binutils: 2 commits new acadd1f361 138: onsuccess: #2064: 1: Success after binutils: 4 commits new f8b7c63a4a 139: onsuccess: #2067: 1: Success after binutils: 2 commits new 39ff30733b 140: onsuccess: #2070: 1: Success after binutils: 4 commits new 7a1a68bcc2 141: onsuccess: #2073: 1: Success after binutils: 3 commits new 7856f9fe12 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits new c527930321 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits new 14ba3f5250 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits new dce6639a43 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits new 16bbd5044e 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits new 66d7c09cd4 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 commits new 50c5bff0a0 148: onsuccess: #2082: 1: Success after gdb-12-branchpoint-2 [...] new 6ad3a4ee7f 149: onsuccess: #2084: 1: Success after gcc: 16 commits new 9c20097e78 150: onsuccess: #2085: 1: Success after gcc: 2 commits new adc8cf14fc 151: onsuccess: #2086: 1: Success after gcc: 2 commits new afadd6773f 152: onsuccess: #2087: 1: Success after gdb-12-branchpoint-2 [...] new 84c478ab73 153: onsuccess: #2088: 1: Success after basepoints/gcc-13-30 [...] new f623914fc7 154: onsuccess: #2089: 1: Success after gcc: 4 commits new ca2f76ef17 155: onsuccess: #2090: 1: Success after binutils/gcc: 22 commits new 92182d04db 156: onsuccess: #2091: 1: Success after binutils/gcc: 2 commits new 3bac186952 157: onsuccess: #2092: 1: Success after binutils/gcc: 3 commits new cc7801e40a 158: onsuccess: #2093: 1: Success after binutils/gcc: 9 commits new 2e7c60592c 159: onsuccess: #2094: 1: Success after binutils/gcc: 23 commits new d963abd5ca 160: onsuccess: #2095: 1: Success after binutils/gcc: 4 commits new 1226dfb400 161: onsuccess: #2096: 1: Success after gcc: 2 commits new 9f36a73fb3 162: onsuccess: #2097: 1: Success after binutils/gcc: 16 commits new 2fc957e903 163: onsuccess: #2098: 1: Success after binutils/gcc: 18 commits new b840302c90 164: onsuccess: #2100: 1: Success after binutils/gcc: 15 commits new 3b7dea9d03 165: onsuccess: #2101: 1: Success after binutils/gcc: 8 commits new fd5def8f98 166: onsuccess: #2102: 1: Success after gcc: 11 commits new ec2e0f0968 167: onsuccess: #2103: 1: Success after binutils/gcc: 7 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 (13682e4d8e) \ 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 1724 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2716 bytes 03-build_abe-binutils/console.log.xz | Bin 38372 -> 37480 bytes 04-build_abe-gcc/console.log.xz | Bin 214616 -> 213288 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3888 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2780 -> 2492 bytes 07-check_regression/console.log.xz | Bin 5848 -> 5344 bytes 07-check_regression/extra-bisect-params | 1 + 07-check_regression/fails.sum | 7 + 07-check_regression/mail-body.txt | 56 +- 07-check_regression/results.compare | 29 +- 07-check_regression/results.compare2 | 302 +- 07-check_regression/results.regressions | 27 + 08-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 58 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 27 + sumfiles/g++.log.xz | Bin 3578920 -> 3557832 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 3118876 -> 3093084 bytes sumfiles/gcc.sum | 4765 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1035172 -> 1044976 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2184 -> 2180 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207516 -> 207340 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2556 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 449860 -> 455248 bytes sumfiles/libstdc++.sum | 12 +- 36 files changed, 2678 insertions(+), 2884 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, 1 month

[dejagnu] branch master updated (0184343 -> d747eee)

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 dejagnu. from 0184343 Change quotes around 'make check' in manual headings adds 369c52e Allow internal unit test names to contain forward slash adds 3554566 Add initial mockvfs support for internal unit tests adds af17601 Add initial unit tests for lib/dg.exp adds 51e4b3f Add unit tests with explicit line numbers for lib/dg.exp adds bbc8691 Avoid needless errors in internal unit test infrastructure adds 1a141d0 Add lib/dg.exp unit tests for skipping files by target adds e4657c2 Add lib/dg.exp unit tests for xfail by target adds ae2a87b Add lib/dg.exp unit tests for skipping files by callback adds e2c7bce Add regression test for PR58065 adds d747eee Buffer test results in case the pruning callback aborts the test No new revisions were added by this update. Summary of changes: ChangeLog | 46 ++++++ lib/dg.exp | 31 +++- testsuite/runtest.libs/dg.test | 293 ++++++++++++++++++++++++++++++++++++ testsuite/runtest.libs/libs.exp | 2 +- testsuite/runtest.libs/mockutil.tcl | 28 +++- testsuite/runtest.libs/mockvfs.tcl | 261 ++++++++++++++++++++++++++++++++ 6 files changed, 647 insertions(+), 14 deletions(-) create mode 100644 testsuite/runtest.libs/dg.test create mode 100644 testsuite/runtest.libs/mockvfs.tcl -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_debug updated (4bcd03c936 -> 4da7fac9df)

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_debug in repository toolchain/ci/base-artifacts. from 4bcd03c936 61: onsuccess: #477: 2: Success after binutils/gcc: 121 commits new 4da7fac9df 62: onsuccess: #478: 2: Success after binutils/gcc: 35 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 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2716 bytes 04-build_abe-binutils/console.log.xz | Bin 51060 -> 50844 bytes 05-build_abe-bootstrap_debug/console.log.xz | Bin 467600 -> 468716 bytes 06-check_regression/console.log.xz | Bin 3096 -> 3048 bytes 06-check_regression/mail-body.txt | 2 +- 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 | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 14 files changed, 26 insertions(+), 17 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_llvm_tx1/llvm-master-aarch64-spec2k6-O3_LTO updated (baceab3cd9 -> 5be2c38f09)

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_tx1/llvm-master-aarch64-spec2k6-O3_LTO in repository toolchain/ci/base-artifacts. from baceab3cd9 23: onsuccess: #470: 1: [TCWG CI] 456.hmmer built and run OK [...] new 5be2c38f09 24: onsuccess: #472: 1: [TCWG CI] No change after binutils/g [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1776 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30984 -> 31084 bytes 04-build_abe-stage1/console.log.xz | Bin 74472 -> 74644 bytes 06-build_abe-linux/console.log.xz | Bin 8564 -> 8640 bytes 07-build_abe-glibc/console.log.xz | Bin 241752 -> 241344 bytes 08-build_abe-stage2/console.log.xz | Bin 182480 -> 183224 bytes 09-build_llvm-true-false-/console.log.xz | Bin 0 -> 64580 bytes 09-build_llvm-true/console.log.xz | Bin 63476 -> 0 bytes 10-benchmark/benchmark-build.log | 122 +- 10-benchmark/benchmark.log | 120 +- 10-benchmark/console.log.xz | Bin 4012 -> 4008 bytes 11-check_regression/console.log.xz | Bin 7716 -> 7704 bytes 11-check_regression/csv-results-0/perf.csv | 86 +- 11-check_regression/csv-results-0/results.csv | 173827 ++++++++----- 11-check_regression/csv-results-0/size.csv | 214667 +++++++++------- 11-check_regression/csv-results-0/vect.csv | 20377 +- 11-check_regression/csv-results-1/perf.csv | 93 +- 11-check_regression/csv-results-1/results.csv | 183521 +++++++------ 11-check_regression/csv-results-1/size.csv | 243212 +++++++++--------- 11-check_regression/csv-results-1/vect.csv | 22798 +- 11-check_regression/exe.improvement | 4 - 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/jira-body.txt | 6 - 11-check_regression/mail-body.txt | 6 - 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results-brief.csv | 40 +- 11-check_regression/results-compare.csv | 13 +- 11-check_regression/results-full.csv | 109 +- 11-check_regression/results-internal.csv | 52 +- 11-check_regression/results.csv | 52 +- 11-check_regression/results.log | 1010 +- dashboard/dashboard-generate.sh | 2 +- .../squad/400.perlbench/results-metadata.json | 18 +- dashboard/squad/400.perlbench/results-metrics.json | 6 +- dashboard/squad/401.bzip2/results-metadata.json | 18 +- dashboard/squad/401.bzip2/results-metrics.json | 4 +- dashboard/squad/403.gcc/results-metadata.json | 18 +- dashboard/squad/403.gcc/results-metrics.json | 6 +- dashboard/squad/429.mcf/results-metadata.json | 18 +- dashboard/squad/429.mcf/results-metrics.json | 2 +- dashboard/squad/444.namd/results-metadata.json | 18 +- dashboard/squad/444.namd/results-metrics.json | 4 +- dashboard/squad/445.gobmk/results-metadata.json | 18 +- dashboard/squad/445.gobmk/results-metrics.json | 4 +- dashboard/squad/447.dealII/results-metadata.json | 18 +- dashboard/squad/447.dealII/results-metrics.json | 4 +- dashboard/squad/450.soplex/results-metadata.json | 18 +- dashboard/squad/450.soplex/results-metrics.json | 2 +- dashboard/squad/453.povray/results-metadata.json | 18 +- dashboard/squad/453.povray/results-metrics.json | 6 +- dashboard/squad/456.hmmer/results-metadata.json | 18 +- dashboard/squad/456.hmmer/results-metrics.json | 6 +- dashboard/squad/458.sjeng/results-metadata.json | 18 +- dashboard/squad/458.sjeng/results-metrics.json | 4 +- .../squad/462.libquantum/results-metadata.json | 18 +- .../squad/462.libquantum/results-metrics.json | 2 +- dashboard/squad/470.lbm/results-metadata.json | 18 +- dashboard/squad/470.lbm/results-metrics.json | 2 +- dashboard/squad/471.omnetpp/results-metadata.json | 18 +- dashboard/squad/471.omnetpp/results-metrics.json | 4 +- dashboard/squad/473.astar/results-metadata.json | 18 +- dashboard/squad/473.astar/results-metrics.json | 4 +- dashboard/squad/482.sphinx3/results-metadata.json | 18 +- dashboard/squad/482.sphinx3/results-metrics.json | 2 +- .../squad/483.xalancbmk/results-metadata.json | 18 +- dashboard/squad/483.xalancbmk/results-metrics.json | 4 +- dashboard/squad/Mean/results-functional.json | 4 - dashboard/squad/Mean/results-metadata.json | 13 - dashboard/squad/Mean/results-metrics.json | 5 - dashboard/squad/dashboard-push-squad.sh | 77 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 57 +- mail/mail-body.txt | 57 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 2 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 402564 -> 402556 bytes save-temps/401.bzip2.tar.xz | Bin 44460 -> 44472 bytes save-temps/403.gcc.tar.xz | Bin 1200680 -> 1200476 bytes save-temps/429.mcf.tar.xz | Bin 22828 -> 22768 bytes save-temps/444.namd.tar.xz | Bin 46792 -> 46944 bytes save-temps/445.gobmk.tar.xz | Bin 614660 -> 615904 bytes save-temps/447.dealII.tar.xz | Bin 933956 -> 906276 bytes save-temps/450.soplex.tar.xz | Bin 204504 -> 211132 bytes save-temps/453.povray.tar.xz | Bin 466644 -> 461216 bytes save-temps/456.hmmer.tar.xz | Bin 125064 -> 124848 bytes save-temps/458.sjeng.tar.xz | Bin 52628 -> 52640 bytes save-temps/462.libquantum.tar.xz | Bin 24164 -> 24328 bytes save-temps/470.lbm.tar.xz | Bin 16044 -> 16032 bytes save-temps/471.omnetpp.tar.xz | Bin 375728 -> 358200 bytes save-temps/473.astar.tar.xz | Bin 43860 -> 43940 bytes save-temps/482.sphinx3.tar.xz | Bin 95868 -> 95864 bytes save-temps/483.xalancbmk.tar.xz | Bin 3335784 -> 3302348 bytes 99 files changed, 461245 insertions(+), 399519 deletions(-) create mode 100644 09-build_llvm-true-false-/console.log.xz delete mode 100644 09-build_llvm-true/console.log.xz delete mode 100644 11-check_regression/exe.improvement 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, 1 month

[gcc] branch master updated (e99dcbb54e0 -> 966010b2eb4)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from e99dcbb54e0 rs6000: Remove the wD constraint new 966010b2eb4 Daily bump. 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: contrib/ChangeLog | 4 ++ gcc/ChangeLog | 85 +++++++++++++++++++++++ gcc/DATESTAMP | 2 +- gcc/analyzer/ChangeLog | 179 ++++++++++++++++++++++++++++++++++++++++++++++++ gcc/cp/ChangeLog | 5 ++ gcc/fortran/ChangeLog | 40 +++++++++++ gcc/testsuite/ChangeLog | 88 ++++++++++++++++++++++++ libgomp/ChangeLog | 4 ++ libstdc++-v3/ChangeLog | 10 +++ 9 files changed, 416 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/release-aarch64 updated (6998623252 -> 0fa052a133)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_binutils/release-aarch64 in repository toolchain/ci/base-artifacts. from 6998623252 16: onsuccess: #115: 1: Success after binutils/gcc/linux/gli [...] new 0fa052a133 17: onsuccess: #116: 1: Success after binutils/gcc/linux/gli [...] 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 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2700 -> 2712 bytes 03-build_abe-binutils/console.log.xz | Bin 37620 -> 37512 bytes 04-build_abe-gcc/console.log.xz | Bin 207008 -> 207780 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8564 -> 8632 bytes 07-build_abe-glibc/console.log.xz | Bin 238728 -> 239768 bytes 08-build_abe-gdb/console.log.xz | Bin 36688 -> 36880 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3828 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2044 -> 2048 bytes 11-check_regression/console.log.xz | Bin 6048 -> 5936 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++-- sumfiles/binutils.log.xz | Bin 55488 -> 55500 bytes sumfiles/binutils.sum | 58 ++--- sumfiles/gas.log.xz | Bin 80384 -> 80388 bytes sumfiles/gas.sum | 270 +++++++++++------------ sumfiles/ld.log.xz | Bin 118820 -> 119028 bytes sumfiles/ld.sum | 332 ++++++++++++++--------------- 29 files changed, 365 insertions(+), 365 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[binutils-gdb] branch gdb-12-branch updated (b61628002ae -> ce2cb0f4db9)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch gdb-12-branch in repository binutils-gdb. from b61628002ae Automatic date update in version.in new ce2cb0f4db9 Automatic date update in version.in 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: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[binutils-gdb] branch master updated (769a27ade58 -> a1509b60cf9)

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 769a27ade58 Re: bfd BLD-POTFILES.in dependencies new a1509b60cf9 Automatic date update in version.in 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: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[binutils-gdb] branch binutils-2_39-branch updated (929345f9502 -> 6cf955dbaa1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch binutils-2_39-branch in repository binutils-gdb. from 929345f9502 Automatic date update in version.in new 6cf955dbaa1 Automatic date update in version.in 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: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022