Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (9db9947250e -> d5733ae194e)

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 9db9947250e 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards e7ffd6075cb 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards f6e2a5ba4ac 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 1dc099777e3 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards b737eeb7c8b 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 9dc9a9658ec 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards a76701ad4cb 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards add9779cd1e 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards b45599a0356 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 8c56c204d40 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 6332d559124 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] discards 4507c5bd915 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] discards bdd1826a153 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 64cb2fd63ad 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards dbf2a83a5a6 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 5554b34b4b5 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 0402ff47c46 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards e6b73a9fbee 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 0f49cbfdbe9 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 467e89412b4 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 9ed9c077796 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 418e239be24 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] discards 1c66282d3af 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] discards 2bc8b6c7cfc 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] discards 406cba70194 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards ffe4f58cec5 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] discards 12fc42f8fea 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] discards 8ac03caa66c 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] discards e1b14757edc 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards 37c47d71d50 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] discards 1c3d83ead46 92: onsuccess: #575: 1: Success after linux: 34 commits discards 604d2dafe22 91: onsuccess: #574: 1: Success after glibc: 3 commits discards ae10f32a210 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 917ce7be524 89: onsuccess: #570: 1: Success after linux: 11 commits discards 3c61ea3a814 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 6af2edfabb0 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 5d69159c26a 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 2ca3b5c626d 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards ec53af3b193 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 34cfb0ec6f1 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] discards e47afd3f071 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] discards 5b439773e09 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 307b7219e5a 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] discards c47da6dc0e5 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] discards 3c8ed76cbad 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] discards 84a1041dd5a 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] discards 2565c122092 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] discards 1ec01b0e5df 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] discards d092b1277ad 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] discards 9c8dad0343f 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards b3ccbdd733f 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 172441ec5c7 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] discards d060ad86157 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards b6a45c046e2 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] discards 61617b7cc58 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] discards c4d953835d1 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] discards 08eb0557bec 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 71a862f50db 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] discards cf77f387283 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 21aed2184e9 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards 58033a75abb 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards 4422ffcbc5e 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 8e5e0dd46b5 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] discards a94b8288266 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards 0f6226df876 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards 704765f6ef6 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] discards cf9a6e3e086 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards ed87f331131 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 92fce90c599 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] discards 4f54f5a902a 53: onsuccess: #531: 1: Success after binutils: 12 commits discards e6c7eb22f62 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 2d39c55c2d4 51: onsuccess: #525: 1: Success after binutils: 8 commits discards db930204eee 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] discards 9541f98ab7c 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] discards f93eda94fbb 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] discards 829ecf11bbc 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] discards c9178d3a0c6 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] discards 2b35bb7494b 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] discards b45cf3d11b0 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] discards 2f0fb84f753 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] discards a6f03da4098 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] discards 6fa91217741 41: onsuccess: #514: 1: Success after linux: 64 commits discards ca7317baf03 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] discards f90ce046e11 39: onsuccess: #511: 1: Success after binutils: 8 commits discards a21a87a4284 38: onsuccess: #508: 1: Success after binutils: 3 commits discards d9a3a1d3454 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] discards eded03ed33c 36: onsuccess: #505: 1: Success after glibc: 3 commits discards b64501ae415 35: onsuccess: #503: 1: Success after binutils: 11 commits discards 95d662d05fa 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards 5fd1433ca2a 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gd [...] discards a40c0d77f06 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] discards b7d055dc08e 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] discards 86605ef381c 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards 9f5e748f745 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards b2b81e308ae 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gd [...] discards 4e745b76c75 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] discards dea1f443d4e 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gl [...] discards 22c023c952f 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] discards 2961f6090e5 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards 0e922d9b48f 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards a81d02c10af 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 33e0a47bec4 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new cf39008e47b 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 464629b5344 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 12e4fb305b5 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] new bdf19084439 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gl [...] new ce9c16ebc47 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] new f08506e34d1 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gd [...] new f5fdf922d82 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new 4fc7e7aa0c9 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new 87e709f7b59 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] new 06b01c037fe 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] new 76fea6e2ae7 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gd [...] new 03400e78073 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new b6a2c3db698 35: onsuccess: #503: 1: Success after binutils: 11 commits new 1f979ff6bdd 36: onsuccess: #505: 1: Success after glibc: 3 commits new 771aee31a2f 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] new 91eb3614579 38: onsuccess: #508: 1: Success after binutils: 3 commits new 01dbef043c4 39: onsuccess: #511: 1: Success after binutils: 8 commits new fc3abe0e0d3 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] new 95896bb389d 41: onsuccess: #514: 1: Success after linux: 64 commits new 35a1ecec2b3 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] new ffa2ecc60ce 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] new fdea9b36c9d 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] new 9eec417a213 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] new 93a8a055ba9 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] new b641a552ae4 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] new a299c3682ab 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] new 5a8aa31ee2c 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] new aa4407da74a 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] new 94a20aed4cb 51: onsuccess: #525: 1: Success after binutils: 8 commits new 7e498ce6fb7 52: onsuccess: #528: 1: Success after binutils: 8 commits new 9b149b9b22e 53: onsuccess: #531: 1: Success after binutils: 12 commits new 22087a8c1f9 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] new 3c6957339e5 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new 291014b5cab 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new 553ad5312ea 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] new 662d306dafc 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new 8fa7e0f917e 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new e518bec443f 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] new 323e08e4846 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new 4610ba62fc2 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new 52afef092ec 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 0f97d0ad54c 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 8956d56a863 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] new 44030751e59 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new ae94b6c6532 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] new 3623f60d081 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] new 4f4683521bb 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] new ac15035b04e 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 499c9192bda 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] new cfb8fc0a2aa 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 6b785f82ad7 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 01ccaf81f76 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] new 70841615015 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] new 2f0c261b388 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] new dbe61bf5441 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] new ac5812cfe81 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] new 0267bc27582 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] new 4015811888e 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] new bae1518eed9 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 23eb071025d 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] new 68575b34c91 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] new b574d126725 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new debd0d413c3 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new 21e1fca7a72 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new 9593da8afdf 87: onsuccess: #567: 1: Success after binutils: 8 commits new 5b5728c48e4 88: onsuccess: #569: 1: Success after glibc: 10 commits new 5f71bd2ed79 89: onsuccess: #570: 1: Success after linux: 11 commits new 9541e141776 90: onsuccess: #572: 1: Success after binutils: 15 commits new 714d00e82c7 91: onsuccess: #574: 1: Success after glibc: 3 commits new fb7afc7cab4 92: onsuccess: #575: 1: Success after linux: 34 commits new b23c726d2b3 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] new 780da9846e7 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new 053f793bd49 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] new 07279f43de7 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] new 4197b2bc9bb 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] new 9b0cd10831b 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new 3545ee1d786 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] new d31de5c247f 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] new 8d4d677375d 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] new add0680b27c 102: onsuccess: #586: 1: Success after binutils: 5 commits new 9a2ff565c22 103: onsuccess: #589: 1: Success after binutils: 3 commits new 5f0cba53c91 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new a9cc642f6f8 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new bc64ea223d3 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new d682acf426d 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 5f4b7c73289 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 2fd1a69d195 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new a59c2a0f4eb 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new fd207b85447 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new c845956568d 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new 6244a18af6c 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new a852f0da36e 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 35ab766ba83 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 96bc241bf07 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new ed389fba92e 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new 29d27c10026 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 8e1dc9e96a5 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 0a8a150235d 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new f51e50caa6a 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 8dddfdceea1 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new d5733ae194e 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (9db9947250e) \ 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 1788 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 53680 -> 53144 bytes 04-build_abe-gcc/console.log.xz | Bin 237236 -> 235616 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8620 -> 8816 bytes 07-build_abe-glibc/console.log.xz | Bin 236696 -> 236800 bytes 08-build_abe-gdb/console.log.xz | Bin 51188 -> 50872 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3816 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2460 -> 2140 bytes 11-check_regression/console.log.xz | Bin 16968 -> 15532 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 37 +- 11-check_regression/mail-body.txt | 158 +- 11-check_regression/results.compare | 78 +- 11-check_regression/results.compare2 | 4184 +++++++------- 11-check_regression/results.regressions | 78 +- 12-update_baseline/console.log | 34 +- 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 | 160 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 78 +- sumfiles/gdb.log.xz | Bin 1728696 -> 1706316 bytes sumfiles/gdb.sum | 8980 ++++++++++++++++--------------- 30 files changed, 6956 insertions(+), 6879 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-master-aarch64-lts-defconfig updated (e4e2af0c014 -> c9784a189cc)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-defconfig in repository toolchain/ci/base-artifacts. from e4e2af0c014 25: onsuccess: #475: boot: Success after binutils/llvm/linu [...] new c9784a189cc 26: onsuccess: #477: boot: Success after binutils: 86 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 1700 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 32888 -> 31496 bytes 04-build_kernel_llvm/console.log.xz | Bin 66384 -> 66852 bytes 05-build_abe-qemu/console.log.xz | Bin 31040 -> 31184 bytes 06-build_linux/console.log.xz | Bin 3460 -> 3496 bytes 07-boot_linux/console.log.xz | Bin 6060 -> 6064 bytes 08-check_regression/console.log.xz | Bin 4280 -> 2912 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 25 +++++++++++-------------- 15 files changed, 20 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[gcc] branch devel/modula-2 updated (e171e6b291b -> 071c72a9e43)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch devel/modula-2 in repository gcc. from e171e6b291b PR-107959 bugfix ICE detect attempt to create aggregate con [...] new 071c72a9e43 Bugfix the scope name when generating constants. 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/m2/gm2-compiler/M2Quads.mod | 60 +++++++++++++++++------------------ gcc/m2/gm2-compiler/M2Scope.mod | 64 ++++++++++++++++++++++---------------- gcc/m2/gm2-compiler/P0SymBuild.mod | 5 ++- gcc/m2/gm2-compiler/P3Build.bnf | 3 +- 4 files changed, 70 insertions(+), 62 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-master-aarch64-lts-allnoconfig updated (9832690ac1a -> 16e1dfe3d80)

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-lts-allnoconfig in repository toolchain/ci/base-artifacts. from 9832690ac1a 25: onsuccess: #467: boot: Success after binutils/gcc/linux [...] new 16e1dfe3d80 26: onsuccess: #468: boot: 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 1708 -> 1960 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 32776 -> 31816 bytes 04-build_abe-stage1/console.log.xz | Bin 72988 -> 73496 bytes 05-build_abe-qemu/console.log.xz | Bin 31152 -> 31092 bytes 06-build_linux/console.log.xz | Bin 3304 -> 3332 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4248 -> 3940 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 ++++++++++++++-------------- 16 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_gnu_native_check_gcc/master-aarch64 updated (553897ab6da -> 82dbb614d0a)

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 553897ab6da 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards 659901d58c2 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards a1a9123d644 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards ff7cdfc7ff2 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 6231c960ef5 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 4886d62146e 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards c914e298c28 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 877c8890f73 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 89a121cc995 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 25dc23d4f7d 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards d4efb85deae 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards f6bbb4f12f0 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards 6a616932d16 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards fe9cdd413ee 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards 1f115a16f52 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards cd0466b3775 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards ce983730a19 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards be4228f6dbd 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 7dfe958af2b 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards e7e17115d0e 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards 5167e2948b9 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 9721b2a0937 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 7338bee3d02 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards d643ffbb0b2 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards fb017fed64a 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 8bc3b163e7f 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 0c505f461a6 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 7cf37fc1159 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards 1f5fe0a2c86 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 60b9e55573f 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards 7d1ec89079f 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards ebb7c076730 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 713363f5a5a 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 7ff5b5fc70e 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards 101cd347570 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards d43364c8e2b 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards 8ecca586e3c 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards 0ce889acbff 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards f7129520eeb 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards c671bf2d9b4 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 641aa0620c2 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards 596091df02a 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 11e6d81d2be 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards fa1362fa339 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards f7de8b9e053 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards b56de458998 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards a564f324361 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards c464205e727 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards 9a11d5b8b68 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards 60a86100e98 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards b3a5b3583e3 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards 14264ccda23 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 2efa6cd1999 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards e579b94f960 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards 8dac2e6d07d 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 693f81b0295 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards f4c912c12f7 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 5313151b028 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards 6c46a22f73c 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards 6396ed53bfc 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards b7adfecf8a5 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards a55ec0eea54 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards 13622d34241 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards b0925549518 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards fe799104474 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards 3446ca76938 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards 03348761c2f 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 64796ed644e 48: onsuccess: #782: 1: Success after binutils: 8 commits discards c83b0be18e2 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards d696b70daed 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards 4144f4318db 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards e7c3358664a 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards 42a8986985f 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards 0e9cbdc3fc8 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards 858ee4ab849 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards 1b794365c6d 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards d03968308cb 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards 3be0a957867 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards bd6c4e41403 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards f7df3f14c8b 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 283c5537bf1 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards 1c5eee00c4e 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards d526c6a3114 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards 915dc99bb51 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards cdbe79ed055 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards e1486c3c091 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards cebf8397443 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards 5f091743054 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards 46b144f2abf 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] discards 8e2b95a2ab7 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] discards 0e4daeb225a 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] discards 90489edcc1e 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards d02970d7f9d 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 8588424e3d0 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards fd444438d64 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 6dc9259a13e 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards d779adef483 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 91b564c964a 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 8c23f9840b0 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 732b8114e92 16: onsuccess: 1: Successful build after binutils: 4 commits discards d98ac7b5b81 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 4161f4b4990 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 78cb71c784d 16: onsuccess: 1: Successful build after binutils: 4 commits new 8a4ecc86f94 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 6c797f2ac00 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 08a8ddbfb3d 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new df138a70b4d 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 777d861975b 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new eff85292727 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new d90340ceea9 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 9ec68d2ea88 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 777cdbbf12f 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] new fb68a452d5a 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new 0e87ddc9074 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new 93578d7f3ce 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new 36c09c6c299 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new 968d977eedc 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new 4d21927aef8 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new bb3a4b12e19 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new 5d7782eedab 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new 2554e2fe6e1 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new 14daeb25736 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new 69fb4c92101 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 13d1023d5de 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new 7c576a7b977 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new 85be3c9e363 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new 8c53ccd47f3 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new 620504ebb2a 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new f1fe2431b1c 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 72f728fa28b 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new a75cf98d046 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new 60ff1151463 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new 5d8eec88af3 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new c8bc4d56cf3 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new 5d7b11e24ea 48: onsuccess: #782: 1: Success after binutils: 8 commits new 9264faa73b0 49: onsuccess: #785: 1: Success after binutils: 12 commits new 1b7c51fe6dd 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new ddaeb4d267a 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new 1d56ce0d105 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new 5ad3e010580 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new 7f0a56b6d8b 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new fa59b7f566f 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new cc9871a3b2e 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 45ef188e309 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new 104a47d97f3 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new a92592654f9 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new c974dc6adb6 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new 846db273969 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 30832047039 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 14d130482f8 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 6434a14e1aa 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new fbaec5cce89 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 7be8a153092 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 7cfb3f8efa0 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new 3aff8928530 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new c40709a75a5 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new 0646de39afa 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new b2184566e74 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new a60d7898b2b 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new a3b14f88484 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new 3228046e5bf 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 8b74ca1eb51 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new 55248fe8325 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 137dfc1dc2f 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new 2d2a286d573 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new 13e6cdcb52c 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new 47e79572903 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new 17f8044ca79 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new 385fd6188a9 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new ad4713a7bc2 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 84fffef4c7e 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 1c53c1fd367 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new af91aaf8ab9 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new ac1003153b6 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new bf326ab5855 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new 7d84b89ce06 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new a9f4e26c6ed 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 66ea2eceff4 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new c6efa766566 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 4dac80139f6 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 4942667e380 94: onsuccess: #832: 1: Success after binutils: 5 commits new e52226e342f 95: onsuccess: #835: 1: Success after binutils: 3 commits new c6ffcb2fa1c 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 48ca6873dd3 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new 75ef36ded78 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 6d80d8725d9 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new a927713ddf9 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new 058c780d646 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new 789724a03a7 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 77c2166b351 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new d847130cf41 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new 38639a65436 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new d7115226963 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new ef2b9165701 107: onsuccess: #849: 1: Success after binutils: 5 commits new 84887dce84a 108: onsuccess: #850: 1: Success after gcc: 2 commits new 81500816d51 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new f9678737b00 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new a0f91f04750 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new a41fe8a6ed6 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new b6d2d6c6f6b 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new 27db290a0fe 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 8760c06b456 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 82dbb614d0a 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (553897ab6da) \ 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 1756 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 39320 -> 39056 bytes 04-build_abe-gcc/console.log.xz | Bin 213908 -> 214372 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8524 -> 8800 bytes 07-build_abe-glibc/console.log.xz | Bin 244744 -> 245628 bytes 08-build_abe-gdb/console.log.xz | Bin 39100 -> 38772 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3836 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3024 -> 2788 bytes 11-check_regression/console.log.xz | Bin 7580 -> 6152 bytes 11-check_regression/mail-body.txt | 42 - 11-check_regression/results.compare | 40 +- 11-check_regression/results.compare2 | 123 +- 12-update_baseline/console.log | 48 +- 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 | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- sumfiles/g++.log.xz | Bin 3739640 -> 3769508 bytes sumfiles/g++.sum | 141 +- sumfiles/gcc.log.xz | Bin 3295760 -> 3305656 bytes sumfiles/gcc.sum | 5120 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1078404 -> 1080036 bytes sumfiles/gfortran.sum | 94 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2272 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 230948 -> 231932 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 451980 -> 453412 bytes sumfiles/libstdc++.sum | 10 +- 38 files changed, 2801 insertions(+), 2933 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_cross_check_gcc/master-arm updated (d5ee6079351 -> a6199e3b0eb)

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 d5ee6079351 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards 0f8177169ca 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards 4710314b49a 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards 36a18eabbbb 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 8925d35e7fb 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards a11e3fa465a 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 601ae8b8e68 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards aefe76876a9 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards 94b41893ff3 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards aca584e8cd9 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards 028706a9f53 194: onsuccess: #1995: 1: Success after linux: 517 commits discards e6266278aba 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 6549199210e 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards 3283bc82586 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards 3411394b65d 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards 9180933d312 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards 8e4dd236f6a 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards 286e2acec93 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards bb1d43114ea 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards 0fc93c7daab 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards 5d291b385f9 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards c21143c79cf 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards 006f4741437 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards b48e600079d 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards 14840d10696 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards 49812204363 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards da224c2d9f7 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards 0bb82089f2f 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards 6c8d7c407b0 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards 5f250333fb0 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards 43d0fc1f800 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards c0ecc6916e0 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards 49f75e5035d 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards 915030173c5 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards 2e660dbf07e 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards ab749d2c9f2 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards 732951a62a9 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards d5fefc2a98a 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards 15a0342147f 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards 52174d11a3c 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards a34c6ef6cca 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards 64010928414 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 95dfabf6019 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards baa007db1c5 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards ff2f483a590 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards 544108404a0 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards d26a9f728e0 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards d849b57fd97 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards 00781161255 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 81c06cb3175 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards 6df43c0609c 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 3fd59454612 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 54d90205bc7 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards 4a77ae27c94 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards 3fef091aa50 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards 8930c26bd79 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards d3519a8fae0 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards 251b93d7294 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards bc0ff329bf4 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards b781efa3451 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards 39ea47b24ea 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 24b7650b403 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards 3c111697a77 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards fb123cc2e1f 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards 3b7f82a508e 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards 45de75506a6 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards 554ef4826e9 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards 1740955380d 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards f8350af317d 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards a60701c1d6e 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 7d3db76d338 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards cd94950c266 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards 383c2dd25b8 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] discards 86129a36b4e 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] discards 6ac87e913dc 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 2d2c032a7d7 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] discards bf4ef2923a5 128: onsuccess: #1723: 1: Success after linux: 12 commits discards f4c06da0285 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] discards 22b474441d7 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 06907812d85 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] discards 032282a61bd 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards df360c70027 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] discards 64664ceb655 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] discards f0c4e72f2cd 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] discards 46e17865c22 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] discards 9481b8f8df5 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] discards e597713fa0e 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] discards 34c6ed1de52 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] discards 5e5201b17e5 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] discards 61ef0113af1 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] discards 69fb5e846ef 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 47c88926839 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] discards c27d63c6cb0 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] discards 27da207dac4 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] discards 83f7638bc32 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 842535b98d1 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 [...] discards 282e475aac0 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 [...] discards f8ff3de59e9 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/ [...] discards 2b3088e7d77 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/ [...] discards 4e4395e9d97 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38edde [...] discards 47fd8c263e7 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 532bc0109ec 104: onsuccess: #1697: 1: Success after gcc: 4 commits new a2938eda479 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38edde [...] new 3adc14c5af4 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/ [...] new 1da6e566b4a 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/ [...] new d1e61369527 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 [...] new b54854011b4 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 [...] new 53bf5277fcd 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 39fc3530a0c 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] new 9572a4ad71f 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] new 1472e198a41 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] new 4f2d7c610a2 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new ad3752b2572 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] new f258aaf9dcf 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] new a1713e97623 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] new a5fbf123d99 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] new d215436795f 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] new 0bd2115b3b6 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] new 94adff5ebcd 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] new 0e21556e7f4 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] new 866041db85b 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] new f09b988f96b 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 185e94b8354 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] new 22831070a5a 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new e850d19fbd0 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] new 392b73f410d 128: onsuccess: #1723: 1: Success after linux: 12 commits new b57afd2e65d 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] new 0556e6888c0 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new f1d8cbfed26 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new 2c8c0859a9f 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new fb0b6a2ee76 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new f48ce9ce1c8 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 3a8a16d5e67 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 30851602199 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new 31f1ad2314c 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 28b612743ec 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new a43426d8808 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new 4adcd620141 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new 950aad31a21 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new fadb489a2fc 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new bce59fd7791 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 82e4d1aa8d4 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 06a742dc2b5 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new 61ea76cbcff 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new 416fac0bdb4 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new b33f245a5cb 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new 4a50778a778 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new b7e49e94564 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new 2f597d1c983 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new 194e2feedc8 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new 8237a25c5e2 153: onsuccess: #1754: 1: Success after gcc: 2 commits new daa945f696d 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 59bb54d723c 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new b023ebc96d4 156: onsuccess: #1757: 1: Success after gcc: 4 commits new b796222fcd1 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new 0712f787544 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new b72b882c19f 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new 2a022636507 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new 9541069843a 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new 66d65292d24 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new 50386a15c4c 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new aecb5fb0318 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new 65a9940cc93 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new f1e45e70cdf 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new a4294767c5a 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new 664692e4ae3 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new c15afe65490 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new 0e6dd9a57d0 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new 822ab65e0c8 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new e933bb6a87f 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new f1a5770e2af 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new 21bb7e8dcec 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new e223b346bfe 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new 6c7b9804ebb 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new 5addbc3620d 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new 0762879ab21 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new 354f22044c4 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new 954f542b87b 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new 0fd9a527114 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new 0539bb852e0 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new a42501e5351 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new e1845eeb010 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new e0fe0ecddf2 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new 442e16d9a7c 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new 77a23577199 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new 598e173a5d7 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new 956042c36de 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new 91c21c745ca 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new c2696205774 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new f83460f38c7 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new d9c55935616 193: onsuccess: #1992: 1: Success after binutils: 151 commits new a62c722c5ac 194: onsuccess: #1995: 1: Success after linux: 517 commits new 0299d6177b1 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new 0f38db5099c 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new 5f75ebc5721 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new 25749b4d728 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new f5602088301 199: onsuccess: #2000: 1: Success after gcc: 5 commits new e92084862bf 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new a2e2744b8fa 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new e87d1bdb10f 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new 0cc2ee1baa5 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new 4c495910780 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new a6199e3b0eb 205: onsuccess: #2006: 1: Success after gcc: 3 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 (d5ee6079351) \ 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 1740 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2812 bytes 03-build_abe-binutils/console.log.xz | Bin 31336 -> 32308 bytes 04-build_abe-stage1/console.log.xz | Bin 91304 -> 92468 bytes 06-build_abe-linux/console.log.xz | Bin 8660 -> 8724 bytes 07-build_abe-glibc/console.log.xz | Bin 235932 -> 237144 bytes 08-build_abe-stage2/console.log.xz | Bin 223788 -> 226908 bytes 09-build_abe-gdb/console.log.xz | Bin 38748 -> 39292 bytes 10-build_abe-qemu/console.log.xz | Bin 30368 -> 31496 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2436 -> 2696 bytes 13-check_regression/console.log.xz | Bin 5752 -> 6024 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 8 + 13-check_regression/mail-body.txt | 42 + 13-check_regression/results.compare | 37 +- 13-check_regression/results.compare2 | 49 +- 13-check_regression/results.regressions | 42 + 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 42 + sumfiles/g++.log.xz | Bin 2714912 -> 2713740 bytes sumfiles/g++.sum | 14 +- sumfiles/gcc.log.xz | Bin 2305304 -> 2313092 bytes sumfiles/gcc.sum | 2594 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 895992 -> 898692 bytes sumfiles/gfortran.sum | 68 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213028 -> 213180 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 425600 -> 440292 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 1646 insertions(+), 1409 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

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_llvm_apm/llvm-release-arm-spec2k6-Oz_LTO updated (47fb32550de -> 04479154ba5)

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_bmk_llvm_apm/llvm-release-arm-spec2k6-Oz_LTO in repository toolchain/ci/base-artifacts. from 47fb32550de 20: onsuccess: #106: 1: [TCWG CI] No change after binutils/ [...] new 04479154ba5 21: onsuccess: #109: 1: [TCWG CI] No change after binutils/ [...] 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 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 30012 -> 30468 bytes 04-build_abe-stage1/console.log.xz | Bin 87468 -> 87484 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-linux/console.log.xz | Bin 8656 -> 8688 bytes 07-build_abe-glibc/console.log.xz | Bin 229592 -> 230120 bytes 08-build_abe-stage2/console.log.xz | Bin 208168 -> 206820 bytes 09-build_llvm-true-false-/console.log.xz | Bin 61792 -> 62696 bytes 10-benchmark/benchmark-build.log | 102 +- 10-benchmark/benchmark.log | 100 +- 10-benchmark/console.log.xz | Bin 3900 -> 3852 bytes 11-check_regression/console.log.xz | Bin 7096 -> 7504 bytes .../csv-results-vs-first-1/perf.csv | 182 +- .../csv-results-vs-first-1/results.csv | 190 +- .../csv-results-vs-first-1/size.csv | 173180 ++++----- .../csv-results-vs-first-1/vect.csv | 12260 +- 11-check_regression/csv-results-vs-prev-0/perf.csv | 167 +- .../csv-results-vs-prev-0/results.csv | 893 +- 11-check_regression/csv-results-vs-prev-0/size.csv | 353980 +++++++++--------- 11-check_regression/csv-results-vs-prev-0/vect.csv | 12586 +- 11-check_regression/csv-results-vs-prev-1/perf.csv | 182 +- .../csv-results-vs-prev-1/results.csv | 190 +- 11-check_regression/csv-results-vs-prev-1/size.csv | 173180 ++++----- 11-check_regression/csv-results-vs-prev-1/vect.csv | 12260 +- 11-check_regression/results-vs-first-brief.csv | 40 +- 11-check_regression/results-vs-first-full.csv | 186 +- 11-check_regression/results-vs-first-internal.csv | 48 +- 11-check_regression/results-vs-first.csv | 48 +- 11-check_regression/results-vs-first.log | 894 +- 11-check_regression/results-vs-prev-brief.csv | 40 +- 11-check_regression/results-vs-prev-full.csv | 196 +- 11-check_regression/results-vs-prev-internal.csv | 48 +- 11-check_regression/results-vs-prev.csv | 48 +- 11-check_regression/results-vs-prev.log | 962 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 18 +- .../squad-vs-first/401.bzip2/results-metadata.json | 18 +- .../squad-vs-first/403.gcc/results-metadata.json | 18 +- .../squad-vs-first/429.mcf/results-metadata.json | 18 +- .../squad-vs-first/433.milc/results-metadata.json | 18 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 18 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../squad-vs-first/445.gobmk/results-metadata.json | 18 +- .../447.dealII/results-metadata.json | 18 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 18 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 18 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../squad-vs-first/456.hmmer/results-metadata.json | 18 +- .../squad-vs-first/458.sjeng/results-metadata.json | 18 +- .../462.libquantum/results-metadata.json | 18 +- .../464.h264ref/results-metadata.json | 18 +- .../squad-vs-first/470.lbm/results-metadata.json | 18 +- .../471.omnetpp/results-metadata.json | 18 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 18 +- .../482.sphinx3/results-metadata.json | 18 +- .../483.xalancbmk/results-metadata.json | 18 +- .../squad-vs-first/Mean/results-metadata.json | 18 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 82 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 50 +- mail/mail-body.txt | 50 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 1259332 -> 2646288 bytes save-temps/401.bzip2.tar.xz | Bin 92008 -> 243284 bytes save-temps/403.gcc.tar.xz | Bin 3536536 -> 6996296 bytes save-temps/410.bwaves.tar.xz | Bin 15240 -> 107112 bytes save-temps/416.gamess.tar.xz | Bin 4118768 -> 21432372 bytes save-temps/429.mcf.tar.xz | Bin 36544 -> 70156 bytes save-temps/433.milc.tar.xz | Bin 165368 -> 421756 bytes save-temps/434.zeusmp.tar.xz | Bin 126080 -> 1025228 bytes save-temps/435.gromacs.tar.xz | Bin 956692 -> 2678788 bytes save-temps/436.cactusADM.tar.xz | Bin 709776 -> 1798020 bytes save-temps/437.leslie3d.tar.xz | Bin 47112 -> 290888 bytes save-temps/444.namd.tar.xz | Bin 165180 -> 521928 bytes save-temps/445.gobmk.tar.xz | Bin 1836896 -> 2562484 bytes save-temps/447.dealII.tar.xz | Bin 6437144 -> 12582720 bytes save-temps/450.soplex.tar.xz | Bin 731120 -> 1331376 bytes save-temps/453.povray.tar.xz | Bin 1385108 -> 2606192 bytes save-temps/454.calculix.tar.xz | Bin 1233932 -> 4963408 bytes save-temps/456.hmmer.tar.xz | Bin 371356 -> 856092 bytes save-temps/458.sjeng.tar.xz | Bin 144080 -> 322192 bytes save-temps/459.GemsFDTD.tar.xz | Bin 150768 -> 904484 bytes save-temps/462.libquantum.tar.xz | Bin 62008 -> 137584 bytes save-temps/464.h264ref.tar.xz | Bin 556680 -> 2050556 bytes save-temps/465.tonto.tar.xz | Bin 2229060 -> 10743388 bytes save-temps/470.lbm.tar.xz | Bin 26824 -> 107576 bytes save-temps/471.omnetpp.tar.xz | Bin 1098832 -> 1474160 bytes save-temps/473.astar.tar.xz | Bin 89276 -> 153884 bytes save-temps/481.wrf.tar.xz | Bin 1593700 -> 11935268 bytes save-temps/482.sphinx3.tar.xz | Bin 248684 -> 578032 bytes save-temps/483.xalancbmk.tar.xz | Bin 11895996 -> 16441108 bytes 102 files changed, 371356 insertions(+), 371218 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_fast_check_gdb/master-aarch64 updated (4598c78cf74 -> 79df520ebaa)

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_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. from 4598c78cf74 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 79df520ebaa 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] 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 1728 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39444 -> 39372 bytes 04-build_abe-gcc/console.log.xz | Bin 212744 -> 215392 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8560 -> 8776 bytes 07-build_abe-glibc/console.log.xz | Bin 245912 -> 246712 bytes 08-build_abe-gdb/console.log.xz | Bin 40076 -> 39268 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3940 -> 3844 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2632 -> 2484 bytes 11-check_regression/console.log.xz | Bin 6088 -> 5700 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- 12-update_baseline/console.log | 9 --------- 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/gdb.log.xz | Bin 14640 -> 14644 bytes sumfiles/gdb.sum | 34 +++++++++++++++++----------------- 25 files changed, 46 insertions(+), 55 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-master-arm-lts-allmodconfig updated (c5534c03be4 -> 61eb6dd3c35)

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-arm-lts-allmodconfig in repository toolchain/ci/base-artifacts. from c5534c03be4 29: onsuccess: #490: 33: Success after binutils/gcc/linux/q [...] new 61eb6dd3c35 30: onsuccess: #491: 33: Success after binutils/gcc/qemu: 2 [...] 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 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 31616 -> 32036 bytes 04-build_abe-stage1/console.log.xz | Bin 90772 -> 92264 bytes 05-build_abe-qemu/console.log.xz | Bin 30668 -> 30672 bytes 06-build_linux/console.log.xz | Bin 5000 -> 5964 bytes 08-check_regression/console.log.xz | Bin 4256 -> 4028 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_gcc_check/master-arm updated (be8361e3f89 -> 8d671a23bf7)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-arm in repository toolchain/ci/base-artifacts. discards be8361e3f89 379: onsuccess: #2019: 1: Success after gcc: 3 commits discards 9a377feae29 378: onsuccess: #2018: 1: Success after binutils/gcc: 2 commits discards 06268fe3f33 377: onsuccess: #2017: 1: Success after binutils: 3 commits discards 9ec067ea911 376: onsuccess: #2016: 1: Success after basepoints/gcc-13-4 [...] discards ca4ca07c480 375: onsuccess: #2015: 1: Success after binutils/gcc: 4 commits discards f463cc641d2 374: onsuccess: #2014: 1: Success after binutils/gcc: 9 commits discards 23fd75840be 373: onsuccess: #2013: 1: Success after gcc: 6 commits discards e8637882add 372: onsuccess: #2012: 1: Success after binutils/gcc: 10 commits discards 4f69102a854 371: onsuccess: #2011: 1: Success after binutils/gcc: 6 commits discards 0ed365aafd5 370: onsuccess: #2010: 1: Success after binutils/gcc: 8 commits discards d99f7af1613 369: onsuccess: #2009: 1: Success after binutils/gcc: 21 commits discards 630b942d156 368: onsuccess: #2008: 1: Success after binutils/gcc: 10 commits discards a063f02aca3 367: onsuccess: #2007: 1: Success after binutils/gcc: 13 commits discards 0f50ed0c962 366: onsuccess: #2006: 1: Success after binutils/gcc: 11 commits discards 701bdd3156c 365: onsuccess: #2005: 1: Success after binutils/gcc: 45 commits discards 1633a3757f3 364: onsuccess: #2000: 1: Success after gcc: 5 commits discards 036bd9e9afe 363: onsuccess: #1999: 1: Success after binutils/gcc: 5 commits discards 28f09b2114f 362: onsuccess: #1998: 1: Success after binutils/gcc: 39 commits discards e247bd4e157 361: onsuccess: #1997: 1: Success after binutils/gcc: 24 commits discards f3ef3b20801 360: onsuccess: #1996: 1: Success after binutils/gcc: 47 commits discards 6c880e25f68 359: onsuccess: #1995: 1: Success after binutils/gcc: 8 commits discards 7b1f6777a14 358: onsuccess: #1994: 1: Success after binutils: 3 commits discards e06f166469e 357: onsuccess: #1993: 1: Success after gdb-12-branchpoint- [...] discards fd8deaa75a4 356: onsuccess: #1992: 1: Success after binutils/gcc: 2 commits discards 2ca6de27e91 355: onsuccess: #1991: 1: Success after basepoints/gcc-13-4 [...] discards a46a5aecf92 354: onsuccess: #1990: 1: Success after binutils: 4 commits discards 3f2e4096e49 353: onsuccess: #1989: 1: Success after binutils/gcc: 2 commits discards c22d1f9a844 352: onsuccess: #1988: 1: Success after basepoints/gcc-13-4 [...] discards 3dcf294291f 351: onsuccess: #1987: 1: Success after binutils/gcc: 9 commits discards 0b5c05519c8 350: onsuccess: #1986: 1: Success after gcc: 6 commits discards d2df48967fb 349: onsuccess: #1985: 1: Success after binutils/gcc: 5 commits discards 1e10f145f6f 348: onsuccess: #1984: 1: Success after gdb-12-branchpoint- [...] discards 487bdfe1f7f 347: onsuccess: #1983: 1: Success after binutils/gcc: 19 commits discards e24cfe8119d 346: onsuccess: #1982: 1: Success after binutils/gcc: 19 commits discards 4995f9ed71a 345: onsuccess: #1981: 1: Success after binutils/gcc: 8 commits discards 4b829a94c5d 344: onsuccess: #1980: 1: Success after gcc: 3 commits discards 12558f76e7f 343: onsuccess: #1979: 1: Success after binutils/gcc: 8 commits discards 84ed2d01c7a 342: onsuccess: #1978: 1: Success after binutils/gcc: 6 commits discards cfc379f1950 341: onsuccess: #1977: 1: Success after binutils/gcc: 14 commits discards f404e33bd89 340: onsuccess: #1976: 1: Success after binutils/gcc: 22 commits discards 4fb29c39357 339: onsuccess: #1975: 1: Success after binutils/gcc: 10 commits discards 7cf75c10d85 338: onsuccess: #1974: 1: Success after binutils/gcc: 5 commits discards 96c17945c70 337: onsuccess: #1973: 1: Success after binutils/gcc: 10 commits discards 55263003712 336: onsuccess: #1972: 1: Success after binutils/gcc: 11 commits discards 946016b4879 335: onsuccess: #1971: 1: Success after binutils/gcc: 14 commits discards e8aee40abdd 334: onsuccess: #1970: 1: Success after gcc: 20 commits discards eee319d1d13 333: onsuccess: #1969: 1: Success after binutils/gcc: 5 commits discards 1670e2dfd70 332: onsuccess: #1968: 1: Success after gcc: 3 commits discards 848d94ee532 331: onsuccess: #1967: 1: Success after binutils/gcc: 4 commits discards 61f6083fa88 330: onsuccess: #1966: 1: Success after binutils/gcc: 3 commits discards ccded3f86fa 329: onsuccess: #1965: 1: Success after gcc: 2 commits discards 6b156ac211a 328: onsuccess: #1964: 1: Success after binutils/gcc: 8 commits discards cc8d0989240 327: onsuccess: #1963: 1: Success after gcc: 3 commits discards 45121512634 326: onsuccess: #1962: 1: Success after binutils/gcc: 5 commits discards bfcdbbd7bbb 325: onsuccess: #1961: 1: Success after binutils/gcc: 16 commits discards 98921102331 324: onsuccess: #1960: 1: Success after binutils/gcc: 14 commits discards ac02efe8346 323: onsuccess: #1959: 1: Success after binutils/gcc: 11 commits discards 8fe1fbb23d4 322: onsuccess: #1957: 1: Success after binutils/gcc: 9 commits discards 7091b63fa1c 321: onsuccess: #1956: 1: Success after binutils/gcc: 12 commits discards 932f81a164c 320: onsuccess: #1955: 1: Success after binutils/gcc: 11 commits discards 0dd5d96f2dd 319: onsuccess: #1954: 1: Success after binutils/gcc: 9 commits discards 7e2edd99e2d 318: onsuccess: #1953: 1: Success after gcc: 11 commits discards 4b5dc9a1aa8 317: onsuccess: #1952: 1: Success after binutils/gcc: 22 commits discards 4e040598d05 316: onsuccess: #1951: 1: Success after binutils/gcc: 8 commits discards d5f2b19bbd3 315: onsuccess: #1950: 1: Success after basepoints/gcc-13-4 [...] discards d43c304c9d7 314: onsuccess: #1949: 1: Success after binutils/gcc: 17 commits discards 174a71454e7 313: onsuccess: #1948: 1: Success after binutils/gcc: 105 commits discards 1ecf299bcc3 312: onsuccess: #1947: 1: Success after gcc: 87 commits discards 09e8de18d73 311: onsuccess: #1945: 1: Success after binutils: 3 commits discards c9d7cea7ffa 310: onsuccess: #1941: 1: Success after binutils: 2 commits discards b83354cf606 309: onsuccess: #1938: 1: Success after gdb-12-branchpoint- [...] discards 66eed314964 308: onsuccess: #1934: 1: Success after gdb-12-branchpoint- [...] discards b9ade80dc2b 307: onsuccess: #1931: 1: Success after binutils: 2 commits discards 5181ddb9ae4 306: onsuccess: #1928: 1: Success after gdb-12-branchpoint- [...] discards aeab91aa714 305: onsuccess: #1926: 1: Success after binutils/gcc: 8 commits discards d532005ae4b 304: onsuccess: #1925: 1: Success after binutils/gcc: 21 commits discards 22485d7a89b 303: onsuccess: #1924: 1: Success after binutils/gcc: 23 commits discards 9ee88eb995d 302: onsuccess: #1923: 1: Success after binutils/gcc: 6 commits discards 4c93cc8c66e 301: onsuccess: #1922: 1: Success after binutils/gcc: 13 commits discards db27ee33d9f 300: onsuccess: #1921: 1: Success after binutils/gcc: 18 commits discards 0fbe41ed7c6 299: onsuccess: #1920: 1: Success after binutils/gcc: 12 commits discards 5289881a7d3 298: onsuccess: #1919: 1: Success after binutils/gcc: 7 commits discards 7bdcf8817eb 297: onsuccess: #1918: 1: Success after binutils/gcc: 12 commits discards 1f8a80a4949 296: onsuccess: #1917: 1: Success after binutils/gcc: 14 commits discards 5f720dff899 295: onsuccess: #1916: 1: Success after binutils/gcc: 29 commits discards 4e6e7ef35b1 294: onsuccess: #1915: 1: Success after binutils/gcc: 6 commits discards 1440c5960e6 293: onsuccess: #1914: 1: Success after binutils/gcc: 12 commits discards b3dddbd9ba3 292: onsuccess: #1913: 1: Success after binutils/gcc: 11 commits discards 2fdb136ac10 291: onsuccess: #1912: 1: Success after binutils/gcc: 30 commits discards e7aae9ff262 290: onsuccess: #1911: 1: Success after binutils/gcc: 15 commits discards 5becd09357e 289: onsuccess: #1910: 1: Success after binutils/gcc: 8 commits discards 0949858d5e2 288: onsuccess: #1909: 1: Success after binutils/gcc: 18 commits discards 122593ae157 287: onsuccess: #1908: 1: Success after gcc: 36 commits discards 6a7fef64c90 286: onsuccess: #1907: 1: Success after binutils/gcc: 8 commits discards 31903dead04 285: onsuccess: #1906: 1: Success after basepoints/gcc-13-3 [...] discards 3d4286c26a4 284: onsuccess: #1905: 1: Success after binutils/gcc: 8 commits discards 12f810ebfb7 283: onsuccess: #1904: 1: Success after basepoints/gcc-13-3 [...] discards ffbe773e6a8 282: onsuccess: #1903: 1: Success after binutils/gcc: 4 commits discards 5f5ee0de741 281: onsuccess: #1902: 1: Success after gcc: 2 commits discards 591086139ff 280: onsuccess: #1901: 1: Success after binutils/gcc: 10 commits discards a02fd4e817d 279: onsuccess: #1900: 1: Success after basepoints/gcc-13-3 [...] new 7acf92dcea3 279: onsuccess: #1900: 1: Success after basepoints/gcc-13-3 [...] new 0c692929641 280: onsuccess: #1901: 1: Success after binutils/gcc: 10 commits new b4c56b4b356 281: onsuccess: #1902: 1: Success after gcc: 2 commits new 8746ce19b03 282: onsuccess: #1903: 1: Success after binutils/gcc: 4 commits new 5126590e3b6 283: onsuccess: #1904: 1: Success after basepoints/gcc-13-3 [...] new 4840147326d 284: onsuccess: #1905: 1: Success after binutils/gcc: 8 commits new 83af28183d6 285: onsuccess: #1906: 1: Success after basepoints/gcc-13-3 [...] new f150513487f 286: onsuccess: #1907: 1: Success after binutils/gcc: 8 commits new 80d556bb967 287: onsuccess: #1908: 1: Success after gcc: 36 commits new af687120614 288: onsuccess: #1909: 1: Success after binutils/gcc: 18 commits new 840fda7c110 289: onsuccess: #1910: 1: Success after binutils/gcc: 8 commits new 53ba50abe60 290: onsuccess: #1911: 1: Success after binutils/gcc: 15 commits new 81710b40db6 291: onsuccess: #1912: 1: Success after binutils/gcc: 30 commits new b09c90975f0 292: onsuccess: #1913: 1: Success after binutils/gcc: 11 commits new a40ed8052c3 293: onsuccess: #1914: 1: Success after binutils/gcc: 12 commits new dd9cbe710a1 294: onsuccess: #1915: 1: Success after binutils/gcc: 6 commits new 2d421e67f78 295: onsuccess: #1916: 1: Success after binutils/gcc: 29 commits new cb6340d9645 296: onsuccess: #1917: 1: Success after binutils/gcc: 14 commits new 6dc27b4b0e0 297: onsuccess: #1918: 1: Success after binutils/gcc: 12 commits new c5faaf45a37 298: onsuccess: #1919: 1: Success after binutils/gcc: 7 commits new 4a7018175eb 299: onsuccess: #1920: 1: Success after binutils/gcc: 12 commits new 6cc00bde9e6 300: onsuccess: #1921: 1: Success after binutils/gcc: 18 commits new 15dc9f64c73 301: onsuccess: #1922: 1: Success after binutils/gcc: 13 commits new 45638a884f8 302: onsuccess: #1923: 1: Success after binutils/gcc: 6 commits new 5b5d6da9c3d 303: onsuccess: #1924: 1: Success after binutils/gcc: 23 commits new 16cf35d46ea 304: onsuccess: #1925: 1: Success after binutils/gcc: 21 commits new 80779947db8 305: onsuccess: #1926: 1: Success after binutils/gcc: 8 commits new 5bbbeefdef2 306: onsuccess: #1928: 1: Success after gdb-12-branchpoint- [...] new dd63f0eb176 307: onsuccess: #1931: 1: Success after binutils: 2 commits new 6b5836adfc1 308: onsuccess: #1934: 1: Success after gdb-12-branchpoint- [...] new 98934c2eba0 309: onsuccess: #1938: 1: Success after gdb-12-branchpoint- [...] new 813ce248b46 310: onsuccess: #1941: 1: Success after binutils: 2 commits new 347f627b9ab 311: onsuccess: #1945: 1: Success after binutils: 3 commits new 6c694a29853 312: onsuccess: #1947: 1: Success after gcc: 87 commits new c697fb26d93 313: onsuccess: #1948: 1: Success after binutils/gcc: 105 commits new 4716f3f837a 314: onsuccess: #1949: 1: Success after binutils/gcc: 17 commits new 9ac1e57ba0e 315: onsuccess: #1950: 1: Success after basepoints/gcc-13-4 [...] new 0d204db7325 316: onsuccess: #1951: 1: Success after binutils/gcc: 8 commits new da639cde32a 317: onsuccess: #1952: 1: Success after binutils/gcc: 22 commits new d767a7bcae9 318: onsuccess: #1953: 1: Success after gcc: 11 commits new cc152a320a6 319: onsuccess: #1954: 1: Success after binutils/gcc: 9 commits new f86e471634d 320: onsuccess: #1955: 1: Success after binutils/gcc: 11 commits new 13fc3378a7c 321: onsuccess: #1956: 1: Success after binutils/gcc: 12 commits new 542cca3b2a2 322: onsuccess: #1957: 1: Success after binutils/gcc: 9 commits new f6165206747 323: onsuccess: #1959: 1: Success after binutils/gcc: 11 commits new b32c87c9bb9 324: onsuccess: #1960: 1: Success after binutils/gcc: 14 commits new b4ec3e1fee7 325: onsuccess: #1961: 1: Success after binutils/gcc: 16 commits new a491b433b55 326: onsuccess: #1962: 1: Success after binutils/gcc: 5 commits new 1cf629ff4c4 327: onsuccess: #1963: 1: Success after gcc: 3 commits new cb23fc5b71a 328: onsuccess: #1964: 1: Success after binutils/gcc: 8 commits new 15f8043fc63 329: onsuccess: #1965: 1: Success after gcc: 2 commits new de0c49e7c52 330: onsuccess: #1966: 1: Success after binutils/gcc: 3 commits new 4bfe84efb39 331: onsuccess: #1967: 1: Success after binutils/gcc: 4 commits new 9ad5463bbba 332: onsuccess: #1968: 1: Success after gcc: 3 commits new 5d4798e3554 333: onsuccess: #1969: 1: Success after binutils/gcc: 5 commits new 25c976bfa25 334: onsuccess: #1970: 1: Success after gcc: 20 commits new 99218d3cf1d 335: onsuccess: #1971: 1: Success after binutils/gcc: 14 commits new 0ce306681a0 336: onsuccess: #1972: 1: Success after binutils/gcc: 11 commits new 222a65a65df 337: onsuccess: #1973: 1: Success after binutils/gcc: 10 commits new c021d9db191 338: onsuccess: #1974: 1: Success after binutils/gcc: 5 commits new d809e048345 339: onsuccess: #1975: 1: Success after binutils/gcc: 10 commits new 8510d73f1cb 340: onsuccess: #1976: 1: Success after binutils/gcc: 22 commits new f7edf524fb8 341: onsuccess: #1977: 1: Success after binutils/gcc: 14 commits new 2951cc61177 342: onsuccess: #1978: 1: Success after binutils/gcc: 6 commits new e5c9eae6266 343: onsuccess: #1979: 1: Success after binutils/gcc: 8 commits new 35b89f05c83 344: onsuccess: #1980: 1: Success after gcc: 3 commits new 35c44011b0e 345: onsuccess: #1981: 1: Success after binutils/gcc: 8 commits new 56f82e31831 346: onsuccess: #1982: 1: Success after binutils/gcc: 19 commits new a6959cd93c4 347: onsuccess: #1983: 1: Success after binutils/gcc: 19 commits new 6d6557166a3 348: onsuccess: #1984: 1: Success after gdb-12-branchpoint- [...] new 6af7f7425f2 349: onsuccess: #1985: 1: Success after binutils/gcc: 5 commits new ae053791e38 350: onsuccess: #1986: 1: Success after gcc: 6 commits new c951368eebb 351: onsuccess: #1987: 1: Success after binutils/gcc: 9 commits new fa6b0a0c066 352: onsuccess: #1988: 1: Success after basepoints/gcc-13-4 [...] new c7254493625 353: onsuccess: #1989: 1: Success after binutils/gcc: 2 commits new 569d3402bc0 354: onsuccess: #1990: 1: Success after binutils: 4 commits new 53c1797819f 355: onsuccess: #1991: 1: Success after basepoints/gcc-13-4 [...] new c58149b614d 356: onsuccess: #1992: 1: Success after binutils/gcc: 2 commits new 0ceaa8bf3f7 357: onsuccess: #1993: 1: Success after gdb-12-branchpoint- [...] new e9c20d9e55e 358: onsuccess: #1994: 1: Success after binutils: 3 commits new 1cf055c8b65 359: onsuccess: #1995: 1: Success after binutils/gcc: 8 commits new a51e273af7e 360: onsuccess: #1996: 1: Success after binutils/gcc: 47 commits new 8144a1bee75 361: onsuccess: #1997: 1: Success after binutils/gcc: 24 commits new 58880288632 362: onsuccess: #1998: 1: Success after binutils/gcc: 39 commits new fe7e4248ec8 363: onsuccess: #1999: 1: Success after binutils/gcc: 5 commits new 1c9e68aaa7f 364: onsuccess: #2000: 1: Success after gcc: 5 commits new 47ea41aabaa 365: onsuccess: #2005: 1: Success after binutils/gcc: 45 commits new 3b440c41f85 366: onsuccess: #2006: 1: Success after binutils/gcc: 11 commits new c8c956d520c 367: onsuccess: #2007: 1: Success after binutils/gcc: 13 commits new 9e74098aaca 368: onsuccess: #2008: 1: Success after binutils/gcc: 10 commits new 05d7d2ec22e 369: onsuccess: #2009: 1: Success after binutils/gcc: 21 commits new 9a4746ad085 370: onsuccess: #2010: 1: Success after binutils/gcc: 8 commits new 0d01b1c1140 371: onsuccess: #2011: 1: Success after binutils/gcc: 6 commits new c3caa9f6268 372: onsuccess: #2012: 1: Success after binutils/gcc: 10 commits new f715824b1fe 373: onsuccess: #2013: 1: Success after gcc: 6 commits new 6b04efc585b 374: onsuccess: #2014: 1: Success after binutils/gcc: 9 commits new 51c7ac313d1 375: onsuccess: #2015: 1: Success after binutils/gcc: 4 commits new f8cbbfaead3 376: onsuccess: #2016: 1: Success after basepoints/gcc-13-4 [...] new be5db91a5ff 377: onsuccess: #2017: 1: Success after binutils: 3 commits new 9484715e005 378: onsuccess: #2018: 1: Success after binutils/gcc: 2 commits new 146367f15a8 379: onsuccess: #2019: 1: Success after gcc: 3 commits new 8d671a23bf7 380: onsuccess: #2020: 1: Success after gcc: 2 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (be8361e3f89) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (8d [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1716 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 52272 -> 53412 bytes 04-build_abe-gcc/console.log.xz | Bin 233968 -> 234440 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3820 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2544 -> 2776 bytes 07-check_regression/console.log.xz | Bin 4636 -> 4736 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 59 +- 08-update_baseline/console.log | 58 +- 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 | 14 +- sumfiles/g++.log.xz | Bin 2857164 -> 2825820 bytes sumfiles/g++.sum | 137 +- sumfiles/gcc.log.xz | Bin 2459164 -> 2458592 bytes sumfiles/gcc.sum | 4564 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 913752 -> 918448 bytes sumfiles/gfortran.sum | 94 +- sumfiles/libatomic.log.xz | Bin 2172 -> 2160 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 216536 -> 216076 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2532 -> 2548 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 471804 -> 466240 bytes sumfiles/libstdc++.sum | 10 +- 30 files changed, 2506 insertions(+), 2482 deletions(-) -- 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