Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-next-allyesconfig updated (6da60f8c832 -> 14b28bd4e68)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-next-allyesconfig in repository toolchain/ci/base-artifacts. from 6da60f8c832 31: onsuccess: #553: 33: Success after binutils/gcc/linux/q [...] new 14b28bd4e68 32: onsuccess: #554: 33: Success after binutils/gcc/linux/q [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1704 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 32012 -> 32096 bytes 04-build_abe-stage1/console.log.xz | Bin 72904 -> 74332 bytes 05-build_abe-qemu/console.log.xz | Bin 30772 -> 31252 bytes 06-build_linux/console.log.xz | Bin 3404 -> 3460 bytes 08-check_regression/console.log.xz | Bin 4372 -> 4456 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 16 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-stable-allyesconfig updated (fa4dd901307 -> 5c524ccc05e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-stable-allyesconfig in repository toolchain/ci/base-artifacts. from fa4dd901307 29: onsuccess: #395: 20882: Success after binutils/gcc/linu [...] new 5c524ccc05e 30: onsuccess: #396: 20882: Success after binutils/gcc/qemu [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1696 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 30120 -> 30336 bytes 04-build_abe-stage1/console.log.xz | Bin 87104 -> 86940 bytes 05-build_abe-qemu/console.log.xz | Bin 30412 -> 31876 bytes 06-build_linux/console.log.xz | Bin 3844 -> 3912 bytes 08-check_regression/console.log.xz | Bin 4352 -> 3856 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 15 files changed, 21 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-mainline-allyesconfig updated (5f15b14a9d4 -> 0b00fcfd5d9)

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-release-arm-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from 5f15b14a9d4 31: onsuccess: #466: 21020: Success after binutils/llvm/qem [...] new 0b00fcfd5d9 32: force: #468: 21020: Success after linux: 185 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 1712 -> 1944 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 30584 -> 30696 bytes 04-build_kernel_llvm/console.log.xz | Bin 65492 -> 64912 bytes 05-build_abe-qemu/console.log.xz | Bin 30072 -> 30892 bytes 06-build_linux/console.log.xz | Bin 4928 -> 4748 bytes 08-check_regression/console.log.xz | Bin 3672 -> 2980 bytes 09-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +++++++++++------------- 14 files changed, 17 insertions(+), 19 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-aarch64 updated (7a5ff5dc1c4 -> ea74a5f72a1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards 7a5ff5dc1c4 131: force: #552: 4: Failure after basepoints/gcc-13-4492-g [...] discards 6a4854e0b87 130: force: #551: 6: Success after gcc: 10 commits discards 114af001f48 129: onsuccess: #548: 6: Success after binutils: 8 commits discards 78b8d343ce7 128: onsuccess: #546: 6: Success after binutils/gcc/linux/g [...] discards da6a597ab4f 127: onsuccess: #545: 6: Success after binutils/gcc/linux/g [...] discards b8829ed9adc 126: onsuccess: #544: 6: Success after binutils/gcc/linux/g [...] discards acc51b84877 125: onsuccess: #543: 6: Success after binutils/gcc/linux/g [...] discards 43df11f8f75 124: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] discards 1a294a36835 123: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] discards e51da1d06a5 122: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] discards 182330f32c4 121: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] discards 12332345559 120: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] discards 30f22ca50d1 119: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] discards 2b9656abb9a 118: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] discards d4f771f8ea0 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 [...] discards 7bb2a610d81 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/g [...] discards f510dd048e2 115: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] discards bab839c7a76 114: onsuccess: #532: 6: Success after binutils/gcc/linux/g [...] discards 2155ae9febf 113: onsuccess: #531: 6: Success after binutils/gcc/linux/g [...] discards a2b1bcf9568 112: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] discards b83035748be 111: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] discards 5672fcebb84 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 [...] discards 138c3c3ef7f 109: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] discards 15cec543219 108: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] discards f64de83d14a 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits discards e21c1478af0 106: onsuccess: #524: 1: Success after gcc: 11 commits discards 241f1c10d20 105: force: #523: 1: Failure after basepoints/gcc-13-3918-g [...] discards 2164582d297 104: force: #522: 6: Success after gcc: 24 commits discards c0962631ab0 103: onsuccess: #520: 6: Success after binutils: 10 commits discards 6e4007f9de2 102: onsuccess: #518: 6: Success after binutils/gcc/linux/g [...] discards 90e7d90f96f 101: onsuccess: #517: 6: Success after binutils/gcc/linux/g [...] discards 35d6d384d03 100: onsuccess: #516: 6: Success after binutils/gcc/linux/g [...] discards 840958ff998 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gl [...] discards 2956ed727de 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gd [...] discards 508e91405b3 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gd [...] discards 053e0c40bcd 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] discards d4f2a110d55 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gl [...] discards e6127c91777 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] discards 6046f89352f 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] discards 08d91577350 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] discards 734b35e95a2 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gl [...] discards 1a999024722 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gd [...] discards 3ea569c8ee4 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gl [...] discards f6ea1a29234 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gl [...] discards 2122f9a5791 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gl [...] discards adc4dbfef83 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gl [...] discards 4775028c1cc 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gl [...] discards 071fcfe9414 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gd [...] discards 987c0e571a4 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gd [...] discards c6e6c707e40 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gd [...] discards cac777969f1 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gl [...] discards f4cb5d4593f 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gd [...] discards acdc0efb59e 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gl [...] discards 3b890f7d6c6 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gd [...] discards 9683d73290f 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gl [...] discards f962b0419a1 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gd [...] discards 9945aa6f84a 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gl [...] discards 0ffa208e1d9 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gl [...] discards 34f936c201e 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gl [...] discards 10142aebe53 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gd [...] discards 261bc7c9fef 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gl [...] discards b4602de78b1 70: onsuccess: #486: 5: Success after gdb: 7 commits discards ff481568a00 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-g [...] discards 62e51652d14 68: force: #484: 6: Success after gdb: 6 commits discards 2bd0416891a 67: onsuccess: #483: 6: Success after linux: 384 commits discards 7cbf1c76fea 66: onsuccess: #482: 6: Success after glibc: 2 commits discards 61ccb78218b 65: onsuccess: #480: 6: Success after gcc: 12 commits discards 40d066d6475 64: onsuccess: #479: 6: Success after binutils: 14 commits discards 291d3d30805 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gl [...] discards 00f4502d624 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gl [...] discards 86ea9530fb6 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gl [...] discards 7f464befbde 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gl [...] discards db889892718 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gl [...] discards 59e40f74a7d 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gl [...] discards b9d9795343f 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gd [...] discards 85cd66712d4 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gl [...] discards f62489b6927 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gl [...] discards 5865b4f293c 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gl [...] discards 23ac25865a5 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gl [...] discards 731e17cb8ac 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits discards ecafa049665 51: onsuccess: #465: 1: Success after gcc: 10 commits discards abc7df0afb8 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb [...] discards 84973bed37e 49: force: #463: 6: Success after gcc: 18 commits discards 9421347e391 48: onsuccess: #461: 6: Success after binutils: 10 commits discards 182bf1626be 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gd [...] discards 32ec89a39f6 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gd [...] discards 09eef24e78e 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gl [...] discards 303a858b19b 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gl [...] discards c8130bac4d7 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gl [...] discards 18f43c9da5f 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gl [...] discards 625953c2bdd 41: onsuccess: #453: 6: Success after binutils/gcc/glibc/gd [...] discards b4c5c1ed823 40: onsuccess: #452: 6: Success after binutils/gcc/linux/gl [...] discards 3770aeab827 39: onsuccess: #451: 6: Success after binutils/gcc/glibc/gd [...] discards 6cba24d2264 38: onsuccess: #450: 6: Success after binutils/gcc/linux/gl [...] discards 0085d5fc0d1 37: onsuccess: #449: 6: Success after binutils/gcc/glibc/gd [...] discards 0c3ad60bf88 36: onsuccess: #448: 6: Success after binutils/gcc/glibc/gd [...] discards 65d9a47fb50 35: onsuccess: #447: 6: Success after binutils/gcc/linux/gl [...] discards 13fc103fc15 34: onsuccess: #446: 6: Success after binutils/gcc/linux/gl [...] discards ffa3a910d65 33: onsuccess: #445: 6: Success after binutils/gcc/linux/gd [...] discards 7c6714ffef5 32: onsuccess: #444: 6: Success after binutils/gcc/linux/gl [...] discards d0a915184f9 31: onsuccess: #443: 6: Success after binutils/gcc/linux/gl [...] new d3581b55640 31: onsuccess: #443: 6: Success after binutils/gcc/linux/gl [...] new 2c90da2a4de 32: onsuccess: #444: 6: Success after binutils/gcc/linux/gl [...] new 072dffadb39 33: onsuccess: #445: 6: Success after binutils/gcc/linux/gd [...] new 058f61f4fd5 34: onsuccess: #446: 6: Success after binutils/gcc/linux/gl [...] new 5645ee2e651 35: onsuccess: #447: 6: Success after binutils/gcc/linux/gl [...] new 3b791abf032 36: onsuccess: #448: 6: Success after binutils/gcc/glibc/gd [...] new 2b388c3574c 37: onsuccess: #449: 6: Success after binutils/gcc/glibc/gd [...] new 4a0efa90226 38: onsuccess: #450: 6: Success after binutils/gcc/linux/gl [...] new 2fbfaf5f7e7 39: onsuccess: #451: 6: Success after binutils/gcc/glibc/gd [...] new 61dd2936db2 40: onsuccess: #452: 6: Success after binutils/gcc/linux/gl [...] new b499af9bfbb 41: onsuccess: #453: 6: Success after binutils/gcc/glibc/gd [...] new d05259e16fd 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gl [...] new d26a97ba29d 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gl [...] new a90b4d0900a 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gl [...] new 5290a9a59c2 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gl [...] new 440073d351e 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gd [...] new 88b83eaac21 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gd [...] new 50e7fd0e486 48: onsuccess: #461: 6: Success after binutils: 10 commits new 44c33f2c389 49: force: #463: 6: Success after gcc: 18 commits new b293b197af6 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb [...] new e6e533517bf 51: onsuccess: #465: 1: Success after gcc: 10 commits new fbdc071d4d7 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits new 1983960d876 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gl [...] new 65f649e5baf 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gl [...] new 26559041ad7 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gl [...] new c3dde71dcdc 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gl [...] new fa5954aacec 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gd [...] new ce7a1dda202 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gl [...] new 9f27075dc3d 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gl [...] new 1a9472f0814 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gl [...] new c7e6707ca75 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gl [...] new abf39af6d34 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gl [...] new 9597e5c1860 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gl [...] new cd3e251db2e 64: onsuccess: #479: 6: Success after binutils: 14 commits new a7600d1ccab 65: onsuccess: #480: 6: Success after gcc: 12 commits new e4db7b09bad 66: onsuccess: #482: 6: Success after glibc: 2 commits new 3021fda5c07 67: onsuccess: #483: 6: Success after linux: 384 commits new 777314d1c42 68: force: #484: 6: Success after gdb: 6 commits new ed42b8ccfb7 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-g [...] new d2d1c212ed4 70: onsuccess: #486: 5: Success after gdb: 7 commits new 568ba842fcb 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gl [...] new 88ebdef3b92 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gd [...] new 1ac4fbce60b 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gl [...] new e5308b6cab3 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gl [...] new 6254e0e3f2b 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gl [...] new a2b15a4ccd2 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gd [...] new 6cfda650f6e 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gl [...] new 92971a1b375 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gd [...] new 6568b409500 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gl [...] new 91b83192568 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gd [...] new 1e000b3ed26 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gl [...] new 05bc7323752 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gd [...] new 771bf57942d 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gd [...] new 413826d50d7 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gd [...] new fb5190470e2 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gl [...] new a6665ed270d 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gl [...] new 49d6babb8b0 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gl [...] new aaba28acd4c 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gl [...] new f1d6b1a44d4 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gl [...] new 721b0fb359f 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gd [...] new d59776c1f70 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gl [...] new 03251bbb4bc 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] new 6157c724de9 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] new 51e062c7531 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] new dd5da2fb33e 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gl [...] new 9fe55f064b6 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] new 2178ee7d941 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gd [...] new fece1713805 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gd [...] new 5b2852455fb 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gl [...] new 38c74219bf6 100: onsuccess: #516: 6: Success after binutils/gcc/linux/g [...] new fae1050ed56 101: onsuccess: #517: 6: Success after binutils/gcc/linux/g [...] new 00cbe87ee3c 102: onsuccess: #518: 6: Success after binutils/gcc/linux/g [...] new f490eec7821 103: onsuccess: #520: 6: Success after binutils: 10 commits new daadf81ae69 104: force: #522: 6: Success after gcc: 24 commits new e69cb7a616d 105: force: #523: 1: Failure after basepoints/gcc-13-3918-g [...] new 0fcf4ff578e 106: onsuccess: #524: 1: Success after gcc: 11 commits new 8bb2646c87a 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits new 311dd6d6904 108: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] new ee1066e066e 109: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] new 5a82bd39f7b 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 [...] new a4b56a3e3f9 111: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] new 8a5eb3fbbe8 112: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] new 4e45c265fb6 113: onsuccess: #531: 6: Success after binutils/gcc/linux/g [...] new 7306caa42c4 114: onsuccess: #532: 6: Success after binutils/gcc/linux/g [...] new 9178269485d 115: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] new 2d06523f77e 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/g [...] new 55c809b34f3 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 [...] new 14e7f510142 118: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] new 194297e36f5 119: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] new 82d39c3c006 120: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] new eb2d20a8616 121: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] new ed91ad08586 122: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] new d14265fed6c 123: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] new 608b75bddec 124: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] new 193ebbf716b 125: onsuccess: #543: 6: Success after binutils/gcc/linux/g [...] new de55aaab1da 126: onsuccess: #544: 6: Success after binutils/gcc/linux/g [...] new ef1af5e02e7 127: onsuccess: #545: 6: Success after binutils/gcc/linux/g [...] new b8bad1aac75 128: onsuccess: #546: 6: Success after binutils/gcc/linux/g [...] new adaf2ee94df 129: onsuccess: #548: 6: Success after binutils: 8 commits new 399404a7d11 130: force: #551: 6: Success after gcc: 10 commits new c757632ad4f 131: force: #552: 4: Failure after basepoints/gcc-13-4492-g [...] new ea74a5f72a1 132: onsuccess: #553: 4: Success after basepoints/gcc-13-44 [...] 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 (7a5ff5dc1c4) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1720 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2780 bytes 04-build_abe-binutils/console.log.xz | Bin 40144 -> 40456 bytes 05-build_abe-gcc/console.log.xz | Bin 216680 -> 217252 bytes 07-build_abe-linux/console.log.xz | Bin 8812 -> 8852 bytes 08-build_abe-glibc/console.log.xz | Bin 175588 -> 175588 bytes 10-check_regression/console.log.xz | Bin 3672 -> 2780 bytes 10-check_regression/jira-body.txt | 2 +- 10-check_regression/mail-body.txt | 28 ++-- 10-check_regression/mail-subject.txt | 2 +- 10-check_regression/results.regressions | 11 -- 10-check_regression/trigger-bisect | 2 - 10-check_regression/trigger-notify | 0 11-update_baseline/console.log | 66 ++++---- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 284 -------------------------------- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 11 -- 26 files changed, 72 insertions(+), 393 deletions(-) delete mode 100644 10-check_regression/results.regressions delete mode 100644 10-check_regression/trigger-bisect delete mode 100644 10-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.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-aarch64 updated (3e5d37a8c0b -> 7a5ff5dc1c4)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards 3e5d37a8c0b 130: force: #551: 6: Success after gcc: 10 commits discards 6f90d179ade 129: onsuccess: #548: 6: Success after binutils: 8 commits discards 70459bc8675 128: onsuccess: #546: 6: Success after binutils/gcc/linux/g [...] discards 7022f3a68e1 127: onsuccess: #545: 6: Success after binutils/gcc/linux/g [...] discards 236fdf55183 126: onsuccess: #544: 6: Success after binutils/gcc/linux/g [...] discards ef37f630392 125: onsuccess: #543: 6: Success after binutils/gcc/linux/g [...] discards 82a2f10b18f 124: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] discards 356ef66893d 123: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] discards 38cc8a79b0c 122: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] discards f3f852116c6 121: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] discards 25985b0b3ef 120: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] discards 9e8f7d97a07 119: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] discards 6af1db6578f 118: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] discards 12c0d3ba98c 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 [...] discards c5f549dcc1b 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/g [...] discards c3525a0ecb7 115: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] discards 02babae0cfc 114: onsuccess: #532: 6: Success after binutils/gcc/linux/g [...] discards f6c5d053a30 113: onsuccess: #531: 6: Success after binutils/gcc/linux/g [...] discards 1cc92bbdc38 112: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] discards 9d6e897404f 111: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] discards d382b147d65 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 [...] discards b94f267d386 109: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] discards 391f22a0614 108: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] discards 66de46ec63e 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits discards 0d55bbe4146 106: onsuccess: #524: 1: Success after gcc: 11 commits discards 7ad95ce3cd0 105: force: #523: 1: Failure after basepoints/gcc-13-3918-g [...] discards 3d920e8ae5d 104: force: #522: 6: Success after gcc: 24 commits discards 84f60009857 103: onsuccess: #520: 6: Success after binutils: 10 commits discards f4fb3d40d8c 102: onsuccess: #518: 6: Success after binutils/gcc/linux/g [...] discards 57227f7ba1c 101: onsuccess: #517: 6: Success after binutils/gcc/linux/g [...] discards 11105699c69 100: onsuccess: #516: 6: Success after binutils/gcc/linux/g [...] discards fb72d514d9e 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gl [...] discards 9c99a465aa7 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gd [...] discards dec51c52a15 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gd [...] discards 69bb9849684 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] discards 315624db7c5 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gl [...] discards 300f9d3a75d 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] discards f6e9599c24e 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] discards 1b1659d7c91 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] discards c3631741977 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gl [...] discards ac9777d7ebf 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gd [...] discards 89d8fa514bd 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gl [...] discards 43b5681d6ad 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gl [...] discards d0970979323 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gl [...] discards 9ca43d01e25 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gl [...] discards 56765a71cf9 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gl [...] discards 462f1d2e6e9 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gd [...] discards d58f6d09068 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gd [...] discards f3640b38b04 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gd [...] discards b77a170ab03 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gl [...] discards a88d592d28c 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gd [...] discards 5963a4ca736 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gl [...] discards 9791afb8143 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gd [...] discards c3d38f06624 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gl [...] discards 7d1ef7be554 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gd [...] discards 1657af5564b 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gl [...] discards 01d96b1640a 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gl [...] discards d3b50a418c5 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gl [...] discards 18c65a6c663 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gd [...] discards 02596ef0387 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gl [...] discards baf2b4655ed 70: onsuccess: #486: 5: Success after gdb: 7 commits discards 24765a26b32 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-g [...] discards af9dade6e74 68: force: #484: 6: Success after gdb: 6 commits discards 6a1a2093efc 67: onsuccess: #483: 6: Success after linux: 384 commits discards ce3a9f2a46b 66: onsuccess: #482: 6: Success after glibc: 2 commits discards 064181a4d62 65: onsuccess: #480: 6: Success after gcc: 12 commits discards 3efc3fdc416 64: onsuccess: #479: 6: Success after binutils: 14 commits discards 9391f37b8f4 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gl [...] discards f3d158a8a4d 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gl [...] discards b5d0db65d25 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gl [...] discards 6c136a4ea88 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gl [...] discards b46fa16b959 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gl [...] discards 893a0aebb09 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gl [...] discards 333335d2ac6 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gd [...] discards 09665dc2fdb 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gl [...] discards 7157748b555 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gl [...] discards 367d83b9874 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gl [...] discards b531a127682 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gl [...] discards 798bbde78b0 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits discards 7159cf8998d 51: onsuccess: #465: 1: Success after gcc: 10 commits discards f08e1e2faf5 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb [...] discards 6e9f07a7c90 49: force: #463: 6: Success after gcc: 18 commits discards 594cc1b527b 48: onsuccess: #461: 6: Success after binutils: 10 commits discards f6274b46fee 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gd [...] discards 65ed76ae37e 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gd [...] discards b2e247bf316 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gl [...] discards 2d758a1b6f6 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gl [...] discards 4b87b0da4f0 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gl [...] discards 268b39e5b3d 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gl [...] discards b0ec32d45e8 41: onsuccess: #453: 6: Success after binutils/gcc/glibc/gd [...] discards afc11cce5dd 40: onsuccess: #452: 6: Success after binutils/gcc/linux/gl [...] discards 2508d96760e 39: onsuccess: #451: 6: Success after binutils/gcc/glibc/gd [...] discards 6e5e09d2764 38: onsuccess: #450: 6: Success after binutils/gcc/linux/gl [...] discards a7f9ddc0e46 37: onsuccess: #449: 6: Success after binutils/gcc/glibc/gd [...] discards ac326123b22 36: onsuccess: #448: 6: Success after binutils/gcc/glibc/gd [...] discards d92799014a6 35: onsuccess: #447: 6: Success after binutils/gcc/linux/gl [...] discards 4d546c23b23 34: onsuccess: #446: 6: Success after binutils/gcc/linux/gl [...] discards b673db6031b 33: onsuccess: #445: 6: Success after binutils/gcc/linux/gd [...] discards a57ab138a82 32: onsuccess: #444: 6: Success after binutils/gcc/linux/gl [...] discards 5755e19658b 31: onsuccess: #443: 6: Success after binutils/gcc/linux/gl [...] discards 6cca397b1f4 30: onsuccess: #442: 6: Success after binutils/gcc/linux/gl [...] new 3d63cc270be 30: onsuccess: #442: 6: Success after binutils/gcc/linux/gl [...] new d0a915184f9 31: onsuccess: #443: 6: Success after binutils/gcc/linux/gl [...] new 7c6714ffef5 32: onsuccess: #444: 6: Success after binutils/gcc/linux/gl [...] new ffa3a910d65 33: onsuccess: #445: 6: Success after binutils/gcc/linux/gd [...] new 13fc103fc15 34: onsuccess: #446: 6: Success after binutils/gcc/linux/gl [...] new 65d9a47fb50 35: onsuccess: #447: 6: Success after binutils/gcc/linux/gl [...] new 0c3ad60bf88 36: onsuccess: #448: 6: Success after binutils/gcc/glibc/gd [...] new 0085d5fc0d1 37: onsuccess: #449: 6: Success after binutils/gcc/glibc/gd [...] new 6cba24d2264 38: onsuccess: #450: 6: Success after binutils/gcc/linux/gl [...] new 3770aeab827 39: onsuccess: #451: 6: Success after binutils/gcc/glibc/gd [...] new b4c5c1ed823 40: onsuccess: #452: 6: Success after binutils/gcc/linux/gl [...] new 625953c2bdd 41: onsuccess: #453: 6: Success after binutils/gcc/glibc/gd [...] new 18f43c9da5f 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gl [...] new c8130bac4d7 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gl [...] new 303a858b19b 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gl [...] new 09eef24e78e 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gl [...] new 32ec89a39f6 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gd [...] new 182bf1626be 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gd [...] new 9421347e391 48: onsuccess: #461: 6: Success after binutils: 10 commits new 84973bed37e 49: force: #463: 6: Success after gcc: 18 commits new abc7df0afb8 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb [...] new ecafa049665 51: onsuccess: #465: 1: Success after gcc: 10 commits new 731e17cb8ac 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits new 23ac25865a5 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gl [...] new 5865b4f293c 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gl [...] new f62489b6927 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gl [...] new 85cd66712d4 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gl [...] new b9d9795343f 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gd [...] new 59e40f74a7d 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gl [...] new db889892718 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gl [...] new 7f464befbde 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gl [...] new 86ea9530fb6 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gl [...] new 00f4502d624 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gl [...] new 291d3d30805 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gl [...] new 40d066d6475 64: onsuccess: #479: 6: Success after binutils: 14 commits new 61ccb78218b 65: onsuccess: #480: 6: Success after gcc: 12 commits new 7cbf1c76fea 66: onsuccess: #482: 6: Success after glibc: 2 commits new 2bd0416891a 67: onsuccess: #483: 6: Success after linux: 384 commits new 62e51652d14 68: force: #484: 6: Success after gdb: 6 commits new ff481568a00 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-g [...] new b4602de78b1 70: onsuccess: #486: 5: Success after gdb: 7 commits new 261bc7c9fef 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gl [...] new 10142aebe53 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gd [...] new 34f936c201e 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gl [...] new 0ffa208e1d9 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gl [...] new 9945aa6f84a 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gl [...] new f962b0419a1 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gd [...] new 9683d73290f 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gl [...] new 3b890f7d6c6 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gd [...] new acdc0efb59e 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gl [...] new f4cb5d4593f 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gd [...] new cac777969f1 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gl [...] new c6e6c707e40 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gd [...] new 987c0e571a4 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gd [...] new 071fcfe9414 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gd [...] new 4775028c1cc 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gl [...] new adc4dbfef83 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gl [...] new 2122f9a5791 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gl [...] new f6ea1a29234 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gl [...] new 3ea569c8ee4 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gl [...] new 1a999024722 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gd [...] new 734b35e95a2 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gl [...] new 08d91577350 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] new 6046f89352f 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] new e6127c91777 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] new d4f2a110d55 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gl [...] new 053e0c40bcd 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] new 508e91405b3 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gd [...] new 2956ed727de 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gd [...] new 840958ff998 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gl [...] new 35d6d384d03 100: onsuccess: #516: 6: Success after binutils/gcc/linux/g [...] new 90e7d90f96f 101: onsuccess: #517: 6: Success after binutils/gcc/linux/g [...] new 6e4007f9de2 102: onsuccess: #518: 6: Success after binutils/gcc/linux/g [...] new c0962631ab0 103: onsuccess: #520: 6: Success after binutils: 10 commits new 2164582d297 104: force: #522: 6: Success after gcc: 24 commits new 241f1c10d20 105: force: #523: 1: Failure after basepoints/gcc-13-3918-g [...] new e21c1478af0 106: onsuccess: #524: 1: Success after gcc: 11 commits new f64de83d14a 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits new 15cec543219 108: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] new 138c3c3ef7f 109: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] new 5672fcebb84 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 [...] new b83035748be 111: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] new a2b1bcf9568 112: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] new 2155ae9febf 113: onsuccess: #531: 6: Success after binutils/gcc/linux/g [...] new bab839c7a76 114: onsuccess: #532: 6: Success after binutils/gcc/linux/g [...] new f510dd048e2 115: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] new 7bb2a610d81 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/g [...] new d4f771f8ea0 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 [...] new 2b9656abb9a 118: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] new 30f22ca50d1 119: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] new 12332345559 120: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] new 182330f32c4 121: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] new e51da1d06a5 122: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] new 1a294a36835 123: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] new 43df11f8f75 124: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] new acc51b84877 125: onsuccess: #543: 6: Success after binutils/gcc/linux/g [...] new b8829ed9adc 126: onsuccess: #544: 6: Success after binutils/gcc/linux/g [...] new da6a597ab4f 127: onsuccess: #545: 6: Success after binutils/gcc/linux/g [...] new 78b8d343ce7 128: onsuccess: #546: 6: Success after binutils/gcc/linux/g [...] new 114af001f48 129: onsuccess: #548: 6: Success after binutils: 8 commits new 6a4854e0b87 130: force: #551: 6: Success after gcc: 10 commits new 7a5ff5dc1c4 131: force: #552: 4: Failure after basepoints/gcc-13-4492-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 (3e5d37a8c0b) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1724 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 39324 -> 40144 bytes 05-build_abe-gcc/console.log.xz | Bin 213908 -> 216680 bytes 06-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 07-build_abe-linux/console.log.xz | Bin 8704 -> 8812 bytes 08-build_abe-glibc/console.log.xz | Bin 246876 -> 175588 bytes 09-build_abe-gdb/console.log.xz | Bin 39604 -> 0 bytes 10-check_regression/console.log.xz | Bin 2936 -> 3672 bytes 10-check_regression/jira-body.txt | 2 +- 10-check_regression/mail-body.txt | 17 +- 10-check_regression/mail-subject.txt | 2 +- 10-check_regression/results.regressions | 11 + 10-check_regression/trigger-bisect | 2 + 10-check_regression/trigger-notify | 0 11-update_baseline/console.log | 40 +-- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/score/results-functional.json | 1 - git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 284 +++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 17 +- mail/mail-subject.txt | 2 +- manifest.sh | 15 +- results | 15 +- 29 files changed, 376 insertions(+), 47 deletions(-) delete mode 100644 09-build_abe-gdb/console.log.xz create mode 100644 10-check_regression/results.regressions create mode 100644 10-check_regression/trigger-bisect create mode 100644 10-check_regression/trigger-notify delete mode 100644 dashboard/squad-vs-first/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.

