Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (cd350c6106 -> 023a1f39d1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. from cd350c6106 49: onsuccess: #562: 1: Success after binutils: 9 commits new 023a1f39d1 50: onsuccess: #564: 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 1620 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 37772 -> 37784 bytes 04-build_abe-gcc/console.log.xz | Bin 211616 -> 211976 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8408 -> 8348 bytes 07-build_abe-glibc/console.log.xz | Bin 239092 -> 239424 bytes 08-build_abe-gdb/console.log.xz | Bin 37444 -> 37168 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3828 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2144 -> 2128 bytes 11-check_regression/console.log.xz | Bin 4700 -> 6272 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +-- sumfiles/binutils.log.xz | Bin 58532 -> 58528 bytes sumfiles/binutils.sum | 60 ++--- sumfiles/gas.log.xz | Bin 81132 -> 81112 bytes sumfiles/gas.sum | 268 +++++++++++----------- sumfiles/ld.log.xz | Bin 121236 -> 121224 bytes sumfiles/ld.sum | 342 ++++++++++++++--------------- 29 files changed, 371 insertions(+), 367 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/master-aarch64-check_bootstrap updated (40fbc4791a -> 806523dde6)

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-aarch64-check_bootstrap in repository toolchain/ci/base-artifacts. from 40fbc4791a 48: onsuccess: #582: 1: Success after binutils: 9 commits new 806523dde6 49: onsuccess: #584: 1: Success after binutils/gcc: 148 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1736 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 37768 -> 38036 bytes 04-build_abe-bootstrap/console.log.xz | Bin 267764 -> 268036 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3816 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2644 -> 2728 bytes 07-check_regression/console.log.xz | Bin 5344 -> 14068 bytes 07-check_regression/extra-bisect-params | 1 + 07-check_regression/fails.sum | 19 + 07-check_regression/mail-body.txt | 118 +- 07-check_regression/results.compare | 615 +++- 07-check_regression/results.compare2 | 1637 +++++++++- 07-check_regression/results.regressions | 101 + dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 120 +- mail/mail-subject.txt | 2 +- manifest.sh | 21 +- results | 101 + sumfiles/g++.log.xz | Bin 3637328 -> 3623712 bytes sumfiles/g++.sum | 1386 ++++++--- sumfiles/gcc.log.xz | Bin 3263280 -> 3214540 bytes sumfiles/gcc.sum | 4334 ++++++++++++++------------- sumfiles/gfortran.log.xz | Bin 1081396 -> 1087828 bytes sumfiles/gfortran.sum | 50 +- sumfiles/libatomic.log.xz | Bin 2356 -> 2356 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213632 -> 213408 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2724 -> 2724 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 464392 -> 466224 bytes sumfiles/libstdc++.sum | 38 +- 35 files changed, 5940 insertions(+), 2637 deletions(-) create mode 100644 07-check_regression/extra-bisect-params create mode 100644 07-check_regression/fails.sum create mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap updated (5606742690 -> a1d013977e)

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 in repository toolchain/ci/base-artifacts. discards 5606742690 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits discards 1d0db5d782 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits discards c2a67111d2 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits discards e77c00a23b 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] discards 7fdc0b3050 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits discards ce2863acf3 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits discards 1dd37e71a8 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards e9c59fc262 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] discards 3469b863e3 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards ccdce5b604 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards 97700724af 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards 5436d596d8 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards c48597dd2d 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards 5c97707174 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards f1cb6e95c6 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards c109565232 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards df16dfe3cd 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards e75fadff5b 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards 188eee554a 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards eeaf749e7a 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards 94249b1886 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards 6048185c13 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards c3d05f9993 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards 4188278a02 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 6342fe2b97 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards 922c98ece5 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards cbd2bd8824 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards faabd3ae6a 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards ae2ada42af 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 8c1704f7e3 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards df743dd232 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards e47cd33ad3 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards c51d7e28f0 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards 727f208817 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards 8ffa91d587 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards ce0d248d8e 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards ce6d3c11db 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards d8f3026462 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards 348001789c 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 098bcb9779 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 4482436bb5 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards f733575570 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards d05e8a8224 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards e4ee43cd7f 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards def80afca2 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards c92de0b930 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 2838dfbbbd 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards 6d3420b29f 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 52e8cd9a81 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 16eb657fc7 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards 05cfd5e444 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards f63ea40157 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards bd73fde2d3 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 5804509491 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 665c173c91 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards b0b6ce2046 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 5831752139 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 3d954f0392 88: onsuccess: 1: Success after gcc: 20 commits discards cb9057c648 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards 82334e2d36 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards 0fd94856bd 85: onsuccess: 2: Success after binutils: 4 commits discards aced4fe28d 84: onsuccess: 2: Success after gcc: 9 commits discards 650978e086 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 75d3e5c689 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 9dc4346a48 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 3bf37d1513 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 6bb0442cdc 79: onsuccess: 1: Successful build after gcc: 3 commits discards 6014bb7b52 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 27bf4e3807 77: force: 2: Successful build after gcc: 32 commits discards f66058c573 76: onsuccess: 2: Successful build after binutils: 10 commits discards d8a28c84d5 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 7064970dfc 74: onsuccess: 2: Successful build after gcc: 13 commits discards 4a4b2328b2 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards c2b2333226 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 6c1a1d049b 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 25bc48f474 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards b945a13795 69: onsuccess: 2: Successful build after baseline build: no [...] discards 99c88e39fd 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 4838897891 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 0fa6e22222 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 2a0e370bfc 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards fef1eec60e 64: onsuccess: 2: Successful build after gcc: 7 commits discards 4071193f10 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 20193d9eb3 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 761a5c2e21 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 9f7dcf475e 60: onsuccess: 1: Successful build after gcc: 15 commits discards e40c8722d1 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 3491d11504 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards 88974f8cdd 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 3fe6ee3fed 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 0c90719d17 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards c5b79d3e1f 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 7fcb06767f 53: onsuccess: 2: Successful build after gcc: 5 commits discards dfecd8923c 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards e2decf2a47 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 9d0c9f628d 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 84561344fa 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards e12e3a725b 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards ff0912c2a1 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 260ec7a92b 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 2b2206d960 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new f05bc9b05b 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 200695b7de 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 928f4c0612 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 3996c47ba4 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new b7040f4416 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 65a2ba6ac5 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new bd418883c1 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 69ae58f17c 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new bdfdcb392b 53: onsuccess: 2: Successful build after gcc: 5 commits new f7bf181169 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ac4d0fc392 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 19297155e1 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new e27347e80a 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 8368c95bf1 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new 6dd580862d 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new ca2053e5d3 60: onsuccess: 1: Successful build after gcc: 15 commits new e88b399609 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 684e260c0c 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new dda830e84d 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new fb9adab089 64: onsuccess: 2: Successful build after gcc: 7 commits new 056b023326 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 2b9a7e6ff0 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 957a63fead 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 322546c2f4 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new e2cc1e705f 69: onsuccess: 2: Successful build after baseline build: no [...] new 6200d97521 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new f30c8118f6 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 3a60390d49 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 3258ee9ad1 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 68e1a93e35 74: onsuccess: 2: Successful build after gcc: 13 commits new b8086972a6 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new d77afcbc05 76: onsuccess: 2: Successful build after binutils: 10 commits new e33ee51bd3 77: force: 2: Successful build after gcc: 32 commits new 63a7b99149 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 84a347bb3f 79: onsuccess: 1: Successful build after gcc: 3 commits new 07e6ea1a54 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new a8b47a9609 81: onsuccess: 2: Success after binutils/gcc: 16 commits new d0026dbb7a 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 915b81d57b 83: onsuccess: 2: Success after binutils/gcc: 7 commits new a0435d1758 84: onsuccess: 2: Success after gcc: 9 commits new 692591cf1d 85: onsuccess: 2: Success after binutils: 4 commits new a4925cc257 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new 525a75668f 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new c62d86e279 88: onsuccess: 1: Success after gcc: 20 commits new d8e7c69960 89: onsuccess: 2: Success after binutils/gcc: 39 commits new ae86174b7a 90: onsuccess: #1472: 2: Success after gcc: 2 commits new b06014d746 91: onsuccess: #1473: 2: Success after gcc: 2 commits new ebc479971a 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 8fe8ef48c6 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new 5969df9dd7 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new f4dda02e5b 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new bd66a22f7a 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 2ba46d3c13 97: onsuccess: #1481: 2: Success after gcc: 8 commits new b832dcb48b 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 7510eb2bc5 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 61af3f4829 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new e8ca31ca50 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new ba3dff51aa 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 7c892b8d4d 103: onsuccess: #1524: 2: Success after gcc: 2 commits new ec3cc9f8a1 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new c8918ea898 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 25083ff042 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 1018d13a66 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new ab097bc776 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 058c14a351 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 635e6d08e1 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 08a9f41f79 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 970d3325ca 112: onsuccess: #1533: 2: Success after gcc: 5 commits new e6dcf750e8 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new a89ac65868 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new eec68df014 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 08cd50fcb5 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 67b86e0ecb 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new eb1d949653 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new e4ad16e779 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new 78c4e5ab68 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 49f391a9a2 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new 7da44d9fca 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 1da710b093 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 327f9f7a22 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new 28f65a2797 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new c613f46baf 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new 1264e12e6f 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new c74a78ac29 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new 6b22f7c352 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new 6c7b0e010d 130: onsuccess: #1554: 2: Success after gcc: 9 commits new 713bb8d3fe 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new 191f97d0a7 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new 42af240b28 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new 9167f13875 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new 3ac9e1d15d 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new 24891a09da 136: onsuccess: #1561: 2: Success after binutils: 3 commits new f07ee24d7c 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new c7a233ac15 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] new d6fee00efe 139: onsuccess: #1566: 1: Success after gcc: 5 commits new 252c853075 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits new f58fbe71d6 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits new a22c263632 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] new 8f28e2eb5c 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits new d5bac15cb3 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits new 65082e52d2 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits new a1d013977e 146: onsuccess: #1573: 2: Success after binutils: 7 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (5606742690) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] 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 1616 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 38060 -> 38576 bytes 05-build_abe-bootstrap/console.log.xz | Bin 272228 -> 270884 bytes 06-check_regression/console.log.xz | Bin 3036 -> 2780 bytes 07-update_baseline/console.log | 40 +++++++++++++++++----------------- 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 | 16 +++++++------- 12 files changed, 33 insertions(+), 33 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[binutils-gdb] branch master updated (d988b231b0d -> 3bf49942762)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from d988b231b0d RISC-V: drop stray INSN_ALIAS flags new 3bf49942762 objcopy: avoid "shadowing" of remove() function name 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: binutils/objcopy.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (6e01019417 -> 5948b5117f)

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-arm in repository toolchain/ci/base-artifacts. discards 6e01019417 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 874198af85 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 616028e5cf 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards a4a5a708bc 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards fdd4cb18ad 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 669554203e 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 756d0ee525 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 10dfc2d8cf 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 9a612caa9d 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 9c2dc5a22c 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 2c92c18364 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 78fb0aa2e8 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards de9aad1186 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 10638ef600 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 32c715c6b4 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 32835372e2 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 3cacbb311e 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 339164b8aa 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 6c28f0b41c 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards e7d3a46864 128: onsuccess: #1723: 1: Success after linux: 12 commits discards ec48df4b0c 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 5592b86198 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards ed8d9c139c 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 39f03e09b1 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 97c7b954bf 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards e4a565b4b6 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards cd3984760d 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards ac7d577305 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards d5bceed6b3 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 1d93f05c60 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 9661acff43 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 69bedf934e 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards a4d5662b2a 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards b882bf8dfd 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards ed8bb9ecdd 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 95c76b2b10 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards e7fba326bf 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 3c1841be1b 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 829786e21f 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards d0ab181c7e 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 3ce2a181d8 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards b8b9830ddc 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 9ec49e605c 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 6e38b16556 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 00a3d15faa 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 6a190a5c77 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards e7372ac4cf 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards bce34a74bf 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards fa39ebdc74 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 4357bc2c00 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 7bd818a9a1 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 11e749815b 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards ba8dc622d3 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards cdbe3ca52c 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 98c92eeefe 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards d4a5d9b33e 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 7cb8d33dec 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 41424d79b5 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards f424cb1249 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2af8bf8a20 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 89d4295089 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards b3e2bdceba 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards ba8d7aaf69 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 5fad5a2d39 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards bd45238dcf 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 2ab5f7bfe0 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards ac6ac3e0c8 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards c869ca023d 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 2fa0f36625 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 5e7bab3c95 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e7d50687ec 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 15f279974e 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 2f9e476809 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1c5bb0c3b8 74: onsuccess: 1: Successful build after linux: 44 commits discards 7222fb6191 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 84ca4c0489 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dc6c91118a 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 19cd1b5966 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 179e926b6b 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 150a6b0a0e 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bc0630a88b 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dcaa6d8185 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 9a15510758 65: onsuccess: 1: Successful build after gcc: 4 commits discards ce88bf9163 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f0f37f1557 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3abdb8b078 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards e78e9c869f 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 2eb13c4887 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 472e50c11f 59: onsuccess: 1: Successful build after glibc: 2 commits discards cfa78e3f0d 58: onsuccess: 1: Successful build after binutils: 2 commits discards 4504a5d491 57: onsuccess: 1: Successful build after gcc: 7 commits discards 2fba437416 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 45a8c35d78 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0531b34a39 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards edd36246de 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 62e3e38940 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards bd4737eab6 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2108ac35b2 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 50419f56f5 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 08bb27195c 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 3010bda873 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1905d8a1d8 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 50f6842b3a 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 532ead1b83 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3d705e2ace 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 067bc32d3e 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new f44cafd70f 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 07dfc6de28 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 24d22df4af 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new b1fc74e027 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9f45ac32a7 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 290222a313 57: onsuccess: 1: Successful build after gcc: 7 commits new 4d3f298697 58: onsuccess: 1: Successful build after binutils: 2 commits new 001db9eebe 59: onsuccess: 1: Successful build after glibc: 2 commits new 1c7abcd883 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new dd2800403a 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 2442c4c07e 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 6c13b1b4e2 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d485700f1c 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 76a5a75a4c 65: onsuccess: 1: Successful build after gcc: 4 commits new 12bd1e73ba 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 51bc0138f7 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2f5277ef5e 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a434b5d0fd 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 159d9116ca 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new f7b7b8aa4a 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new ba5d4b4c63 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6a5c226248 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 135a659a82 74: onsuccess: 1: Successful build after linux: 44 commits new d9a1682456 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8f9aa06aa1 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 9f4ee516df 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 18c3fb3e77 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new fbde6004a5 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 073cdc08b5 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 4706f77d49 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 0a9ab7c298 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 68b19f82ae 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new ef1946ed85 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 683deeeb01 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 0f7362f793 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new bbce0b12e8 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 992e7395f2 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new e6e666d838 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new adb175c715 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 205c43fefa 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 89aefb98e5 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 65c67a03f6 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new d8772de64b 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 2528a3bdf4 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 798b0e1ebb 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 2b108f5b5a 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 8def3bed92 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new db09a44a81 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 43ff174a36 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new e799e8405e 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 22a52a5f61 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 1b8a06d1d7 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 3b13f519c2 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 343865baa9 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 7fa5573035 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 4fcbc07093 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 046ca4440a 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 7eaaebb426 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 283b91cc85 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 3e25c39d5f 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 99100ad592 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new df06bac642 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 17e4d4a13f 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new c19efbc729 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 800e64eb0a 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new f509b3e9f8 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new d0b597f2aa 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new d53ead43ee 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 3ac07afa97 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 1b5b409b8f 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 298eef0430 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 1e5a1d8316 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 61ce0bf6ac 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 54b10c88ea 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 1783a9a610 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new cd0c215bc2 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 36cc0810e5 128: onsuccess: #1723: 1: Success after linux: 12 commits new c9dc40cc9c 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 8017bd45a4 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new c97950aa67 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 02e0509ec6 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new e8dc81a960 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new e73c190057 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 37ee5bcfbc 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 7a38ef4a23 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 6125e5ad08 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 203820eb85 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new bf28cf4e91 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 2d06afc5b7 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 7aaeba662c 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 56214ad86a 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 87696960dd 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 59e19a4eda 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 4688e9cbe2 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new e3c16571fc 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 2d0f4342c1 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 5948b5117f 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/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 (6e01019417) \ 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 1684 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 29912 -> 30300 bytes 04-build_abe-stage1/console.log.xz | Bin 90360 -> 90676 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8432 -> 8468 bytes 07-build_abe-glibc/console.log.xz | Bin 233124 -> 233904 bytes 08-build_abe-stage2/console.log.xz | Bin 223648 -> 223088 bytes 09-build_abe-gdb/console.log.xz | Bin 37240 -> 37588 bytes 10-build_abe-qemu/console.log.xz | Bin 31424 -> 31360 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3852 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2428 -> 2764 bytes 13-check_regression/console.log.xz | Bin 6528 -> 5912 bytes 13-check_regression/mail-body.txt | 47 - 13-check_regression/results.compare | 32 +- 13-check_regression/results.compare2 | 100 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 49 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- sumfiles/g++.log.xz | Bin 2671680 -> 2681660 bytes sumfiles/g++.sum | 108 +- sumfiles/gcc.log.xz | Bin 2236828 -> 2193204 bytes sumfiles/gcc.sum | 2256 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 889400 -> 882492 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201272 -> 201232 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 433956 -> 423400 bytes sumfiles/libstdc++.sum | 16 +- 40 files changed, 1311 insertions(+), 1483 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[binutils-gdb] branch master updated (c4a7e6b5621 -> d988b231b0d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from c4a7e6b5621 LoongArch: Update ELF e_flags handling according to specification. new 1cb0ab18ad2 x86/Intel: restrict suffix derivation new 7b94647ad00 x86: improve match_template()'s diagnostics new 79d635fc64b x86: correct build dependencies in opcodes/ new 839189bc932 RISC-V: re-arrange opcode table for consistent alias handling new d988b231b0d RISC-V: drop stray INSN_ALIAS flags The 5 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: gas/config/tc-i386-intel.c | 76 +- gas/config/tc-i386.c | 151 +- gas/testsuite/gas/i386/i386.exp | 1 + gas/testsuite/gas/i386/inval-tls.l | 4 +- gas/testsuite/gas/i386/noavx512-1.l | 14 +- gas/testsuite/gas/i386/noavx512-2.l | 8 +- gas/testsuite/gas/i386/simd.s | 5 + gas/testsuite/gas/i386/simd16.d | 137 + gas/testsuite/gas/i386/simd16.s | 2 + gas/testsuite/gas/i386/x86-64-branch-4.l | 10 +- gas/testsuite/gas/i386/x86-64-branch-5.l | 32 +- gas/testsuite/gas/i386/x86-64-inval-tls.l | 4 +- gas/testsuite/gas/riscv/b-ext-64-na.d | 72 + gas/testsuite/gas/riscv/b-ext-64.d | 48 +- gas/testsuite/gas/riscv/b-ext-na.d | 51 + gas/testsuite/gas/riscv/b-ext.d | 28 +- gas/testsuite/gas/riscv/c-zero-imm-na.d | 24 + gas/testsuite/gas/riscv/c-zero-imm.d | 12 +- gas/testsuite/gas/riscv/c-zero-reg.d | 2 +- gas/testsuite/gas/riscv/csr-insns-pseudo-zfinx.d | 6 +- gas/testsuite/gas/riscv/csr-insns-pseudo.d | 6 +- gas/testsuite/gas/riscv/ext-32.d | 48 +- gas/testsuite/gas/riscv/ext-64.d | 64 +- gas/testsuite/gas/riscv/fence-tso-na.d | 12 + gas/testsuite/gas/riscv/insn-na.d | 69 + gas/testsuite/gas/riscv/insn.d | 12 +- gas/testsuite/gas/riscv/k-ext-64.d | 4 +- gas/testsuite/gas/riscv/k-ext.d | 2 +- gas/testsuite/gas/riscv/li32.d | 8 +- gas/testsuite/gas/riscv/li64.d | 56 +- gas/testsuite/gas/riscv/lla32.d | 6 +- gas/testsuite/gas/riscv/lla64.d | 10 +- .../gas/riscv/{zbkb-32.d => zbkb-32-na.d} | 3 +- gas/testsuite/gas/riscv/zbkb-32.d | 2 +- gas/testsuite/gas/riscv/zbkb-64.d | 4 +- ld/testsuite/ld-riscv-elf/ifunc-plt-01.d | 2 +- ld/testsuite/ld-riscv-elf/ifunc-plt-02.d | 2 +- ld/testsuite/ld-riscv-elf/ifunc-reloc-pcrel.d | 2 +- ld/testsuite/ld-riscv-elf/pcgp-relax-02.d | 4 +- ld/testsuite/ld-riscv-elf/weakref32.d | 4 +- ld/testsuite/ld-riscv-elf/weakref64.d | 4 +- opcodes/Makefile.am | 14 +- opcodes/Makefile.in | 14 +- opcodes/i386-gen.c | 2 - opcodes/i386-opc.h | 6 - opcodes/i386-opc.tbl | 300 +- opcodes/i386-tbl.h | 14636 +++++++++---------- opcodes/riscv-opc.c | 82 +- 48 files changed, 8234 insertions(+), 7831 deletions(-) create mode 100644 gas/testsuite/gas/i386/simd16.d create mode 100644 gas/testsuite/gas/i386/simd16.s create mode 100644 gas/testsuite/gas/riscv/b-ext-64-na.d create mode 100644 gas/testsuite/gas/riscv/b-ext-na.d create mode 100644 gas/testsuite/gas/riscv/c-zero-imm-na.d create mode 100644 gas/testsuite/gas/riscv/fence-tso-na.d create mode 100644 gas/testsuite/gas/riscv/insn-na.d copy gas/testsuite/gas/riscv/{zbkb-32.d => zbkb-32-na.d} (95%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (06a2d295df -> f3437bbff7)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-arm in repository toolchain/ci/base-artifacts. discards 06a2d295df 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] discards 2747382562 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] discards 9479146d57 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards ac7b92ccdb 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards b1d963aa8e 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards 6d299b2b27 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards f17219a16b 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards 164c88faf1 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards 2d459bfb1d 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards f2a06fe3c1 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards 03412e55b1 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards aef2249820 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards 2cf00b3679 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards c183e943a1 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards acf4ad0eb8 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards 723df76037 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 00ea279b63 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards 236d0c0863 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 86acfeadc5 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards 4e7982367a 132: onsuccess: #1645: 7: Success after linux: 23 commits discards b55ac87687 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 7689fed9bd 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards f64e283479 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 444d0348bc 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards 9e34cc893c 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 0d3a6cf395 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 12730ddab9 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards 20f8ad2e43 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 0abd87ce11 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards a6fbff5833 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 8885f40142 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 9e4ea125c4 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards d0b2218d0b 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 3d3162f928 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards d4b8fc96c6 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 507a8357a8 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards bf70145148 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 3ae2aca247 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 427257a9db 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 62a54f5ae5 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 945aef3259 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 230f7f0f44 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards 1f0f371d02 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 92544e9ed4 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 35cd2fde42 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 7df35a1d91 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 92f69f3bb1 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 7b35eadeed 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 0b360e7955 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards ccd7181430 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards fc406e0a91 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 53619b0645 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 3700ce9033 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 567d7a7523 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 9479995f26 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards 313eb45d67 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 70a72154cc 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards 63d0166a89 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards e245eeeefe 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 81daaf781c 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 1147af57ae 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards cbf2cfa2eb 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 70fdaea349 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards ff336f44ab 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards b60e2a85f4 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 71b42155ca 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 1beca5249f 85: onsuccess: 7: Success after gcc: 9 commits discards 77e6aa9761 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards ea29796de2 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 3490cd9367 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 637ef1b726 81: onsuccess: 7: Successful build after gcc: 2 commits discards 764a6f9e0c 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards d2de4a818e 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards e365ab41d6 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 129bb9d1ac 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 0bff996869 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b791f72426 75: onsuccess: 7: Successful build after linux: 44 commits discards cf86b8afcb 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 0b4a7cba49 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3b5f482208 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 4f1244bef6 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 612150d64f 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 8fbe4fd5a4 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards f6e4980580 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7a6274f57f 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 071286c748 66: onsuccess: 7: Successful build after gcc: 3 commits discards 752bc64b77 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d0f71eee44 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 78d32c6860 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards c649b5e796 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards dd6b533038 61: onsuccess: 4: Successful build after gcc: 15 commits discards 4517f85246 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards c3f25e4080 59: force: 7: Successful build after gcc: 2 commits discards 3eb3575647 58: onsuccess: 7: Successful build after glibc: 2 commits discards a1bbc89dc3 57: onsuccess: 7: Successful build after gcc: 7 commits discards d673ba3de3 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 87245fab0f 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a2689a5106 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 348b02b5f7 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 23e4eb8e22 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards ed9f7ef606 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new cdcefe8d74 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 5752b93a2b 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new fb1ec742db 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 11e8e05164 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new fa6d5cf4ae 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7857a50269 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 624274d0f6 57: onsuccess: 7: Successful build after gcc: 7 commits new 7ee66451e4 58: onsuccess: 7: Successful build after glibc: 2 commits new 4a8e656b86 59: force: 7: Successful build after gcc: 2 commits new 5f81c4560e 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 4502d4ecfe 61: onsuccess: 4: Successful build after gcc: 15 commits new 72c1010d69 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 0e0b377751 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new ff2ac65922 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4bbfdf95bc 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7ef9e9a81b 66: onsuccess: 7: Successful build after gcc: 3 commits new 5185ba1200 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 9a164f6069 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f6237e9dfd 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new b7ac6a2be8 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 411730b886 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 311815273c 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 02b7329753 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7e9a9604a9 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 9ad0dfa44f 75: onsuccess: 7: Successful build after linux: 44 commits new 9782c52a66 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7c45ecc8fb 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 27f8eeca3f 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5281d6b44e 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new e15f14f53b 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new ab739e0484 81: onsuccess: 7: Successful build after gcc: 2 commits new 0ab8bb3c05 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 36295794cf 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 7d3d98ecab 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 1626e7dda5 85: onsuccess: 7: Success after gcc: 9 commits new dec27674f8 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new f2bb3bc33e 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 97bab3b931 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new c35723eff8 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 97bbb116fa 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new dbd01bfe3c 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 3414988978 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 8edf02cdc8 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new bc549c8efc 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 4cc6a2f65d 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 9d5528f444 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new bcd4758acc 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new b8dcdd3369 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new e552a97011 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 5518397756 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new 9957e07d65 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 8932ff0cdc 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 8614bb1d0d 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 638ab8f651 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new c2df094a7c 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new ec62d53b0a 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 2041c3099c 107: onsuccess: #1618: 7: Success after gcc: 2 commits new dce176b710 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new 08df0b1e68 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 18c929eb2f 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new f7a82e51e6 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new e31128d762 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 049a876880 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 9563610cfa 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 69d4ee46f7 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 98d87ea7e9 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 5bc3453677 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 40dcf9c84c 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new baf8183c06 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new ab3a8cbf2f 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 5e276eba4b 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new e389529448 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new ddfc0c2d98 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new c7b639b842 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new d499027470 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new bf87e2eed3 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new f990eb2cf2 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 21d461739c 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 6ebcfeeb33 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 4333413703 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 494dc06eda 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 31028abd64 132: onsuccess: #1645: 7: Success after linux: 23 commits new 1cbdbf240f 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new a2dc6146ac 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new 7db46ac5a5 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new 89ee0ddd6c 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 4eb9b99c40 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new 03a75e89ef 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new 5caf9fe4d5 139: onsuccess: #1654: 1: Success after gcc: 11 commits new a82657e550 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new 24524e40e3 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 844f8f92a6 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 5473377bd8 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new 09592d60cd 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new 3c049bd5a7 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new 1f6b4e58d9 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new 06b44bb7da 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new d144b94807 148: onsuccess: #1663: 7: Success after glibc: 2 commits new 91106e13fe 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new 9531665ac0 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] new a8d5a8c3f3 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] new f3437bbff7 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/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 (06a2d295df) \ 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 1716 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 30108 -> 30228 bytes 05-build_abe-stage1/console.log.xz | Bin 90616 -> 91164 bytes 07-build_abe-linux/console.log.xz | Bin 8448 -> 8472 bytes 08-build_abe-glibc/console.log.xz | Bin 233792 -> 234220 bytes 09-build_abe-stage2/console.log.xz | Bin 223688 -> 224088 bytes 10-build_abe-gdb/console.log.xz | Bin 37116 -> 37440 bytes 11-build_abe-qemu/console.log.xz | Bin 31548 -> 31584 bytes 12-check_regression/console.log.xz | Bin 4048 -> 3820 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +++++++++++----------- 20 files changed, 60 insertions(+), 60 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

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

