Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[binutils-gdb] branch master updated (137c886e9a6 -> 511f4ff4d9b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 137c886e9a6 [gdb/c++] Print destructor the same for gcc and clang new 511f4ff4d9b [gdb/testsuite] Add aranges to gdb.dwarf2/dw2-dir-file-name.exp 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: gdb/testsuite/gdb.dwarf2/dw2-dir-file-name.exp | 16 ++++++++++++++++ gdb/testsuite/lib/dwarf.exp | 15 +++++++++++++-- 2 files changed, 29 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-norov-allmodconfig updated (e4dac61969 -> 31da2d521a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-norov-allmodconfig in repository toolchain/ci/base-artifacts. from e4dac61969 13: onsuccess: #52: 23330: Success after qemu: 118 commits new 31da2d521a 14: force: #53: 23330: Success after llvm: 27 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 1908 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 30424 -> 30364 bytes 04-build_kernel_llvm/console.log.xz | Bin 65896 -> 63728 bytes 05-build_abe-qemu/console.log.xz | Bin 31224 -> 31376 bytes 06-build_linux/console.log.xz | Bin 3776 -> 3740 bytes 08-check_regression/console.log.xz | Bin 2968 -> 3008 bytes 09-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 ++++++++-------- 14 files changed, 14 insertions(+), 14 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[binutils-gdb] branch master updated (4eeb0013059 -> 137c886e9a6)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 4eeb0013059 PR29626, Segfault when disassembling ARM code new 137c886e9a6 [gdb/c++] Print destructor the same for gcc and clang 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: gdb/c-typeprint.c | 55 +++++++++++++--------- gdb/testsuite/gdb.base/ptype-offsets.exp | 2 +- .../default-args.c => gdb.cp/print-method-args.cc} | 29 ++++++------ ...pointer-to-member.exp => print-method-args.exp} | 14 +++++- gdb/testsuite/gdb.cp/templates.exp | 4 +- 5 files changed, 61 insertions(+), 43 deletions(-) copy gdb/testsuite/{gdb.base/default-args.c => gdb.cp/print-method-args.cc} (80%) copy gdb/testsuite/gdb.cp/{pointer-to-member.exp => print-method-args.exp} (78%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

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

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 a96ca07908 49: onsuccess: #474: 1: Success after binutils: 10 commits new 207726412c 50: onsuccess: #476: 1: Success after binutils/gcc: 145 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1676 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 50336 -> 51756 bytes 04-build_abe-bootstrap_lto/console.log.xz | Bin 471704 -> 472268 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3848 bytes 06-build_abe-check_bootstrap_lto/console.log.xz | Bin 2428 -> 2776 bytes 07-check_regression/console.log.xz | Bin 4476 -> 10372 bytes 07-check_regression/extra-bisect-params | 1 + 07-check_regression/fails.sum | 17 + 07-check_regression/mail-body.txt | 80 + 07-check_regression/results.compare | 79 +- 07-check_regression/results.compare2 | 1116 +++++- 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 | 82 +- mail/mail-subject.txt | 2 +- manifest.sh | 19 +- results | 80 + sumfiles/g++.log.xz | Bin 2830608 -> 2871112 bytes sumfiles/g++.sum | 899 ++++- sumfiles/gcc.log.xz | Bin 2529032 -> 2478572 bytes sumfiles/gcc.sum | 4819 ++++++++++++----------- sumfiles/gfortran.log.xz | Bin 941872 -> 948396 bytes sumfiles/gfortran.sum | 48 +- sumfiles/libatomic.log.xz | Bin 2308 -> 2316 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 212084 -> 211224 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2724 -> 2724 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 478444 -> 474020 bytes sumfiles/libstdc++.sum | 38 +- 35 files changed, 4872 insertions(+), 2522 deletions(-) create mode 100644 07-check_regression/extra-bisect-params create mode 100644 07-check_regression/fails.sum create mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap updated (293e98471d -> 17deb53cb4)

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 293e98471d 149: onsuccess: #1554: 2: Success after binutils/gcc: 15 commits discards 34700b9623 148: onsuccess: #1553: 2: Success after binutils/gcc: 32 commits discards b8dc0faf20 147: onsuccess: #1552: 1: Success after gcc: 2 commits discards 2ab4f043da 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 commits discards 0bf3a905e1 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits discards 4bce1da6e5 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits discards 02a1d44aaf 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits discards 126e8e0c02 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits discards 26801a9346 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits discards 426d425817 140: onsuccess: #1545: 1: Success after gcc: 7 commits discards bbcf959879 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits discards f54c7bc532 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits discards acdd4245ae 137: onsuccess: #1542: 1: Success after gcc: 4 commits discards 2217821d77 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] discards 6af13c1458 135: force: #1540: 2: Success after gcc: 23 commits discards 9cbeaece1a 134: onsuccess: #1538: 2: Success after binutils: 2 commits discards f7ab998b34 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits discards 897026ac45 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits discards 59959927e0 131: onsuccess: #1534: 2: Success after gcc: 9 commits discards d4c6e071cf 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] discards 6ef3bc430d 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits discards 3bd37aba78 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 6981e5dc9b 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards 6ec40a9ff0 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards adc4289f7f 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards 7d22b99d9c 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards f36d6128e6 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards f772b85b2b 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards 067cb3bc07 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards 84b184ab79 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards 07ab09a399 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards 5b835f2126 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards a756d38d2c 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards 9cd3f9a662 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards f42f28236a 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards 90de2f7c33 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 2bc9a1434c 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards 9dde6ef66d 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards cfb3045d1d 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards e0e80e47f9 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards 83d6c3b508 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards dcb62bf474 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 4697b1cab9 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards f6a1d43feb 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards a5ab771bd0 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards 27b81732a4 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards b375bbf148 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 85ccaf4b2e 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards 198a6ff8cc 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards 72c45e8a09 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards f675a156cc 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards 00b3f9c70b 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards 32b4ec2429 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 17d6eee51f 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 4ca9447e03 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards d7dd38af4f 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards 83aacfa4d7 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards 96f781fc32 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards bfefa79438 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards a69de884ee 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards a6e33be5aa 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards 3832982bfd 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards 3da6d7ecc6 87: onsuccess: 2: Success after gcc: 4 commits discards c427e26576 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards 6540a9870d 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 0ecc71c823 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 6fe15ef61d 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 6c3f99d77d 82: onsuccess: 1: Successful build after gcc: 3 commits discards 966ca251f4 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards d65f4b4dce 80: force: 2: Successful build after gcc: 14 commits discards 2a67580d4b 79: onsuccess: 2: Successful build after binutils: 5 commits discards 1d4a67b6a9 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards 9a2c6c0768 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 0a52c8410a 76: onsuccess: 2: Successful build after gcc: 12 commits discards 7be4bc7fd8 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 18314016da 74: onsuccess: 2: Successful build after baseline build: no [...] discards ef39141967 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards c89094b390 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards d0958dceaa 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 9782f6f8dc 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 361c651ef1 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards c85a4260bc 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards a75a07965f 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards ec51019957 66: onsuccess: 2: Successful build after gcc: 9 commits discards 219f361c39 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 8f2fa9fc0a 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 6440f3cf69 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 8083ad3b0c 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 1a47b1b90d 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards e5c29006ff 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards 5e46cf17af 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 42f0b27ec1 58: force: 2: Successful build after gcc: 6 commits discards a846513350 57: onsuccess: 2: Successful build after binutils: gdb: new [...] discards 4587ee29fe 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 2f00a6eadd 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards f3a7758e76 54: onsuccess: 2: Successful build after gcc: 5 commits discards b174897b5c 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 8efb1d3f14 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 01ae057eef 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards a1b8a9d1a7 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 06e640cede 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new c4147a49f2 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 7f424285f9 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new de245deaee 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new df46b68501 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 2d9e0c414b 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 0f10d0f244 54: onsuccess: 2: Successful build after gcc: 5 commits new 721ce6f1fd 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ad64475155 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 9bba58b683 57: onsuccess: 2: Successful build after binutils: gdb: new [...] new d24a03b16f 58: force: 2: Successful build after gcc: 6 commits new 2a8c44d08a 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 7990f37167 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new a2fe53562d 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new cd9f49e79f 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 05b43268cb 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 052d47de80 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new d8d96cf41c 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 97a5efb56d 66: onsuccess: 2: Successful build after gcc: 9 commits new c9a9471db4 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new c18891829e 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new a05e387d71 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ec6a49dec2 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 2ae5444e41 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new f4a84c5be9 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 86e7dce738 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 0141bedaf1 74: onsuccess: 2: Successful build after baseline build: no [...] new c508978f03 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 719a63e554 76: onsuccess: 2: Successful build after gcc: 12 commits new d06f556d79 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 933168b14f 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new 5a6bca379b 79: onsuccess: 2: Successful build after binutils: 5 commits new 2391baf0bc 80: force: 2: Successful build after gcc: 14 commits new 74d337cd9d 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 70d3b23a46 82: onsuccess: 1: Successful build after gcc: 3 commits new b1caf687fe 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new 8863fdbcb1 84: onsuccess: 2: Success after binutils/gcc: 15 commits new ba61d30ce1 85: onsuccess: 2: Success after binutils/gcc: 25 commits new ff1c0b14e9 86: onsuccess: 2: Success after binutils/gcc: 10 commits new bf1df7e18b 87: onsuccess: 2: Success after gcc: 4 commits new 3e53fe032c 88: onsuccess: 2: Success after binutils/gcc: 25 commits new 61a8f23cd0 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 850305e23e 90: onsuccess: 2: Success after binutils/gcc: 16 commits new c55a46dc8f 91: onsuccess: 2: Success after binutils/gcc: 7 commits new df38b910fa 92: onsuccess: 2: Success after binutils/gcc: 9 commits new ccf2d33a33 93: onsuccess: 2: Success after binutils/gcc: 3 commits new 00b4087f8c 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new 69b9fd6160 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new ebee8b945a 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 6b67d2125d 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new 3c85c3e92c 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new f863da5568 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new 68d721ee0b 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new d918ee0ba4 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new e526b575f5 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new 44fc691f56 103: onsuccess: #1504: 2: Success after gcc: 2 commits new 57f3ed282f 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new a61d9c8e0e 105: onsuccess: #1506: 2: Success after gcc: 2 commits new 2f4b720822 106: onsuccess: #1507: 2: Success after gcc: 2 commits new d6b0298ffc 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new ab30daa6e4 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 7a6cc9c544 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new 93030972d9 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new 83fbdf0da8 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new 293eda3808 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new dd190e453f 113: onsuccess: #1514: 2: Success after gcc: 5 commits new 9f074d9bb3 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new 372db574d6 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new d19ef0900f 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new 38baac91a7 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new a54c4452c9 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new e214106beb 119: onsuccess: #1520: 2: Success after binutils: 8 commits new c45155ac38 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new b3a262a185 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new 446f8aa8a6 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new 9f1310133b 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new b6010185dd 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new 7ec0e55c37 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new e8c9e52be9 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new 7e71e1f8a0 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new 6a7e4f9513 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 7b32af005c 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits new 21724e871e 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] new 5f04d05877 131: onsuccess: #1534: 2: Success after gcc: 9 commits new 8c8ff5d21b 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits new acc14a14ba 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits new 2f37e80066 134: onsuccess: #1538: 2: Success after binutils: 2 commits new 559f7ea836 135: force: #1540: 2: Success after gcc: 23 commits new cbd7b96aab 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] new 287e0d29d9 137: onsuccess: #1542: 1: Success after gcc: 4 commits new e2d51cec50 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits new 771ed04d75 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits new 24537f6195 140: onsuccess: #1545: 1: Success after gcc: 7 commits new 9deb39e870 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits new 428e8819fb 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits new 8f0425dcab 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits new 2d85afbb00 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits new 7eda011e7c 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits new 7d16d81b6d 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 commits new 031f4340a1 147: onsuccess: #1552: 1: Success after gcc: 2 commits new 263749bc9b 148: onsuccess: #1553: 2: Success after binutils/gcc: 32 commits new bf54e98382 149: onsuccess: #1554: 2: Success after binutils/gcc: 15 commits new 17deb53cb4 150: onsuccess: #1555: 2: Success after binutils/gcc: 14 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 (293e98471d) \ 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 1692 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2704 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 50528 -> 51464 bytes 05-build_abe-bootstrap/console.log.xz | Bin 463384 -> 464432 bytes 06-check_regression/console.log.xz | Bin 2960 -> 3040 bytes 07-update_baseline/console.log | 40 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++-------- 13 files changed, 35 insertions(+), 35 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-norov-allmodconfig updated (69f3791fa1 -> e4dac61969)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-norov-allmodconfig in repository toolchain/ci/base-artifacts. from 69f3791fa1 12: onsuccess: #50: 23330: Success after binutils: 24 commits new e4dac61969 13: onsuccess: #52: 23330: Success after qemu: 118 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 1708 -> 1908 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30188 -> 30424 bytes 04-build_kernel_llvm/console.log.xz | Bin 64876 -> 65896 bytes 05-build_abe-qemu/console.log.xz | Bin 31600 -> 31224 bytes 06-build_linux/console.log.xz | Bin 3804 -> 3776 bytes 08-check_regression/console.log.xz | Bin 2984 -> 2968 bytes dashboard/dashboard-generate.sh | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 13 files changed, 14 insertions(+), 14 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

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

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap in repository toolchain/ci/base-artifacts. discards e2df2325a5 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits discards db33f9a08b 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits discards 2c5cab1aed 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] discards 1bf4835291 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits discards 704a4654fd 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits discards a90bbef6f7 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards 9dab17a7dc 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] discards d61500f37c 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards b209ee9feb 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards 058717bb5b 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards fe429ac68c 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards 1ee692072b 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards e4070f3925 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards f8f17c7afc 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards 3c2f592864 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards 0f7c0c3c5c 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards b7a413f575 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards 3e120b1959 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards e0a319038c 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards c6617cf137 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards 712bcfbd73 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards 3f12e5af96 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards aab460dffb 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 9e01213964 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards edbede8ab4 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards 8a147f8b16 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards ac9ef75b6d 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 6715c165c0 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 476455da13 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 7d524cd6e2 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards ba0f469dd0 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards f1d0d76322 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards 1cf971cd9f 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards 9cf6f7fea0 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 005af6feee 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 5584aa5011 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards f14a01bb45 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards 0741e2e988 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards ccf7534114 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards da97157abb 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards 6556d37fa4 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards eeb2cf9a38 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 5799181ab1 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards 5a9cb72da5 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards 02465e095b 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards cecb35ac25 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards b1b2703e78 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 2a6bb15751 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards a0c028c5b9 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards 9f8747e81b 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards f8660f567c 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 80c6c74124 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards c32d83cec0 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards a9bccf7ddc 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards f79fb68897 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards bfd1d0fb3a 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 7d5054890b 88: onsuccess: 1: Success after gcc: 20 commits discards df19746e4d 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards accd0785d6 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards 8a85dcd14d 85: onsuccess: 2: Success after binutils: 4 commits discards dc9cc1f6d9 84: onsuccess: 2: Success after gcc: 9 commits discards 0199180fb4 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 1eb4c35a78 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards f8e152c383 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 899055e5a5 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 9693732298 79: onsuccess: 1: Successful build after gcc: 3 commits discards 79b07110c1 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 727249cbb3 77: force: 2: Successful build after gcc: 32 commits discards 4788067e50 76: onsuccess: 2: Successful build after binutils: 10 commits discards cfb9eab28b 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 74e9f7ed5c 74: onsuccess: 2: Successful build after gcc: 13 commits discards cea596ad04 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 7bd44acb3a 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 8caa253f83 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards e539379257 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 9d548d8d96 69: onsuccess: 2: Successful build after baseline build: no [...] discards 719f732a11 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 6d3b1be02f 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 3a1068f8ba 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 470450dbed 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 26b3176a6e 64: onsuccess: 2: Successful build after gcc: 7 commits discards 08f1b2aa74 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 5b862e1697 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 5b56c692e3 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 0ef4bea712 60: onsuccess: 1: Successful build after gcc: 15 commits discards d318d8d8cb 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards f4dc731767 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards 22d20b86f0 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 8eab788108 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards e1e28d31c8 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 1f01494fb3 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards ce96fa0662 53: onsuccess: 2: Successful build after gcc: 5 commits discards 3242b09525 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 5386f73c8d 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 1366f69ddb 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 06930f8297 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 3dbec75355 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 4e480f3e44 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards d295b4ae19 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 8a3d6d1b4b 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards 1532d99ed4 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 793160b1bd 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 2b2206d960 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 260ec7a92b 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new ff0912c2a1 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new e12e3a725b 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 84561344fa 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 9d0c9f628d 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new e2decf2a47 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new dfecd8923c 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 7fcb06767f 53: onsuccess: 2: Successful build after gcc: 5 commits new c5b79d3e1f 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 0c90719d17 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 3fe6ee3fed 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 88974f8cdd 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 3491d11504 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new e40c8722d1 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 9f7dcf475e 60: onsuccess: 1: Successful build after gcc: 15 commits new 761a5c2e21 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 20193d9eb3 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 4071193f10 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new fef1eec60e 64: onsuccess: 2: Successful build after gcc: 7 commits new 2a0e370bfc 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 0fa6e22222 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 4838897891 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 99c88e39fd 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new b945a13795 69: onsuccess: 2: Successful build after baseline build: no [...] new 25bc48f474 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 6c1a1d049b 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new c2b2333226 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 4a4b2328b2 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 7064970dfc 74: onsuccess: 2: Successful build after gcc: 13 commits new d8a28c84d5 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new f66058c573 76: onsuccess: 2: Successful build after binutils: 10 commits new 27bf4e3807 77: force: 2: Successful build after gcc: 32 commits new 6014bb7b52 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 6bb0442cdc 79: onsuccess: 1: Successful build after gcc: 3 commits new 3bf37d1513 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 9dc4346a48 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 75d3e5c689 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 650978e086 83: onsuccess: 2: Success after binutils/gcc: 7 commits new aced4fe28d 84: onsuccess: 2: Success after gcc: 9 commits new 0fd94856bd 85: onsuccess: 2: Success after binutils: 4 commits new 82334e2d36 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new cb9057c648 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new 3d954f0392 88: onsuccess: 1: Success after gcc: 20 commits new 5831752139 89: onsuccess: 2: Success after binutils/gcc: 39 commits new b0b6ce2046 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 665c173c91 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 5804509491 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new bd73fde2d3 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new f63ea40157 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new 05cfd5e444 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 16eb657fc7 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 52e8cd9a81 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 6d3420b29f 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 2838dfbbbd 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new c92de0b930 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new def80afca2 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new e4ee43cd7f 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new d05e8a8224 103: onsuccess: #1524: 2: Success after gcc: 2 commits new f733575570 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 4482436bb5 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 098bcb9779 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 348001789c 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new d8f3026462 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new ce6d3c11db 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new ce0d248d8e 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 8ffa91d587 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 727f208817 112: onsuccess: #1533: 2: Success after gcc: 5 commits new c51d7e28f0 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new e47cd33ad3 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new df743dd232 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 8c1704f7e3 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new ae2ada42af 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new faabd3ae6a 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new cbd2bd8824 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new 922c98ece5 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 6342fe2b97 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new 4188278a02 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new c3d05f9993 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 6048185c13 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new 94249b1886 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new eeaf749e7a 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new 188eee554a 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new e75fadff5b 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new df16dfe3cd 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new c109565232 130: onsuccess: #1554: 2: Success after gcc: 9 commits new f1cb6e95c6 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new 5c97707174 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new c48597dd2d 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new 5436d596d8 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new 97700724af 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new ccdce5b604 136: onsuccess: #1561: 2: Success after binutils: 3 commits new 3469b863e3 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new e9c59fc262 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] new 1dd37e71a8 139: onsuccess: #1566: 1: Success after gcc: 5 commits new ce2863acf3 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits new 7fdc0b3050 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits new e77c00a23b 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] new c2a67111d2 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits new 1d0db5d782 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits new 5606742690 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 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 (e2df2325a5) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1696 -> 1616 bytes 02-prepare_abe/console.log.xz | Bin 2708 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 37924 -> 38060 bytes 05-build_abe-bootstrap/console.log.xz | Bin 270884 -> 272228 bytes 06-check_regression/console.log.xz | Bin 2888 -> 3036 bytes 07-update_baseline/console.log | 36 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 ++++++++--------- 13 files changed, 33 insertions(+), 33 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

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

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 7996c53f8c 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 739c705dbb 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 5e6ce1894f 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards cbad4cfdf3 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 6ccdc449c1 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 6587909b08 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards a60cdeb593 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards b93b64adc8 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards fede1f1a11 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 6dc03c21d0 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 16009aeeec 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards e7d8b7fd80 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards de1d046ec3 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 1f78420c3b 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 6644b68643 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 46e94c8beb 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 15da311af1 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards c64610416e 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards c2376a2aa0 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 7c397071aa 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards c0219e1f1b 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 909245781e 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards d6065a8ff5 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards a701706b56 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 6a3740697b 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 80a5db4817 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards ccfb5700ce 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 2c5fd9bb5d 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 53627e4b34 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 9e98615099 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 76522a1c0b 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards f9f31138c8 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 045e7b7fb8 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards adeeff7331 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 7222ddfb0d 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 8212db00b8 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards fe47d65218 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 30a36b8540 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 8760599bd1 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards ca7fcbdea8 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 907732a504 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 19bdf680a5 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 264aa95cd9 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards db22686902 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards f992c6572c 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards d628d5127a 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 23f1aef86f 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 226cec3118 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards bb282dce99 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards ec659cdee8 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards e2b38ff740 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards cc510d185a 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 78f7bf282f 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards a2fd076206 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 808990ea28 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 0dc4d64e6b 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards ab30ed6397 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards ebf56773e8 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards d655b06a79 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 8a65161d44 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 3a79cedd21 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 036d4d5364 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards fe2d0d83b6 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards fc19e06693 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 271d055af0 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 8e8c1d71d4 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards c6298a144f 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 95b18aacee 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 9ce174d9f2 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards cbfd730abe 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ae15d47665 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards aea051dd27 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 157b000514 74: onsuccess: 1: Successful build after linux: 44 commits discards e2a4a23607 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards eef49b0ea7 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 142516c4d7 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 8cfac98ff2 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 6f93a8d30c 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards d3cc8d7dcc 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 428c30c822 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ddc33ed6a8 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3650eddc40 65: onsuccess: 1: Successful build after gcc: 4 commits discards 129adc366a 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 55283022a5 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1eae0ffe7c 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 8c9722a4ad 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 3fc39d8472 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards b80a79b835 59: onsuccess: 1: Successful build after glibc: 2 commits discards 902919300f 58: onsuccess: 1: Successful build after binutils: 2 commits discards 8f04b89c3e 57: onsuccess: 1: Successful build after gcc: 7 commits discards 68d266ba97 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c00abce9ce 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 839cb53b5d 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 13a2a06b7b 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 01e61b996c 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 9599ed7bec 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 063fb4f889 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a3cde4271c 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 362c3425d0 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards dde93d3159 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cd7c0358bb 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 91ca2f5b68 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 3010bda873 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 08bb27195c 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 50419f56f5 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2108ac35b2 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bd4737eab6 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 62e3e38940 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new edd36246de 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 0531b34a39 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 45a8c35d78 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2fba437416 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4504a5d491 57: onsuccess: 1: Successful build after gcc: 7 commits new cfa78e3f0d 58: onsuccess: 1: Successful build after binutils: 2 commits new 472e50c11f 59: onsuccess: 1: Successful build after glibc: 2 commits new 2eb13c4887 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new e78e9c869f 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 3abdb8b078 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new f0f37f1557 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ce88bf9163 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9a15510758 65: onsuccess: 1: Successful build after gcc: 4 commits new dcaa6d8185 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new bc0630a88b 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 150a6b0a0e 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 179e926b6b 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 19cd1b5966 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new dc6c91118a 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 84ca4c0489 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7222fb6191 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 1c5bb0c3b8 74: onsuccess: 1: Successful build after linux: 44 commits new 2f9e476809 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 15f279974e 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new e7d50687ec 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5e7bab3c95 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2fa0f36625 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new c869ca023d 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new ac6ac3e0c8 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 2ab5f7bfe0 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new bd45238dcf 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 5fad5a2d39 84: onsuccess: 1: Success after gcc/glibc: 9 commits new ba8d7aaf69 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new b3e2bdceba 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 89d4295089 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 2af8bf8a20 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new f424cb1249 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 41424d79b5 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 7cb8d33dec 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new d4a5d9b33e 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 98c92eeefe 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new cdbe3ca52c 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new ba8dc622d3 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 11e749815b 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 7bd818a9a1 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 4357bc2c00 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new fa39ebdc74 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new bce34a74bf 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new e7372ac4cf 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 6a190a5c77 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 00a3d15faa 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 6e38b16556 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 9ec49e605c 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new b8b9830ddc 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 3ce2a181d8 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new d0ab181c7e 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 829786e21f 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 3c1841be1b 110: onsuccess: #1703: 1: Success after gcc: 6 commits new e7fba326bf 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 95c76b2b10 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new ed8bb9ecdd 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new b882bf8dfd 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new a4d5662b2a 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 69bedf934e 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 9661acff43 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 1d93f05c60 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new d5bceed6b3 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new ac7d577305 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new cd3984760d 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new e4a565b4b6 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 97c7b954bf 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 39f03e09b1 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new ed8d9c139c 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 5592b86198 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new ec48df4b0c 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new e7d3a46864 128: onsuccess: #1723: 1: Success after linux: 12 commits new 6c28f0b41c 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 339164b8aa 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 3cacbb311e 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 32835372e2 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 32c715c6b4 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 10638ef600 134: onsuccess: #1730: 1: Success after binutils: 2 commits new de9aad1186 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 78fb0aa2e8 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 2c92c18364 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 9c2dc5a22c 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 9a612caa9d 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 10dfc2d8cf 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 756d0ee525 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 669554203e 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new fdd4cb18ad 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new a4a5a708bc 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 616028e5cf 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 874198af85 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 6e01019417 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (7996c53f8c) \ 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 1680 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30516 -> 29912 bytes 04-build_abe-stage1/console.log.xz | Bin 90712 -> 90360 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9304 -> 8432 bytes 07-build_abe-glibc/console.log.xz | Bin 233952 -> 233124 bytes 08-build_abe-stage2/console.log.xz | Bin 223188 -> 223648 bytes 09-build_abe-gdb/console.log.xz | Bin 37624 -> 37240 bytes 10-build_abe-qemu/console.log.xz | Bin 31424 -> 31424 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3844 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2732 -> 2428 bytes 13-check_regression/console.log.xz | Bin 7968 -> 6528 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 13 - 13-check_regression/mail-body.txt | 69 +- 13-check_regression/results.compare | 46 +- 13-check_regression/results.compare2 | 242 +-- 13-check_regression/results.regressions | 47 - 14-update_baseline/console.log | 42 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 71 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 47 - sumfiles/g++.log.xz | Bin 2686552 -> 2671680 bytes sumfiles/g++.sum | 133 +- sumfiles/gcc.log.xz | Bin 2197536 -> 2236828 bytes sumfiles/gcc.sum | 2636 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 892680 -> 889400 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201096 -> 201272 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 432276 -> 433956 bytes sumfiles/libstdc++.sum | 10 +- 44 files changed, 1635 insertions(+), 1842 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[dejagnu] branch PR58065 created (now 3554566)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch PR58065 in repository dejagnu. at 3554566 Add initial mockvfs support for internal unit tests This branch includes the following new commits: new 369c52e Allow internal unit test names to contain forward slash new 3554566 Add initial mockvfs support for internal unit tests 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. -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

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

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-arm in repository toolchain/ci/base-artifacts. discards 6a0c8c6863 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] discards 5d7d3ae495 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards 8fe99d549b 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 0d9197f93b 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards 6f7e38ab08 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards 2d1e96b14e 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards 5b7c5a62fa 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards 7a8f878d1b 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards 74e161138c 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards a03b36444e 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards 1931309914 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards 08e6b96583 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards 9cca03e509 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards 0e2486eab7 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards 709a46a2c4 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 0d7fffa7d9 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards 4256df1dcb 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 076dfd5472 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards df4e278bd4 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 7b1d8b15c0 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards e8123c44a5 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards 3ed8d9a4c3 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 9a75e9059d 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards d7e0e28325 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 7fb3453c06 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 64db71a4ed 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards bae1252d24 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 89f1825736 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards b4d48a8d3f 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards e45a9ccc18 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 9c0822fb0c 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 956860dfb8 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards a4ac7028c2 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards b75131d5bc 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 3a439d2f84 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 10fde3257c 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards abf47d809c 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards ca1e2762be 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 97a63a66c9 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 4e2957400c 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 2102b5bc85 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards ea841b8750 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 64025fa4b4 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 00e57e46db 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 8dd99a1326 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 35195acd46 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 2cd246ceb0 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 11c8f2e08f 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards a323258e3d 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 92f603987b 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 8fa4929724 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 38976bdc5e 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 13edd0ccb4 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 6967f39b46 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards feaf1ae7e8 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 927dc72d09 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards 9f901f685e 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 6679cfece0 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 6a6338b50b 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 933db73a4e 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards e50ba34e39 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 3c1792c5ae 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards bb376421b6 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 047d49b869 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards f70138a08d 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 7c675aa576 85: onsuccess: 7: Success after gcc: 9 commits discards 28e9aaa5aa 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 20f75d5df0 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 6b1e447491 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 2f711d8e99 81: onsuccess: 7: Successful build after gcc: 2 commits discards 181f07fd79 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards f0c24de5ee 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards e66943f687 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 04d5c29079 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 2db091681c 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ff603f16ce 75: onsuccess: 7: Successful build after linux: 44 commits discards f11df7affb 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards bddf0f3852 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e7121a894a 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards f0e99b5512 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 51c9ef4933 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 04c9bf381e 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards a94c9c32a7 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6e348a1845 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 52c71eca12 66: onsuccess: 7: Successful build after gcc: 3 commits discards 11cbac398c 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c64443559d 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 29e03c624d 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 91c34a2184 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards a6e464fcdc 61: onsuccess: 4: Successful build after gcc: 15 commits discards d0c124760f 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 15be51bdd1 59: force: 7: Successful build after gcc: 2 commits discards c268477658 58: onsuccess: 7: Successful build after glibc: 2 commits discards ed7e6d26da 57: onsuccess: 7: Successful build after gcc: 7 commits discards 275a729692 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 8fb95c4bb5 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 4314935b62 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards e0753d7c7f 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 3a408d0f25 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 4d6625b041 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards b0011699ae 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ea630f4f91 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ed9f7ef606 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 23e4eb8e22 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 348b02b5f7 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new a2689a5106 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 87245fab0f 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d673ba3de3 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a1bbc89dc3 57: onsuccess: 7: Successful build after gcc: 7 commits new 3eb3575647 58: onsuccess: 7: Successful build after glibc: 2 commits new c3f25e4080 59: force: 7: Successful build after gcc: 2 commits new 4517f85246 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new dd6b533038 61: onsuccess: 4: Successful build after gcc: 15 commits new c649b5e796 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 78d32c6860 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new d0f71eee44 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 752bc64b77 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 071286c748 66: onsuccess: 7: Successful build after gcc: 3 commits new 7a6274f57f 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new f6e4980580 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8fbe4fd5a4 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 612150d64f 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 4f1244bef6 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 3b5f482208 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 0b4a7cba49 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new cf86b8afcb 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new b791f72426 75: onsuccess: 7: Successful build after linux: 44 commits new 0bff996869 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 129bb9d1ac 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new e365ab41d6 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d2de4a818e 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 764a6f9e0c 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 637ef1b726 81: onsuccess: 7: Successful build after gcc: 2 commits new 3490cd9367 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new ea29796de2 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 77e6aa9761 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 1beca5249f 85: onsuccess: 7: Success after gcc: 9 commits new 71b42155ca 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new b60e2a85f4 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new ff336f44ab 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 70fdaea349 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new cbf2cfa2eb 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 1147af57ae 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 81daaf781c 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new e245eeeefe 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new 63d0166a89 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 70a72154cc 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 313eb45d67 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 9479995f26 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 567d7a7523 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 3700ce9033 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 53619b0645 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new fc406e0a91 101: onsuccess: #1609: 7: Success after binutils: 78 commits new ccd7181430 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 0b360e7955 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 7b35eadeed 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 92f69f3bb1 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 7df35a1d91 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 35cd2fde42 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 92544e9ed4 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new 1f0f371d02 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 230f7f0f44 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new 945aef3259 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 62a54f5ae5 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 427257a9db 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 3ae2aca247 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new bf70145148 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 507a8357a8 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new d4b8fc96c6 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 3d3162f928 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new d0b2218d0b 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 9e4ea125c4 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 8885f40142 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new a6fbff5833 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 0abd87ce11 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 20f8ad2e43 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 12730ddab9 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new 0d3a6cf395 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new 9e34cc893c 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 444d0348bc 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new f64e283479 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 7689fed9bd 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new b55ac87687 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 4e7982367a 132: onsuccess: #1645: 7: Success after linux: 23 commits new 86acfeadc5 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new 236d0c0863 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new 00ea279b63 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new 723df76037 136: onsuccess: #1650: 7: Success after binutils: 2 commits new acf4ad0eb8 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new c183e943a1 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new 2cf00b3679 139: onsuccess: #1654: 1: Success after gcc: 11 commits new aef2249820 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new 03412e55b1 141: onsuccess: #1656: 7: Success after gcc: 7 commits new f2a06fe3c1 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 2d459bfb1d 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new 164c88faf1 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new f17219a16b 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new 6d299b2b27 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new b1d963aa8e 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new ac7b92ccdb 148: onsuccess: #1663: 7: Success after glibc: 2 commits new 9479146d57 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new 2747382562 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] new 06a2d295df 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (6a0c8c6863) \ 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 1708 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 30384 -> 30108 bytes 05-build_abe-stage1/console.log.xz | Bin 90568 -> 90616 bytes 07-build_abe-linux/console.log.xz | Bin 9308 -> 8448 bytes 08-build_abe-glibc/console.log.xz | Bin 234216 -> 233792 bytes 09-build_abe-stage2/console.log.xz | Bin 224120 -> 223688 bytes 10-build_abe-gdb/console.log.xz | Bin 37680 -> 37116 bytes 11-build_abe-qemu/console.log.xz | Bin 31404 -> 31548 bytes 12-check_regression/console.log.xz | Bin 4540 -> 4048 bytes 13-update_baseline/console.log | 62 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++++++++++----------- 20 files changed, 58 insertions(+), 58 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

← Newer
1
...
9
10
11
12
13
14
15
...
469
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022