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 ecafc414dd 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 1df35921e5 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 6697c9623a 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 4b4c9b7ce8 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 2da93c514b 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 074ae5a59d 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 6d0dc37751 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards ad7047889d 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards ff50a187d3 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 72cca13661 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 1044c1a0e5 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 8aa951a37e 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards a83ddbae52 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 1e656048fc 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards b849b2f44e 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 21c52ad36c 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards d65c66311a 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 23e85aff34 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 7e3adfbcb9 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards e7b7493690 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 84bf42db5e 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards fb83898960 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 0d5045e104 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards dec8e033e1 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 8a6b446bf7 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 1ec1f55daa 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 0e154df4f1 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 4b2cb79166 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards ae231a65f3 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards cffbadc61a 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 4811a72de1 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards c6c0e8cd5c 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards db7c516e4a 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 2cc69b080e 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards df28a73a4e 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards ec98b8653a 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 557a183705 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 4d3fe9fe4b 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 7b4dfaf1f8 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 9a3b5430cd 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 273cdf6382 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 35af870548 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards f0078f3026 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 0c55d6f243 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 8c09d960fa 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 0e5fd0c817 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards e508c0d157 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 2677feccab 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 2daae6b96d 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 6f664ea9f6 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 5d2d8edb39 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards fdb33a2186 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 4f0bf57047 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards fb1a281379 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 60a0431366 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 03c1389e21 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0905b09dd1 74: onsuccess: 1: Successful build after linux: 44 commits discards 50fc9d3711 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 07a7ba7a56 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b2910842b1 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards e394e875b6 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 2fcb355a8e 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards ae56273fe4 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 53b4629172 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6cb0a62fd4 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c6e937f529 65: onsuccess: 1: Successful build after gcc: 4 commits discards f7a6dc9008 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1c9631906c 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c229702f1b 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards b8a7a25760 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards aacc4e5ae6 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 083fcb7623 59: onsuccess: 1: Successful build after glibc: 2 commits discards f7b3f02bf7 58: onsuccess: 1: Successful build after binutils: 2 commits discards ebcef19bfc 57: onsuccess: 1: Successful build after gcc: 7 commits discards 024417f60e 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 79a1ebd7f3 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5c85427cac 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 789e1d5906 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards d42c7e5879 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards dc08955d4b 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 05b547f523 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b41786864f 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f7da76ac15 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 818ef28b34 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e07301b0c7 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 3eb48879c6 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 193c50b5ab 44: onsuccess: 1: Successful build after linux: 34 commits discards 2b05f0c2a5 43: onsuccess: 1: Successful build after gcc: 2 commits discards 32ddef2b62 42: onsuccess: 1: Successful build after baseline build: no [...] discards 0fd014a920 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3588de45bc 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f9bf61470f 39: onsuccess: 1: Successful build after gcc: 2 commits discards 092a8d59f9 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d2749e0e0a 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0eacda666f 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d30516ef0c 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e2be69d981 34: onsuccess: 1: Successful build after gcc: 3 commits discards 0ee43e11bb 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7a863b7269 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 394268c90b 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 410b227e87 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new dc9c71c00f 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 07996cf9d3 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0727adf3cc 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new b4404b15bd 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e232137c1e 34: onsuccess: 1: Successful build after gcc: 3 commits new 48ac4c6980 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 03811c5634 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b4a40cbf0a 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d457a7aa23 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6864e6f436 39: onsuccess: 1: Successful build after gcc: 2 commits new a608605ab6 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 909ff62bba 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ab692564ed 42: onsuccess: 1: Successful build after baseline build: no [...] new eb6b17a89a 43: onsuccess: 1: Successful build after gcc: 2 commits new ed5d51cdaf 44: onsuccess: 1: Successful build after linux: 34 commits new 651c11857e 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 93361ddc1f 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 706ee75753 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 799671cf6a 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 69cb5a8a30 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c110fa40ab 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 50aa5b1746 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new da8a525772 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new a0d5057754 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new eeac610967 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 05f320dfe7 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b54afb5f9b 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7824adbcdd 57: onsuccess: 1: Successful build after gcc: 7 commits new 3ca387a528 58: onsuccess: 1: Successful build after binutils: 2 commits new 6e35ac5c8f 59: onsuccess: 1: Successful build after glibc: 2 commits new f94a6fc299 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 3a51591400 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new d541c6af21 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 75db1be36e 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6dd04b81d7 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 982074f803 65: onsuccess: 1: Successful build after gcc: 4 commits new b8ed6c4ef2 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 8d4e989dba 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2056e97bcb 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 97d4af1919 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 87dfec1baa 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 87f3729cd0 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 13314d2091 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0ef3024c2c 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 08405f57e6 74: onsuccess: 1: Successful build after linux: 44 commits new 57ef8a38a6 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 69109d7030 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 1108230c82 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 30ff581014 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c04aa6dbfc 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new baa6f69a7b 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new b96c1f8c90 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 73ec75fb88 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 8f82d97a2c 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new c9c950bd47 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 61368d3e0c 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new cdab33c5db 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 4b73727b8b 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 3d1d629559 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 1e2812df5f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new c733a579a1 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 2060606aa2 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new f4cde1b291 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 082d4b49b3 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 73d8d46d15 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new a84c53ed42 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new d37039416c 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 095278b8f4 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 120c0ebd1a 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 914decab46 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 551c7be5b9 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new a8e8ccf591 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 7c08dfe9d7 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 9c81e0e52b 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new a8160844ae 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 5c7496fb4d 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new e4168c6c21 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new b1cbe0fc5c 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new a1de7ff7ee 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 084da64930 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 8207c1bc71 110: onsuccess: #1703: 1: Success after gcc: 6 commits new c46f23b881 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 3093f364d7 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new e71943e0e7 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 786645428b 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 88f5238127 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new a2fdd841a8 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 5824033dfb 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new e0c5e59d6f 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 8ee473f5c7 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 19cd4de165 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new a2831576b7 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 9251a2792c 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new fe3ad7e747 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 14039e2a11 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new a9147d9e7b 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new ed5012b5b9 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 709a0f26bd 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new fdbb2dff2f 128: onsuccess: #1723: 1: Success after linux: 12 commits new 5485f06e00 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new e15d57c6a5 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new e6d3640795 131: onsuccess: #1726: 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 (ecafc414dd) \ 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 1772 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 29904 -> 29992 bytes 04-build_abe-stage1/console.log.xz | Bin 91260 -> 90388 bytes 06-build_abe-linux/console.log.xz | Bin 8956 -> 8312 bytes 07-build_abe-glibc/console.log.xz | Bin 234196 -> 233636 bytes 08-build_abe-stage2/console.log.xz | Bin 224268 -> 222660 bytes 09-build_abe-gdb/console.log.xz | Bin 37136 -> 37224 bytes 10-build_abe-qemu/console.log.xz | Bin 31040 -> 30944 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3848 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2888 -> 2424 bytes 13-check_regression/console.log.xz | Bin 6924 -> 5336 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 261 +--- 14-update_baseline/console.log | 60 +- 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 | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.xz | Bin 2659916 -> 2659608 bytes sumfiles/g++.sum | 38 +- sumfiles/gcc.log.xz | Bin 2213044 -> 2197864 bytes sumfiles/gcc.sum | 2092 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 882136 -> 881268 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201260 -> 201268 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 426372 -> 426076 bytes sumfiles/libstdc++.sum | 2 +- 39 files changed, 1141 insertions(+), 1456 deletions(-)