Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[gcc] branch master updated (13ec81eb4c3 -> d495ea2b232)

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 13ec81eb4c3 Daily bump. new d495ea2b232 diagnostics: ensure that .sarif files are UTF-8 encoded [PR109098] 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/diagnostic-format-sarif.cc | 78 +++---------- gcc/input.cc | 125 +++++++++++++++++++++ gcc/input.h | 1 + .../c-c++-common/diagnostic-format-sarif-file-1.c | 1 + .../c-c++-common/diagnostic-format-sarif-file-2.c | 2 + .../c-c++-common/diagnostic-format-sarif-file-3.c | 2 + .../c-c++-common/diagnostic-format-sarif-file-4.c | 2 + .../diagnostic-format-sarif-file-Wbidi-chars.c | 23 ++++ ...gnostic-format-sarif-file-bad-utf8-pr109098-1.c | 23 ++++ ...gnostic-format-sarif-file-bad-utf8-pr109098-2.c | 16 +++ ...gnostic-format-sarif-file-bad-utf8-pr109098-3.c | 95 ++++++++++++++++ .../diagnostic-format-sarif-file-valid-CP850.c | 22 ++++ gcc/testsuite/gcc.dg/plugin/crash-test-ice-sarif.c | 1 + .../plugin/crash-test-write-though-null-sarif.c | 1 + .../gcc.dg/plugin/diagnostic-test-paths-5.c | 2 + gcc/testsuite/lib/scansarif.exp | 29 +++++ gcc/testsuite/lib/verify-sarif-file.py | 11 ++ libcpp/charset.cc | 27 +++++ libcpp/include/cpplib.h | 1 + 19 files changed, 401 insertions(+), 61 deletions(-) create mode 100644 gcc/testsuite/c-c++-common/diagnostic-format-sarif-file-Wbidi-chars.c create mode 100644 gcc/testsuite/c-c++-common/diagnostic-format-sarif-file-bad-utf [...] create mode 100644 gcc/testsuite/c-c++-common/diagnostic-format-sarif-file-bad-utf [...] create mode 100644 gcc/testsuite/c-c++-common/diagnostic-format-sarif-file-bad-utf [...] create mode 100644 gcc/testsuite/c-c++-common/diagnostic-format-sarif-file-valid-CP850.c create mode 100644 gcc/testsuite/lib/verify-sarif-file.py -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (f6085b956dc -> dd0ee1ca93e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards f6085b956dc 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] discards 23034e963da 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] discards b56ef3a8e0b 219: force: #50: 1: Failure after linux: 2520 commits discards 5ae404e006c 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] discards abbc626556b 217: force: #45: 1: Success after linux: 1 commits discards 1d8931c005d 216: force: #43: : Failure after baseline build: no new commits discards 0deb1dd5e57 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 8976690ef02 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 5f73003f61c 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 43dc469b7a9 212: force: #27: : Failure after baseline build: no new commits discards 3aeb30670d0 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 0a4ed564db3 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 70d4b6aaa21 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 5fb0dbd97a1 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 560c295a74f 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 6c468f168fd 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards dac63edf22b 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 7bfa5d7880c 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards ad18fb34cae 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 1ffc5e43688 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 64a21722d5a 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 84d1d045717 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 3c3f36f6d7a 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards eeaa4478972 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 391776064b0 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards debdef72440 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 7f859764325 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 094753995a0 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 3b6273d70d2 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 02010650733 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 95e31df7a88 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 1db7da68194 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards dbece5b43bd 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards e014e2566c4 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards 8acd5e7a8b7 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 8a880a43704 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards c4cd163b457 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 91c26c3f62c 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards b54491dbb1a 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards e8c62c7cf8d 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards fcae719b2e1 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 86104176ffe 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards e250fbfbf35 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 54df284acab 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 7609246cb3e 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards fa61f2be9f7 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards ca55176f72a 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 9aa001b7897 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 49cb0f638be 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 4f0f0b5114a 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 9531f50b02c 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 9df5fb69aae 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 2e046ed0b65 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards b6bba74a470 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 2325bbd97f7 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards dc0d3f1f82f 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards a8ec68362d3 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 4449d5e106c 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 27c4a76b6c9 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards a3d2b03f885 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards eea7dbde5f9 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards e71ab6d40a9 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 4e44936d807 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 87606e34ea9 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 4db4bb22e23 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 6f8eec63c19 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 604ff50f73e 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 243dcbb07fe 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 17cdf0acf21 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards a964c11d9b7 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 95f5d4184f0 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 54e2a3851c1 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 59f440cac77 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 9284aab7955 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 988055fcbad 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards 58859b294d0 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards eca09d8f728 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards e2228d91095 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards 809e6c6e1ad 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards bd3a1e5384d 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards eabb81108ed 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards a50078ec03d 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 341ee9b3fcc 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 82168ab00df 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 27dc1560516 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards b5883597a56 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 9164a912c04 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 8cc079ca0b3 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards c5a20ea3d93 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards a45b75253c7 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 7f2efa4c5cc 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards c6328a4bd7b 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards 0792db74c61 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 6d8d35ba520 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards d53e563a185 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 1ae32b58e73 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 317b203ded5 125: onsuccess: #614: 1: Success after linux: 12 commits discards ae980169a5c 124: onsuccess: #612: 1: Success after binutils: 18 commits discards c5376006567 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards d38e3f22153 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 1f70b42a0cc 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new de116694245 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 28800a97e87 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new b0b3c2911f0 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new ae5ed12bab8 124: onsuccess: #612: 1: Success after binutils: 18 commits new 3d57354fd25 125: onsuccess: #614: 1: Success after linux: 12 commits new 06db7252b7b 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 88240a506a1 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new e34104f0b49 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 7a89714b7be 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 765a48d1ce0 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new b9cfc33ac3d 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 018fea9e3d5 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 93278a44c37 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new f5b60fbc060 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new b993c3d303a 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 57ec07ede44 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new eaaa3911e8f 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 914eb26f771 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new ac99098f702 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new c3e65fb6cbd 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 480eab6d795 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 1e37a933538 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new d46a1b0ea97 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 06dd4fb2fbb 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new 4b721e31198 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 256729f3042 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 17196588f88 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 1b259cfbef4 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 7d98ed1ca5f 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new ba617340acf 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 4a077d82542 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new fd0b15a6694 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 613747f55c2 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 474772e7c0c 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 06577a1be3d 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 8effcc911d8 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new f72ec504448 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 16486c599af 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new b7f1607a6bb 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new eacae59b83c 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 261231ebf55 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new d792d762ac3 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new a3b5f93d8a6 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new dbed61e82a1 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new a68391e52f6 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new e92a93ec89d 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 03dea317819 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 64fbb3c1ba3 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new c5e6c8559a4 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new f6f1b7518fc 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 7e6935922c2 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 26eb7b67e64 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new fdc28085130 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 1d7081240c4 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new ae0fe21e5b9 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 942fce2a5da 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 74ec54da26d 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 173d4476008 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new e45fa26f79a 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 340c7653e44 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 156b06ed48a 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 17766137f3c 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 3eae43b1961 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 87435fd29a0 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new 28045495bc8 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 910e8f04566 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new 2523d8612bf 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 706118541be 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new ed1dc937f8c 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 645c0db4833 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 89726698160 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 73aef8aa430 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 118752d3fd3 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new e9f03d575e0 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 7f515203b78 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new a93304f19ce 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 2b8f4508832 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 844a67e4bef 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 526c3a8e73a 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new e3eb58ed316 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 06b040e6e78 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 239b1c98c6f 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 6e5651af2d0 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 68fd83baa78 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 4b1fdd570b7 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 1cb8a86a4d8 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new aa66c814098 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 553bdfc815d 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 47d509d9500 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 59c8f05f39c 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 2a366154225 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new befa33b9700 212: force: #27: : Failure after baseline build: no new commits new 5043cccf4db 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 0927d5ba587 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new 1ab0d71c248 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new 787a4103359 216: force: #43: : Failure after baseline build: no new commits new c1a07c20779 217: force: #45: 1: Success after linux: 1 commits new c1dfbb1e0a0 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] new a78d6cf4023 219: force: #50: 1: Failure after linux: 2520 commits new 6ed041e5075 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] new 78c06658fda 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] new dd0ee1ca93e 222: force: #60: 1: Success after gdb: 16 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 (f6085b956dc) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2072 -> 2052 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 48680 -> 49000 bytes 04-build_abe-gcc/console.log.xz | Bin 236424 -> 235968 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8556 -> 8588 bytes 07-build_abe-glibc/console.log.xz | Bin 233076 -> 233684 bytes 08-build_abe-gdb/console.log.xz | Bin 46984 -> 47232 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3788 -> 3772 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4496 -> 4700 bytes 11-check_regression/console.log.xz | Bin 3216 -> 3208 bytes 11-check_regression/jira-body.txt | 1 - 11-check_regression/mail-body.txt | 2 +- 11-check_regression/results.compare | 19 +- 12-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 1 - mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/gdb.log.0.xz | Bin 2930820 -> 2959316 bytes sumfiles/gdb.log.1.xz | Bin 185224 -> 138376 bytes sumfiles/gdb.log.10.xz | Bin 0 -> 10096 bytes sumfiles/gdb.log.11.xz | Bin 0 -> 10364 bytes sumfiles/gdb.log.12.xz | Bin 0 -> 10272 bytes sumfiles/gdb.log.13.xz | Bin 0 -> 10108 bytes sumfiles/gdb.log.14.xz | Bin 0 -> 10132 bytes sumfiles/gdb.log.2.xz | Bin 16820 -> 11924 bytes sumfiles/gdb.log.3.xz | Bin 14812 -> 10084 bytes sumfiles/gdb.log.4.xz | Bin 14976 -> 10364 bytes sumfiles/gdb.log.5.xz | Bin 10288 -> 10080 bytes sumfiles/gdb.log.6.xz | Bin 10312 -> 10144 bytes sumfiles/gdb.log.7.xz | Bin 10160 -> 10192 bytes sumfiles/gdb.log.8.xz | Bin 10364 -> 10108 bytes sumfiles/gdb.log.9.xz | Bin 10116 -> 10160 bytes sumfiles/gdb.sum | 3699 +++++++++++++- sumfiles/gdb.sum.0 | 3715 +++++++++++++- sumfiles/gdb.sum.1 | 8652 +-------------------------------- sumfiles/{gdb.sum.9 => gdb.sum.10} | 28 +- sumfiles/{gdb.sum.9 => gdb.sum.11} | 56 +- sumfiles/{gdb.sum.9 => gdb.sum.12} | 21 +- sumfiles/{gdb.sum.9 => gdb.sum.13} | 24 +- sumfiles/{gdb.sum.9 => gdb.sum.14} | 20 +- sumfiles/gdb.sum.2 | 198 +- sumfiles/gdb.sum.3 | 207 +- sumfiles/gdb.sum.4 | 206 +- sumfiles/gdb.sum.5 | 18 +- sumfiles/gdb.sum.6 | 45 +- sumfiles/gdb.sum.7 | 84 +- sumfiles/gdb.sum.8 | 32 +- sumfiles/gdb.sum.9 | 25 +- 52 files changed, 7808 insertions(+), 9337 deletions(-) delete mode 100644 11-check_regression/jira-body.txt delete mode 100644 mail/jira-body.txt create mode 100644 sumfiles/gdb.log.10.xz create mode 100644 sumfiles/gdb.log.11.xz create mode 100644 sumfiles/gdb.log.12.xz create mode 100644 sumfiles/gdb.log.13.xz create mode 100644 sumfiles/gdb.log.14.xz copy sumfiles/{gdb.sum.9 => gdb.sum.10} (99%) copy sumfiles/{gdb.sum.9 => gdb.sum.11} (98%) copy sumfiles/{gdb.sum.9 => gdb.sum.12} (99%) copy sumfiles/{gdb.sum.9 => gdb.sum.13} (99%) copy sumfiles/{gdb.sum.9 => gdb.sum.14} (99%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (2274ba0fe6a -> 4c56e5b4054)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-arm in repository toolchain/ci/base-artifacts. discards 2274ba0fe6a 490: onsuccess: #34: 7: Success after binutils/gcc/linux/gd [...] discards 9f779b34db2 489: onsuccess: #33: 7: Success after binutils/gcc/linux/gd [...] discards be661a9fa8b 488: onsuccess: #32: 7: Success after binutils/gcc/linux/gl [...] discards 82a630810c4 487: onsuccess: #31: 7: Success after binutils/gcc/linux/gd [...] discards 9b340f58366 486: onsuccess: #30: 7: Success after binutils/gcc/linux/gd [...] discards e4015bfd497 485: onsuccess: #29: 7: Success after binutils/gcc/linux/gd [...] discards 9cf6ede4946 484: onsuccess: #28: 7: Success after binutils/gcc/linux/gd [...] discards 4ab06d7be4c 483: onsuccess: #27: 7: Success after binutils/gcc/linux/gd [...] discards ca26b924760 482: onsuccess: #26: 7: Success after binutils/gcc/linux/gd [...] discards fe3856fe6b4 481: onsuccess: #25: 7: Success after binutils/gcc/linux/gl [...] discards 8132320dcf9 480: onsuccess: #24: 7: Success after binutils/gcc/linux/gl [...] discards 1b6b00e3635 479: onsuccess: #23: 7: Success after binutils/gcc/linux/gd [...] discards e81e332f93a 478: onsuccess: #22: 7: Success after binutils/gcc/linux/gd [...] discards 83f3f2f6fa7 477: onsuccess: #21: 7: Success after binutils/gcc/linux/gl [...] discards 8952c3d5494 476: onsuccess: #20: 7: Success after binutils/gcc/linux/gd [...] discards dc5769c725c 475: onsuccess: #19: 7: Success after binutils/gcc/linux/gl [...] discards 911344e97a1 474: onsuccess: #18: 7: Success after binutils/gcc/linux/gl [...] discards 18b288f3e08 473: onsuccess: #17: 7: Success after binutils/gcc/linux/gl [...] discards c04a805c20e 472: onsuccess: #16: 7: Success after binutils/gcc/linux/gd [...] discards 6d9d1bef09f 471: onsuccess: #15: 7: Success after binutils/gcc/linux/gd [...] discards a7393580306 470: onsuccess: #14: 7: Success after binutils/gcc/linux/gd [...] discards bcf80672f67 469: onsuccess: #13: 7: Success after binutils/gcc/linux/gl [...] discards 8096714ee50 468: onsuccess: #12: 7: Success after binutils/gcc/linux/gl [...] discards c85a4799a55 467: onsuccess: #11: 7: Success after binutils/gcc/linux/gl [...] discards de51c29ab45 466: onsuccess: #10: 7: Success after binutils/gcc/linux/gl [...] discards 7ca7ef6c0fd 465: onsuccess: #9: 7: Success after binutils/gcc/linux/gdb [...] discards ffd921b0211 464: onsuccess: #8: 7: Success after binutils/gcc/linux/gli [...] discards 88d10e3dc25 463: onsuccess: #7: 7: Success after binutils/gcc/gdb: 5 commits discards 1b9cfe7cfe0 462: onsuccess: #6: 7: Success after gcc/linux: 385 commits discards f4135a7fe01 461: onsuccess: #5: 7: Success after binutils/gcc/linux/gli [...] discards db6f884a94f 460: onsuccess: #4: 7: Success after binutils/gcc/gdb: 5 commits discards 40786eb4028 459: onsuccess: #3: 7: Success after binutils/gcc/glibc/gdb [...] discards 9401625d1c7 458: onsuccess: #2: 7: Success after gcc/linux/glibc: 581 commits discards f5a3ed03150 457: onsuccess: #2194: 7: Success after binutils/gcc/linux/ [...] discards 483b4bcc7bd 456: onsuccess: #1: 7: Success after binutils/gcc/linux/gli [...] discards 8bfaf7db162 455: onsuccess: #2193: 7: Success after binutils/gcc/gdb: 1 [...] discards 87857e45f58 454: onsuccess: #2192: 7: Success after binutils/linux/glib [...] discards 88a59b774d6 453: onsuccess: #2191: 7: Success after binutils/gcc/linux/ [...] discards 2d3641c632d 452: onsuccess: #2190: 7: Success after binutils/gcc/linux/ [...] discards f913452e46b 451: onsuccess: #2189: 7: Success after binutils/gcc/gdb: 1 [...] discards c9480193805 450: onsuccess: #2188: 7: Success after binutils/gcc/linux/ [...] discards 6094fc4ccf5 449: onsuccess: #2186: 7: Success after binutils/gcc/linux/ [...] discards cb299483500 448: onsuccess: #2185: 7: Success after binutils/gcc/gdb/qe [...] discards 359a3e3d81e 447: onsuccess: #2184: 7: Success after binutils/gcc/linux/ [...] discards 763d87ff131 446: onsuccess: #2183: 7: Success after binutils/gcc/linux/ [...] discards 21a10447c75 445: onsuccess: #2182: 7: Success after binutils/gcc/glibc/ [...] discards 95e4915688b 444: onsuccess: #2181: 7: Success after binutils/gcc/glibc/ [...] discards 5812ca7c3e5 443: onsuccess: #2180: 7: Success after binutils/gdb: 2 commits discards dbb4ac7dbfa 442: onsuccess: #2179: 7: Success after binutils/gcc/linux/ [...] discards e6711e82942 441: onsuccess: #2178: 7: Success after binutils/linux/gdb: [...] discards 2b2b9ab8de6 440: onsuccess: #2177: 7: Success after binutils/gcc/gdb: 6 [...] discards 021f0ae88b1 439: onsuccess: #2176: 7: Success after linux: 11 commits discards bc3a0ff3ec6 438: onsuccess: #2175: 7: Success after gcc: 7 commits discards 99d9777453d 437: onsuccess: #2174: 7: Success after gcc/linux: 9 commits discards 1c14e081593 436: onsuccess: #2173: 7: Success after binutils/gcc/linux/ [...] discards 15d24017757 435: onsuccess: #2172: 7: Success after binutils/gcc/glibc/ [...] discards cbc517457d9 434: onsuccess: #2171: 7: Success after gcc/glibc: 5 commits discards 07a38684f3d 433: onsuccess: #2170: 7: Success after binutils/gcc/linux/ [...] discards 4cfc6ee14d5 432: onsuccess: #2169: 7: Success after binutils/gcc/linux/ [...] discards 53ffafe8b5f 431: onsuccess: #2168: 7: Success after binutils/gcc/gdb/qe [...] discards 470fe376a07 430: onsuccess: #2167: 7: Success after binutils/gcc/gdb/qe [...] discards 48567c10b15 429: onsuccess: #2166: 7: Success after binutils/gcc/linux/ [...] discards 8e9a6b0ec91 428: onsuccess: #2165: 7: Success after binutils/gcc/glibc/ [...] discards 11c4aa21ecd 427: onsuccess: #2163: 7: Success after binutils/gdb: 4 commits discards 1c5689971e0 426: onsuccess: #2162: 7: Success after binutils/gcc/gdb: 1 [...] discards 60e8b05b641 425: onsuccess: #2161: 7: Success after binutils/gcc/linux/ [...] discards 8072a7ab862 424: onsuccess: #2160: 7: Success after binutils/gcc/glibc/ [...] discards 9a64c43a329 423: onsuccess: #2159: 7: Success after binutils/gcc/gdb: 5 [...] discards c1a7c0667ce 422: onsuccess: #2158: 7: Success after binutils/gcc/linux/ [...] discards adceb57871a 421: onsuccess: #2157: 7: Success after binutils/gcc/linux/ [...] discards 8df0cd55d1c 420: onsuccess: #2156: 7: Success after binutils/gcc/gdb: 2 [...] discards a587bc182a3 419: onsuccess: #2155: 7: Success after binutils/gcc/gdb: 4 [...] discards 997908653cf 418: onsuccess: #2154: 7: Success after binutils/gcc/linux/ [...] discards f952660e676 417: onsuccess: #2153: 7: Success after linux/glibc: 27 commits discards 19fa0a2aa1c 416: onsuccess: #2152: 7: Success after gcc: 50 commits discards ad3ae0a3cfa 415: onsuccess: #2151: 7: Success after binutils/gcc/gdb: 9 [...] discards bcc952f8d9c 414: onsuccess: #2150: 7: Success after binutils/gcc/linux/ [...] discards d159a16c916 413: onsuccess: #2149: 7: Success after binutils/gcc/linux/ [...] discards 5ea73fe010d 412: onsuccess: #2148: 7: Success after binutils/gcc/gdb: 6 [...] discards 0741e32cb13 411: onsuccess: #2147: 7: Success after binutils/gcc/gdb: 9 [...] discards 6cd9b8de4c2 410: onsuccess: #2146: 7: Success after binutils/gcc/linux/ [...] discards 617df6f8429 409: onsuccess: #2145: 7: Success after binutils/gcc/linux/ [...] discards b8e245ed7f6 408: onsuccess: #2144: 7: Success after binutils/gcc/gdb/qe [...] discards 833122acdbd 407: onsuccess: #2143: 7: Success after binutils/gcc/linux/ [...] discards e3e985d9ee9 406: onsuccess: #2142: 7: Success after binutils/gcc/gdb: 1 [...] discards 20d1b86e2a6 405: onsuccess: #2141: 7: Success after binutils/gcc/linux/ [...] discards 2290fd45d3d 404: onsuccess: #2139: 7: Success after basepoints/gcc-13-5 [...] discards e02fd6a4584 403: onsuccess: #2138: 7: Success after binutils/gcc/gdb: 4 [...] discards bf77d0465b2 402: onsuccess: #2137: 7: Success after binutils/gcc/gdb: 2 [...] discards c4d935fafc1 401: onsuccess: #2136: 7: Success after binutils/gcc/glibc/ [...] discards 14c160f1f5e 400: onsuccess: #2135: 7: Success after binutils/gcc/linux/ [...] discards 6affb0aa675 399: onsuccess: #2134: 7: Success after binutils/gcc/linux/ [...] discards 568fe35f2e9 398: onsuccess: #2133: 7: Success after binutils/gcc/glibc/ [...] discards 0c8ad6867a8 397: onsuccess: #2132: 7: Success after gcc: 2 commits discards c06d50ae61a 396: onsuccess: #2131: 7: Success after binutils/gcc/linux/ [...] discards 0bd92a034a2 395: onsuccess: #2130: 7: Success after binutils/gcc/gdb/qe [...] discards 7e82aea6ecf 394: onsuccess: #2129: 7: Success after binutils/gcc/linux/ [...] discards e4046fd8688 393: onsuccess: #2128: 7: Success after gcc/qemu: 42 commits discards 158e03a2e95 392: onsuccess: #2127: 7: Success after glibc-2.37.9000-17- [...] discards 8445fc6f160 391: onsuccess: #2126: 7: Success after binutils/gcc/linux/ [...] discards 5c6fcdff18d 390: onsuccess: #2125: 7: Success after binutils/gcc/linux/ [...] new 8c0dbbd74bb 390: onsuccess: #2125: 7: Success after binutils/gcc/linux/ [...] new 6679be2a712 391: onsuccess: #2126: 7: Success after binutils/gcc/linux/ [...] new 77ace4b7cde 392: onsuccess: #2127: 7: Success after glibc-2.37.9000-17- [...] new f4034cda978 393: onsuccess: #2128: 7: Success after gcc/qemu: 42 commits new 756dd8b65e4 394: onsuccess: #2129: 7: Success after binutils/gcc/linux/ [...] new 81deb6682c6 395: onsuccess: #2130: 7: Success after binutils/gcc/gdb/qe [...] new 3263aa9cef8 396: onsuccess: #2131: 7: Success after binutils/gcc/linux/ [...] new d1bc2416d48 397: onsuccess: #2132: 7: Success after gcc: 2 commits new e5c30deb7ce 398: onsuccess: #2133: 7: Success after binutils/gcc/glibc/ [...] new 3f544f712f7 399: onsuccess: #2134: 7: Success after binutils/gcc/linux/ [...] new 82ac3f0ef10 400: onsuccess: #2135: 7: Success after binutils/gcc/linux/ [...] new f0fb0721bc4 401: onsuccess: #2136: 7: Success after binutils/gcc/glibc/ [...] new bfff7bb4d2a 402: onsuccess: #2137: 7: Success after binutils/gcc/gdb: 2 [...] new fa9eb0ee608 403: onsuccess: #2138: 7: Success after binutils/gcc/gdb: 4 [...] new 9d3a1ff2a2b 404: onsuccess: #2139: 7: Success after basepoints/gcc-13-5 [...] new 46452bb04e0 405: onsuccess: #2141: 7: Success after binutils/gcc/linux/ [...] new 451a2d4d10a 406: onsuccess: #2142: 7: Success after binutils/gcc/gdb: 1 [...] new 424931d7209 407: onsuccess: #2143: 7: Success after binutils/gcc/linux/ [...] new 6efc99348ed 408: onsuccess: #2144: 7: Success after binutils/gcc/gdb/qe [...] new 86483087064 409: onsuccess: #2145: 7: Success after binutils/gcc/linux/ [...] new a0a24d68593 410: onsuccess: #2146: 7: Success after binutils/gcc/linux/ [...] new 6f91bab822f 411: onsuccess: #2147: 7: Success after binutils/gcc/gdb: 9 [...] new 313a6dcd7e3 412: onsuccess: #2148: 7: Success after binutils/gcc/gdb: 6 [...] new 7cfa40960b1 413: onsuccess: #2149: 7: Success after binutils/gcc/linux/ [...] new 63132b77912 414: onsuccess: #2150: 7: Success after binutils/gcc/linux/ [...] new 4339836cca2 415: onsuccess: #2151: 7: Success after binutils/gcc/gdb: 9 [...] new 0cb7fbce20c 416: onsuccess: #2152: 7: Success after gcc: 50 commits new 38dc8f00e0a 417: onsuccess: #2153: 7: Success after linux/glibc: 27 commits new 5da4963c1e2 418: onsuccess: #2154: 7: Success after binutils/gcc/linux/ [...] new dc9fdd60b44 419: onsuccess: #2155: 7: Success after binutils/gcc/gdb: 4 [...] new 08c3c319cbc 420: onsuccess: #2156: 7: Success after binutils/gcc/gdb: 2 [...] new 44cbdcf63c6 421: onsuccess: #2157: 7: Success after binutils/gcc/linux/ [...] new 205a3be2d7d 422: onsuccess: #2158: 7: Success after binutils/gcc/linux/ [...] new b23a20d904c 423: onsuccess: #2159: 7: Success after binutils/gcc/gdb: 5 [...] new b809d3ce719 424: onsuccess: #2160: 7: Success after binutils/gcc/glibc/ [...] new 1d11e8905a3 425: onsuccess: #2161: 7: Success after binutils/gcc/linux/ [...] new 9c73a5ad7e7 426: onsuccess: #2162: 7: Success after binutils/gcc/gdb: 1 [...] new 0965d0f7e38 427: onsuccess: #2163: 7: Success after binutils/gdb: 4 commits new ac802af3453 428: onsuccess: #2165: 7: Success after binutils/gcc/glibc/ [...] new dc2c1f71180 429: onsuccess: #2166: 7: Success after binutils/gcc/linux/ [...] new 068b30d11f8 430: onsuccess: #2167: 7: Success after binutils/gcc/gdb/qe [...] new 0aab4f89a6c 431: onsuccess: #2168: 7: Success after binutils/gcc/gdb/qe [...] new 9113a0a05a4 432: onsuccess: #2169: 7: Success after binutils/gcc/linux/ [...] new 964ac1a2ba8 433: onsuccess: #2170: 7: Success after binutils/gcc/linux/ [...] new a6f4bb5f4d3 434: onsuccess: #2171: 7: Success after gcc/glibc: 5 commits new 1c60ca12141 435: onsuccess: #2172: 7: Success after binutils/gcc/glibc/ [...] new c2ecc4ae264 436: onsuccess: #2173: 7: Success after binutils/gcc/linux/ [...] new b661001ec14 437: onsuccess: #2174: 7: Success after gcc/linux: 9 commits new 4a3be8501b7 438: onsuccess: #2175: 7: Success after gcc: 7 commits new d43d1492808 439: onsuccess: #2176: 7: Success after linux: 11 commits new 87d5117c9b5 440: onsuccess: #2177: 7: Success after binutils/gcc/gdb: 6 [...] new 7668530020a 441: onsuccess: #2178: 7: Success after binutils/linux/gdb: [...] new e6274853627 442: onsuccess: #2179: 7: Success after binutils/gcc/linux/ [...] new b06ea241256 443: onsuccess: #2180: 7: Success after binutils/gdb: 2 commits new 056890d5d66 444: onsuccess: #2181: 7: Success after binutils/gcc/glibc/ [...] new 74de5bfdd6d 445: onsuccess: #2182: 7: Success after binutils/gcc/glibc/ [...] new 27d06598940 446: onsuccess: #2183: 7: Success after binutils/gcc/linux/ [...] new 70e95ccc2e7 447: onsuccess: #2184: 7: Success after binutils/gcc/linux/ [...] new 3c704ed60f3 448: onsuccess: #2185: 7: Success after binutils/gcc/gdb/qe [...] new 879a20fb292 449: onsuccess: #2186: 7: Success after binutils/gcc/linux/ [...] new cfce082e6f0 450: onsuccess: #2188: 7: Success after binutils/gcc/linux/ [...] new 745b464396b 451: onsuccess: #2189: 7: Success after binutils/gcc/gdb: 1 [...] new f6102aa5e6a 452: onsuccess: #2190: 7: Success after binutils/gcc/linux/ [...] new 026305086ef 453: onsuccess: #2191: 7: Success after binutils/gcc/linux/ [...] new 967f30e4c79 454: onsuccess: #2192: 7: Success after binutils/linux/glib [...] new 2e4ddb16d9c 455: onsuccess: #2193: 7: Success after binutils/gcc/gdb: 1 [...] new d74fb381151 456: onsuccess: #1: 7: Success after binutils/gcc/linux/gli [...] new 7c9ed5b00a8 457: onsuccess: #2194: 7: Success after binutils/gcc/linux/ [...] new ed3e545f8b8 458: onsuccess: #2: 7: Success after gcc/linux/glibc: 581 commits new 403803a82e6 459: onsuccess: #3: 7: Success after binutils/gcc/glibc/gdb [...] new d602574a4c2 460: onsuccess: #4: 7: Success after binutils/gcc/gdb: 5 commits new 13732c49c11 461: onsuccess: #5: 7: Success after binutils/gcc/linux/gli [...] new 86aa4f86ef9 462: onsuccess: #6: 7: Success after gcc/linux: 385 commits new 3ada1f2e70e 463: onsuccess: #7: 7: Success after binutils/gcc/gdb: 5 commits new 3c75b275f9e 464: onsuccess: #8: 7: Success after binutils/gcc/linux/gli [...] new 1191d7aecbd 465: onsuccess: #9: 7: Success after binutils/gcc/linux/gdb [...] new d2656f7e9d6 466: onsuccess: #10: 7: Success after binutils/gcc/linux/gl [...] new 5ef1b8b71a4 467: onsuccess: #11: 7: Success after binutils/gcc/linux/gl [...] new 4ec2e049183 468: onsuccess: #12: 7: Success after binutils/gcc/linux/gl [...] new 16c99d1e555 469: onsuccess: #13: 7: Success after binutils/gcc/linux/gl [...] new 9b8050a76b5 470: onsuccess: #14: 7: Success after binutils/gcc/linux/gd [...] new 9df88dd72d3 471: onsuccess: #15: 7: Success after binutils/gcc/linux/gd [...] new 3845a2341fc 472: onsuccess: #16: 7: Success after binutils/gcc/linux/gd [...] new 83b843190da 473: onsuccess: #17: 7: Success after binutils/gcc/linux/gl [...] new b133f764889 474: onsuccess: #18: 7: Success after binutils/gcc/linux/gl [...] new 0b090f59a33 475: onsuccess: #19: 7: Success after binutils/gcc/linux/gl [...] new 44fb6439d4e 476: onsuccess: #20: 7: Success after binutils/gcc/linux/gd [...] new b57947ab811 477: onsuccess: #21: 7: Success after binutils/gcc/linux/gl [...] new d9900fea793 478: onsuccess: #22: 7: Success after binutils/gcc/linux/gd [...] new d85cbb9ef0d 479: onsuccess: #23: 7: Success after binutils/gcc/linux/gd [...] new 0136af7f58c 480: onsuccess: #24: 7: Success after binutils/gcc/linux/gl [...] new 4cc63083653 481: onsuccess: #25: 7: Success after binutils/gcc/linux/gl [...] new 1fe3d087c70 482: onsuccess: #26: 7: Success after binutils/gcc/linux/gd [...] new 7fa514898a9 483: onsuccess: #27: 7: Success after binutils/gcc/linux/gd [...] new dc2245dc348 484: onsuccess: #28: 7: Success after binutils/gcc/linux/gd [...] new 05cd3ddc7d5 485: onsuccess: #29: 7: Success after binutils/gcc/linux/gd [...] new 27e4ca0e55f 486: onsuccess: #30: 7: Success after binutils/gcc/linux/gd [...] new bbdfd9d61e0 487: onsuccess: #31: 7: Success after binutils/gcc/linux/gd [...] new a27b1a39d15 488: onsuccess: #32: 7: Success after binutils/gcc/linux/gl [...] new ea27b4334c7 489: onsuccess: #33: 7: Success after binutils/gcc/linux/gd [...] new 90b9fe9a368 490: onsuccess: #34: 7: Success after binutils/gcc/linux/gd [...] new 4c56e5b4054 491: onsuccess: #35: 7: Success after binutils/gcc/linux/gd [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (2274ba0fe6a) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2092 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2568 -> 2544 bytes 04-build_abe-binutils/console.log.xz | Bin 26980 -> 26972 bytes 05-build_abe-stage1/console.log.xz | Bin 88692 -> 90132 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8424 -> 9280 bytes 08-build_abe-glibc/console.log.xz | Bin 233724 -> 233248 bytes 09-build_abe-stage2/console.log.xz | Bin 225420 -> 226448 bytes 10-build_abe-gdb/console.log.xz | Bin 34272 -> 34608 bytes 11-build_abe-qemu/console.log.xz | Bin 31924 -> 32088 bytes 12-check_regression/console.log.xz | Bin 4348 -> 4312 bytes 12-check_regression/jira-body.txt | 1 - 12-check_regression/mail-body.txt | 2 +- 13-update_baseline/console.log | 66 +++++++++++++++++------------------ 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 | 1 - mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 ++++++++++----------- 23 files changed, 61 insertions(+), 63 deletions(-) delete mode 100644 12-check_regression/jira-body.txt delete mode 100644 mail/jira-body.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch releases/gcc-12 updated (0c87356095b -> 495bf0455b0)

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 0c87356095b Daily bump. new 495bf0455b0 Daily bump. 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/DATESTAMP | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch releases/gcc-11 updated (2055702e8d4 -> f08980e8b7c)

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-11 in repository gcc. from 2055702e8d4 Fortran: reject MODULE PROCEDURE outside generic module int [...] new f08980e8b7c Daily bump. 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/DATESTAMP | 2 +- gcc/fortran/ChangeLog | 27 +++++++++++++++++++++++++++ gcc/testsuite/ChangeLog | 24 ++++++++++++++++++++++++ 3 files changed, 52 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch releases/gcc-10 updated (b9f6e7e234b -> 78a626186aa)

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-10 in repository gcc. from b9f6e7e234b Fortran: simplification of NEAREST for large argument [PR109186] new 78a626186aa Daily bump. 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/DATESTAMP | 2 +- gcc/fortran/ChangeLog | 18 ++++++++++++++++++ gcc/testsuite/ChangeLog | 16 ++++++++++++++++ 3 files changed, 35 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (fdb06fe6825 -> 13ec81eb4c3)

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 fdb06fe6825 docs, analyzer: improvements to "Debugging the Analyzer" new 13ec81eb4c3 Daily bump. 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/ChangeLog | 49 +++++++++++++++++++++++++++++++ gcc/DATESTAMP | 2 +- gcc/cp/ChangeLog | 11 +++++++ gcc/fortran/ChangeLog | 19 ++++++++++++ gcc/go/ChangeLog | 10 +++++++ gcc/testsuite/ChangeLog | 77 +++++++++++++++++++++++++++++++++++++++++++++++++ libatomic/ChangeLog | 6 ++++ libgomp/ChangeLog | 10 +++++++ 8 files changed, 183 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_ubsan updated (52a6db4a86c -> db736e1bfdf)

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_ubsan in repository toolchain/ci/base-artifacts. discards 52a6db4a86c 221: onsuccess: #32: 2: Success after binutils/gcc: 33 commits discards e3d927e5a4d 220: onsuccess: #31: 2: Success after binutils/gcc: 38 commits discards a35c47966a3 219: onsuccess: #30: 2: Success after binutils/gcc: 194 commits discards 05250f6113b 218: onsuccess: #24: 2: Success after binutils/gcc: 39 commits discards d5f2b068b29 217: onsuccess: #23: 2: Success after binutils/gcc: 48 commits discards f90baaec9ac 216: onsuccess: #22: 2: Success after binutils/gcc: 51 commits discards 4366a711d78 215: onsuccess: #21: 2: Success after binutils/gcc: 15 commits discards a236d2e3ff4 214: onsuccess: #20: 2: Success after binutils/gcc: 14 commits discards 40f6ca34ae4 213: onsuccess: #19: 2: Success after binutils/gcc: 56 commits discards f90fc7e0731 212: onsuccess: #18: 2: Success after binutils/gcc: 35 commits discards 4a0ae0e8009 211: onsuccess: #17: 2: Success after binutils/gcc: 49 commits discards 460e91d8386 210: onsuccess: #16: 0: Success after binutils: 23 commits discards 2d25eeda4e4 209: force: #15: 0: Failure after gdb-13-branchpoint-1318-g [...] discards 627ebfef6c4 208: force: #14: 2: Success after binutils: 17 commits discards c0fe4881c4b 207: onsuccess: #12: 2: Success after binutils/gcc: 27 commits discards 188d5f92a8f 206: onsuccess: #11: 2: Success after binutils/gcc: 18 commits discards 29a2daaa1b5 205: onsuccess: #10: 2: Success after binutils/gcc: 17 commits discards 9a454197d49 204: onsuccess: #9: 2: Success after binutils/gcc: 53 commits discards 796400a350d 203: onsuccess: #8: 2: Success after binutils/gcc: 35 commits discards 87a8046ed8b 202: onsuccess: #7: 2: Success after binutils/gcc: 29 commits discards 1ce5d42b218 201: onsuccess: #6: 2: Success after binutils/gcc: 46 commits discards 31381e8fbad 200: onsuccess: #5: 2: Success after binutils/gcc: 41 commits discards d46b44d002d 199: onsuccess: #4: 2: Success after binutils/gcc: 5 commits discards ae1f69a3caf 198: onsuccess: #3: 2: Success after binutils/gcc: 10 commits discards aebb65c1593 197: onsuccess: #2: 2: Success after binutils/gcc: 19 commits discards f9e76bf4daf 196: onsuccess: #1: 2: Success after binutils/gcc: 23 commits discards 2af103e1a4c 195: onsuccess: #623: 2: Success after binutils/gcc: 44 commits discards eb3aa4a3840 194: onsuccess: #622: 2: Success after binutils/gcc: 36 commits discards 8658fca29b9 193: onsuccess: #621: 2: Success after binutils/gcc: 146 commits discards ffd3569db78 192: onsuccess: #620: 2: Success after binutils/gcc: 236 commits discards 5190dfe366f 191: onsuccess: #614: 2: Success after binutils/gcc: 31 commits discards 197974d08fb 190: onsuccess: #613: 2: Success after binutils/gcc: 94 commits discards 7115916aa08 189: onsuccess: #612: 2: Success after binutils/gcc: 113 commits discards 3348921d334 188: onsuccess: #611: 2: Success after binutils/gcc: 57 commits discards b375826a446 187: onsuccess: #610: 2: Success after binutils/gcc: 81 commits discards ca782604d0f 186: onsuccess: #609: 2: Success after binutils/gcc: 10 commits discards ce494ffc79b 185: onsuccess: #608: 2: Success after binutils/gcc: 41 commits discards 68a78e89546 184: onsuccess: #607: 2: Success after binutils/gcc: 15 commits discards 43bed4b447f 183: onsuccess: #606: 2: Success after binutils/gcc: 31 commits discards d9009b94b25 182: onsuccess: #605: 2: Success after binutils/gcc: 6 commits discards 3ec4ec0e1a8 181: onsuccess: #604: 2: Success after binutils/gcc: 30 commits discards dc4296e9715 180: onsuccess: #603: 2: Success after binutils/gcc: 59 commits discards 3ef864338f1 179: onsuccess: #602: 2: Success after binutils/gcc: 36 commits discards 0bf969622fe 178: onsuccess: #601: 2: Success after binutils/gcc: 108 commits discards c82674a0f5c 177: onsuccess: #600: 2: Success after binutils/gcc: 54 commits discards 97aab78b0a1 176: onsuccess: #599: 2: Success after binutils/gcc: 13 commits discards 20f289a739f 175: onsuccess: #598: 2: Success after binutils/gcc: 47 commits discards 6b5ef8ca9e3 174: onsuccess: #597: 2: Success after binutils/gcc: 115 commits discards d4d5b85b637 173: onsuccess: #596: 2: Success after binutils/gcc: 50 commits discards a02cd3c5a2b 172: onsuccess: #595: 2: Success after binutils/gcc: 44 commits discards a8f76dd40d5 171: onsuccess: #594: 2: Success after binutils/gcc: 48 commits discards 50cac0a535f 170: onsuccess: #593: 2: Success after binutils/gcc: 16 commits discards 3d9d13fa112 169: onsuccess: #592: 2: Success after binutils/gcc: 39 commits discards 2ac42ae68d8 168: onsuccess: #591: 2: Success after binutils/gcc: 44 commits discards f15b880ff4c 167: onsuccess: #590: 2: Success after binutils/gcc: 31 commits discards 6a8ea6f035a 166: onsuccess: #589: 2: Success after binutils/gcc: 74 commits discards 7367a3ef3fa 165: onsuccess: #588: 2: Success after binutils/gcc: 34 commits discards 67ff8a764f4 164: onsuccess: #587: 2: Success after binutils/gcc: 139 commits discards 4a7a5ac1086 163: onsuccess: #586: 2: Success after binutils/gcc: 34 commits discards ddd271186cb 162: onsuccess: #585: 2: Success after binutils/gcc: 139 commits discards 5d3cca0d332 161: onsuccess: #583: 2: Success after binutils/gcc: 6 commits discards 1f6aec996eb 160: onsuccess: #582: 2: Success after binutils/gcc: 10 commits discards 14c3990d281 159: onsuccess: #581: 2: Success after binutils/gcc: 33 commits discards 44adfc87ab9 158: onsuccess: #580: 2: Success after binutils/gcc: 51 commits discards edfe361681e 157: onsuccess: #579: 2: Success after binutils/gcc: 43 commits discards 7038b1f14b5 156: onsuccess: #578: 2: Success after binutils/gcc: 46 commits discards 77096e41670 155: onsuccess: #577: 2: Success after binutils/gcc: 24 commits discards c52f712949f 154: onsuccess: #576: 2: Success after binutils/gcc: 14 commits discards 73295afdd10 153: onsuccess: #575: 2: Success after binutils/gcc: 18 commits discards 34286a02b01 152: onsuccess: #574: 2: Success after binutils/gcc: 25 commits discards 763632cd842 151: onsuccess: #573: 2: Success after binutils/gcc: 7 commits discards a8da22981be 150: onsuccess: #572: 2: Success after binutils/gcc: 22 commits discards ae3256ab8ad 149: onsuccess: #571: 2: Success after binutils/gcc: 14 commits discards d1501191af4 148: onsuccess: #570: 2: Success after binutils/gcc: 6 commits discards 12697883fae 147: onsuccess: #569: 2: Success after binutils/gcc: 28 commits discards 6f526e258e2 146: onsuccess: #568: 2: Success after binutils/gcc: 10 commits discards 4a40b6d934a 145: onsuccess: #567: 2: Success after binutils/gcc: 93 commits discards aaced9aa438 144: onsuccess: #566: 2: Success after binutils/gcc: 38 commits discards a0e2a1b2261 143: onsuccess: #565: 2: Success after binutils/gcc: 65 commits discards c92412c93c9 142: onsuccess: #564: 2: Success after binutils/gcc: 20 commits discards f4154ef34be 141: onsuccess: #563: 2: Success after binutils/gcc: 46 commits discards 3f7a8135fb2 140: onsuccess: #562: 2: Success after binutils/gcc: 10 commits discards 8515fffe624 139: onsuccess: #561: 2: Success after binutils/gcc: 26 commits discards 20abe63c6f8 138: onsuccess: #560: 2: Success after binutils/gcc: 42 commits discards 8bdab87e67c 137: onsuccess: #559: 1: Success after binutils/gcc: 24 commits discards 318bfe5d75e 136: onsuccess: #558: 1: Success after binutils/gcc: 51 commits discards c76d2bf9eda 135: onsuccess: #557: 1: Success after binutils/gcc: 69 commits discards 2a19d16c6f7 134: onsuccess: #556: 1: Success after binutils/gcc: 44 commits discards b4e9f619101 133: onsuccess: #555: 1: Success after binutils/gcc: 27 commits discards daf61e56e74 132: onsuccess: #554: 1: Success after gcc: 36 commits discards 13c93f6a6df 131: force: #553: 1: Failure after gcc: 10 commits discards 3e8c0694eb4 130: onsuccess: #549: 2: Success after binutils: 14 commits discards b85a5801831 129: onsuccess: #546: 2: Success after binutils/gcc: 31 commits discards 497f90185f8 128: onsuccess: #545: 2: Success after binutils/gcc: 42 commits discards 5dd341bb7e4 127: onsuccess: #544: 2: Success after binutils/gcc: 29 commits discards 84f438c61f2 126: onsuccess: #543: 2: Success after binutils/gcc: 10 commits discards 4030a517ddd 125: onsuccess: #542: 2: Success after binutils/gcc: 14 commits discards b33e3d2c56e 124: onsuccess: #541: 2: Success after binutils/gcc: 36 commits discards c60d02b64ed 123: onsuccess: #540: 2: Success after binutils/gcc: 53 commits discards 26547a65acc 122: onsuccess: #539: 2: Success after binutils/gcc: 37 commits discards 587060e9057 121: onsuccess: #538: 2: Success after binutils/gcc: 55 commits new 839dc1085ef 121: onsuccess: #538: 2: Success after binutils/gcc: 55 commits new 96766ec0c33 122: onsuccess: #539: 2: Success after binutils/gcc: 37 commits new 5b86ed3d2ca 123: onsuccess: #540: 2: Success after binutils/gcc: 53 commits new f1264b2a482 124: onsuccess: #541: 2: Success after binutils/gcc: 36 commits new c715bade79f 125: onsuccess: #542: 2: Success after binutils/gcc: 14 commits new d5c578c6895 126: onsuccess: #543: 2: Success after binutils/gcc: 10 commits new 609104a1b36 127: onsuccess: #544: 2: Success after binutils/gcc: 29 commits new c94a6170207 128: onsuccess: #545: 2: Success after binutils/gcc: 42 commits new 25468bcff4a 129: onsuccess: #546: 2: Success after binutils/gcc: 31 commits new 1da431f9321 130: onsuccess: #549: 2: Success after binutils: 14 commits new 3038effad3d 131: force: #553: 1: Failure after gcc: 10 commits new b23a651e66e 132: onsuccess: #554: 1: Success after gcc: 36 commits new f03a55f760f 133: onsuccess: #555: 1: Success after binutils/gcc: 27 commits new 24f9be1f962 134: onsuccess: #556: 1: Success after binutils/gcc: 44 commits new 53b117bbb1c 135: onsuccess: #557: 1: Success after binutils/gcc: 69 commits new 7bde2558b98 136: onsuccess: #558: 1: Success after binutils/gcc: 51 commits new e661a90461b 137: onsuccess: #559: 1: Success after binutils/gcc: 24 commits new 2d1cd90e68e 138: onsuccess: #560: 2: Success after binutils/gcc: 42 commits new 209b734dee4 139: onsuccess: #561: 2: Success after binutils/gcc: 26 commits new be6b5cb01a4 140: onsuccess: #562: 2: Success after binutils/gcc: 10 commits new d9e40b38a36 141: onsuccess: #563: 2: Success after binutils/gcc: 46 commits new f8e3c4ef302 142: onsuccess: #564: 2: Success after binutils/gcc: 20 commits new 139f7d4592f 143: onsuccess: #565: 2: Success after binutils/gcc: 65 commits new 8b45b17b974 144: onsuccess: #566: 2: Success after binutils/gcc: 38 commits new f488f30dc2c 145: onsuccess: #567: 2: Success after binutils/gcc: 93 commits new a580c13cc0c 146: onsuccess: #568: 2: Success after binutils/gcc: 10 commits new 05fa6761d94 147: onsuccess: #569: 2: Success after binutils/gcc: 28 commits new 55109ae905c 148: onsuccess: #570: 2: Success after binutils/gcc: 6 commits new cd795747909 149: onsuccess: #571: 2: Success after binutils/gcc: 14 commits new ddfcb5c09b6 150: onsuccess: #572: 2: Success after binutils/gcc: 22 commits new a7ef6501efe 151: onsuccess: #573: 2: Success after binutils/gcc: 7 commits new 0cbf45135ae 152: onsuccess: #574: 2: Success after binutils/gcc: 25 commits new e021d1319fa 153: onsuccess: #575: 2: Success after binutils/gcc: 18 commits new 8210d5dfdca 154: onsuccess: #576: 2: Success after binutils/gcc: 14 commits new 3e5ea3f356a 155: onsuccess: #577: 2: Success after binutils/gcc: 24 commits new 0933cd38fac 156: onsuccess: #578: 2: Success after binutils/gcc: 46 commits new 9a72dd717cf 157: onsuccess: #579: 2: Success after binutils/gcc: 43 commits new 333a6587ad8 158: onsuccess: #580: 2: Success after binutils/gcc: 51 commits new 2398adbef8a 159: onsuccess: #581: 2: Success after binutils/gcc: 33 commits new 4bd543c15b6 160: onsuccess: #582: 2: Success after binutils/gcc: 10 commits new 4f1732a0ce2 161: onsuccess: #583: 2: Success after binutils/gcc: 6 commits new 8676ed4de6c 162: onsuccess: #585: 2: Success after binutils/gcc: 139 commits new 39bef564aca 163: onsuccess: #586: 2: Success after binutils/gcc: 34 commits new 2f3878f86bf 164: onsuccess: #587: 2: Success after binutils/gcc: 139 commits new 0897cf683fa 165: onsuccess: #588: 2: Success after binutils/gcc: 34 commits new 83bab4d4228 166: onsuccess: #589: 2: Success after binutils/gcc: 74 commits new 69cedfaf706 167: onsuccess: #590: 2: Success after binutils/gcc: 31 commits new 189c387fd30 168: onsuccess: #591: 2: Success after binutils/gcc: 44 commits new 42bc719df37 169: onsuccess: #592: 2: Success after binutils/gcc: 39 commits new d3eadada59c 170: onsuccess: #593: 2: Success after binutils/gcc: 16 commits new 876c1f045b5 171: onsuccess: #594: 2: Success after binutils/gcc: 48 commits new 6ceb6b51414 172: onsuccess: #595: 2: Success after binutils/gcc: 44 commits new 2e42c495377 173: onsuccess: #596: 2: Success after binutils/gcc: 50 commits new d3d1d5a0cf1 174: onsuccess: #597: 2: Success after binutils/gcc: 115 commits new c85c2ec2e22 175: onsuccess: #598: 2: Success after binutils/gcc: 47 commits new 503824199c1 176: onsuccess: #599: 2: Success after binutils/gcc: 13 commits new fdbbf513b65 177: onsuccess: #600: 2: Success after binutils/gcc: 54 commits new 8cc2ede7561 178: onsuccess: #601: 2: Success after binutils/gcc: 108 commits new dab6d809a7a 179: onsuccess: #602: 2: Success after binutils/gcc: 36 commits new 0c7dcd8906e 180: onsuccess: #603: 2: Success after binutils/gcc: 59 commits new 797e12bafa3 181: onsuccess: #604: 2: Success after binutils/gcc: 30 commits new 10fb825482e 182: onsuccess: #605: 2: Success after binutils/gcc: 6 commits new 83f2fdd0ac1 183: onsuccess: #606: 2: Success after binutils/gcc: 31 commits new 12f92af1acf 184: onsuccess: #607: 2: Success after binutils/gcc: 15 commits new 4db1e595f69 185: onsuccess: #608: 2: Success after binutils/gcc: 41 commits new 88c476b1269 186: onsuccess: #609: 2: Success after binutils/gcc: 10 commits new 23281e76366 187: onsuccess: #610: 2: Success after binutils/gcc: 81 commits new 7bfa00a2c2f 188: onsuccess: #611: 2: Success after binutils/gcc: 57 commits new ec86f931a9b 189: onsuccess: #612: 2: Success after binutils/gcc: 113 commits new ad4d6d7efcd 190: onsuccess: #613: 2: Success after binutils/gcc: 94 commits new 8984a259968 191: onsuccess: #614: 2: Success after binutils/gcc: 31 commits new 859b5c74dfe 192: onsuccess: #620: 2: Success after binutils/gcc: 236 commits new 431847392b1 193: onsuccess: #621: 2: Success after binutils/gcc: 146 commits new ede0d3897b2 194: onsuccess: #622: 2: Success after binutils/gcc: 36 commits new dc9454f74b7 195: onsuccess: #623: 2: Success after binutils/gcc: 44 commits new 4fd1fab02ac 196: onsuccess: #1: 2: Success after binutils/gcc: 23 commits new 0fd63ff3e9c 197: onsuccess: #2: 2: Success after binutils/gcc: 19 commits new e209ffa7304 198: onsuccess: #3: 2: Success after binutils/gcc: 10 commits new 574d64c78c3 199: onsuccess: #4: 2: Success after binutils/gcc: 5 commits new 768fbb95b0f 200: onsuccess: #5: 2: Success after binutils/gcc: 41 commits new 2b646b3c3f4 201: onsuccess: #6: 2: Success after binutils/gcc: 46 commits new 24ec5218640 202: onsuccess: #7: 2: Success after binutils/gcc: 29 commits new 946c71e25dd 203: onsuccess: #8: 2: Success after binutils/gcc: 35 commits new 8dc1c57ec46 204: onsuccess: #9: 2: Success after binutils/gcc: 53 commits new ffda7235969 205: onsuccess: #10: 2: Success after binutils/gcc: 17 commits new 36ca04cf1c2 206: onsuccess: #11: 2: Success after binutils/gcc: 18 commits new e2467359937 207: onsuccess: #12: 2: Success after binutils/gcc: 27 commits new 4d581c3479d 208: force: #14: 2: Success after binutils: 17 commits new 33785ec508a 209: force: #15: 0: Failure after gdb-13-branchpoint-1318-g [...] new fbe960b5427 210: onsuccess: #16: 0: Success after binutils: 23 commits new 5aded3b0305 211: onsuccess: #17: 2: Success after binutils/gcc: 49 commits new da8bda72787 212: onsuccess: #18: 2: Success after binutils/gcc: 35 commits new dc0d7528c87 213: onsuccess: #19: 2: Success after binutils/gcc: 56 commits new 7d6f807dda7 214: onsuccess: #20: 2: Success after binutils/gcc: 14 commits new 3bffda044b4 215: onsuccess: #21: 2: Success after binutils/gcc: 15 commits new 790347754e9 216: onsuccess: #22: 2: Success after binutils/gcc: 51 commits new 0c696a0bbe4 217: onsuccess: #23: 2: Success after binutils/gcc: 48 commits new 8046bacb930 218: onsuccess: #24: 2: Success after binutils/gcc: 39 commits new 423da9d805c 219: onsuccess: #30: 2: Success after binutils/gcc: 194 commits new d08417117f4 220: onsuccess: #31: 2: Success after binutils/gcc: 38 commits new 0830d6ca794 221: onsuccess: #32: 2: Success after binutils/gcc: 33 commits new db736e1bfdf 222: onsuccess: #33: 2: Success after binutils/gcc: 33 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 (52a6db4a86c) \ 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 1916 -> 2236 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2524 bytes 04-build_abe-binutils/console.log.xz | Bin 48748 -> 49192 bytes 05-build_abe-bootstrap_ubsan/console.log.xz | Bin 537316 -> 537164 bytes 06-check_regression/console.log.xz | Bin 3116 -> 3040 bytes 06-check_regression/jira-body.txt | 1 - 06-check_regression/mail-body.txt | 2 +- 07-update_baseline/console.log | 44 ++++++++++++++-------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 1 - mail/mail-body.txt | 2 +- manifest.sh | 20 ++++++------- 14 files changed, 37 insertions(+), 39 deletions(-) delete mode 100644 06-check_regression/jira-body.txt delete mode 100644 mail/jira-body.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[binutils-gdb] branch master updated (4bfcb286dd1 -> f06b840b9a0)

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 4bfcb286dd1 Preserve name of range types new f06b840b9a0 Automatic date update in version.in 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: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[binutils-gdb] branch gdb-13-branch updated (b3eff3e1557 -> 913105ea213)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch gdb-13-branch in repository binutils-gdb. from b3eff3e1557 aarch64: Check for valid inferior thread/regcache before re [...] new 913105ea213 Automatic date update in version.in 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: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits March 2023