Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[gcc] branch releases/gcc-12 updated (fa9abddf947 -> d61d6c91b02)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-12 in repository gcc. from fa9abddf947 Daily bump. new d61d6c91b02 aarch64: Specify that FEAT_MOPS sequences clobber CC 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/config/aarch64/aarch64.md | 5 +++++ gcc/testsuite/gcc.target/aarch64/mops_5.c | 17 +++++++++++++++++ gcc/testsuite/gcc.target/aarch64/mops_6.c | 17 +++++++++++++++++ gcc/testsuite/gcc.target/aarch64/mops_7.c | 16 ++++++++++++++++ 4 files changed, 55 insertions(+) create mode 100644 gcc/testsuite/gcc.target/aarch64/mops_5.c create mode 100644 gcc/testsuite/gcc.target/aarch64/mops_6.c create mode 100644 gcc/testsuite/gcc.target/aarch64/mops_7.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[gcc] branch master updated (a0ee2e52252 -> 926f5059bb8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from a0ee2e52252 range-op-float: Improve binary reverse operations new 926f5059bb8 tree-optimization/104475 - improve access diagnostics 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/pointer-query.cc | 20 ++++++++++++++++---- gcc/pointer-query.h | 5 ++++- 2 files changed, 20 insertions(+), 5 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_binutils/master-aarch64 updated (809e1de4c6b -> 2a7f489d3fe)

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_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. discards 809e1de4c6b 115: onsuccess: #645: 1: Success after binutils: 27 commits discards c23e94a9aec 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 5f28072b635 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards e215365a6fc 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards e9b593aff72 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards b8b3ecdbbb5 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 77d84d1890a 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards f1009aa7de9 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 329c3ce795f 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 4dcf638a128 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 62dc5896bb6 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 657b35b7a4a 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 4019cc2a082 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] discards b732258fde4 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] discards ef852d9c6ae 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 5b2fd34fcaf 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 27b5995be91 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 491280fdea0 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] discards 7734f267037 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards aff1bbc0845 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 0890c408ef7 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 0076ef88770 94: onsuccess: #616: 1: Success after binutils: 2 commits discards ab9333dc39c 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 30b25abba02 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards 8549291ad17 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards f084ce1f3fb 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 249dd80f39d 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] discards 4c713e48e72 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] discards e1d8b56cee7 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] discards 4ca0b7bc4ba 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 819e000573d 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] discards d1f96bdebd9 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 5a9f38bc093 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 5afc2777680 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] discards 1f4fbb6198d 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 1812fb4d0de 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards b33549bd289 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards e27b598a50a 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards f8ba2d209ea 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] discards 1a2a88b3f4c 76: onsuccess: #592: 1: Success after linux: 63 commits discards aa232909e21 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 3ff20763107 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 68ebe895c60 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards b13a737e105 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] discards 4287a12b29d 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] discards 51008df1482 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards f7bf8620a2b 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards 50057aaef4d 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards dc79bd5245c 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] discards 763447b7c73 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards aeedc7b7315 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] discards 9f0050cedf9 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards b511611af3c 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards a68fcc13fba 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 2f666f025ad 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards d079506bb9c 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 6d8e6737c3e 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] discards 15bf34c9717 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] discards 18ed0aef8b5 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] discards f62aaa6cf38 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] discards fd72b79ef67 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] discards c57104eeb05 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] discards 8db2c121732 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] discards 0c3e16eaddd 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards 49e147597f5 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards f8fc21c9680 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards cf5971dfeef 49: onsuccess: #562: 1: Success after binutils: 9 commits discards aa6c000c6bd 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 430159cfb26 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 1aa24cc753a 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] discards 88281315f97 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 2f62bbc7e24 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards e7ec495b512 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards 6353d98b69d 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards f163a3e1225 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] discards 896694a8c50 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards d5644b1f98e 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] discards 1709bac1dfd 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 3c5caa8d2c7 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] discards 8b906e154c4 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 39f36661a83 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards da76c72519e 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards f4898695474 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 6f347cc0af3 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards 6a9e64b261b 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards bbbc46e35c8 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards a3862bac251 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards 95ff4d6849f 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards 0174d0dcd88 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 0735e45e875 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards 922b7464545 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] discards 8feb6d8d672 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] discards c74d93a3cf9 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] discards bdc3e832d15 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards c193e38e6ad 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 86c3654e44f 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 94b5895354c 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 9a27dd4b3d1 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 8c574b283f7 17: onsuccess: 1: Successful build after binutils/gcc/glibc [...] discards 4ab70a2da1d 16: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 87af7af69d3 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 2e12c75178f 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new fb71445d08c 16: onsuccess: 1: Successful build after binutils/gcc/linux [...] new c80a8f95f14 17: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new 70e12a2d59e 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new eee71ebe917 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 0782d6b53de 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new fee1cfb9736 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new d69c03f3250 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 4904c7b31e3 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] new 8044e352631 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] new 41aad23346c 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] new 59d118c7465 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 5ffaf96bc9a 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new 206a9f40a26 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new 949c7377388 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 3765fce0542 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new e099029be92 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new a4636020e33 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 67cb632b6a6 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new 0cc936f0821 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new c8d964306ae 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 82a7fcdd168 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 55a543066d7 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] new 0f5297ff0da 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new ab1b8f6d3d9 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] new 95ab006a4b2 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new 0f45bab3a46 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] new 170a0b27675 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new ea693fa6580 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new 4964bfe4de0 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new a39c0cffaed 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new e43b4fe4b5a 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] new 6e0398a773a 47: onsuccess: #556: 1: Success after binutils: 12 commits new 0437c504e40 48: onsuccess: #559: 1: Success after binutils: 6 commits new fd24e6f2f9c 49: onsuccess: #562: 1: Success after binutils: 9 commits new 599f2c59e29 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new 8e816effba6 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new 94eb9635333 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new d433d7537f5 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] new e6dd8a6ff94 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] new 45628aa586a 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] new 5e14bf34080 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] new 95c17cdbace 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] new 45642447983 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] new 133c8e8d13c 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] new 219f09203a4 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 8ab371c1e1a 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new ff6f95f857c 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 4efd3037147 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new 7f061c9a7ce 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new 7356ea51a88 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] new 72a1d9a3592 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new 746ea92d66b 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] new 6f35245a9b9 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 6e06e4b28e8 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new c8f788d5962 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new f351cb51348 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] new 568b1080c37 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] new b73097c8303 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 924274486b8 74: onsuccess: #590: 1: Success after binutils: 16 commits new bed7054ac8e 75: onsuccess: #591: 1: Success after gcc: 25 commits new bde70a15f11 76: onsuccess: #592: 1: Success after linux: 63 commits new 78bce507493 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] new e9ecb59dee7 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new aa727093a39 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 52e69e77533 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new f4178b41b04 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 670e00e7147 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] new 997843f0dbe 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new c04200ab8f5 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new a22d680a058 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] new 12fcc25a31d 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 35fd8f038b5 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] new e7a867a9424 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] new 6ae9ce20312 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] new 3223ba057b6 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new f9f4ab46395 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 1c572805d7f 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new 44a379e276e 93: onsuccess: #613: 1: Success after binutils: 19 commits new efe7a9391e7 94: onsuccess: #616: 1: Success after binutils: 2 commits new 197e1322888 95: onsuccess: #619: 1: Success after binutils: 5 commits new d30ff9ed5fc 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 51dc16c10a6 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 840bff1cd09 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] new 36cd4b0f084 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 1d3315f99f8 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new cdd4eed6d75 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 5bcd4a3b38b 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] new c92583273c5 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] new 16f6449e2fe 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 14fe9f742d3 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 7e8792e9a08 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new f1962d7bc7f 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new d2da6af3744 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 05240d1deb4 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 71104bae473 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 30d25ee04cb 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new bfdcd83867b 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 9584436edb5 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 264d921360a 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 51ce6a57f6e 115: onsuccess: #645: 1: Success after binutils: 27 commits new 2a7f489d3fe 116: onsuccess: #647: 1: Success after linux: 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 (809e1de4c6b) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1692 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39492 -> 39232 bytes 04-build_abe-gcc/console.log.xz | Bin 214644 -> 214332 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8420 -> 8684 bytes 07-build_abe-glibc/console.log.xz | Bin 244912 -> 244104 bytes 08-build_abe-gdb/console.log.xz | Bin 38912 -> 39128 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3848 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2208 -> 2208 bytes 11-check_regression/console.log.xz | Bin 4764 -> 4576 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 20 +- 12-update_baseline/console.log | 44 ++-- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- sumfiles/binutils.log.xz | Bin 63072 -> 63128 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 81772 -> 81772 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 121704 -> 121704 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 26 files changed, 384 insertions(+), 392 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[binutils-gdb] branch master updated (40849d84cbc -> c8ea5e409b0)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 40849d84cbc x86: Remove unnecessary vex.w check for xh_mode in disassembler new c8ea5e409b0 gdb/riscv: correct dwarf to gdb register number mapping The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gdb/riscv-tdep.c | 4 ++-- 1 file changed, 2 insertions(+), 2 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 (705027a25d3 -> 08d1bcaeb16)

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 705027a25d3 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 4199a67ece5 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 4c076ffd5d0 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards b13f1b859f6 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards abcd300fa3a 208: onsuccess: #2012: 1: Success after linux: 12 commits discards bdaacb27c49 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 55756871ae6 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 5ed4587f356 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards a95a3307f2e 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards 628939c85ae 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards 5acc2192fa3 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards cfc4889f7a8 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards b7f6930b6b4 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards c1c207781a4 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards be722c82ad1 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards 6995bbbc5c8 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards 8bca49aa67b 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards 0083fdf6c5d 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards 331a40d7ad1 194: onsuccess: #1995: 1: Success after linux: 517 commits discards b6b37bc9bd9 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 81766c7c50a 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards 5c0d843568a 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards 2e7dda6dca2 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards 1b7ec68d45d 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards 368ad50a5ff 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards 87e04a1ff77 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards 7fbe6bc05ad 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards 8b327978242 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards 53d9b440956 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards 23bc68479f0 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards f8236457821 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards fbac3fd058e 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards d837bb76acb 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards b9c5313d4ec 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards 4e9bdf680ad 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards 3f0aa0414e4 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards fdf138bb0ca 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards 952ffb49c31 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards f52e4dcc9dd 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards 3f01197b176 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards 075bd39ecb7 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards 712fd879fee 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards 6f8d2e23f55 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards 1bdd33f6438 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards 0fe09f1fca6 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards c7b2b8917d4 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards 40459f70692 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards 8257627461e 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards 99de173533f 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards ad3fd8549ca 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 54f99ae3823 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards c4c5cef2d49 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards f6a934e2214 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards 4219cdcfd49 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards 112cbe0c0f3 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards 348e24e4726 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards 7a1e2ce374f 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 7125b7a4ad2 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards d38fb7e3faa 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 05e8b6d7fe0 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 5a72cb4cbd6 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards ebbf64821ef 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards 8fb59b48b85 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards 6cd54830d27 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards fcbba4921e7 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards 99993f77443 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards 83279c225f2 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards 5138e64ef12 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards cab760f6bf0 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards fad72cbd845 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards 71f7b4da119 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards 6c929b09ce1 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards 9dc072c7567 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards 78d67571593 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards 1bbaf895473 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards a851c0d5d56 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 830bb0b8656 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards 8e825e6367d 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 678667a0170 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards fd4269c3154 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards 106b4a421e6 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] discards db4ea052bfa 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] discards 538c30f303b 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 34d2a48e61d 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] discards bd1b4ed92da 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 80363965cce 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] discards b03f93af2bf 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 0aa6e690a4e 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] discards b42a3529a86 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards df6154f3f28 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] discards ef0d70689f0 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] discards fa8bb6dfcd4 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] discards d4c6bcc1243 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] discards 56813a168d1 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] discards af35af6d411 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] discards 0ba15f9c4c0 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] discards 93aa3a17446 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] discards bde1d9cadac 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] discards 5c4645eb529 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 6a5675e8af1 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] discards e257484f5fe 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] new fb3eda9cabd 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] new 166693fb527 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] new ffbbe376248 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new a8a68f301e8 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] new 807e3ba8ada 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] new e8626250af5 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] new f285520d6ad 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] new 602c88719a6 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] new 75f91099968 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] new 77e14b6460b 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] new 22ec2d784f0 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] new 65870ccb71d 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] new 3bb8cdffc72 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 31f8777bf72 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] new e33e2f5dd98 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new d5cfc85afd8 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] new 9ef035f434f 128: onsuccess: #1723: 1: Success after linux: 12 commits new af23b03c7e5 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] new 29ef8e75f59 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new c0c733bff8b 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new a02e63fbce7 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new 7a1496811a5 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new 90ae89d5b72 134: onsuccess: #1730: 1: Success after binutils: 2 commits new a2d90e676a0 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 8c5692c455d 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new aeecab173a3 137: onsuccess: #1736: 1: Success after gcc: 5 commits new df2f36faf57 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new e30c6c656d1 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new 121b2c8742a 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new 369ff03144e 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new 4e10a672345 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new 30625542840 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 3dc8f2e186f 144: onsuccess: #1743: 1: Success after glibc: 2 commits new fbc75855005 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new ece49fe7f94 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new 80c11907366 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new ac93173e88f 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new eae6288f305 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new 4cec6b48cbb 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new 8f5dec2f10e 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new 6eb50e67abe 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new 649fcd802f8 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 94ec4d3115f 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new f6773ee1395 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new fc759c56afd 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 8e55659970c 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new 64b16b2dfcd 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new d23b1df8573 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new 8383c918cc6 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new 8f4fd4792e0 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new 6c62dba2d4d 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new dc5f849d06a 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 37df0f7b210 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new 73de395171b 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new 4c731dd0983 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new 6b4fb514a7a 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new a2aa5ebc370 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new 76066821b0e 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new 323de939d95 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new 6f3f2ffca95 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new 9679d0ad49a 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new 03b31a5523b 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new ff6e45c651d 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new 90790cc401d 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new dca590f987a 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new f4146a8150b 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new 6265fb8bc44 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new 05217933436 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new 05aae23d47e 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new 29b5089822d 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new 21c325e5137 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new 0ffd53fda50 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new c872b835726 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new e75e4e10f4c 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new e2223774c79 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new a436a788157 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new 27a6e822d8b 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new 5ca621569f5 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new c303c37b312 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new 0e6de209f71 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new dd170886744 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new 01c10b32e43 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 2eb0249bcd9 194: onsuccess: #1995: 1: Success after linux: 517 commits new f380aebdbda 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new b7a71475eb8 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new 7d474f436f4 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new b417d3c46c9 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new a4d02bcd817 199: onsuccess: #2000: 1: Success after gcc: 5 commits new ae4cc1c7e9f 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new 1b95a55b814 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 29ab552051b 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new afd2b9bb6c1 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new 083c6514b3a 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new 898d0dea9be 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 2d4a1507bfe 206: onsuccess: #2007: 1: Success after gcc: 2 commits new e858b1c32c4 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 41485d27953 208: onsuccess: #2012: 1: Success after linux: 12 commits new bd0490200df 209: onsuccess: #2014: 1: Success after binutils: 12 commits new de93a56c606 210: onsuccess: #2017: 1: Success after binutils: 6 commits new bb3116eeff6 211: onsuccess: #2020: 1: Success after binutils: 10 commits new abf8be904e5 212: onsuccess: #2022: 1: Success after linux: 3 commits new 08d1bcaeb16 213: onsuccess: #2024: 1: Success after binutils: 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 (705027a25d3) \ 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 1792 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 31584 -> 31812 bytes 04-build_abe-stage1/console.log.xz | Bin 91152 -> 91684 bytes 06-build_abe-linux/console.log.xz | Bin 8772 -> 8740 bytes 07-build_abe-glibc/console.log.xz | Bin 238520 -> 236872 bytes 08-build_abe-stage2/console.log.xz | Bin 226796 -> 225376 bytes 09-build_abe-gdb/console.log.xz | Bin 39260 -> 38880 bytes 10-build_abe-qemu/console.log.xz | Bin 31216 -> 30832 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2468 -> 2440 bytes 13-check_regression/console.log.xz | Bin 4908 -> 4920 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 16 +- 13-check_regression/results.compare2 | 4 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 2712628 -> 2736348 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 2305704 -> 2280328 bytes sumfiles/gcc.sum | 2272 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 891512 -> 891636 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213104 -> 213236 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436304 -> 429620 bytes sumfiles/libstdc++.sum | 2 +- 36 files changed, 1207 insertions(+), 1259 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_bmk_gnu_apm/gnu-master-arm-spec2k6-Os_LTO updated (f945fb7a51b -> 57f6154632b)

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_gnu_apm/gnu-master-arm-spec2k6-Os_LTO in repository toolchain/ci/base-artifacts. from f945fb7a51b 26: onsuccess: #186: 1: [TCWG CI] No change after binutils: [...] new 57f6154632b 27: onsuccess: #188: 1: [TCWG CI] No change after glibc: 48 [...] 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 1796 -> 1820 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31836 -> 32052 bytes 04-build_abe-stage1/console.log.xz | Bin 94012 -> 92700 bytes 06-build_abe-linux/console.log.xz | Bin 8820 -> 8808 bytes 07-build_abe-glibc/console.log.xz | Bin 237560 -> 238244 bytes 08-build_abe-stage2/console.log.xz | Bin 214872 -> 213684 bytes 09-benchmark/benchmark-build.log | 84 +- 09-benchmark/benchmark.log | 82 +- 09-benchmark/console.log.xz | Bin 3756 -> 3768 bytes 10-check_regression/console.log.xz | Bin 6256 -> 6136 bytes .../csv-results-vs-first-1/perf.csv | 235 ++-- .../csv-results-vs-first-1/results.csv | 769 +++++++------- .../csv-results-vs-first-1/size.csv | 580 +++++----- 10-check_regression/csv-results-vs-prev-0/perf.csv | 252 +++-- .../csv-results-vs-prev-0/results.csv | 268 ++--- 10-check_regression/csv-results-vs-prev-1/perf.csv | 235 ++-- .../csv-results-vs-prev-1/results.csv | 769 +++++++------- 10-check_regression/csv-results-vs-prev-1/size.csv | 580 +++++----- 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 249 +++-- 10-check_regression/results-vs-first-internal.csv | 80 +- 10-check_regression/results-vs-first.csv | 80 +- 10-check_regression/results-vs-first.log | 1070 +++++++++---------- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 2 +- 10-check_regression/results-vs-prev-full.csv | 275 +++-- 10-check_regression/results-vs-prev-internal.csv | 80 +- 10-check_regression/results-vs-prev.csv | 80 +- 10-check_regression/results-vs-prev.log | 1122 ++++++++++---------- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 10 +- .../squad-vs-first/401.bzip2/results-metadata.json | 10 +- .../squad-vs-first/403.gcc/results-metadata.json | 10 +- .../410.bwaves/results-metadata.json | 10 +- .../416.gamess/results-metadata.json | 10 +- .../squad-vs-first/416.gamess/results-metrics.json | 2 +- .../squad-vs-first/429.mcf/results-metadata.json | 10 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 10 +- .../434.zeusmp/results-metadata.json | 10 +- .../435.gromacs/results-metadata.json | 10 +- .../436.cactusADM/results-metadata.json | 10 +- .../436.cactusADM/results-metrics.json | 2 +- .../437.leslie3d/results-metadata.json | 10 +- .../squad-vs-first/444.namd/results-metadata.json | 10 +- .../squad-vs-first/445.gobmk/results-metadata.json | 10 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 10 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 10 +- .../453.povray/results-metadata.json | 10 +- .../454.calculix/results-metadata.json | 10 +- .../squad-vs-first/456.hmmer/results-metadata.json | 10 +- .../squad-vs-first/458.sjeng/results-metadata.json | 10 +- .../459.GemsFDTD/results-metadata.json | 10 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 10 +- .../464.h264ref/results-metadata.json | 10 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 10 +- .../squad-vs-first/465.tonto/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 10 +- .../471.omnetpp/results-metadata.json | 10 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 10 +- .../squad-vs-first/481.wrf/results-metadata.json | 10 +- .../482.sphinx3/results-metadata.json | 10 +- .../483.xalancbmk/results-metadata.json | 10 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +-- git/glibc_rev | 2 +- mail/jira-body.txt | 14 +- mail/mail-body.txt | 14 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results_id | 2 +- 77 files changed, 3741 insertions(+), 3777 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_bmk_gnu_sq/gnu-master-aarch64-spec2k6-Os updated (40fc56551ff -> e0cd5bc2064)

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_gnu_sq/gnu-master-aarch64-spec2k6-Os in repository toolchain/ci/base-artifacts. from 40fc56551ff 42: onsuccess: #91: 1: [TCWG CI] No change after gcc: 660 commits new e0cd5bc2064 43: onsuccess: #93: 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 1812 -> 1816 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32032 -> 31444 bytes 04-build_abe-stage1/console.log.xz | Bin 73100 -> 72836 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 7984 -> 8780 bytes 07-build_abe-glibc/console.log.xz | Bin 246096 -> 244188 bytes 08-build_abe-stage2/console.log.xz | Bin 180076 -> 177696 bytes 09-benchmark/benchmark-build.log | 84 +- 09-benchmark/benchmark.log | 82 +- 09-benchmark/console.log.xz | Bin 3708 -> 3768 bytes 10-check_regression/console.log.xz | Bin 13664 -> 13096 bytes .../csv-results-vs-first-0/md5sum.csv | 2766 +- .../csv-results-vs-first-0/results.csv | 648150 ++++++++-------- .../csv-results-vs-first-0/size.csv | 662114 ++++++++--------- .../csv-results-vs-first-0/vect.csv | 42 +- .../csv-results-vs-first-1/md5sum.csv | 3188 +- .../csv-results-vs-first-1/perf.csv | 3732 +- .../csv-results-vs-first-1/results.csv | 689958 +++++++++-------- .../csv-results-vs-first-1/size.csv | 692698 +++++++++--------- .../csv-results-vs-first-1/vect.csv | 38 +- .../csv-results-vs-prev-0/md5sum.csv | 3418 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 3706 +- .../csv-results-vs-prev-0/results.csv | 684010 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/size.csv | 686655 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/vect.csv | 39 +- .../csv-results-vs-prev-1/md5sum.csv | 3188 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 3732 +- .../csv-results-vs-prev-1/results.csv | 689958 +++++++++-------- 10-check_regression/csv-results-vs-prev-1/size.csv | 692698 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/vect.csv | 38 +- 10-check_regression/results-vs-first-brief.csv | 60 +- 10-check_regression/results-vs-first-full.csv | 3712 +- 10-check_regression/results-vs-first-internal.csv | 233 +- 10-check_regression/results-vs-first.csv | 233 +- 10-check_regression/results-vs-first.log | 992 +- 10-check_regression/results-vs-prev-brief.csv | 62 +- 10-check_regression/results-vs-prev-compare.csv | 6 +- 10-check_regression/results-vs-prev-full.csv | 3930 +- 10-check_regression/results-vs-prev-internal.csv | 239 +- 10-check_regression/results-vs-prev.csv | 239 +- 10-check_regression/results-vs-prev.log | 1055 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 10 +- .../squad-vs-first/401.bzip2/results-metadata.json | 10 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 10 +- .../410.bwaves/results-metadata.json | 10 +- .../416.gamess/results-metadata.json | 10 +- .../squad-vs-first/429.mcf/results-metadata.json | 10 +- .../squad-vs-first/433.milc/results-metadata.json | 10 +- .../434.zeusmp/results-metadata.json | 10 +- .../435.gromacs/results-metadata.json | 10 +- .../435.gromacs/results-metrics.json | 2 +- .../436.cactusADM/results-metadata.json | 10 +- .../436.cactusADM/results-metrics.json | 2 +- .../437.leslie3d/results-metadata.json | 10 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 10 +- .../squad-vs-first/445.gobmk/results-metadata.json | 10 +- .../447.dealII/results-metadata.json | 10 +- .../450.soplex/results-metadata.json | 10 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 10 +- .../454.calculix/results-functional.json | 2 +- .../454.calculix/results-metadata.json | 10 +- .../454.calculix/results-metrics.json | 1 - .../squad-vs-first/456.hmmer/results-metadata.json | 10 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 10 +- .../459.GemsFDTD/results-metadata.json | 10 +- .../462.libquantum/results-metadata.json | 10 +- .../464.h264ref/results-metadata.json | 10 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 10 +- .../squad-vs-first/470.lbm/results-metadata.json | 10 +- .../471.omnetpp/results-metadata.json | 10 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 10 +- .../squad-vs-first/481.wrf/results-metadata.json | 10 +- .../482.sphinx3/results-metadata.json | 10 +- .../483.xalancbmk/results-metadata.json | 10 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/binutils_rev | 2 +- mail/jira-body.txt | 14 +- mail/mail-body.txt | 14 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results_id | 2 +- 91 files changed, 2746949 insertions(+), 2734599 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_binutils/master-arm updated (aec629a5c17 -> d840c767431)

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_binutils/master-arm in repository toolchain/ci/base-artifacts. discards aec629a5c17 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards f34d48c5bd2 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 0fe4a8c6fcb 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 4c11f83d7e6 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards cff89997070 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards fc6f9a30bef 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards 7ce0ee0188a 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards 899edd38a5b 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards 01003cd6727 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards 42fd40ac2c0 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards 86b83bb873d 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] discards 6c96982d99c 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] discards 30d61662539 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] discards 4b5cb19c45c 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] discards be6f53755dd 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] discards f22d521fd6f 107: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] discards 0309617670e 106: onsuccess: #532: 1: Success after binutils/gcc/linux/g [...] discards 6c61fac3f7c 105: onsuccess: #531: 1: Success after binutils/gcc/linux/g [...] discards 78a060a7c96 104: onsuccess: #530: 1: Success after gcc: 7 commits discards 1a458ec6504 103: onsuccess: #529: 1: Success after binutils/gcc/linux/g [...] discards 09e10ece3b7 102: onsuccess: #527: 1: Success after binutils: 5 commits discards da957bcc2dc 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 0a21ba01cfd 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 88c98ce1f72 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] discards 93f0c7000d7 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gl [...] discards e8dd7168959 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] discards c52c099c2e9 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] discards 38872865fb4 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gd [...] discards da84f17876e 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gd [...] discards 2920dabfebc 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] discards d27a42575c2 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gl [...] discards 4dab396db4a 91: onsuccess: #511: 1: Success after linux: 27 commits discards e2680a4b0f7 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 01af051d74e 89: onsuccess: #508: 1: Success after binutils: 12 commits discards eaf5e1839da 88: onsuccess: #506: 1: Success after linux: 34 commits discards b9ed76b907a 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 3db49c80f34 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 9c55dce5755 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards ee56d3c8f4d 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] discards 6ddaaf368cf 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gd [...] discards fc792cc4fe0 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gl [...] discards 350f190fb2d 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards 968753bc3aa 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards 2903d85459a 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] discards 6ae3e435402 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] discards 69e8b889492 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gd [...] discards bd0525e5daf 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gd [...] discards e7206526964 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] discards 3e606e9355c 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gl [...] discards 6af0b489b69 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gd [...] discards 2a5cb9906db 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gl [...] discards 208b8623786 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gd [...] discards f308d205875 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gl [...] discards 6865db4edf9 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] discards e6fe9654ec6 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gl [...] discards 80a0b540ce5 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] discards 7b92770f333 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gl [...] discards 1bdb7fe8c53 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gd [...] discards 713119723cb 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] discards d10c92f10d6 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gl [...] discards 1d21611949c 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gl [...] discards 46ea1c24750 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gl [...] discards 5cdc71a1754 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gl [...] discards 2c01287d146 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gl [...] discards 2e331242fa5 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gl [...] discards 4160440539c 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gl [...] discards 3df0566eeea 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gd [...] discards b1933f0f079 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gl [...] discards 700895a1534 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gl [...] discards 64fdd4a1001 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gl [...] discards a3f49b521f6 52: onsuccess: #467: 1: Success after binutils: 9 commits discards e2ef4b03309 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 261f6d93fd3 50: onsuccess: #461: 1: Success after binutils: 12 commits discards 1f3d7b230c9 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gd [...] discards cc963d2825d 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gd [...] discards 8fb4fec9ee1 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gl [...] discards 9bf9e94b8b1 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gl [...] discards acde108d78d 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gl [...] discards af4d36f3955 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gd [...] discards 78b24b236c4 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gd [...] discards e3c0093309a 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gd [...] discards 9bec2422d51 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gl [...] discards 3af9118bd57 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g [...] discards 9fb2c8a8b61 39: onsuccess: #447: 1: Success after binutils: 5 commits discards 4e625d319ec 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g [...] discards 9486c48a501 37: onsuccess: #443: 1: Success after binutils: 2 commits discards 26a29193fcf 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gl [...] discards 1406750a37f 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gl [...] discards 3b5c6801f4e 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gl [...] discards be33481c357 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gd [...] discards dc6e6b0e8d8 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gl [...] discards d9f8a075f9c 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gl [...] discards eeb57580605 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gd [...] discards 838f6551e38 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gl [...] discards 0e8e2209422 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gl [...] discards 46eb360ea21 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gd [...] discards d44999b8455 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gd [...] discards 02b4677ce4e 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gd [...] discards eced20d066c 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 [...] discards 187e1c45f72 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 2f597371ef3 22: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new 0f8a76d8270 22: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new c40c7233cc0 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new acf3575b1a9 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 [...] new 62bebc3a56f 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gd [...] new 4088e2c1338 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gd [...] new 1df8b4f88dc 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gd [...] new bcf028dbf25 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gl [...] new 7996b3b334d 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gl [...] new dc937b86a1f 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gd [...] new f53063b2969 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gl [...] new de5240641f7 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gl [...] new 51576f2ec79 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gd [...] new 2c7cabc7c8b 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gl [...] new 6aea0b5ffa6 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gl [...] new 558f02e5502 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gl [...] new 9d00cda88f2 37: onsuccess: #443: 1: Success after binutils: 2 commits new 8efb5d42fe8 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g [...] new 806e55ed55d 39: onsuccess: #447: 1: Success after binutils: 5 commits new 7277a380896 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g [...] new 271165c9968 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gl [...] new 28824673d6d 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gd [...] new 3f496cb354d 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gd [...] new 1fbeae91194 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gd [...] new 08c9d52a9a8 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gl [...] new ee0d8401cca 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gl [...] new b4c369b15c1 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gl [...] new 200a17b0215 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gd [...] new 187e4e07be3 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gd [...] new 04659256202 50: onsuccess: #461: 1: Success after binutils: 12 commits new 2cc55b6ad8d 51: onsuccess: #464: 1: Success after binutils: 6 commits new 7890a626251 52: onsuccess: #467: 1: Success after binutils: 9 commits new 45f7a4b27d2 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gl [...] new 33f87d2cb4a 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gl [...] new 7cd975312b7 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gl [...] new 060654549c1 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gd [...] new e572810f699 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gl [...] new 46cd4eb1171 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gl [...] new a7a0ceefe64 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gl [...] new bd4ac7d61dc 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gl [...] new 5bddea26bec 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gl [...] new 03b71e5979a 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gl [...] new 1a04913f0f6 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gl [...] new 2013e424aef 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] new a1a47d740ff 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gd [...] new 1d1d17d7b12 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gl [...] new 029132f90d5 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] new a0ca8b5e158 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gl [...] new 64bff83dce2 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] new 7012c13dcc4 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gl [...] new d22cdaa05c5 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gd [...] new b38ec917bb2 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gl [...] new 04cbe013e5d 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gd [...] new 80188d901ac 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gl [...] new 8260843f3ac 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] new e4da1d40b02 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gd [...] new ddc89683e3a 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gd [...] new 22700a43694 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] new 910dfed329b 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] new 483f6944662 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new 0a68c8805d0 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new 4e4d83400e5 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gl [...] new a7f0fafb828 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gd [...] new 1ed20b9c01d 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] new b73c2deb2b6 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new 567b0badb1f 86: onsuccess: #503: 1: Success after binutils: 12 commits new 137690d76f6 87: onsuccess: #505: 1: Success after glibc: 7 commits new 0ab5bcb47df 88: onsuccess: #506: 1: Success after linux: 34 commits new 8bf0657ef20 89: onsuccess: #508: 1: Success after binutils: 12 commits new 5daa9d7c48b 90: onsuccess: #510: 1: Success after glibc: 5 commits new 1a835e0eb23 91: onsuccess: #511: 1: Success after linux: 27 commits new 5054d0df7e3 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gl [...] new 982cd193680 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] new 1f5af427452 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gd [...] new 22379b05cbe 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gd [...] new fcde8d57231 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] new 5700d1d6605 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] new 5487580de22 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gl [...] new e95586c9caf 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] new cbb06ae5306 100: onsuccess: #521: 1: Success after binutils: 10 commits new 749c7df55fd 101: onsuccess: #524: 1: Success after binutils: 2 commits new 7a20cdd94be 102: onsuccess: #527: 1: Success after binutils: 5 commits new c6b78c75870 103: onsuccess: #529: 1: Success after binutils/gcc/linux/g [...] new 31dc9a4ae22 104: onsuccess: #530: 1: Success after gcc: 7 commits new 6f590f640ad 105: onsuccess: #531: 1: Success after binutils/gcc/linux/g [...] new 27ddabab9d3 106: onsuccess: #532: 1: Success after binutils/gcc/linux/g [...] new b1dcc1aefbd 107: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] new 8de5ec194ec 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] new 5eb84b2e8bd 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] new 8f21dbfc951 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] new 3d135de7851 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] new 73348b17a79 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new 823acbf807b 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new dcba7ff9de5 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new ea810b16105 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new e23b49052ca 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new b4114608dfe 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new 8133304b5b5 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 5f717a77469 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 60f96b91516 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new cc963ff1390 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new cdadc9b03f6 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new d840c767431 123: onsuccess: #550: 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 (aec629a5c17) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] 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 1760 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 51960 -> 52588 bytes 04-build_abe-gcc/console.log.xz | Bin 234468 -> 233916 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8320 -> 8652 bytes 07-build_abe-glibc/console.log.xz | Bin 236548 -> 235776 bytes 08-build_abe-gdb/console.log.xz | Bin 51776 -> 51732 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3828 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2152 -> 2220 bytes 11-check_regression/console.log.xz | Bin 5716 -> 5784 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 20 +- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +-- sumfiles/binutils.log.xz | Bin 62468 -> 62740 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 98184 -> 98128 bytes sumfiles/gas.sum | 275 +++++++++++------------ sumfiles/ld.log.xz | Bin 131640 -> 131564 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 29 files changed, 401 insertions(+), 392 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_bootstrap/master-arm-bootstrap updated (0a1092a19ba -> f542c4b9f38)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap in repository toolchain/ci/base-artifacts. discards 0a1092a19ba 386: onsuccess: #1810: 2: Success after binutils/gcc: 12 commits discards 722bc48c50c 385: onsuccess: #1809: 2: Success after binutils/gcc: 3 commits discards 03c5ed11d8a 384: onsuccess: #1808: 2: Success after binutils/gcc: 15 commits discards 0562569099b 383: onsuccess: #1807: 2: Success after binutils/gcc: 4 commits discards 8804110d10d 382: onsuccess: #1806: 2: Success after binutils/gcc: 5 commits discards 5923baa9297 381: onsuccess: #1805: 2: Success after gcc: 5 commits discards f06ddadcd88 380: onsuccess: #1804: 2: Success after gcc: 3 commits discards ad658044a2d 379: onsuccess: #1803: 2: Success after binutils/gcc: 2 commits discards 104a0ba445c 378: onsuccess: #1802: 2: Success after binutils/gcc: 4 commits discards 4d4c61390e8 377: onsuccess: #1801: 2: Success after binutils/gcc: 7 commits discards 0b1d4dab000 376: onsuccess: #1800: 2: Success after binutils/gcc: 15 commits discards 7f5be2033ae 375: onsuccess: #1798: 2: Success after binutils/gcc: 7 commits discards 4011c4819be 374: onsuccess: #1797: 2: Success after binutils/gcc: 6 commits discards 3f4794540fb 373: onsuccess: #1796: 2: Success after binutils/gcc: 19 commits discards 92f8a4e0253 372: onsuccess: #1795: 2: Success after binutils/gcc: 16 commits discards 24d63de856d 371: onsuccess: #1794: 2: Success after binutils/gcc: 6 commits discards 52e47e82e64 370: onsuccess: #1793: 2: Success after binutils/gcc: 16 commits discards 7b71edf1e34 369: onsuccess: #1792: 2: Success after binutils/gcc: 12 commits discards 199be468188 368: onsuccess: #1791: 2: Success after binutils/gcc: 13 commits discards 94dba1b090b 367: onsuccess: #1790: 2: Success after binutils/gcc: 9 commits discards 13c390ad3a4 366: onsuccess: #1789: 2: Success after binutils/gcc: 8 commits discards 55e786b51d7 365: onsuccess: #1788: 2: Success after binutils/gcc: 7 commits discards ef6348e7941 364: onsuccess: #1787: 2: Success after gcc: 6 commits discards a480d9b7152 363: onsuccess: #1786: 2: Success after binutils/gcc: 3 commits discards eab421b95c2 362: onsuccess: #1785: 2: Success after binutils/gcc: 19 commits discards 9c758354f52 361: onsuccess: #1784: 2: Success after binutils/gcc: 31 commits discards b9c15d268d9 360: onsuccess: #1783: 1: Success after binutils/gcc: 62 commits discards ff0c1e9831d 359: onsuccess: #1782: 1: Success after basepoints/gcc-13-4 [...] discards 95b1a20c929 358: onsuccess: #1781: 1: Success after binutils/gcc: 8 commits discards 23e7b22cf0c 357: onsuccess: #1780: 1: Success after binutils: 3 commits discards 8a145637479 356: onsuccess: #1779: 1: Success after gdb-12-branchpoint- [...] discards 2d3e1dde0b8 355: onsuccess: #1778: 1: Success after binutils/gcc: 2 commits discards e88790fe506 354: onsuccess: #1777: 1: Success after basepoints/gcc-13-4 [...] discards 2e54ab0ba6e 353: onsuccess: #1776: 1: Success after binutils: 4 commits discards 8d0249cc112 352: onsuccess: #1775: 1: Success after binutils/gcc: 124 commits discards 13cea244325 351: onsuccess: #1774: 1: Success after gcc: 8 commits discards 65f54ef42b2 350: force: #1773: 1: Failure after basepoints/gcc-13-4227- [...] discards 8ceef791410 349: onsuccess: #1764: 2: Success after binutils: 3 commits discards 231cde8ff49 348: onsuccess: #1762: 2: Success after binutils/gcc: 4 commits discards 76d3cca6c9f 347: onsuccess: #1761: 2: Success after binutils/gcc: 13 commits discards 2ee764a9feb 346: onsuccess: #1760: 2: Success after binutils/gcc: 14 commits discards c11d7e441fc 345: onsuccess: #1759: 2: Success after binutils/gcc: 23 commits discards 8ffae2b1c14 344: onsuccess: #1758: 2: Success after gcc: 3 commits discards 3b5ca094b63 343: onsuccess: #1757: 2: Success after binutils/gcc: 5 commits discards 6f743439f54 342: onsuccess: #1756: 2: Success after gcc: 4 commits discards ea7c750a913 341: onsuccess: #1755: 2: Success after binutils/gcc: 3 commits discards 3a58192fadf 340: onsuccess: #1754: 2: Success after binutils/gcc: 3 commits discards ffeca820210 339: onsuccess: #1753: 2: Success after binutils/gcc: 7 commits discards 9bbb622843e 338: onsuccess: #1752: 2: Success after binutils/gcc: 5 commits discards c1d8bfa9daa 337: onsuccess: #1751: 2: Success after binutils/gcc: 2 commits discards 7e4a8b0a309 336: onsuccess: #1750: 2: Success after binutils/gcc: 5 commits discards 1b56094da0a 335: onsuccess: #1749: 2: Success after binutils/gcc: 22 commits discards 4a9b88887dc 334: onsuccess: #1748: 2: Success after binutils/gcc: 9 commits discards 27f3e6fa7d6 333: onsuccess: #1747: 2: Success after binutils/gcc: 4 commits discards 2265ad5f7bc 332: onsuccess: #1746: 2: Success after binutils/gcc: 6 commits discards a706883939d 331: onsuccess: #1745: 2: Success after binutils/gcc: 14 commits discards 1c6390b67df 330: onsuccess: #1744: 2: Success after binutils/gcc: 11 commits discards 1ab99068b05 329: onsuccess: #1743: 2: Success after binutils/gcc: 7 commits discards 87f7bb8274f 328: onsuccess: #1742: 2: Success after binutils/gcc: 14 commits discards a9fd18fdd75 327: onsuccess: #1741: 2: Success after binutils/gcc: 12 commits discards 108182d18a3 326: onsuccess: #1740: 2: Success after binutils/gcc: 19 commits discards 47ca2f36cc6 325: onsuccess: #1739: 2: Success after gcc: 4 commits discards d0a82768412 324: onsuccess: #1738: 2: Success after binutils/gcc: 18 commits discards 8d78c73aa05 323: onsuccess: #1737: 2: Success after binutils/gcc: 84 commits discards 60f8dcea83f 322: onsuccess: #1736: 2: Success after binutils/gcc: 22 commits discards f92c24107bc 321: onsuccess: #1735: 1: Success after binutils/gcc: 54 commits discards a174253dcf2 320: onsuccess: #1734: 1: Success after binutils/gcc: 4 commits discards 408e1122410 319: onsuccess: #1733: 1: Success after binutils/gcc: 8 commits discards 894284d988b 318: onsuccess: #1732: 1: Success after binutils/gcc: 2 commits discards 9f6abf54922 317: onsuccess: #1731: 1: Success after binutils/gcc: 8 commits discards c0ae1fe6313 316: onsuccess: #1730: 1: Success after binutils/gcc: 16 commits discards c3156471c46 315: onsuccess: #1729: 1: Success after baseline build: no [...] discards 6b42044b2bd 314: force: #1728: 1: Failure after basepoints/gcc-13-3918- [...] discards ab93467ec6a 313: force: #1727: 2: Success after gcc: 6 commits discards b729143eded 312: onsuccess: #1724: 2: Success after gdb-12-branchpoint- [...] discards cf9fea646fd 311: onsuccess: #1722: 2: Success after binutils/gcc: 8 commits discards 78bc220c6b8 310: onsuccess: #1721: 2: Success after binutils/gcc: 27 commits discards 80e400173f8 309: onsuccess: #1720: 2: Success after binutils/gcc: 14 commits discards c0cc304cf94 308: onsuccess: #1719: 2: Success after binutils/gcc: 5 commits discards 146b8c66732 307: onsuccess: #1718: 2: Success after binutils/gcc: 22 commits discards 2ca5f8461d8 306: onsuccess: #1717: 2: Success after binutils/gcc: 12 commits discards 273edaa9a83 305: onsuccess: #1716: 2: Success after binutils/gcc: 10 commits discards 4d2edbf842b 304: onsuccess: #1715: 2: Success after binutils/gcc: 8 commits discards d03698a18dc 303: onsuccess: #1714: 2: Success after binutils/gcc: 17 commits discards 646217bffa5 302: onsuccess: #1713: 2: Success after binutils/gcc: 35 commits discards 321d938cb8c 301: onsuccess: #1711: 2: Success after gdb-12-branchpoint- [...] discards e6601c3d896 300: onsuccess: #1709: 2: Success after binutils/gcc: 9 commits discards 0d593aa55ca 299: onsuccess: #1708: 2: Success after binutils/gcc: 16 commits discards 5204ed0b084 298: onsuccess: #1707: 2: Success after gcc: 32 commits discards 2c88c641f6d 297: onsuccess: #1706: 2: Success after binutils/gcc: 9 commits discards 5f5d0b7f0fc 296: onsuccess: #1705: 2: Success after binutils/gcc: 9 commits discards e7fccdf50fb 295: onsuccess: #1704: 2: Success after binutils/gcc: 17 commits discards 06b57be2c4e 294: onsuccess: #1703: 2: Success after binutils/gcc: 12 commits discards 49f965512ef 293: onsuccess: #1702: 2: Success after binutils/gcc: 37 commits discards 6d9738bb84e 292: onsuccess: #1701: 2: Success after binutils/gcc: 3 commits discards 6604f0e01b1 291: onsuccess: #1700: 2: Success after gcc: 4 commits discards 855491a31c1 290: onsuccess: #1699: 2: Success after binutils/gcc: 5 commits discards 18d8c63d75d 289: onsuccess: #1698: 2: Success after basepoints/gcc-13-3 [...] discards 69916da5081 288: onsuccess: #1697: 2: Success after binutils/gcc: 4 commits discards 9b0c771d1a0 287: onsuccess: #1696: 2: Success after gcc: 3 commits discards fca612fe054 286: onsuccess: #1695: 2: Success after binutils/gcc: 10 commits new 89b7f3257f7 286: onsuccess: #1695: 2: Success after binutils/gcc: 10 commits new 70913fcac86 287: onsuccess: #1696: 2: Success after gcc: 3 commits new d257ed34889 288: onsuccess: #1697: 2: Success after binutils/gcc: 4 commits new 3d05970e89a 289: onsuccess: #1698: 2: Success after basepoints/gcc-13-3 [...] new 6eb22c7b7a3 290: onsuccess: #1699: 2: Success after binutils/gcc: 5 commits new 635d8b2db80 291: onsuccess: #1700: 2: Success after gcc: 4 commits new e0fa4b60020 292: onsuccess: #1701: 2: Success after binutils/gcc: 3 commits new bc64e44b56e 293: onsuccess: #1702: 2: Success after binutils/gcc: 37 commits new f4763514a06 294: onsuccess: #1703: 2: Success after binutils/gcc: 12 commits new 1b4a7c463c4 295: onsuccess: #1704: 2: Success after binutils/gcc: 17 commits new da1d2bdf9e3 296: onsuccess: #1705: 2: Success after binutils/gcc: 9 commits new 763a5b1d01e 297: onsuccess: #1706: 2: Success after binutils/gcc: 9 commits new ea67a991cd3 298: onsuccess: #1707: 2: Success after gcc: 32 commits new 98a01fc38da 299: onsuccess: #1708: 2: Success after binutils/gcc: 16 commits new 9cd8dc7cee0 300: onsuccess: #1709: 2: Success after binutils/gcc: 9 commits new 0619ab88ffc 301: onsuccess: #1711: 2: Success after gdb-12-branchpoint- [...] new e2286ff64cf 302: onsuccess: #1713: 2: Success after binutils/gcc: 35 commits new 91dc7ef2590 303: onsuccess: #1714: 2: Success after binutils/gcc: 17 commits new 49b95782656 304: onsuccess: #1715: 2: Success after binutils/gcc: 8 commits new a3f9de6e179 305: onsuccess: #1716: 2: Success after binutils/gcc: 10 commits new e694e914467 306: onsuccess: #1717: 2: Success after binutils/gcc: 12 commits new 30ee0000d84 307: onsuccess: #1718: 2: Success after binutils/gcc: 22 commits new 96b536f2a24 308: onsuccess: #1719: 2: Success after binutils/gcc: 5 commits new 64dcec51602 309: onsuccess: #1720: 2: Success after binutils/gcc: 14 commits new 251ebad6a34 310: onsuccess: #1721: 2: Success after binutils/gcc: 27 commits new c0e88c9c759 311: onsuccess: #1722: 2: Success after binutils/gcc: 8 commits new cbcc7bbb235 312: onsuccess: #1724: 2: Success after gdb-12-branchpoint- [...] new 7c85af7133a 313: force: #1727: 2: Success after gcc: 6 commits new 7bfeda4415e 314: force: #1728: 1: Failure after basepoints/gcc-13-3918- [...] new fbfb4a643f9 315: onsuccess: #1729: 1: Success after baseline build: no [...] new 6b7dd9d2650 316: onsuccess: #1730: 1: Success after binutils/gcc: 16 commits new 8b7ee87c158 317: onsuccess: #1731: 1: Success after binutils/gcc: 8 commits new 73be427a223 318: onsuccess: #1732: 1: Success after binutils/gcc: 2 commits new 2b4e4ec13c3 319: onsuccess: #1733: 1: Success after binutils/gcc: 8 commits new 454de177f85 320: onsuccess: #1734: 1: Success after binutils/gcc: 4 commits new 0fa74909fef 321: onsuccess: #1735: 1: Success after binutils/gcc: 54 commits new a83cee8f32b 322: onsuccess: #1736: 2: Success after binutils/gcc: 22 commits new 57465db8915 323: onsuccess: #1737: 2: Success after binutils/gcc: 84 commits new ed594aecce3 324: onsuccess: #1738: 2: Success after binutils/gcc: 18 commits new 5fb33e38845 325: onsuccess: #1739: 2: Success after gcc: 4 commits new 2a3e8a48188 326: onsuccess: #1740: 2: Success after binutils/gcc: 19 commits new 48917f04100 327: onsuccess: #1741: 2: Success after binutils/gcc: 12 commits new 5760c8fa43f 328: onsuccess: #1742: 2: Success after binutils/gcc: 14 commits new 1803456d15d 329: onsuccess: #1743: 2: Success after binutils/gcc: 7 commits new 722175d5623 330: onsuccess: #1744: 2: Success after binutils/gcc: 11 commits new 752a335cc74 331: onsuccess: #1745: 2: Success after binutils/gcc: 14 commits new a9857fb5e7b 332: onsuccess: #1746: 2: Success after binutils/gcc: 6 commits new a4d319b39db 333: onsuccess: #1747: 2: Success after binutils/gcc: 4 commits new bcef3ea9873 334: onsuccess: #1748: 2: Success after binutils/gcc: 9 commits new c7b66d1adaa 335: onsuccess: #1749: 2: Success after binutils/gcc: 22 commits new 9dd227c611f 336: onsuccess: #1750: 2: Success after binutils/gcc: 5 commits new 464f9e6ab8b 337: onsuccess: #1751: 2: Success after binutils/gcc: 2 commits new 2b6d6466078 338: onsuccess: #1752: 2: Success after binutils/gcc: 5 commits new 2a009a1fdfe 339: onsuccess: #1753: 2: Success after binutils/gcc: 7 commits new cbb687818e1 340: onsuccess: #1754: 2: Success after binutils/gcc: 3 commits new 913a0716cb1 341: onsuccess: #1755: 2: Success after binutils/gcc: 3 commits new 18a1a2b429c 342: onsuccess: #1756: 2: Success after gcc: 4 commits new 303170305bc 343: onsuccess: #1757: 2: Success after binutils/gcc: 5 commits new 0b7d49c890b 344: onsuccess: #1758: 2: Success after gcc: 3 commits new 4bc8fcf6423 345: onsuccess: #1759: 2: Success after binutils/gcc: 23 commits new 078381f3e17 346: onsuccess: #1760: 2: Success after binutils/gcc: 14 commits new 0757cdc3a8c 347: onsuccess: #1761: 2: Success after binutils/gcc: 13 commits new 52b7c8a8f0e 348: onsuccess: #1762: 2: Success after binutils/gcc: 4 commits new 44d03a774f6 349: onsuccess: #1764: 2: Success after binutils: 3 commits new 204d3515587 350: force: #1773: 1: Failure after basepoints/gcc-13-4227- [...] new 95091bde5b6 351: onsuccess: #1774: 1: Success after gcc: 8 commits new 16fe011c669 352: onsuccess: #1775: 1: Success after binutils/gcc: 124 commits new 5b6e672189d 353: onsuccess: #1776: 1: Success after binutils: 4 commits new 26bdc6ac2ed 354: onsuccess: #1777: 1: Success after basepoints/gcc-13-4 [...] new 7bf2f42d45a 355: onsuccess: #1778: 1: Success after binutils/gcc: 2 commits new 82463bb44bc 356: onsuccess: #1779: 1: Success after gdb-12-branchpoint- [...] new 38ec7fb614d 357: onsuccess: #1780: 1: Success after binutils: 3 commits new cfa5cfcd765 358: onsuccess: #1781: 1: Success after binutils/gcc: 8 commits new 1d7488fccdf 359: onsuccess: #1782: 1: Success after basepoints/gcc-13-4 [...] new 80731bfcd8d 360: onsuccess: #1783: 1: Success after binutils/gcc: 62 commits new 9ef21e51237 361: onsuccess: #1784: 2: Success after binutils/gcc: 31 commits new 373dc53b69c 362: onsuccess: #1785: 2: Success after binutils/gcc: 19 commits new b56c37dea57 363: onsuccess: #1786: 2: Success after binutils/gcc: 3 commits new 50511e92583 364: onsuccess: #1787: 2: Success after gcc: 6 commits new e5f24f706ff 365: onsuccess: #1788: 2: Success after binutils/gcc: 7 commits new dabb9e1e265 366: onsuccess: #1789: 2: Success after binutils/gcc: 8 commits new e7b605f73d2 367: onsuccess: #1790: 2: Success after binutils/gcc: 9 commits new 75b8b803fb8 368: onsuccess: #1791: 2: Success after binutils/gcc: 13 commits new ee1e4b4435c 369: onsuccess: #1792: 2: Success after binutils/gcc: 12 commits new ee73e46a829 370: onsuccess: #1793: 2: Success after binutils/gcc: 16 commits new cb528fe2297 371: onsuccess: #1794: 2: Success after binutils/gcc: 6 commits new 0d01db67180 372: onsuccess: #1795: 2: Success after binutils/gcc: 16 commits new 534308c3d09 373: onsuccess: #1796: 2: Success after binutils/gcc: 19 commits new 42a8fa3518b 374: onsuccess: #1797: 2: Success after binutils/gcc: 6 commits new 51fbab5ae02 375: onsuccess: #1798: 2: Success after binutils/gcc: 7 commits new 995fada732b 376: onsuccess: #1800: 2: Success after binutils/gcc: 15 commits new 46f688af653 377: onsuccess: #1801: 2: Success after binutils/gcc: 7 commits new a4f9d86be0c 378: onsuccess: #1802: 2: Success after binutils/gcc: 4 commits new 572c7623697 379: onsuccess: #1803: 2: Success after binutils/gcc: 2 commits new 2f20ecd341b 380: onsuccess: #1804: 2: Success after gcc: 3 commits new 53335cb9b21 381: onsuccess: #1805: 2: Success after gcc: 5 commits new b8753c04587 382: onsuccess: #1806: 2: Success after binutils/gcc: 5 commits new ceda10ac9db 383: onsuccess: #1807: 2: Success after binutils/gcc: 4 commits new 025e96d679e 384: onsuccess: #1808: 2: Success after binutils/gcc: 15 commits new 80a500f1c6d 385: onsuccess: #1809: 2: Success after binutils/gcc: 3 commits new 9bd440e44ac 386: onsuccess: #1810: 2: Success after binutils/gcc: 12 commits new f542c4b9f38 387: onsuccess: #1811: 2: Success after binutils/gcc: 6 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 (0a1092a19ba) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1716 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2784 bytes 04-build_abe-binutils/console.log.xz | Bin 53380 -> 53320 bytes 05-build_abe-bootstrap/console.log.xz | Bin 467312 -> 467848 bytes 06-check_regression/console.log.xz | Bin 2848 -> 2728 bytes 07-update_baseline/console.log | 64 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++----- 13 files changed, 47 insertions(+), 47 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_binutils/master-aarch64 updated (68f64b1f25f -> 809e1de4c6b)

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_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. discards 68f64b1f25f 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 30e55ff723e 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 9c9728ae0da 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards ec595061b6a 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards b77603bd55b 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 86dec16af50 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 90104569448 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards bbcc57bba86 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 4bc2e6ed67d 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards df9b06984df 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards aab591ef62d 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards cc68072c0e7 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] discards d372aac77bc 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] discards 6ea6fd70b4f 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 2b10c3bfbd2 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards cbe6faf68ad 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 67be1399c39 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] discards b4310633d32 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards be1289552dd 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards e3d62e3ab80 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 66843fe86e0 94: onsuccess: #616: 1: Success after binutils: 2 commits discards fbc8775c85b 93: onsuccess: #613: 1: Success after binutils: 19 commits discards d24932fd238 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards 9a6e1c0ce7a 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards 67a1b905a4c 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 5529a4b5839 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] discards 04addbf8202 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] discards 4ceaaa371e2 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] discards 69ed3bcdc0a 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards d978d26f388 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] discards 7d2e86e3df0 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 63b9ad90684 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 8a196990b32 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] discards a193d721566 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 190023d5d4f 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards 309ebf03094 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 8968987a329 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 5600abe1e91 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] discards 4d38a601358 76: onsuccess: #592: 1: Success after linux: 63 commits discards 690b82e75ba 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 9b636912916 74: onsuccess: #590: 1: Success after binutils: 16 commits discards b0064b3650f 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards 5f33174b893 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] discards 1a57e2cdcdf 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] discards 991d4b6e59f 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards af8c8172450 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards 6465331048c 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards f38a9906eb1 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] discards d70dbb1716a 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards 1dca5740667 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] discards a6b39208832 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards 5fbe1bf19bb 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards d02bad6dd56 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards bd2421c43c8 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards 08fe5bee3bb 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards a922ec5cdef 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] discards b96bf7f88f3 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] discards 4f6c977637e 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] discards a54724f5348 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] discards 01a5a7452bd 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] discards 9002ab4920a 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] discards c8365fea811 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] discards e0dcccb9277 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards cd46aad4d7b 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 9033a557e5b 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards 4d991d6d635 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 03356fbf8ad 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 78e2061eb64 47: onsuccess: #556: 1: Success after binutils: 12 commits discards f6f19396a14 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] discards fcc135d3143 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards c64bd32acf2 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards d4863855383 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards f91d1600b54 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 73e525ab6de 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] discards 151cbeb160e 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards 1d04602db3c 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] discards 1ea58947790 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 2141497cc20 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] discards f5c89f1ebfa 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 14879c7e528 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards 13ac3dd7530 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards 19e9719f293 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 4471feab3bb 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards 4d01ecb4cd6 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards e2fde621ed0 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards 9f8eaa538dd 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards b97d9d0dc49 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards 688e572fec7 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 4c56f2e35e3 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards f7a3a147789 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] discards 9dd9fa1287e 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] discards 50142837a2d 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] discards 85d36d94aff 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 93d639b286d 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 77f991f0390 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards fd106c7a27c 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 92b784d1d9b 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 2daea3b540d 17: onsuccess: 1: Successful build after binutils/gcc/glibc [...] discards 8a84de95fb9 16: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 37580b5c40e 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards a7fb1f5a605 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 9312e621049 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 87af7af69d3 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 4ab70a2da1d 16: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 8c574b283f7 17: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new 9a27dd4b3d1 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 94b5895354c 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 86c3654e44f 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new c193e38e6ad 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new bdc3e832d15 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new c74d93a3cf9 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] new 8feb6d8d672 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] new 922b7464545 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] new 0735e45e875 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 0174d0dcd88 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new 95ff4d6849f 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new a3862bac251 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new bbbc46e35c8 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new 6a9e64b261b 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new 6f347cc0af3 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new f4898695474 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new da76c72519e 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new 39f36661a83 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 8b906e154c4 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 3c5caa8d2c7 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] new 1709bac1dfd 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new d5644b1f98e 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] new 896694a8c50 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new f163a3e1225 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] new 6353d98b69d 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new e7ec495b512 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new 2f62bbc7e24 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 88281315f97 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new 1aa24cc753a 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] new 430159cfb26 47: onsuccess: #556: 1: Success after binutils: 12 commits new aa6c000c6bd 48: onsuccess: #559: 1: Success after binutils: 6 commits new cf5971dfeef 49: onsuccess: #562: 1: Success after binutils: 9 commits new f8fc21c9680 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new 49e147597f5 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new 0c3e16eaddd 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new 8db2c121732 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] new c57104eeb05 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] new fd72b79ef67 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] new f62aaa6cf38 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] new 18ed0aef8b5 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] new 15bf34c9717 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] new 6d8e6737c3e 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] new d079506bb9c 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 2f666f025ad 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new a68fcc13fba 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new b511611af3c 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new 9f0050cedf9 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new aeedc7b7315 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] new 763447b7c73 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new dc79bd5245c 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] new 50057aaef4d 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new f7bf8620a2b 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 51008df1482 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 4287a12b29d 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] new b13a737e105 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] new 68ebe895c60 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 3ff20763107 74: onsuccess: #590: 1: Success after binutils: 16 commits new aa232909e21 75: onsuccess: #591: 1: Success after gcc: 25 commits new 1a2a88b3f4c 76: onsuccess: #592: 1: Success after linux: 63 commits new f8ba2d209ea 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] new e27b598a50a 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new b33549bd289 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 1812fb4d0de 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new 1f4fbb6198d 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 5afc2777680 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] new 5a9f38bc093 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new d1f96bdebd9 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 819e000573d 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] new 4ca0b7bc4ba 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new e1d8b56cee7 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] new 4c713e48e72 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] new 249dd80f39d 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] new f084ce1f3fb 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 8549291ad17 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 30b25abba02 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new ab9333dc39c 93: onsuccess: #613: 1: Success after binutils: 19 commits new 0076ef88770 94: onsuccess: #616: 1: Success after binutils: 2 commits new 0890c408ef7 95: onsuccess: #619: 1: Success after binutils: 5 commits new aff1bbc0845 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 7734f267037 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 491280fdea0 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] new 27b5995be91 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 5b2fd34fcaf 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new ef852d9c6ae 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new b732258fde4 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] new 4019cc2a082 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] new 657b35b7a4a 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 62dc5896bb6 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 4dcf638a128 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 329c3ce795f 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new f1009aa7de9 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 77d84d1890a 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new b8b3ecdbbb5 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new e9b593aff72 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new e215365a6fc 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 5f28072b635 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new c23e94a9aec 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 809e1de4c6b 115: onsuccess: #645: 1: Success after binutils: 27 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 (68f64b1f25f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] 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 1736 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 39548 -> 39492 bytes 04-build_abe-gcc/console.log.xz | Bin 214172 -> 214644 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8276 -> 8420 bytes 07-build_abe-glibc/console.log.xz | Bin 244944 -> 244912 bytes 08-build_abe-gdb/console.log.xz | Bin 38796 -> 38912 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3832 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2136 -> 2208 bytes 11-check_regression/console.log.xz | Bin 5716 -> 4764 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 20 +- 12-update_baseline/console.log | 56 ++--- 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 | 26 +-- sumfiles/binutils.log.xz | Bin 63288 -> 63072 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 81792 -> 81772 bytes sumfiles/gas.sum | 275 +++++++++++------------ sumfiles/ld.log.xz | Bin 121940 -> 121704 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 26 files changed, 404 insertions(+), 399 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