Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (04cf66f630 -> 1608fb57ac)

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 04cf66f630 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards e4111fd4df 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards 5bd0c89d06 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 76f0244a54 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards 83e2675725 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards eeba06a990 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards 0d48932481 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards f769cb571c 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards 03c007e8c0 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards 6a556a6397 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards adda31b975 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards b8f950296b 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards d2668218c9 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards b1691bef6b 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 240fe41463 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards be37d4f2f7 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 77526a2a77 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 920f6b6462 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards df18cf54ce 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 907b2901f8 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 7bfd1aec26 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards 8af8ce8fc4 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 232f8a53de 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards b86124e24d 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards 3850b68b98 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards f42976e3f9 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards 4183af5a47 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards c8e8792ee2 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards cbbefc49d2 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards fbaac69648 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards eea477c51e 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards 0f7bef7f8d 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards e7d862ec88 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards ef94e36126 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards dafab6f28b 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards cde6b02889 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards c22e79386e 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards a669118997 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards b82f2774c8 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards f7758290ab 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards c9b135c2d2 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards bcc05c8e54 102: force: #1551: 1: Failure after gcc: 306 commits discards a1868f1cfd 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards ce22105627 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards b30f9386cd 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 153f0d569b 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards f301972b8a 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 258b6e44ca 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards dff69d58da 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards c7705e11c9 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 441189964e 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 46318791ce 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 001122f392 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 3cbf850e5e 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 8b1787ce36 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards b252a3027f 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 753e3ca1bb 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards b6860d56a4 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 920198b0e5 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 7b423f56ec 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 707c2e4a81 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 27218916af 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards a7a7847525 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 43cc483e3b 80: onsuccess: 7: Successful build after linux: 44 commits discards f9a89750cd 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 8dd6fb5a06 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards 561aa06804 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d117eda6fe 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards ae293087af 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards db9212e553 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 0da412b9d9 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards eb53f88481 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 86588bde81 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 6e04898d0c 70: onsuccess: 7: Successful build after gcc: 4 commits discards 033b665c55 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c06a83b5d0 68: onsuccess: 7: Successful build after linux: 6 commits discards 17484cb063 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards d5506bfd66 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards 72e90f17de 65: onsuccess: 7: Successful build after binutils: 3 commits discards 5e55b2f164 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 1437da5d6a 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards bd9390c256 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 18479aaf38 61: onsuccess: 4: Successful build after gcc: 5 commits discards e918e3548e 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 6a974ec635 59: force: 7: Successful build after gcc: 3 commits discards 46b3b82de4 58: onsuccess: 7: Successful build after glibc: 2 commits discards d572d3db2b 57: onsuccess: 7: Successful build after gcc: 7 commits discards bb7ad47d01 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9a378b5d85 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c376ecb459 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards ccbe58c386 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 97a428db00 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] discards e07d56432f 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 6fcb06a5bc 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 786a16a089 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 3d10625f40 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 60d8aaeb07 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b815d2f547 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 371747810f 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 98f3d82a28 44: onsuccess: 7: Successful build after linux: 34 commits discards 955479f945 43: onsuccess: 7: Successful build after gcc: 2 commits new 10afca84d8 43: onsuccess: 7: Successful build after gcc: 2 commits new 3cc7d88334 44: onsuccess: 7: Successful build after linux: 34 commits new 69a7f80a3c 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a296b10e5b 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new c3161ec54c 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7c1b8dd748 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 47f1257626 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 5be8be9670 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new bdb7de9528 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new d9f1dc8164 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new b734e0af4e 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 3e5e413ab1 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 5c3017c3ea 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 80142a75d2 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d3dda06e55 57: onsuccess: 7: Successful build after gcc: 7 commits new 14d03ece5f 58: onsuccess: 7: Successful build after glibc: 2 commits new 11f227a670 59: force: 7: Successful build after gcc: 3 commits new f3a0adbb9f 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 4c55885145 61: onsuccess: 4: Successful build after gcc: 5 commits new 26aab64ddb 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new f9b8ec8227 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new e2021d0319 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new a90ed9a9a9 65: onsuccess: 7: Successful build after binutils: 3 commits new e1fae8d8df 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 30d41f8878 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new 5c2e90038e 68: onsuccess: 7: Successful build after linux: 6 commits new d51846f44c 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7a5b5e7ab3 70: onsuccess: 7: Successful build after gcc: 4 commits new 26e0a19bd5 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new c8dc40ff62 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 306a952b5f 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b1b3e267f6 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 94217c442d 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 0e0e237234 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 1eb4c378ab 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d44d959349 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new 7d60429efa 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 21f3ddefe2 80: onsuccess: 7: Successful build after linux: 44 commits new e2d1de9ace 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 582d40ad1c 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 9217f494e9 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 67c485e519 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 130307f612 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new a3bd21fbe3 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 7f4b69f097 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 7a71dd83ed 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 506e496c5e 89: onsuccess: 7: Success after gcc/glibc: 8 commits new f9fd814ab3 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new ca474b655a 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new c4b39892c1 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 4a8e9f05c8 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 7fc467c9bb 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new c3ce5fd723 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new d135ea501e 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 4235756c93 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 0b9dd6b174 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 2ac0c58945 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 6e9548f9e1 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new c13360c68b 101: onsuccess: #1547: 7: Success after binutils: 82 commits new cefe1a691a 102: force: #1551: 1: Failure after gcc: 306 commits new 595a263522 103: onsuccess: #1552: 1: Success after gcc: 5 commits new a077d5a6ad 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 63601c2254 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 80eba1bdec 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 91c5e1659a 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new ba4c46b155 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new 1070d964fd 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 7b64d923f6 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 73fa349dc0 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new e62132ff72 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new e70ae3ce9a 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new 2ead423aec 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 016ddfb593 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 9f36d754ae 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 5ee6fc3ca8 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 5814124d80 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new 94ae4fe79b 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new 41267028a9 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 2114849a56 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new ab53b54ba2 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new fa2c81136e 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new ab207b91d8 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 114b1294d9 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new ed775bfba5 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new a0904b0c8b 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new 6fbc39707a 128: onsuccess: #1579: 7: Success after linux: 12 commits new c20ff71e7d 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new 28c197beb1 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 276193ae86 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new 657bee8521 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 2ce318254f 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new 61c42f75a2 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new 4e640a60d5 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new 660c7d4063 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new 77a62676b8 137: onsuccess: #1588: 7: Success after gcc: 5 commits new b35bc69880 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new 6c1fe8d597 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 677bcf0a43 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new 0b83a73933 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new 5eb202c8b7 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new a392e8e189 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new 1608fb57ac 144: onsuccess: #1595: 7: Success after glibc: 2 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 (04cf66f630) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1684 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 30176 -> 30208 bytes 05-build_abe-stage1/console.log.xz | Bin 72180 -> 72192 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 8708 -> 8732 bytes 08-build_abe-glibc/console.log.xz | Bin 239652 -> 239840 bytes 09-build_abe-stage2/console.log.xz | Bin 202160 -> 202672 bytes 10-build_abe-gdb/console.log.xz | Bin 37564 -> 37300 bytes 11-build_abe-qemu/console.log.xz | Bin 31232 -> 31544 bytes 12-check_regression/console.log.xz | Bin 4456 -> 3328 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 ++++++------- 18 files changed, 50 insertions(+), 50 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/master-arm-check_bootstrap updated (54ebc287c7 -> d191fda7c1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check_bootstrap/master-arm-check_bootstrap in repository toolchain/ci/base-artifacts. from 54ebc287c7 46: onsuccess: #558: 1: Success after binutils: 7 commits new d191fda7c1 47: onsuccess: #561: 1: Success after binutils: 9 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 1656 -> 1652 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 52412 -> 51820 bytes 04-build_abe-bootstrap/console.log.xz | Bin 465156 -> 462196 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3808 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2620 -> 2612 bytes 07-check_regression/console.log.xz | Bin 4444 -> 4440 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 6 +- 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 | 14 +- sumfiles/g++.log.xz | Bin 2869920 -> 2858912 bytes sumfiles/g++.sum | 130 +- sumfiles/gcc.log.xz | Bin 2462108 -> 2479936 bytes sumfiles/gcc.sum | 4740 +++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 944680 -> 948792 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2316 -> 2308 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 210972 -> 211992 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2728 -> 2728 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 475496 -> 476580 bytes sumfiles/libstdc++.sum | 10 +- 29 files changed, 2497 insertions(+), 2497 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (9e79a25b66c -> f758d447d7f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 9e79a25b66c Daily bump. new f758d447d7f Check nonlinear iv in vect_can_advance_ivs_p. 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: gcc/testsuite/gcc.target/i386/pr107055.c | 4 ++ gcc/tree-vect-loop-manip.cc | 10 ++++ gcc/tree-vect-loop.cc | 82 ++++++++++++++++++-------------- gcc/tree-vectorizer.h | 3 ++ 4 files changed, 64 insertions(+), 35 deletions(-) create mode 100644 gcc/testsuite/gcc.target/i386/pr107055.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_debug updated (62671f3746 -> 420c5d8ff2)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_debug in repository toolchain/ci/base-artifacts. from 62671f3746 52: onsuccess: #441: 1: Success after gcc: 5 commits new 420c5d8ff2 53: onsuccess: #442: 1: Success after binutils/gcc: 47 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 -> 1916 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 38692 -> 38080 bytes 05-build_abe-bootstrap_debug/console.log.xz | Bin 79716 -> 79648 bytes 06-check_regression/console.log.xz | Bin 2692 -> 3072 bytes 06-check_regression/mail-body.txt | 11 ----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 13 +------------ mail/mail-subject.txt | 2 +- manifest.sh | 19 ++++++++++--------- 13 files changed, 16 insertions(+), 37 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 updated (a01c49f503 -> 643c47daec)

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-aarch64 in repository toolchain/ci/base-artifacts. from a01c49f503 45: onsuccess: #815: 1: Success after binutils: 6 commits new 643c47daec 46: onsuccess: #818: 1: Success after binutils: 10 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 1644 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 37712 -> 37180 bytes 04-build_abe-gcc/console.log.xz | Bin 212220 -> 211260 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8784 -> 8776 bytes 07-build_abe-glibc/console.log.xz | Bin 239896 -> 239156 bytes 08-build_abe-gdb/console.log.xz | Bin 37500 -> 37180 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3816 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2044 -> 2028 bytes 11-check_regression/console.log.xz | Bin 8340 -> 13980 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 19 +- 11-check_regression/mail-body.txt | 149 +- 11-check_regression/results.compare | 53 +- 11-check_regression/results.compare2 | 5429 +++++++++++++++----- 11-check_regression/results.regressions | 53 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 151 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 53 +- sumfiles/gdb.log.xz | Bin 1889084 -> 1881556 bytes sumfiles/gdb.sum | 8525 +++++++++++++++++++++++-------- 26 files changed, 10808 insertions(+), 3654 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-arm updated (f7bd2d9044 -> f54c7cb363)

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 f7bd2d9044 140: onsuccess: #1756: 1: Success after binutils: 3 commits discards fb76f01eda 139: onsuccess: #1753: 1: Success after binutils: 5 commits discards d052aa7166 138: onsuccess: #1749: 1: Success after binutils: 5 commits discards 4407cd435d 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] discards cb3005621b 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] discards e9581713eb 135: onsuccess: #1739: 1: Success after binutils: 4 commits discards 9065ee7b66 134: onsuccess: #1736: 1: Success after binutils: 3 commits discards 3da6274059 133: onsuccess: #1733: 1: Success after binutils: 3 commits discards 6da4cd54bd 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits discards eda726212a 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits discards fdca23c1d2 130: onsuccess: #1729: 1: Success after gcc: 9 commits discards a10612b685 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] discards df089e9c26 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits discards dfa74a8fdf 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] discards cacb222063 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits discards 111a43b73a 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits discards 366566505a 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits discards 2f07a6d99d 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits discards af04da817c 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits discards e9f413de34 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits discards 14ff4bf4a1 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits discards 62541d5814 119: onsuccess: #1715: 1: Success after binutils: 4 commits discards 270048efda 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits discards 8f5d151aa0 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits discards ddfe4bbb21 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits discards ae925e1be6 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits discards d5527ef659 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits discards 70d4a2642b 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards e4f782f0a9 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards cb5ec5900e 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards cef0a52f71 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards 321d5efa2e 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] discards 876740d3a7 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards 672f3e47c5 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] discards 3bf5084c6c 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards cd6fc18111 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards 794ff2ef98 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards 2bc398ba96 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits discards aac1b4e0f8 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits discards d102aa92e6 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits discards a24064d640 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] discards d7475d7906 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits discards f614089323 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits discards a6b4f9a26d 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits discards 973e1f889e 96: onsuccess: #1654: 1: Success after gcc: 5 commits discards ceeef40b9c 95: onsuccess: #1653: 1: Success after gcc: 13 commits discards d0cb4bfaa4 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits discards 257956dd30 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] discards 441acd5403 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits discards 1f552c9d20 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] discards 39557ba143 90: onsuccess: #1645: 1: Success after gcc: 2 commits discards 75e044c42e 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] discards bcf46ac78e 88: onsuccess: 1: Success after binutils/gcc: 2 commits discards 9ea614c8ce 87: onsuccess: 1: Success after gcc: 6 commits discards 7228d4aa15 86: onsuccess: 1: Success after binutils/gcc: 8 commits discards 31b6776ffe 85: onsuccess: 1: Success after binutils/gcc: 19 commits discards b61bf47d8b 84: onsuccess: 1: Success after binutils/gcc: 2 commits discards 1d3b5ae56d 83: onsuccess: 1: Success after gcc: 14 commits discards 6ba1e06418 82: onsuccess: 1: Success after binutils/gcc: 9 commits discards 7d040fc6b7 81: onsuccess: 1: Success after binutils/gcc: 8 commits discards e43b0bda35 80: onsuccess: 1: Success after binutils/gcc: 8 commits discards 9ba5dee1fb 79: onsuccess: 1: Success after binutils/gcc: 23 commits discards 446bc6c38a 78: onsuccess: 1: Success after binutils/gcc: 17 commits discards 2844ce8981 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards eeed2155cf 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards e031a5a6f3 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards ff4c4441f9 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits discards 5b9a97601d 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 7fc0ad277b 72: onsuccess: 1: Successful build after baseline build: no [...] discards c96fee6f2f 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards 2b17da3a28 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 5308707f79 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] discards d59f082c46 68: onsuccess: 1: Successful build after gcc: 2 commits discards f81d015407 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 188a7a91c0 66: onsuccess: 1: Successful build after gcc: 4 commits discards a55b5b9f76 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards ec6f649db1 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 76e32c5f7a 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards fc5d9908e8 62: onsuccess: 1: Successful build after gcc: 4 commits discards 9ec27e6941 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 09ede4cf39 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards b1c9362816 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits discards 65bdf8bf93 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] discards feb94a2f9d 57: onsuccess: 1: Successful build after binutils: 2 commits discards 0b6bca7364 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards a3422a3d5d 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards ebc3634450 54: onsuccess: 1: Successful build after gcc: 5 commits discards b7dc195964 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 0c528d61dc 52: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 9699374c8b 51: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards a92459082e 50: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards c9b1dd1a28 49: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 3cdfd5b997 48: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 9ce982e288 47: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards c8dd76dc48 46: onsuccess: 1: Successful build after baseline build: no [...] discards a1f7f3b673 45: onsuccess: 1: Successful build after binutils: Fix crash [...] discards c48e96ab5a 44: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 8de8c89b98 43: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards eca22ef515 42: onsuccess: 1: Successful build after baseline build: no [...] discards f4a18ce503 41: onsuccess: 1: Successful build after gcc: 2 commits discards 2d3345f434 40: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 2e71ffcb56 40: onsuccess: 1: Successful build after binutils/gcc: 2 commits new d6a887d45b 41: onsuccess: 1: Successful build after gcc: 2 commits new 41c1b92887 42: onsuccess: 1: Successful build after baseline build: no [...] new c07384688f 43: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 81662154cd 44: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 0023dd7e07 45: onsuccess: 1: Successful build after binutils: Fix crash [...] new 1be42d3808 46: onsuccess: 1: Successful build after baseline build: no [...] new 3a1d314379 47: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 619078d8c0 48: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 3366fe4fb6 49: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 2f04067277 50: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 64944d04d5 51: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 5873659de2 52: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 7539a8e78c 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 475141e24a 54: onsuccess: 1: Successful build after gcc: 5 commits new ba7637dfe6 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 58fbd34ad3 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits new a9647b361e 57: onsuccess: 1: Successful build after binutils: 2 commits new c8bdafd59a 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] new 442d6e1f13 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits new 10899d5418 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits new 376ce83e7f 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits new d02f37188f 62: onsuccess: 1: Successful build after gcc: 4 commits new f7393692f8 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits new dd4177e265 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits new ecd04fb952 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits new de28ad4543 66: onsuccess: 1: Successful build after gcc: 4 commits new 5df34ea186 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 245c6d3cad 68: onsuccess: 1: Successful build after gcc: 2 commits new 1997e781a7 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] new ec3756ed97 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits new ec5a2885b5 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 1677e7d6ab 72: onsuccess: 1: Successful build after baseline build: no [...] new 7716f77cca 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 05e883b34b 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits new 78b28abb12 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits new cb6976bbf6 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 35d81fedfd 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits new d75d4efd4b 78: onsuccess: 1: Success after binutils/gcc: 17 commits new 43fdb49c0c 79: onsuccess: 1: Success after binutils/gcc: 23 commits new ca9db2fa07 80: onsuccess: 1: Success after binutils/gcc: 8 commits new 1a0471bc4c 81: onsuccess: 1: Success after binutils/gcc: 8 commits new ea4dda354b 82: onsuccess: 1: Success after binutils/gcc: 9 commits new 463fdfeb42 83: onsuccess: 1: Success after gcc: 14 commits new 7d56372cf6 84: onsuccess: 1: Success after binutils/gcc: 2 commits new 9d00f7b2ff 85: onsuccess: 1: Success after binutils/gcc: 19 commits new f21af752a2 86: onsuccess: 1: Success after binutils/gcc: 8 commits new f22bce5fd7 87: onsuccess: 1: Success after gcc: 6 commits new afce736826 88: onsuccess: 1: Success after binutils/gcc: 2 commits new ecd4d43393 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] new 0c2d2f747c 90: onsuccess: #1645: 1: Success after gcc: 2 commits new b837cb6534 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] new ce0c718fb3 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits new a2c6717df9 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] new 9d0b67f3d6 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits new 81ea5b9a42 95: onsuccess: #1653: 1: Success after gcc: 13 commits new d4eee57bc2 96: onsuccess: #1654: 1: Success after gcc: 5 commits new 57921f722a 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits new ed72b92ebd 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits new 49fccfbe4c 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits new f00aac9b5a 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] new 4f230f4a02 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits new 7f9ee7162a 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits new 671a749c9e 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new cd8588219b 104: onsuccess: #1700: 1: Success after gcc: 2 commits new 5b87865a2d 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new 87589da6ad 106: onsuccess: #1702: 1: Success after gcc: 4 commits new 848e6343ca 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] new 760db2f2f2 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new 2ae0763525 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] new 24c4ea04c4 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new 29c87207c8 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new df2dbef9d5 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new 2813d392da 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new 2db0677713 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits new fc1f5e5275 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits new de1ba84e9f 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits new c2aba49cff 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits new 80f08a2960 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits new a7114ff695 119: onsuccess: #1715: 1: Success after binutils: 4 commits new a06bebd744 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits new 5fa37c082d 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits new 4147a3d787 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits new 2d04ff18be 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits new 9443396750 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits new a67cccc57b 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits new 871b300b75 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits new a7b46960c7 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] new b137e17374 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits new 539aebb5ad 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] new 2d9ca3f7b7 130: onsuccess: #1729: 1: Success after gcc: 9 commits new 058cd198eb 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits new f461f01efa 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits new de82b4e5fa 133: onsuccess: #1733: 1: Success after binutils: 3 commits new 89dc150bcd 134: onsuccess: #1736: 1: Success after binutils: 3 commits new 15d2443f8a 135: onsuccess: #1739: 1: Success after binutils: 4 commits new 62268e7cb7 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] new 31bce6b7cf 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] new a8cd455eae 138: onsuccess: #1749: 1: Success after binutils: 5 commits new ebc21495bf 139: onsuccess: #1753: 1: Success after binutils: 5 commits new 7249e8e41f 140: onsuccess: #1756: 1: Success after binutils: 3 commits new f54c7cb363 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] 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 (f7bd2d9044) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (f5 [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1680 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 51440 -> 50732 bytes 04-build_abe-gcc/console.log.xz | Bin 231460 -> 232016 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3788 -> 3872 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2620 -> 2632 bytes 07-check_regression/console.log.xz | Bin 4320 -> 4288 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 6 +- 08-update_baseline/console.log | 58 +- 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 | 12 +- sumfiles/g++.log.xz | Bin 2787716 -> 2778992 bytes sumfiles/g++.sum | 142 +- sumfiles/gcc.log.xz | Bin 2405276 -> 2393112 bytes sumfiles/gcc.sum | 4232 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 910080 -> 910164 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2172 -> 2172 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 204292 -> 204500 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2532 -> 2532 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 466632 -> 466736 bytes sumfiles/libstdc++.sum | 10 +- 30 files changed, 2277 insertions(+), 2277 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (38de7d267d -> 10d1816627)

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_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 38de7d267d 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards ef04a833e2 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 16d8cb0893 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 02ab90f984 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards f66f703013 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards d98470100a 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards e994945042 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 71780998a5 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 15663f57a3 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 5914263c85 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards c755390aca 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards f387cc5e22 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 5496d26224 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 5d3bd713c8 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 8b497a51a1 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards bea9075d3d 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 1a41eda35c 124: onsuccess: #2159: 1: Success after linux: 23 commits discards b0dc7745e7 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 40eabdac44 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 77da1d8ef2 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 681430a012 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 369aaacf42 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 2ae849728b 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 68d151ede0 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards eebf3a15d2 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards a791da04a7 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards f63bf6fa30 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 948d67d832 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards a1abfd262e 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards b3f3dc80c3 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards a85bd70783 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 61747f198d 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards a1ded338ed 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 5a384ba38f 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 729ae34657 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards e467b646e6 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 90c01e991e 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 23963eaf1e 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 874dc0548b 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards e0595bfa3c 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 77b735b487 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards d925d54a5e 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 6ed44424cb 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 1d22d50b8e 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 9285437987 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards ea79fbfbf7 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 9714a6dfe8 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards e330b75c5c 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards ea9bb0408b 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 4268844807 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards e4e8562a2b 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards dc3fb38bb4 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 32a36ecfc1 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards a761bd2f6f 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 02e4c0d484 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 32ded68430 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 803f2abc1d 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 08e6639e86 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards a7d88a121a 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 2c08910c30 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 21bb330c66 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 530cd80ab0 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2fc5d08cd3 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards fcc1397e64 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards cf8ac6c680 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1f21ff6400 75: onsuccess: 1: Successful build after linux: 44 commits discards 51004375a5 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards fd8bc62491 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c9d3df4831 72: onsuccess: 1: Successful build after linux: 12 commits discards 3e6edad1a5 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 1c28025b57 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards c12825aeee 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards fb46729c20 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 16dd72db71 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards d4bd4d0a38 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards c5c760165e 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c4213c0bbd 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c41823c9a2 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 1bdbc100b2 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 4f8e12d3e4 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 5ab6ba0eff 60: onsuccess: 1: Successful build after glibc: 2 commits discards 5c924c1d0b 59: onsuccess: 1: Successful build after binutils: 2 commits discards d79d219a21 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 791333ccd0 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7869c77db1 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4855714ea8 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 9efef54265 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 7df6cf9065 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 3c4b46e809 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 3e4e269439 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3e0454c730 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 9ed95e11cc 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 806703b2fb 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d28b31de0f 47: onsuccess: 1: Successful build after linux: 10 commits discards d0ff91acf2 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 6a1512cd37 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2b14ca160d 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 9bf447e4fd 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 8479a8c218 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards d416f636e8 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e0f4372173 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new d9a130033d 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new a167d8c1f8 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7b76e5991b 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new e512667d39 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 6f0f5a21d0 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 64becad8be 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7e04321469 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 3f6c2c991a 47: onsuccess: 1: Successful build after linux: 10 commits new 8d300b6f15 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a03befecb3 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new cf4acf9bab 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 02e393cc1e 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c54588ad85 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 9ed32bc9a0 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 2c000c4bcf 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 2b00d9a9f9 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new de844407a2 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 17fe9d2c9f 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c345d91720 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new b5e9fddb2a 59: onsuccess: 1: Successful build after binutils: 2 commits new b40262ff7b 60: onsuccess: 1: Successful build after glibc: 2 commits new 75e51acb66 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 4903446c15 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 8a23a3c045 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 33a218cdc4 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 24dd4c9489 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3b493e8a8c 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 10f70c3ff7 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new f75bb89acc 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1432166b35 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new b0aa1895b1 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 4710148579 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 3fa226fffb 72: onsuccess: 1: Successful build after linux: 12 commits new 1706192c3e 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 16ce320760 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new c3816fe2ce 75: onsuccess: 1: Successful build after linux: 44 commits new cfe5d3cef6 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 146f426708 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 51ffadaa3f 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new e04fee8247 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4e8aa1faaa 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new bc0eb001f6 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 3d54447f71 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 0f2552c4b5 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 4738742b2f 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 801faa2123 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 210a239a63 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 3e07639222 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new ede016ed43 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 31c0be90b3 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new cc87a1acd4 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 76e69a80cd 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 66f87caf4a 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new f2ee325ccf 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new cc8d276911 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new bf15ca1202 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 36b1e24bf9 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new fca3856a80 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 078a5f6d28 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 3f2deb50b2 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new b32549dd2e 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new df331d3b08 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 141f727347 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new ed1d09cdf1 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new ef378a55ce 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new f1cfe38791 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new a1176844f0 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 1467f7f69c 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 6b7dadc842 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 8b506db7e7 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new f722ec8a3c 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 9701187827 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new edeeecdac8 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 8ed571f30b 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 0b064598b2 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 1fd0ab8298 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 054927852c 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 704e6cf58f 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new b677870f8c 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new a8c4f499ae 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 6849480045 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 23ee3af466 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 5784221756 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 3b42233454 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new e0171c1113 124: onsuccess: #2159: 1: Success after linux: 23 commits new 31ac2d584a 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 7211a661a1 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new e3b8a3ff39 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 2098c90a09 128: onsuccess: #2163: 1: Success after linux: 23 commits new ed4be7e2f8 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 15d3b375f5 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new d47a8cb388 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 4832b9f0e7 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 7478abb5ec 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 307475a6cb 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 67d81f7394 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 7e86d3dbf0 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new a2f21db290 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 17ccc7b3dc 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 2e54f72a69 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 11da134dd0 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 10d1816627 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 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 (38de7d267d) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] 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 1748 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 31696 -> 30228 bytes 04-build_abe-stage1/console.log.xz | Bin 73648 -> 72388 bytes 06-build_abe-linux/console.log.xz | Bin 8712 -> 8728 bytes 07-build_abe-glibc/console.log.xz | Bin 240720 -> 240676 bytes 08-build_abe-stage2/console.log.xz | Bin 203236 -> 202640 bytes 09-build_abe-gdb/console.log.xz | Bin 38264 -> 37460 bytes 10-build_abe-qemu/console.log.xz | Bin 31184 -> 31180 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2916 -> 2460 bytes 13-check_regression/console.log.xz | Bin 6912 -> 5872 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 76 +- 14-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 | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.xz | Bin 3409060 -> 3410432 bytes sumfiles/g++.sum | 66 +- sumfiles/gcc.log.xz | Bin 3033704 -> 3035140 bytes sumfiles/gcc.sum | 3670 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1031216 -> 1028168 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201944 -> 202040 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 417924 -> 421128 bytes sumfiles/libstdc++.sum | 30 +- 38 files changed, 2007 insertions(+), 2041 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_O1 updated (a535c250d4 -> 046a02646c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_O1 in repository toolchain/ci/base-artifacts. from a535c250d4 48: onsuccess: #440: 1: Success after binutils/gcc: 29 commits new 046a02646c 49: onsuccess: #441: 1: Success after binutils/gcc: 24 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 1680 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2704 bytes 04-build_abe-binutils/console.log.xz | Bin 50808 -> 50692 bytes 05-build_abe-bootstrap_O1/console.log.xz | Bin 111664 -> 111424 bytes 06-check_regression/console.log.xz | Bin 3068 -> 3080 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 12 files changed, 15 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_llvm_apm/llvm-master-aarch64-cpu2017-O3_VECT updated (7732b89203 -> c1622d5ef9)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_llvm_apm/llvm-master-aarch64-cpu2017-O3_VECT in repository toolchain/ci/base-artifacts. from 7732b89203 0: init: #2: 1: [TCWG CI] No change after baseline build: no [...] new c1622d5ef9 1: onsuccess: #4: 1: [TCWG CI] No change after binutils/gcc/ [...] 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 2264 -> 1736 bytes 01-reset_artifacts/patch-env.sh | 2 - 02-prepare_abe/console.log.xz | Bin 2736 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30932 -> 31044 bytes 04-build_abe-stage1/console.log.xz | Bin 74868 -> 72224 bytes 06-build_abe-linux/console.log.xz | Bin 8596 -> 8640 bytes 07-build_abe-glibc/console.log.xz | Bin 241556 -> 238664 bytes 08-build_abe-stage2/console.log.xz | Bin 182976 -> 176236 bytes 09-build_llvm-true/console.log.xz | Bin 63152 -> 63644 bytes 10-benchmark/benchmark-build.log | 98 +- 10-benchmark/benchmark.log | 96 +- 10-benchmark/console.log.xz | Bin 3756 -> 3780 bytes 11-check_regression/console.log.xz | Bin 6160 -> 8740 bytes 11-check_regression/csv-results-0/md5sum.csv | 706 +- 11-check_regression/csv-results-0/results.csv | 253206 ++++++++--------- 11-check_regression/csv-results-0/size.csv | 253762 ++++++++--------- 11-check_regression/csv-results-0/vect.csv | 21878 +- 11-check_regression/csv-results-1/md5sum.csv | 1255 +- 11-check_regression/csv-results-1/perf.csv | 1426 +- 11-check_regression/csv-results-1/results.csv | 253439 +++++++++-------- 11-check_regression/csv-results-1/size.csv | 253764 +++++++++--------- 11-check_regression/csv-results-1/vect.csv | 21878 +- 11-check_regression/results-brief.csv | 28 +- 11-check_regression/results-compare.csv | 2 +- 11-check_regression/results-full.csv | 1469 +- 11-check_regression/results-internal.csv | 79 +- 11-check_regression/results.csv | 79 +- 11-check_regression/results.log | 378 +- 12-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- .../squad/600.perlbench_s/results-metadata.json | 18 +- .../squad/600.perlbench_s/results-metrics.json | 4 +- dashboard/squad/602.gcc_s/results-metadata.json | 18 +- dashboard/squad/602.gcc_s/results-metrics.json | 4 +- dashboard/squad/605.mcf_s/results-metadata.json | 18 +- dashboard/squad/605.mcf_s/results-metrics.json | 2 +- dashboard/squad/619.lbm_s/results-metadata.json | 18 +- dashboard/squad/619.lbm_s/results-metrics.json | 2 +- .../squad/620.omnetpp_s/results-metadata.json | 18 +- dashboard/squad/620.omnetpp_s/results-metrics.json | 4 +- .../squad/623.xalancbmk_s/results-metadata.json | 18 +- .../squad/623.xalancbmk_s/results-metrics.json | 4 +- dashboard/squad/625.x264_s/results-metadata.json | 18 +- dashboard/squad/625.x264_s/results-metrics.json | 4 +- .../squad/631.deepsjeng_s/results-metadata.json | 18 +- .../squad/631.deepsjeng_s/results-metrics.json | 4 +- .../squad/638.imagick_s/results-metadata.json | 18 +- dashboard/squad/638.imagick_s/results-metrics.json | 4 +- dashboard/squad/641.leela_s/results-metadata.json | 18 +- dashboard/squad/641.leela_s/results-metrics.json | 2 +- dashboard/squad/644.nab_s/results-metadata.json | 18 +- dashboard/squad/644.nab_s/results-metrics.json | 4 +- dashboard/squad/Mean/results-functional.json | 4 - dashboard/squad/Mean/results-metadata.json | 13 - dashboard/squad/Mean/results-metrics.json | 5 - dashboard/squad/dashboard-push-squad.sh | 53 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 30 +- mail/mail-body.txt | 30 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results_id | 2 +- 66 files changed, 531994 insertions(+), 531982 deletions(-) delete mode 100644 01-reset_artifacts/patch-env.sh delete mode 100644 dashboard/squad/Mean/results-functional.json delete mode 100644 dashboard/squad/Mean/results-metadata.json delete mode 100644 dashboard/squad/Mean/results-metrics.json -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/master-arm-check_bootstrap_lto updated (443fa40653 -> a96ca07908)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check_bootstrap/master-arm-check_bootstrap_lto in repository toolchain/ci/base-artifacts. from 443fa40653 48: onsuccess: #471: 1: Success after binutils: 8 commits new a96ca07908 49: onsuccess: #474: 1: Success after binutils: 10 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 1644 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 50420 -> 50336 bytes 04-build_abe-bootstrap_lto/console.log.xz | Bin 474268 -> 471704 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3812 bytes 06-build_abe-check_bootstrap_lto/console.log.xz | Bin 2432 -> 2428 bytes 07-check_regression/console.log.xz | Bin 4476 -> 4476 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 6 +- 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 | 14 +- sumfiles/g++.log.xz | Bin 2864876 -> 2830608 bytes sumfiles/g++.sum | 118 +- sumfiles/gcc.log.xz | Bin 2480232 -> 2529032 bytes sumfiles/gcc.sum | 5422 +++++++++++------------ sumfiles/gfortran.log.xz | Bin 953832 -> 941872 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2316 -> 2308 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 211232 -> 212084 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2724 -> 2724 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 476372 -> 478444 bytes sumfiles/libstdc++.sum | 10 +- 29 files changed, 2832 insertions(+), 2832 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022