1 year, 12 months

[toolchain/ci/interesting-commits] branch master updated (67a61ca -> 9473df2)

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 67a61ca Add entry 13917d936e367b0c42d4c32566e1017ff8e15520 from https [...] new 9473df2 Add entry 4500baaccb6e4d696e223c338bbdf7705c3646dd 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-4492-g4500baaccb6 | 1 + .../tcwg_gnu_native_build/master-aarch64/build_url | 2 +- .../tcwg_gnu_native_build/master-aarch64/last_good | 1 + .../master-aarch64/summary.txt | 1 + .../tcwg_gnu_native_build/status.txt | 75 ++++++++++++++++++++++ 5 files changed, 79 insertions(+), 1 deletion(-) create mode 120000 gcc/basepoints/gcc-13-4492-g4500baaccb6 copy gcc/sha1/{b04208895fed34171eac6bafb60c90048eb1cb0c => 4500baaccb6e4d696e223c3 [...] create mode 100644 gcc/sha1/4500baaccb6e4d696e223c338bbdf7705c3646dd/tcwg_gnu_nati [...] create mode 100644 gcc/sha1/4500baaccb6e4d696e223c338bbdf7705c3646dd/tcwg_gnu_nati [...] create mode 100644 gcc/sha1/4500baaccb6e4d696e223c338bbdf7705c3646dd/tcwg_gnu_nati [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto_lean updated (b921fc84479 -> 2f2811bc414)

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_profiled_lto_lean in repository toolchain/ci/base-artifacts. discards b921fc84479 107: onsuccess: #506: 2: Success after binutils/gcc: 6 commits discards 4d77a1a6b3b 106: onsuccess: #505: 2: Success after binutils/gcc: 31 commits discards f0ee68bfdfb 105: onsuccess: #504: 2: Success after binutils/gcc: 54 commits discards d392fcc2252 104: onsuccess: #503: 2: Success after binutils/gcc: 41 commits discards e5071f95247 103: onsuccess: #502: 2: Success after binutils/gcc: 25 commits discards cd2945e2ab0 102: onsuccess: #501: 2: Success after binutils/gcc: 117 commits discards f39807b38b9 101: onsuccess: #500: 2: Success after binutils/gcc: 34 commits discards b954413b3e4 100: onsuccess: #493: 2: Success after binutils/gcc: 43 commits discards c4c3fe5857b 99: onsuccess: #492: 2: Success after binutils/gcc: 18 commits discards 3a217e3685d 98: onsuccess: #491: 2: Success after binutils/gcc: 32 commits discards 25d40b9709f 97: onsuccess: #490: 2: Success after binutils/gcc: 80 commits discards 5fc72166880 96: onsuccess: #489: 2: Success after gcc: 7 commits discards f6ccb4f4fd0 95: onsuccess: #488: 2: Success after binutils: 5 commits discards 9e51cd8b0f0 94: onsuccess: #486: 2: Success after binutils/gcc: 95 commits discards 7067d017547 93: onsuccess: #481: 2: Success after binutils/gcc: 50 commits discards c8224e4fd1a 92: onsuccess: #480: 2: Success after binutils/gcc: 215 commits discards badfe8d3b73 91: onsuccess: #479: 1: Success after baseline build: no ne [...] discards fe3b9ec51da 90: force: #478: 1: Failure after gcc: 33 commits discards 3322b4e9dc6 89: onsuccess: #474: 2: Success after binutils: 25 commits discards 3c1c9da2283 88: onsuccess: #472: 2: Success after binutils/gcc: 49 commits discards 1a82cf6fffb 87: onsuccess: #471: 2: Success after binutils/gcc: 63 commits discards b3ab410bf0e 86: onsuccess: #470: 2: Success after binutils/gcc: 66 commits discards 347b067214d 85: onsuccess: #469: 2: Success after binutils/gcc: 73 commits discards e84b648d579 84: onsuccess: #468: 2: Success after binutils/gcc: 12 commits discards 708f598f437 83: onsuccess: #467: 2: Success after binutils/gcc: 24 commits discards 2ea59c4ff64 82: onsuccess: #466: 2: Success after binutils/gcc: 64 commits discards 0791c130f69 81: onsuccess: #465: 2: Success after binutils/gcc: 49 commits discards 6a59a1d53fc 80: onsuccess: #464: 2: Success after binutils/gcc: 27 commits discards 8cc061fee76 79: onsuccess: #463: 2: Success after binutils/gcc: 28 commits discards c3ad0f4d3f1 78: onsuccess: #462: 2: Success after binutils/gcc: 43 commits discards e6f02c12a9d 77: onsuccess: #461: 2: Success after binutils/gcc: 3 commits discards e9754349fde 76: onsuccess: #460: 2: Success after binutils/gcc: 24 commits discards 47122d51336 75: onsuccess: #459: 2: Success after binutils/gcc: 33 commits discards 856459f21ce 74: onsuccess: #458: 2: Success after binutils/gcc: 29 commits discards c944890ed6d 73: onsuccess: #457: 2: Success after binutils/gcc: 34 commits discards 9af8e4a5b08 72: onsuccess: #456: 2: Success after binutils/gcc: 35 commits discards 2f6f77cebd3 71: onsuccess: #455: 2: Success after binutils/gcc: 43 commits discards f608e04c99b 70: onsuccess: #454: 2: Success after binutils/gcc: 6 commits discards 03202a74260 69: onsuccess: #453: 2: Success after binutils/gcc: 6 commits discards 7d94c575885 68: onsuccess: #452: 2: Success after binutils/gcc: 38 commits discards 25903e9fbe2 67: onsuccess: #451: 2: Success after binutils/gcc: 46 commits discards 8103dc7132e 66: onsuccess: #450: 2: Success after binutils/gcc: 49 commits discards ad0b7d160bd 65: onsuccess: #449: 2: Success after binutils/gcc: 43 commits discards 931cc2f12e6 64: onsuccess: #448: 2: Success after binutils/gcc: 46 commits discards c82f990ac7c 63: onsuccess: #447: 2: Success after binutils/gcc: 9 commits discards 647de6f5be6 62: onsuccess: #446: 2: Success after binutils/gcc: 6 commits discards d54f2827c69 61: onsuccess: #445: 2: Success after binutils/gcc: 53 commits discards 255389c2ac1 60: onsuccess: #444: 2: Success after binutils/gcc: 27 commits discards 294cb907681 59: onsuccess: #443: 2: Success after binutils/gcc: 41 commits discards db69fe50fb6 58: onsuccess: #442: 2: Success after binutils/gcc: 61 commits discards 8d25ce9d0b7 57: onsuccess: #441: 2: Success after binutils/gcc: 49 commits discards 89ab2f8d514 56: onsuccess: #440: 2: Success after binutils/gcc: 7 commits discards f9227c91130 55: onsuccess: #439: 2: Success after binutils/gcc: 5 commits discards edbd725f343 54: onsuccess: #438: 2: Success after binutils/gcc: 41 commits discards 71ace463577 53: onsuccess: #437: 2: Success after binutils/gcc: 54 commits discards e1f7f39c1a1 52: onsuccess: #436: 2: Success after binutils/gcc: 31 commits discards ffdc5dfb69c 51: onsuccess: #435: 2: Success after binutils/gcc: 259 commits discards 79c6719d90a 50: onsuccess: #434: 1: Success after gcc: 22 commits discards de8f1a442df 49: force: #433: 1: Failure after basepoints/gcc-13-2887-gb [...] discards 05b1d8b35e3 48: force: #432: 2: Success after basepoints/gcc-13-2886-g8 [...] discards e02a68f0fef 47: onsuccess: #429: 2: Success after binutils: 8 commits discards 85e4c94cd2b 46: onsuccess: #427: 2: Success after binutils/gcc: 55 commits discards 2f57b9bdaf8 45: onsuccess: #426: 2: Success after binutils/gcc: 12 commits discards 2621e214dfb 44: onsuccess: #425: 2: Success after binutils/gcc: 9 commits discards 1bfa9f9dfe4 43: onsuccess: #424: 2: Success after binutils/gcc: 136 commits discards 6a8d45fde2f 42: onsuccess: #421: 2: Success after binutils/gcc: 39 commits discards af4629ea97e 41: onsuccess: #420: 2: Success after binutils/gcc: 10 commits discards ec10f51378b 40: onsuccess: #419: 2: Success after binutils/gcc: 7 commits discards a86831af57d 39: onsuccess: #418: 2: Success after binutils/gcc: 6 commits discards 2c729dfe0fb 38: onsuccess: #417: 2: Success after binutils/gcc: 24 commits discards 52a77ae71ee 37: onsuccess: #416: 2: Success after binutils/gcc: 18 commits discards 9c08ac7363d 36: onsuccess: #415: 2: Success after binutils/gcc: 30 commits discards b6438ae09e8 35: onsuccess: #414: 2: Success after binutils/gcc: 35 commits discards cf28b1a4ad6 34: onsuccess: #413: 2: Success after binutils/gcc: 68 commits discards 5fe89172fed 33: onsuccess: #412: 2: Success after binutils/gcc: 4 commits discards a6df6523939 32: onsuccess: #411: 2: Success after binutils/gcc: 7 commits discards 57549354443 31: onsuccess: #410: 2: Success after binutils/gcc: 25 commits discards 132e986e684 30: onsuccess: #409: 2: Success after binutils/gcc: 30 commits discards 567bce0c768 29: onsuccess: #408: 2: Success after binutils/gcc: 31 commits discards 05d7f0379d2 28: onsuccess: #407: 2: Success after binutils/gcc: 63 commits discards 9f41be0ec50 27: onsuccess: #406: 2: Success after binutils/gcc: 64 commits discards 38b3a545fad 26: onsuccess: #404: 2: Success after binutils/gcc: 6 commits discards 0084c26f914 25: onsuccess: 2: Success after binutils/gcc: 35 commits discards f8d4e80eac2 24: onsuccess: 2: Success after binutils/gcc: 39 commits discards 82f7357ce07 23: onsuccess: 2: Success after binutils/gcc: 52 commits discards 683b3405d76 22: onsuccess: 2: Successful build after binutils/gcc: 51 commits discards 1a036691e4d 21: onsuccess: 2: Successful build after binutils/gcc: 18 commits discards eb278786a2d 20: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards b57b7e1fcba 19: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 401f24bd04c 18: onsuccess: 2: Successful build after binutils/gcc: 30 commits discards 59fd150c4e3 17: onsuccess: 2: Successful build after binutils/gcc: 29 commits discards 589a5ae684a 16: onsuccess: 2: Successful build after binutils/gcc: 37 commits discards 9e3baf248f2 15: onsuccess: 2: Successful build after binutils/gcc: 21 commits discards 6b0d26bb4f5 14: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards 6e7cb03df24 13: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 17f2fd3229b 12: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 8c1ab7a4e5d 11: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 64c83105cb0 10: onsuccess: 2: Successful build after binutils/gcc: 31 commits discards 39accab611f 9: onsuccess: 2: Successful build after binutils/gcc: 27 commits discards a271ea758b8 8: onsuccess: 2: Successful build after binutils/gcc: 40 commits discards 1ca5f384135 7: onsuccess: binutils-gcc: 2 new 2f642e65a15 7: onsuccess: binutils-gcc: 2 new 33964eb92b0 8: onsuccess: 2: Successful build after binutils/gcc: 40 commits new f6c0062c62b 9: onsuccess: 2: Successful build after binutils/gcc: 27 commits new 8fe7ac24621 10: onsuccess: 2: Successful build after binutils/gcc: 31 commits new b6727cdc0ce 11: onsuccess: 2: Successful build after binutils/gcc: 11 commits new dd20de70015 12: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 94346cd8106 13: onsuccess: 2: Successful build after binutils/gcc: 3 commits new a4051edc7e0 14: onsuccess: 2: Successful build after binutils/gcc: 24 commits new b02ee00fcc0 15: onsuccess: 2: Successful build after binutils/gcc: 21 commits new e790ca99ba3 16: onsuccess: 2: Successful build after binutils/gcc: 37 commits new feab9a6f610 17: onsuccess: 2: Successful build after binutils/gcc: 29 commits new 75f5d502a12 18: onsuccess: 2: Successful build after binutils/gcc: 30 commits new 8f62584f41b 19: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 1c0e76db792 20: onsuccess: 2: Successful build after binutils/gcc: 3 commits new ec1f45aed90 21: onsuccess: 2: Successful build after binutils/gcc: 18 commits new 46b1b54448c 22: onsuccess: 2: Successful build after binutils/gcc: 51 commits new 2f078f63a0a 23: onsuccess: 2: Success after binutils/gcc: 52 commits new cac99bfe4e3 24: onsuccess: 2: Success after binutils/gcc: 39 commits new 931b2a28f35 25: onsuccess: 2: Success after binutils/gcc: 35 commits new 4475babcc0c 26: onsuccess: #404: 2: Success after binutils/gcc: 6 commits new bd43cd0b619 27: onsuccess: #406: 2: Success after binutils/gcc: 64 commits new aa7999f2f91 28: onsuccess: #407: 2: Success after binutils/gcc: 63 commits new f128fd0d02a 29: onsuccess: #408: 2: Success after binutils/gcc: 31 commits new 3d1d7c0f8eb 30: onsuccess: #409: 2: Success after binutils/gcc: 30 commits new 6933c3fd0e2 31: onsuccess: #410: 2: Success after binutils/gcc: 25 commits new b6470da4ed3 32: onsuccess: #411: 2: Success after binutils/gcc: 7 commits new 80c98567cfd 33: onsuccess: #412: 2: Success after binutils/gcc: 4 commits new 54a6c90b42d 34: onsuccess: #413: 2: Success after binutils/gcc: 68 commits new 6cab2053a86 35: onsuccess: #414: 2: Success after binutils/gcc: 35 commits new f00f7d53c87 36: onsuccess: #415: 2: Success after binutils/gcc: 30 commits new 88ed15c2d5f 37: onsuccess: #416: 2: Success after binutils/gcc: 18 commits new d7cfaa15597 38: onsuccess: #417: 2: Success after binutils/gcc: 24 commits new 7b66a582977 39: onsuccess: #418: 2: Success after binutils/gcc: 6 commits new 3b98f7ca611 40: onsuccess: #419: 2: Success after binutils/gcc: 7 commits new 160cd0755af 41: onsuccess: #420: 2: Success after binutils/gcc: 10 commits new 9791d641da8 42: onsuccess: #421: 2: Success after binutils/gcc: 39 commits new b78495845a1 43: onsuccess: #424: 2: Success after binutils/gcc: 136 commits new ab6b4cc15bd 44: onsuccess: #425: 2: Success after binutils/gcc: 9 commits new 8a34f946f83 45: onsuccess: #426: 2: Success after binutils/gcc: 12 commits new 50d7cd8ba73 46: onsuccess: #427: 2: Success after binutils/gcc: 55 commits new eae9830ec78 47: onsuccess: #429: 2: Success after binutils: 8 commits new c9140e16af0 48: force: #432: 2: Success after basepoints/gcc-13-2886-g8 [...] new 09eab6fde71 49: force: #433: 1: Failure after basepoints/gcc-13-2887-gb [...] new 631ec54c341 50: onsuccess: #434: 1: Success after gcc: 22 commits new 211909cff42 51: onsuccess: #435: 2: Success after binutils/gcc: 259 commits new 8ff8df57849 52: onsuccess: #436: 2: Success after binutils/gcc: 31 commits new a122c4e2a34 53: onsuccess: #437: 2: Success after binutils/gcc: 54 commits new b863752c253 54: onsuccess: #438: 2: Success after binutils/gcc: 41 commits new ae17da51a0d 55: onsuccess: #439: 2: Success after binutils/gcc: 5 commits new 248be199ebf 56: onsuccess: #440: 2: Success after binutils/gcc: 7 commits new ccc2d1a6676 57: onsuccess: #441: 2: Success after binutils/gcc: 49 commits new 0742477e5cd 58: onsuccess: #442: 2: Success after binutils/gcc: 61 commits new d8b4fef9494 59: onsuccess: #443: 2: Success after binutils/gcc: 41 commits new 93ec3b5e483 60: onsuccess: #444: 2: Success after binutils/gcc: 27 commits new 9f40255aaac 61: onsuccess: #445: 2: Success after binutils/gcc: 53 commits new cd95b8426aa 62: onsuccess: #446: 2: Success after binutils/gcc: 6 commits new 63b13787614 63: onsuccess: #447: 2: Success after binutils/gcc: 9 commits new 439c23d4caa 64: onsuccess: #448: 2: Success after binutils/gcc: 46 commits new 5a17e3e4988 65: onsuccess: #449: 2: Success after binutils/gcc: 43 commits new deb4b11a1f7 66: onsuccess: #450: 2: Success after binutils/gcc: 49 commits new 89674f0da0b 67: onsuccess: #451: 2: Success after binutils/gcc: 46 commits new 39a3d5bba5b 68: onsuccess: #452: 2: Success after binutils/gcc: 38 commits new 74fe0531e23 69: onsuccess: #453: 2: Success after binutils/gcc: 6 commits new 0ba664c6f86 70: onsuccess: #454: 2: Success after binutils/gcc: 6 commits new 99d74c08b7e 71: onsuccess: #455: 2: Success after binutils/gcc: 43 commits new 1bbcadfb45d 72: onsuccess: #456: 2: Success after binutils/gcc: 35 commits new 3364cf99cde 73: onsuccess: #457: 2: Success after binutils/gcc: 34 commits new 0337f88c0b7 74: onsuccess: #458: 2: Success after binutils/gcc: 29 commits new bad3364c783 75: onsuccess: #459: 2: Success after binutils/gcc: 33 commits new 4a994738e61 76: onsuccess: #460: 2: Success after binutils/gcc: 24 commits new ac7c7b2b068 77: onsuccess: #461: 2: Success after binutils/gcc: 3 commits new 18c09693eff 78: onsuccess: #462: 2: Success after binutils/gcc: 43 commits new 81cb8c2be03 79: onsuccess: #463: 2: Success after binutils/gcc: 28 commits new 0a44d87448f 80: onsuccess: #464: 2: Success after binutils/gcc: 27 commits new 78c58b20731 81: onsuccess: #465: 2: Success after binutils/gcc: 49 commits new 94c14460f3c 82: onsuccess: #466: 2: Success after binutils/gcc: 64 commits new 903250dd2f2 83: onsuccess: #467: 2: Success after binutils/gcc: 24 commits new 27eaa66614f 84: onsuccess: #468: 2: Success after binutils/gcc: 12 commits new 2b9ae99a2bf 85: onsuccess: #469: 2: Success after binutils/gcc: 73 commits new b670e7ab6ee 86: onsuccess: #470: 2: Success after binutils/gcc: 66 commits new 398f5eeb559 87: onsuccess: #471: 2: Success after binutils/gcc: 63 commits new 5ba345a249b 88: onsuccess: #472: 2: Success after binutils/gcc: 49 commits new a6097ef2e03 89: onsuccess: #474: 2: Success after binutils: 25 commits new 8965131a927 90: force: #478: 1: Failure after gcc: 33 commits new a9940e962f9 91: onsuccess: #479: 1: Success after baseline build: no ne [...] new 2ab89459367 92: onsuccess: #480: 2: Success after binutils/gcc: 215 commits new 17e34bbb326 93: onsuccess: #481: 2: Success after binutils/gcc: 50 commits new 712f33599a1 94: onsuccess: #486: 2: Success after binutils/gcc: 95 commits new 1b3f33bcc3f 95: onsuccess: #488: 2: Success after binutils: 5 commits new cbecbb182d2 96: onsuccess: #489: 2: Success after gcc: 7 commits new ba339e42524 97: onsuccess: #490: 2: Success after binutils/gcc: 80 commits new 5ebdc95e7c5 98: onsuccess: #491: 2: Success after binutils/gcc: 32 commits new 6f4dc0d54bf 99: onsuccess: #492: 2: Success after binutils/gcc: 18 commits new 22aa66bbe45 100: onsuccess: #493: 2: Success after binutils/gcc: 43 commits new a221dec3e36 101: onsuccess: #500: 2: Success after binutils/gcc: 34 commits new f612e82aee2 102: onsuccess: #501: 2: Success after binutils/gcc: 117 commits new c72315fe571 103: onsuccess: #502: 2: Success after binutils/gcc: 25 commits new e1ba326f70a 104: onsuccess: #503: 2: Success after binutils/gcc: 41 commits new 407f7dbf39a 105: onsuccess: #504: 2: Success after binutils/gcc: 54 commits new a8854f73f13 106: onsuccess: #505: 2: Success after binutils/gcc: 31 commits new d14bba86c8a 107: onsuccess: #506: 2: Success after binutils/gcc: 6 commits new 2f2811bc414 108: onsuccess: #507: 2: Success after binutils/gcc: 13 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 (b921fc84479) \ 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 1740 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2752 bytes 04-build_abe-binutils/console.log.xz | Bin 39564 -> 39764 bytes .../console.log.xz | Bin 526804 -> 527448 bytes 06-check_regression/console.log.xz | Bin 2748 -> 2960 bytes 07-update_baseline/console.log | 38 ++++++++++----------- 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, 34 insertions(+), 34 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-aarch64 updated (fdc0328f544 -> 3e5d37a8c0b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards fdc0328f544 129: onsuccess: #548: 6: Success after binutils: 8 commits discards d6323574de3 128: onsuccess: #546: 6: Success after binutils/gcc/linux/g [...] discards 26bf67f5c77 127: onsuccess: #545: 6: Success after binutils/gcc/linux/g [...] discards fc0cb2e2a8b 126: onsuccess: #544: 6: Success after binutils/gcc/linux/g [...] discards 68184b593be 125: onsuccess: #543: 6: Success after binutils/gcc/linux/g [...] discards 533507ecf1b 124: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] discards 19978202a93 123: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] discards 2b9c0f96dd6 122: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] discards e9a2c457770 121: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] discards e5be4d48b04 120: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] discards cc134d4115f 119: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] discards 86a97042707 118: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] discards ac479ff4b91 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 [...] discards 9e89d061200 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/g [...] discards ac803e6e26c 115: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] discards 22aab19739f 114: onsuccess: #532: 6: Success after binutils/gcc/linux/g [...] discards 7a8b605efae 113: onsuccess: #531: 6: Success after binutils/gcc/linux/g [...] discards fc660e2ac8b 112: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] discards 908bd2ba852 111: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] discards 1cf6a852de5 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 [...] discards 0f8fec99b24 109: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] discards 15697b42f92 108: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] discards 8e39f19d5a8 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits discards 9318b1376cd 106: onsuccess: #524: 1: Success after gcc: 11 commits discards dfe65be711d 105: force: #523: 1: Failure after basepoints/gcc-13-3918-g [...] discards 1215dcc3634 104: force: #522: 6: Success after gcc: 24 commits discards da84ce947d1 103: onsuccess: #520: 6: Success after binutils: 10 commits discards 3a3fcb005f1 102: onsuccess: #518: 6: Success after binutils/gcc/linux/g [...] discards b43cbc293b3 101: onsuccess: #517: 6: Success after binutils/gcc/linux/g [...] discards f67505736d8 100: onsuccess: #516: 6: Success after binutils/gcc/linux/g [...] discards c8a28ead20d 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gl [...] discards 9c36d0affd2 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gd [...] discards c2c637c4e8f 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gd [...] discards 20fdd69f687 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] discards b7b01e1a7a0 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gl [...] discards c4289578268 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] discards f66ad92ca46 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] discards 22fd8ef85dc 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] discards 9884e086ce5 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gl [...] discards ca13bb8f6e2 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gd [...] discards 69a0eaafc23 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gl [...] discards 7acf3bf69ea 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gl [...] discards 5201369483f 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gl [...] discards dc18d77fc21 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gl [...] discards 2d16cbcddf3 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gl [...] discards acd763556ce 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gd [...] discards 0e1629c2372 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gd [...] discards 57e36937cfd 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gd [...] discards 4972a075d74 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gl [...] discards ac36dd68fdb 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gd [...] discards 157f705bad4 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gl [...] discards 064a6d05372 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gd [...] discards b767fedcd8f 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gl [...] discards e2d8e1dbf9e 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gd [...] discards 941645fa679 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gl [...] discards b679949afc1 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gl [...] discards 2787dc40010 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gl [...] discards 5d7fd9d8ec1 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gd [...] discards c86e0fd8887 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gl [...] discards 4a39c73a118 70: onsuccess: #486: 5: Success after gdb: 7 commits discards 21a491692f9 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-g [...] discards 3550ad57c72 68: force: #484: 6: Success after gdb: 6 commits discards 28bc0909bb3 67: onsuccess: #483: 6: Success after linux: 384 commits discards 06588fb6afb 66: onsuccess: #482: 6: Success after glibc: 2 commits discards 4395cee3d23 65: onsuccess: #480: 6: Success after gcc: 12 commits discards edd09999dd1 64: onsuccess: #479: 6: Success after binutils: 14 commits discards 9e4b0841d99 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gl [...] discards 11a82c44adf 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gl [...] discards 8f2d06af9fb 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gl [...] discards 771ec5ad4f4 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gl [...] discards db39aa7dcc4 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gl [...] discards d2ca96842b6 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gl [...] discards 5a096bfa6da 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gd [...] discards 7a6e408d672 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gl [...] discards 22745b4287f 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gl [...] discards f9dae3807d2 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gl [...] discards af906586106 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gl [...] discards 364d22122f9 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits discards f4bde4054c5 51: onsuccess: #465: 1: Success after gcc: 10 commits discards 4de4336f601 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb [...] discards 73d4bea8871 49: force: #463: 6: Success after gcc: 18 commits discards daac271227a 48: onsuccess: #461: 6: Success after binutils: 10 commits discards 223b3919cd7 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gd [...] discards d01a56fee2e 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gd [...] discards 0a1010e7e55 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gl [...] discards 2fe1bdd1354 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gl [...] discards a51a4ee9405 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gl [...] discards 4a382eb2886 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gl [...] discards 92bb961fc6f 41: onsuccess: #453: 6: Success after binutils/gcc/glibc/gd [...] discards aa0477559b8 40: onsuccess: #452: 6: Success after binutils/gcc/linux/gl [...] discards b6f87618501 39: onsuccess: #451: 6: Success after binutils/gcc/glibc/gd [...] discards d7f84ff032d 38: onsuccess: #450: 6: Success after binutils/gcc/linux/gl [...] discards 12ce81eb798 37: onsuccess: #449: 6: Success after binutils/gcc/glibc/gd [...] discards 75a970c6c33 36: onsuccess: #448: 6: Success after binutils/gcc/glibc/gd [...] discards 372a3a88286 35: onsuccess: #447: 6: Success after binutils/gcc/linux/gl [...] discards 3941db3796e 34: onsuccess: #446: 6: Success after binutils/gcc/linux/gl [...] discards 64301829067 33: onsuccess: #445: 6: Success after binutils/gcc/linux/gd [...] discards 4bf06041624 32: onsuccess: #444: 6: Success after binutils/gcc/linux/gl [...] discards 7a3bb5aa99b 31: onsuccess: #443: 6: Success after binutils/gcc/linux/gl [...] discards af7e063035b 30: onsuccess: #442: 6: Success after binutils/gcc/linux/gl [...] discards 4eaa29434bc 29: onsuccess: #441: 6: Success after binutils/gcc/glibc/gd [...] new ae667563737 29: onsuccess: #441: 6: Success after binutils/gcc/glibc/gd [...] new 6cca397b1f4 30: onsuccess: #442: 6: Success after binutils/gcc/linux/gl [...] new 5755e19658b 31: onsuccess: #443: 6: Success after binutils/gcc/linux/gl [...] new a57ab138a82 32: onsuccess: #444: 6: Success after binutils/gcc/linux/gl [...] new b673db6031b 33: onsuccess: #445: 6: Success after binutils/gcc/linux/gd [...] new 4d546c23b23 34: onsuccess: #446: 6: Success after binutils/gcc/linux/gl [...] new d92799014a6 35: onsuccess: #447: 6: Success after binutils/gcc/linux/gl [...] new ac326123b22 36: onsuccess: #448: 6: Success after binutils/gcc/glibc/gd [...] new a7f9ddc0e46 37: onsuccess: #449: 6: Success after binutils/gcc/glibc/gd [...] new 6e5e09d2764 38: onsuccess: #450: 6: Success after binutils/gcc/linux/gl [...] new 2508d96760e 39: onsuccess: #451: 6: Success after binutils/gcc/glibc/gd [...] new afc11cce5dd 40: onsuccess: #452: 6: Success after binutils/gcc/linux/gl [...] new b0ec32d45e8 41: onsuccess: #453: 6: Success after binutils/gcc/glibc/gd [...] new 268b39e5b3d 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gl [...] new 4b87b0da4f0 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gl [...] new 2d758a1b6f6 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gl [...] new b2e247bf316 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gl [...] new 65ed76ae37e 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gd [...] new f6274b46fee 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gd [...] new 594cc1b527b 48: onsuccess: #461: 6: Success after binutils: 10 commits new 6e9f07a7c90 49: force: #463: 6: Success after gcc: 18 commits new f08e1e2faf5 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb [...] new 7159cf8998d 51: onsuccess: #465: 1: Success after gcc: 10 commits new 798bbde78b0 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits new b531a127682 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gl [...] new 367d83b9874 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gl [...] new 7157748b555 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gl [...] new 09665dc2fdb 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gl [...] new 333335d2ac6 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gd [...] new 893a0aebb09 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gl [...] new b46fa16b959 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gl [...] new 6c136a4ea88 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gl [...] new b5d0db65d25 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gl [...] new f3d158a8a4d 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gl [...] new 9391f37b8f4 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gl [...] new 3efc3fdc416 64: onsuccess: #479: 6: Success after binutils: 14 commits new 064181a4d62 65: onsuccess: #480: 6: Success after gcc: 12 commits new ce3a9f2a46b 66: onsuccess: #482: 6: Success after glibc: 2 commits new 6a1a2093efc 67: onsuccess: #483: 6: Success after linux: 384 commits new af9dade6e74 68: force: #484: 6: Success after gdb: 6 commits new 24765a26b32 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-g [...] new baf2b4655ed 70: onsuccess: #486: 5: Success after gdb: 7 commits new 02596ef0387 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gl [...] new 18c65a6c663 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gd [...] new d3b50a418c5 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gl [...] new 01d96b1640a 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gl [...] new 1657af5564b 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gl [...] new 7d1ef7be554 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gd [...] new c3d38f06624 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gl [...] new 9791afb8143 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gd [...] new 5963a4ca736 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gl [...] new a88d592d28c 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gd [...] new b77a170ab03 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gl [...] new f3640b38b04 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gd [...] new d58f6d09068 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gd [...] new 462f1d2e6e9 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gd [...] new 56765a71cf9 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gl [...] new 9ca43d01e25 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gl [...] new d0970979323 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gl [...] new 43b5681d6ad 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gl [...] new 89d8fa514bd 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gl [...] new ac9777d7ebf 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gd [...] new c3631741977 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gl [...] new 1b1659d7c91 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] new f6e9599c24e 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] new 300f9d3a75d 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] new 315624db7c5 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gl [...] new 69bb9849684 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] new dec51c52a15 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gd [...] new 9c99a465aa7 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gd [...] new fb72d514d9e 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gl [...] new 11105699c69 100: onsuccess: #516: 6: Success after binutils/gcc/linux/g [...] new 57227f7ba1c 101: onsuccess: #517: 6: Success after binutils/gcc/linux/g [...] new f4fb3d40d8c 102: onsuccess: #518: 6: Success after binutils/gcc/linux/g [...] new 84f60009857 103: onsuccess: #520: 6: Success after binutils: 10 commits new 3d920e8ae5d 104: force: #522: 6: Success after gcc: 24 commits new 7ad95ce3cd0 105: force: #523: 1: Failure after basepoints/gcc-13-3918-g [...] new 0d55bbe4146 106: onsuccess: #524: 1: Success after gcc: 11 commits new 66de46ec63e 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits new 391f22a0614 108: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] new b94f267d386 109: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] new d382b147d65 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 [...] new 9d6e897404f 111: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] new 1cc92bbdc38 112: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] new f6c5d053a30 113: onsuccess: #531: 6: Success after binutils/gcc/linux/g [...] new 02babae0cfc 114: onsuccess: #532: 6: Success after binutils/gcc/linux/g [...] new c3525a0ecb7 115: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] new c5f549dcc1b 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/g [...] new 12c0d3ba98c 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 [...] new 6af1db6578f 118: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] new 9e8f7d97a07 119: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] new 25985b0b3ef 120: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] new f3f852116c6 121: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] new 38cc8a79b0c 122: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] new 356ef66893d 123: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] new 82a2f10b18f 124: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] new ef37f630392 125: onsuccess: #543: 6: Success after binutils/gcc/linux/g [...] new 236fdf55183 126: onsuccess: #544: 6: Success after binutils/gcc/linux/g [...] new 7022f3a68e1 127: onsuccess: #545: 6: Success after binutils/gcc/linux/g [...] new 70459bc8675 128: onsuccess: #546: 6: Success after binutils/gcc/linux/g [...] new 6f90d179ade 129: onsuccess: #548: 6: Success after binutils: 8 commits new 3e5d37a8c0b 130: force: #551: 6: Success after gcc: 10 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (fdc0328f544) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...] 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 1740 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2748 bytes 04-build_abe-binutils/console.log.xz | Bin 41040 -> 39324 bytes 05-build_abe-gcc/console.log.xz | Bin 218140 -> 213908 bytes 06-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 07-build_abe-linux/console.log.xz | Bin 8776 -> 8704 bytes 08-build_abe-glibc/console.log.xz | Bin 246892 -> 246876 bytes 09-build_abe-gdb/console.log.xz | Bin 39528 -> 39604 bytes 10-check_regression/console.log.xz | Bin 3040 -> 2936 bytes 11-update_baseline/console.log | 60 +++++++++++++++++------------------ 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 | 16 +++++----- 16 files changed, 43 insertions(+), 43 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[gcc] branch master updated (d492d50f644 -> 0d14720f93a)

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 d492d50f644 tree-optimization/106868 - bogus -Wdangling-pointer diagnostic new 0d14720f93a middle-end/40635 - SSA update losing PHI arg loations The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/testsuite/gcc.dg/uninit-pr40635.c | 33 +++++++++++++++++++++++++++++++++ gcc/tree-into-ssa.cc | 11 +++++++---- 2 files changed, 40 insertions(+), 4 deletions(-) create mode 100644 gcc/testsuite/gcc.dg/uninit-pr40635.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (41a9b7bca14 -> e4b84e838c0)

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 41a9b7bca14 208: onsuccess: #2012: 1: Success after linux: 12 commits discards cb1f13b5da1 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 15a4c6a17dc 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 72b09cc6d6d 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards be235021a9a 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards ec7c611f16e 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards 0dfe5b44c54 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards a11d6b0a997 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 639b5a7aca6 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards 0ff40ea2dda 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards cbc707fd53d 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards 2746ba299cb 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards a373bfa398c 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards 545a534564d 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards 7c7ec89d611 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 985e8cd61d1 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards c39eacc9d7d 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards a91125117ea 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards d0a0fdfccc2 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards da98baf9188 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards 08b6f2ff951 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards f384b004c4f 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards f4fe1b24efc 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards 3f1041bac10 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards 7ce50ec13ce 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards 847a5f74fd3 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards 2dd55a07e80 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards e2ff37a8e53 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards 3add6eda7ea 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards 24e9dedd209 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards 4813f22fac3 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards 8bfd2627ecb 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards edd543c2bd7 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards f04221fba08 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards 5163150df12 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards 1dc328f5cdb 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards 820f927d452 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards f6c513f97be 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards ec0f1c53274 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards a1b14730bcc 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards 52247a0921d 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards d6365693259 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards 0ce77217be8 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards 52172b33258 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards 2dbb6b46e3b 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards 93930f368d8 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 3fb03deb914 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards 3466968ca67 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards 3011d72fb14 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards a11cb153e07 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards 2c88b057067 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards 8f41954a530 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards b3666fbd991 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 6b3a5efee2a 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards 177ccb406e2 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 7cecadb7534 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 375c9280e5a 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards 243ce48002b 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards 21b140f1bc5 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards 4719e7499c3 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards 25331ec27f2 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards 59dbc9677e5 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards d4685c8b18f 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards 5d11d1c703d 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards 503ab697f3e 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 0c81d58396c 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards 955c3cfd3af 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards 7fcf0df7c45 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards 02333b72450 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards 1abc8439a4c 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards e9870940dc9 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards 62ed542d74f 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 120cb5f5fdd 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards 1e601b18d15 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards e359282308f 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 3c818605c18 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards a98529a477d 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] discards 0c1f2823e38 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] discards b2325a332f1 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 18b7ebb3f6f 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] discards 792409f7bc5 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 534a624c486 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] discards 9d4e72eb955 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 172f0d0d25d 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] discards 84719070458 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 758841e7110 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] discards 997f55732c9 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] discards 77edebc9ad5 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] discards 5568ad39b4b 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] discards 793383dd865 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] discards e46d97d8e70 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] discards 9da1b912c90 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] discards 5b8ff6f3d89 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] discards 3aa2c1d4580 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] discards 967fd745074 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 1f34efaf5ae 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] discards c911b152b5b 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] discards 79ffbf6aacc 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] discards 7346ae05476 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 4ee4edfb0b7 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 [...] discards d63511679a1 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 [...] new 2eb1af8c437 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 [...] new 3f0591fc4f4 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 [...] new bdfd7f4654a 110: onsuccess: #1703: 1: Success after gcc: 6 commits new e0f8bb5f617 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] new b310cd7f94a 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] new d8976088d35 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] new c6eaa8b2fd7 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 2ac8a1dfee5 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] new 39473b9486d 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] new 2d53340e8a2 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] new ed7ac5b26a6 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] new e08821eabfa 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] new 6a33c299b98 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] new fbcd3fc8fcd 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] new f41c9aa0210 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] new 8bea826e23e 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] new 05d4b29cfe4 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new ae353d2b0e7 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] new 30d56dcfaec 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new e5cbfba51b8 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] new 7eaf72512a3 128: onsuccess: #1723: 1: Success after linux: 12 commits new 2d1dffb05eb 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] new 3e363ede102 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new e521308c5e0 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new d7f37d2640a 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new c3ca703ff73 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new 129e0eb3c6b 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 28de58989fe 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 8776b6e3b0d 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new a1a84ae51a8 137: onsuccess: #1736: 1: Success after gcc: 5 commits new c9ca9efe9c6 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new e7ee02c3437 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new ad6df4167cf 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new bd38154ff22 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new 072c92138d2 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new 9445df2374d 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 1d9d4338281 144: onsuccess: #1743: 1: Success after glibc: 2 commits new a44a47f5e1e 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new b8caf36ad1f 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new 95c045cf927 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new 03c72808d4f 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new 75c282af6f3 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new 5615fdc349d 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new 43c34ec0e21 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new 3e9b8adee24 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new 38081c2bf32 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 0e9a79dff65 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new be2640b879f 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new ffa7f460776 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 2c2e6fd2b41 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new bae9c362d0f 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new 0ff08f785e7 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new bb3035e1711 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new a525f0d80b2 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new a99d89c027b 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new fc6d30d3212 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new cdb56c44d8e 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new 0d2a85850f1 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new ffcb6df5838 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new fc9453317c5 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new 4d3758491cf 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new 4b6ec57092b 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new 66de55595de 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new 6e01ba2909a 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new 66f4b9afd4a 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new f933f8d90c3 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new 851538da36b 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new 7605e384aa5 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new d763f323f50 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new c693a15f0b4 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new f24e6491e7a 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new c408c5cb8f7 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new cf255ceca07 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new dd79c8cbb5d 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new 8527f9472ef 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new ffc1661a5ed 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new 8c26ad94bd0 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new fc9f3b38e69 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new 86f2cc211a2 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new 07be56fdfdd 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new 407aaf9f483 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new 07dbb57416d 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new 836d5abf3e5 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new 6b5651a849e 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new 6ddfbed886b 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new 199ac86d751 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 187a87db95a 194: onsuccess: #1995: 1: Success after linux: 517 commits new 7295cfda7af 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new ba2a2647cd7 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new 08561cb6887 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new 28a788155ff 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new ad5baba04fe 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 6a055428224 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new 117e2e13a42 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 9eaa828dc04 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new bf197f5d49c 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new dd520e935c9 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new 653e85c7b48 205: onsuccess: #2006: 1: Success after gcc: 3 commits new afa6ef260d4 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 48e2227ae70 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 97f39a64613 208: onsuccess: #2012: 1: Success after linux: 12 commits new e4b84e838c0 209: onsuccess: #2014: 1: Success after binutils: 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 (41a9b7bca14) \ 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 1732 -> 1924 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31436 -> 31756 bytes 04-build_abe-stage1/console.log.xz | Bin 91804 -> 91356 bytes 06-build_abe-linux/console.log.xz | Bin 8496 -> 8396 bytes 07-build_abe-glibc/console.log.xz | Bin 236756 -> 236876 bytes 08-build_abe-stage2/console.log.xz | Bin 225952 -> 223868 bytes 09-build_abe-gdb/console.log.xz | Bin 38728 -> 38976 bytes 10-build_abe-qemu/console.log.xz | Bin 30620 -> 30592 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2460 -> 2416 bytes 13-check_regression/console.log.xz | Bin 5368 -> 5428 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 26 + 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 36 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +- results | 26 + sumfiles/g++.log.xz | Bin 2711992 -> 2739924 bytes sumfiles/g++.sum | 14 +- sumfiles/gcc.log.xz | Bin 2313940 -> 2273992 bytes sumfiles/gcc.sum | 1928 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 892248 -> 893856 bytes sumfiles/gfortran.sum | 58 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213232 -> 213156 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434364 -> 430740 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 1194 insertions(+), 1092 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022