Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-aarch64-bootstrap_ubsan updated (3a039109a51 -> 84db2d0b895)

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-aarch64-bootstrap_ubsan in repository toolchain/ci/base-artifacts. from 3a039109a51 34: onsuccess: #141: 2: Success after binutils/gcc: 9 commits new 84db2d0b895 35: onsuccess: #142: 2: Success after binutils/gcc: 18 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 1676 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2780 bytes 04-build_abe-binutils/console.log.xz | Bin 37784 -> 39300 bytes 05-build_abe-bootstrap_ubsan/console.log.xz | Bin 317748 -> 322456 bytes 06-check_regression/console.log.xz | Bin 2828 -> 2892 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.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-next-defconfig updated (eb637afb552 -> 4008da047be)

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-arm-next-defconfig in repository toolchain/ci/base-artifacts. from eb637afb552 25: onsuccess: #333: boot: Success after binutils/linux/qem [...] new 4008da047be 26: onsuccess: #334: boot: Success after binutils/llvm/linu [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1704 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 30132 -> 30004 bytes 04-build_kernel_llvm/console.log.xz | Bin 65296 -> 63132 bytes 05-build_abe-qemu/console.log.xz | Bin 30556 -> 30256 bytes 06-build_linux/console.log.xz | Bin 3708 -> 3132 bytes 07-boot_linux/console.log.xz | Bin 5656 -> 5712 bytes 08-check_regression/console.log.xz | Bin 3640 -> 4096 bytes 08-check_regression/mail-body.txt | 4 ++-- 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 | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 19 files changed, 29 insertions(+), 29 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-stable-defconfig updated (af88b16944a -> 437dcf463fc)

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-stable-defconfig in repository toolchain/ci/base-artifacts. from af88b16944a 24: onsuccess: #276: boot: Success after binutils/llvm/qemu [...] new 437dcf463fc 25: onsuccess: #278: boot: Success after binutils/llvm/linu [...] 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 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2812 bytes 03-build_abe-binutils/console.log.xz | Bin 30260 -> 30720 bytes 04-build_kernel_llvm/console.log.xz | Bin 66344 -> 65908 bytes 05-build_abe-qemu/console.log.xz | Bin 30768 -> 31352 bytes 06-build_linux/console.log.xz | Bin 3384 -> 4384 bytes 07-boot_linux/console.log.xz | Bin 6268 -> 6256 bytes 08-check_regression/console.log.xz | Bin 3548 -> 4184 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.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (960678e349d -> e95b8315c7c)

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 960678e349d 202: onsuccess: #1856: 7: Success after gcc: 2 commits discards deccd0ebd40 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/ [...] discards 5aa3ff7833f 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits discards dbe35f1154d 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 1 [...] discards c683143d451 198: onsuccess: #1852: 7: Success after gcc: 5 commits discards c1bfb5d7eff 197: onsuccess: #1851: 7: Success after binutils/gcc/linux/ [...] discards 0c99ffde05b 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 4 [...] discards ca1fb9345f5 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 1 [...] discards 5e8054feb8a 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 1 [...] discards 225a3448b82 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/ [...] discards ea59af26c8a 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/ [...] discards 8dd718c7e31 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/ [...] discards 05b7d50c516 190: onsuccess: #1774: 7: Success after binutils: 10 commits discards 752556602e6 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 3 [...] discards 697f1aae5bb 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/ [...] discards 8fa7d8ba83c 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/ [...] discards 388312e8d54 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/ [...] discards 4f74cf47bbe 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] discards 2c26bf9d8c4 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/ [...] discards fe79b3d19b7 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/ [...] discards 4be5794706d 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/ [...] discards dc773725009 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/ [...] discards f2a927fc02f 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] discards e2e3ce84c46 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/ [...] discards d97032af757 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/ [...] discards d54bb048eea 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/ [...] discards f8559d21cba 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/ [...] discards 72a29d7dd43 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/ [...] discards f46bf781e3f 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 1 [...] discards c5d6c8be4fc 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/ [...] discards 9834c0ddbfe 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qem [...] discards 5581914ab86 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 1 [...] discards 2ea9212f1a5 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/ [...] discards 332c1377e7a 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/ [...] discards ceec5921481 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/ [...] discards 384f5c34967 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 2 [...] discards c534dc2cfd4 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits discards 48268e33832 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/ [...] discards ab909570f9e 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/ [...] discards f97c022484e 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 1 [...] discards 8745c021379 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 [...] discards 9e557630d8c 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/ [...] discards 82f5ad59adf 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/ [...] discards 0ce2592c710 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards d9bf8322a7a 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/ [...] discards 4d923abdab6 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards fdfe52a4fac 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards 5d09d38f2a1 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb [...] discards 51c4cd67d8f 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards f46a1bd743f 153: force: #1606: 1: Failure after basepoints/gcc-13-3004- [...] discards ecff6787d5b 152: force: #1605: 7: Success after gcc: 9 commits discards f0e52966e60 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint- [...] discards 348c191a7f7 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/ [...] discards 95ac7cb7a9b 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 2 [...] discards 82e604bcf8a 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/ [...] discards 870af70f33e 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/ [...] discards 66ad53a0280 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/ [...] discards 9cf67ce9950 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 3 [...] discards 719d7fb20e8 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 31eb355bb38 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/ [...] discards e5ea8163af6 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/ [...] discards fbafb6de524 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 [...] discards 0aace0c57c0 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 [...] discards e4a53ffc19b 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/ [...] discards 7c6ac79ab0e 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/ [...] discards 289a741c832 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 3e279de56be 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 1 [...] discards 9605c5ad5dd 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/ [...] discards 9217925a402 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/ [...] discards 5a4622ec275 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 2 [...] discards 40a11216425 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 1 [...] discards 2efa086a85b 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/ [...] discards 1f7d94242ce 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards e657fa97de6 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-2 [...] discards 41dc9a402a4 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 5dd088d82c9 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 [...] discards c7e0cbd6f53 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 0292a5c1d7b 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 [...] discards 5d8f887daa6 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 42b242cba31 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/ [...] discards bf0c9051ec9 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/ [...] discards 21644e9dab4 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/ [...] discards 4307cfa25a0 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/ [...] discards d4ce8ef71bb 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/ [...] discards 4e80eae4feb 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 [...] discards e186f339419 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qe [...] discards 8d945f28d52 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/ [...] discards beb46c42e02 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 1 [...] discards 3b394c97d43 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards 59269bc36ca 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/ [...] discards 7d7589c8666 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/ [...] discards c4b3bcc42ca 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/ [...] discards f0a553cdfab 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 51c8deb97ab 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 [...] discards 5c16f471c74 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-2 [...] discards ccadf18ba41 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/ [...] discards b674e7af536 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/ [...] discards 3858ad4c8f1 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38edde [...] discards 0ec6483302c 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/ [...] discards e6805dad0aa 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 68dd0f1a8fc 102: force: #1551: 1: Failure after gcc: 306 commits new 8897dcb3bda 102: force: #1551: 1: Failure after gcc: 306 commits new b56e83463e3 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 15eb14e3217 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/ [...] new 893699737ff 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38edde [...] new 16bbabf0a5b 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/ [...] new 36bcaa333dd 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/ [...] new 618f96b030e 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-2 [...] new 4265ddf8955 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 [...] new e23617e7c06 110: onsuccess: #1559: 7: Success after gcc: 4 commits new b718a8af431 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/ [...] new 6cd65c3718a 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/ [...] new 28c79554bf3 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/ [...] new b9036f01f58 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 2aa98e0fe2c 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 1 [...] new 353dc0209d6 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/ [...] new da31d05ae9e 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qe [...] new 8e2d597fb24 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 [...] new 0e565b7e3f4 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/ [...] new 7d24671e112 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/ [...] new 1924329c871 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/ [...] new 4c2d9bc1e64 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/ [...] new 4ac30d5eedd 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/ [...] new df366221c42 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 12a12ea6862 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 [...] new d90fe35baf9 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new f134e775cb0 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 [...] new bb9b026c343 128: onsuccess: #1579: 7: Success after linux: 12 commits new 749b88ed9ee 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-2 [...] new ca315b82af6 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new a4ffbbd7d83 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/ [...] new e4961240c13 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 1 [...] new 754cf1008b6 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 2 [...] new 0d2d12a0e68 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/ [...] new f036fac9a0a 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/ [...] new 15936dfb0dd 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 1 [...] new 30843b31d92 137: onsuccess: #1588: 7: Success after gcc: 5 commits new d8d6ff84923 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/ [...] new 061b34f8c39 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/ [...] new a8e09de6ec9 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 [...] new bff9779ee7d 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 [...] new 4157deadbca 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/ [...] new 7378880b06e 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/ [...] new 711390bde4b 144: onsuccess: #1595: 7: Success after glibc: 2 commits new 7bee7976a4f 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 3 [...] new 31430a9d688 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/ [...] new dbb5486bbbd 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/ [...] new 369cea6b8d8 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/ [...] new 59eadb77e25 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 2 [...] new 5b6400ae8d5 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/ [...] new aba9cf620ce 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint- [...] new 1ed3ccd2f5a 152: force: #1605: 7: Success after gcc: 9 commits new e51fe652b90 153: force: #1606: 1: Failure after basepoints/gcc-13-3004- [...] new 9b65df6da08 154: onsuccess: #1607: 1: Success after gcc: 2 commits new e24af26feae 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb [...] new 24d1276a1c5 156: onsuccess: #1609: 7: Success after gcc: 2 commits new fd40c89e97b 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new 0738c7e1a28 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/ [...] new d65139bdcdc 159: onsuccess: #1612: 7: Success after gcc: 4 commits new 8c53e94a628 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/ [...] new 9728ac808ca 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/ [...] new a503f25292c 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 [...] new 09aa02c80b7 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 1 [...] new f27e08561eb 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/ [...] new 67761221d16 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/ [...] new 206ddc2d4ad 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits new 3afa469fb4b 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 2 [...] new 220dc9ee543 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/ [...] new b5bd60242fe 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/ [...] new 5ed3acaa423 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/ [...] new f521ef087dd 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 1 [...] new 084a5281c4a 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qem [...] new 501baf82530 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/ [...] new ebb32fda209 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 1 [...] new 4f9d4bca9af 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/ [...] new f2416055a47 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/ [...] new a4733050f46 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/ [...] new 83c8774b93a 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/ [...] new f6a2eea088b 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/ [...] new 8e5a20b1cfd 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] new ff3d3352f1a 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/ [...] new ce3e896aa1f 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/ [...] new 7a77d94e502 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/ [...] new c143f374cb4 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/ [...] new 4bae747b68c 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] new a35fa0b7c34 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/ [...] new f02104c3c15 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/ [...] new 7c6e2beaf01 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/ [...] new 9c9d2183d8d 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 3 [...] new 5f68d0ceb76 190: onsuccess: #1774: 7: Success after binutils: 10 commits new 690ce493152 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/ [...] new 56fce58b51a 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/ [...] new 6f24e3dee5f 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/ [...] new f39e389742a 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 1 [...] new 037e6ffe64d 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 1 [...] new 2ba58198182 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 4 [...] new 2d9122ab86d 197: onsuccess: #1851: 7: Success after binutils/gcc/linux/ [...] new fae79593344 198: onsuccess: #1852: 7: Success after gcc: 5 commits new f441ac721ea 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 1 [...] new b139721a876 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits new d73c00380b2 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/ [...] new c9e8ea55a75 202: onsuccess: #1856: 7: Success after gcc: 2 commits new e95b8315c7c 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 [...] 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 (960678e349d) \ 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 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2788 bytes 04-build_abe-binutils/console.log.xz | Bin 31588 -> 32288 bytes 05-build_abe-stage1/console.log.xz | Bin 72848 -> 73852 bytes 07-build_abe-linux/console.log.xz | Bin 8536 -> 8560 bytes 08-build_abe-glibc/console.log.xz | Bin 244120 -> 246276 bytes 09-build_abe-stage2/console.log.xz | Bin 203844 -> 206908 bytes 10-build_abe-gdb/console.log.xz | Bin 38912 -> 39192 bytes 11-build_abe-qemu/console.log.xz | Bin 30732 -> 30980 bytes 12-check_regression/console.log.xz | Bin 3128 -> 3552 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++---------- 19 files changed, 56 insertions(+), 56 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm updated (6a449c2b606 -> 8b9fc9551db)

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 6a449c2b606 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 8b9fc9551db 28: onsuccess: #33: 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 1688 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 52396 -> 52228 bytes 04-build_abe-gcc/console.log.xz | Bin 234044 -> 235772 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8740 -> 8532 bytes 07-build_abe-glibc/console.log.xz | Bin 235588 -> 236176 bytes 08-build_abe-gdb/console.log.xz | Bin 51316 -> 50456 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3868 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2648 -> 2568 bytes 11-check_regression/console.log.xz | Bin 5768 -> 5960 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/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/gdb.log.xz | Bin 14496 -> 14512 bytes sumfiles/gdb.sum | 34 +++++++++++++++--------------- 25 files changed, 50 insertions(+), 50 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-lts-allnoconfig updated (e3dc8712b63 -> df0a7184355)

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-arm-lts-allnoconfig in repository toolchain/ci/base-artifacts. from e3dc8712b63 24: onsuccess: #246: all: Success after binutils/llvm/qemu: [...] new df0a7184355 25: onsuccess: #248: 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 1688 -> 1928 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 30004 -> 30536 bytes 04-build_kernel_llvm/console.log.xz | Bin 63868 -> 64788 bytes 05-build_abe-qemu/console.log.xz | Bin 30348 -> 30512 bytes 06-build_linux/console.log.xz | Bin 3424 -> 3460 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 3556 -> 4136 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.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-allnoconfig updated (ab7ec13195d -> b489d2d0c89)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-allnoconfig in repository toolchain/ci/base-artifacts. from ab7ec13195d 24: onsuccess: #478: boot: Success after binutils/llvm/linu [...] new b489d2d0c89 25: onsuccess: #481: boot: Success after binutils: 148 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 1728 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 31804 -> 31856 bytes 04-build_kernel_llvm/console.log.xz | Bin 64816 -> 66860 bytes 05-build_abe-qemu/console.log.xz | Bin 30564 -> 30856 bytes 06-build_linux/console.log.xz | Bin 3080 -> 3172 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4328 -> 2904 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 25 +++++++++++-------------- 15 files changed, 20 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (8024b4a2138 -> 4bba0b2356a)

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 8024b4a2138 376: onsuccess: #2338: 1: Success after gcc: 2 commits discards 5b9160eb5f8 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits discards 772c3ee51e1 374: onsuccess: #2336: 1: Success after gcc: 4 commits discards 8b88ef1cd15 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits discards 31268ab522b 372: onsuccess: #2334: 1: Success after gcc: 5 commits discards 4277bc49643 371: onsuccess: #2333: 1: Success after binutils: 5 commits discards ab09cda7572 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits discards c5e66321399 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits discards 8bee001d44f 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits discards 60a14794d84 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits discards 3570a50e22e 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits discards 1f6825a3686 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits discards 36052f17864 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits discards 11adee11654 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits discards c742ec380c4 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits discards 61b9e729903 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits discards a3443ba8973 360: onsuccess: #2317: 1: Success after binutils: 4 commits discards e4541b17279 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint- [...] discards d167c635ac0 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits discards 06b4fea3e1f 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits discards 8378d537d62 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits discards 87a26c5b82a 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits discards 7286466770a 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits discards f1841a28c9f 353: onsuccess: #2309: 1: Success after gcc: 7 commits discards 378fe49dd88 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits discards 6dd46831128 351: onsuccess: #2307: 1: Success after binutils: 2 commits discards eab009d8fb7 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits discards c56386954f7 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits discards 508c4ecb02d 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits discards 6a2484fc0a5 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits discards 80cce930c2e 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits discards e7a97ecbb79 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits discards 719a2d5f089 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits discards 183e32c31a3 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits discards 0c5331046dd 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits discards ec158832be1 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits discards 86f366e8150 340: onsuccess: #2296: 1: Success after gcc: 3 commits discards 3efd7fcc618 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits discards 7ab827c6507 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits discards b461d2bd105 337: onsuccess: #2293: 1: Success after gcc: 21 commits discards f5c2d131b2d 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits discards f9fb03cf26e 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits discards 5cd166c89de 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits discards 71d90297a84 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-4 [...] discards fbdd59c6156 332: onsuccess: #2288: 1: Success after gcc: 2 commits discards f9ceb1327a7 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint- [...] discards 6d2ea8bbb4f 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits discards b2d017031be 329: onsuccess: #2285: 1: Success after gcc: 8 commits discards 3c3085a901e 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint- [...] discards 8ba14b85375 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits discards a8a620b9f18 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits discards 29f04f12185 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits discards 6a5ba769055 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits discards e7ebc25fd46 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits discards 9462a586299 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits discards 1d9dc03163d 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits discards 779f7f89e96 320: onsuccess: #2274: 1: Success after gcc: 5 commits discards 77705a3e108 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits discards 789885c7fa6 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits discards a15ae5c7c46 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits discards c6696feea5e 316: onsuccess: #2270: 1: Success after gcc: 2 commits discards db3be00c9c2 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits discards f064398d0f7 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits discards c79a1f4a964 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits discards fcf41c2e9e7 312: onsuccess: #2265: 1: Success after binutils: 2 commits discards 463797cc3f2 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint- [...] discards 601e4816b8d 310: onsuccess: #2259: 1: Success after binutils: 2 commits discards 0d207ba725b 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint- [...] discards b08d0832769 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint- [...] discards 1eb42ec49c4 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint- [...] discards db7ebd616b5 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint- [...] discards f203a9c7774 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits discards 6a717559bf4 304: onsuccess: #2243: 1: Success after binutils/gcc: 23 commits discards ff18eab1a68 303: onsuccess: #2242: 1: Success after binutils/gcc: 17 commits discards 7d10496a084 302: onsuccess: #2241: 1: Success after binutils/gcc: 10 commits discards 8b8122b35e1 301: onsuccess: #2240: 1: Success after binutils/gcc: 10 commits discards c61b156d862 300: onsuccess: #2239: 1: Success after binutils/gcc: 20 commits discards 5d04911d6ac 299: onsuccess: #2238: 1: Success after binutils/gcc: 12 commits discards 614653abaef 298: onsuccess: #2237: 1: Success after binutils/gcc: 9 commits discards 06c2050da4f 297: onsuccess: #2236: 1: Success after binutils/gcc: 9 commits discards e9dc90f61e8 296: onsuccess: #2235: 1: Success after binutils/gcc: 14 commits discards 4e6e92122b6 295: onsuccess: #2234: 1: Success after binutils/gcc: 33 commits discards 514f8fb0738 294: onsuccess: #2233: 1: Success after binutils/gcc: 4 commits discards 6ff486c5c33 293: onsuccess: #2232: 1: Success after binutils/gcc: 5 commits discards b5d7eb0eec5 292: onsuccess: #2231: 1: Success after binutils/gcc: 19 commits discards 965029cd196 291: onsuccess: #2230: 1: Success after binutils/gcc: 31 commits discards 8ea7e119d06 290: onsuccess: #2229: 1: Success after binutils/gcc: 12 commits discards 8766cc89cf3 289: onsuccess: #2228: 1: Success after binutils/gcc: 11 commits discards a5a4273c6fb 288: onsuccess: #2227: 1: Success after binutils/gcc: 16 commits discards 0577468fa6d 287: onsuccess: #2226: 1: Success after binutils/gcc: 38 commits discards 53233adb70c 286: onsuccess: #2225: 1: Success after binutils/gcc: 7 commits discards 72d8d33f717 285: onsuccess: #2224: 1: Success after binutils/gcc: 2 commits discards b6f55389383 284: onsuccess: #2223: 1: Success after binutils/gcc: 5 commits discards 35f31a54e2c 283: onsuccess: #2222: 1: Success after gcc: 4 commits discards 2517c3f54bf 282: onsuccess: #2221: 1: Success after gcc: 2 commits discards 45b95cf489c 281: onsuccess: #2220: 1: Success after binutils/gcc: 4 commits discards 802f6bfb8c0 280: onsuccess: #2219: 1: Success after binutils/gcc: 10 commits discards dea6ac410b1 279: onsuccess: #2218: 1: Success after basepoints/gcc-13-3 [...] discards f481e9b6338 278: onsuccess: #2217: 1: Success after binutils: 7 commits discards b2e0d0d48bf 277: onsuccess: #2216: 1: Success after binutils: 2 commits discards eec0bd0d918 276: onsuccess: #2215: 1: Success after binutils/gcc: 44 commits new 43963ca0ee5 276: onsuccess: #2215: 1: Success after binutils/gcc: 44 commits new 8ba6ddb640c 277: onsuccess: #2216: 1: Success after binutils: 2 commits new 14d4fd16274 278: onsuccess: #2217: 1: Success after binutils: 7 commits new f56fcf2bfe9 279: onsuccess: #2218: 1: Success after basepoints/gcc-13-3 [...] new b550e435966 280: onsuccess: #2219: 1: Success after binutils/gcc: 10 commits new adbc88f9a3c 281: onsuccess: #2220: 1: Success after binutils/gcc: 4 commits new 9d96bcc7723 282: onsuccess: #2221: 1: Success after gcc: 2 commits new 46ab00e34ed 283: onsuccess: #2222: 1: Success after gcc: 4 commits new d05e7593931 284: onsuccess: #2223: 1: Success after binutils/gcc: 5 commits new 83ca1df439f 285: onsuccess: #2224: 1: Success after binutils/gcc: 2 commits new ca4a1adccc6 286: onsuccess: #2225: 1: Success after binutils/gcc: 7 commits new fa983cdf034 287: onsuccess: #2226: 1: Success after binutils/gcc: 38 commits new d1a02fae5f9 288: onsuccess: #2227: 1: Success after binutils/gcc: 16 commits new 96e9cd5cfcb 289: onsuccess: #2228: 1: Success after binutils/gcc: 11 commits new 1da47f0349c 290: onsuccess: #2229: 1: Success after binutils/gcc: 12 commits new 1f1a7f9c2dc 291: onsuccess: #2230: 1: Success after binutils/gcc: 31 commits new 72d3c22a5d9 292: onsuccess: #2231: 1: Success after binutils/gcc: 19 commits new 803a841c594 293: onsuccess: #2232: 1: Success after binutils/gcc: 5 commits new 2362bd89aec 294: onsuccess: #2233: 1: Success after binutils/gcc: 4 commits new d57ae078de7 295: onsuccess: #2234: 1: Success after binutils/gcc: 33 commits new df265350bf2 296: onsuccess: #2235: 1: Success after binutils/gcc: 14 commits new 08084d99717 297: onsuccess: #2236: 1: Success after binutils/gcc: 9 commits new 767a29bfc0a 298: onsuccess: #2237: 1: Success after binutils/gcc: 9 commits new 8134550c81e 299: onsuccess: #2238: 1: Success after binutils/gcc: 12 commits new 9708099ae13 300: onsuccess: #2239: 1: Success after binutils/gcc: 20 commits new fe5fb863b31 301: onsuccess: #2240: 1: Success after binutils/gcc: 10 commits new 227e9196825 302: onsuccess: #2241: 1: Success after binutils/gcc: 10 commits new 11231690f34 303: onsuccess: #2242: 1: Success after binutils/gcc: 17 commits new c668c8e85bc 304: onsuccess: #2243: 1: Success after binutils/gcc: 23 commits new a487e1cd3c9 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits new 8d41d0dc1ec 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint- [...] new 85277f71163 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint- [...] new 8f4128a2027 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint- [...] new c27676f851e 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint- [...] new e3b44c2f174 310: onsuccess: #2259: 1: Success after binutils: 2 commits new 718d3eb1f71 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint- [...] new e7d58d65a93 312: onsuccess: #2265: 1: Success after binutils: 2 commits new 03413d04a56 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits new 8fd194db409 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits new c8ae632b4a1 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits new 8c5a1c99774 316: onsuccess: #2270: 1: Success after gcc: 2 commits new 1884d8c8c53 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits new b743c584738 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits new a7d26f77f07 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits new b7226c97035 320: onsuccess: #2274: 1: Success after gcc: 5 commits new 444dcf9bdc7 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits new 790cc8cd552 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits new f36a348db7c 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits new 8c076475375 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits new 9a03f928827 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits new 40ed7f4df30 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits new 63f6b549fef 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits new 5a31f6405cb 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint- [...] new 1d90fe5d631 329: onsuccess: #2285: 1: Success after gcc: 8 commits new 483dde44240 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits new 809bb46fa65 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint- [...] new 580907fba5f 332: onsuccess: #2288: 1: Success after gcc: 2 commits new e6589d75f52 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-4 [...] new 0e70c7260a2 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits new 7ec217733c6 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits new 1c842368dd2 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits new 50cc52afa7d 337: onsuccess: #2293: 1: Success after gcc: 21 commits new 7050124279b 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits new 6035e15ff7d 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits new 64b281486f3 340: onsuccess: #2296: 1: Success after gcc: 3 commits new 826177bbe0d 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits new e2e982ee658 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits new 3ea3e0d125e 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits new 2c385ffd14b 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits new 291b1d351e3 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits new d6d13171fbb 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits new 64719e47932 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits new c3a5393a6fd 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits new baece422aef 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits new 1ebaac29d74 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits new 3fb7e995da3 351: onsuccess: #2307: 1: Success after binutils: 2 commits new 3462b1f337d 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits new 6b58aee94fe 353: onsuccess: #2309: 1: Success after gcc: 7 commits new 28baa8ef29c 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits new b5254ccd8c8 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits new 7828f92f8a2 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits new e32ca2cb051 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits new c254c514a82 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits new bed30b4f297 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint- [...] new 9b8c1bb58f5 360: onsuccess: #2317: 1: Success after binutils: 4 commits new ce8ef042a6e 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits new 14472a84ebd 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits new 3c3331c56ff 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits new 7fa15c19672 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits new eeb1d086431 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits new a9e5af8636d 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits new 9ce1b770276 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits new 2864130bbb3 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits new 770f07815d0 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits new 1aab191941e 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits new 5364af68359 371: onsuccess: #2333: 1: Success after binutils: 5 commits new 72287e9294d 372: onsuccess: #2334: 1: Success after gcc: 5 commits new 45f7cb68ec6 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits new 43a5836cbc9 374: onsuccess: #2336: 1: Success after gcc: 4 commits new 1409c78856a 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits new 0712c60b754 376: onsuccess: #2338: 1: Success after gcc: 2 commits new 4bba0b2356a 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 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 (8024b4a2138) \ 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 1780 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 40108 -> 39692 bytes 04-build_abe-gcc/console.log.xz | Bin 216548 -> 216036 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3848 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2568 -> 2988 bytes 07-check_regression/console.log.xz | Bin 4288 -> 4660 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 35 +- 08-update_baseline/console.log | 36 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 3601436 -> 3610816 bytes sumfiles/g++.sum | 146 +- sumfiles/gcc.log.xz | Bin 3148372 -> 3134684 bytes sumfiles/gcc.sum | 4550 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1049312 -> 1050940 bytes sumfiles/gfortran.sum | 94 +- sumfiles/libatomic.log.xz | Bin 2188 -> 2192 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 218992 -> 218644 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2552 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 452056 -> 452248 bytes sumfiles/libstdc++.sum | 10 +- 31 files changed, 2486 insertions(+), 2457 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (b63a3b3360e -> 553897ab6da)

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_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards b63a3b3360e 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 98cc57cd9c0 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 36ca3dfbe3d 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards a0af8d81a1b 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 71a87bc82b1 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 7572a51d1d0 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 2ea43c1d010 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 7b054ea04c8 107: onsuccess: #849: 1: Success after binutils: 5 commits discards cbacae92809 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 8f06d55a9d6 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards 2a7c1245ff8 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards 2b3a48b5098 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards c6798c2192e 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards a26899f7d6e 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 91567e7972e 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards 2f96a9a03c3 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards 20cd329f146 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 4dc1621e2c9 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards d027896f2f1 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards db36c72cff4 95: onsuccess: #835: 1: Success after binutils: 3 commits discards f3fa1b38c05 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 92bb328b4c5 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards d60db611484 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 65c150ee69c 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 8ff6de6b88b 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 9b3f71de24b 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 061a02eb474 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards 672cfd0a830 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 28b3434932b 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards aba16e62cef 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 7505a55e63f 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 296791af455 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 00a5fd8fbde 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards 0ac6b561627 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards b9c0196b6e1 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards 486f93017ad 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards d688db2bdbd 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards dcc6657bc17 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards 1f5fa162150 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 537d76c01a8 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards 31074a04498 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 2f0a3b84860 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards 67f4713483e 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards 8ee72e80c5e 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards eaf9845afa6 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards f7a8a05e17a 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards 7f13056d8e9 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards 00e49b69ef8 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards 5bb925b9c3c 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 41705b0a9fd 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards 4cb24f460c9 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 940eb0216cf 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 7d99b927e73 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards c6f12f6db2b 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards ebb0f78c985 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards 2e7fda5e00b 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 4d10d3d1b1b 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards b72e8e455e2 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards d292a1ca4ca 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 51ffe1af45b 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 699357f77e7 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards d9f6215df13 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards 0bbc244e290 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards 6d9685e3065 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards 0c7c072d40e 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards a82a59f8062 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 2d3340dd2be 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 774b7e23dc8 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards f8c3b814a05 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards 05bb1e94c42 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards 210627e9a24 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards 41b870f7f40 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards a11e5f0f836 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards 6b9311f974e 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards bbf61966ad2 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards bb4f8653718 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards 86192a74d11 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards d66e58d030d 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards 1d094f8b2af 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 0c091c80c0a 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards a748113b361 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards ae037d49a03 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards 7c127f1cc5b 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards e8746e57edc 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards c02cb654980 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards c15deca5b6e 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards 53ba6ab2d1c 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards 1345927d62e 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] discards 17aaa4f16f1 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] discards 2b8d4deffcd 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] discards c4e8d0ca025 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards 67508e1f2c1 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards cbc8dadb101 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 626a0fec65a 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 0a5996f9f18 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 8aad06f750d 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards ed7262575c6 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards f44f19d094d 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 91a484dee8e 16: onsuccess: 1: Successful build after binutils: 4 commits discards d62144261d4 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 64f8e7b4147 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 44a95345dff 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new d98ac7b5b81 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 732b8114e92 16: onsuccess: 1: Successful build after binutils: 4 commits new 8c23f9840b0 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 91b564c964a 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new d779adef483 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 6dc9259a13e 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new fd444438d64 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 8588424e3d0 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new d02970d7f9d 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 90489edcc1e 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 0e4daeb225a 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] new 8e2b95a2ab7 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new 46b144f2abf 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new 5f091743054 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new cebf8397443 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new e1486c3c091 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new cdbe79ed055 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new 915dc99bb51 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new d526c6a3114 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new 1c5eee00c4e 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new 283c5537bf1 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new f7df3f14c8b 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new bd6c4e41403 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new 3be0a957867 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new d03968308cb 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new 1b794365c6d 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new 858ee4ab849 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new 0e9cbdc3fc8 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 42a8986985f 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new e7c3358664a 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new 4144f4318db 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new d696b70daed 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new c83b0be18e2 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new 64796ed644e 48: onsuccess: #782: 1: Success after binutils: 8 commits new 03348761c2f 49: onsuccess: #785: 1: Success after binutils: 12 commits new 3446ca76938 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new fe799104474 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new b0925549518 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new 13622d34241 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new a55ec0eea54 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new b7adfecf8a5 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 6396ed53bfc 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 6c46a22f73c 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new 5313151b028 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new f4c912c12f7 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 693f81b0295 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new 8dac2e6d07d 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new e579b94f960 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 2efa6cd1999 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 14264ccda23 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new b3a5b3583e3 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 60a86100e98 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 9a11d5b8b68 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new c464205e727 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new a564f324361 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new b56de458998 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new f7de8b9e053 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new fa1362fa339 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new 11e6d81d2be 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new 596091df02a 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 641aa0620c2 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new c671bf2d9b4 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new f7129520eeb 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new 0ce889acbff 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new 8ecca586e3c 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new d43364c8e2b 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new 101cd347570 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new 7ff5b5fc70e 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new 713363f5a5a 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new ebb7c076730 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 7d1ec89079f 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 60b9e55573f 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new 1f5fe0a2c86 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 7cf37fc1159 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new 0c505f461a6 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 8bc3b163e7f 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new fb017fed64a 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new d643ffbb0b2 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 7338bee3d02 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 9721b2a0937 94: onsuccess: #832: 1: Success after binutils: 5 commits new 5167e2948b9 95: onsuccess: #835: 1: Success after binutils: 3 commits new e7e17115d0e 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 7dfe958af2b 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new be4228f6dbd 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new ce983730a19 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new cd0466b3775 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new 1f115a16f52 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new fe9cdd413ee 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 6a616932d16 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new f6bbb4f12f0 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new d4efb85deae 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new 25dc23d4f7d 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 89a121cc995 107: onsuccess: #849: 1: Success after binutils: 5 commits new 877c8890f73 108: onsuccess: #850: 1: Success after gcc: 2 commits new c914e298c28 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 4886d62146e 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 6231c960ef5 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new ff7cdfc7ff2 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new a1a9123d644 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new 659901d58c2 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 553897ab6da 115: onsuccess: #858: 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 (b63a3b3360e) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/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 1740 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 39084 -> 39320 bytes 04-build_abe-gcc/console.log.xz | Bin 214544 -> 213908 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8684 -> 8524 bytes 07-build_abe-glibc/console.log.xz | Bin 243288 -> 244744 bytes 08-build_abe-gdb/console.log.xz | Bin 38824 -> 39100 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3848 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2596 -> 3024 bytes 11-check_regression/console.log.xz | Bin 7792 -> 7580 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 7 - 11-check_regression/mail-body.txt | 61 +- 11-check_regression/results.compare | 45 +- 11-check_regression/results.compare2 | 218 +- 11-check_regression/results.regressions | 42 - 12-update_baseline/console.log | 46 +- 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 | 63 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 42 - sumfiles/g++.log.xz | Bin 3748248 -> 3739640 bytes sumfiles/g++.sum | 153 +- sumfiles/gcc.log.xz | Bin 3297028 -> 3295760 bytes sumfiles/gcc.sum | 4751 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1084188 -> 1078404 bytes sumfiles/gfortran.sum | 58 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 231112 -> 230948 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 453260 -> 451980 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 2700 insertions(+), 2877 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (3ed632bae76 -> 9db9947250e)

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 3ed632bae76 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 3ffde4ee914 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 49dbf33d658 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards f0ba207f11c 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 8fc9b663026 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards 803df02227a 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 67a20d21ac5 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 26863f28792 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards f909ae522d2 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 215c3a5d815 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] discards bd04c4d6f48 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] discards 80dd64f415e 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards bb7ecff74d7 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 1f9abe783d0 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 1d0ebf620e9 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 8995cf3f62d 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards f44e34635cf 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 9511e77d0a2 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 3940c47dd0a 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 94a18eb4ad9 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 9ed539d33ef 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] discards 78ee75f7a20 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] discards c2a4f087a43 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] discards 8bea0b7bdfb 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards 47daeafeea1 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] discards 3c086d1f001 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] discards 7eb4902c4fe 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] discards 903f39cdbc1 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards 836d8b75d70 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] discards 4a8ea8d5b11 92: onsuccess: #575: 1: Success after linux: 34 commits discards 0135baf38c5 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 6d7380231f4 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 971e89d33c1 89: onsuccess: #570: 1: Success after linux: 11 commits discards 307aad4be1a 88: onsuccess: #569: 1: Success after glibc: 10 commits discards b660cbdadb7 87: onsuccess: #567: 1: Success after binutils: 8 commits discards aed2b07212d 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 7dcd0fecb91 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards 3f5c9f61723 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 2d967c89e30 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] discards 856800cd7f0 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] discards 6182c064e0c 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 3c6cc9bd8fa 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] discards dd89d44836a 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] discards e9787b91d8c 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] discards 79035441b72 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] discards 5bb7ef3e388 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] discards 25e3852dc62 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] discards 62e7c83ed47 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] discards ff7c7650418 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 843e08d6335 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards a1448df8122 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] discards d4bdb73f412 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards f7b5d6bdf8c 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] discards 8c21f1733db 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] discards 64ef2076678 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] discards 2b18e6ea468 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards deed754e87c 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] discards 8806d069cac 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 5f1dea21984 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards b6f7854e6d2 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards 6f90e77e6e3 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 5ff0b1d028f 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] discards 3208658a21e 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards 6b487be0af3 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards 5df29e5af59 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] discards 5e84ec83185 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards a8170f4bebe 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 7006f9e889e 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] discards 96b6dc26030 53: onsuccess: #531: 1: Success after binutils: 12 commits discards c8b13e320e6 52: onsuccess: #528: 1: Success after binutils: 8 commits discards a6d3c289d9f 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 2f289ed4a71 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] discards 157ad65a4a7 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] discards 51dbf5c3a0b 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] discards 28db7282d0f 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] discards be991b7475b 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] discards f3122399d66 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] discards 640c1d32935 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] discards 32c3406e43b 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] discards f94233b5afa 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] discards 7f7581495ba 41: onsuccess: #514: 1: Success after linux: 64 commits discards 8643eeb5a40 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] discards 11a89a55d1d 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 248cba77148 38: onsuccess: #508: 1: Success after binutils: 3 commits discards 597dd9d0115 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] discards 25ef3f7b488 36: onsuccess: #505: 1: Success after glibc: 3 commits discards 4e2174c5abe 35: onsuccess: #503: 1: Success after binutils: 11 commits discards 7e8494cafcf 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards c2e77101c75 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gd [...] discards c6410390c25 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] discards c28a3573b50 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] discards dac3f3c4556 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards c53568fab64 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards de9ed32d184 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gd [...] discards 40fd8d18c6d 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] discards bfde8daa300 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gl [...] discards 1432182e357 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] discards 8f46a2c789d 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards d3dbdf7fd00 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 3dd53e81bde 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards ad573a86c97 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new a3014753926 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new a81d02c10af 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 0e922d9b48f 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 2961f6090e5 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 22c023c952f 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] new dea1f443d4e 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gl [...] new 4e745b76c75 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] new b2b81e308ae 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gd [...] new 9f5e748f745 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new 86605ef381c 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new b7d055dc08e 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] new a40c0d77f06 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] new 5fd1433ca2a 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gd [...] new 95d662d05fa 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new b64501ae415 35: onsuccess: #503: 1: Success after binutils: 11 commits new eded03ed33c 36: onsuccess: #505: 1: Success after glibc: 3 commits new d9a3a1d3454 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] new a21a87a4284 38: onsuccess: #508: 1: Success after binutils: 3 commits new f90ce046e11 39: onsuccess: #511: 1: Success after binutils: 8 commits new ca7317baf03 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] new 6fa91217741 41: onsuccess: #514: 1: Success after linux: 64 commits new a6f03da4098 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] new 2f0fb84f753 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] new b45cf3d11b0 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] new 2b35bb7494b 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] new c9178d3a0c6 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] new 829ecf11bbc 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] new f93eda94fbb 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] new 9541f98ab7c 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] new db930204eee 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] new 2d39c55c2d4 51: onsuccess: #525: 1: Success after binutils: 8 commits new e6c7eb22f62 52: onsuccess: #528: 1: Success after binutils: 8 commits new 4f54f5a902a 53: onsuccess: #531: 1: Success after binutils: 12 commits new 92fce90c599 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] new ed87f331131 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new cf9a6e3e086 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new 704765f6ef6 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] new 0f6226df876 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new a94b8288266 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new 8e5e0dd46b5 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] new 4422ffcbc5e 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new 58033a75abb 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new 21aed2184e9 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new cf77f387283 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 71a862f50db 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] new 08eb0557bec 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new c4d953835d1 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] new 61617b7cc58 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] new b6a45c046e2 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] new d060ad86157 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 172441ec5c7 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] new b3ccbdd733f 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 9c8dad0343f 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new d092b1277ad 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] new 1ec01b0e5df 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] new 2565c122092 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] new 84a1041dd5a 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] new 3c8ed76cbad 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] new c47da6dc0e5 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] new 307b7219e5a 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] new 5b439773e09 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new e47afd3f071 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] new 34cfb0ec6f1 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] new ec53af3b193 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 2ca3b5c626d 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new 5d69159c26a 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new 6af2edfabb0 87: onsuccess: #567: 1: Success after binutils: 8 commits new 3c61ea3a814 88: onsuccess: #569: 1: Success after glibc: 10 commits new 917ce7be524 89: onsuccess: #570: 1: Success after linux: 11 commits new ae10f32a210 90: onsuccess: #572: 1: Success after binutils: 15 commits new 604d2dafe22 91: onsuccess: #574: 1: Success after glibc: 3 commits new 1c3d83ead46 92: onsuccess: #575: 1: Success after linux: 34 commits new 37c47d71d50 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] new e1b14757edc 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new 8ac03caa66c 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] new 12fc42f8fea 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] new ffe4f58cec5 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] new 406cba70194 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new 2bc8b6c7cfc 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] new 1c66282d3af 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] new 418e239be24 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] new 9ed9c077796 102: onsuccess: #586: 1: Success after binutils: 5 commits new 467e89412b4 103: onsuccess: #589: 1: Success after binutils: 3 commits new 0f49cbfdbe9 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new e6b73a9fbee 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 0402ff47c46 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 5554b34b4b5 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new dbf2a83a5a6 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 64cb2fd63ad 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new bdd1826a153 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 4507c5bd915 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new 6332d559124 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new 8c56c204d40 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new b45599a0356 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new add9779cd1e 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new a76701ad4cb 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 9dc9a9658ec 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new b737eeb7c8b 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 1dc099777e3 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new f6e2a5ba4ac 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new e7ffd6075cb 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 9db9947250e 122: onsuccess: #609: 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 (3ed632bae76) \ 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 1740 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 52008 -> 53680 bytes 04-build_abe-gcc/console.log.xz | Bin 237172 -> 237236 bytes 06-build_abe-linux/console.log.xz | Bin 8780 -> 8620 bytes 07-build_abe-glibc/console.log.xz | Bin 236752 -> 236696 bytes 08-build_abe-gdb/console.log.xz | Bin 51708 -> 51188 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3820 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2044 -> 2460 bytes 11-check_regression/console.log.xz | Bin 20544 -> 16968 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 39 +- 11-check_regression/mail-body.txt | 178 +- 11-check_regression/results.compare | 80 +- 11-check_regression/results.compare2 | 2570 ++---------------- 11-check_regression/results.regressions | 80 +- 12-update_baseline/console.log | 32 +- 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 | 180 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 80 +- sumfiles/gdb.log.xz | Bin 1761932 -> 1728696 bytes sumfiles/gdb.sum | 4510 ++----------------------------- 30 files changed, 859 insertions(+), 6946 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022