Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-mainline-allmodconfig updated (fcf819c6a34 -> 4c0a3e3593c)

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-release-aarch64-mainline-allmodconfig in repository toolchain/ci/base-artifacts. from fcf819c6a34 34: onsuccess: #449: all: Success after binutils/llvm/linux [...] new 4c0a3e3593c 35: onsuccess: #450: all: Success after binutils/llvm/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 1724 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31364 -> 30340 bytes 04-build_kernel_llvm/console.log.xz | Bin 66756 -> 64560 bytes 05-build_abe-qemu/console.log.xz | Bin 32404 -> 30672 bytes 06-build_linux/console.log.xz | Bin 3184 -> 3092 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3972 -> 4096 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm updated (913a3406008 -> 679bc164bcc)

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_fast_check_gdb/master-arm in repository toolchain/ci/base-artifacts. from 913a3406008 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new 679bc164bcc 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1732 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 51796 -> 52488 bytes 04-build_abe-gcc/console.log.xz | Bin 234156 -> 234536 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8544 -> 8588 bytes 07-build_abe-glibc/console.log.xz | Bin 236032 -> 235620 bytes 08-build_abe-gdb/console.log.xz | Bin 51636 -> 51732 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3820 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2584 -> 3068 bytes 11-check_regression/console.log.xz | Bin 6020 -> 5748 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++++++++++----------------- sumfiles/gdb.log.xz | Bin 14512 -> 14504 bytes sumfiles/gdb.sum | 34 +++++++++++++++++----------------- 24 files changed, 47 insertions(+), 47 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (1ca22a1f107 -> 2dcf26935d2)

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 1ca22a1f107 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 1 [...] discards b78afde1dd0 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 1 [...] discards 794194a3246 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/ [...] discards bd4e2902673 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/ [...] discards dbbc117b464 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/ [...] discards 78511530e42 190: onsuccess: #1774: 7: Success after binutils: 10 commits discards 841b1d8709d 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 3 [...] discards f7a98224581 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/ [...] discards 9ea00d4f443 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/ [...] discards 182d127561a 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/ [...] discards 8a2d6ec7e3c 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] discards 9090ca36285 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/ [...] discards aa6b788ede0 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/ [...] discards cd8d3597f3f 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/ [...] discards 18b4a85153b 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/ [...] discards 4f72c22f705 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] discards 3767baadde0 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/ [...] discards 02870137c65 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/ [...] discards d731c36de70 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/ [...] discards 2b2989ed504 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/ [...] discards 496f1a03cad 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/ [...] discards c3699249f39 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 1 [...] discards 76b1ac8fd34 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/ [...] discards 36fa9ad306c 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qem [...] discards 980d6c5ead5 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 1 [...] discards 54a9a19aa3f 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/ [...] discards d91354f5149 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/ [...] discards 6f44cd29b47 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/ [...] discards a4ebcc47531 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 2 [...] discards 77d75806ad2 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits discards 6086ec45213 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/ [...] discards 32e51ac9156 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/ [...] discards 3c321e5a93f 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 1 [...] discards 65113922d94 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 [...] discards 3b56c3ba537 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/ [...] discards 0f0cdbec2cf 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/ [...] discards dac45342cea 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards 0682a379917 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/ [...] discards acc8d234279 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards e289daaa979 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards 893d28aaf45 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb [...] discards 4cec1288574 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards dac7790777a 153: force: #1606: 1: Failure after basepoints/gcc-13-3004- [...] discards fbed0d36a45 152: force: #1605: 7: Success after gcc: 9 commits discards 80dadba6bee 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint- [...] discards 94e5bf27114 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/ [...] discards 300eeff9dc6 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 2 [...] discards 9dc1db71361 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/ [...] discards da464875956 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/ [...] discards c9a6e53e4c9 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/ [...] discards 4f132a3ff77 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 3 [...] discards d0e37b5567c 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards f1dd14f9dcc 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/ [...] discards 2a6df97f081 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/ [...] discards 9feb740b84c 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 [...] discards fd4fa68e209 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 [...] discards f8e669f9536 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/ [...] discards b46f2e7f2c8 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/ [...] discards afabe369fd8 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 3da1549cfaa 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 1 [...] discards 9212f7dcd9c 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/ [...] discards d5cee92c646 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/ [...] discards c8b07d7511a 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 2 [...] discards 577d63ca9be 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 1 [...] discards eecc68b4ecc 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/ [...] discards 79a39ed78dc 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 38eafe0ac0e 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-2 [...] discards 523d583b671 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 5edb9446b82 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 [...] discards bc5eafb2a6e 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 510cb2e9233 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 [...] discards 0af32e663f2 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards a55529fcf14 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/ [...] discards d3356841276 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/ [...] discards 96488ea4e33 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/ [...] discards 6b92fb51e1b 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/ [...] discards 27ee4a20c4f 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/ [...] discards c80430bf49b 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 [...] discards 57fe9a824e6 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qe [...] discards 33fc27a237f 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/ [...] discards 6f688a9bed5 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 1 [...] discards df5787fa8cd 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards d3ab84c7e27 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/ [...] discards 19dfe994cb5 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/ [...] discards e77c2e03d10 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/ [...] discards 18c93fa94be 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 7e02721fe0f 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 [...] discards 1a45e71d455 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-2 [...] discards 2385ae7fc6c 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/ [...] discards 73a95e528c4 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/ [...] discards 1f2c0ddadc4 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38edde [...] discards 6950d604472 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/ [...] discards 35a351126f2 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards e37299ceb16 102: force: #1551: 1: Failure after gcc: 306 commits discards a38d8c6cba5 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 7f9126f8bce 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/ [...] discards 2bf904a2969 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 933f9959367 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/g [...] discards 425f7af07bb 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 48cf5aa1e86 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu [...] discards 7ffda5a15a1 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu [...] new 3ef0b663f5f 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu [...] new 9e02a7e9578 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu [...] new 36cf60595ea 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new b9cfc02fb85 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/g [...] new e6488b8f14a 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 0955dfad08a 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/ [...] new 25c786aac0f 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 3430eb8c334 102: force: #1551: 1: Failure after gcc: 306 commits new 7d87a3b37d2 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 8d199d6b4ac 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/ [...] new 5e640121607 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38edde [...] new 2252ef3278d 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/ [...] new dacb5a483ac 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/ [...] new 9dbaea7ec96 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-2 [...] new c37bd5e41df 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 [...] new f6e6419aa67 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 07afcfc4bf9 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/ [...] new bfa587e8970 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/ [...] new 9f5b43e8be4 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/ [...] new 1c102ec917d 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 6c94b593ffd 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 1 [...] new b8882869d97 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/ [...] new bbc08372535 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qe [...] new a1cb55d2567 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 [...] new 1c0689faa06 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/ [...] new ec8facbae39 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/ [...] new db93e906653 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/ [...] new d4e2f18c0a5 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/ [...] new 689c7a01e18 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/ [...] new 7531eeb953a 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 8e535e72b4d 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 [...] new 3407d5a46af 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 3a262863641 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 [...] new 9d269dac5ba 128: onsuccess: #1579: 7: Success after linux: 12 commits new f6d5ec3a538 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-2 [...] new 991fc516ec4 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 9dd08326aae 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/ [...] new 400dd97b3ad 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 1 [...] new 26594fc5ada 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 2 [...] new 240cdeb68fe 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/ [...] new f257949c644 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/ [...] new 3ab0a802b02 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 1 [...] new f9a0c05967d 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 410580566cb 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/ [...] new 7972b555c68 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/ [...] new a0ddcc058cb 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 [...] new 395478a1cf9 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 [...] new f18f01dfa70 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/ [...] new e118071cd7f 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/ [...] new 01e9cdc22e4 144: onsuccess: #1595: 7: Success after glibc: 2 commits new 35f2d6d1a48 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 3 [...] new d58960b3842 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/ [...] new 9f188831643 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/ [...] new 799ff0949ba 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/ [...] new 9d068fd8d57 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 2 [...] new a42346801dc 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/ [...] new 0c56c297a1c 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint- [...] new 377ef1810bd 152: force: #1605: 7: Success after gcc: 9 commits new 330206641a6 153: force: #1606: 1: Failure after basepoints/gcc-13-3004- [...] new fe3ee47b113 154: onsuccess: #1607: 1: Success after gcc: 2 commits new fe1db203404 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb [...] new 64844cfca68 156: onsuccess: #1609: 7: Success after gcc: 2 commits new e96d1b88220 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new 7e2d93ab0dc 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/ [...] new a628d0f7429 159: onsuccess: #1612: 7: Success after gcc: 4 commits new d729a7e6ea6 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/ [...] new c5d0ffaee77 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/ [...] new c59152c6be8 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 [...] new 4eb5c5051e5 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 1 [...] new 653115c1d0c 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/ [...] new 467e20cc9d7 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/ [...] new c0d931e95f8 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits new 55066ee3de0 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 2 [...] new 467f5d0a5cd 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/ [...] new d1c8205f248 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/ [...] new 046ee982624 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/ [...] new 2dc2e87f336 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 1 [...] new 92493ee43b8 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qem [...] new 22649ba8a4b 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/ [...] new 11e3b3a120c 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 1 [...] new e1cd46ecd55 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/ [...] new 8ffa2a49654 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/ [...] new 7a5d765281c 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/ [...] new 77937767031 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/ [...] new 7107c09bd3e 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/ [...] new 6ac75233f56 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] new 65730ffa751 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/ [...] new 9a6b4aab437 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/ [...] new 3c10acdd1e7 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/ [...] new 338e100dd2a 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/ [...] new ffa0dab5730 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] new bb96a577ada 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/ [...] new 568cbd19595 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/ [...] new 1e01182bad7 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/ [...] new 7ecee31e310 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 3 [...] new 3c5bbc024e8 190: onsuccess: #1774: 7: Success after binutils: 10 commits new 7d227aae767 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/ [...] new 3d87f03ff87 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/ [...] new 2d64870c4cc 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/ [...] new e2e5453cdc3 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 1 [...] new c4972dc9301 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 1 [...] new 2dcf26935d2 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 4 [...] 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 (1ca22a1f107) \ 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 1728 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2768 bytes 04-build_abe-binutils/console.log.xz | Bin 32088 -> 32172 bytes 05-build_abe-stage1/console.log.xz | Bin 73720 -> 73736 bytes 07-build_abe-linux/console.log.xz | Bin 8632 -> 8580 bytes 08-build_abe-glibc/console.log.xz | Bin 245392 -> 246012 bytes 09-build_abe-stage2/console.log.xz | Bin 206284 -> 206244 bytes 10-build_abe-gdb/console.log.xz | Bin 39932 -> 39204 bytes 11-build_abe-qemu/console.log.xz | Bin 31036 -> 30988 bytes 12-check_regression/console.log.xz | Bin 3776 -> 3936 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++--------- 19 files changed, 56 insertions(+), 56 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (a5a8eaa500b -> d6989624cdc)

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 a5a8eaa500b 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 1 [...] discards 6bf56b39a67 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 1 [...] discards ff841c9b594 202: onsuccess: #1923: 7: Success after binutils/gcc/linux/ [...] discards 23d148dcf45 201: onsuccess: #1905: 7: Success after binutils/gcc/linux/ [...] discards 6c5f7076cc5 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/ [...] discards 00dcc163442 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/ [...] discards a7ef9bac6fe 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/ [...] discards 0f67708055e 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/ [...] discards e86f0c0ce1a 196: onsuccess: #1855: 4: Success after gcc: 30 commits discards 32d2855fb74 195: force: #1854: 4: Failure after basepoints/gcc-13-3918- [...] discards 9d10a2316a4 194: force: #1853: 7: Success after gcc: 26 commits discards ca02e751188 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint- [...] discards 77479ec35a2 192: onsuccess: #1848: 7: Success after linux: 213 commits discards 50d77f7665e 191: onsuccess: #1846: 7: Success after binutils: 4 commits discards d6fa0e99a00 190: onsuccess: #1834: 7: Success after binutils: 25 commits discards 475e89918ae 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/ [...] discards 9362c23f4ca 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/ [...] discards 79cf321eafe 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/ [...] discards 0b180a79f3f 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/ [...] discards c0c963d7ebe 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/ [...] discards 70d1bfdc2bd 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/ [...] discards 2c08eaebdcd 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/ [...] discards 56c9dc9767b 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 [...] discards a883e6ae35e 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/ [...] discards 8d1c31fcbd4 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/ [...] discards 530f91cc12c 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/ [...] discards a3d8fb40424 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/ [...] discards a099fce3d88 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/ [...] discards f7864fc7c01 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/ [...] discards c09ad18673a 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 1 [...] discards b93cdb084d8 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/ [...] discards 0dd774d787c 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qem [...] discards b881fb25b2c 172: onsuccess: #1687: 7: Success after gcc: 11 commits discards b17c168f48d 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/ [...] discards f8fa94def18 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/ [...] discards 83d96f27dcb 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/ [...] discards 2c511c18355 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 3 [...] discards 46a7a92acf0 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits discards 302e57f20f4 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/ [...] discards a8556fb0e7b 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/ [...] discards 6131604db00 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 1 [...] discards 34e6066c0bd 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 [...] discards dde4cafd6a4 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/ [...] discards 8cb732c9a1d 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/ [...] discards 046c9b21103 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 1 [...] discards c433fe61e8a 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/ [...] discards 6a48373c87a 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards dbec5e68ff3 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards e41c57267a2 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards bdca2c410be 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/ [...] discards 5d6ec676bab 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/ [...] discards 056a92aed2e 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 2 [...] discards b65805723f5 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/ [...] discards eb0337deadb 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/ [...] discards 0812b026db1 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/ [...] discards 5299c9727bd 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 3 [...] discards 7bc163337f4 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 0839ee6faaa 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/ [...] discards 41f2edf7d4f 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/ [...] discards 80e7d617779 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 1 [...] discards 3edbc286bb4 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 [...] discards bb900c75cd7 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/ [...] discards accf5fb63c9 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/ [...] discards f45d6cd919f 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards d712ea87d54 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/ [...] discards 762ac8f5b05 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards b734213cab8 138: force: #1653: 1: Failure after basepoints/gcc-13-2871- [...] discards c526ebb9d0f 137: force: #1652: 7: Success after basepoints/gcc-13-2870- [...] discards eb3abb4b797 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 53a60c36729 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 2 [...] discards ae6323daada 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 1 [...] discards c863ec8f40b 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/ [...] discards 8ffbde55702 132: onsuccess: #1645: 7: Success after linux: 23 commits discards a44fccf3247 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards f281c7f6705 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/ [...] discards 7ca2c8b9f68 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards ae59fb05176 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 [...] discards 04575280a73 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 047cc91f08e 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/ [...] discards a4f1cd62cd2 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/ [...] discards 42cb82703ed 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/ [...] discards 2c913ce280a 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/ [...] discards db7833f00d5 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/ [...] discards 300846c9727 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 1 [...] discards b2724a88b8f 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qe [...] discards f91cc11c683 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/ [...] discards fc93f95680e 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 1 [...] discards 44966e1b636 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 5370ee506c2 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/ [...] discards 29e1964dfdb 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/ [...] discards b3bb2b72c10 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/ [...] discards 4cc3a97bff4 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards ed4bfc4659f 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 [...] discards 7435efbd917 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 [...] discards 9de8457df47 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/ [...] discards 00b7ff8280b 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/ [...] discards bbe5a019543 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38edde [...] discards 77c7783f1e7 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 6082365cb9d 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 3ba3a1e3714 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/ [...] discards 6a583c1e662 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 15756b8740b 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new b0699a1c617 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/ [...] new 40e32f72c19 106: onsuccess: #1617: 7: Success after gcc: 2 commits new aa9087deeff 107: onsuccess: #1618: 7: Success after gcc: 2 commits new af6e6f56724 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38edde [...] new a4963a859f1 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/ [...] new fc883a80d81 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/ [...] new 469b353c1ce 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 [...] new 0a7ef375cc1 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 [...] new f14646c5b9c 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 5ec3764c5f6 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/ [...] new 3f1a8e3ed8f 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/ [...] new 2b3f40b07f7 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/ [...] new 7ca3e5e87dd 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new e8b5d31ff60 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 1 [...] new a797c5eac74 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/ [...] new b6a6e9bb31a 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qe [...] new 98299bbb2eb 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 1 [...] new c35ee38eab4 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/ [...] new 4f7e41102e2 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/ [...] new ee4d67c1469 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/ [...] new efd83da4cde 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/ [...] new b8766a7bbaf 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/ [...] new 7055a5cb67c 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new c7423ea550e 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 [...] new 73e6e0c91e8 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new cb1a9c83da1 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/ [...] new 56e0ed137da 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 2bad68a33a0 132: onsuccess: #1645: 7: Success after linux: 23 commits new 2150e771f27 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/ [...] new 4cdd763ca50 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 1 [...] new e94a914567e 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 2 [...] new 14f03a7e02c 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 129db758633 137: force: #1652: 7: Success after basepoints/gcc-13-2870- [...] new ff5f63b7d59 138: force: #1653: 1: Failure after basepoints/gcc-13-2871- [...] new 2d106ea6c3d 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 21b1e486c7f 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/ [...] new 1809bb65e57 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 17fca84bd41 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/ [...] new 4d3600b027f 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/ [...] new be26336e8ba 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 [...] new 86fb668ae32 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 1 [...] new f1309a3d6fe 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/ [...] new 3cc5db30b09 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/ [...] new 02f07b506eb 148: onsuccess: #1663: 7: Success after glibc: 2 commits new b724bdeb346 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 3 [...] new 652b81bef3d 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/ [...] new cebff67dc71 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/ [...] new f134af100db 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/ [...] new 85f2f2eec38 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 2 [...] new a24ac1873e1 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/ [...] new 75c619b00b8 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/ [...] new f99bfd75394 156: onsuccess: #1671: 7: Success after gcc: 3 commits new 9a9bdbf4941 157: onsuccess: #1672: 7: Success after gcc: 2 commits new 03cf87c7e2c 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new 59018758eec 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/ [...] new e0983531a8f 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 1 [...] new 100944066af 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/ [...] new 18dc67de47b 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/ [...] new 03169d7e4af 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 [...] new 72682f7237f 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 1 [...] new 3b59a9aab6e 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/ [...] new 59e53d266e5 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/ [...] new 52de293da36 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits new da8f4e617f5 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 3 [...] new d7aacc08574 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/ [...] new 018b157510e 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/ [...] new b83b6084658 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/ [...] new 749bec64969 172: onsuccess: #1687: 7: Success after gcc: 11 commits new 1f68ffe58b5 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qem [...] new 63f09922978 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/ [...] new 64d53a9f666 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 1 [...] new 67a3b039161 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/ [...] new dcd2c99c393 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/ [...] new 54fce8b11db 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/ [...] new d6415085ca6 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/ [...] new d538ae810ba 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/ [...] new 6dea454b041 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/ [...] new 3e75f398452 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 [...] new dfbc29c1b7f 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/ [...] new 03f1e341837 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/ [...] new f163cb09e23 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/ [...] new 2b40122c0c0 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/ [...] new 18adfe2d0a3 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/ [...] new fda6195e49b 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/ [...] new 36794f89fe8 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/ [...] new b9839d87408 190: onsuccess: #1834: 7: Success after binutils: 25 commits new 877ba41896e 191: onsuccess: #1846: 7: Success after binutils: 4 commits new 2315e217ec6 192: onsuccess: #1848: 7: Success after linux: 213 commits new 973e6fda787 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint- [...] new 393ebe955e3 194: force: #1853: 7: Success after gcc: 26 commits new 5dbc63fa5f8 195: force: #1854: 4: Failure after basepoints/gcc-13-3918- [...] new 7c0d19352f3 196: onsuccess: #1855: 4: Success after gcc: 30 commits new 41ce0b946d8 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/ [...] new 2f1868604f9 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/ [...] new c45bbf988a0 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/ [...] new a7e31da1cdb 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/ [...] new 6fda041fc7c 201: onsuccess: #1905: 7: Success after binutils/gcc/linux/ [...] new b169916b9a2 202: onsuccess: #1923: 7: Success after binutils/gcc/linux/ [...] new 3d65e74fd58 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 1 [...] new 0d2b4710c7b 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 1 [...] new d6989624cdc 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 4 [...] 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 (a5a8eaa500b) \ 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 1688 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 32284 -> 31716 bytes 05-build_abe-stage1/console.log.xz | Bin 92580 -> 91420 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8588 -> 8580 bytes 08-build_abe-glibc/console.log.xz | Bin 236784 -> 236516 bytes 09-build_abe-stage2/console.log.xz | Bin 225440 -> 225092 bytes 10-build_abe-gdb/console.log.xz | Bin 39096 -> 38752 bytes 11-build_abe-qemu/console.log.xz | Bin 30568 -> 30556 bytes 12-check_regression/console.log.xz | Bin 3908 -> 3824 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++--------- 20 files changed, 56 insertions(+), 56 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (05248a2f472 -> 22b734c1110)

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 05248a2f472 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits discards 34e3763850c 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits discards fbcb627833e 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits discards 6c00c8c9bda 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits discards 37f2d343084 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits discards 5c490be8683 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits discards bbaf156311d 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits discards 1f2f5fbd4fd 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits discards e3d4d03ba52 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits discards 3c332f99285 360: onsuccess: #2317: 1: Success after binutils: 4 commits discards e0c80bc8795 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint- [...] discards 18236ab9b07 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits discards d9d013da32c 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits discards ee52ec7d1de 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits discards a9cd49da69f 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits discards 46682467553 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits discards acb988a4d5e 353: onsuccess: #2309: 1: Success after gcc: 7 commits discards 90d613379af 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits discards 9fe88c1b74f 351: onsuccess: #2307: 1: Success after binutils: 2 commits discards b59be4fdeed 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits discards da4b2571d06 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits discards 505f7c85344 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits discards afbe64a7b7c 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits discards ce06a51b91f 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits discards e08467540fb 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits discards 07bdd94fa73 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits discards 384418504e0 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits discards bf9de17492a 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits discards 13f457d45ff 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits discards 699ba2745a2 340: onsuccess: #2296: 1: Success after gcc: 3 commits discards a8f7c33b665 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits discards ca4ff3bba01 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits discards 8204c5a1d15 337: onsuccess: #2293: 1: Success after gcc: 21 commits discards 6df34eeb66e 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits discards 5faa2d50b84 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits discards dba514980da 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits discards 33db8c6872a 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-4 [...] discards a6f1abb8311 332: onsuccess: #2288: 1: Success after gcc: 2 commits discards 6e230b3cae7 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint- [...] discards c611bff90fa 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits discards 1b1a89fe57a 329: onsuccess: #2285: 1: Success after gcc: 8 commits discards d62a3a614b2 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint- [...] discards 385b961bece 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits discards 9c64ea52033 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits discards e87ae1727d6 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits discards 8a967d7c691 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits discards 0a77accb1ef 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits discards 6c56fea502b 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits discards e303b1477af 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits discards 931810fa1e5 320: onsuccess: #2274: 1: Success after gcc: 5 commits discards 4db6def0767 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits discards a9bcdc308f7 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits discards 22d33ef1302 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits discards 6698008c61f 316: onsuccess: #2270: 1: Success after gcc: 2 commits discards 5b857e0e2c1 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits discards d164e819cf6 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits discards f66a1d6a99c 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits discards 36c0f83a82f 312: onsuccess: #2265: 1: Success after binutils: 2 commits discards 3d27b90f294 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint- [...] discards 3e5de5bffdc 310: onsuccess: #2259: 1: Success after binutils: 2 commits discards f7b2df8ba09 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint- [...] discards a60073d448b 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint- [...] discards e9c624e5f19 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint- [...] discards dc004d30ba7 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint- [...] discards 5f6e40dfd8d 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits discards b09dd83bf7b 304: onsuccess: #2243: 1: Success after binutils/gcc: 23 commits discards 82ac03f1e94 303: onsuccess: #2242: 1: Success after binutils/gcc: 17 commits discards 858630f1363 302: onsuccess: #2241: 1: Success after binutils/gcc: 10 commits discards e5f2cb19c8d 301: onsuccess: #2240: 1: Success after binutils/gcc: 10 commits discards 233432829f9 300: onsuccess: #2239: 1: Success after binutils/gcc: 20 commits discards 82e731f23b3 299: onsuccess: #2238: 1: Success after binutils/gcc: 12 commits discards e606c57e999 298: onsuccess: #2237: 1: Success after binutils/gcc: 9 commits discards 13fd2b03567 297: onsuccess: #2236: 1: Success after binutils/gcc: 9 commits discards 6ce0eb97834 296: onsuccess: #2235: 1: Success after binutils/gcc: 14 commits discards 52a21c8ec7e 295: onsuccess: #2234: 1: Success after binutils/gcc: 33 commits discards 2419e3e9b1e 294: onsuccess: #2233: 1: Success after binutils/gcc: 4 commits discards 2e18a0b89ca 293: onsuccess: #2232: 1: Success after binutils/gcc: 5 commits discards a19c32d907d 292: onsuccess: #2231: 1: Success after binutils/gcc: 19 commits discards 93a4e3f31b8 291: onsuccess: #2230: 1: Success after binutils/gcc: 31 commits discards b5e7b65168c 290: onsuccess: #2229: 1: Success after binutils/gcc: 12 commits discards 3114d016279 289: onsuccess: #2228: 1: Success after binutils/gcc: 11 commits discards 95b2a4752fd 288: onsuccess: #2227: 1: Success after binutils/gcc: 16 commits discards 2128fec1b90 287: onsuccess: #2226: 1: Success after binutils/gcc: 38 commits discards b3438e3967f 286: onsuccess: #2225: 1: Success after binutils/gcc: 7 commits discards 4bdaf553ef5 285: onsuccess: #2224: 1: Success after binutils/gcc: 2 commits discards cb16c23729e 284: onsuccess: #2223: 1: Success after binutils/gcc: 5 commits discards 83d91603999 283: onsuccess: #2222: 1: Success after gcc: 4 commits discards 78a96e0b6bd 282: onsuccess: #2221: 1: Success after gcc: 2 commits discards 72a9c830bff 281: onsuccess: #2220: 1: Success after binutils/gcc: 4 commits discards 65b80c69aab 280: onsuccess: #2219: 1: Success after binutils/gcc: 10 commits discards 26daf1ae545 279: onsuccess: #2218: 1: Success after basepoints/gcc-13-3 [...] discards eb2e2c47ae1 278: onsuccess: #2217: 1: Success after binutils: 7 commits discards dc381b02772 277: onsuccess: #2216: 1: Success after binutils: 2 commits discards c9a0d7cc080 276: onsuccess: #2215: 1: Success after binutils/gcc: 44 commits discards d60b7064c5a 275: onsuccess: #2214: 1: Success after binutils/gcc: 14 commits discards f85628cb641 274: onsuccess: #2213: 1: Success after binutils/gcc: 12 commits discards 5f214600be6 273: onsuccess: #2212: 1: Success after binutils/gcc: 13 commits discards 3af6a7be0bb 272: onsuccess: #2211: 1: Success after binutils/gcc: 19 commits discards 2ddaa81f910 271: onsuccess: #2210: 1: Success after binutils/gcc: 8 commits discards 0d0a132dbc5 270: onsuccess: #2209: 1: Success after gcc: 2 commits discards 8217e6d5a4e 269: onsuccess: #2208: 1: Success after binutils/gcc: 8 commits new 17336554988 269: onsuccess: #2208: 1: Success after binutils/gcc: 8 commits new 46a5d685f9b 270: onsuccess: #2209: 1: Success after gcc: 2 commits new d3c2328615e 271: onsuccess: #2210: 1: Success after binutils/gcc: 8 commits new 10b3044a795 272: onsuccess: #2211: 1: Success after binutils/gcc: 19 commits new 35ec9f1e3ef 273: onsuccess: #2212: 1: Success after binutils/gcc: 13 commits new 5b2f97395a0 274: onsuccess: #2213: 1: Success after binutils/gcc: 12 commits new ffa1d3a0ff4 275: onsuccess: #2214: 1: Success after binutils/gcc: 14 commits new 5b957feddf2 276: onsuccess: #2215: 1: Success after binutils/gcc: 44 commits new 725172f2890 277: onsuccess: #2216: 1: Success after binutils: 2 commits new 162e75b3b26 278: onsuccess: #2217: 1: Success after binutils: 7 commits new f807e1e459e 279: onsuccess: #2218: 1: Success after basepoints/gcc-13-3 [...] new d10ff64887e 280: onsuccess: #2219: 1: Success after binutils/gcc: 10 commits new 4b9bd6dcbc8 281: onsuccess: #2220: 1: Success after binutils/gcc: 4 commits new d3e7c552040 282: onsuccess: #2221: 1: Success after gcc: 2 commits new b095dfe6035 283: onsuccess: #2222: 1: Success after gcc: 4 commits new 771d83b3999 284: onsuccess: #2223: 1: Success after binutils/gcc: 5 commits new ca05cd98f68 285: onsuccess: #2224: 1: Success after binutils/gcc: 2 commits new cd059ee4310 286: onsuccess: #2225: 1: Success after binutils/gcc: 7 commits new b9184c96b81 287: onsuccess: #2226: 1: Success after binutils/gcc: 38 commits new f10fcd81b59 288: onsuccess: #2227: 1: Success after binutils/gcc: 16 commits new 0a38e1bbc1a 289: onsuccess: #2228: 1: Success after binutils/gcc: 11 commits new 2feb208eb7c 290: onsuccess: #2229: 1: Success after binutils/gcc: 12 commits new 5341c2d3c20 291: onsuccess: #2230: 1: Success after binutils/gcc: 31 commits new 2e41fe00efc 292: onsuccess: #2231: 1: Success after binutils/gcc: 19 commits new eeac12d1514 293: onsuccess: #2232: 1: Success after binutils/gcc: 5 commits new 8bd5ef98907 294: onsuccess: #2233: 1: Success after binutils/gcc: 4 commits new 0bc89035944 295: onsuccess: #2234: 1: Success after binutils/gcc: 33 commits new 085db533684 296: onsuccess: #2235: 1: Success after binutils/gcc: 14 commits new 2b80e956ff7 297: onsuccess: #2236: 1: Success after binutils/gcc: 9 commits new da4465d6974 298: onsuccess: #2237: 1: Success after binutils/gcc: 9 commits new 45552e81317 299: onsuccess: #2238: 1: Success after binutils/gcc: 12 commits new 6202030065a 300: onsuccess: #2239: 1: Success after binutils/gcc: 20 commits new f2a5ca92199 301: onsuccess: #2240: 1: Success after binutils/gcc: 10 commits new e76f0aba5b9 302: onsuccess: #2241: 1: Success after binutils/gcc: 10 commits new be191c8a44d 303: onsuccess: #2242: 1: Success after binutils/gcc: 17 commits new 5ec8a1703b9 304: onsuccess: #2243: 1: Success after binutils/gcc: 23 commits new e9f90f04f23 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits new a835168e319 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint- [...] new 3a8cb6bed0e 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint- [...] new b3d11352894 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint- [...] new 639defb2b40 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint- [...] new 3a1290af600 310: onsuccess: #2259: 1: Success after binutils: 2 commits new d19b8275f75 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint- [...] new 3d1ff2815e1 312: onsuccess: #2265: 1: Success after binutils: 2 commits new 27b6453043e 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits new a2c281526fa 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits new 44f7123eb41 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits new 45c8e072218 316: onsuccess: #2270: 1: Success after gcc: 2 commits new e7c4db454b4 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits new adf3632da76 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits new 23b968874fb 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits new 65eb995518b 320: onsuccess: #2274: 1: Success after gcc: 5 commits new 2fbe1451354 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits new 31d311d11ce 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits new 8479c64694f 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits new 87526b47d0f 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits new 61c3c4fffca 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits new f501dd7b773 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits new 746616c05e9 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits new 0ab9ec8a2dd 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint- [...] new 0c414aa6164 329: onsuccess: #2285: 1: Success after gcc: 8 commits new fe7ee197fab 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits new 6cddaa58b70 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint- [...] new edc3d2ad20f 332: onsuccess: #2288: 1: Success after gcc: 2 commits new 2e2f66bbe5f 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-4 [...] new 2ad276cc605 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits new 77bf8b0be84 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits new c01d703d281 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits new 1dc9a6d293d 337: onsuccess: #2293: 1: Success after gcc: 21 commits new 8eb12e8a5c6 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits new bd48d3bddd0 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits new f599165cb27 340: onsuccess: #2296: 1: Success after gcc: 3 commits new 0f9541cdfa9 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits new 98bbd9ddb98 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits new 04faf55a56d 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits new b568d0d921a 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits new 03e151759db 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits new 2c4afc23bf3 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits new 8c36e2a31b3 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits new 5824259f569 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits new f6f90316008 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits new 03656c9a58d 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits new b1f298a8465 351: onsuccess: #2307: 1: Success after binutils: 2 commits new 7a8cef48067 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits new 4aa295a75d9 353: onsuccess: #2309: 1: Success after gcc: 7 commits new 01d4d1a7456 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits new 2bbd99ba49f 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits new 0c1249c7578 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits new 729f41200b5 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits new fd2e7a5cd2b 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits new 83461755d8f 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint- [...] new 7b111761f4b 360: onsuccess: #2317: 1: Success after binutils: 4 commits new 276a3bcf1ad 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits new 79b2faa0632 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits new 94dcd875aed 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits new 40264352b06 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits new 8b828a1e243 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits new 08f9403568d 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits new 8ccb6101728 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits new b6cd2384fd7 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits new cfc2a8ac95b 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits new 22b734c1110 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 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 (05248a2f472) \ 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 1728 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 39376 -> 41140 bytes 04-build_abe-gcc/console.log.xz | Bin 214340 -> 216720 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3844 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2880 -> 2872 bytes 07-check_regression/console.log.xz | Bin 5348 -> 5280 bytes 07-check_regression/extra-bisect-params | 1 - 07-check_regression/fails.sum | 9 - 07-check_regression/mail-body.txt | 22 +- 07-check_regression/results.compare | 25 +- 07-check_regression/results.compare2 | 67 +- 07-check_regression/results.regressions | 29 - 08-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 24 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 29 - sumfiles/g++.log.xz | Bin 3622492 -> 3615132 bytes sumfiles/g++.sum | 134 +- sumfiles/gcc.log.xz | Bin 3143256 -> 3147464 bytes sumfiles/gcc.sum | 4992 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1053216 -> 1048180 bytes sumfiles/gfortran.sum | 94 +- sumfiles/libatomic.log.xz | Bin 2180 -> 2180 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 219048 -> 218788 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2548 -> 2552 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 448924 -> 456588 bytes sumfiles/libstdc++.sum | 10 +- 36 files changed, 2740 insertions(+), 2816 deletions(-) delete mode 100644 07-check_regression/extra-bisect-params delete mode 100644 07-check_regression/fails.sum delete mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[binutils-gdb] branch master updated (4cb80f0e5bd -> c367d9e0cbf)

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 4cb80f0e5bd Remove call to registers_changed from windows-nat.c new c367d9e0cbf PowerPC, fix gdb.reverse/finish-reverse-bkpt.exp and gdb.re [...] 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: .../finish-reverse-bkpt.c} | 19 ++++++++++- gdb/testsuite/gdb.reverse/finish-reverse-bkpt.exp | 24 ++++++++++++- ...itpid-reverse.c => next-reverse-bkpt-over-sr.c} | 39 +++++++++++----------- .../gdb.reverse/next-reverse-bkpt-over-sr.exp | 31 +++++++++++++---- 4 files changed, 85 insertions(+), 28 deletions(-) copy gdb/testsuite/{gdb.base/fullname.c => gdb.reverse/finish-reverse-bkpt.c} (64%) copy gdb/testsuite/gdb.reverse/{waitpid-reverse.c => next-reverse-bkpt-over-sr.c} (53%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_debug updated (25d6ead9284 -> 590d0234344)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_debug in repository toolchain/ci/base-artifacts. from 25d6ead9284 36: onsuccess: #159: 2: Success after binutils/gcc: 7 commits new 590d0234344 37: onsuccess: #160: 2: Success after binutils/gcc: 12 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1688 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 51312 -> 51864 bytes 05-build_abe-bootstrap_debug/console.log.xz | Bin 461888 -> 461780 bytes 06-check_regression/console.log.xz | Bin 2672 -> 2900 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 | 20 ++++++++++---------- 12 files changed, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/release-arm-check_bootstrap updated (145be55542c -> 888a70e1b3e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check_bootstrap/release-arm-check_bootstrap in repository toolchain/ci/base-artifacts. from 145be55542c 36: onsuccess: #159: 1: Success after binutils/gcc: 7 commits new 888a70e1b3e 37: onsuccess: #160: 1: Success after binutils/gcc: 12 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1668 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 50812 -> 50760 bytes 04-build_abe-bootstrap/console.log.xz | Bin 460524 -> 466336 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3868 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2452 -> 2788 bytes 07-check_regression/console.log.xz | Bin 5104 -> 5488 bytes 07-check_regression/fails.sum | 4 +- 07-check_regression/mail-body.txt | 58 +- 07-check_regression/results.compare | 31 +- 07-check_regression/results.compare2 | 39 +- 07-check_regression/results.regressions | 31 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 60 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 31 +- sumfiles/g++.log.xz | Bin 2817736 -> 2810360 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 2499124 -> 2461920 bytes sumfiles/gcc.sum | 4636 +++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 956644 -> 951940 bytes sumfiles/gfortran.sum | 94 +- sumfiles/libatomic.log.xz | Bin 2304 -> 2308 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207096 -> 206608 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2720 -> 2728 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 471776 -> 460948 bytes sumfiles/libstdc++.sum | 10 +- 34 files changed, 2657 insertions(+), 2515 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[linux] branch master updated (ef4d3ea40565 -> 355479c70a48)

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 linux. from ef4d3ea40565 afs: Fix server->active leak in afs_put_server new 4cc47e8add63 clk: qcom: gdsc: Remove direct runtime PM calls new ef80c95c29dc clk: samsung: exynos7885: Correct "div4" clock parents new 4854e8b083d8 dt-bindings: clock: exynosautov9: fix reference to CMU_FSYS1 new 2bc5febd05ab clk: samsung: Revert "clk: samsung: exynos-clkout: Use of_ [...] new 0d51d0db9f92 Merge tag 'samsung-clk-6.2' of https://git.kernel.org/pub/ [...] new 579767624286 ARM: at91: rm9200: fix usb device clock id new 4e85952f2678 Merge tag 'clk-microchip-fixes-6.1' of https://git.kernel. [...] new f6abcc21d943 clk: qcom: gcc-sc8280xp: add cxo as parent for three ufs ref clks new 063c0e773ab3 Merge tag 'clk-fixes-for-linus' of git://git.kernel.org/pu [...] new 07e06193ead8 hwmon: (ltc2947) fix temperature scaling new b8d27d2ce8df hwmon: (ina3221) Fix shunt sum critical calculation new 3b7f98f23752 hwmon: (i5500_temp) fix missing pci_disable_device() new e2a87785aab0 hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails new a89ff5f5cc64 hwmon: (coretemp) Check for null before removing sysfs attrs new 7dec14537c59 hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new() new 9bdc112be727 hwmon: (asus-ec-sensors) Add checks for devm_kcalloc new e214dd935bf1 Merge tag 'hwmon-for-v6.1-rc8' of git://git.kernel.org/pub [...] new 7572ac3c979d arm64: efi: Revert "Recover from synchronous exceptions ..." new 355479c70a48 Merge tag 'efi-fixes-for-v6.1-4' of git://git.kernel.org/p [...] The 19 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: .../bindings/clock/samsung,exynosautov9-clock.yaml | 2 +- arch/arm/boot/dts/at91rm9200.dtsi | 2 +- arch/arm64/include/asm/efi.h | 8 --- arch/arm64/kernel/efi-rt-wrapper.S | 33 +----------- arch/arm64/kernel/efi.c | 26 --------- arch/arm64/mm/fault.c | 4 -- drivers/clk/at91/at91rm9200.c | 2 +- drivers/clk/qcom/gcc-sc8280xp.c | 6 +++ drivers/clk/qcom/gdsc.c | 61 +++------------------- drivers/clk/qcom/gdsc.h | 2 - drivers/clk/samsung/clk-exynos-clkout.c | 6 ++- drivers/clk/samsung/clk-exynos7885.c | 4 +- drivers/hwmon/asus-ec-sensors.c | 2 + drivers/hwmon/coretemp.c | 9 +++- drivers/hwmon/i5500_temp.c | 2 +- drivers/hwmon/ibmpex.c | 1 + drivers/hwmon/ina3221.c | 4 +- drivers/hwmon/ltc2947-core.c | 2 +- 18 files changed, 38 insertions(+), 138 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (a928742e77a -> d8e06da0ac7)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards a928742e77a 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 5c1b889cca8 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 883ede36f77 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards 710ae3589b2 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards d6f1f3ed9ac 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 6b9df53c5fe 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards f0be3ceaa37 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 3f471667892 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] discards abf2d0fca0a 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] discards 2a11a9adc3c 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 4e9dd804434 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 5cf17badc35 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 2be858510cb 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 0525ade9320 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 2d0d550765c 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 8aa0cce400b 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 89927af15da 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 3d93ea80086 102: onsuccess: #586: 1: Success after binutils: 5 commits discards c34ab6e53b0 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] discards 06c9ff3a743 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] discards 2d2f5de1930 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] discards 29c9677f992 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards c53b8082d50 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] discards 5a28a74611d 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] discards 05e931c296a 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] discards 2d8c731a9bc 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards 7d8c91023bb 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] discards ebf4fe913b9 92: onsuccess: #575: 1: Success after linux: 34 commits discards e7c4c0ab574 91: onsuccess: #574: 1: Success after glibc: 3 commits discards dc1eb65acb4 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 4275b56ce92 89: onsuccess: #570: 1: Success after linux: 11 commits discards 961b2eb6ecd 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 4387f7ec083 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 3cfd040e325 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 05626c38571 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards f9e485b3743 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 094a1465a8a 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] discards d3980d06087 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] discards cbcf8767442 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards e73e4c0ba41 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] discards f369737a084 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] discards 9e0497ce0e5 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] discards 1ea64d45600 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] discards dbb4376bda5 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] discards 1478f8194f5 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] discards 1bde0216dfa 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] discards 5acef4d51fb 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 729cfbe05f7 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 1fc0e5468ed 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] discards eb6c1e3ec2d 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards caf15b5a11f 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] discards e74c37f7468 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] discards 1cfcdbb6bb3 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] discards e5e19f7c240 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards c5c27b41425 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] discards a1ce1a0b94f 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards a0b0e667cb6 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards b734ff57e8b 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards 5dd96992524 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 8e3071e8f87 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] discards 1c43b4798cc 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards 624a872d1a7 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards 6a73f426561 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] discards 98e6df4287c 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards d3055b89c22 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 25a9bf6a542 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] discards 78393e065ef 53: onsuccess: #531: 1: Success after binutils: 12 commits discards e08f71d1f93 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 44ea3a809ab 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 2da7f9d71f4 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] discards 15169060c84 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] discards 22bfffc185e 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] discards bda5aadb24b 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] discards e5f28b766fa 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] discards adedce41c05 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] discards 6f591f4a83c 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] discards 0e96fec7105 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] discards 6db491d296f 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] discards cb4520fa22a 41: onsuccess: #514: 1: Success after linux: 64 commits discards a16a63c94e6 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] discards ba371be8366 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 3051d23d4ba 38: onsuccess: #508: 1: Success after binutils: 3 commits discards f516c7c35c5 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] discards 02dffdc7407 36: onsuccess: #505: 1: Success after glibc: 3 commits discards c71980adf4b 35: onsuccess: #503: 1: Success after binutils: 11 commits discards 7a1a3dae0b6 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards b305a2766e1 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gd [...] discards 50fc88ca0ae 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] discards 0ff4bcd9d69 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] discards 40cfa37adab 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards 6e235cfaa0d 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards 787f11ccd4c 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gd [...] discards 2b4c27b6804 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] discards a2093c6da7a 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gl [...] discards 82ccc768bf4 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] discards cab6e9ab10e 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards a5e65c1741f 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards b2aac918b31 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 7cdf5fd4b86 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards c609a71b326 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards e01e3f33909 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 57b443449aa 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new cf14c162743 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 17d1ff2e52d 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new ce8943468eb 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 6afe49af6ed 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 4f0e5e3c9de 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 3d45c83153f 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] new f1a246b2e2a 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gl [...] new a5e610842d9 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] new 966fe82dd0e 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gd [...] new 81525d6c6f8 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new aae26873d44 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new 4a89e4b522d 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] new d0727c23f47 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] new ec7a3e21a2b 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gd [...] new dcf00e71f92 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new a156927e9ce 35: onsuccess: #503: 1: Success after binutils: 11 commits new c3b3b2b633f 36: onsuccess: #505: 1: Success after glibc: 3 commits new a7ed7ebb988 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] new 49a12818bd6 38: onsuccess: #508: 1: Success after binutils: 3 commits new c28275edd27 39: onsuccess: #511: 1: Success after binutils: 8 commits new 6f47c459617 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] new 281a336b4ed 41: onsuccess: #514: 1: Success after linux: 64 commits new a5d1d0f89b5 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] new 9305223a266 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] new d8a8593b8eb 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] new 2e3252bee16 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] new bf8285f4526 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] new fc0c464507f 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] new 63fe280cae4 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] new ca6ccdfa3f1 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] new 5d36a788b7a 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] new b4e40ed0899 51: onsuccess: #525: 1: Success after binutils: 8 commits new 35da88ce0c1 52: onsuccess: #528: 1: Success after binutils: 8 commits new d42ee0bf323 53: onsuccess: #531: 1: Success after binutils: 12 commits new 883a47e2a9f 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] new 04e46e59305 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new 855b3502015 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new f12cd0ad84e 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] new ef7d19d6748 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new 9162ed79f62 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new 614e56f1a96 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] new 64fae7aae07 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new a6c4099264c 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new 3e14d79f8d8 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new a7e80f71f9f 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 4f46a69cb6e 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] new 69794520dbc 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new 1631b021c3e 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] new c4cec629d04 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] new b5a8e238c47 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] new b72496cbce3 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 14ad3535bf5 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] new ea25c7e9e18 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 628ac3ff68d 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 1a41a12c743 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] new 2d050553466 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] new 36c1d4ca818 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] new ab8edc1e231 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] new c6b85cb1549 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] new c9ff3b3d4d1 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] new 3af66f696e5 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] new ad85f005d5d 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 459a0c65792 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] new b090926bd58 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] new fe48b1d0be2 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 640cccd8a36 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new 11c7444207d 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new fa07b5eefeb 87: onsuccess: #567: 1: Success after binutils: 8 commits new e2e4791a3ab 88: onsuccess: #569: 1: Success after glibc: 10 commits new adca18a829f 89: onsuccess: #570: 1: Success after linux: 11 commits new 9a0adca8a7d 90: onsuccess: #572: 1: Success after binutils: 15 commits new 3347b5785da 91: onsuccess: #574: 1: Success after glibc: 3 commits new ddd0c38bef0 92: onsuccess: #575: 1: Success after linux: 34 commits new d2e9cfbb464 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] new 7e2581b91f4 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new 9e84ab16b1e 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] new 3eec881711d 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] new 7ed31a3849d 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] new fa6b260fcdc 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new 34697d0099b 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] new f76672fb573 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] new 9c6efa4a6c3 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] new fb4c8e26cd6 102: onsuccess: #586: 1: Success after binutils: 5 commits new 7f3904959fa 103: onsuccess: #589: 1: Success after binutils: 3 commits new 969d92eb3ce 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 6c4340bd6dc 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 80d3d624336 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new e30a8a2d0d5 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new d29f747289d 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new fd7a4447ffa 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 5cde44e88bf 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 60e7c63366c 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new e9781e8846a 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new 1ce5deaee27 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new a1cd67ebd97 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new cc22b968e2a 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 1cc1cc64982 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 731f2e8cf22 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new bc77f92bb49 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 6a6e32e8635 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new d8e06da0ac7 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (a928742e77a) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] 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 1692 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 53140 -> 53700 bytes 04-build_abe-gcc/console.log.xz | Bin 235164 -> 235064 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9568 -> 8644 bytes 07-build_abe-glibc/console.log.xz | Bin 238256 -> 238336 bytes 08-build_abe-gdb/console.log.xz | Bin 51836 -> 51896 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3812 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2264 -> 2464 bytes 11-check_regression/console.log.xz | Bin 13292 -> 10236 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 57 +- 11-check_regression/mail-body.txt | 222 +- 11-check_regression/results.compare | 97 +- 11-check_regression/results.compare2 | 3094 ++++------------- 11-check_regression/results.regressions | 101 +- 12-update_baseline/console.log | 54 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 224 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 101 +- sumfiles/gdb.log.xz | Bin 1698856 -> 1690736 bytes sumfiles/gdb.sum | 5645 +++++++++++++++---------------- 30 files changed, 3769 insertions(+), 5876 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022