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 570ce02f4b 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 52df9a66f1 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 4e176eaf40 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 62d6233a8d 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 04170bf518 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 46f65a82ce 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards f0ade27006 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards bfd16e44d9 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 59e16aafb8 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards da000130be 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 3e15bd5fb6 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 4efd64c9c7 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 232b85ceba 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 289cb3277c 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 2e1c24e86b 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 957ba58bf8 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards e5f1682e4d 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 85d0a03403 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards b9f3d97bd4 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards c604a8d9a4 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards dc53777d86 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards c4f369d8d0 128: onsuccess: #1723: 1: Success after linux: 12 commits discards e60a4cfebf 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 66260b16de 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 62c140a10a 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards feda6cced5 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards f9dd369e53 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 2232942f49 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 5adf637d7d 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 80033c4968 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 7652f7a4d9 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 18bf013f30 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards b3b06a00d4 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards beaff14e73 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards a4099feeae 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 507908ffa8 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards d642121417 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 9dc1dda699 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 1744358d53 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 40d864c120 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 3f5589016e 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 62d009622b 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 8091b72ed2 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 9f18136107 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards bcaafceae8 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards d478bc10d7 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards aa1359c8b7 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 246335503e 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 54012e09d7 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 61ad149cb8 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards d344d64a8d 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 3ded6c973a 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards f81b0af170 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 8e83b96aa2 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 444f3b2cfb 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 05f7a6540c 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 37a3fab4c4 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards c25b899e02 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 10de729902 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards a87a196cb6 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards a598665c09 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards cf163926a9 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 2d6e809b4c 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 33a47a017c 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 71dbee2fc1 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 78943fc972 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 867899a3e1 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards f2cc2b45d3 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards e785018eb7 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards a794195b4c 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards b465e2b288 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards fff0b9ac74 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 26e10ff634 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0c3ad31c28 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards e005d35fab 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 05ab332e63 74: onsuccess: 1: Successful build after linux: 44 commits discards e7be8be677 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 84f7d183c1 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 558bf1f7ac 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards ee34af6070 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 6f516485d0 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards bda6c7d34c 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1effdfe09e 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0d0ea56fa2 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7c379500cd 65: onsuccess: 1: Successful build after gcc: 4 commits discards 6d5f2c5bd4 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b60cbd9823 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e5f9c9136d 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 925de18f72 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 3fbb992695 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 01d5b85d3a 59: onsuccess: 1: Successful build after glibc: 2 commits discards 17246d152c 58: onsuccess: 1: Successful build after binutils: 2 commits discards fd98804f7a 57: onsuccess: 1: Successful build after gcc: 7 commits discards 839729bad9 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bb994f7db3 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 043c2aafea 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards ca75dc5008 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 384a44745f 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards b33ab3a079 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b627aaa175 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 21dda0fc6f 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 87fd059afc 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b34a4ff93c 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6c4851d9c5 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 00099e56ea 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 59c29b850a 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 0c6fd883a5 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 2fffe0681f 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bb06c17286 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 818bba84e3 57: onsuccess: 1: Successful build after gcc: 7 commits new a0ab07e12f 58: onsuccess: 1: Successful build after binutils: 2 commits new 51e36cc1bd 59: onsuccess: 1: Successful build after glibc: 2 commits new e074ff7971 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 835d31095d 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new dc85d10525 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new bddac867c7 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 51b2bf706c 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 642609f3c6 65: onsuccess: 1: Successful build after gcc: 4 commits new 564cd633ed 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 8b9fb74467 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cc1bb61150 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6958d48eca 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 6ceecb7518 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 59b01a7130 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new b5aaf16e02 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b2b20b42ad 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new afc0e77016 74: onsuccess: 1: Successful build after linux: 44 commits new 2d15305894 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new aa4a4f9eda 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 6ddc1c5fc3 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d5ff1c9d97 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 54d07d776e 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 6fc45e3aa3 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new e6bd18213c 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 2933b505b0 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 8fe15a0c0c 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 90e0996b88 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 26bd683491 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 63da97653a 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new ab1b248fdb 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 2e25d0c796 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 79154a537c 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new b372f347f1 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new de72ecea99 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new f47b979cbc 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 88c1b85c0e 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new c48b015212 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 193935ddb9 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new c3fb8eaba5 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new d37f0b758c 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 33b39abf66 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new d2b827105f 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new cff1b9c2f6 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 2eb5875d9e 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 9db737ff43 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new f292704a0f 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new e51dce9c94 104: onsuccess: #1697: 1: Success after gcc: 4 commits new ecda3331fd 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new c0fd022f11 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 6fdbc67ca5 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 6cd8175017 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 92af2765eb 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 07dc331bec 110: onsuccess: #1703: 1: Success after gcc: 6 commits new ab2848b45c 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 1639a573d7 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 7a4c8af082 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 65c40aea67 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 73096b6c9a 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 99e70b99d1 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 7c7e41e0c9 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new a6e086d4f8 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new e9d6b24a7c 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new f6499222e1 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new b153967597 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 7b1e4c33bb 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 0176eb0cab 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 5d8d8d8b1d 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 1ab787969e 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new efdc0c5110 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new de9111dd1a 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 6dca6aaacb 128: onsuccess: #1723: 1: Success after linux: 12 commits new 6b0db4273c 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new c8163e6e46 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new e57bff34f6 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 1403e301ba 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 91eec19290 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new c9da380fd6 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 793b025dc5 135: onsuccess: #1733: 1: Success after binutils: 5 commits new d05b4eaca9 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 0095cbf25f 137: onsuccess: #1736: 1: Success after gcc: 5 commits new bb829aac99 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new f2b648fb9d 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 5f5063c716 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 2a722f4fca 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 054b1d2182 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 30313766d4 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 5d927d71c6 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 7d001a576d 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 45da3cd9b8 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 7f1fcb1aa4 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new b89ad94942 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new c4f36cb77c 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 5ff743c5b3 150: onsuccess: #1749: 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 (570ce02f4b) \ 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 1732 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 29912 -> 30156 bytes 04-build_abe-stage1/console.log.xz | Bin 91120 -> 91196 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8464 -> 8676 bytes 07-build_abe-glibc/console.log.xz | Bin 233632 -> 233600 bytes 08-build_abe-stage2/console.log.xz | Bin 223696 -> 225056 bytes 09-build_abe-gdb/console.log.xz | Bin 37252 -> 37416 bytes 10-build_abe-qemu/console.log.xz | Bin 31988 -> 31468 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3892 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3156 -> 3148 bytes 13-check_regression/console.log.xz | Bin 6496 -> 7736 bytes 13-check_regression/fails.sum | 3 +- 13-check_regression/mail-body.txt | 65 +- 13-check_regression/results.compare | 39 +- 13-check_regression/results.compare2 | 268 +++- 13-check_regression/results.regressions | 39 +- 14-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 67 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 39 +- sumfiles/g++.log.xz | Bin 2694152 -> 2658932 bytes sumfiles/g++.sum | 266 ++-- sumfiles/gcc.log.xz | Bin 2209208 -> 2203868 bytes sumfiles/gcc.sum | 2394 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 880904 -> 887140 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201412 -> 201608 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 425084 -> 429464 bytes sumfiles/libstdc++.sum | 23 +- 44 files changed, 1878 insertions(+), 1497 deletions(-)