Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-next-allmodconfig updated (4ed8b816fd -> 07bddb06a2)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-next-allmodconfig in repository toolchain/ci/base-artifacts. from 4ed8b816fd 21: onsuccess: #567: 33: Success after binutils/gcc/linux/qe [...] new 07bddb06a2 22: onsuccess: #568: 33: Success after binutils/gcc/linux/qe [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1688 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 30180 -> 30472 bytes 04-build_abe-stage1/console.log.xz | Bin 90632 -> 92620 bytes 05-build_abe-qemu/console.log.xz | Bin 32056 -> 31832 bytes 06-build_linux/console.log.xz | Bin 5008 -> 4852 bytes 08-check_regression/console.log.xz | Bin 4404 -> 4452 bytes 09-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 33 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_gcc_bootstrap/release-arm-bootstrap_debug updated (86afc50101 -> a1e598a862)

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 86afc50101 25: onsuccess: #148: 2: Success after binutils/gcc: 11 commits new a1e598a862 26: onsuccess: #149: 2: Success after binutils/gcc: 11 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1704 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 51592 -> 51988 bytes 05-build_abe-bootstrap_debug/console.log.xz | Bin 461768 -> 464884 bytes 06-check_regression/console.log.xz | Bin 2932 -> 2820 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- manifest.sh | 20 ++++++++++---------- 9 files changed, 13 insertions(+), 13 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 (de6fdfc460 -> cde30173cb)

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 de6fdfc460 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/g [...] discards b3dff1171e 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/g [...] discards eb257ce023 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] discards a1be47d725 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards 1df6025dcd 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/g [...] discards 0fee689b68 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards c90979ecbe 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/g [...] discards 0618d7ed04 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/g [...] discards 26ed6fa443 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 15 [...] discards 61262cbf23 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards b1bdf2c722 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qemu [...] discards e7103bf2de 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 12 [...] discards 3c97d8501d 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/g [...] discards 81c03037fc 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/g [...] discards 282d075670 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/g [...] discards 56428c297b 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 28 [...] discards 2cd6815f82 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits discards 13da254433 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/g [...] discards 2fb64b0c52 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/g [...] discards 146ec33247 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 12 [...] discards 772b22686b 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 commits discards 52edff61fd 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/g [...] discards ea63975359 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 23ddf76d06 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards 0c373f4bdb 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] discards 7897c81c5d 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards d87032aff3 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards 6de85b8c63 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] discards dbef2ef054 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards 16a589f0bc 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] discards de47596c18 152: force: #1605: 7: Success after gcc: 9 commits discards 8a7be0b1da 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] discards c571c5c6cd 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] discards 5b1fd968bf 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards 94641d1a45 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards ea00179fe6 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards 370d4ec0b2 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards 902587c5ae 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards abd2406f54 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards eda1fcbc70 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards 65bd8740a8 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards 5f43879e6c 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 289f4e73f4 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards d92b52e23e 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards 6ac180f569 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards 29807a9346 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 5e94736b9f 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards a34472abf7 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards 0a9df52c29 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 8798dda3d5 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards d940526186 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards d597a0588a 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 8244f35ab1 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 6b02e8920b 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards bbba2ec9f5 128: onsuccess: #1579: 7: Success after linux: 12 commits discards c180783488 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards cd9e0256ae 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 4bfb5f680d 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 2de49161d9 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards f9cde2525c 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards 87db0aca81 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 0b2dc41d5e 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards b440733880 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards 4035892055 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 466f0940d6 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards 4d442b75b6 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 74354fcb3d 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards a172418056 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards dfa347bf05 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards a72ce66c0e 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards 17fdbbbf00 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards 2f421d6ac3 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 1befc4f0a1 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards a2a1da17f0 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 2734534b69 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 839b1d88a4 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 6e4d1b2a03 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 160647f5a9 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards ff9d7c75f5 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards 6d50c20b53 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards d28f8e20b4 102: force: #1551: 1: Failure after gcc: 306 commits discards 892fe9b850 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 2d542e9ae9 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 942f99ccfd 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards e82eb42369 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 4305791f54 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards caaaa4dd10 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 91d2d9bf57 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards aff0435a1a 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 1fd2c1d853 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 9d3c7ab69f 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 80df83eee6 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 2226467ea8 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 3f8fd3461c 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 1a257eb304 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards a951338673 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards ba61013f07 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 99804fc682 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 6e7556250e 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards ae3c6c683e 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 44c34ec53a 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 511a5b3c96 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 162a879826 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 0aa97095ba 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new c76c8d641f 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 53402a6cfd 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 26ae2b0d2f 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 26bf09d1d5 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new f918e02218 89: onsuccess: 7: Success after gcc/glibc: 8 commits new a211899d9b 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new a4e1e6f64a 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 60b7ca7c26 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 46183bd725 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new ae466b57cb 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 0d3b2c985a 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 5403ac796f 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new a43ff81ee2 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new e0a5e5f25c 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 798efe63d3 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 6114f4765a 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 8e057fffbf 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 55d78b2c2d 102: force: #1551: 1: Failure after gcc: 306 commits new 56f296c3b2 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 45c9afd2db 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 23df14049b 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 3e838d9eb7 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new b3a2ac8420 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new cedbbe533e 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new e75ef835db 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new f1268b03a1 110: onsuccess: #1559: 7: Success after gcc: 4 commits new aa2d10b99b 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new 68c6af84f1 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 96272f6234 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new 531000861d 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new e4ea6c0fc4 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new c86219730c 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new e7d64f8a6d 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new e8bee6ac43 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new 90919de149 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new 60b7556eb0 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 6144ba056b 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 700179dd17 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new c4fc5ae80e 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new 9451f0ef39 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new a9a602be56 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new b3aab877cc 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 516f5a6140 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new b1f595af9f 128: onsuccess: #1579: 7: Success after linux: 12 commits new 177e6be6b8 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new 35f22f33b5 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 3f6f198f77 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new ab98198f47 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 77df9127b6 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new f790823a0a 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new 8f22cdb4df 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new 3bb19391b6 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new 8617313458 137: onsuccess: #1588: 7: Success after gcc: 5 commits new e09e08ad2f 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new df573feab2 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new ac516f5d04 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new 44d466a228 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new 377879ea01 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new 26e310023d 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new 7b71410976 144: onsuccess: #1595: 7: Success after glibc: 2 commits new 90c5b71edc 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new f7b8b9a847 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new a92c143c1d 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new 7837134986 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new ec5e67148c 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new dedace796c 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] new 0c274347c6 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] new 0dff734dd1 152: force: #1605: 7: Success after gcc: 9 commits new fb526c24c3 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] new 30ae7e309d 154: onsuccess: #1607: 1: Success after gcc: 2 commits new f655892f4d 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] new 0b48d08d55 156: onsuccess: #1609: 7: Success after gcc: 2 commits new 1bfeba596d 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new 24c2f9d317 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] new 3bb600ffaf 159: onsuccess: #1612: 7: Success after gcc: 4 commits new efe94ab4b5 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new e056d78387 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/g [...] new 867a6060cc 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 commits new b4fbe692ed 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 12 [...] new e3398da657 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/g [...] new c558c1c690 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/g [...] new 520707e3e7 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits new a5424d1d4c 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 28 [...] new af8d7e3814 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/g [...] new 2410a58019 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/g [...] new 26b3777363 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/g [...] new 3b4466580b 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 12 [...] new ad0cb9ea60 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qemu [...] new 23ab2a2d1a 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new cd7098b372 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 15 [...] new 1c7188dd10 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/g [...] new f47344405f 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/g [...] new ba9fc3e23a 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 74dd152fb8 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/g [...] new efec9e3420 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 69bc72c17d 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] new 58c2c169bd 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/g [...] new 34bd4f155b 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/g [...] new cde30173cb 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (de6fdfc460) \ 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 1696 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2748 bytes 04-build_abe-binutils/console.log.xz | Bin 31056 -> 30516 bytes 05-build_abe-stage1/console.log.xz | Bin 72992 -> 73044 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 9580 -> 8456 bytes 08-build_abe-glibc/console.log.xz | Bin 239776 -> 239648 bytes 09-build_abe-stage2/console.log.xz | Bin 205356 -> 203880 bytes 10-build_abe-gdb/console.log.xz | Bin 38268 -> 38024 bytes 11-build_abe-qemu/console.log.xz | Bin 32224 -> 32068 bytes 12-check_regression/console.log.xz | Bin 5348 -> 4532 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 ++++++++++----------- 22 files changed, 62 insertions(+), 62 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 (71d21b8c26 -> 326198556b)

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. from 71d21b8c26 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 326198556b 83: onsuccess: #562: 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 1692 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 51768 -> 50616 bytes 04-build_abe-gcc/console.log.xz | Bin 233252 -> 235760 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9300 -> 8672 bytes 07-build_abe-glibc/console.log.xz | Bin 234828 -> 233576 bytes 08-build_abe-gdb/console.log.xz | Bin 49764 -> 49700 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3864 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2272 -> 2348 bytes 11-check_regression/console.log.xz | Bin 12672 -> 11876 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 33 +- 11-check_regression/mail-body.txt | 174 +- 11-check_regression/results.compare | 76 +- 11-check_regression/results.compare2 | 466 +- 11-check_regression/results.regressions | 76 +- 12-update_baseline/console.log | 9 + 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 | 176 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 76 +- sumfiles/gdb.log.xz | Bin 1718144 -> 1686028 bytes sumfiles/gdb.sum | 7307 ++++++++++++++++++++----------- 31 files changed, 5214 insertions(+), 3233 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_gcc/master-aarch64 updated (2ac71a4542 -> 533d422d73)

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. from 2ac71a4542 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 533d422d73 79: onsuccess: #816: 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 1700 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 38056 -> 38148 bytes 04-build_abe-gcc/console.log.xz | Bin 212668 -> 213512 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9192 -> 8408 bytes 07-build_abe-glibc/console.log.xz | Bin 239780 -> 239204 bytes 08-build_abe-gdb/console.log.xz | Bin 37636 -> 37748 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3840 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2836 -> 2652 bytes 11-check_regression/console.log.xz | Bin 7860 -> 8700 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 754 +++-- 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 | 36 +- sumfiles/g++.log.xz | Bin 3762784 -> 3737188 bytes sumfiles/g++.sum | 194 +- sumfiles/gcc.log.xz | Bin 3269092 -> 3280340 bytes sumfiles/gcc.sum | 5269 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1075008 -> 1080656 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 222748 -> 221728 bytes sumfiles/libgomp.sum | 228 +- sumfiles/libitm.log.xz | Bin 2676 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 449172 -> 443168 bytes sumfiles/libstdc++.sum | 14 +- 37 files changed, 3507 insertions(+), 3074 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_kernel/gnu-master-aarch64-lts-allnoconfig updated (5a3cbee090 -> 43e1c6c395)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-allnoconfig in repository toolchain/ci/base-artifacts. from 5a3cbee090 17: onsuccess: #459: boot: Success after binutils/gcc/qemu: [...] new 43e1c6c395 18: onsuccess: #460: boot: Success after binutils/gcc/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1692 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30400 -> 31188 bytes 04-build_abe-stage1/console.log.xz | Bin 72676 -> 73276 bytes 05-build_abe-qemu/console.log.xz | Bin 32036 -> 32148 bytes 06-build_linux/console.log.xz | Bin 3304 -> 3320 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3964 -> 4292 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 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_kernel/llvm-master-aarch64-lts-defconfig updated (3bc04f441b -> 0f284601ee)

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-lts-defconfig in repository toolchain/ci/base-artifacts. from 3bc04f441b 17: onsuccess: #467: boot: Success after binutils/llvm/qemu: [...] new 0f284601ee 18: onsuccess: #468: boot: 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 1696 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30340 -> 30564 bytes 04-build_kernel_llvm/console.log.xz | Bin 66120 -> 66216 bytes 05-build_abe-qemu/console.log.xz | Bin 32292 -> 32040 bytes 06-build_linux/console.log.xz | Bin 3464 -> 3500 bytes 07-boot_linux/console.log.xz | Bin 6028 -> 6080 bytes 08-check_regression/console.log.xz | Bin 4064 -> 4192 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_kernel/llvm-master-arm-stable-allmodconfig updated (28e37e8015 -> 2532493f72)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-stable-allmodconfig in repository toolchain/ci/base-artifacts. from 28e37e8015 34: onsuccess: #506: 23022: Success after binutils/llvm/linu [...] new 2532493f72 35: onsuccess: #507: 23022: 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 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30452 -> 30328 bytes 04-build_kernel_llvm/console.log.xz | Bin 65048 -> 64732 bytes 05-build_abe-qemu/console.log.xz | Bin 31856 -> 31704 bytes 06-build_linux/console.log.xz | Bin 4968 -> 5208 bytes 08-check_regression/console.log.xz | Bin 4580 -> 4324 bytes 08-check_regression/mail-body.txt | 2 +- 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 | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 26 insertions(+), 26 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-arm updated (38280d55a8 -> 1f6fc6ba2e)

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-arm in repository toolchain/ci/base-artifacts. discards 38280d55a8 250: onsuccess: #1871: 1: Success after binutils/gcc: 11 commits discards 61de1242c6 249: onsuccess: #1870: 1: Success after binutils/gcc: 9 commits discards 353be1ccf2 248: onsuccess: #1869: 1: Success after gcc: 4 commits discards c8855926cb 247: onsuccess: #1868: 1: Success after binutils/gcc: 7 commits discards 72f1738e36 246: onsuccess: #1867: 1: Success after binutils/gcc: 8 commits discards b3ff02628c 245: onsuccess: #1866: 1: Success after binutils/gcc: 8 commits discards daed2b0aec 244: onsuccess: #1865: 1: Success after gcc: 6 commits discards ccb4dd4b02 243: onsuccess: #1864: 1: Success after binutils/gcc: 6 commits discards 4000fe90be 242: onsuccess: #1863: 1: Success after binutils/gcc: 17 commits discards f5158cf9ee 241: onsuccess: #1862: 1: Success after binutils/gcc: 5 commits discards 00604e5f09 240: onsuccess: #1861: 1: Success after gcc: 6 commits discards a2ee8bc317 239: onsuccess: #1860: 1: Success after binutils/gcc: 9 commits discards f976c58b46 238: onsuccess: #1859: 1: Success after binutils/gcc: 14 commits discards 89e41d4f31 237: onsuccess: #1858: 1: Success after binutils/gcc: 6 commits discards d970f27ec0 236: onsuccess: #1857: 1: Success after binutils/gcc: 10 commits discards f360095626 235: onsuccess: #1856: 1: Success after binutils/gcc: 18 commits discards 78270e114d 234: onsuccess: #1855: 1: Success after binutils/gcc: 7 commits discards 120df903b6 233: onsuccess: #1854: 1: Success after binutils/gcc: 6 commits discards 3b01febae0 232: onsuccess: #1853: 1: Success after binutils: 3 commits discards 23bd836817 231: onsuccess: #1852: 1: Success after binutils/gcc: 4 commits discards 3ecb7fceb2 230: onsuccess: #1851: 1: Success after basepoints/gcc-13-34 [...] discards 53df601cd4 229: onsuccess: #1850: 1: Success after basepoints/gcc-13-34 [...] discards eec709e3b1 228: onsuccess: #1849: 1: Success after binutils/gcc: 3 commits discards 7f828fdd2b 227: onsuccess: #1848: 1: Success after binutils/gcc: 4 commits discards a4ed1ec584 226: onsuccess: #1847: 1: Success after binutils/gcc: 8 commits discards ba50af592b 225: onsuccess: #1846: 1: Success after binutils/gcc: 18 commits discards a3ca74b3c4 224: onsuccess: #1845: 1: Success after binutils/gcc: 9 commits discards 7d83e0a09b 223: onsuccess: #1844: 1: Success after gcc: 7 commits discards 183321ab65 222: onsuccess: #1843: 1: Success after binutils/gcc: 17 commits discards 1f3cbfbf24 221: onsuccess: #1842: 1: Success after binutils/gcc: 15 commits discards 6e6b3f8f13 220: onsuccess: #1841: 1: Success after binutils/gcc: 10 commits discards 620badd399 219: onsuccess: #1840: 1: Success after gcc: 7 commits discards 39cd4664ef 218: onsuccess: #1839: 1: Success after binutils/gcc: 23 commits discards 162123ae5f 217: onsuccess: #1838: 1: Success after binutils/gcc: 12 commits discards 42ccbd3124 216: onsuccess: #1837: 1: Success after binutils/gcc: 4 commits discards f10b61ada6 215: onsuccess: #1836: 1: Success after binutils/gcc: 2 commits discards 1f5c36b18e 214: onsuccess: #1835: 1: Success after binutils/gcc: 30 commits discards 7886262961 213: onsuccess: #1834: 1: Success after binutils/gcc: 8 commits discards d87cc9eee4 212: onsuccess: #1833: 1: Success after binutils/gcc: 8 commits discards c2923c2d92 211: onsuccess: #1832: 1: Success after binutils/gcc: 26 commits discards 5ca19fe8d9 210: onsuccess: #1830: 1: Success after binutils/gcc: 10 commits discards 5e2439d766 209: onsuccess: #1829: 1: Success after binutils/gcc: 4 commits discards 20f8f0ee85 208: onsuccess: #1828: 1: Success after binutils: 2 commits discards a9b34bfb88 207: onsuccess: #1827: 1: Success after gcc: 2 commits discards 773ef5406d 206: onsuccess: #1826: 1: Success after binutils/gcc: 5 commits discards da46f717af 205: onsuccess: #1825: 1: Success after gcc: 3 commits discards 4b50765a8c 204: onsuccess: #1824: 1: Success after gdb-12-branchpoint-2 [...] discards 671642fa5a 203: onsuccess: #1823: 1: Success after binutils/gcc: 3 commits discards c7df986e87 202: onsuccess: #1822: 1: Success after binutils/gcc: 10 commits discards df84a2054f 201: onsuccess: #1821: 1: Success after binutils/gcc: 19 commits discards 9c32ed8994 200: onsuccess: #1820: 1: Success after binutils/gcc: 19 commits discards 9af67a3ec8 199: onsuccess: #1819: 1: Success after binutils/gcc: 5 commits discards d31b7aefeb 198: onsuccess: #1818: 1: Success after binutils/gcc: 5 commits discards d69fde0fcc 197: onsuccess: #1817: 1: Success after gcc: 13 commits discards da0fc1c240 196: onsuccess: #1816: 1: Success after binutils/gcc: 5 commits discards a5fcbab5c1 195: onsuccess: #1815: 1: Success after binutils/gcc: 4 commits discards 22cf87b9c5 194: onsuccess: #1814: 1: Success after binutils/gcc: 8 commits discards d08f71d687 193: onsuccess: #1813: 1: Success after binutils/gcc: 17 commits discards b63e326688 192: onsuccess: #1812: 1: Success after binutils/gcc: 11 commits discards fc6ac014fc 191: onsuccess: #1811: 1: Success after binutils/gcc: 6 commits discards 825d90e729 190: onsuccess: #1810: 1: Success after binutils/gcc: 6 commits discards 90288216cf 189: onsuccess: #1809: 1: Success after binutils/gcc: 33 commits discards c080d23d6b 188: onsuccess: #1808: 1: Success after binutils/gcc: 15 commits discards f8295851b1 187: onsuccess: #1807: 1: Success after binutils/gcc: 7 commits discards 3d2d99d45b 186: onsuccess: #1806: 1: Success after binutils/gcc: 11 commits discards 48f58021ff 185: onsuccess: #1805: 1: Success after binutils/gcc: 18 commits discards 9b2cab4d3c 184: onsuccess: #1804: 1: Success after binutils/gcc: 16 commits discards c0e1f8418c 183: onsuccess: #1803: 1: Success after binutils/gcc: 4 commits discards e493b8141d 182: onsuccess: #1802: 1: Success after gcc: 2 commits discards 4564545d65 181: onsuccess: #1801: 1: Success after basepoints/gcc-13-31 [...] discards 04b8ee0582 180: onsuccess: #1800: 1: Success after binutils/gcc: 2 commits discards dee84301bf 179: onsuccess: #1799: 1: Success after basepoints/gcc-13-31 [...] discards 584ef056c5 178: onsuccess: #1798: 1: Success after gdb-12-branchpoint-2 [...] discards 110444aeb4 177: onsuccess: #1797: 1: Success after gdb-12-branchpoint-2 [...] discards 0d802469ec 176: onsuccess: #1796: 1: Success after binutils/gcc: 3 commits discards 4462f4cca2 175: onsuccess: #1795: 1: Success after binutils/gcc: 7 commits discards edb22abb48 174: onsuccess: #1794: 1: Success after binutils/gcc: 17 commits discards 6462b06b43 173: onsuccess: #1793: 1: Success after gcc: 12 commits discards f45d446d01 172: onsuccess: #1792: 1: Success after binutils/gcc: 4 commits discards d39803a121 171: onsuccess: #1791: 1: Success after binutils/gcc: 7 commits discards db2b36cad2 170: onsuccess: #1790: 1: Success after binutils/gcc: 9 commits discards 709376fa19 169: onsuccess: #1789: 1: Success after binutils/gcc: 30 commits discards 3d94087fc8 168: onsuccess: #1788: 1: Success after binutils/gcc: 9 commits discards b1c342bea2 167: onsuccess: #1787: 1: Success after gcc: 8 commits discards e87c2105a5 166: onsuccess: #1786: 1: Success after gcc: 10 commits discards 5e8fb9c927 165: onsuccess: #1785: 1: Success after binutils/gcc: 6 commits discards fb07301145 164: onsuccess: #1784: 1: Success after binutils/gcc: 11 commits discards cc29b55a09 163: onsuccess: #1783: 1: Success after binutils/gcc: 8 commits discards 0db5b41d15 162: onsuccess: #1782: 1: Success after binutils/gcc: 14 commits discards b62188ae19 161: onsuccess: #1781: 1: Success after binutils/gcc: 16 commits discards f27de09a44 160: onsuccess: #1780: 1: Success after binutils/gcc: 4 commits discards 75b382a49b 159: onsuccess: #1779: 1: Success after gcc: 2 commits discards 971089b6e1 158: onsuccess: #1778: 1: Success after binutils/gcc: 30 commits discards a98144fb16 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 commits discards 164f56d155 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits discards e67aca2b70 155: onsuccess: #1775: 1: Success after binutils: 2 commits discards 855d0a43eb 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits discards b3aa40eb85 153: onsuccess: #1773: 1: Success after gcc: 4 commits discards c9137cae05 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits discards 2da336b040 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] discards 69dbdcc138 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] new 0c2e003694 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] new e478ac644f 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] new 80ccb1e988 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits new 3731af8ad6 153: onsuccess: #1773: 1: Success after gcc: 4 commits new dc13eb3c2a 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits new d82dd7852e 155: onsuccess: #1775: 1: Success after binutils: 2 commits new 7edd221985 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits new 3c35d3d4f7 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 commits new 2b0351e2b5 158: onsuccess: #1778: 1: Success after binutils/gcc: 30 commits new 1ec943fa79 159: onsuccess: #1779: 1: Success after gcc: 2 commits new 21a8827014 160: onsuccess: #1780: 1: Success after binutils/gcc: 4 commits new e981f3f0f7 161: onsuccess: #1781: 1: Success after binutils/gcc: 16 commits new c5c3a2995e 162: onsuccess: #1782: 1: Success after binutils/gcc: 14 commits new bc8498bbcc 163: onsuccess: #1783: 1: Success after binutils/gcc: 8 commits new b5c72837de 164: onsuccess: #1784: 1: Success after binutils/gcc: 11 commits new 9b1e01e3e5 165: onsuccess: #1785: 1: Success after binutils/gcc: 6 commits new 3dd10a96c5 166: onsuccess: #1786: 1: Success after gcc: 10 commits new 1b76fdaa2f 167: onsuccess: #1787: 1: Success after gcc: 8 commits new 2482253516 168: onsuccess: #1788: 1: Success after binutils/gcc: 9 commits new 1bbe02ccdc 169: onsuccess: #1789: 1: Success after binutils/gcc: 30 commits new 7e0d8201d2 170: onsuccess: #1790: 1: Success after binutils/gcc: 9 commits new d2fdbc7939 171: onsuccess: #1791: 1: Success after binutils/gcc: 7 commits new 86153fa6db 172: onsuccess: #1792: 1: Success after binutils/gcc: 4 commits new 76920f0f4e 173: onsuccess: #1793: 1: Success after gcc: 12 commits new a1c5c9ef6c 174: onsuccess: #1794: 1: Success after binutils/gcc: 17 commits new 46e1e371b6 175: onsuccess: #1795: 1: Success after binutils/gcc: 7 commits new 75261bc9c0 176: onsuccess: #1796: 1: Success after binutils/gcc: 3 commits new 7842c6504b 177: onsuccess: #1797: 1: Success after gdb-12-branchpoint-2 [...] new bdb3a275b0 178: onsuccess: #1798: 1: Success after gdb-12-branchpoint-2 [...] new c290ee8bd8 179: onsuccess: #1799: 1: Success after basepoints/gcc-13-31 [...] new 98ed0f9e78 180: onsuccess: #1800: 1: Success after binutils/gcc: 2 commits new 748677a1d8 181: onsuccess: #1801: 1: Success after basepoints/gcc-13-31 [...] new 1fcbfcbbdf 182: onsuccess: #1802: 1: Success after gcc: 2 commits new bf650b957b 183: onsuccess: #1803: 1: Success after binutils/gcc: 4 commits new 5bf4e0d39b 184: onsuccess: #1804: 1: Success after binutils/gcc: 16 commits new b925778a17 185: onsuccess: #1805: 1: Success after binutils/gcc: 18 commits new 977bd5b7bc 186: onsuccess: #1806: 1: Success after binutils/gcc: 11 commits new 5c8d586449 187: onsuccess: #1807: 1: Success after binutils/gcc: 7 commits new d9465ce776 188: onsuccess: #1808: 1: Success after binutils/gcc: 15 commits new f21f2edde1 189: onsuccess: #1809: 1: Success after binutils/gcc: 33 commits new d4bb65fc79 190: onsuccess: #1810: 1: Success after binutils/gcc: 6 commits new 5f9830c43a 191: onsuccess: #1811: 1: Success after binutils/gcc: 6 commits new a83cc1cbe7 192: onsuccess: #1812: 1: Success after binutils/gcc: 11 commits new fb44e04426 193: onsuccess: #1813: 1: Success after binutils/gcc: 17 commits new e96fa72517 194: onsuccess: #1814: 1: Success after binutils/gcc: 8 commits new 3b92fe2af3 195: onsuccess: #1815: 1: Success after binutils/gcc: 4 commits new cf4b17d6dc 196: onsuccess: #1816: 1: Success after binutils/gcc: 5 commits new f7092df28e 197: onsuccess: #1817: 1: Success after gcc: 13 commits new eafbd27f4b 198: onsuccess: #1818: 1: Success after binutils/gcc: 5 commits new abeed9f66e 199: onsuccess: #1819: 1: Success after binutils/gcc: 5 commits new 42b4a3aff0 200: onsuccess: #1820: 1: Success after binutils/gcc: 19 commits new d7d1a19e80 201: onsuccess: #1821: 1: Success after binutils/gcc: 19 commits new 680bd131aa 202: onsuccess: #1822: 1: Success after binutils/gcc: 10 commits new a920f24f2d 203: onsuccess: #1823: 1: Success after binutils/gcc: 3 commits new 39e13c71dd 204: onsuccess: #1824: 1: Success after gdb-12-branchpoint-2 [...] new a11da81ffe 205: onsuccess: #1825: 1: Success after gcc: 3 commits new a7d2fa0c53 206: onsuccess: #1826: 1: Success after binutils/gcc: 5 commits new fc20c6c0d9 207: onsuccess: #1827: 1: Success after gcc: 2 commits new affaef2234 208: onsuccess: #1828: 1: Success after binutils: 2 commits new ad3b83db49 209: onsuccess: #1829: 1: Success after binutils/gcc: 4 commits new a08c4e197b 210: onsuccess: #1830: 1: Success after binutils/gcc: 10 commits new 3cc44ca479 211: onsuccess: #1832: 1: Success after binutils/gcc: 26 commits new ff785c3977 212: onsuccess: #1833: 1: Success after binutils/gcc: 8 commits new 348a436ed4 213: onsuccess: #1834: 1: Success after binutils/gcc: 8 commits new f1194532e5 214: onsuccess: #1835: 1: Success after binutils/gcc: 30 commits new 5642d4c4fa 215: onsuccess: #1836: 1: Success after binutils/gcc: 2 commits new 830a1fcd2d 216: onsuccess: #1837: 1: Success after binutils/gcc: 4 commits new ede4dee91c 217: onsuccess: #1838: 1: Success after binutils/gcc: 12 commits new a752980e17 218: onsuccess: #1839: 1: Success after binutils/gcc: 23 commits new d239cd1efd 219: onsuccess: #1840: 1: Success after gcc: 7 commits new 074137d597 220: onsuccess: #1841: 1: Success after binutils/gcc: 10 commits new 767c2f167f 221: onsuccess: #1842: 1: Success after binutils/gcc: 15 commits new 787df38acb 222: onsuccess: #1843: 1: Success after binutils/gcc: 17 commits new 02a1aad2c7 223: onsuccess: #1844: 1: Success after gcc: 7 commits new b03de6a58d 224: onsuccess: #1845: 1: Success after binutils/gcc: 9 commits new 2fb217f6b7 225: onsuccess: #1846: 1: Success after binutils/gcc: 18 commits new d69b86ad1c 226: onsuccess: #1847: 1: Success after binutils/gcc: 8 commits new 9b14e967e2 227: onsuccess: #1848: 1: Success after binutils/gcc: 4 commits new ebb472b6e6 228: onsuccess: #1849: 1: Success after binutils/gcc: 3 commits new ab14e9680c 229: onsuccess: #1850: 1: Success after basepoints/gcc-13-34 [...] new 23b98ad352 230: onsuccess: #1851: 1: Success after basepoints/gcc-13-34 [...] new 58d24a5a0f 231: onsuccess: #1852: 1: Success after binutils/gcc: 4 commits new a7defb2b24 232: onsuccess: #1853: 1: Success after binutils: 3 commits new 955896fac8 233: onsuccess: #1854: 1: Success after binutils/gcc: 6 commits new 7914ddc55b 234: onsuccess: #1855: 1: Success after binutils/gcc: 7 commits new ba9308f0d0 235: onsuccess: #1856: 1: Success after binutils/gcc: 18 commits new d64111d3e7 236: onsuccess: #1857: 1: Success after binutils/gcc: 10 commits new 4799e5d98f 237: onsuccess: #1858: 1: Success after binutils/gcc: 6 commits new d03f661f83 238: onsuccess: #1859: 1: Success after binutils/gcc: 14 commits new 5040a13d9e 239: onsuccess: #1860: 1: Success after binutils/gcc: 9 commits new 808f8a6e5a 240: onsuccess: #1861: 1: Success after gcc: 6 commits new eb5cc87531 241: onsuccess: #1862: 1: Success after binutils/gcc: 5 commits new bcdecf01c5 242: onsuccess: #1863: 1: Success after binutils/gcc: 17 commits new f40b61aba1 243: onsuccess: #1864: 1: Success after binutils/gcc: 6 commits new 4d3dca0034 244: onsuccess: #1865: 1: Success after gcc: 6 commits new a782726272 245: onsuccess: #1866: 1: Success after binutils/gcc: 8 commits new 8560d7d92c 246: onsuccess: #1867: 1: Success after binutils/gcc: 8 commits new 3f6934db71 247: onsuccess: #1868: 1: Success after binutils/gcc: 7 commits new 825d86033a 248: onsuccess: #1869: 1: Success after gcc: 4 commits new 00950ff36d 249: onsuccess: #1870: 1: Success after binutils/gcc: 9 commits new 5eef1ad688 250: onsuccess: #1871: 1: Success after binutils/gcc: 11 commits new 1f6fc6ba2e 251: onsuccess: #1872: 1: Success after binutils/gcc: 10 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (38280d55a8) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (1f [...] 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 1668 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 51248 -> 50872 bytes 04-build_abe-gcc/console.log.xz | Bin 233636 -> 233452 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3832 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2976 -> 2588 bytes 07-check_regression/console.log.xz | Bin 6536 -> 5440 bytes 07-check_regression/mail-body.txt | 44 - 07-check_regression/results.compare | 31 +- 07-check_regression/results.compare2 | 450 +--- 08-update_baseline/console.log | 44 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 46 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 2792464 -> 2839564 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 2404544 -> 2395188 bytes sumfiles/gcc.sum | 4483 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 915612 -> 922448 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2172 -> 2172 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 206508 -> 206740 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2536 -> 2536 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 468956 -> 469960 bytes sumfiles/libstdc++.sum | 14 +- 32 files changed, 2541 insertions(+), 2811 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_build/master-arm updated (91e72b8d2e -> 218812679c)

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_build/master-arm in repository toolchain/ci/base-artifacts. from 91e72b8d2e 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] new 218812679c 91: onsuccess: #495: 6: 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 1668 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 50368 -> 52304 bytes 05-build_abe-gcc/console.log.xz | Bin 233836 -> 233968 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 9240 -> 8428 bytes 08-build_abe-glibc/console.log.xz | Bin 234256 -> 234744 bytes 09-build_abe-gdb/console.log.xz | Bin 50312 -> 50688 bytes 10-check_regression/console.log.xz | Bin 4584 -> 4560 bytes 11-update_baseline/console.log | 9 +++++++++ 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 | 36 +++++++++++++++++------------------ 20 files changed, 36 insertions(+), 27 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 October 2022