by git＠git.linaro.org

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (c569ec51bd -> e25a460018)

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 c569ec51bd 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards 5e6975dd5f 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards 7109d91464 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards 5794ac65f3 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 10bef23fc0 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards f73631db86 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards 189e672586 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards f23a95ae0f 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards 5caef046f0 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards fc922cea08 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards 8ce586cc23 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards c3e56d4292 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards 12158d2c29 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards 587637a977 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 56242574c8 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards 465b8f85ac 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards f516785574 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 69a2fa7123 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 9b8160a340 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards 2bba1a5b3f 128: onsuccess: #1579: 7: Success after linux: 12 commits discards e54a1b9238 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 8189d88247 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 9b234e6ad0 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards a4744593d5 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards af92a46a6e 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards e479996ffe 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards e527cc4d56 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards b8f2d223ab 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards 01decfddf9 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 11aae636f4 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards 11ba4db3ba 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards e08c3c54f8 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards c98ea79f5f 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards e8682e21cb 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards 850487b36f 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards e33885529a 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards f5bda69c49 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards da59059167 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards e1f847095d 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 1016e837cd 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 8f2e5fc879 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards e4763d6c4a 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards ed20fcab79 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards 7f4642db46 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards 310adb2020 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards e8cdf11a6b 102: force: #1551: 1: Failure after gcc: 306 commits discards 8f47c10ee2 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards e287f0fcde 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 8cc2476f42 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 6f83e5a938 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 35711901ab 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards d975baa218 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 42be049976 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1dfa8a42d4 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards edb4a86e96 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards eceafcf7a2 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 1fdbac6822 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 6a486f1299 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards a14884aca9 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 304ee70819 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 0b2201a2eb 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 73a89feec6 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 0d830b0be1 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards e83e4dc545 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 14f5d33fc5 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5b2212ed7e 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 0549ce3545 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e02ff168f3 80: onsuccess: 7: Successful build after linux: 44 commits discards 4187dfe7d3 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 3b4630d98b 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards 34b80ab7dc 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d156404aec 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 814c8f9f5f 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards bdcdc263c9 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards a28675b804 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e8ba5ac537 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 238fb29fd7 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards f616752d33 70: onsuccess: 7: Successful build after gcc: 4 commits discards bce28e38bd 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 8557b69d14 68: onsuccess: 7: Successful build after linux: 6 commits discards b6b9562263 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards 6008248e5d 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards ab00d6041e 65: onsuccess: 7: Successful build after binutils: 3 commits discards dff224a807 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 95a759b74d 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 2345dc8b36 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 691da9d741 61: onsuccess: 4: Successful build after gcc: 5 commits discards c101016570 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 924b40a2ba 59: force: 7: Successful build after gcc: 3 commits discards 7cbacd2a17 58: onsuccess: 7: Successful build after glibc: 2 commits discards 0f30293ce2 57: onsuccess: 7: Successful build after gcc: 7 commits discards e639df1d9d 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5f1878cb15 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e04230d4d5 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards b46ef8913d 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 6a1c0ba611 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] discards e96037553f 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards bf77ea730a 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 90e3c2831a 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards cba55b18e2 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 874a444f88 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5e36210fc9 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 38baa22d32 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 8b1f59ba1c 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 698977530c 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 51cfa37733 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 44e208e380 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new 377f2d8ac5 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 5ebe1a8ec5 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new a00ec6dcc2 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f84c654e14 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 0f6ca84419 57: onsuccess: 7: Successful build after gcc: 7 commits new 0753c76cd2 58: onsuccess: 7: Successful build after glibc: 2 commits new 5a29d982ef 59: force: 7: Successful build after gcc: 3 commits new c1c6348cfe 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 581dd8a0e3 61: onsuccess: 4: Successful build after gcc: 5 commits new de7ebb9ad6 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new e75469dea0 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 2da43c676a 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new cde8a0972b 65: onsuccess: 7: Successful build after binutils: 3 commits new a05a712a90 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 88d375b67b 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new 905ee59c68 68: onsuccess: 7: Successful build after linux: 6 commits new 269743932e 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 938fd94d61 70: onsuccess: 7: Successful build after gcc: 4 commits new 56c386044b 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 95106cf21a 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 9a2db4759a 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 0a189b385e 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 10f727dc01 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new cedebc9f62 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new fed1953754 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new efe26c381e 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new b0aadfdfad 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new e6f269077f 80: onsuccess: 7: Successful build after linux: 44 commits new 6446d10bf8 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 111e5d318e 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 9cc589bc9f 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e9121e8be3 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 59016b8d46 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 928e9456ed 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 6745b00710 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 117ab4f979 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 790609fba8 89: onsuccess: 7: Success after gcc/glibc: 8 commits new ce298ecd31 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 197c10eb91 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 87a5798da3 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 57af793785 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 15678e2844 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new d3d57b7b37 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 5c313b4159 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new b8c16ee67a 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 4395d95906 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 44411e6185 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 9fba5acd9c 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 9f6bdf6e1f 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 093cabef1b 102: force: #1551: 1: Failure after gcc: 306 commits new d3e51325d5 103: onsuccess: #1552: 1: Success after gcc: 5 commits new b298856745 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 1f773edb43 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new a1dbc215b6 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new bd616c26b8 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new bbdb3a75be 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new 515ebbf741 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new c86adc916a 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 99f2f7f4ae 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new 2c00735de4 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new cf9ec65eec 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new 4b46e54312 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 8983bdd2f3 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 822e90b7bd 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new e07bc6988d 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 993f3c0316 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new 272e505276 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new 70b6d44ba0 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 8df0b73259 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 68142ef5cf 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 647b3ae7e9 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new f9472b63bd 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 810717c4d1 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 6b8c2a77ca 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 708d516859 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new 1098d81c65 128: onsuccess: #1579: 7: Success after linux: 12 commits new c206a1bf53 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new 567bc5c455 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new f1d1bc2284 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new 6cc3c2f8ed 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 47480af588 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new f9d02ddb3c 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new a8912336ac 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new b908e233d3 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new f19e797d01 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 8d3cc00126 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new f03dab070c 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 6dbab2cce1 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new 346207108d 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new 4fb2d650c2 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new 8798d448d2 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new 6c3614d7e6 144: onsuccess: #1595: 7: Success after glibc: 2 commits new 642860ca1f 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new b5ddb3e933 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new 240af40538 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new e25a460018 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/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 (c569ec51bd) \ 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 1720 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 30144 -> 30408 bytes 05-build_abe-stage1/console.log.xz | Bin 72100 -> 72460 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 8452 -> 8456 bytes 08-build_abe-glibc/console.log.xz | Bin 240244 -> 239464 bytes 09-build_abe-stage2/console.log.xz | Bin 202692 -> 202436 bytes 10-build_abe-gdb/console.log.xz | Bin 37296 -> 37796 bytes 11-build_abe-qemu/console.log.xz | Bin 31980 -> 31956 bytes 12-check_regression/console.log.xz | Bin 4156 -> 3836 bytes 13-update_baseline/console.log | 70 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++---------- 21 files changed, 62 insertions(+), 62 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (5fe12ecd1d -> 4127416d5c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-aarch64 in repository toolchain/ci/base-artifacts. discards 5fe12ecd1d 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits discards fe21692b1f 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits discards 91e1633e04 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits discards 7461788739 141: onsuccess: #2073: 1: Success after binutils: 3 commits discards c6b412dc98 140: onsuccess: #2070: 1: Success after binutils: 4 commits discards 3a95d418da 139: onsuccess: #2067: 1: Success after binutils: 2 commits discards 65865d1ee5 138: onsuccess: #2064: 1: Success after binutils: 4 commits discards dbc21e0fc6 137: onsuccess: #2061: 1: Success after binutils: 2 commits discards 35721acc01 136: onsuccess: #2056: 1: Success after binutils: 4 commits discards f7e517a1a4 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits discards d86ba3e951 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits discards 0d08f236ac 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits discards ff1f8c486a 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits discards 5712d7b94f 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] discards 8a8f5aa0da 130: onsuccess: #2049: 1: Success after gcc: 9 commits discards 481230d05a 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] discards 5c4d6301f5 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] discards 22d7a01be6 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] discards e2664d38bc 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] discards 7f06eb1532 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits discards b9098e7662 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits discards cb2fdfe6e2 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits discards 413594fa04 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits discards 83d49d9cfc 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits discards 1a7b94267e 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits discards 86b759107a 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits discards ef96cca70d 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits discards e4adb311a2 117: onsuccess: #2034: 1: Success after binutils: 2 commits discards f73cf1c7ae 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits discards f9d1d419b2 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits discards 0228e2c173 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits discards a31bb2f7d4 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits discards b5f7ef0907 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits discards d4d58c2841 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits discards 829474084e 110: onsuccess: #2027: 1: Success after gcc: 5 commits discards 317ea0b147 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits discards e3e87fa693 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits discards 5c56e3d465 107: onsuccess: #2024: 1: Success after gcc: 3 commits discards 198f3e0be5 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits discards 8d1de6481b 105: onsuccess: #2022: 1: Success after gcc: 4 commits discards bb7885391e 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards 406b7da45e 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards 57d115e4e9 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] discards 486948924a 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards fa204ace4f 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards 4ab9750082 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards 980e704473 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards 8015211bb8 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards e366f646af 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] discards 8fabf02466 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] discards a0dac01d2c 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards 4ac974eb73 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] discards d04ab53b80 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards c45daaf037 91: onsuccess: 1: Success after gcc: Daily bump. discards 4c551339f0 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards 4e8c2a78e0 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards 18a6e63e0e 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards 243c486ef5 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards 666a130638 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards f1562f1b71 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards f51a2f6a67 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards 0e720c0b74 83: onsuccess: 1: Success after gcc: 8 commits discards 8f22e75c11 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards 3d6f3b323f 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards 4d6f6ca2e2 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards b390dab5b5 79: onsuccess: 1: Successful build after gcc: Daily bump. discards 7a4232b739 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 6b5d3d45cc 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 858951fd92 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 8e891b3b5d 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards e3648a2acc 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards fb189fa002 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards 1f88ba63d4 72: onsuccess: 1: Successful build after gcc: 2 commits discards 6671768e9f 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 49e9ec013c 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards 3935504a7a 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 7933ab599f 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 7a03262ea1 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 810ea138de 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards a6c5d8a7d3 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 22d9bec6dd 64: onsuccess: 1: Successful build after gcc: 5 commits discards ca00159339 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards bc3c97ad5d 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards f13dec6fee 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits discards fa076eb7fe 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 48f6fa8f34 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits discards 43225f9495 58: onsuccess: 1: Successful build after binutils: 2 commits discards 00689f0735 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards 04475f9f24 56: onsuccess: 1: Successful build after gcc: Daily bump. discards 94a9a49b80 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards be90ba1cbd 54: onsuccess: 1: Successful build after gcc: 7 commits discards b2d87ce131 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 3c9c7e870a 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 1d3238c742 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 211f672294 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 9f4d183975 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 89d839e470 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 052cd1ea34 47: onsuccess: 1: Successful build after binutils: 2 commits discards 8d84bea123 46: onsuccess: 1: Successful build after gcc: Daily bump. discards 673c1aa291 45: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards e7db8c6b13 44: onsuccess: 1: Successful build after gcc: 2 commits new 758a2a8c38 44: onsuccess: 1: Successful build after gcc: 2 commits new 8574e28ac1 45: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 6494cf8e1f 46: onsuccess: 1: Successful build after gcc: Daily bump. new 2432936b27 47: onsuccess: 1: Successful build after binutils: 2 commits new 78a1ac45b2 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 693046cfba 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 21871bc1d5 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 871c0de9eb 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 9e8fb5de43 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 30de8bb389 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 4d78034f47 54: onsuccess: 1: Successful build after gcc: 7 commits new 5d132af293 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 0054781c66 56: onsuccess: 1: Successful build after gcc: Daily bump. new 1b84370f9c 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits new 4885e12fcd 58: onsuccess: 1: Successful build after binutils: 2 commits new 580b55c61a 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits new 980703e043 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 7baa6eb208 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits new 7a9a3d2d8b 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 6deb6d201d 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 75f062127f 64: onsuccess: 1: Successful build after gcc: 5 commits new b31396958d 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 86cb74d1b8 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 6ff45aedac 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new f14591e784 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new c1c1298611 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 991f937dfc 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new 3ccbb0d45c 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 3f87a42514 72: onsuccess: 1: Successful build after gcc: 2 commits new c5c5ae3fc7 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 81edbf08a6 74: onsuccess: 1: Successful build after binutils: Automatic [...] new cd24c90347 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new ac93780669 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new a756c86a80 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new b3c0ba150a 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 212f412b04 79: onsuccess: 1: Successful build after gcc: Daily bump. new 3e772308e9 80: onsuccess: 1: Success after binutils/gcc: 14 commits new efe52fecf2 81: onsuccess: 1: Success after binutils/gcc: 27 commits new 39c18759b2 82: onsuccess: 1: Success after binutils/gcc: 10 commits new 1b39c517b6 83: onsuccess: 1: Success after gcc: 8 commits new 393722885b 84: onsuccess: 1: Success after binutils/gcc: 9 commits new 53da167529 85: onsuccess: 1: Success after binutils/gcc: 9 commits new a8bb61531a 86: onsuccess: 1: Success after binutils/gcc: 13 commits new 1677ae3e81 87: onsuccess: 1: Success after binutils/gcc: 4 commits new 612dcda40c 88: onsuccess: 1: Success after binutils/gcc: 16 commits new 7fed26eebf 89: onsuccess: 1: Success after binutils/gcc: 9 commits new e9bfb63dd0 90: onsuccess: 1: Success after binutils/gcc: 6 commits new 8b4d2e7dbc 91: onsuccess: 1: Success after gcc: Daily bump. new d0599f2a71 92: onsuccess: #1965: 1: Success after gcc: 2 commits new 3e6572c7b5 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] new f63a90abf8 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new 1a0613095b 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] new b7d7ebbe50 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] new 0bd6ddb9c1 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new e5306b3c97 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new 2a91523d72 99: onsuccess: #1974: 1: Success after gcc: 14 commits new 15fed3be18 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new 269fbb5cbb 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new 62f10e26ce 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] new 0c6d2108ac 103: onsuccess: #2020: 1: Success after gcc: 2 commits new aca929f226 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new 57674dcffe 105: onsuccess: #2022: 1: Success after gcc: 4 commits new 0587cf8aaf 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits new a47182266c 107: onsuccess: #2024: 1: Success after gcc: 3 commits new b00ae5c6df 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits new 09fe868a3a 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits new 3bfc488332 110: onsuccess: #2027: 1: Success after gcc: 5 commits new 0f48e51cbe 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits new 331417ccb3 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits new cf21d4388a 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits new bf6dd0634c 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits new bd9be62898 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits new 0f6b582251 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits new 1202439a60 117: onsuccess: #2034: 1: Success after binutils: 2 commits new 05a7a6abb3 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits new 4224235c17 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits new 74f07f3398 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits new 551c1701a2 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits new 59c7c6144a 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits new 6b33a48f8f 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits new 4243caaf26 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits new 313bb468db 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits new 6c8f82b104 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] new 9e9bce8f0f 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] new a49dd43ca8 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] new 1c6c9833cb 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] new 7092228590 130: onsuccess: #2049: 1: Success after gcc: 9 commits new db04826ce1 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] new 860955f10c 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits new a483136803 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits new d4ee24fef7 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits new d087c3eb14 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits new 475fe7649f 136: onsuccess: #2056: 1: Success after binutils: 4 commits new 35bfb7787f 137: onsuccess: #2061: 1: Success after binutils: 2 commits new 53ed044e52 138: onsuccess: #2064: 1: Success after binutils: 4 commits new 33beca1845 139: onsuccess: #2067: 1: Success after binutils: 2 commits new 40b56abf08 140: onsuccess: #2070: 1: Success after binutils: 4 commits new 94784fa72b 141: onsuccess: #2073: 1: Success after binutils: 3 commits new ac1ec96b1a 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits new 571e9d07f9 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits new 19b5c8f698 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits new 4127416d5c 145: onsuccess: #2078: 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 (5fe12ecd1d) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-aarch64 [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1724 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 37608 -> 38460 bytes 04-build_abe-gcc/console.log.xz | Bin 212256 -> 213908 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3888 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2876 -> 2724 bytes 07-check_regression/console.log.xz | Bin 5636 -> 4712 bytes 07-check_regression/mail-body.txt | 37 - 07-check_regression/results.compare | 31 +- 07-check_regression/results.compare2 | 108 +- 08-update_baseline/console.log | 56 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 39 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 3559424 -> 3569964 bytes sumfiles/g++.sum | 128 +- sumfiles/gcc.log.xz | Bin 3103044 -> 3100244 bytes sumfiles/gcc.sum | 4830 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1042484 -> 1041792 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2192 -> 2184 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207100 -> 207396 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 450096 -> 443520 bytes sumfiles/libstdc++.sum | 10 +- 32 files changed, 2575 insertions(+), 2758 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

← Newer
1
...
6
7
8
9
10
11
12
...
469
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022