Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[binutils-gdb] branch master updated (701ea7a2562 -> c536b4f527d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 701ea7a2562 sim: iq2000: drop unused cpu define logic new c536b4f527d sim: or1k: drop unused rules 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: sim/or1k/Makefile.in | 12 ------------ 1 file changed, 12 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/release-arm-check_bootstrap updated (e25fb28c01 -> b961443083)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check_bootstrap/release-arm-check_bootstrap in repository toolchain/ci/base-artifacts. from e25fb28c01 46: onsuccess: #169: 1: Success after binutils/gcc: 7 commits new b961443083 47: onsuccess: #170: 1: Success after binutils/gcc: 8 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 1732 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 52048 -> 51248 bytes 04-build_abe-bootstrap/console.log.xz | Bin 463232 -> 463352 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3820 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2720 -> 2440 bytes 07-check_regression/console.log.xz | Bin 4876 -> 5040 bytes 07-check_regression/extra-bisect-params | 1 + 07-check_regression/fails.sum | 7 + 07-check_regression/mail-body.txt | 27 + 07-check_regression/results.compare | 26 +- 07-check_regression/results.compare2 | 64 +- 07-check_regression/results.regressions | 27 + dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 27 + sumfiles/g++.log.xz | Bin 2836156 -> 2805060 bytes sumfiles/g++.sum | 126 +- sumfiles/gcc.log.xz | Bin 2502136 -> 2468808 bytes sumfiles/gcc.sum | 4218 +++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 955400 -> 943236 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2308 -> 2304 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207248 -> 207248 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2732 -> 2724 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 471512 -> 462780 bytes sumfiles/libstdc++.sum | 12 +- 35 files changed, 2388 insertions(+), 2272 deletions(-) create mode 100644 07-check_regression/extra-bisect-params create mode 100644 07-check_regression/fails.sum create mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_debug updated (e795049f17 -> 2e8b263aa5)

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/release-arm-bootstrap_debug in repository toolchain/ci/base-artifacts. from e795049f17 46: onsuccess: #169: 2: Success after binutils/gcc: 7 commits new 2e8b263aa5 47: onsuccess: #170: 2: Success after binutils/gcc: 8 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 1732 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2764 bytes 04-build_abe-binutils/console.log.xz | Bin 51220 -> 53720 bytes 05-build_abe-bootstrap_debug/console.log.xz | Bin 461748 -> 463412 bytes 06-check_regression/console.log.xz | Bin 2680 -> 2660 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 12 files changed, 15 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (89f20e04f4 -> 4f67a9b9a5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 89f20e04f4 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 519b770eba 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 3c6a453919 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 59a06a41b2 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards dbe79b0377 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards a01fb31456 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards 8e8987dfce 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards 42ebf110b2 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 0ec5e22d49 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards e46988c0fb 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards 8543165d79 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards b9560c14e4 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards e681417aaa 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards 61b345164e 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards 22520a527a 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 0f7b38422a 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 0f3d67ea90 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards febd88a187 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards ea7cd22203 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards 6ddc0a111e 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards c82c7b4164 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards daff5b69ec 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards d7719e5c13 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards ea6daee9b9 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 44a59d605a 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards e37d474f33 125: onsuccess: #614: 1: Success after linux: 12 commits discards c53c6b1788 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 6461b3bce9 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 037fb4d758 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 139b4c1fb1 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 92c43f3da9 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards c23efff4fd 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards dbe689fb41 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards dc926e6453 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards fdd51f8648 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards b0e94d97cd 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards 52088aac8d 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 60da8e115e 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 131e4be7ad 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards 12805b1c78 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards 02d8c2f3db 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 5194404b87 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards af02456c61 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards 9480cde35e 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 5929e66a13 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards ac9f2db27c 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 792b4f7f21 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards ff64b253bf 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 056224a969 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 65a9b7bf03 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards b753a96e91 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards bd1bf93f16 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 152aeacddc 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards c4b1e1ce7f 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards dfbbe0f4ad 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 81ff61949d 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 5f6c78377b 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards ebd99a64f1 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 617ce41d1c 92: onsuccess: #575: 1: Success after linux: 34 commits discards 73f8852c39 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 4eeaf9160f 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 90711752bf 89: onsuccess: #570: 1: Success after linux: 11 commits discards b5cacc5b80 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 585573769e 87: onsuccess: #567: 1: Success after binutils: 8 commits discards ddfbd882eb 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards f45198238c 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 507b72771e 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 6bea8dfd56 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 5d7541a03d 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 557da4c043 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 776a2486ed 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 4351f4515b 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards f67db1e149 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 6e7688d948 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards b8cca8394e 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 8609147233 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards fe9fd4cf2f 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards b562375f56 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 6461544911 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 8f9531b960 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards c091f52ad6 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 68ff630bf5 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 40bf19c777 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards 2a5b10bd67 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 4953e6270d 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 67dd7b5641 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 7bd4bf520e 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards fce7923c23 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards eca51a9b32 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards fbb5560803 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 89f641dc76 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards 64c613fa15 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards efd19ddf07 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards da58b6d074 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards 56d897ce1e 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 928846fd1e 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 440158cb51 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards 9ea867792c 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 72035bbf31 52: onsuccess: #528: 1: Success after binutils: 8 commits discards cc9554438e 51: onsuccess: #525: 1: Success after binutils: 8 commits discards a43e0cbdd5 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new 62e7d9c63a 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new 90ed460a7c 51: onsuccess: #525: 1: Success after binutils: 8 commits new 495ed793c6 52: onsuccess: #528: 1: Success after binutils: 8 commits new 26514da5f6 53: onsuccess: #531: 1: Success after binutils: 12 commits new 3416338436 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new b85e3605ac 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 127e78d1a2 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 52758b1b59 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 55a2f0fc8a 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 666e05a702 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 6dc183bf32 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new 7edf602bb4 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 8939f67148 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new f26e2afea7 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new ca41f33d95 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 041536db62 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 3f9d78035d 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 6029e1bbe6 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 0230b1ff7f 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new 3bb131f30b 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 896acaeabf 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 53437f11c8 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new a9dae26de2 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 0f24e988c9 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new fb20f69526 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 359f1bd962 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 58558438e8 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 6016c217fa 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new c6b923412a 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 0932cce3f1 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new f051f1f8ba 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 16d760d20b 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new d079b2070d 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 3fdedc9422 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new afc0ae1a7b 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new e1b5e20236 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new e1616f3e9e 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new ec11c33d09 87: onsuccess: #567: 1: Success after binutils: 8 commits new e6973d6554 88: onsuccess: #569: 1: Success after glibc: 10 commits new e307d6e0b1 89: onsuccess: #570: 1: Success after linux: 11 commits new 643443b9e4 90: onsuccess: #572: 1: Success after binutils: 15 commits new de5db9859a 91: onsuccess: #574: 1: Success after glibc: 3 commits new e293475f96 92: onsuccess: #575: 1: Success after linux: 34 commits new 6f9c681474 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new a6a9212a28 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 91e47ef40e 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 9fe4f0f848 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 0fe8abfc1b 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 506f12034a 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 177301540e 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 392b285bb6 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 477830ec94 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 2b51db9126 102: onsuccess: #586: 1: Success after binutils: 5 commits new 44d6da3a58 103: onsuccess: #589: 1: Success after binutils: 3 commits new 6e7bf1a442 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 25bf1e26d7 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 4ea40f299b 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 6ce44a0a38 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new be7306419b 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 276019cd87 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 5799a69c57 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new a6350bc83c 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 43d9325177 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 252515fbc6 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new aa7d7d6200 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new c28fb1e2c2 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 7ec50bc1eb 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 4a8ee84b81 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new cb9932f7a6 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new e3ce91767f 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 586d6a9c10 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new 6f58d12a26 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 49898c28a8 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 8833d8a22f 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new 404c3068a0 124: onsuccess: #612: 1: Success after binutils: 18 commits new eedeed7b20 125: onsuccess: #614: 1: Success after linux: 12 commits new ece3c68506 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new 8fb1ea69b3 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 89673f543e 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 05bac0d3e2 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 6112e60fcf 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 20c6147ef0 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 9bcdea9be1 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new d8712b04a6 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new 0d2ba7a562 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 7e6aca0737 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 6d44497d26 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new b2ddf60e88 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new e5b503b03a 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 596c5b2c0e 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new 493797cb6e 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new bfd6c1dd74 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new 7a68694e66 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new 7869e3fbc4 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 446a14822f 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new 8aa6ffdefd 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 5c74bf17c1 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new 7d9115d5e4 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new 6044c153d2 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 2e0eb61b17 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 833fad6356 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 4f67a9b9a5 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] 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 (89f20e04f4) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] 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 1744 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2808 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 54852 -> 54808 bytes 04-build_abe-gcc/console.log.xz | Bin 241544 -> 240432 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9020 -> 8724 bytes 07-build_abe-glibc/console.log.xz | Bin 236432 -> 236852 bytes 08-build_abe-gdb/console.log.xz | Bin 51884 -> 52700 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3848 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2140 -> 2336 bytes 11-check_regression/console.log.xz | Bin 12988 -> 10472 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 40 +- 11-check_regression/mail-body.txt | 170 +- 11-check_regression/results.compare | 85 +- 11-check_regression/results.compare2 | 1424 +------ 11-check_regression/results.regressions | 85 +- 12-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 172 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 85 +- sumfiles/gdb.log.xz | Bin 1803196 -> 1829424 bytes sumfiles/gdb.sum | 6736 +++++++++++++++++++------------ 30 files changed, 4713 insertions(+), 4190 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (0dd2b45b83 -> fdceb026b4)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards 0dd2b45b83 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits discards e4bd1d1d86 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits discards 7f1415c5d6 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] discards c9646e25bd 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits discards 3c80ac1231 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits discards 7ea76fdf50 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] discards 7333b9ef98 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits discards 737f6eebbd 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits discards 6667e863cf 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits discards 0fbe419ff8 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards cf29450189 288: onsuccess: #1985: 7: Success after gcc: 17 commits discards d3f4eb2858 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits discards 76c345ba03 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits discards 25c024be46 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits discards 75c9f72e7b 284: onsuccess: #1981: 7: Success after gcc: 2 commits discards 4cc4f76f4d 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits discards 636d1aeefa 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] discards 3c4d82e1a8 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] discards 4f906a94f8 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits discards 91cd6381a3 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits discards c58516d437 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] discards b418f6cb36 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits discards 56aa0883ef 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] discards 3b95a2f43e 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] discards 23eb81fc3b 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] discards 4710b23649 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits discards 62cffcbd9c 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] discards 9643af25dd 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] discards a802c5ed74 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] discards 382d87bc4d 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] discards bf798e29ad 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] discards 9131373d02 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] discards 2a49fbf6ac 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] discards 4bcafabc38 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] discards 5807414fe6 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] discards 1650121ee6 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] discards 5ad159642d 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] discards 9436f4fe80 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] discards 2bf881d06c 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits discards 0d8b331d13 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] discards 780835a7cb 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits discards c56ade8c5f 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits discards c49f38d5de 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] discards 634338e9a4 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] discards 2f73541b48 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] discards 054fe86ee4 253: onsuccess: #1950: 7: Success after glibc: 2 commits discards bb26895901 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] discards fa0c8af767 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] discards 35753e18dd 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits discards 5f962c57cc 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits discards 9ce30dddb6 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] discards 2307a72686 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits discards 94abad4774 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits discards add4b8186d 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] discards c17e7178cc 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] discards e7003c0a49 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] discards ce51a5def9 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] discards ca6263358b 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] discards a71820d530 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] discards 06f490e419 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] discards d0d8f75565 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] discards aef0f23f31 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] discards 23a24d651b 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] discards 1041669bc7 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] discards 3d524b9f85 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] discards fb11da3ba1 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] discards e1bd5ea1a4 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] discards 3bdd9413a1 231: onsuccess: #1928: 3: Success after gcc: 8 commits discards ff14a002f4 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] discards 02b3353966 229: force: #1926: 7: Success after gcc: 7 commits discards 17d13a9ab5 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] discards 2613182237 227: onsuccess: #1906: 7: Success after binutils: 9 commits discards 06da48b72a 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] discards 93dd4deaf1 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/g [...] discards 62dfe6d590 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/g [...] discards e9370e9ace 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-45 [...] discards 2f579317ef 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/g [...] discards 0f26a19ce7 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 15 [...] discards 93754d4be9 220: onsuccess: #1898: 7: Success after binutils/linux/glibc [...] discards 674bd7d072 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 commits discards d1ea5b8b81 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/g [...] discards 0bd01a3cde 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 10 [...] discards f6e4c2fd31 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits discards 51d41f0c66 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/g [...] discards 1f6f704762 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/g [...] discards f13bd020c5 213: onsuccess: #1889: 7: Success after gcc: 5 commits discards 6719c24c06 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/g [...] discards ce71868d71 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/g [...] discards 1442651355 210: onsuccess: #1868: 7: Success after binutils: 7 commits discards 3ebf5d53ab 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qem [...] discards 8890565531 208: onsuccess: #1865: 7: Success after linux: 12 commits discards 6dabd90075 207: onsuccess: #1862: 7: Success after binutils: 4 commits discards 5779dda0b8 206: onsuccess: #1860: 7: Success after gcc: 2 commits discards 81564b97ac 205: onsuccess: #1859: 7: Success after gcc: 3 commits discards 0c3d26ef3b 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/g [...] discards a6a061c46f 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 commits discards 22cdc79103 202: onsuccess: #1856: 7: Success after gcc: 2 commits discards 043f1309ed 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/g [...] discards f78e6439bc 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits discards 9abf18ef63 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 18 [...] discards 03339121d7 198: onsuccess: #1852: 7: Success after gcc: 5 commits new 2803b36461 198: onsuccess: #1852: 7: Success after gcc: 5 commits new c6fca2562a 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 18 [...] new edb0cde42e 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits new 1a4a713bde 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/g [...] new 624c87ea64 202: onsuccess: #1856: 7: Success after gcc: 2 commits new a3aacb69ec 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 commits new 36b81febbf 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/g [...] new fabd3f1475 205: onsuccess: #1859: 7: Success after gcc: 3 commits new 10316ccdc6 206: onsuccess: #1860: 7: Success after gcc: 2 commits new 278181d8c5 207: onsuccess: #1862: 7: Success after binutils: 4 commits new 6181a3aec8 208: onsuccess: #1865: 7: Success after linux: 12 commits new a6d2b28ba6 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qem [...] new b3137bc8e3 210: onsuccess: #1868: 7: Success after binutils: 7 commits new 2d77848925 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/g [...] new 80c7a9285e 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/g [...] new 2d8168c409 213: onsuccess: #1889: 7: Success after gcc: 5 commits new 847993a548 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/g [...] new a2d30debb6 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/g [...] new 0634a53a63 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits new 22be3a26e2 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 10 [...] new 33b287a508 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/g [...] new d7e55fa533 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 commits new bd2308c809 220: onsuccess: #1898: 7: Success after binutils/linux/glibc [...] new 3d64f5f20c 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 15 [...] new 3e99b729ac 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/g [...] new 2475137be1 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-45 [...] new 5019710892 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/g [...] new a0e9132ffe 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/g [...] new 05a020b7d5 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] new 08c579eedd 227: onsuccess: #1906: 7: Success after binutils: 9 commits new cef2f3794f 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] new 3278e7d06f 229: force: #1926: 7: Success after gcc: 7 commits new 92bae57582 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] new 221d15adb5 231: onsuccess: #1928: 3: Success after gcc: 8 commits new 13d9e2afaf 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] new ff857f3fba 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] new 8dd8a8df89 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] new d52c5db7c6 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] new 6da36c35ad 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] new 4f79bd127e 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] new 87a3d8fdee 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] new bc781793cf 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] new 03bb31aa2d 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] new d15d174656 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] new ef31a06202 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] new 649e2349f0 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] new 124b744a40 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] new 67ebda51d5 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] new 74507db1ab 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits new 76367cd4d2 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits new 3ef15fe446 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] new 2833ef32e3 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits new 5619464b02 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits new 2e3ecbfd05 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] new 296e8182ee 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] new 2f42d66110 253: onsuccess: #1950: 7: Success after glibc: 2 commits new 8663c2ca26 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] new 13d8f0fa7f 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] new 58a9949456 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] new 35b6ae4367 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits new f05ea1a828 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits new 6368daf2af 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] new 0b229a7fd8 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits new 20648bdaa5 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] new 10bc1101f4 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] new 4252362515 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] new 6360749010 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] new 8c3b12ca61 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] new 90956b96c1 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] new 2198da7d25 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] new 85e7344884 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] new e48ea25a24 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] new b4429794b4 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] new 5775b020d4 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] new c978671215 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] new 1fcb7d3c7c 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits new a9a3c30d6e 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] new 87c1b7ab86 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] new 42769b1ede 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] new 8c4a11e8c6 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits new 4e462bc429 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] new 04822e3e54 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits new 4859ac7690 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits new 7cd1fb2557 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] new 498dba1bc1 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] new 4196c6e1c5 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits new 217513df1f 284: onsuccess: #1981: 7: Success after gcc: 2 commits new 50d5ad49bc 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits new e23b8f32e9 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits new 176344b164 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits new 52dbdca786 288: onsuccess: #1985: 7: Success after gcc: 17 commits new fde3e087c5 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new e0dda56535 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits new 19de5bee4d 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits new 68f2136766 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits new a295c417ee 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] new d3e60df4b4 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits new 84ececab21 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits new 48ca7269bf 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] new 855f9c3975 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits new 4a6155c696 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits new fdceb026b4 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] 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 (0dd2b45b83) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1768 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2772 bytes 04-build_abe-binutils/console.log.xz | Bin 32288 -> 32096 bytes 05-build_abe-stage1/console.log.xz | Bin 73472 -> 74132 bytes 07-build_abe-linux/console.log.xz | Bin 8760 -> 8768 bytes 08-build_abe-glibc/console.log.xz | Bin 245224 -> 244860 bytes 09-build_abe-stage2/console.log.xz | Bin 204552 -> 205416 bytes 10-build_abe-gdb/console.log.xz | Bin 39536 -> 39464 bytes 11-build_abe-qemu/console.log.xz | Bin 32016 -> 31416 bytes 12-check_regression/console.log.xz | Bin 3548 -> 3680 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 ++++++++-------- 19 files changed, 54 insertions(+), 54 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allyesconfig updated (5e9bd37aac -> 7d92db087b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allyesconfig in repository toolchain/ci/base-artifacts. from 5e9bd37aac 51: force: #529: 21031: Success after baseline build: no new [...] new 7d92db087b 52: force: #531: 21031: Success after baseline build: no new [...] 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 1752 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31840 -> 32116 bytes 04-build_kernel_llvm/console.log.xz | Bin 64968 -> 65208 bytes 05-build_abe-qemu/console.log.xz | Bin 31124 -> 31712 bytes 06-build_linux/console.log.xz | Bin 3812 -> 3820 bytes 08-check_regression/console.log.xz | Bin 2288 -> 2280 bytes dashboard/dashboard-generate.sh | 2 +- manifest.sh | 12 ++++++------ 9 files changed, 7 insertions(+), 7 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-lts-allyesconfig updated (3778abb98b -> 23d0762d18)

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-lts-allyesconfig in repository toolchain/ci/base-artifacts. from 3778abb98b 38: onsuccess: #413: all: Success after binutils/gcc/qemu: 2 [...] new 23d0762d18 39: onsuccess: #414: all: Success after binutils/gcc/linux: [...] 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 1772 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 30844 -> 30140 bytes 04-build_abe-stage1/console.log.xz | Bin 87664 -> 87076 bytes 05-build_abe-qemu/console.log.xz | Bin 31576 -> 31424 bytes 06-build_linux/console.log.xz | Bin 3484 -> 3448 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 3736 -> 3620 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +++++++++++++------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (909a5e2cc3 -> c9317b2082)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 909a5e2cc3 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] discards 1cd5937f83 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] discards 15237383c4 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards e5ecd2c38d 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards daa74a19cc 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards 495b94dc7d 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 29cb01e581 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards 6b26584580 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards de0ebea120 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards f6782dd1b3 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 4299e208f4 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 87f39a73d3 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards e2b8605f0b 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 995a0429b7 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards 5589973f3e 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 213fcc1b08 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards 8523cb7893 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 43959548d0 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards e881c0dce6 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 0c4d8b9acf 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 4b5244a9b9 127: onsuccess: #874: 1: Success after linux: 219 commits discards 95d2668515 126: onsuccess: #873: 1: Success after glibc: 2 commits discards eaa94e2133 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 40711cbe96 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards c86c76237f 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards 1c7d6343cd 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards 691937f356 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards d63ad49690 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards c9fca99108 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards fd589f0ac3 118: onsuccess: #863: 1: Success after linux: 12 commits discards 63475c6bee 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 90cbbae1e1 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 7df87d2328 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 8d293d9741 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards cbf62e31da 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards d4025bc1fc 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards c1caeebd8c 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 63c562f5be 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 76f081d3f8 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards 432681c08b 108: onsuccess: #850: 1: Success after gcc: 2 commits discards c6cc3b144d 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 2dd1569fad 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards 8f4c4661f1 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards 8a93261383 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 3aedfadf37 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 3295483c9c 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 07d9239765 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards f5b26b169f 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards ea518265e8 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards c2b3e2aa8e 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 00e3de8ad3 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards d78cb541c1 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards f80cdc0b18 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 8cf88fd87d 94: onsuccess: #832: 1: Success after binutils: 5 commits discards b7de52b187 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 97913fb77e 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards effd8e2dcc 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 423c29c10f 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards c473832f3b 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 4edd2e5dc3 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards ccd39e5a9a 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards cab312206b 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 13efa39ca1 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards eef123e276 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 72fde0fc9b 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards d8f5a7426a 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards b2892fdd17 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 7dd7365689 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 6387a4486d 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 2def7e5b61 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 57998df50e 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 6e65ca6890 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards b2f956463c 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 266a0fe377 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards b781431715 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 30967ee1fb 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 139ca3cb2e 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 30fd7fd0ad 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards d3f3dd0643 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards e7f32a873a 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 3710304143 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 1c29144bda 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards c3537b1463 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 2968957363 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 613b6f9240 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards a42cbcaa14 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards bb5dd26e26 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 62f8952cb9 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards bbb29f026e 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards c763cb8cbc 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards b2f0d72488 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards fd82b387d7 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 7019ac1d36 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards ddca3fbd7d 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards fbb70e1468 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 4f3d06fa26 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards 7d1de8d0da 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards a9eea1a37c 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 29c09ebead 49: onsuccess: #785: 1: Success after binutils: 12 commits discards f62aa4ed68 48: onsuccess: #782: 1: Success after binutils: 8 commits discards acf65adf88 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new 8c82acebb2 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new 54d310815f 48: onsuccess: #782: 1: Success after binutils: 8 commits new 1baa0788d1 49: onsuccess: #785: 1: Success after binutils: 12 commits new 176019d2d6 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new dbcfba8080 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new 26b8245f25 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new 7744c6ece2 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new edcb33eecc 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 1922da90ea 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 2418a9414d 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new fd03b85701 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new 43780e2e18 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 7d1f2bebbd 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new a154b76fa0 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 797b378d45 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new f3243a1805 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new b56d8cb5e1 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 3ee565bcce 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 53a147ec95 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new f9c926e7eb 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new fb09c2e8eb 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new f378e378df 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new c5bb0e5854 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new c77beafd34 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 1f221a5a64 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 855b7e82cb 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 2b4f05e608 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 588b602915 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 89da1e68d2 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 88f2aebfa8 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new fdba836102 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 719144053d 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new da34aa03a7 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new c61b662d8b 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 21e2feba74 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new 9ba4021b93 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 6a30f65e73 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 5ebca48324 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 6fb9842ac5 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 077d6224ce 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new f6013b5ff5 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 9d95c046ef 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 91c8e65f72 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 73f165a61d 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 2938802beb 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 0473850d72 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new c0432df23a 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 2f72f6d102 94: onsuccess: #832: 1: Success after binutils: 5 commits new 6a0d7e9ef6 95: onsuccess: #835: 1: Success after binutils: 3 commits new 150a20862b 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new ad77844c70 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 79bcf39199 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new c309faa0e5 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new bee0849850 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 7b2349db23 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 660e3dc5b0 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 00e824d288 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new cde73792b6 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 4e5f028922 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 661b36c595 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 0756698898 107: onsuccess: #849: 1: Success after binutils: 5 commits new 8893f5a10b 108: onsuccess: #850: 1: Success after gcc: 2 commits new e8d5e1f4c9 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 42be4ac336 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 4c8cb2fe13 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new fee1892c9f 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new e16d09eee6 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new 55fbca9f28 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new 048e974d7c 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 49a341010f 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new ad4e42dbee 117: onsuccess: #861: 1: Success after binutils: 18 commits new 3be6490eb5 118: onsuccess: #863: 1: Success after linux: 12 commits new 1ebd91c3bd 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new b4c23c0a66 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new fd47b85d28 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new a11852cd0d 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new a4a50cb323 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 8fb8546ded 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new ed0b3b9d1d 125: onsuccess: #871: 1: Success after binutils: 26 commits new d76d061e89 126: onsuccess: #873: 1: Success after glibc: 2 commits new 5989b3d373 127: onsuccess: #874: 1: Success after linux: 219 commits new 804029df2b 128: onsuccess: #876: 1: Success after binutils: 12 commits new e8723433b2 129: onsuccess: #878: 1: Success after linux: 3008 commits new 2ad382cbdb 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new c3ae617bd2 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new c2f45ce419 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new a55fd06101 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 2f2e994899 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new f0d204bbc9 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new 61feb5c3fb 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new d9d036227f 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new f0468aefd0 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new da24daa9c7 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new bca677ab85 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new d11387d00f 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new 3685c3167b 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 2737191146 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new 709cf9e784 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new d8254c9638 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 8cc66b449e 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] new d73f0f5785 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] new c9317b2082 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] 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 (909a5e2cc3) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1748 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 40144 -> 39768 bytes 04-build_abe-gcc/console.log.xz | Bin 214096 -> 216332 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9080 -> 8688 bytes 07-build_abe-glibc/console.log.xz | Bin 244620 -> 246148 bytes 08-build_abe-gdb/console.log.xz | Bin 39664 -> 39808 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3880 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3020 -> 3140 bytes 11-check_regression/console.log.xz | Bin 5812 -> 5984 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 44 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- sumfiles/g++.log.xz | Bin 3776248 -> 3740940 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 3301752 -> 3335600 bytes sumfiles/gcc.sum | 4730 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1095552 -> 1079556 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2276 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232984 -> 232056 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 459740 -> 459468 bytes sumfiles/libstdc++.sum | 12 +- 37 files changed, 2531 insertions(+), 2533 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[linux] branch master updated (e4cf7c25bae5 -> 150aae354b81)

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 linux. from e4cf7c25bae5 Merge tag 'kbuild-fixes-v6.2' of git://git.kernel.org/pub/ [...] new c5bc07366820 drm/i915: fix TLB invalidation for Gen12.50 video and comp [...] new fff758698842 drm/i915: Remove __maybe_unused from mtl_info new 3f882f2d4f68 drm/i915: improve the catch-all evict to handle lock contention new 11ce8fd8fd87 drm/i915/uc: Fix two issues with over-size firmware files new 963bbdb32b47 drm/i915/dsi: add support for ICL+ native MIPI GPIO sequence new 6217e9f05a74 drm/i915/dsi: fix MIPI_BKLT_EN_1 native GPIO index new a9f5a752e86f Merge tag 'drm-intel-fixes-2022-12-30' of git://anongit.fr [...] new 8b41948296b7 Merge tag 'drm-fixes-2023-01-01' of git://anongit.freedesk [...] new 1c0908d8e441 rtmutex: Add acquire semantics for rtmutex lock acquisitio [...] new 94cd8fa09f5f futex: Fix futex_waitv() hrtimer debug object leak on kcal [...] new 95d248d16f9c Merge tag 'locking_urgent_for_v6.2_rc2' of git://git.kerne [...] new ade8c20847fc x86/calldepth: Fix incorrect init section references new 1993bf97992d x86/kprobes: Fix kprobes instruction boudary check with CO [...] new 63dc6325ff41 x86/kprobes: Fix optprobe optimization check with CONFIG_RETHUNK new 5b129817aedb Merge tag 'x86_urgent_for_v6.2_rc2' of git://git.kernel.or [...] new e2d371484653 perf core: Return error pointer if inherit_event() fails t [...] new f841b682baef perf/core: Fix cgroup events tracking new 08245672cdc6 perf/x86/amd: fix potential integer overflow on shift of a int new a551844e345b perf: Fix use-after-free in error path new 0a041ebca495 perf/core: Call LSM hook after copying perf_event_attr new 150aae354b81 Merge tag 'perf_urgent_for_v6.2_rc2' of git://git.kernel.o [...] The 21 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: arch/x86/events/amd/core.c | 2 +- arch/x86/kernel/callthunks.c | 4 +- arch/x86/kernel/kprobes/core.c | 10 ++- arch/x86/kernel/kprobes/opt.c | 28 +++----- drivers/gpu/drm/i915/display/intel_dsi_vbt.c | 94 ++++++++++++++++++++++++- drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 59 +++++++++++++--- drivers/gpu/drm/i915/gem/i915_gem_mman.c | 2 +- drivers/gpu/drm/i915/gt/intel_gt.c | 8 ++- drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c | 42 +++++++---- drivers/gpu/drm/i915/i915_gem_evict.c | 37 +++++++--- drivers/gpu/drm/i915/i915_gem_evict.h | 4 +- drivers/gpu/drm/i915/i915_irq.c | 3 + drivers/gpu/drm/i915/i915_pci.c | 1 - drivers/gpu/drm/i915/i915_reg.h | 1 + drivers/gpu/drm/i915/i915_vma.c | 2 +- drivers/gpu/drm/i915/selftests/i915_gem_evict.c | 4 +- kernel/events/core.c | 54 +++++--------- kernel/futex/syscalls.c | 11 +-- kernel/locking/rtmutex.c | 55 ++++++++++++--- kernel/locking/rtmutex_api.c | 6 +- 20 files changed, 303 insertions(+), 124 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allyesconfig updated (b8c224ae4a -> 119a1e11b5)

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-stable-allyesconfig in repository toolchain/ci/base-artifacts. from b8c224ae4a 37: onsuccess: #509: 33: Success after binutils/gcc/qemu: 18 [...] new 119a1e11b5 38: onsuccess: #510: 33: Success after binutils/gcc/linux: 1 [...] 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 1744 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 32196 -> 32416 bytes 04-build_abe-stage1/console.log.xz | Bin 74252 -> 74024 bytes 05-build_abe-qemu/console.log.xz | Bin 32152 -> 31656 bytes 06-build_linux/console.log.xz | Bin 4948 -> 5644 bytes 08-check_regression/console.log.xz | Bin 3936 -> 3892 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +++++++++++++------------- 15 files changed, 20 insertions(+), 20 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits January 2023