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 8d187495bf 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits discards d7a313edc8 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits discards 312372a958 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits discards 98bf246726 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits discards 8546209ca4 140: onsuccess: #1545: 1: Success after gcc: 7 commits discards 950967b874 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits discards 8482a70439 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits discards cc7afb4c5d 137: onsuccess: #1542: 1: Success after gcc: 4 commits discards 0c091f4ba2 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] discards cbc9be2f3c 135: force: #1540: 2: Success after gcc: 23 commits discards b7229567c6 134: onsuccess: #1538: 2: Success after binutils: 2 commits discards 897f13f915 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits discards 16d8494a91 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits discards 293568d333 131: onsuccess: #1534: 2: Success after gcc: 9 commits discards 04ee8b91ff 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] discards fa202d359c 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits discards 731627068e 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards c84f3b7e03 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards 63a1d5b845 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards 955702ea54 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards 6ea103485c 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards 33ffbef27f 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards f7bdda42b0 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards 2f1ebef138 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards 5181fedd0c 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards 29f7e7d16f 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards d765674165 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards f5ca068cf5 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards 06cf83fa2f 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards fc57fa4b15 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards 46181d9550 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 20e8a621bf 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards c9e06aaa03 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards bf08f277b3 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards 0fb69f76c7 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards 3e4ebe94e8 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards dfa936bf75 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 5e7f994391 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards ba64d3b8fd 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards b602226c9d 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards 57a42dd1a0 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards 0d79b21f70 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards cbc1092044 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards 7578c08d4d 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards f474ea0b8d 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards 54e05e8186 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards 78e1927143 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards cb8bd1e7b8 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 1cc548a918 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 20c3bf8f87 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards da005b318a 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards d79e444d21 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards cc7bac15cf 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards f253a04f3a 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards 64eb35a1d6 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards 93c8934bae 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards df739ddbbb 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards 1c498a6786 87: onsuccess: 2: Success after gcc: 4 commits discards 3fddac4ac7 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards e8e51c2669 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 51392dee26 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 3f972c44aa 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 825fc3d054 82: onsuccess: 1: Successful build after gcc: 3 commits discards a4cb5147cd 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 18d170433a 80: force: 2: Successful build after gcc: 14 commits discards 7d9474bed9 79: onsuccess: 2: Successful build after binutils: 5 commits discards c39a4141cf 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards e14c347240 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 194459e378 76: onsuccess: 2: Successful build after gcc: 12 commits discards 18cd480b70 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 4d4a05878c 74: onsuccess: 2: Successful build after baseline build: no [...] discards c902d6bda1 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards c17785ef2a 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 7e391ec4f7 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 7baa1320c6 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 072c6d9d80 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards d62d28c9d3 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 315a8aeebc 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards cd1fbeebfe 66: onsuccess: 2: Successful build after gcc: 9 commits discards 30bd9fc681 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards f33d56e8ef 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 5fc7b9b481 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 9f061bc262 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 79aa12a2c5 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards c5cde8a795 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards dffc1c72cb 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards be8cc9bbf3 58: force: 2: Successful build after gcc: 6 commits discards b7f276562d 57: onsuccess: 2: Successful build after binutils: gdb: new [...] discards 83f06259fb 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 9a254cc2fd 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards f719665a3b 54: onsuccess: 2: Successful build after gcc: 5 commits discards 2b96dfa5b0 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 381e505ef5 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards a21aa9635d 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards d41f5620d8 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 3f4b66066c 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 17d3d52795 48: onsuccess: 2: Successful build after gcc: 4 commits discards 0c6560e712 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 9263380980 46: onsuccess: 2: Successful build after baseline build: no [...] discards 4ce5b3da00 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards b6a438178a 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new c7debf78e8 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new d101dfc6d2 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 9f80016f1e 46: onsuccess: 2: Successful build after baseline build: no [...] new 0a8e4ad195 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits new b18875c449 48: onsuccess: 2: Successful build after gcc: 4 commits new 9149c4bd51 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new cd4715d929 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new db814157a9 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 8be81dddc4 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 257f8ba30b 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 9beff6f3e9 54: onsuccess: 2: Successful build after gcc: 5 commits new 060fbe79ce 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 01352dfdd0 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new e14d5d94d0 57: onsuccess: 2: Successful build after binutils: gdb: new [...] new 60727f43ec 58: force: 2: Successful build after gcc: 6 commits new b23567c402 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 8a18d0ff57 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 50a084f395 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new 6ebc0e678c 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new bf7792f53a 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 98512795d2 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 88e827ea8d 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 8c94a3bfdc 66: onsuccess: 2: Successful build after gcc: 9 commits new a9561b32fa 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 83fcd6595a 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 2cacaa3123 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 3af998297d 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 011aa66f8f 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 3688a2a0c0 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 338f47b194 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 980bd232cd 74: onsuccess: 2: Successful build after baseline build: no [...] new b119b8019e 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 3962942472 76: onsuccess: 2: Successful build after gcc: 12 commits new b3eb998a35 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 137c0618c0 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new d4d961c305 79: onsuccess: 2: Successful build after binutils: 5 commits new 31f2aa500c 80: force: 2: Successful build after gcc: 14 commits new 53b056092c 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 633cafa317 82: onsuccess: 1: Successful build after gcc: 3 commits new 7195d91775 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new 1a13cdd30c 84: onsuccess: 2: Success after binutils/gcc: 15 commits new d7a2858538 85: onsuccess: 2: Success after binutils/gcc: 25 commits new ba82fc5bfc 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 7baa5547bf 87: onsuccess: 2: Success after gcc: 4 commits new e0406187df 88: onsuccess: 2: Success after binutils/gcc: 25 commits new a56e017864 89: onsuccess: 2: Success after binutils/gcc: 4 commits new ef3566c8f2 90: onsuccess: 2: Success after binutils/gcc: 16 commits new 606726f2f2 91: onsuccess: 2: Success after binutils/gcc: 7 commits new c215daa329 92: onsuccess: 2: Success after binutils/gcc: 9 commits new a74bdf2ee0 93: onsuccess: 2: Success after binutils/gcc: 3 commits new aa15ac5978 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new 5346c23b6e 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new 47e0ad8f1d 96: onsuccess: #1452: 2: Success after gcc: 2 commits new cac97a60a1 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new bdb82ccd81 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new 67345f00f9 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new 89858fb943 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 929d1d07b7 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new 625a4d54c1 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new 0a483367d8 103: onsuccess: #1504: 2: Success after gcc: 2 commits new f82e0d5681 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new 5940289390 105: onsuccess: #1506: 2: Success after gcc: 2 commits new 63fb2994be 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 7fe683f38c 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new 53fe16f06d 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 826e704351 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new e591fe8a03 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new ee8b70dbb7 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new ba7bb7c121 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new 0b7e179396 113: onsuccess: #1514: 2: Success after gcc: 5 commits new 8c5acdb23f 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new 41165c04de 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new bbc6922d43 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new 51ca5f14f9 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 42f474eb54 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new a6b217ad02 119: onsuccess: #1520: 2: Success after binutils: 8 commits new 4c638b221a 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new 9f41f5c1b2 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new 51b506434b 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new d4446a9351 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new 9869e93cc9 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new 99198d6b09 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new 9fafe3d275 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new 9ae584c84c 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new d17853eb7a 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new d50d69df6a 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits new 25a3eafc40 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] new 311dff2f9d 131: onsuccess: #1534: 2: Success after gcc: 9 commits new 3b21bbc36e 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits new 940b326fd2 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits new 7cf0632137 134: onsuccess: #1538: 2: Success after binutils: 2 commits new b0289eef0e 135: force: #1540: 2: Success after gcc: 23 commits new 4892af99a8 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] new b3bf804c10 137: onsuccess: #1542: 1: Success after gcc: 4 commits new 902a812ee0 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits new 6defc9fec6 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits new a51e61b7d6 140: onsuccess: #1545: 1: Success after gcc: 7 commits new b295598339 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits new 08118e22a5 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits new a432206a91 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits new b19b85984d 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits new 1008ae9026 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 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 (8d187495bf) \ 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 51380 -> 51624 bytes 05-build_abe-bootstrap/console.log.xz | Bin 111700 -> 112108 bytes 06-check_regression/console.log.xz | Bin 3032 -> 2948 bytes 07-update_baseline/console.log | 28 ++++++++++++++-------------- 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, 29 insertions(+), 29 deletions(-)