Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-mainline-allmodconfig updated (2c4422311b -> 1faa9ee61e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-mainline-allmodconfig in repository toolchain/ci/base-artifacts. from 2c4422311b 20: onsuccess: #495: 36: Success after llvm: 10 commits new 1faa9ee61e 21: onsuccess: #496: 23021: Success after binutils/llvm/linu [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1784 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30116 -> 29924 bytes 04-build_kernel_llvm/console.log.xz | Bin 63868 -> 64724 bytes 05-build_abe-qemu/console.log.xz | Bin 31092 -> 31584 bytes 06-build_linux/console.log.xz | Bin 3548 -> 4680 bytes 08-check_regression/console.log.xz | Bin 3004 -> 4528 bytes 08-check_regression/mail-body.txt | 9 +-------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 11 ++--------- mail/mail-subject.txt | 2 +- manifest.sh | 31 +++++++++++++++++-------------- results | 2 +- 18 files changed, 28 insertions(+), 39 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/release-arm updated (5d35aadfab -> 6b5c88ee77)

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/release-arm in repository toolchain/ci/base-artifacts. from 5d35aadfab 17: onsuccess: #180: 1: Success after binutils/gcc: 8 commits new 6b5c88ee77 18: onsuccess: #181: 1: Success after binutils/gcc: 14 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 1660 -> 1660 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 51752 -> 51972 bytes 04-build_abe-gcc/console.log.xz | Bin 229156 -> 230208 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3808 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2332 -> 2320 bytes 07-check_regression/console.log.xz | Bin 5600 -> 5516 bytes 07-check_regression/extra-bisect-params | 1 - 07-check_regression/fails.sum | 7 - 07-check_regression/mail-body.txt | 52 +- 07-check_regression/results.compare | 39 +- 07-check_regression/results.compare2 | 100 +- 07-check_regression/results.regressions | 45 - dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 54 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 45 - sumfiles/g++.log.xz | Bin 2764092 -> 2763200 bytes sumfiles/g++.sum | 142 +- sumfiles/gcc.log.xz | Bin 2329144 -> 2359200 bytes sumfiles/gcc.sum | 3996 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 912056 -> 907708 bytes sumfiles/gfortran.sum | 48 +- sumfiles/libatomic.log.xz | Bin 2160 -> 2172 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 199472 -> 199500 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2548 -> 2532 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 458888 -> 461448 bytes sumfiles/libstdc++.sum | 22 +- 35 files changed, 2243 insertions(+), 2364 deletions(-) delete mode 100644 07-check_regression/extra-bisect-params delete mode 100644 07-check_regression/fails.sum delete mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (bebf3e43f8 -> 004a49bcd3)

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 bebf3e43f8 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] discards df3e0d3cd1 152: force: #1605: 7: Success after gcc: 9 commits discards 007d0453e7 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] discards c775b6f7a7 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] discards 7663cac513 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards 50f369be5d 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards 2e8581914e 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards 67814c8298 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards 0a1d4f7471 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards adc3de6f64 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards cf9a6a0507 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards b274c637b4 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards 80a381a38f 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 7e0f7b0b44 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards af5d47d89c 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards ce013099e6 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards 1e28f70a90 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 4203bcf32b 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards 3278a84788 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards 5bcf600492 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards e9e5acfad3 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards 50d5aea325 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards 4e01175e2b 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 5c98ad1f96 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 085d52e234 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards 0cfebf62d6 128: onsuccess: #1579: 7: Success after linux: 12 commits discards bbe18347d2 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 3336ba57a3 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards aa5267ab95 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 060ef40ad8 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 94609b40e2 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards 2deaa7835b 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 48caf50364 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards 80dc671134 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards 87b299e94d 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 87dc270594 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards c711fefa1a 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 90696fe10d 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 951e967c94 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards a31debcfec 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards df66d0b2e7 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards b1369d2cee 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards c90e087657 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 2f8422c500 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 0728d175ba 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 1b87aff227 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 5a1a901e9f 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 4b3d075fb8 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 2d0aa2f079 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards e830529b3b 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards 80321aeea7 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 2831dda4c1 102: force: #1551: 1: Failure after gcc: 306 commits discards f77e74136d 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards fb245099e0 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards f32f52e1a9 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 2e5c857f38 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 74a00630db 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 7463a4c5d9 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1768a183e4 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2928b76cbb 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 1fa6474632 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards a43950e381 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 62ac08ab31 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards ef7c6a9f3b 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards dd97a1a3a3 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 5dfb6931d7 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards a19d6b1da7 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 59f8d73f28 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards e4f6822e54 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 77ecba4f11 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 89706d6337 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6bc49fe127 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 0fa15d499c 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 01090beebb 80: onsuccess: 7: Successful build after linux: 44 commits discards d32b0ba3a5 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards c24eaa66d7 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards f884ea7077 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 49ab0f27e6 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 192d492bdc 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 7854fd4fa8 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 90de574951 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 8d775714bf 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards aabe12511b 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 0888c92317 70: onsuccess: 7: Successful build after gcc: 4 commits discards ae101f2e4f 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards fe4170ff5e 68: onsuccess: 7: Successful build after linux: 6 commits discards a338fd9989 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards 0d8b3f0c2a 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards 286d825e8e 65: onsuccess: 7: Successful build after binutils: 3 commits discards f3af2a8704 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards fbb40b14c1 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 2938c17491 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 8ab93d104f 61: onsuccess: 4: Successful build after gcc: 5 commits discards 975ed19c02 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 88ebebefeb 59: force: 7: Successful build after gcc: 3 commits discards f4c4463a6e 58: onsuccess: 7: Successful build after glibc: 2 commits discards 78f0e8095f 57: onsuccess: 7: Successful build after gcc: 7 commits discards a12191cb08 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 364da07488 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 1716a17134 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards edb9ccd60c 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new e47554ec66 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 43c056860c 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 7242398605 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 22157db12c 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 06f3bfed4f 57: onsuccess: 7: Successful build after gcc: 7 commits new 6dba4437f8 58: onsuccess: 7: Successful build after glibc: 2 commits new 642a87b140 59: force: 7: Successful build after gcc: 3 commits new 8889209de5 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 5724cf5bd2 61: onsuccess: 4: Successful build after gcc: 5 commits new 1353e72aa0 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 30e3721045 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 2d1d369039 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new d7b68b61d4 65: onsuccess: 7: Successful build after binutils: 3 commits new d738de419a 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new d898094ca2 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new 1547c069b6 68: onsuccess: 7: Successful build after linux: 6 commits new 912fd64c4c 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 37b5b22787 70: onsuccess: 7: Successful build after gcc: 4 commits new 0203295f2a 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 02aadb216d 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 75a6ac00a4 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new dff83950a7 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 6b1124bda5 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 7b20421b16 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 35a44a3f07 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 633750aeeb 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new f463802dde 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new b71ef982ee 80: onsuccess: 7: Successful build after linux: 44 commits new 27137ac642 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 9f9469154f 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 74feb20704 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b724be04ac 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 31344fdc73 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new e2c166d34d 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 89b8261d4e 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new b7aec749ac 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 1233ac4b9e 89: onsuccess: 7: Success after gcc/glibc: 8 commits new ac55105442 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 623252821d 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 633533068e 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 852d51ba71 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new acb1982c28 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new df2f40cda1 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new d1a68a0974 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new d9ba8c0cba 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 21393194d0 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 37bda5fff6 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new b32c11dd98 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 1406b6a760 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 9a050f23ce 102: force: #1551: 1: Failure after gcc: 306 commits new c01cb9d52c 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 67ec2ceb67 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new f47d360b97 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 190f4158a6 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 8d25ddef82 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new d4785a4cee 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new bfdf43eb0b 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 89893892ab 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 0cde3dd95b 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new f065017ae0 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new d700c4026a 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new d0de182cbc 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 44928007a3 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 8f371d992f 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 8ef3abc5e8 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 6b45abaa27 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new ebf4d60975 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new 337ae95125 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 0788083ee8 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new c23dbd135e 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 67b9c78dd9 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new b1321f25ca 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new db871e5c98 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 98ca2d71d0 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 671958c438 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new d530175135 128: onsuccess: #1579: 7: Success after linux: 12 commits new 84cb3f644c 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new 91ffd0d840 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 99e04dc2b1 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new 567e5ea927 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 86c2758959 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new d86d38bade 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new d7aa2185f4 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new fec6057633 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new 58b3d02c0d 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 37cd6f0d19 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new 88e62445aa 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 5a2138b12e 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new a32a770e64 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new 564924c90b 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new 155d676b99 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new 2341dbe31b 144: onsuccess: #1595: 7: Success after glibc: 2 commits new fc128d8b78 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new 0f7fb94741 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new 904d7c1437 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new 465a495f48 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new a0e7ab4aa7 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new 3f202981d1 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] new 2842bc481f 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] new 274ae7a023 152: force: #1605: 7: Success after gcc: 9 commits new c7f27ffa12 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] new 004a49bcd3 154: onsuccess: #1607: 1: Success after gcc: 2 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (bebf3e43f8) \ 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 1616 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 30224 -> 30108 bytes 05-build_abe-stage1/console.log.xz | Bin 41460 -> 41044 bytes 12-check_regression/console.log.xz | Bin 3860 -> 2584 bytes 12-check_regression/jira-body.txt | 2 +- 12-check_regression/mail-body.txt | 26 +-- 12-check_regression/mail-subject.txt | 2 +- 12-check_regression/results.regressions | 6 - 12-check_regression/trigger-bisect | 2 - 12-check_regression/trigger-notify | 0 13-update_baseline/console.log | 66 +++--- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 342 -------------------------------- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 26 +-- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 6 - 24 files changed, 62 insertions(+), 447 deletions(-) delete mode 100644 12-check_regression/results.regressions delete mode 100644 12-check_regression/trigger-bisect delete mode 100644 12-check_regression/trigger-notify delete mode 100644 jenkins/jira-status.draft delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

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

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 ecf715a6b9 152: force: #1605: 7: Success after gcc: 9 commits discards 7d2715a2d5 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] discards ba83e55334 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] discards 1d550ee5d7 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards 2d73c8d584 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards 7eafc6ce19 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards 0f324bd7b1 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards 76f40c4768 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards badd8438ac 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 4739732891 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards dcdc816217 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards 37970bb206 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 0c0a74d8b4 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards dff2e0f40a 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards 6d014348b7 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards bb45bdab1b 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards d21efa685c 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards aab2a0f98f 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards 60f62c2568 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 173a982e88 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards 8055160880 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards 9ead425e96 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 1d13d39062 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 12baa81dca 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards d334768413 128: onsuccess: #1579: 7: Success after linux: 12 commits discards b002e6923e 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards b54f3e264d 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards a445c261c6 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards dd7657b641 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 75752b08cc 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards 570bc7cd61 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 64c31898f4 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards 050e8e1854 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards 821978ee16 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 2e7db72006 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards a65d6e1757 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 69812e5966 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 53ed9e0a46 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards 10ad8e8b82 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards 084317d864 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards 4bcf520082 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards d83633083e 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 59612f3bd1 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 8ec56cb2b2 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 18004e7597 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 84dbf98ba0 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 6ffc3ef12e 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 8c3bc9a513 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards 7d30484615 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards 253428bee1 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 74a5396d92 102: force: #1551: 1: Failure after gcc: 306 commits discards a3213487c3 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 2771b67c4a 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 816dc1c457 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards dd44c98133 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards dcf8d60475 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards ca4b96fe14 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards c6708a5d14 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1f1bcb970c 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 0d01ba0260 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 9a9da8711d 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 1ffae52e96 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards b1af6d390e 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 4edf3e6e02 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards ff7c7e62ea 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 56cff4681a 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 852dc1befd 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards ab24e77d5d 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 7ab0185e35 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 9a4a5f4d4d 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3c9dbabc39 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards c747ae398e 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7f157f4087 80: onsuccess: 7: Successful build after linux: 44 commits discards b15521f9ea 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 5c4292e276 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards d5785b3665 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5c9ee2bc5f 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards e383dc9892 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards bfd7ebcc38 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 0abca81c3e 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards beef71db7a 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ccc02d2fd3 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards de71d56118 70: onsuccess: 7: Successful build after gcc: 4 commits discards 9f3f9d7d44 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 065cfb416b 68: onsuccess: 7: Successful build after linux: 6 commits discards a18e8e3d5e 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards da91967893 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards 94f3eb6369 65: onsuccess: 7: Successful build after binutils: 3 commits discards eb777d4ac8 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards b5bb2c1b3f 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards df94b0d0e3 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards e44f03f3dd 61: onsuccess: 4: Successful build after gcc: 5 commits discards c25a3217c9 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards f41957fd70 59: force: 7: Successful build after gcc: 3 commits discards 60bc104969 58: onsuccess: 7: Successful build after glibc: 2 commits discards 8d692ad77a 57: onsuccess: 7: Successful build after gcc: 7 commits discards 3cdd5295a3 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 4ef90ada74 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 554e0c325b 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards c8422451f5 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 569db2fc61 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new 2cbc40fd72 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new edb9ccd60c 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 1716a17134 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 364da07488 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a12191cb08 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 78f0e8095f 57: onsuccess: 7: Successful build after gcc: 7 commits new f4c4463a6e 58: onsuccess: 7: Successful build after glibc: 2 commits new 88ebebefeb 59: force: 7: Successful build after gcc: 3 commits new 975ed19c02 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 8ab93d104f 61: onsuccess: 4: Successful build after gcc: 5 commits new 2938c17491 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new fbb40b14c1 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new f3af2a8704 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 286d825e8e 65: onsuccess: 7: Successful build after binutils: 3 commits new 0d8b3f0c2a 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new a338fd9989 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new fe4170ff5e 68: onsuccess: 7: Successful build after linux: 6 commits new ae101f2e4f 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 0888c92317 70: onsuccess: 7: Successful build after gcc: 4 commits new aabe12511b 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 8d775714bf 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 90de574951 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7854fd4fa8 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 192d492bdc 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 49ab0f27e6 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new f884ea7077 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c24eaa66d7 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new d32b0ba3a5 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 01090beebb 80: onsuccess: 7: Successful build after linux: 44 commits new 0fa15d499c 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6bc49fe127 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 89706d6337 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 77ecba4f11 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new e4f6822e54 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 59f8d73f28 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new a19d6b1da7 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 5dfb6931d7 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new dd97a1a3a3 89: onsuccess: 7: Success after gcc/glibc: 8 commits new ef7c6a9f3b 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 62ac08ab31 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new a43950e381 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 1fa6474632 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 2928b76cbb 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 1768a183e4 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 7463a4c5d9 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 74a00630db 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 2e5c857f38 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new f32f52e1a9 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new fb245099e0 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new f77e74136d 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 2831dda4c1 102: force: #1551: 1: Failure after gcc: 306 commits new 80321aeea7 103: onsuccess: #1552: 1: Success after gcc: 5 commits new e830529b3b 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 2d0aa2f079 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 4b3d075fb8 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 5a1a901e9f 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new 1b87aff227 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new 0728d175ba 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 2f8422c500 110: onsuccess: #1559: 7: Success after gcc: 4 commits new c90e087657 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new b1369d2cee 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new df66d0b2e7 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new a31debcfec 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 951e967c94 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 90696fe10d 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new c711fefa1a 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 87dc270594 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new 87b299e94d 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new 80dc671134 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 48caf50364 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 2deaa7835b 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 94609b40e2 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new 060ef40ad8 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new aa5267ab95 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 3336ba57a3 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new bbe18347d2 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new 0cfebf62d6 128: onsuccess: #1579: 7: Success after linux: 12 commits new 085d52e234 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new 5c98ad1f96 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 4e01175e2b 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new 50d5aea325 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new e9e5acfad3 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new 5bcf600492 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new 3278a84788 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new 4203bcf32b 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new 1e28f70a90 137: onsuccess: #1588: 7: Success after gcc: 5 commits new ce013099e6 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new af5d47d89c 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 7e0f7b0b44 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new 80a381a38f 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new b274c637b4 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new cf9a6a0507 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new adc3de6f64 144: onsuccess: #1595: 7: Success after glibc: 2 commits new 0a1d4f7471 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new 67814c8298 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new 2e8581914e 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new 50f369be5d 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new 7663cac513 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new c775b6f7a7 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] new 007d0453e7 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] new df3e0d3cd1 152: force: #1605: 7: Success after gcc: 9 commits new bebf3e43f8 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-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 (ecf715a6b9) \ 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 1636 -> 1616 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 30236 -> 30224 bytes 05-build_abe-stage1/console.log.xz | Bin 72220 -> 41460 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 0 bytes 07-build_abe-linux/console.log.xz | Bin 8748 -> 0 bytes 08-build_abe-glibc/console.log.xz | Bin 239556 -> 0 bytes 09-build_abe-stage2/console.log.xz | Bin 202600 -> 0 bytes 10-build_abe-gdb/console.log.xz | Bin 37664 -> 0 bytes 11-build_abe-qemu/console.log.xz | Bin 32424 -> 0 bytes 12-check_regression/console.log.xz | Bin 3116 -> 3860 bytes 12-check_regression/jira-body.txt | 2 +- 12-check_regression/mail-body.txt | 20 +- 12-check_regression/mail-subject.txt | 2 +- 12-check_regression/results.regressions | 6 + 12-check_regression/trigger-bisect | 2 + 12-check_regression/trigger-notify | 0 13-update_baseline/console.log | 64 ++--- dashboard/dashboard-generate.sh | 2 +- dashboard/squad/score/results-functional.json | 1 - git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 342 ++++++++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 20 +- mail/mail-subject.txt | 2 +- manifest.sh | 29 +-- results | 18 +- 31 files changed, 427 insertions(+), 96 deletions(-) delete mode 100644 06-clean_sysroot/console.log.xz delete mode 100644 07-build_abe-linux/console.log.xz delete mode 100644 08-build_abe-glibc/console.log.xz delete mode 100644 09-build_abe-stage2/console.log.xz delete mode 100644 10-build_abe-gdb/console.log.xz delete mode 100644 11-build_abe-qemu/console.log.xz create mode 100644 12-check_regression/results.regressions create mode 100644 12-check_regression/trigger-bisect create mode 100644 12-check_regression/trigger-notify delete mode 100644 dashboard/squad/score/results-functional.json create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/interesting-commits] branch master updated (4a9fcf4 -> 511dbd7)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from 4a9fcf4 Add entry b04208895fed34171eac6bafb60c90048eb1cb0c from https [...] new 511dbd7 Add entry 1214196da79aabbe5c14ed36e5a28012e141f04c from https [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/basepoints/gcc-13-3004-g1214196da79 | 1 + .../tcwg_gnu_cross_build/master-aarch64/build_url | 1 + .../tcwg_gnu_cross_build/master-aarch64/last_good | 1 + .../master-aarch64/summary.txt | 1 + .../tcwg_gnu_cross_build/status.txt | 78 ++++++++++++++++++++++ 5 files changed, 82 insertions(+) create mode 120000 gcc/basepoints/gcc-13-3004-g1214196da79 create mode 100644 gcc/sha1/1214196da79aabbe5c14ed36e5a28012e141f04c/tcwg_gnu_cros [...] create mode 100644 gcc/sha1/1214196da79aabbe5c14ed36e5a28012e141f04c/tcwg_gnu_cros [...] create mode 100644 gcc/sha1/1214196da79aabbe5c14ed36e5a28012e141f04c/tcwg_gnu_cros [...] create mode 100644 gcc/sha1/1214196da79aabbe5c14ed36e5a28012e141f04c/tcwg_gnu_cros [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

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

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 ee68299923 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] discards 692a41d4ab 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] discards e28184ae51 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards 41a39edda3 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards 8909ac7b91 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards a5ad82a442 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards d77060e6c4 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards 0154ea4689 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards a7b005c9b0 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards 9aa86bae33 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards 7009a7a28b 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 849f5388bc 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards d91cc228e5 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards 5fbffd9dbe 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards beb610b2e4 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards b95956b86e 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards ba0ee51b89 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards d2f21714ab 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 5017c91b22 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards 979ab643bf 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards 88665a430d 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards dffb6f758d 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 54410d9cb6 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards b2271cbace 128: onsuccess: #1579: 7: Success after linux: 12 commits discards dba3e196c0 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards ae644e93f6 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 9abd141a06 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 3d4ce51975 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 6288e2cce9 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards 9698537d32 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 583b0c649c 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards 84a06927bd 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards d732be2b5f 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 5fd789224c 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards 9db61768b4 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards c90af8913e 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 8dd3f38022 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards ba88e8714e 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards 8213365e01 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards 42dfeddcce 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards 8cad3c3879 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 9df72ebac7 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 64927a7fca 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards b07f0518d7 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 2e1b3d21f2 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 75f4a6566b 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards af7331b397 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards e65f9f8ff1 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards 6aa5d3bebf 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 02230fdd00 102: force: #1551: 1: Failure after gcc: 306 commits discards 8d0fa414ca 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 6ed84ffc2a 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 330ceda1fd 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards ef6ecaf861 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards a4184703ef 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards d3fa9867f8 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 8cca2314e3 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 30897d3979 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 2615b2c521 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards b9d83ed9f0 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards ba3bcd10b7 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards b24e5cc3b5 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards e2869a20ae 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 1f6b059bbe 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 232058de5a 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards bc6195a315 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 7b30354374 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards d7254bb482 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 145d5508d0 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 55a30c519c 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards c2caad1508 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d33cf4142f 80: onsuccess: 7: Successful build after linux: 44 commits discards 7b19e7100c 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 5638125268 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards 7b759549e3 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e28e6d3109 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards f74a2b6ef8 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 6a0955eb8c 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards bd67ad851e 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a149c01a47 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 76701ca976 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 58de55f17a 70: onsuccess: 7: Successful build after gcc: 4 commits discards 5ce5d5a068 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d55010b20a 68: onsuccess: 7: Successful build after linux: 6 commits discards 1fe834cd6b 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards 9fbf25df55 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards 27686d6861 65: onsuccess: 7: Successful build after binutils: 3 commits discards a1abc5f1e5 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 0b78cd01eb 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards b828b3452d 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 83f10cdfb0 61: onsuccess: 4: Successful build after gcc: 5 commits discards a57cb323d0 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 88db660b26 59: force: 7: Successful build after gcc: 3 commits discards 5f40222e1e 58: onsuccess: 7: Successful build after glibc: 2 commits discards 55a246c6e7 57: onsuccess: 7: Successful build after gcc: 7 commits discards c5d3576f53 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 98a20171fd 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 90fdb66513 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards 0e7c8b5f5b 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 9ec1c43462 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] discards 226302a3bf 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new d0eeba9f02 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 569db2fc61 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new c8422451f5 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 554e0c325b 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 4ef90ada74 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 3cdd5295a3 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8d692ad77a 57: onsuccess: 7: Successful build after gcc: 7 commits new 60bc104969 58: onsuccess: 7: Successful build after glibc: 2 commits new f41957fd70 59: force: 7: Successful build after gcc: 3 commits new c25a3217c9 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new e44f03f3dd 61: onsuccess: 4: Successful build after gcc: 5 commits new df94b0d0e3 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new b5bb2c1b3f 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new eb777d4ac8 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 94f3eb6369 65: onsuccess: 7: Successful build after binutils: 3 commits new da91967893 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new a18e8e3d5e 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new 065cfb416b 68: onsuccess: 7: Successful build after linux: 6 commits new 9f3f9d7d44 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new de71d56118 70: onsuccess: 7: Successful build after gcc: 4 commits new ccc02d2fd3 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new beef71db7a 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 0abca81c3e 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new bfd7ebcc38 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new e383dc9892 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 5c9ee2bc5f 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new d5785b3665 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5c4292e276 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new b15521f9ea 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 7f157f4087 80: onsuccess: 7: Successful build after linux: 44 commits new c747ae398e 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 3c9dbabc39 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 9a4a5f4d4d 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7ab0185e35 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new ab24e77d5d 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 852dc1befd 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 56cff4681a 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new ff7c7e62ea 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 4edf3e6e02 89: onsuccess: 7: Success after gcc/glibc: 8 commits new b1af6d390e 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 1ffae52e96 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 9a9da8711d 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 0d01ba0260 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 1f1bcb970c 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new c6708a5d14 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new ca4b96fe14 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new dcf8d60475 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new dd44c98133 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 816dc1c457 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 2771b67c4a 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new a3213487c3 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 74a5396d92 102: force: #1551: 1: Failure after gcc: 306 commits new 253428bee1 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 7d30484615 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 8c3bc9a513 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 6ffc3ef12e 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 84dbf98ba0 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new 18004e7597 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new 8ec56cb2b2 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 59612f3bd1 110: onsuccess: #1559: 7: Success after gcc: 4 commits new d83633083e 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new 4bcf520082 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 084317d864 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new 10ad8e8b82 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 53ed9e0a46 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 69812e5966 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new a65d6e1757 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 2e7db72006 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new 821978ee16 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new 050e8e1854 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 64c31898f4 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 570bc7cd61 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 75752b08cc 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new dd7657b641 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new a445c261c6 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new b54f3e264d 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new b002e6923e 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new d334768413 128: onsuccess: #1579: 7: Success after linux: 12 commits new 12baa81dca 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new 1d13d39062 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 9ead425e96 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new 8055160880 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 173a982e88 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new 60f62c2568 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new aab2a0f98f 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new d21efa685c 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new bb45bdab1b 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 6d014348b7 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new dff2e0f40a 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 0c0a74d8b4 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new 37970bb206 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new dcdc816217 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new 4739732891 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new badd8438ac 144: onsuccess: #1595: 7: Success after glibc: 2 commits new 76f40c4768 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new 0f324bd7b1 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new 7eafc6ce19 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new 2d73c8d584 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new 1d550ee5d7 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new ba83e55334 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] new 7d2715a2d5 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] new ecf715a6b9 152: force: #1605: 7: Success after gcc: 9 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 (ee68299923) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1688 -> 1636 bytes 02-prepare_abe/console.log.xz | Bin 2708 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30176 -> 30236 bytes 05-build_abe-stage1/console.log.xz | Bin 72928 -> 72220 bytes 07-build_abe-linux/console.log.xz | Bin 8780 -> 8748 bytes 08-build_abe-glibc/console.log.xz | Bin 239704 -> 239556 bytes 09-build_abe-stage2/console.log.xz | Bin 203112 -> 202600 bytes 10-build_abe-gdb/console.log.xz | Bin 37692 -> 37664 bytes 11-build_abe-qemu/console.log.xz | Bin 32092 -> 32424 bytes 12-check_regression/console.log.xz | Bin 2964 -> 3116 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +++++++------- 17 files changed, 50 insertions(+), 50 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[gcc] branch master updated (aa360fbf68b -> dd9c8f644f0)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from aa360fbf68b Install correct patch version. new f8cb417d6a4 c++: cast split_nonconstant_init return val to void new dd9c8f644f0 c++: loop through array CONSTRUCTOR The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/cp/cp-gimplify.cc | 19 ++++++++++++------- gcc/cp/init.cc | 6 +++++- 2 files changed, 17 insertions(+), 8 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/master-arm-check_bootstrap_lto updated (207726412c -> 7ece2b7732)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check_bootstrap/master-arm-check_bootstrap_lto in repository toolchain/ci/base-artifacts. from 207726412c 50: onsuccess: #476: 1: Success after binutils/gcc: 145 commits new 7ece2b7732 51: onsuccess: #477: 1: Success after binutils/gcc: 48 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 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 51756 -> 50828 bytes 04-build_abe-bootstrap_lto/console.log.xz | Bin 472268 -> 476244 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3852 bytes 06-build_abe-check_bootstrap_lto/console.log.xz | Bin 2776 -> 2504 bytes 07-check_regression/console.log.xz | Bin 10372 -> 6852 bytes 07-check_regression/extra-bisect-params | 1 - 07-check_regression/fails.sum | 17 - 07-check_regression/mail-body.txt | 22 +- 07-check_regression/results.compare | 72 +- 07-check_regression/results.compare2 | 1304 ++----- 07-check_regression/results.regressions | 80 - dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 24 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 80 - sumfiles/g++.log.xz | Bin 2871112 -> 2864728 bytes sumfiles/g++.sum | 265 +- sumfiles/gcc.log.xz | Bin 2478572 -> 2479352 bytes sumfiles/gcc.sum | 4579 ++++++++++++----------- sumfiles/gfortran.log.xz | Bin 948396 -> 956004 bytes sumfiles/gfortran.sum | 52 +- sumfiles/libatomic.log.xz | Bin 2316 -> 2308 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 211224 -> 212368 bytes sumfiles/libgomp.sum | 59 +- sumfiles/libitm.log.xz | Bin 2724 -> 2724 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 474020 -> 478416 bytes sumfiles/libstdc++.sum | 10 +- 35 files changed, 2845 insertions(+), 3760 deletions(-) delete mode 100644 07-check_regression/extra-bisect-params delete mode 100644 07-check_regression/fails.sum delete mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap updated (1accc201d4 -> 23f2057058)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap in repository toolchain/ci/base-artifacts. discards 1accc201d4 153: onsuccess: #1558: 2: Success after binutils/gcc: 12 commits discards b0c218e930 152: onsuccess: #1557: 2: Success after binutils/gcc: 12 commits discards 4044ef4232 151: onsuccess: #1556: 2: Success after binutils: 12 commits discards 3469a6504e 150: onsuccess: #1555: 2: Success after binutils/gcc: 14 commits discards 22fead4c78 149: onsuccess: #1554: 2: Success after binutils/gcc: 15 commits discards d2babd268f 148: onsuccess: #1553: 2: Success after binutils/gcc: 32 commits discards ad0d5dcfd4 147: onsuccess: #1552: 1: Success after gcc: 2 commits discards ba4326250a 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 commits discards b2c41c7150 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits discards 4da874f64a 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits discards 019ffcbd4f 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits discards 225075337b 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits discards 38d5e85f8c 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits discards 9381a6bbcd 140: onsuccess: #1545: 1: Success after gcc: 7 commits discards 8fd1511094 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits discards 3fa226465d 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits discards 3d685efa9a 137: onsuccess: #1542: 1: Success after gcc: 4 commits discards cf7540b3e2 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] discards fe194e32f8 135: force: #1540: 2: Success after gcc: 23 commits discards 17e7754c46 134: onsuccess: #1538: 2: Success after binutils: 2 commits discards 41688778d4 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits discards b8826d5a05 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits discards 2413b840d8 131: onsuccess: #1534: 2: Success after gcc: 9 commits discards d5d8a816fa 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] discards 3f1ccfb266 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits discards 4d29891a60 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 98a9416f84 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards f2d9f138ad 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards 00b573d901 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards 20597d0239 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards a5f176ac99 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards b2710b2d7d 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards 8386876bed 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards 2d377e9bd0 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards e8293499cc 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards 154c565037 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards e5e4f04735 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards 2c3dfe88bc 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards c3cb10f936 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards 721a5939aa 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards f036090153 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards eca1d56b6b 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards 244a7b49ae 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards d95c73721c 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards 8ed5f46910 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards 982367baa2 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 775620757f 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards fb224c3478 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards cecddcdf77 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards ba4051d2a4 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards 74792a8c53 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 05356a434b 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards faae41afce 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards d8be3624c2 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards eb0d1f6e00 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards 104fce4b0d 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards a9296e9004 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 0e9c1f1e60 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards b3cb737c6a 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards c8129d3800 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards 223d9131a1 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards d59a682fe7 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards 8b83c81603 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards c9a0fce1e8 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards c0b6c28814 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards 0da6ce16a2 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards ab8c266b4c 87: onsuccess: 2: Success after gcc: 4 commits discards a5e16226ad 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards f24549a450 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 4c822c984e 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 48371cd834 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 157dd1fdd6 82: onsuccess: 1: Successful build after gcc: 3 commits discards 634c60f848 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 43181953aa 80: force: 2: Successful build after gcc: 14 commits discards 5510389adb 79: onsuccess: 2: Successful build after binutils: 5 commits discards 99f93fb946 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards eeba58a0e7 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 196acf4c59 76: onsuccess: 2: Successful build after gcc: 12 commits discards 5b0460d012 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards ba6ebe401d 74: onsuccess: 2: Successful build after baseline build: no [...] discards 6bd051f9b6 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards a66f97585e 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 1d56124696 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 611ff8dbef 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 8dd1e7e962 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 55635dc1bd 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 2193957bb0 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards fa7d6fd22e 66: onsuccess: 2: Successful build after gcc: 9 commits discards e7bcb69bb4 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 62cf896a19 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards d77f88fb1f 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 62e2d6433d 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 9f8415fd20 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards 9e6a415d76 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards f112307b8b 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 13c5e1b428 58: force: 2: Successful build after gcc: 6 commits discards 3eeb6983a6 57: onsuccess: 2: Successful build after binutils: gdb: new [...] discards 1390b8f573 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards d9587c2904 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards c393b81a57 54: onsuccess: 2: Successful build after gcc: 5 commits discards cf3064dc2c 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 4027e4ddc3 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 929a18ed99 54: onsuccess: 2: Successful build after gcc: 5 commits new ed17a87506 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 16c9771a5c 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 02bf9e6071 57: onsuccess: 2: Successful build after binutils: gdb: new [...] new 41006219f8 58: force: 2: Successful build after gcc: 6 commits new a53d1b8f72 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new bbc3e91a57 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 6c33333c1a 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new 7268261618 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 004961dae8 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 0d6858c4f0 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 220003bfec 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 598e011ab3 66: onsuccess: 2: Successful build after gcc: 9 commits new 3459bfa63e 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 2c9d24b7d4 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new db2820a0fa 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 9166aaa704 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 3385c0b1f4 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 2520377bb6 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 29091184a2 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 91e13f495b 74: onsuccess: 2: Successful build after baseline build: no [...] new c86cb12cc2 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 341840d558 76: onsuccess: 2: Successful build after gcc: 12 commits new 332f857372 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 19d05c000e 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new ed11a9e2bf 79: onsuccess: 2: Successful build after binutils: 5 commits new 27e767e9cc 80: force: 2: Successful build after gcc: 14 commits new c1b3bc6566 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 164625ff6a 82: onsuccess: 1: Successful build after gcc: 3 commits new 0b0165d8b9 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new 52e26f5c20 84: onsuccess: 2: Success after binutils/gcc: 15 commits new 9918b388dd 85: onsuccess: 2: Success after binutils/gcc: 25 commits new 5184ebf890 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 14576ed93e 87: onsuccess: 2: Success after gcc: 4 commits new 5474ab83b0 88: onsuccess: 2: Success after binutils/gcc: 25 commits new b6cc64dcdf 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 2ccfe898d4 90: onsuccess: 2: Success after binutils/gcc: 16 commits new b436fabe7f 91: onsuccess: 2: Success after binutils/gcc: 7 commits new 69c7c1506f 92: onsuccess: 2: Success after binutils/gcc: 9 commits new 2342b624a9 93: onsuccess: 2: Success after binutils/gcc: 3 commits new a0205da39b 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new 82eab80823 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new ded6864892 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 6727d53f8b 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new 207e471758 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new b51368f9d0 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new d57f1748e5 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new dcd2b46ca3 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new 004e2ce697 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new c2efa6dd70 103: onsuccess: #1504: 2: Success after gcc: 2 commits new 49a176e0ec 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new 570c199bb4 105: onsuccess: #1506: 2: Success after gcc: 2 commits new e7abde070f 106: onsuccess: #1507: 2: Success after gcc: 2 commits new ab9266530e 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new 953c4c2371 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new d00608783d 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new b5e54ccf81 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new 5a1299aaf4 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new a8c4f779c7 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new ee1a18996a 113: onsuccess: #1514: 2: Success after gcc: 5 commits new ed2d83e92c 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new 9bcf6789c0 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new d36d11d6d5 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new 4cd4a7e9c5 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 7d24a0ac0a 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new d5e035ba35 119: onsuccess: #1520: 2: Success after binutils: 8 commits new a75af294b9 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new 39120d659f 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new 41bbc496cf 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new e3e0215c79 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new b3b1562b57 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new 1cd377319f 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new d84e77de63 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new 6850683691 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new b742e42e0e 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new a1358b8265 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits new 29a2321798 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] new ecc62bfc1d 131: onsuccess: #1534: 2: Success after gcc: 9 commits new 4758431bae 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits new 4c9e847a93 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits new 1d5a263090 134: onsuccess: #1538: 2: Success after binutils: 2 commits new ada4680054 135: force: #1540: 2: Success after gcc: 23 commits new 1d135542dd 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] new 02d90f8355 137: onsuccess: #1542: 1: Success after gcc: 4 commits new 3ad993c3d3 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits new cdeac792ca 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits new 6b2ce4d224 140: onsuccess: #1545: 1: Success after gcc: 7 commits new 5cfee4c854 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits new 5b54659d9d 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits new 28af8cb32a 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits new a419b430ae 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits new 24510866a6 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits new 2f6b454464 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 commits new b92ef0d8ab 147: onsuccess: #1552: 1: Success after gcc: 2 commits new d0354a8b88 148: onsuccess: #1553: 2: Success after binutils/gcc: 32 commits new 04d1899904 149: onsuccess: #1554: 2: Success after binutils/gcc: 15 commits new e0153931bb 150: onsuccess: #1555: 2: Success after binutils/gcc: 14 commits new 8496422919 151: onsuccess: #1556: 2: Success after binutils: 12 commits new d80674d200 152: onsuccess: #1557: 2: Success after binutils/gcc: 12 commits new b1a3fb2d77 153: onsuccess: #1558: 2: Success after binutils/gcc: 12 commits new 23f2057058 154: onsuccess: #1559: 2: Success after binutils/gcc: 12 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 (1accc201d4) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1688 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2704 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 50708 -> 51068 bytes 05-build_abe-bootstrap/console.log.xz | Bin 464288 -> 465072 bytes 06-check_regression/console.log.xz | Bin 2884 -> 2780 bytes 07-update_baseline/console.log | 36 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- manifest.sh | 18 ++++++++--------- 10 files changed, 30 insertions(+), 30 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (5ff743c5b3 -> be22469ea3)

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 5ff743c5b3 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards c4f36cb77c 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards b89ad94942 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 7f1fcb1aa4 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 45da3cd9b8 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 7d001a576d 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 5d927d71c6 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 30313766d4 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 054b1d2182 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 2a722f4fca 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 5f5063c716 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards f2b648fb9d 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards bb829aac99 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 0095cbf25f 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards d05b4eaca9 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 793b025dc5 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards c9da380fd6 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 91eec19290 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 1403e301ba 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards e57bff34f6 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards c8163e6e46 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 6b0db4273c 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 6dca6aaacb 128: onsuccess: #1723: 1: Success after linux: 12 commits discards de9111dd1a 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards efdc0c5110 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 1ab787969e 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 5d8d8d8b1d 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 0176eb0cab 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 7b1e4c33bb 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards b153967597 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards f6499222e1 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards e9d6b24a7c 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards a6e086d4f8 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 7c7e41e0c9 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 99e70b99d1 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 73096b6c9a 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 65c40aea67 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 7a4c8af082 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 1639a573d7 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards ab2848b45c 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 07dc331bec 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 92af2765eb 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 6cd8175017 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 6fdbc67ca5 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards c0fd022f11 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards ecda3331fd 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards e51dce9c94 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards f292704a0f 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 9db737ff43 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 2eb5875d9e 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards cff1b9c2f6 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards d2b827105f 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 33b39abf66 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards d37f0b758c 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards c3fb8eaba5 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 193935ddb9 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards c48b015212 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 88c1b85c0e 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards f47b979cbc 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards de72ecea99 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards b372f347f1 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 79154a537c 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2e25d0c796 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards ab1b248fdb 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 63da97653a 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 26bd683491 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 90e0996b88 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 8fe15a0c0c 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 2933b505b0 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards e6bd18213c 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 6fc45e3aa3 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 54d07d776e 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards d5ff1c9d97 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 6ddc1c5fc3 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards aa4a4f9eda 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 2d15305894 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards afc0e77016 74: onsuccess: 1: Successful build after linux: 44 commits discards b2b20b42ad 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards b5aaf16e02 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 59b01a7130 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 6ceecb7518 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 6958d48eca 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards cc1bb61150 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8b9fb74467 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 564cd633ed 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 642609f3c6 65: onsuccess: 1: Successful build after gcc: 4 commits discards 51b2bf706c 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bddac867c7 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dc85d10525 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 835d31095d 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards e074ff7971 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 51e36cc1bd 59: onsuccess: 1: Successful build after glibc: 2 commits discards a0ab07e12f 58: onsuccess: 1: Successful build after binutils: 2 commits discards 818bba84e3 57: onsuccess: 1: Successful build after gcc: 7 commits discards bb06c17286 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2fffe0681f 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0c6fd883a5 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 59c29b850a 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 00099e56ea 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 6c4851d9c5 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b34a4ff93c 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new eb025feb3e 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fb27844bcd 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b2958b3c3b 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 7e834a6fef 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 0eed999457 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new e2c3245533 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 451f7f1b15 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 700be9be19 57: onsuccess: 1: Successful build after gcc: 7 commits new fd5454f717 58: onsuccess: 1: Successful build after binutils: 2 commits new d3aa5d91b0 59: onsuccess: 1: Successful build after glibc: 2 commits new 245aa6b28c 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new c8a9710061 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 315e609fe8 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 4c4acb4f4b 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new af278c90d8 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2009a6fc70 65: onsuccess: 1: Successful build after gcc: 4 commits new 02dda90490 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 64f4be014b 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a53320e710 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ed8c9f3ea1 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 5ef792ad56 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new d7a51559de 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 74a81fb194 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 21215796ef 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 53fc1bc285 74: onsuccess: 1: Successful build after linux: 44 commits new 986e545050 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b2cbfd1263 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 451d7dbe39 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 76f5b070ee 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 200f42b170 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 17d6de449a 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 5ddbbff27e 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 6d77c265c9 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 3364880c6f 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new c7d9223c89 84: onsuccess: 1: Success after gcc/glibc: 9 commits new adf05ba43b 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new e54f133e71 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new e8288fc131 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new e3479b08ed 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 556a3b0663 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 184ab19a71 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 3ba5601b0f 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 528a801d5b 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new c2600f27af 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 5ac05d11c3 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new f0a73b0ad5 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 533a61f689 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 22aeca399b 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 29429d71f1 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 37a4d92771 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 7174c5f6f4 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new df67eef8a0 101: onsuccess: #1693: 1: Success after glibc: 14 commits new b2c4262913 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 14ac9a099b 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 39adf8cc24 104: onsuccess: #1697: 1: Success after gcc: 4 commits new c3bef21ba6 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 602fae82cc 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 9a22133d13 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new cf590efcdd 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 6283e6ced7 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 95bff9c995 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 25823e2216 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new ffba6f748f 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new e0066dd6f1 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 54fb90f967 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 4f30537b55 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 0153a9a2cb 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new d3a23cb3e4 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new a981689307 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 144cc3eded 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 219f6065dd 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 86664e8516 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 4960880e1f 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 8fa8ffe3e3 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 2792f465d8 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 2a7855faf8 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 578bf3a719 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 5903740896 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new e350d9987a 128: onsuccess: #1723: 1: Success after linux: 12 commits new bb62a55664 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 1e01781b70 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 826e20d11e 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 76a32cb3b2 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new d239fdee81 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new ebaaad2962 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 6a8f680e3e 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 949a6c62a1 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 46488db0ab 137: onsuccess: #1736: 1: Success after gcc: 5 commits new a64a1e272a 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new eadf6c8eed 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new ccd92d4aa9 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 2014e9cd8c 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 87653b3735 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new c2def89621 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 21a74ea47c 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 9e8b035568 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new f3242af5c9 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 180c584964 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new b447b3fc1d 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new 909886b2ce 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 93c9a8b712 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new be22469ea3 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (5ff743c5b3) \ 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 1688 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30156 -> 30040 bytes 04-build_abe-stage1/console.log.xz | Bin 91196 -> 91148 bytes 06-build_abe-linux/console.log.xz | Bin 8676 -> 8804 bytes 07-build_abe-glibc/console.log.xz | Bin 233600 -> 234236 bytes 08-build_abe-stage2/console.log.xz | Bin 225056 -> 223816 bytes 09-build_abe-gdb/console.log.xz | Bin 37416 -> 37436 bytes 10-build_abe-qemu/console.log.xz | Bin 31468 -> 31292 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3904 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3148 -> 3172 bytes 13-check_regression/console.log.xz | Bin 7736 -> 5316 bytes 13-check_regression/fails.sum | 3 +- 13-check_regression/mail-body.txt | 60 +- 13-check_regression/results.compare | 21 +- 13-check_regression/results.compare2 | 217 +-- 13-check_regression/results.regressions | 21 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 62 +- mail/mail-subject.txt | 2 +- manifest.sh | 29 +- results | 21 +- sumfiles/g++.log.xz | Bin 2658932 -> 2667116 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 2203868 -> 2229916 bytes sumfiles/gcc.sum | 2538 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 887140 -> 885780 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201608 -> 201444 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429464 -> 425100 bytes sumfiles/libstdc++.sum | 6 +- 39 files changed, 1451 insertions(+), 1627 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022