Tcwg-commits February 2023

tcwg-commits@lists.linaro.org

5 participants
3393 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled updated (195d06c137 -> 3758804182)

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-aarch64-bootstrap_profiled in repository toolchain/ci/base-artifacts. discards 195d06c137 167: onsuccess: #579: 2: Success after binutils/gcc: 43 commits discards fd7f2b1af3 166: onsuccess: #578: 2: Success after binutils/gcc: 16 commits discards c7300cd4e7 165: onsuccess: #577: 2: Success after binutils/gcc: 31 commits discards 150d02130e 164: onsuccess: #576: 2: Success after binutils/gcc: 5 commits discards f9fdae4e54 163: onsuccess: #575: 2: Success after binutils/gcc: 30 commits discards 5be18a0e6b 162: onsuccess: #574: 2: Success after binutils/gcc: 55 commits discards eda11904b1 161: onsuccess: #573: 2: Success after binutils/gcc: 41 commits discards dbd316f118 160: onsuccess: #572: 2: Success after binutils/gcc: 107 commits discards 3b102b3b5b 159: onsuccess: #571: 2: Success after binutils/gcc: 55 commits discards 633000ddbc 158: onsuccess: #570: 2: Success after binutils/gcc: 13 commits discards c593c42e14 157: onsuccess: #569: 2: Success after binutils/gcc: 43 commits discards ec7cb7093b 156: onsuccess: #568: 2: Success after binutils/gcc: 117 commits discards d33e72ade2 155: onsuccess: #567: 2: Success after binutils/gcc: 27 commits discards 3c23a4dad7 154: onsuccess: #566: 2: Success after binutils/gcc: 65 commits discards b0acd29cfc 153: onsuccess: #565: 2: Success after binutils/gcc: 52 commits discards 129fa328be 152: onsuccess: #564: 2: Success after binutils/gcc: 11 commits discards d44e2824b4 151: onsuccess: #563: 2: Success after binutils/gcc: 5 commits discards fa2f0e7c6d 150: onsuccess: #562: 2: Success after binutils/gcc: 39 commits discards 165ade3e96 149: onsuccess: #561: 2: Success after binutils/gcc: 41 commits discards 0fe1730522 148: onsuccess: #560: 2: Success after binutils/gcc: 32 commits discards da852cc4c7 147: onsuccess: #559: 2: Success after binutils/gcc: 76 commits discards f5fa83d240 146: onsuccess: #558: 2: Success after binutils/gcc: 34 commits discards 78d823213c 145: onsuccess: #557: 2: Success after binutils/gcc: 137 commits discards dd4002ebf1 144: onsuccess: #556: 2: Success after binutils/gcc: 36 commits discards 0e6955bf8c 143: onsuccess: #555: 2: Success after binutils/gcc: 139 commits discards ae2952bd8a 142: onsuccess: #553: 2: Success after binutils/gcc: 6 commits discards d4646c29fc 141: onsuccess: #552: 2: Success after binutils/gcc: 9 commits discards d6f2a7316e 140: onsuccess: #551: 2: Success after binutils/gcc: 68 commits discards ba71210851 139: onsuccess: #549: 2: Success after binutils/gcc: 104 commits discards 1d6b39accd 138: onsuccess: #548: 1: Success after gcc: 3 commits discards 7f1de6a855 137: force: #547: 1: Failure after basepoints/gcc-13-4953-g3 [...] discards 39c77930bb 136: force: #546: 2: Success after gcc: 8 commits discards ec7b040a3a 135: onsuccess: #543: 2: Success after binutils: 14 commits discards 747f78ac35 134: onsuccess: #541: 2: Success after binutils/gcc: 13 commits discards b80480da62 133: onsuccess: #540: 2: Success after binutils/gcc: 16 commits discards 2b4fc8e66e 132: onsuccess: #539: 2: Success after binutils/gcc: 28 commits discards 31986ad527 131: onsuccess: #538: 2: Success after binutils/gcc: 5 commits discards 66a819c65d 130: onsuccess: #537: 2: Success after binutils/gcc: 15 commits discards ef9ada0fff 129: onsuccess: #536: 2: Success after binutils/gcc: 23 commits discards bc840d7dbd 128: onsuccess: #535: 2: Success after binutils/gcc: 6 commits discards 495ee47478 127: onsuccess: #534: 2: Success after binutils/gcc: 27 commits discards 4b455230f0 126: onsuccess: #533: 2: Success after binutils/gcc: 9 commits discards 9140235d3d 125: onsuccess: #532: 2: Success after binutils/gcc: 95 commits discards 5f177c9563 124: onsuccess: #531: 2: Success after binutils/gcc: 37 commits discards 51ba4dbb73 123: onsuccess: #530: 2: Success after binutils/gcc: 65 commits discards e94a432874 122: onsuccess: #529: 2: Success after binutils/gcc: 18 commits discards 89a4e939a5 121: onsuccess: #528: 2: Success after binutils/gcc: 49 commits discards ec5fd49f9b 120: onsuccess: #527: 2: Success after binutils/gcc: 9 commits discards 9f44c85bc1 119: onsuccess: #526: 2: Success after binutils/gcc: 26 commits discards 698235a3a8 118: onsuccess: #525: 2: Success after binutils/gcc: 42 commits discards 18f532dc4d 117: onsuccess: #524: 2: Success after binutils/gcc: 25 commits discards d684e57e4e 116: onsuccess: #523: 2: Success after binutils/gcc: 48 commits discards 32d7b72592 115: onsuccess: #522: 2: Success after binutils/gcc: 71 commits discards 763c65aa00 114: onsuccess: #521: 2: Success after binutils/gcc: 42 commits discards be79b98f03 113: onsuccess: #520: 2: Success after binutils/gcc: 11 commits discards e33b16f843 112: onsuccess: #519: 2: Success after binutils/gcc: 77 commits discards c9cd8852c7 111: onsuccess: #516: 2: Success after binutils/gcc: 32 commits discards 8fb6e44c7d 110: onsuccess: #515: 2: Success after binutils/gcc: 71 commits discards 55e275a4f1 109: onsuccess: #513: 2: Success after binutils/gcc: 9 commits discards 3ce1b002a7 108: onsuccess: #512: 2: Success after binutils/gcc: 15 commits discards 251b6db3a9 107: onsuccess: #511: 2: Success after binutils/gcc: 30 commits discards 795702da77 106: onsuccess: #510: 2: Success after binutils/gcc: 55 commits discards efe22e047c 105: onsuccess: #509: 2: Success after binutils/gcc: 39 commits discards 58a977c147 104: onsuccess: #508: 2: Success after binutils/gcc: 54 commits discards 6ec853f750 103: onsuccess: #507: 2: Success after binutils/gcc: 83 commits discards e5834c6987 102: onsuccess: #506: 2: Success after binutils/gcc: 32 commits discards 2d9cf29c9f 101: onsuccess: #501: 2: Success after binutils/gcc: 49 commits discards de8069000c 100: onsuccess: #500: 2: Success after binutils/gcc: 50 commits discards 6fe3f0cdeb 99: onsuccess: #499: 2: Success after binutils/gcc: 36 commits discards 10154b289d 98: onsuccess: #498: 2: Success after binutils/gcc: 42 commits discards 3d03996192 97: onsuccess: #497: 2: Success after binutils/gcc: 9 commits discards 5e51b795f2 96: onsuccess: #496: 2: Success after binutils/gcc: 30 commits discards a9da8293c7 95: onsuccess: #495: 1: Success after binutils/gcc: 311 commits discards aeaa1b430b 94: onsuccess: #494: 1: Success after gcc: 11 commits discards b2dd453b7d 93: force: #493: 1: Failure after gcc: 10 commits discards 794218c8b7 92: onsuccess: #489: 2: Success after binutils: 5 commits discards 9491b51525 91: onsuccess: #487: 2: Success after binutils/gcc: 61 commits discards 0ed0086090 90: onsuccess: #486: 2: Success after binutils/gcc: 51 commits discards 61e8b5776d 89: onsuccess: #485: 2: Success after binutils/gcc: 60 commits discards 0612443a56 88: onsuccess: #484: 2: Success after binutils/gcc: 65 commits discards bb2e5aa88a 87: onsuccess: #483: 2: Success after binutils/gcc: 63 commits discards ca273e7e35 86: onsuccess: #482: 2: Success after binutils/gcc: 15 commits discards 90530db676 85: onsuccess: #481: 2: Success after binutils/gcc: 24 commits discards 1e24c8a308 84: onsuccess: #480: 2: Success after binutils/gcc: 87 commits discards 25ff6abf79 83: onsuccess: #479: 2: Success after binutils/gcc: 30 commits discards 3497c8afce 82: onsuccess: #478: 2: Success after binutils/gcc: 30 commits discards c4cc6c7612 81: onsuccess: #477: 2: Success after binutils/gcc: 27 commits discards a6ed5bb80c 80: onsuccess: #476: 2: Success after binutils/gcc: 33 commits discards 6fd5eb8b17 79: onsuccess: #475: 2: Success after binutils/gcc: 3 commits discards b1ba5e4b86 78: onsuccess: #474: 2: Success after binutils/gcc: 31 commits discards cc63c35ac8 77: onsuccess: #473: 2: Success after binutils/gcc: 34 commits discards 0c7393352f 76: onsuccess: #472: 2: Success after binutils/gcc: 29 commits discards eb527e7976 75: onsuccess: #471: 2: Success after binutils/gcc: 34 commits discards 0e06b8054a 74: onsuccess: #470: 2: Success after binutils/gcc: 39 commits discards 06ec09495e 73: onsuccess: #469: 2: Success after binutils/gcc: 34 commits discards cd97710c88 72: onsuccess: #468: 2: Success after binutils/gcc: 4 commits discards e5ab183bd9 71: onsuccess: #467: 2: Success after binutils/gcc: 9 commits discards bf789dd838 70: onsuccess: #466: 2: Success after binutils/gcc: 41 commits discards f0313c9e7e 69: onsuccess: #465: 2: Success after binutils/gcc: 50 commits discards 6ba2b3b9d5 68: onsuccess: #464: 2: Success after binutils/gcc: 41 commits discards 4a848ffaa4 67: onsuccess: #463: 2: Success after binutils/gcc: 53 commits new 8c8352e4b3 67: onsuccess: #463: 2: Success after binutils/gcc: 53 commits new e5d5569384 68: onsuccess: #464: 2: Success after binutils/gcc: 41 commits new 6c454de053 69: onsuccess: #465: 2: Success after binutils/gcc: 50 commits new eebcdb1b6a 70: onsuccess: #466: 2: Success after binutils/gcc: 41 commits new 07a07faece 71: onsuccess: #467: 2: Success after binutils/gcc: 9 commits new 84bdb7974b 72: onsuccess: #468: 2: Success after binutils/gcc: 4 commits new 56de43453a 73: onsuccess: #469: 2: Success after binutils/gcc: 34 commits new f5ce5c967c 74: onsuccess: #470: 2: Success after binutils/gcc: 39 commits new 1d41716080 75: onsuccess: #471: 2: Success after binutils/gcc: 34 commits new 547c1110de 76: onsuccess: #472: 2: Success after binutils/gcc: 29 commits new f49c99304e 77: onsuccess: #473: 2: Success after binutils/gcc: 34 commits new 3eae36364b 78: onsuccess: #474: 2: Success after binutils/gcc: 31 commits new eee247adab 79: onsuccess: #475: 2: Success after binutils/gcc: 3 commits new 5354b6d14c 80: onsuccess: #476: 2: Success after binutils/gcc: 33 commits new 9bdb1d9533 81: onsuccess: #477: 2: Success after binutils/gcc: 27 commits new b2f9bd65ae 82: onsuccess: #478: 2: Success after binutils/gcc: 30 commits new 21a947e193 83: onsuccess: #479: 2: Success after binutils/gcc: 30 commits new 59c2934f45 84: onsuccess: #480: 2: Success after binutils/gcc: 87 commits new 221f93e74f 85: onsuccess: #481: 2: Success after binutils/gcc: 24 commits new f61febde6c 86: onsuccess: #482: 2: Success after binutils/gcc: 15 commits new 43e9f3a2d8 87: onsuccess: #483: 2: Success after binutils/gcc: 63 commits new da5c8e6b89 88: onsuccess: #484: 2: Success after binutils/gcc: 65 commits new 936088887f 89: onsuccess: #485: 2: Success after binutils/gcc: 60 commits new 85b6937b1b 90: onsuccess: #486: 2: Success after binutils/gcc: 51 commits new 2bf17540fb 91: onsuccess: #487: 2: Success after binutils/gcc: 61 commits new 32d22dc474 92: onsuccess: #489: 2: Success after binutils: 5 commits new d26fe48574 93: force: #493: 1: Failure after gcc: 10 commits new 7c52bf434b 94: onsuccess: #494: 1: Success after gcc: 11 commits new 10190edce4 95: onsuccess: #495: 1: Success after binutils/gcc: 311 commits new 67a485b580 96: onsuccess: #496: 2: Success after binutils/gcc: 30 commits new afbdeab4b4 97: onsuccess: #497: 2: Success after binutils/gcc: 9 commits new 33c6e0a6bc 98: onsuccess: #498: 2: Success after binutils/gcc: 42 commits new 4b7800fd76 99: onsuccess: #499: 2: Success after binutils/gcc: 36 commits new b36a1aa191 100: onsuccess: #500: 2: Success after binutils/gcc: 50 commits new 9dd0037fcf 101: onsuccess: #501: 2: Success after binutils/gcc: 49 commits new ac5938b259 102: onsuccess: #506: 2: Success after binutils/gcc: 32 commits new 83e1c0ae05 103: onsuccess: #507: 2: Success after binutils/gcc: 83 commits new ef1634087f 104: onsuccess: #508: 2: Success after binutils/gcc: 54 commits new 3ba5e9e345 105: onsuccess: #509: 2: Success after binutils/gcc: 39 commits new 31fc358816 106: onsuccess: #510: 2: Success after binutils/gcc: 55 commits new be954cc5e3 107: onsuccess: #511: 2: Success after binutils/gcc: 30 commits new 1f84dc440c 108: onsuccess: #512: 2: Success after binutils/gcc: 15 commits new f84bc84f2c 109: onsuccess: #513: 2: Success after binutils/gcc: 9 commits new af5a13cb2b 110: onsuccess: #515: 2: Success after binutils/gcc: 71 commits new 78153a2b11 111: onsuccess: #516: 2: Success after binutils/gcc: 32 commits new db01bc899a 112: onsuccess: #519: 2: Success after binutils/gcc: 77 commits new 447aa0c51f 113: onsuccess: #520: 2: Success after binutils/gcc: 11 commits new 6d2b4fe489 114: onsuccess: #521: 2: Success after binutils/gcc: 42 commits new 98ce735f6b 115: onsuccess: #522: 2: Success after binutils/gcc: 71 commits new 6445664e37 116: onsuccess: #523: 2: Success after binutils/gcc: 48 commits new d644827cd0 117: onsuccess: #524: 2: Success after binutils/gcc: 25 commits new ed309b0262 118: onsuccess: #525: 2: Success after binutils/gcc: 42 commits new 7ebbff0481 119: onsuccess: #526: 2: Success after binutils/gcc: 26 commits new 460a1e877f 120: onsuccess: #527: 2: Success after binutils/gcc: 9 commits new 7b41ff5445 121: onsuccess: #528: 2: Success after binutils/gcc: 49 commits new bf097fed92 122: onsuccess: #529: 2: Success after binutils/gcc: 18 commits new 85c3a1d96a 123: onsuccess: #530: 2: Success after binutils/gcc: 65 commits new 49312903b1 124: onsuccess: #531: 2: Success after binutils/gcc: 37 commits new 96a6b1dbee 125: onsuccess: #532: 2: Success after binutils/gcc: 95 commits new 9701ef6cfd 126: onsuccess: #533: 2: Success after binutils/gcc: 9 commits new d2fc173edb 127: onsuccess: #534: 2: Success after binutils/gcc: 27 commits new e147903358 128: onsuccess: #535: 2: Success after binutils/gcc: 6 commits new 187db30b97 129: onsuccess: #536: 2: Success after binutils/gcc: 23 commits new b78de43276 130: onsuccess: #537: 2: Success after binutils/gcc: 15 commits new 660c4a0137 131: onsuccess: #538: 2: Success after binutils/gcc: 5 commits new 3944ceabb4 132: onsuccess: #539: 2: Success after binutils/gcc: 28 commits new 49c91961c6 133: onsuccess: #540: 2: Success after binutils/gcc: 16 commits new 64f4b151a5 134: onsuccess: #541: 2: Success after binutils/gcc: 13 commits new f805a17d11 135: onsuccess: #543: 2: Success after binutils: 14 commits new aa9e6802e0 136: force: #546: 2: Success after gcc: 8 commits new e646437852 137: force: #547: 1: Failure after basepoints/gcc-13-4953-g3 [...] new a03a90597a 138: onsuccess: #548: 1: Success after gcc: 3 commits new 172513e923 139: onsuccess: #549: 2: Success after binutils/gcc: 104 commits new f7e6480458 140: onsuccess: #551: 2: Success after binutils/gcc: 68 commits new e958afcf43 141: onsuccess: #552: 2: Success after binutils/gcc: 9 commits new 9734c8dbcb 142: onsuccess: #553: 2: Success after binutils/gcc: 6 commits new e9e7614d84 143: onsuccess: #555: 2: Success after binutils/gcc: 139 commits new 77832629e6 144: onsuccess: #556: 2: Success after binutils/gcc: 36 commits new bcc2c1d14c 145: onsuccess: #557: 2: Success after binutils/gcc: 137 commits new 027789acc7 146: onsuccess: #558: 2: Success after binutils/gcc: 34 commits new b92ef98f1c 147: onsuccess: #559: 2: Success after binutils/gcc: 76 commits new 85b52115f5 148: onsuccess: #560: 2: Success after binutils/gcc: 32 commits new 827c28ed74 149: onsuccess: #561: 2: Success after binutils/gcc: 41 commits new 29b6154e80 150: onsuccess: #562: 2: Success after binutils/gcc: 39 commits new 4809cbf3c4 151: onsuccess: #563: 2: Success after binutils/gcc: 5 commits new 3b9a94752d 152: onsuccess: #564: 2: Success after binutils/gcc: 11 commits new 1f87284b37 153: onsuccess: #565: 2: Success after binutils/gcc: 52 commits new 1c217b3974 154: onsuccess: #566: 2: Success after binutils/gcc: 65 commits new 2619fe05d9 155: onsuccess: #567: 2: Success after binutils/gcc: 27 commits new 48630e4f62 156: onsuccess: #568: 2: Success after binutils/gcc: 117 commits new 754ee651fb 157: onsuccess: #569: 2: Success after binutils/gcc: 43 commits new fdb5c476f7 158: onsuccess: #570: 2: Success after binutils/gcc: 13 commits new 15ce9189c1 159: onsuccess: #571: 2: Success after binutils/gcc: 55 commits new b3c3a1dfba 160: onsuccess: #572: 2: Success after binutils/gcc: 107 commits new 84d6db4f4d 161: onsuccess: #573: 2: Success after binutils/gcc: 41 commits new 4c7dceb58f 162: onsuccess: #574: 2: Success after binutils/gcc: 55 commits new e2cb8e39e9 163: onsuccess: #575: 2: Success after binutils/gcc: 30 commits new daae9791dc 164: onsuccess: #576: 2: Success after binutils/gcc: 5 commits new 4f1c61e5cb 165: onsuccess: #577: 2: Success after binutils/gcc: 31 commits new d398c4bcfd 166: onsuccess: #578: 2: Success after binutils/gcc: 16 commits new 091bedbb74 167: onsuccess: #579: 2: Success after binutils/gcc: 43 commits new 3758804182 168: onsuccess: #580: 2: Success after binutils/gcc: 23 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 (195d06c137) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] 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 1780 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 39020 -> 39088 bytes 05-build_abe-bootstrap_profiled/console.log.xz | Bin 516048 -> 516316 bytes 06-check_regression/console.log.xz | Bin 3092 -> 3068 bytes 07-update_baseline/console.log | 36 ++++++++++++------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +++++++------- 13 files changed, 34 insertions(+), 34 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[binutils-gdb] branch master updated (be01687991a -> 632652850db)

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 be01687991a [gdb/cli] Add maint info frame-unwinders new 632652850db [gdb/testsuite] Fix linespec ambiguity in gdb.base/longjmp.exp The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gdb/testsuite/gdb.base/longjmp.exp | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch master updated (edfc4402504 -> 6493b7af37e)

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 edfc4402504 RISC-V: Add vand.vx C++ API test. new 99f3ad2e5b1 Add function context for querying global ranges. new 6493b7af37e Query rangers cache in readonly mode only from within The 2 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/gimple-range-cache.cc | 4 ++-- gcc/gimple-range-infer.cc | 2 +- gcc/testsuite/g++.dg/pr108520.C | 17 +++++++++++++++++ gcc/value-query.cc | 10 +++++----- gcc/value-query.h | 4 +++- 5 files changed, 28 insertions(+), 9 deletions(-) create mode 100644 gcc/testsuite/g++.dg/pr108520.C -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (361b2f40e7 -> e5ef86d88c)

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 361b2f40e7 407: onsuccess: #2143: 7: Success after binutils/gcc/linux/g [...] discards c0dde4d326 406: onsuccess: #2142: 7: Success after binutils/gcc/gdb: 14 [...] discards 2fa4ccaf23 405: onsuccess: #2141: 7: Success after binutils/gcc/linux/g [...] discards 82bbc53475 404: onsuccess: #2139: 7: Success after basepoints/gcc-13-57 [...] discards 42e4d2c5fb 403: onsuccess: #2138: 7: Success after binutils/gcc/gdb: 4 commits discards 1703f73cd0 402: onsuccess: #2137: 7: Success after binutils/gcc/gdb: 22 [...] discards 1cfb8a0df2 401: onsuccess: #2136: 7: Success after binutils/gcc/glibc/g [...] discards 617f046972 400: onsuccess: #2135: 7: Success after binutils/gcc/linux/g [...] discards ed6b52ba6b 399: onsuccess: #2134: 7: Success after binutils/gcc/linux/g [...] discards be985ff634 398: onsuccess: #2133: 7: Success after binutils/gcc/glibc/g [...] discards 2d62ed42bb 397: onsuccess: #2132: 7: Success after gcc: 2 commits discards 11455e56d3 396: onsuccess: #2131: 7: Success after binutils/gcc/linux/g [...] discards 3e695c5ed5 395: onsuccess: #2130: 7: Success after binutils/gcc/gdb/qem [...] discards 6997c35aab 394: onsuccess: #2129: 7: Success after binutils/gcc/linux/g [...] discards 0922679cc9 393: onsuccess: #2128: 7: Success after gcc/qemu: 42 commits discards 0953258100 392: onsuccess: #2127: 7: Success after glibc-2.37.9000-17-g [...] discards e18094dcc0 391: onsuccess: #2126: 7: Success after binutils/gcc/linux/g [...] discards 25e3b4e1ab 390: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] discards 5932c47d1a 389: onsuccess: #2124: 7: Success after binutils/gcc/gdb: 5 commits discards 1fbdb27b95 388: onsuccess: #2123: 7: Success after binutils/gcc/gdb: 3 commits discards fb2d62d6a2 387: onsuccess: #2122: 7: Success after gcc/linux/qemu: 117 commits discards d18f139776 386: onsuccess: #2121: 7: Success after binutils/gcc/glibc/g [...] discards 899f71797b 385: onsuccess: #2120: 7: Success after binutils/gcc/gdb/qem [...] discards 288436e28f 384: onsuccess: #2119: 7: Success after binutils/gcc/linux/g [...] discards 2ead99416e 383: onsuccess: #2118: 7: Success after binutils/gcc/glibc/g [...] discards d3c115402f 382: onsuccess: #2117: 7: Success after binutils/gcc/linux/g [...] discards 9f375380b8 381: onsuccess: #2116: 7: Success after binutils/gcc/linux/g [...] discards 7e507d4a7d 380: onsuccess: #2115: 7: Success after binutils/gcc/linux/g [...] discards 0dba8cc0aa 379: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] discards 997a97ae7f 378: onsuccess: #2113: 7: Success after binutils/gcc/linux/g [...] discards eb1a532f92 377: onsuccess: #2112: 7: Success after binutils/gcc/gdb: 16 [...] discards 09f0d7fef1 376: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] discards 29674cf7ea 375: onsuccess: #2110: 7: Success after binutils/gcc/linux/g [...] discards 6c2f56fcbd 374: onsuccess: #2109: 7: Success after binutils/gcc/linux/g [...] discards 7231f520e6 373: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] discards 575e1a46cd 372: onsuccess: #2106: 7: Success after binutils/gcc/linux/g [...] discards 332d1f708a 371: onsuccess: #2105: 7: Success after binutils/gcc/gdb/qem [...] discards dff3644ba0 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] discards be8e7141a2 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] discards 23cedf0705 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] discards 0a29b9dfdc 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] discards 4f43103ed3 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] discards 7a141854da 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits discards 253b68c283 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits discards 8081702698 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] discards 8c6187aeed 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] discards f02f2e6a60 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits discards b9895005a7 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards 16d34a4b8d 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] discards dd77297895 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] discards 4e7bb99c0b 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] discards c989b5ef05 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards 086b145b2a 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] discards f0fba28415 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits discards b4a45a170b 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards f4419c99d4 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits discards e6b2794128 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] discards f6fd46b397 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards 39a1365832 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards 3053548474 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] discards 8600e7593d 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] discards d1e380a2af 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits discards f42f47fd13 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] discards 15fd3b902f 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits discards d53a3fae13 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] discards 2547712ea3 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits discards 9644adc54b 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits discards e738afc735 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits discards 74a6fdcd55 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits discards cb7203cb8a 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] discards e5adb52988 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] discards a1234abe95 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] discards e80952e7be 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards 517d1f3d9b 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] discards b5c85230ce 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] discards 623015f749 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] discards c54e0d6947 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 82ee728f57 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits discards 47bb1498b7 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] discards 613b618caa 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards aa5c56c795 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards 1316299096 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] discards c461e5c7a0 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits discards aab46e5de7 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards 23d06c266a 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] discards c440d0eafe 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] discards 128db75c5b 321: force: #2055: 7: Success after gdb: 2 commits discards dd1ae2b97a 320: onsuccess: #2050: 7: Success after gcc: 4 commits discards a844d80323 319: onsuccess: #2049: 7: Success after binutils: 4 commits discards a003c977b3 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] discards 3a59273c90 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits discards f80fe06f41 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 36bb2f55d7 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards 0dc1522b66 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] discards ebf33b506b 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits discards d4ab5b99d1 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits discards 73ec19bf6f 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits discards 5eb4416aac 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits discards b949ab50ac 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits discards 0e3ed79ac1 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards 316cabbbe4 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits new 4254289ae8 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits new 74ba77a943 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new 7ae227a493 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits new d6f4364c9c 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits new 40c7e59e5b 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits new 8dfb293809 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits new 5581a2d9f9 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits new 2abec5a4f8 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] new 43bb5b52ac 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new a89fd8d44b 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new 08d7661dc2 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits new 81a5c12261 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] new d026260f34 319: onsuccess: #2049: 7: Success after binutils: 4 commits new 1bde622ff2 320: onsuccess: #2050: 7: Success after gcc: 4 commits new 783d2b5238 321: force: #2055: 7: Success after gdb: 2 commits new 7238680e82 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] new a754400ba7 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] new c3fe2d17d0 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new 1b2758184f 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits new c63d642505 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] new 2757260650 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new 44eb33d0d0 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new 4be679a7d4 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] new 457d31668f 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits new d978694314 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new 755ecfe579 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] new 2515f4f9a5 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] new f0f83e6f5f 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] new c928123703 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new 750291e66e 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] new 0919d147f0 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] new 416bcd101c 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] new 351bd15361 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits new 2199e2c7a5 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits new 9ea3e8f081 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits new 6916036376 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits new 9e703bb696 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] new c638e07e0e 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits new 62c575c123 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] new 4164107e1a 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits new a0d1f87663 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] new 5e3fae6385 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] new fde9389e54 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new fefb835a0c 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new 65efef4199 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] new e971c16ab7 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits new a385300315 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new 88e47a9f4a 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits new d5076e2e99 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] new 32f8bc0ff3 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new eb42e57908 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] new fa1169bae6 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] new da5f4eb2d4 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] new d832e4c469 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new 8ac667a7a6 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits new 2a6c540c47 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] new d92d7017eb 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] new 9f29367788 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits new 0d2c06b19d 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits new fa40302300 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] new ae9c430505 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] new d2b26b2f69 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] new 00146ab445 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] new 479be0261d 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] new 966f9217ab 371: onsuccess: #2105: 7: Success after binutils/gcc/gdb/qem [...] new 0f452f2154 372: onsuccess: #2106: 7: Success after binutils/gcc/linux/g [...] new f8e9c2167f 373: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] new 2f280426a5 374: onsuccess: #2109: 7: Success after binutils/gcc/linux/g [...] new e0bda61076 375: onsuccess: #2110: 7: Success after binutils/gcc/linux/g [...] new f6375c2836 376: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] new ef47bad7b7 377: onsuccess: #2112: 7: Success after binutils/gcc/gdb: 16 [...] new 6454035206 378: onsuccess: #2113: 7: Success after binutils/gcc/linux/g [...] new 2868561a9b 379: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] new 2ad03eb05c 380: onsuccess: #2115: 7: Success after binutils/gcc/linux/g [...] new 7ad905ca2d 381: onsuccess: #2116: 7: Success after binutils/gcc/linux/g [...] new bff150d826 382: onsuccess: #2117: 7: Success after binutils/gcc/linux/g [...] new b5bff3b1dc 383: onsuccess: #2118: 7: Success after binutils/gcc/glibc/g [...] new d05216a5d7 384: onsuccess: #2119: 7: Success after binutils/gcc/linux/g [...] new e0a1aaf78b 385: onsuccess: #2120: 7: Success after binutils/gcc/gdb/qem [...] new 9b905e7061 386: onsuccess: #2121: 7: Success after binutils/gcc/glibc/g [...] new ee00e2ed63 387: onsuccess: #2122: 7: Success after gcc/linux/qemu: 117 commits new e013aa8740 388: onsuccess: #2123: 7: Success after binutils/gcc/gdb: 3 commits new d05ed054df 389: onsuccess: #2124: 7: Success after binutils/gcc/gdb: 5 commits new 2c99a7f5f0 390: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] new e76d50d8e8 391: onsuccess: #2126: 7: Success after binutils/gcc/linux/g [...] new 24ea2cfa57 392: onsuccess: #2127: 7: Success after glibc-2.37.9000-17-g [...] new 20ac5ee783 393: onsuccess: #2128: 7: Success after gcc/qemu: 42 commits new c90224fede 394: onsuccess: #2129: 7: Success after binutils/gcc/linux/g [...] new 9080ebabcc 395: onsuccess: #2130: 7: Success after binutils/gcc/gdb/qem [...] new 4fd17cfc10 396: onsuccess: #2131: 7: Success after binutils/gcc/linux/g [...] new 323d73ccd1 397: onsuccess: #2132: 7: Success after gcc: 2 commits new 293792d262 398: onsuccess: #2133: 7: Success after binutils/gcc/glibc/g [...] new 81c0b1554f 399: onsuccess: #2134: 7: Success after binutils/gcc/linux/g [...] new 7502d38c7c 400: onsuccess: #2135: 7: Success after binutils/gcc/linux/g [...] new 9cfa5f9bc1 401: onsuccess: #2136: 7: Success after binutils/gcc/glibc/g [...] new d47c5f58aa 402: onsuccess: #2137: 7: Success after binutils/gcc/gdb: 22 [...] new 9f14a74d9b 403: onsuccess: #2138: 7: Success after binutils/gcc/gdb: 4 commits new e00b43a6a1 404: onsuccess: #2139: 7: Success after basepoints/gcc-13-57 [...] new 62c8d1f39f 405: onsuccess: #2141: 7: Success after binutils/gcc/linux/g [...] new 948979b739 406: onsuccess: #2142: 7: Success after binutils/gcc/gdb: 14 [...] new b1c3d16dc6 407: onsuccess: #2143: 7: Success after binutils/gcc/linux/g [...] new e5ef86d88c 408: onsuccess: #2144: 7: Success after binutils/gcc/gdb/qem [...] 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 (361b2f40e7) \ 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 1736 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2792 bytes 04-build_abe-binutils/console.log.xz | Bin 31020 -> 31404 bytes 05-build_abe-stage1/console.log.xz | Bin 91860 -> 92428 bytes 07-build_abe-linux/console.log.xz | Bin 9356 -> 9404 bytes 08-build_abe-glibc/console.log.xz | Bin 236412 -> 236996 bytes 09-build_abe-stage2/console.log.xz | Bin 227904 -> 227816 bytes 10-build_abe-gdb/console.log.xz | Bin 38360 -> 38884 bytes 11-build_abe-qemu/console.log.xz | Bin 30808 -> 31440 bytes 12-check_regression/console.log.xz | Bin 4036 -> 4164 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++++++++++----------- 20 files changed, 59 insertions(+), 59 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-fujitsu_speed-cpu2017rate/gnu-aarch64-master-O2 updated (77af556247 -> 6601438c31)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-fujitsu_speed-cpu2017rate/gnu-aarch64-master-O2 in repository toolchain/ci/base-artifacts. from 77af556247 53: force: #35: 1: [TCWG CI] No change after v6.1.8-105-gf5e [...] new 6601438c31 54: onsuccess: #36: 1: [TCWG CI] No change after linux: 4579 [...] 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 1804 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31820 -> 31824 bytes 04-build_abe-stage1/console.log.xz | Bin 74076 -> 73924 bytes 06-build_abe-linux/console.log.xz | Bin 9128 -> 8708 bytes 07-build_abe-glibc/console.log.xz | Bin 247192 -> 246976 bytes 08-build_abe-stage2/console.log.xz | Bin 183716 -> 188516 bytes 09-benchmark/benchmark-build.log | 108 +- 09-benchmark/benchmark.log | 106 +- 09-benchmark/console.log.xz | Bin 3880 -> 3916 bytes 10-check_regression/console.log.xz | Bin 13156 -> 13564 bytes .../csv-results-vs-first-1/md5sum.csv | 1736 +- .../csv-results-vs-first-1/perf.csv | 2793 +- .../csv-results-vs-first-1/results.csv | 9967 +- .../csv-results-vs-first-1/size.csv | 205364 +++++---- 10-check_regression/csv-results-vs-first-1/sve.csv | 10456 +- .../csv-results-vs-first-1/vect.csv | 212 +- .../csv-results-vs-prev-0/md5sum.csv | 2054 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 2773 +- .../csv-results-vs-prev-0/results.csv | 15810 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 423334 +++++++++--------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 13986 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 256 +- .../csv-results-vs-prev-1/md5sum.csv | 1736 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 2793 +- .../csv-results-vs-prev-1/results.csv | 9967 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 205364 +++++---- 10-check_regression/csv-results-vs-prev-1/sve.csv | 10456 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 212 +- 10-check_regression/results-vs-first-brief.csv | 56 +- 10-check_regression/results-vs-first-full.csv | 2728 +- 10-check_regression/results-vs-first-internal.csv | 186 +- 10-check_regression/results-vs-first.csv | 186 +- 10-check_regression/results-vs-first.log | 952 +- 10-check_regression/results-vs-prev-brief.csv | 56 +- 10-check_regression/results-vs-prev-compare.csv | 4 +- 10-check_regression/results-vs-prev-full.csv | 2870 +- 10-check_regression/results-vs-prev-internal.csv | 190 +- 10-check_regression/results-vs-prev.csv | 190 +- 10-check_regression/results-vs-prev.log | 1040 +- 10-check_regression/skipped-symbols.txt | 2 +- 11-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 10 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 10 +- .../503.bwaves_r/results-metadata.json | 10 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 10 +- .../507.cactuBSSN_r/results-metadata.json | 10 +- .../508.namd_r/results-metadata.json | 10 +- .../510.parest_r/results-metadata.json | 10 +- .../511.povray_r/results-metadata.json | 10 +- .../511.povray_r/results-metrics.json | 2 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 10 +- .../520.omnetpp_r/results-metadata.json | 10 +- .../520.omnetpp_r/results-metrics.json | 2 +- .../squad-vs-first/521.wrf_r/results-metadata.json | 10 +- .../523.xalancbmk_r/results-metadata.json | 10 +- .../525.x264_r/results-metadata.json | 10 +- .../526.blender_r/results-metadata.json | 10 +- .../527.cam4_r/results-metadata.json | 10 +- .../squad-vs-first/527.cam4_r/results-metrics.json | 2 +- .../531.deepsjeng_r/results-metadata.json | 10 +- .../531.deepsjeng_r/results-metrics.json | 2 +- .../538.imagick_r/results-metadata.json | 10 +- .../541.leela_r/results-metadata.json | 10 +- .../squad-vs-first/544.nab_r/results-metadata.json | 10 +- .../548.exchange2_r/results-metadata.json | 10 +- .../549.fotonik3d_r/results-metadata.json | 10 +- .../554.roms_r/results-metadata.json | 10 +- .../squad-vs-first/554.roms_r/results-metrics.json | 2 +- .../squad-vs-first/557.xz_r/results-metadata.json | 10 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 98 +- git/linux_rev | 2 +- mail/jira-body.txt | 11 +- mail/mail-body.txt | 11 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results_id | 2 +- 79 files changed, 465239 insertions(+), 463098 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (d1da188a80 -> 531983cc33)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards d1da188a80 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 48db3fff04 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 0405b777eb 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 16af9fbb8c 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 5480015ec1 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards e3b9fdbaa4 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 1e663a9042 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 52ea0cb736 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 986555f5d9 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 9d8f106de1 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards f44d7d71b2 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 3ab854d060 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 562574e476 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 1a8e5cf26a 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards d80e1f05e5 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 089b423d23 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 75c3ad7c79 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 695a2bf3a5 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 65e223b683 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards a489745c37 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards ee8ee2251f 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 623153d069 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards df354603ee 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 81c7a2203a 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 7c7102eda1 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 1c0fb77a52 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 55f8f09597 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards aa95b2d17e 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards ed5e36fa57 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 2bdce65cf2 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 6a4bba0402 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 86fd3ccad3 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 15e97fc96a 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 191b5901d3 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards ae0fba5b9b 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 9f7bd9ff57 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 74af86ce04 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards ae458b159a 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards c396244e10 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 79bd89044e 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards dd9e8c4862 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards cf3cc03dc2 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 0d85506880 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 30a59ccef0 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards f76a860c35 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 22e5b6d190 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 7ba5b904bf 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 968c6a6abc 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 30c22fc2a6 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 990f479d67 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards ebbcab6fb6 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards d4e1e9ea74 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 3b132be110 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 61644a76a0 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards b4fc00d608 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 83dae4a708 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 026834b9b0 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards ac43432cb2 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 1fa46a8323 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards cca2670b69 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 5260c4fa2a 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 39eb23c4fb 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards a7e773ebeb 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards da40f8bf37 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 0743dc022e 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 853469ec78 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 356f240792 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards da5855f53c 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 11629f7a12 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 8ab1059922 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards c4e4c534f5 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 541340611d 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards cf32b3739a 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 7a33b26c63 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 2966cdfba9 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards b805ff64b5 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards f69834a310 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards aab99f3084 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 01dcdc4d2c 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 611f6d69bb 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 547341ec11 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 902f69c40f 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards f377976a29 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 9ec3c2a2a7 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 94e9aef106 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 422375620e 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards c8769e3b61 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards c4cf95d7d7 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards bbc71d1571 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 55b165bb90 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards eea3093a23 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards e800728c36 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 18d92c923e 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 3485756c0d 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards b608db89fd 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 66c152703f 301: onsuccess: #2118: 1: Success after linux: 16 commits discards de38d86801 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 0fbfa5a634 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 8c9f6baa43 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 5f6ede2ff8 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards ebd53026c1 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 4aa5649fc9 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new f7815925b6 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 7a2eb97e5b 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 3e6309063a 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 9920a37271 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 0fdd16c443 301: onsuccess: #2118: 1: Success after linux: 16 commits new 6bd6859e0b 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new ff8567fdc8 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 276df279d9 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 10c11bebcc 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 019d130f81 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 099d9f19fa 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 30ec737c10 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 2e969e5676 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 51c6f84e14 310: onsuccess: #2129: 1: Success after binutils: 4 commits new fbc51565bd 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 06c7892017 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new e2a26665dd 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 33f514a94e 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 4df974a83f 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 149108daf0 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 6b39a72224 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new ab4cedb9bd 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new ca1790a4e4 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new c99123ef96 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 40fdd39ee1 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new a1ac9c7493 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new dd28aad890 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 78973d0811 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 917ba96cb4 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new e0216145e2 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 3acfafdfc4 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 8d7c21f6a1 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new cd9c63c78b 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 92824673af 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new ace3d26754 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 3051148946 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new c045bd4062 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new dbc8526681 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 1c50c57cde 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 7d68ed7ea4 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 23a7f59a7c 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 0a84d89044 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new d51f9a1964 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 76a77c2be1 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 1324ba9283 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 781abce72f 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new eacd0c7e69 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 5f47bccbc7 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 621d2b3f61 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 3a949d918f 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 3e615efb37 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new fc3d0697f5 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 303f5a4126 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 5d35f03211 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 40599d572b 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 84a472cbf1 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 9f8c71a9b8 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new d1f3785cf1 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 193d696582 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new ab97d6a9dc 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 9b37a77e72 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new c42a45810a 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 2c6899fa6b 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new de8d965520 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new a277856390 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 9052c946ef 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 671a9096b6 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new d67c9d0e5d 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 75f9f44148 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 48f4aa2f05 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 4fca1d7451 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 0fc9bee10d 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 557c6c5edc 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 21c09e845a 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 11027f54c6 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 2bab471ea6 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new a2413d4fdd 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new c7e7a36caa 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 333a53d8d3 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 6b9cd94a62 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 16ee579285 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new de4608cf8b 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new f5d48a5fba 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 76cca0f78d 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 4b43491f64 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 1b6b5f4c31 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 53e7ab9670 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new bd2ca0b42c 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 5eae999a38 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new e83307dd57 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new cffc987933 387: onsuccess: #2208: 1: Success after gcc: 2 commits new dbf9890d02 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 1c9a8e3951 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new e6c7e32e7f 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 89ebe5671a 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new b90bc11e67 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new e9e8375fcd 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 1871e8d733 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 12e93408b4 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 8de1a61ad6 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 531983cc33 397: onsuccess: #2218: 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 (d1da188a80) \ 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 1816 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 31040 -> 30868 bytes 04-build_abe-stage1/console.log.xz | Bin 91984 -> 91792 bytes 06-build_abe-linux/console.log.xz | Bin 8612 -> 9376 bytes 07-build_abe-glibc/console.log.xz | Bin 236352 -> 235792 bytes 08-build_abe-stage2/console.log.xz | Bin 229732 -> 228136 bytes 09-build_abe-gdb/console.log.xz | Bin 38488 -> 38460 bytes 10-build_abe-qemu/console.log.xz | Bin 30832 -> 30636 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3916 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2984 -> 3104 bytes 13-check_regression/console.log.xz | Bin 7400 -> 6780 bytes 13-check_regression/fails.sum | 2 +- 13-check_regression/mail-body.txt | 60 +- 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 124 +- 13-check_regression/results.regressions | 25 +- 14-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 | 2 +- mail/mail-body.txt | 62 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 25 +- sumfiles/g++.log.xz | Bin 2650780 -> 2651172 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2186412 -> 2205476 bytes sumfiles/gcc.sum | 2069 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 886596 -> 893624 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2252 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217064 -> 216992 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434616 -> 434720 bytes sumfiles/libstdc++.sum | 35 +- 42 files changed, 1268 insertions(+), 1307 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-allyesconfig updated (ec3088f1eb -> 87ea8f3c3e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-allyesconfig in repository toolchain/ci/base-artifacts. from ec3088f1eb 46: onsuccess: #505: 33: Success after binutils/gcc/linux/qe [...] new 87ea8f3c3e 47: onsuccess: #506: 33: Success after binutils/gcc/linux/qe [...] 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 1764 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 31184 -> 31764 bytes 04-build_abe-stage1/console.log.xz | Bin 91732 -> 92596 bytes 05-build_abe-qemu/console.log.xz | Bin 31152 -> 31628 bytes 06-build_linux/console.log.xz | Bin 5236 -> 5080 bytes 08-check_regression/console.log.xz | Bin 4348 -> 4244 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 16 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (c5d81031a0 -> 5bbeb958ac)

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 c5d81031a0 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 6dc6f1ceb3 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards a3b49d136e 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 6e1403ebd2 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 825a156de5 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards afe9446b51 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 9e04c1dfc6 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 6ee5423e97 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 0140d6d5db 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 89952f3086 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 9fd8b28b98 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 3d8d209222 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 2cad31049c 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards b7635702fd 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards e4660a4a47 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards cdc36108e6 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 4e4474919e 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 74c3f8156d 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 8e7e18f330 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 6ee0875fc9 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards da43dda343 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards c757ce6b1b 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards a222b4a3af 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards f23fed92c6 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 676826c8c3 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 1bff27b422 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 384c3150e1 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 9b29b6e92d 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 56f043820a 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 88ff27f397 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 7be837a5c9 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 5407f29f08 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 295307e4f6 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 168b21aea4 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 6e9300e2b9 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 5212921009 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards ac62edb17b 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards f4109b9507 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 402749baca 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 6ddd585bc2 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 5348f008a1 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards eb38550b16 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 30745a0276 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 20133d70c6 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards a7e47dd526 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 689b877827 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards e6e6b7f833 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards ef6a20c04d 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 189fee0e2b 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards fa48e9e070 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards c0223cf115 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 95d7e2f290 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 39ad255817 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards bc9d890149 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 9c5c8b8650 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 458ae02b37 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 9a17637e9d 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 1f3cc430ef 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 126158ca12 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards ce8884f15c 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards b90e8ed774 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards cf27fda2f8 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards e2af9c6838 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 9d8204675c 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 771b764745 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 7b52b01b20 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards cc56f30469 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards d1cdcde4ff 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 73b37d8c72 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 8e7f0a6233 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 55d3a1711b 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards befda919be 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 16da28f9b6 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards f20b8b8735 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 7a79026b41 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards f2b26377af 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 5f7d3b762c 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 6c1d2a8422 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards f4471e4327 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 23412d8233 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 179a9a1056 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards b2ccb93b11 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 950245be25 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 95ebf0c98e 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 45a13c64a7 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 9cb82aa629 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards d0bf689893 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 7c0ae9d4f7 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards ed9672dc33 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards f5c5a9f40a 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 2b05806f57 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 4296e9b735 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 3e6e9785d7 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 41b50d2032 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 9fce70bd42 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 4651f65d75 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards c6549e849d 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards ef30df4251 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 6fc5bd9bba 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 7da139a378 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 66bf3857fb 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 81d4bc43b6 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new e622ec3350 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 345f505e1e 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 1a8beb3583 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 2760722022 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 54722485e2 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new de187a2106 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new fbc8539d56 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new d143b076cb 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new fbb87fbe35 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 3b24692c7c 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new adf3142644 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new a0ccf09b58 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 1a763b1434 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 76cf5bdc63 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 1e6c072724 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 5149590f5d 295: onsuccess: #2545: 1: Success after linux: 10 commits new 7b76d35258 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 698cd25e07 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 227a40f74e 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new cbf5dec350 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new ea36016146 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 19a22ec5e9 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 849cf2ad85 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new aeb56dc771 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 13437f498a 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new ce70ba8665 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new acf4952a5d 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 14fe69b20f 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 49238d1ffd 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 4a22260a1e 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 4d7ec07c42 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 8c95af894f 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new ed42e3b294 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 1296b8723b 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new b710f7ae3a 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 3a59526fb2 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new a59af6d692 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 09a3067098 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 70e4ffee87 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 4d9b895b52 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new e16f8245e8 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 1e46a56c9a 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 4f597f5e8e 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 2896661149 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new dec5f7ed9f 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new ebfedf9a38 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 612d3d7583 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new e20d693c66 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new ead24841f9 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new f841479a6f 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 017e875c1e 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 70c0ee67a9 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new a92840fbdd 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 8b8cb45111 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new b0fadda654 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new aa723fe685 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new b3ab81884a 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new fb6816f033 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 8b2d8141d2 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 2a4c55266a 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new ab7ec89383 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new a3caf05a23 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 4766b45fa6 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 2f4596f1e1 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 4611bacd17 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 498927b1f4 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new e54e51829c 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 8e4d849a6e 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 36cd1856f5 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new ee9e6fe360 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 5ea4a02a10 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new f4cf565d29 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 1245073110 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 8d55bfa3dd 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 67c2e94514 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new da2f3d7d7f 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 5b1fefcdbc 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 7b0adf9979 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 267c5abd57 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new ed0b6a6842 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new d77d331c95 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 7108b36d96 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 1d2d7c5e93 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 9fc8ad26bb 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new befffd0a6e 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new c1f3e18ed0 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 12a2093f9f 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 3a4cc00a65 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 46ce3e1e85 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 03371a0b77 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new bd45206f59 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 6894264b82 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 5cba6ae79d 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 0654b4c98e 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 8dd1f82600 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 57e86ad7d5 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new b723ea3e71 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 9ae6eae655 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 552b0e2d9e 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 0826ccc5f2 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 5bbeb958ac 380: onsuccess: #2631: 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 (c5d81031a0) \ 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 1764 -> 1816 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 32172 -> 31296 bytes 04-build_abe-stage1/console.log.xz | Bin 74176 -> 73232 bytes 06-build_abe-linux/console.log.xz | Bin 8576 -> 9384 bytes 07-build_abe-glibc/console.log.xz | Bin 245488 -> 244544 bytes 08-build_abe-stage2/console.log.xz | Bin 208484 -> 204400 bytes 09-build_abe-gdb/console.log.xz | Bin 39408 -> 38480 bytes 10-build_abe-qemu/console.log.xz | Bin 31544 -> 31148 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3916 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3120 -> 3124 bytes 13-check_regression/console.log.xz | Bin 8292 -> 8256 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 59 +- 13-check_regression/mail-body.txt | 124 +- 13-check_regression/results.compare | 58 +- 13-check_regression/results.compare2 | 247 +- 13-check_regression/results.regressions | 58 +- 14-update_baseline/console.log | 70 +- 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 | 126 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 58 +- sumfiles/g++.log.xz | Bin 3392096 -> 3397020 bytes sumfiles/g++.sum | 43 +- sumfiles/gcc.log.xz | Bin 3023272 -> 3028304 bytes sumfiles/gcc.sum | 4397 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1033676 -> 1037284 bytes sumfiles/gfortran.sum | 16 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217688 -> 217632 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 432660 -> 437468 bytes sumfiles/libstdc++.sum | 167 +- 43 files changed, 2924 insertions(+), 2564 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (1aeb459c20 -> 831a38087f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards 1aeb459c20 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits discards c151d4aa48 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] discards aa6819b106 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards cec0449dbc 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] discards 876e2aa180 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] discards 741640a442 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards 5bf3188d30 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] discards b0c71e2bae 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards 47711cd134 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] discards 85c18d208d 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] discards d62e8e977d 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards e9e2c3b1c8 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards bc1e381d69 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] discards 9e61e9eb28 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] discards c323c550a1 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] discards 70e9e9a791 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits discards 36a216435c 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] discards 2856dc8866 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] discards bb99a47357 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] discards a045a4972c 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] discards a65a021969 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits discards 8e9b3881c7 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits discards 311eb4880d 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] discards dc1f2678dc 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] discards 7a4fde49e4 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] discards 06d48e39f3 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards 1f48751c3f 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] discards c3017658f9 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] discards 84cd097d7a 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] discards ffbac6fb66 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 800f594f24 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] discards c32ddb406f 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] discards f4a45cf274 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards ab28dfcf18 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards fa36ddaa65 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] discards 72a909b73b 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] discards 5529fc9d0e 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards 8ee7b975e6 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] discards 843e7dfcd0 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] discards 5f9253eff8 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] discards cd8606e015 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] discards ed378fcd47 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] discards 3d9ad68599 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] discards 1edc96ea73 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] discards d091ad7841 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] discards 425641cf7c 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits discards 6b5a9bed0d 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] discards 7b2054c732 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] discards 34239a325d 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] discards 65b9a23aba 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 651a2f1c43 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards a76787f1fa 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits discards 8e0856f7a2 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] discards 440eed7cd1 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] discards 46b2459546 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] discards 589df65580 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits discards b64fd1dd20 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits discards 44887c182d 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards b13b903103 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] discards 082b771b04 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] discards bacc0a63ed 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits discards 2ca5b5ed6e 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] discards a38eb86ca4 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] discards e40478b5f3 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] discards 81e5be77d6 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits discards 2e1bbfc8a0 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] discards 1599f99523 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] discards 3a84000209 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] discards f3e458023d 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] discards 0dd8604fdf 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits discards a79fe45566 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] discards ea4b8f17e2 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits discards 71bed9f20a 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits discards 576febf411 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] discards e2da0b05a3 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] discards 7dce946ceb 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] discards 64f177ed60 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] discards 9f22244cf9 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] discards 1011f7808b 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] discards 80a504d410 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits discards 0696267b12 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] discards 8b7fc78fcc 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] discards 8758421b4a 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards e273085b90 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] discards 6d399bd569 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] discards eec96e4e83 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards 5fa094573f 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] discards 9355ed1f91 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] discards 1cf233d505 305: force: #2006: 7: Success after gdb: 2 commits discards 2edb253452 304: onsuccess: #2002: 7: Success after gcc: 4 commits discards f055afcbd6 303: onsuccess: #2001: 7: Success after binutils: 4 commits discards 28668dc616 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] discards 6ba807676d 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits discards b277f5f092 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] discards ebbe52e8e4 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] discards fed2364cc1 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits discards 440326868e 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits discards f72bc62bd7 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] discards 07e605776c 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits discards 4aa763b26c 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits discards a9860609b0 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] new 840ffc9670 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] new e835f0f0ba 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits new b40d22a435 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits new fc23d9fc67 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] new 3e186552ef 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits new d030b98bea 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits new f8fcecbfaf 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] new 9b4a54df35 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] new cbb34cf5cb 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits new 653b4db501 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] new aa4189cb45 303: onsuccess: #2001: 7: Success after binutils: 4 commits new 496fda2d1a 304: onsuccess: #2002: 7: Success after gcc: 4 commits new 75057a769b 305: force: #2006: 7: Success after gdb: 2 commits new 9ec5203fb3 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] new 1e793c6564 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] new 77967e8d8e 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new 5da302c9dd 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] new 0757f768a1 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] new 59aca8cfc3 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new 1fca64062b 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] new 1d064e4cfa 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] new 3c89db695b 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits new e22e4dc8b8 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] new 57c33ae2a3 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] new cf7b1a07c2 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] new e4b15b7284 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] new 3fe7852ab5 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] new 8da8d97d1f 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] new 9590b8d230 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits new 62c91a500a 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits new ff01ad5d33 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] new 9a398c4061 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits new 77743ea876 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] new c65b5bf377 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] new 8b15b141e0 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] new 8b7e231ad3 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] new 8b39e06ea7 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits new 342b2ee6cf 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] new e563c79196 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] new b2fc9f8da5 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] new dab2c78626 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits new 7a1b3ffde8 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] new 4bc42bd837 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] new 958c1085bb 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new 7abcc3560f 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits new b8026404b2 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits new d7060234ab 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] new 761ad70e7c 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] new 893299d088 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] new 5ecca2d42a 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits new 3e0372cf71 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new c3097cb9ae 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new 674b27c0e5 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] new dabd02fdda 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] new 36cea71734 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] new 3bc2bf373a 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits new bf89dd6b33 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] new 493c424199 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] new fc1d113871 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] new 4fa57719b6 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] new 893b8abb5a 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] new 1427003d92 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] new ad7f97036e 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] new 9eccccc1b6 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] new c876d538be 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new 7b6b16257b 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] new a2cc233cfa 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] new 55bc62c44b 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new b9255bee73 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new f70219e0a8 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] new 0f800086d1 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] new da98c7d6e5 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new 9a4eddf6aa 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] new fcd711c638 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] new 12ff301614 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] new 05d548e53a 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new 59eef42e19 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] new 8b6fdf6ca7 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] new a8097f3a6b 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] new 300929a6c8 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits new e8ec738fda 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits new 565606b912 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] new f7e6b8b91c 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] new 92fa7e081f 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] new b57e965b5d 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] new 67fd81d54f 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits new cc2cd386e4 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] new f79246f457 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] new 57a5581c74 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] new aaa99f9dfd 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new 03f88475bd 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new 7a125b1377 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] new 0c30c1b847 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] new c58275b4e1 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new ef06997550 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] new 992a55fe61 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new f3a7148a22 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] new e2affbe79a 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] new 40a1c15068 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new 767c12d404 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] new d522357f96 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits new 831a38087f 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/qem [...] 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 (1aeb459c20) \ 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 1748 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2784 bytes 04-build_abe-binutils/console.log.xz | Bin 31256 -> 31492 bytes 05-build_abe-stage1/console.log.xz | Bin 73312 -> 73336 bytes 07-build_abe-linux/console.log.xz | Bin 9396 -> 9424 bytes 08-build_abe-glibc/console.log.xz | Bin 244408 -> 245456 bytes 09-build_abe-stage2/console.log.xz | Bin 204720 -> 205032 bytes 10-build_abe-gdb/console.log.xz | Bin 38368 -> 38912 bytes 11-build_abe-qemu/console.log.xz | Bin 31044 -> 31656 bytes 12-check_regression/console.log.xz | Bin 3720 -> 4128 bytes 13-update_baseline/console.log | 62 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++++++++++----------- 20 files changed, 58 insertions(+), 58 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/gnu-arm-master-Os updated (c12e13ec87 -> 04cd344a3b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/gnu-arm-master-Os in repository toolchain/ci/base-artifacts. from c12e13ec87 50: onsuccess: #14: 1: [TCWG CI] No change after v6.1.10-455 [...] new 04cd344a3b 51: onsuccess: #15: 1: [TCWG CI] No change after binutils/gc [...] 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 1996 -> 2048 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 31088 -> 31872 bytes 04-build_abe-stage1/console.log.xz | Bin 92120 -> 93856 bytes 06-build_abe-linux/console.log.xz | Bin 8680 -> 8068 bytes 07-build_abe-glibc/console.log.xz | Bin 236068 -> 238180 bytes 08-build_abe-stage2/console.log.xz | Bin 214064 -> 216448 bytes 09-benchmark/benchmark-build.log | 106 +- 09-benchmark/benchmark.log | 104 +- 09-benchmark/console.log.xz | Bin 3840 -> 3808 bytes 10-check_regression/console.log.xz | Bin 12956 -> 15016 bytes .../csv-results-vs-first-0/md5sum.csv | 3292 +- .../csv-results-vs-first-0/results.csv | 682734 ++++++++--------- .../csv-results-vs-first-0/size.csv | 699004 ++++++++--------- 10-check_regression/csv-results-vs-first-0/sve.csv | 42 +- .../csv-results-vs-first-1/md5sum.csv | 3491 +- .../csv-results-vs-first-1/perf.csv | 3736 +- .../csv-results-vs-first-1/results.csv | 690199 +++++++++-------- .../csv-results-vs-first-1/size.csv | 706646 +++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 42 +- .../csv-results-vs-first-1/vect.csv | 40 +- .../csv-results-vs-prev-0/md5sum.csv | 3947 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 4192 +- .../csv-results-vs-prev-0/results.csv | 690449 +++++++++-------- 10-check_regression/csv-results-vs-prev-0/size.csv | 706588 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 40 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 40 +- .../csv-results-vs-prev-1/md5sum.csv | 3491 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 3736 +- .../csv-results-vs-prev-1/results.csv | 690199 +++++++++-------- 10-check_regression/csv-results-vs-prev-1/size.csv | 706646 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 42 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 40 +- 10-check_regression/results-vs-first-brief.csv | 66 +- 10-check_regression/results-vs-first-full.csv | 3754 +- 10-check_regression/results-vs-first-internal.csv | 245 +- 10-check_regression/results-vs-first.csv | 245 +- 10-check_regression/results-vs-first.log | 1080 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 35 +- 10-check_regression/results-vs-prev-full.csv | 3972 +- 10-check_regression/results-vs-prev-internal.csv | 249 +- 10-check_regression/results-vs-prev.csv | 249 +- 10-check_regression/results-vs-prev.log | 1130 +- 11-update_baseline/console.log | 8 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 16 +- .../squad-vs-first/401.bzip2/results-metadata.json | 16 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 16 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../410.bwaves/results-metadata.json | 16 +- .../squad-vs-first/410.bwaves/results-metrics.json | 2 +- .../416.gamess/results-metadata.json | 16 +- .../squad-vs-first/416.gamess/results-metrics.json | 2 +- .../squad-vs-first/429.mcf/results-metadata.json | 16 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 16 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 16 +- .../435.gromacs/results-metadata.json | 16 +- .../436.cactusADM/results-metadata.json | 16 +- .../437.leslie3d/results-metadata.json | 16 +- .../squad-vs-first/444.namd/results-metadata.json | 16 +- .../squad-vs-first/445.gobmk/results-metadata.json | 16 +- .../447.dealII/results-metadata.json | 16 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 16 +- .../453.povray/results-metadata.json | 16 +- .../454.calculix/results-metadata.json | 16 +- .../squad-vs-first/456.hmmer/results-metadata.json | 16 +- .../squad-vs-first/458.sjeng/results-metadata.json | 16 +- .../459.GemsFDTD/results-metadata.json | 16 +- .../462.libquantum/results-metadata.json | 16 +- .../464.h264ref/results-metadata.json | 16 +- .../squad-vs-first/465.tonto/results-metadata.json | 16 +- .../squad-vs-first/470.lbm/results-metadata.json | 16 +- .../471.omnetpp/results-metadata.json | 16 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 16 +- .../squad-vs-first/481.wrf/results-metadata.json | 16 +- .../482.sphinx3/results-metadata.json | 16 +- .../483.xalancbmk/results-metadata.json | 16 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 16 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 30 +- mail/mail-body.txt | 30 +- mail/mail-subject.txt | 2 +- manifest.sh | 35 +- results_id | 2 +- 95 files changed, 2804221 insertions(+), 2806455 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

Jump to page: