Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/interesting-commits] branch master updated (10b8e58 -> 5d22adb)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from 10b8e58 Add entry e07ead85a368173a56e96a21d6841aa497ad80f8 from https [...] new 5d22adb Add entry e07ead85a368173a56e96a21d6841aa497ad80f8 from https [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: .../build_url | 2 +- .../last_good | 0 .../summary.txt | 0 .../e07ead85a368173a56e96a21d6841aa497ad80f8/tcwg_kernel/status.txt | 3 +++ 4 files changed, 4 insertions(+), 1 deletion(-) copy llvm/sha1/e07ead85a368173a56e96a21d6841aa497ad80f8/tcwg_kernel/{llvm-master-a [...] copy llvm/sha1/e07ead85a368173a56e96a21d6841aa497ad80f8/tcwg_kernel/{llvm-master-a [...] copy llvm/sha1/e07ead85a368173a56e96a21d6841aa497ad80f8/tcwg_kernel/{llvm-master-a [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-arm updated (0889e07cff -> b0ce12373f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-arm in repository toolchain/ci/base-artifacts. discards 0889e07cff 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits discards 5c7dced54b 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits discards 936ea7de6d 142: onsuccess: #1761: 1: Success after gcc: 83 commits discards 6258b223aa 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] discards bc00ac19dd 140: onsuccess: #1756: 1: Success after binutils: 3 commits discards 84b4480c3d 139: onsuccess: #1753: 1: Success after binutils: 5 commits discards ea203aef55 138: onsuccess: #1749: 1: Success after binutils: 5 commits discards e94ed7158d 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] discards 68d1834fd3 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] discards 47eaee5e3d 135: onsuccess: #1739: 1: Success after binutils: 4 commits discards 1f2fc460dd 134: onsuccess: #1736: 1: Success after binutils: 3 commits discards 9296b80cd5 133: onsuccess: #1733: 1: Success after binutils: 3 commits discards 9aff1cde80 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits discards ce23e6ba9a 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits discards d41aeafc1c 130: onsuccess: #1729: 1: Success after gcc: 9 commits discards 2396109580 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] discards b05a37d6f9 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits discards b47d51ca2f 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] discards a0266a154e 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits discards 491ff368bd 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits discards 10a12d5fa0 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits discards eef05ee72f 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits discards ebbaee5e46 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits discards d876abd8dc 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits discards 460bc72f2c 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits discards e5b95566b4 119: onsuccess: #1715: 1: Success after binutils: 4 commits discards 614c0d5fb6 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits discards c43e28f133 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits discards d29bb678c1 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits discards 1f769f7ca5 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits discards 9253f2b07d 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits discards 63fb595f2f 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards 74f2ef03c4 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards 2ad2f26943 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards bade91755d 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards c5d43a6a4c 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] discards 905b3336df 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards 2b4ff61d97 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] discards f636ee9dc3 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards b86c0a087e 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards c329d60511 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards c4b4ae4d5f 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits discards b39403d772 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits discards f6c174ca5e 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits discards 3cbdb623ac 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] discards e0195304e1 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits discards a46042ef9a 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits discards e0e4c740a2 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits discards 6e8f8b015c 96: onsuccess: #1654: 1: Success after gcc: 5 commits discards 8df32b9b7d 95: onsuccess: #1653: 1: Success after gcc: 13 commits discards 3fa946b9eb 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits discards 188d338a54 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] discards 42add4f1ad 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits discards e9d5efaeca 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] discards dbfb19c43b 90: onsuccess: #1645: 1: Success after gcc: 2 commits discards 5a048027b9 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] discards 9b811372b9 88: onsuccess: 1: Success after binutils/gcc: 2 commits discards 8950595aeb 87: onsuccess: 1: Success after gcc: 6 commits discards af9ee7efbb 86: onsuccess: 1: Success after binutils/gcc: 8 commits discards 98e329f9e9 85: onsuccess: 1: Success after binutils/gcc: 19 commits discards fd3716ef28 84: onsuccess: 1: Success after binutils/gcc: 2 commits discards 780a708bd2 83: onsuccess: 1: Success after gcc: 14 commits discards 1d83dc624f 82: onsuccess: 1: Success after binutils/gcc: 9 commits discards 9d3c6f1369 81: onsuccess: 1: Success after binutils/gcc: 8 commits discards efe2f3e556 80: onsuccess: 1: Success after binutils/gcc: 8 commits discards 858e1a4a87 79: onsuccess: 1: Success after binutils/gcc: 23 commits discards 6d3bbbcca6 78: onsuccess: 1: Success after binutils/gcc: 17 commits discards a52d3dd13c 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 1bfdcaf087 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 6d0b61ce1e 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 594442a583 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits discards 79ca94026d 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards bc16527546 72: onsuccess: 1: Successful build after baseline build: no [...] discards 5d96515645 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards df0f732ddd 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards db88ab3311 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] discards a4b70f1570 68: onsuccess: 1: Successful build after gcc: 2 commits discards 633bd3f95a 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards c0ea2d0070 66: onsuccess: 1: Successful build after gcc: 4 commits discards e226eb64d3 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 4dd572a67a 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 8e5eb8e43c 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 1fd2a1c781 62: onsuccess: 1: Successful build after gcc: 4 commits discards ba89b5c71d 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards f17bd15d94 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards 25e2ebb297 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits discards 2df46c6552 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] discards dd87b2d452 57: onsuccess: 1: Successful build after binutils: 2 commits discards 2bb278ac9a 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 89549cfb56 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards dfc35b6d82 54: onsuccess: 1: Successful build after gcc: 5 commits discards 5d43eed341 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 03f7cb9bf8 52: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 86c2d12dd5 51: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 58684b956f 50: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards cbd423ef79 49: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards c4f7d226da 48: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards a67312b45f 47: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 12913f6489 46: onsuccess: 1: Successful build after baseline build: no [...] discards e78923c6c3 45: onsuccess: 1: Successful build after binutils: Fix crash [...] discards df4b827e66 44: onsuccess: 1: Successful build after binutils/gcc: 2 commits new ba1e8dc440 44: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 9c6b43a87c 45: onsuccess: 1: Successful build after binutils: Fix crash [...] new 6445f8f0e9 46: onsuccess: 1: Successful build after baseline build: no [...] new 9d02d5440e 47: onsuccess: 1: Successful build after binutils/gcc: 4 commits new c91f103400 48: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 7f79597baf 49: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 861517e70e 50: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 9e60824f5c 51: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 28deece49d 52: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 6363339345 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 254e69fe6b 54: onsuccess: 1: Successful build after gcc: 5 commits new 23d728e938 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 3990fa13e9 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 32ad536c78 57: onsuccess: 1: Successful build after binutils: 2 commits new 6b447cb7dd 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] new 03c30e7652 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits new c8039bbdba 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits new 788eeca06d 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 59da154016 62: onsuccess: 1: Successful build after gcc: 4 commits new 0d0b4f3f78 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 2ef3954181 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 85f3cf3a20 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 1cf382205a 66: onsuccess: 1: Successful build after gcc: 4 commits new 4bd8e6c18f 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new aa9839de24 68: onsuccess: 1: Successful build after gcc: 2 commits new 209608a0fa 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] new 3f62356a49 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 584644dbc3 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 835fd0a88b 72: onsuccess: 1: Successful build after baseline build: no [...] new 6a35a727bc 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits new de987583eb 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits new a66b804122 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 7787194811 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 24cf76e20b 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits new b5e7890a22 78: onsuccess: 1: Success after binutils/gcc: 17 commits new 85eeee9dba 79: onsuccess: 1: Success after binutils/gcc: 23 commits new 0b6ebc3156 80: onsuccess: 1: Success after binutils/gcc: 8 commits new 1cd1a1f3b1 81: onsuccess: 1: Success after binutils/gcc: 8 commits new cbe5e176f3 82: onsuccess: 1: Success after binutils/gcc: 9 commits new ae90d0cc4d 83: onsuccess: 1: Success after gcc: 14 commits new c522446002 84: onsuccess: 1: Success after binutils/gcc: 2 commits new c173bcf7b2 85: onsuccess: 1: Success after binutils/gcc: 19 commits new f7f0459774 86: onsuccess: 1: Success after binutils/gcc: 8 commits new c1b3647211 87: onsuccess: 1: Success after gcc: 6 commits new 983a19c80b 88: onsuccess: 1: Success after binutils/gcc: 2 commits new caaede8d6b 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] new c8bf6b90fb 90: onsuccess: #1645: 1: Success after gcc: 2 commits new a4b0dcb448 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] new 93f5729f9d 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits new ccff2b47b5 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] new c44dcf0d32 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits new 69e091c72d 95: onsuccess: #1653: 1: Success after gcc: 13 commits new 7edd815d5e 96: onsuccess: #1654: 1: Success after gcc: 5 commits new 340b4255e7 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits new a1def53bb8 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits new f77b877771 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits new 998133b968 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] new 7f99161db0 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits new 3ea3a70883 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits new b3075a9002 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new d41392fdf0 104: onsuccess: #1700: 1: Success after gcc: 2 commits new 2f233868bf 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new d4f6eccde9 106: onsuccess: #1702: 1: Success after gcc: 4 commits new a34a5edc14 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] new a567105609 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new 4555a05922 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] new 04ae5e422b 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new 78ae0a54c3 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new 63da8d64cd 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new 798f31fc1e 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new c61b385d23 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits new 4664e28d3e 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits new 862393c7f5 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits new 2e83c534c6 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits new 25cc6d4f76 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits new f5c80f6c91 119: onsuccess: #1715: 1: Success after binutils: 4 commits new bd5966f9e9 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits new 9b91520200 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits new 12a6735e4b 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits new 0875c37659 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits new be7fe19d99 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits new de6d72c77d 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits new 298029fc1b 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits new f7deea452d 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] new 2f3aa5d482 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits new b7c322eef4 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] new 290ef386c2 130: onsuccess: #1729: 1: Success after gcc: 9 commits new 986c3d79eb 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits new 200116e8ae 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits new 9f4afd1a7b 133: onsuccess: #1733: 1: Success after binutils: 3 commits new db6b084216 134: onsuccess: #1736: 1: Success after binutils: 3 commits new db9683ea21 135: onsuccess: #1739: 1: Success after binutils: 4 commits new e4a10d2e40 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] new fecf7863bb 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] new dd8641446d 138: onsuccess: #1749: 1: Success after binutils: 5 commits new 534fade5df 139: onsuccess: #1753: 1: Success after binutils: 5 commits new 3b2705d0c4 140: onsuccess: #1756: 1: Success after binutils: 3 commits new da59ac4dae 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] new e098e01a69 142: onsuccess: #1761: 1: Success after gcc: 83 commits new 0a97b8e985 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits new 3ec250ddd7 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits new b0ce12373f 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (0889e07cff) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (b0 [...] 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 1676 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 51064 -> 50672 bytes 04-build_abe-gcc/console.log.xz | Bin 233100 -> 232240 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3804 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2592 -> 2736 bytes 07-check_regression/console.log.xz | Bin 5452 -> 5464 bytes 07-check_regression/extra-bisect-params | 1 + 07-check_regression/fails.sum | 7 + 07-check_regression/mail-body.txt | 34 +- 07-check_regression/results.compare | 28 +- 07-check_regression/results.compare2 | 145 +- .../results.regressions | 35 +- 08-update_baseline/console.log | 56 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 27 + sumfiles/g++.log.xz | Bin 2798148 -> 2778720 bytes sumfiles/g++.sum | 116 +- sumfiles/gcc.log.xz | Bin 2347388 -> 2381068 bytes sumfiles/gcc.sum | 4818 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 908900 -> 914984 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2160 -> 2172 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 204380 -> 204524 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2548 -> 2532 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 462528 -> 464936 bytes sumfiles/libstdc++.sum | 10 +- 36 files changed, 2722 insertions(+), 2687 deletions(-) create mode 100644 07-check_regression/extra-bisect-params create mode 100644 07-check_regression/fails.sum copy mail/mail-body.txt => 07-check_regression/results.regressions (58%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allyesconfig updated (0327e6e31c -> b75dc13dc8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allyesconfig in repository toolchain/ci/base-artifacts. from 0327e6e31c 17: onsuccess: #478: 20954: Success after qemu: 118 commits new b75dc13dc8 18: force: #479: 20954: Success after llvm: 30 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1772 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30088 -> 30032 bytes 04-build_kernel_llvm/console.log.xz | Bin 62504 -> 62812 bytes 05-build_abe-qemu/console.log.xz | Bin 31208 -> 31228 bytes 06-build_linux/console.log.xz | Bin 5744 -> 5732 bytes 08-check_regression/console.log.xz | Bin 2988 -> 3020 bytes 09-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +++++++------- 14 files changed, 13 insertions(+), 13 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (ca61c02b45 -> 3943ef17c3)

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-aarch64 in repository toolchain/ci/base-artifacts. discards ca61c02b45 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 716e75cfe3 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 4a5f7126a3 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 098c778525 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards c1c9e285a3 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 6ff51d2f77 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 3d3d6ad826 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards dd2518f5f9 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 776c75ef77 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards ce45154710 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 863e5c781a 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards d8bae3f689 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards af8166c7d5 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 072bb16431 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 5dcfcdc07e 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 57a86c5120 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 34c525236c 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 139b987915 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 104d0201e7 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards db63b028b7 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 19fde11b1a 124: onsuccess: #2159: 1: Success after linux: 23 commits discards dacf19a3c3 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 4f791791b7 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 889a2782ef 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 3a36c6c046 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards de494da3aa 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 9353fd2f1c 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 1d05e93568 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 6698a29ca8 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 0aab5795a1 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 40ce0eb38a 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards b29cab3f3b 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards cc71706965 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 333549c8e3 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 732109ff19 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 0572a129ac 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 1147a614ed 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards df0a126fbd 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards e8dbe7945c 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 329ac8f71e 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards e7101e1f17 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 7c8abf8148 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 0ed4e327ce 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 56200baf9a 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 7429d6df35 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards ed58ee5769 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 82c202a2f2 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards b8ece9096a 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 8b0d4129a9 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 4924a09012 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards bc7fb63495 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards c97fbaadcd 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards d35d9af008 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 23e74b3960 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards c44754c976 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 720824ce7b 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards dfb04e6904 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 3699c9ad8b 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards b99ae2b216 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards d6e8ec44b0 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 4dcb0ee794 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 7324229d23 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 49a8ec890d 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 4e7908b3dd 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards a65a0159e7 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards cce1c8d871 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 013ac56063 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards d22e298b04 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards e73bd2505d 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ae4a06046b 75: onsuccess: 1: Successful build after linux: 44 commits discards 37c4d2042d 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 011ba2bf59 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 81f8ea66b9 72: onsuccess: 1: Successful build after linux: 12 commits discards 834dc23130 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 42c40d7b79 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 28d74518b4 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 8811920845 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 75337e0acc 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 0a60a8b8c4 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 17ff15c2e2 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 92b2d448a6 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c8e9e63db1 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 802563cbad 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 823a585d85 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 82b15dd902 60: onsuccess: 1: Successful build after glibc: 2 commits discards ef01651b3e 59: onsuccess: 1: Successful build after binutils: 2 commits discards 075b818817 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 7db3f0324b 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2447fe8794 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 633b3506cd 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards ec9b5c2ef3 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 0dd6c6a1e4 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 84c7016f0c 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 9cff3a5581 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a578111d8c 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards df07fe6b22 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 5f56201ca0 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e4c56ea6b4 47: onsuccess: 1: Successful build after linux: 10 commits discards b794509600 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 7d1aa79ddb 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4c8e64bfeb 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 6a3aecdc0b 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new b3b34b6601 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8cd2a5c101 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 9a46de5cb9 47: onsuccess: 1: Successful build after linux: 10 commits new a7954c698e 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 866a8a9e4b 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new a96bbf4538 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 540dd0d969 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 74d6dfc93b 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new c1c2961d04 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 3b72d5e8f2 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new a02e4b37cc 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 9e629da782 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 750b7d20db 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 408a03c40b 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new e08e809406 59: onsuccess: 1: Successful build after binutils: 2 commits new ee141547be 60: onsuccess: 1: Successful build after glibc: 2 commits new 17775cfbad 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 88bc304076 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new b9def31c05 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new d62e56a854 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 08155e106c 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d439142b2e 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 1b68c19ffa 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new cfa25305ab 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 75d33ee957 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new a2de583ccf 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 84494f2f72 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new bb29e2732e 72: onsuccess: 1: Successful build after linux: 12 commits new 5148cc9cfc 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8ed00318f2 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 7dc0771d39 75: onsuccess: 1: Successful build after linux: 44 commits new 0c08bef861 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0e87defb6d 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 3f5ea8ccf3 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 70e87cb461 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d1cc036524 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 137da7954d 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 2e19f43b5e 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 2077b478bd 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 785deca647 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 1f5ee70afe 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 593d153e9b 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 89cea660f7 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 5d39123d1d 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 8665cdc360 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new da3f10b913 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new cba44c13f4 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 04cb8b2b6a 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 6e41d0dbc8 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 43bfd02c40 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 89d38dcad3 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new e6c47c7bf6 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new f9a032c510 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 1654b1d68b 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 51e592e2f1 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new dc320e504a 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new cf6413bf20 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 878127e2d0 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new ddd8788c48 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new ba073081f2 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new c4d2350b3c 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 39acccc973 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 0d19cdf1f2 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new cd45df225a 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new e595e5ffd4 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new b05dfc05d3 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new e3e912cf3f 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 4a2e9decc2 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 5181a21259 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 53f41d8e41 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 0156404bc9 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new f9dbedf1c8 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 986702590c 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new a905f9eb34 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 0f9cbcfe65 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 69935ab006 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 0e44afa5ae 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 4348a3c025 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 901d3006af 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 7484b3c9c7 124: onsuccess: #2159: 1: Success after linux: 23 commits new 9059c2b63b 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new b36a3219e6 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 5f9a3b9946 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 1cedef2da6 128: onsuccess: #2163: 1: Success after linux: 23 commits new 3cc39e45d8 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new dc2d559315 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 1f106314c6 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new c60979b242 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 8fbb5b9f96 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 64a71d5d96 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 8beaa9ac8c 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 3d99b06d8a 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 505b00255f 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 16b9b0c344 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 99f1bb7fec 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 5431a7d60f 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new e7d681620f 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new dc2283d773 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 5dfe1e8c9d 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 787481397c 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 3943ef17c3 145: onsuccess: #2180: 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 (ca61c02b45) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1740 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 30200 -> 30300 bytes 04-build_abe-stage1/console.log.xz | Bin 72464 -> 72300 bytes 06-build_abe-linux/console.log.xz | Bin 9288 -> 8472 bytes 07-build_abe-glibc/console.log.xz | Bin 240172 -> 239608 bytes 08-build_abe-stage2/console.log.xz | Bin 202948 -> 202884 bytes 09-build_abe-gdb/console.log.xz | Bin 37528 -> 37496 bytes 10-build_abe-qemu/console.log.xz | Bin 31820 -> 31904 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2660 -> 2784 bytes 13-check_regression/console.log.xz | Bin 7032 -> 8936 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 52 +- 13-check_regression/mail-body.txt | 175 +- 13-check_regression/results.compare | 77 +- 13-check_regression/results.compare2 | 488 +++- 13-check_regression/results.regressions | 77 +- 14-update_baseline/console.log | 54 +- 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 | 177 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 77 +- sumfiles/g++.log.xz | Bin 3413944 -> 3439504 bytes sumfiles/g++.sum | 94 +- sumfiles/gcc.log.xz | Bin 3024756 -> 3011328 bytes sumfiles/gcc.sum | 4797 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1028436 -> 1035292 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202196 -> 202308 bytes sumfiles/libgomp.sum | 12 +- sumfiles/libitm.log.xz | Bin 2660 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 424008 -> 425728 bytes sumfiles/libstdc++.sum | 2 +- 43 files changed, 3399 insertions(+), 2745 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 updated (643c47daec -> f5999a488d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. from 643c47daec 46: onsuccess: #818: 1: Success after binutils: 10 commits new f5999a488d 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] 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 1672 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 37180 -> 37552 bytes 04-build_abe-gcc/console.log.xz | Bin 211260 -> 211136 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8776 -> 8336 bytes 07-build_abe-glibc/console.log.xz | Bin 239156 -> 239492 bytes 08-build_abe-gdb/console.log.xz | Bin 37180 -> 37692 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3820 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2028 -> 2272 bytes 11-check_regression/console.log.xz | Bin 13980 -> 13912 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 36 +- 11-check_regression/mail-body.txt | 111 +- 11-check_regression/results.compare | 58 +- 11-check_regression/results.compare2 | 1373 +----- 11-check_regression/results.regressions | 58 +- 12-update_baseline/console.log | 9 + dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 113 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 58 +- sumfiles/gdb.log.xz | Bin 1881556 -> 1816460 bytes sumfiles/gdb.sum | 7416 +++++++++---------------------- 31 files changed, 2582 insertions(+), 6702 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[binutils-gdb] branch master updated (1d4c108cec2 -> 0d94a873505)

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 1d4c108cec2 [gdb/testsuite] Fix gdb.mi/mi-sym-info.exp on openSUSE Tumbleweed new 0d94a873505 gprofng: fix cppcheck warnings 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: gprofng/common/hwcdrv.c | 2 +- gprofng/src/ABS.h | 2 +- gprofng/src/CompCom.cc | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allyesconfig updated (f26d3d6d42 -> 0327e6e31c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allyesconfig in repository toolchain/ci/base-artifacts. from f26d3d6d42 16: onsuccess: #476: 20954: Success after binutils: 24 commits new 0327e6e31c 17: onsuccess: #478: 20954: Success after qemu: 118 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1672 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30088 -> 30088 bytes 04-build_kernel_llvm/console.log.xz | Bin 64832 -> 62504 bytes 05-build_abe-qemu/console.log.xz | Bin 31556 -> 31208 bytes 06-build_linux/console.log.xz | Bin 5904 -> 5744 bytes 08-check_regression/console.log.xz | Bin 3064 -> 2988 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 14 files changed, 19 insertions(+), 19 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

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

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-norov-allmodconfig in repository toolchain/ci/base-artifacts. from 31da2d521a 14: force: #53: 23330: Success after llvm: 27 commits new a50ce4f03b 15: force: #54: 36: Failure after llvmorg-16-init-5673-ge07e [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1752 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30364 -> 30276 bytes 04-build_kernel_llvm/console.log.xz | Bin 63728 -> 63752 bytes 05-build_abe-qemu/console.log.xz | Bin 31376 -> 31076 bytes 06-build_linux/console.log.xz | Bin 3740 -> 3952 bytes 08-check_regression/console.log.xz | Bin 3008 -> 3720 bytes 08-check_regression/jira-body.txt | 2 +- 08-check_regression/mail-body.txt | 11 +- 08-check_regression/mail-subject.txt | 2 +- 08-check_regression/results.regressions | 7 + 08-check_regression/trigger-bisect | 2 + 08-check_regression/trigger-notify | 0 dashboard/dashboard-generate.sh | 2 +- git/llvm_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 440 ++++++++++++++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 11 +- mail/mail-subject.txt | 2 +- manifest.sh | 12 +- results | 9 +- 25 files changed, 496 insertions(+), 17 deletions(-) create mode 100644 08-check_regression/results.regressions create mode 100644 08-check_regression/trigger-bisect create mode 100644 08-check_regression/trigger-notify create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/interesting-commits] branch master updated (099c2c0 -> 10b8e58)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from 099c2c0 Add entry e07ead85a368173a56e96a21d6841aa497ad80f8 from https [...] new 10b8e58 Add entry e07ead85a368173a56e96a21d6841aa497ad80f8 from https [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: .../tcwg_kernel/llvm-master-aarch64-norov-allmodconfig}/build_url | 2 +- .../last_good | 0 .../summary.txt | 0 .../e07ead85a368173a56e96a21d6841aa497ad80f8/tcwg_kernel/status.txt | 3 +++ 4 files changed, 4 insertions(+), 1 deletion(-) copy {linux/sha1/3dd33a09f5dc12ccb0902923c4c784eb0f8c7554/tcwg_kernel/llvm-master- [...] copy llvm/sha1/e07ead85a368173a56e96a21d6841aa497ad80f8/tcwg_kernel/{llvm-master-a [...] copy llvm/sha1/e07ead85a368173a56e96a21d6841aa497ad80f8/tcwg_kernel/{llvm-master-a [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[binutils-gdb] branch master updated (511f4ff4d9b -> 1d4c108cec2)

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 511f4ff4d9b [gdb/testsuite] Add aranges to gdb.dwarf2/dw2-dir-file-name.exp new f3700471469 gdb: Remove unused extra_lines variable new d6b99a80716 RISC-V: Add privileged extensions without instructions/CSRs new 1d4c108cec2 [gdb/testsuite] Fix gdb.mi/mi-sym-info.exp on openSUSE Tumbleweed The 3 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: bfd/elfxx-riscv.c | 3 +++ gdb/testsuite/gdb.mi/mi-sym-info.exp | 3 ++- gdb/xcoffread.c | 8 -------- 3 files changed, 5 insertions(+), 9 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022