This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap in repository toolchain/ci/base-artifacts.
discards 0cb7121136 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits discards 18fede7dde 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits discards 7c01513734 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits discards d7d21bb819 140: onsuccess: #1545: 1: Success after gcc: 7 commits discards ea9734f4e8 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits discards 3409ee6069 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits discards 8825e6998e 137: onsuccess: #1542: 1: Success after gcc: 4 commits discards c567d0fe03 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] discards f80fe83d09 135: force: #1540: 2: Success after gcc: 23 commits discards eadbd3758c 134: onsuccess: #1538: 2: Success after binutils: 2 commits discards 92f5d3396d 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits discards e4a719f540 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits discards a86c16777f 131: onsuccess: #1534: 2: Success after gcc: 9 commits discards b560337a70 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] discards 2f44eb863e 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits discards b752851b7d 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 93a530337c 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards 5ec1e8506b 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards 0e97f7b4ac 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards 6ffd4f8f03 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards 40767e1083 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards 8e7512683c 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards e8ada16555 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards 15eb84dc7c 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards b961e47184 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards 84840fdf13 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards aea09ab6a1 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards a21ed59484 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards d0dfab3a8c 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards b4c8a66011 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 4f9577d37f 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards eef838cbef 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards 2aacfb4393 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards 555aac3a57 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards 249a4c8412 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards 0c9e1b9402 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 8eebcccbdf 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards bb5ca631eb 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards ac5d964de1 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards 5c47828b9c 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards 613f0fb932 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards babcd5680c 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards 4d74ea7f09 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards 2cf4829bf7 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards 89e95a347f 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards 74a2c23ac7 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards 9015d512e4 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 2caf1e20ab 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 6d7e5889e9 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards 489bb05f69 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards 36ec130dea 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards 6ed3ced888 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards b711a506bc 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards 36f4cb6870 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards bac41fecee 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards e29f8f687e 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards cfb0d6870b 87: onsuccess: 2: Success after gcc: 4 commits discards dc39a500b4 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards 6dca411232 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 43e7e15a35 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards ff816e1ee5 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 77604bb0d7 82: onsuccess: 1: Successful build after gcc: 3 commits discards 79a3acd00c 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 6b947c3db9 80: force: 2: Successful build after gcc: 14 commits discards 478050e90e 79: onsuccess: 2: Successful build after binutils: 5 commits discards 1fae03c2e6 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards ba007ea134 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards c063b7829b 76: onsuccess: 2: Successful build after gcc: 12 commits discards 21137a3601 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 22ecc8a809 74: onsuccess: 2: Successful build after baseline build: no [...] discards 563d460136 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 9b00a6787d 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards e273578f99 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards cb0814d755 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 002c63ba23 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards ce5942a1a9 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards dcccbafded 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards afa3ce72a2 66: onsuccess: 2: Successful build after gcc: 9 commits discards d9ef433e21 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 249e1ec5c5 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 540d48fc2c 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 7419bef8f0 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 24f606794e 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards ebfa0a38fe 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards 3981306b32 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 3e6d6a7e5a 58: force: 2: Successful build after gcc: 6 commits discards 4aab83d857 57: onsuccess: 2: Successful build after binutils: gdb: new [...] discards a67f540f64 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 5519ddb9d3 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 2d099a13d5 54: onsuccess: 2: Successful build after gcc: 5 commits discards 8744cf2bf2 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards e69f343542 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 1eb059151a 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 39ed0f5f2e 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards fe258e3a89 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 7e593de193 48: onsuccess: 2: Successful build after gcc: 4 commits discards 577ddee362 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards fb37d43dff 46: onsuccess: 2: Successful build after baseline build: no [...] discards 55ed6134a7 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards f00ff4ee7f 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards cadb70cf6e 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new 79cffd6ab1 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new b6a438178a 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 4ce5b3da00 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 9263380980 46: onsuccess: 2: Successful build after baseline build: no [...] new 0c6560e712 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 17d3d52795 48: onsuccess: 2: Successful build after gcc: 4 commits new 3f4b66066c 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new d41f5620d8 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new a21aa9635d 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 381e505ef5 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 2b96dfa5b0 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new f719665a3b 54: onsuccess: 2: Successful build after gcc: 5 commits new 9a254cc2fd 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 83f06259fb 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new b7f276562d 57: onsuccess: 2: Successful build after binutils: gdb: new [...] new be8cc9bbf3 58: force: 2: Successful build after gcc: 6 commits new dffc1c72cb 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new c5cde8a795 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 79aa12a2c5 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new 9f061bc262 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 5fc7b9b481 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new f33d56e8ef 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 30bd9fc681 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new cd1fbeebfe 66: onsuccess: 2: Successful build after gcc: 9 commits new 315a8aeebc 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new d62d28c9d3 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 072c6d9d80 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 7baa1320c6 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 7e391ec4f7 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new c17785ef2a 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new c902d6bda1 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 4d4a05878c 74: onsuccess: 2: Successful build after baseline build: no [...] new 18cd480b70 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 194459e378 76: onsuccess: 2: Successful build after gcc: 12 commits new e14c347240 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new c39a4141cf 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new 7d9474bed9 79: onsuccess: 2: Successful build after binutils: 5 commits new 18d170433a 80: force: 2: Successful build after gcc: 14 commits new a4cb5147cd 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 825fc3d054 82: onsuccess: 1: Successful build after gcc: 3 commits new 3f972c44aa 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new 51392dee26 84: onsuccess: 2: Success after binutils/gcc: 15 commits new e8e51c2669 85: onsuccess: 2: Success after binutils/gcc: 25 commits new 3fddac4ac7 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 1c498a6786 87: onsuccess: 2: Success after gcc: 4 commits new df739ddbbb 88: onsuccess: 2: Success after binutils/gcc: 25 commits new 93c8934bae 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 64eb35a1d6 90: onsuccess: 2: Success after binutils/gcc: 16 commits new f253a04f3a 91: onsuccess: 2: Success after binutils/gcc: 7 commits new cc7bac15cf 92: onsuccess: 2: Success after binutils/gcc: 9 commits new d79e444d21 93: onsuccess: 2: Success after binutils/gcc: 3 commits new da005b318a 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new 20c3bf8f87 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new 1cc548a918 96: onsuccess: #1452: 2: Success after gcc: 2 commits new cb8bd1e7b8 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new 78e1927143 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new 54e05e8186 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new f474ea0b8d 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 7578c08d4d 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new cbc1092044 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new 0d79b21f70 103: onsuccess: #1504: 2: Success after gcc: 2 commits new 57a42dd1a0 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new b602226c9d 105: onsuccess: #1506: 2: Success after gcc: 2 commits new ba64d3b8fd 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 5e7f994391 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new dfa936bf75 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 3e4ebe94e8 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new 0fb69f76c7 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new bf08f277b3 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new c9e06aaa03 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new 20e8a621bf 113: onsuccess: #1514: 2: Success after gcc: 5 commits new 46181d9550 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new fc57fa4b15 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new 06cf83fa2f 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new f5ca068cf5 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new d765674165 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new 29f7e7d16f 119: onsuccess: #1520: 2: Success after binutils: 8 commits new 5181fedd0c 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new 2f1ebef138 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new f7bdda42b0 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new 33ffbef27f 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new 6ea103485c 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new 955702ea54 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new 63a1d5b845 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new c84f3b7e03 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new 731627068e 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new fa202d359c 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits new 04ee8b91ff 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] new 293568d333 131: onsuccess: #1534: 2: Success after gcc: 9 commits new 16d8494a91 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits new 897f13f915 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits new b7229567c6 134: onsuccess: #1538: 2: Success after binutils: 2 commits new cbc9be2f3c 135: force: #1540: 2: Success after gcc: 23 commits new 0c091f4ba2 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] new cc7afb4c5d 137: onsuccess: #1542: 1: Success after gcc: 4 commits new 8482a70439 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits new 950967b874 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits new 8546209ca4 140: onsuccess: #1545: 1: Success after gcc: 7 commits new 98bf246726 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits new 312372a958 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits new d7a313edc8 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits new 8d187495bf 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 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 (0cb7121136) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...]
You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.
Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.
The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.
Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1660 -> 1660 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 50792 -> 51380 bytes 05-build_abe-bootstrap/console.log.xz | Bin 110396 -> 111700 bytes 06-check_regression/console.log.xz | Bin 2620 -> 3032 bytes 07-update_baseline/console.log | 30 +++++++++++++++--------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 13 files changed, 30 insertions(+), 30 deletions(-)