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 7792c15538 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 9189886a7e 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards 6d8592ca9e 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards 918690780f 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 60b6ec45c5 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards 7cfdd9ae24 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards 4eac41c889 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards eaaf013820 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 3c02c33160 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards 1208361e2e 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 66f6ac0db7 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards c0037cd2e5 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 7bab981e20 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 936fe5d70f 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 2d8bb682ca 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards f7faaf39f1 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards cc2ffb806f 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards 39b5a0880a 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards f7702c3686 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 9cb347727c 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards f4a57356a3 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards d24daa28bc 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 26641640ac 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards 8ef5371cc3 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards caabcc116b 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards 1b535d1e00 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards ab7f0a4736 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 650bcce16b 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 25bb435d93 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 21de3e66bb 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards d835ea44aa 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards deab3e5da2 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards b119bdcdf9 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards f44f22aee0 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards 4213026884 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 37bbcb7e3b 102: force: #1551: 1: Failure after gcc: 306 commits discards 1ee06eae4c 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards b30dd3b9f6 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards fcfa05963a 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 156a69686f 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 96d56a5ab9 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards f2da31d17f 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 8bc45fcb30 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards e2cfe4005d 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards c425f1af9c 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 780a1517ec 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 42dbbefaf1 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards a769ebf4b9 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards f79fb2dd11 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 3a4911eb8d 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 0e079e9eb0 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards c12731fde4 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards b29613ced9 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 48484a2aa2 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 0f255d89af 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 767dd44b4d 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 4fa58c7b57 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 75deff01ee 80: onsuccess: 7: Successful build after linux: 44 commits discards d84011c908 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards c34961423b 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards fb299a8c07 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 4faaad0b94 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 5fc08a3646 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards c38c719d58 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 216dd4e639 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 59b09a373e 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards fa35351003 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 1d3dd30b05 70: onsuccess: 7: Successful build after gcc: 4 commits discards 0067357634 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 2e06b53606 68: onsuccess: 7: Successful build after linux: 6 commits discards 1233fbf7d1 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards 28f6983aa8 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards 140361ce0d 65: onsuccess: 7: Successful build after binutils: 3 commits discards 21bd6e880d 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards cca7202b91 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 9832a04339 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards c2b51be6cf 61: onsuccess: 4: Successful build after gcc: 5 commits discards 6765a0df66 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 5d81eff450 59: force: 7: Successful build after gcc: 3 commits discards 8418c81072 58: onsuccess: 7: Successful build after glibc: 2 commits discards 8c39a9d39b 57: onsuccess: 7: Successful build after gcc: 7 commits discards 44f0dfd025 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e9de09718a 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards fed8d1a18b 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards 156be97720 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 55c750ed88 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] discards 0c602adfc9 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 265ec3786f 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c2f7887f4b 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 4c544e5de8 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards daedd8f40e 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e7fd14ca8f 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 312201073d 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d9baba9204 44: onsuccess: 7: Successful build after linux: 34 commits discards 2f19a29294 43: onsuccess: 7: Successful build after gcc: 2 commits discards 1f4b6d8244 42: onsuccess: 7: Successful build after baseline build: no [...] discards 2b2de6d02a 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 8eb2731486 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ece2677ad8 39: onsuccess: 7: Successful build after gcc: 2 commits discards 38b3317207 38: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0f9b569044 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new bdccc1b99b 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 740996e0e6 38: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ad4e801b1b 39: onsuccess: 7: Successful build after gcc: 2 commits new a5ba1f9942 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new acfad655a0 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4420461914 42: onsuccess: 7: Successful build after baseline build: no [...] new 66b33bdc30 43: onsuccess: 7: Successful build after gcc: 2 commits new c9cdaac19f 44: onsuccess: 7: Successful build after linux: 34 commits new f29245d6c7 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 431a7c1450 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 744e963d69 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 596f120822 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 8623399957 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 07c6206b6e 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2128594858 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new fd873b760b 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new d82bd9131e 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new d0ce18a4b6 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new f4da945154 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new daa8bdc555 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a4918ac0d5 57: onsuccess: 7: Successful build after gcc: 7 commits new c5d169779f 58: onsuccess: 7: Successful build after glibc: 2 commits new e680227234 59: force: 7: Successful build after gcc: 3 commits new 832353ae45 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new dd5c649626 61: onsuccess: 4: Successful build after gcc: 5 commits new b94703bd03 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new a2aae60f0d 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 38e9846c0b 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new e32de697cf 65: onsuccess: 7: Successful build after binutils: 3 commits new a26f22d97d 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 1fb48dc698 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new 215e8bbc6d 68: onsuccess: 7: Successful build after linux: 6 commits new ad0b8284c6 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 153be52499 70: onsuccess: 7: Successful build after gcc: 4 commits new 49c7074672 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 0412e72607 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e96f69b9f3 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new de2e0d05fa 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 5a7b466364 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 11f906e805 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 138b3a4084 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 414595de18 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new f8ea0e2e85 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new cc2b3d508b 80: onsuccess: 7: Successful build after linux: 44 commits new 68a7802129 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new bf7e8a6d5c 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 32a062412c 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b0cff79e4b 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 3696d36076 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new c2765984c8 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 0fde53c00e 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 811aabbd01 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 16924efb39 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 0df79264aa 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new ce232d5544 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 43bf20d391 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 1c85122c53 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 581fe03e20 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new f690748664 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 6af48816ba 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 743d613502 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 9642a8e9a0 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 29e3412fb4 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 58247fdfc9 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 18b9f420c8 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 4cb8abfdd8 102: force: #1551: 1: Failure after gcc: 306 commits new b6695b465a 103: onsuccess: #1552: 1: Success after gcc: 5 commits new b2778737b9 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 54b0467b61 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 03519f4916 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 438e3544e1 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new cc3164502d 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new 5c3f819c7f 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 3bbb423958 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 6207de6b9c 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new f05eb58fe1 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new cbccd2d449 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new 48c81a7593 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 10e921f90b 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new d10801ca03 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 46e2dc7312 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 461f30b068 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new 42cd6a67ef 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new 0e95faac07 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 30fcc07e24 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new c42f520337 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new b47be1a359 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new edae49cb73 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 59c846178e 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 3629de2afe 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 12e2cd7696 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new 5191b0a183 128: onsuccess: #1579: 7: Success after linux: 12 commits new 26a06abc74 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new 64a23a05c6 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new c18f4c13f8 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new 4739bec038 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 9850c1203f 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new da168e499d 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new b4dd046bc7 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new 7de059f12f 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new b89f162e32 137: onsuccess: #1588: 7: Success after gcc: 5 commits new cd7311b777 138: onsuccess: #1589: 7: 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 (7792c15538) \ 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 1652 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2748 bytes 04-build_abe-binutils/console.log.xz | Bin 30500 -> 30284 bytes 05-build_abe-stage1/console.log.xz | Bin 72472 -> 72412 bytes 07-build_abe-linux/console.log.xz | Bin 8776 -> 8648 bytes 08-build_abe-glibc/console.log.xz | Bin 239720 -> 240868 bytes 09-build_abe-stage2/console.log.xz | Bin 203764 -> 205444 bytes 10-build_abe-gdb/console.log.xz | Bin 38740 -> 38004 bytes 11-build_abe-qemu/console.log.xz | Bin 32560 -> 31168 bytes 12-check_regression/console.log.xz | Bin 3468 -> 4656 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +++++++++++------------ 21 files changed, 64 insertions(+), 64 deletions(-)