Tcwg-commits November 2022

tcwg-commits@lists.linaro.org

5 participants
4683 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-next-allmodconfig updated (7b6f246d6e -> 0d8ecde7e0)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-next-allmodconfig in repository toolchain/ci/base-artifacts. from 7b6f246d6e 26: onsuccess: #572: 33: Success after binutils/gcc/linux/qe [...] new 0d8ecde7e0 27: onsuccess: #573: 33: Success after binutils/gcc/linux/qe [...] The 1 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 1692 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 31584 -> 31704 bytes 04-build_abe-stage1/console.log.xz | Bin 91536 -> 91572 bytes 05-build_abe-qemu/console.log.xz | Bin 30232 -> 30644 bytes 06-build_linux/console.log.xz | Bin 4732 -> 4728 bytes 08-check_regression/console.log.xz | Bin 4400 -> 4380 bytes 09-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_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 | 32 ++++++++++++++++---------------- 17 files changed, 33 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-defconfig updated (0842583dd5 -> f62ace3b88)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-defconfig in repository toolchain/ci/base-artifacts. from 0842583dd5 22: onsuccess: #472: boot: Success after binutils/llvm/linux [...] new f62ace3b88 23: onsuccess: #473: boot: Success after binutils/llvm/qemu: [...] The 1 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 1712 -> 1908 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 31744 -> 31948 bytes 04-build_kernel_llvm/console.log.xz | Bin 66404 -> 66872 bytes 05-build_abe-qemu/console.log.xz | Bin 30588 -> 31364 bytes 06-build_linux/console.log.xz | Bin 3492 -> 3484 bytes 07-boot_linux/console.log.xz | Bin 6056 -> 6060 bytes 08-check_regression/console.log.xz | Bin 4348 -> 3940 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 17 files changed, 25 insertions(+), 25 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (ebba09a1db -> 2bba27d644)

by git＠git.linaro.org

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 ebba09a1db 190: onsuccess: #1774: 7: Success after binutils: 10 commits discards d655170eeb 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 37 [...] discards eced300939 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/g [...] discards b3b606e279 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/g [...] discards fffdc85c80 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/g [...] discards 559be17635 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] discards 26cf00adc9 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/g [...] discards 0871966a29 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/g [...] discards ba94c44ee4 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/g [...] discards 4b550025d4 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/g [...] discards d30c80ab33 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] discards d02f61dfb7 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards 99881c91bd 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/g [...] discards 78cc1002e6 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards f79cd4971f 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/g [...] discards 383f06ae11 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/g [...] discards c96cbf3365 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 15 [...] discards fdfcfa1284 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 42019bf7a3 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qemu [...] discards 066b55a3f0 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 12 [...] discards 55aac66748 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/g [...] discards 7ccb7ba56f 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/g [...] discards b9826b9f32 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/g [...] discards 51649edf9a 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 28 [...] discards 6474c7fcb5 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits discards fa3d937a4d 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/g [...] discards ee90427c3f 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/g [...] discards 606f4bcb57 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 12 [...] discards 9eca34566e 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 commits discards 2f9e669286 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/g [...] discards 82d5079c52 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 38ddf54297 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards 58180a5bd6 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] discards aa75fe2631 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards 7ff58b4490 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards ccba490cc3 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] discards 6eb61e1ef3 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards 596be5245e 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] discards cb657a59e4 152: force: #1605: 7: Success after gcc: 9 commits discards fd6611661b 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] discards 5186c77a02 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] discards b388b2e07d 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards 20cc04d456 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards e5a46d9d8e 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards 3bf3a4e65e 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards 990e53a266 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards b7ad35dede 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 6472aec326 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards 182291216e 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards 959cd7f6f0 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 4a092301a5 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards 8c53d2ad03 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards 6705ae4ebe 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards c175c6cce8 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 0e8cdebaad 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards a6bc820703 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards 91cfd9a522 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 5c792f3a04 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards 5e38f8d6b6 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards 0eea49ef1e 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 269b63841b 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards cc0a1f1597 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards 2c95a9df19 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 0521c93012 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 69b7ce8c72 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 6eafd7dcfb 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 656689e6c9 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 2df262f3ae 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards be6b96120f 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 678b39627f 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards 4ababd062f 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards 1d69dedce3 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 35edd281ea 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards 8e95d100c6 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards ba8fd6080c 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards ed2c10d07a 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards 449317b8cc 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards 02ac86bbda 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards eea7619df1 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards e36d39e502 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 720b612160 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 36e9c34086 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 1aed4ebc59 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards cd25c40ddd 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 181476e6f8 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards c68efe9db4 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards 643b6fa9ea 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards cbdeb41e1d 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 83d7fdcd98 102: force: #1551: 1: Failure after gcc: 306 commits discards bcab96f158 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 9dd1df0183 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 1b87ddecee 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 8f7a368bb7 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards fa31625c20 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards e0d1aec36d 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 42974a83be 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards d8a99d707f 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards db14cbcbf3 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards fea71b8b2c 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards fddc35c537 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards bf827cfb95 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 52f6290f9e 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 4c8fc32988 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new cf3915b955 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new ccd64bf31a 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 8bd6bb8052 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 413a33b9e2 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new a3292c12ab 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 21ac00d80a 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 9e62a2cd96 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 855c257589 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 2d3c059442 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new e96d21c688 101: onsuccess: #1547: 7: Success after binutils: 82 commits new e9e7176f06 102: force: #1551: 1: Failure after gcc: 306 commits new 34c8e4b375 103: onsuccess: #1552: 1: Success after gcc: 5 commits new b27686a40d 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 3a9ad60fd9 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 562fe58678 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 28cf853378 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new 14b51d12b0 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new 50ff88aa11 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new f691bddb9c 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 279a250cba 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new be9ecbc4cb 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 2c0217ca11 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new e00869087a 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new f6b082f990 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 9d13770d1a 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 72a50c390e 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 70d7c5b571 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new e6ce996e9f 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new 7fa0579ba7 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 3f4d963df4 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new c8cbd7df83 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new b533bb14b9 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new 0047da4d11 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 75fb7d2144 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new ab7c339da7 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 2e4c35a7ff 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new 04043b6e5f 128: onsuccess: #1579: 7: Success after linux: 12 commits new f86893f207 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new 7d16046139 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new a3f5d307e8 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new d6313430fc 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 422ed134d2 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new ef0461ac56 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new 8e54b0f09f 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new 6e2096d24c 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new a0da331c92 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 7007440f19 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new 0168a1822f 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 4929758594 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new e407657d5e 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new fe196725d5 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new d8071634cb 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new e3513e31dc 144: onsuccess: #1595: 7: Success after glibc: 2 commits new db9187ea66 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new 16219aef03 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new 9dafee2802 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new 1e5777debf 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new 95b7a69051 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new a9455ae67a 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] new 2f1c72feea 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] new 37861c45c6 152: force: #1605: 7: Success after gcc: 9 commits new ad74ee038f 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] new f7514d4aa6 154: onsuccess: #1607: 1: Success after gcc: 2 commits new 634a508d52 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] new 1fe0a64945 156: onsuccess: #1609: 7: Success after gcc: 2 commits new ac837ccc79 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new c3228c292d 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] new 4027706a19 159: onsuccess: #1612: 7: Success after gcc: 4 commits new f33033945c 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 3ba1ea510e 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/g [...] new 57d7ec3d4d 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 commits new 14bbd5410a 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 12 [...] new 9a6bf78297 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/g [...] new 2b5ae3e7ac 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/g [...] new cc2a8f3fc6 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits new 8489cfaaa4 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 28 [...] new 8348000655 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/g [...] new ab516c9303 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/g [...] new a335fb1731 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/g [...] new 8d2a11b7e1 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 12 [...] new 5f22e3bda0 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qemu [...] new 75697008b7 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 0b090b4f9a 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 15 [...] new 9433dea2cf 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/g [...] new 7735d294a8 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/g [...] new f0cc6f2c3f 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 23c1cae5ea 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/g [...] new 3c4c80c199 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 3b88b59b24 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] new 159d4064aa 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/g [...] new fc36c44790 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/g [...] new 6da99c523a 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/g [...] new 8720a4d9b1 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/g [...] new 02e94a26f0 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] new 4f2b277d03 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/g [...] new daf6e4a66d 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/g [...] new 1b7631ff2d 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/g [...] new ae26f9a271 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 37 [...] new 820c7eefc9 190: onsuccess: #1774: 7: Success after binutils: 10 commits new 2bba27d644 191: onsuccess: #1808: 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 (ebba09a1db) \ 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 1632 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30260 -> 32120 bytes 05-build_abe-stage1/console.log.xz | Bin 71884 -> 73616 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 9748 -> 8656 bytes 08-build_abe-glibc/console.log.xz | Bin 244236 -> 243580 bytes 09-build_abe-stage2/console.log.xz | Bin 202332 -> 204476 bytes 10-build_abe-gdb/console.log.xz | Bin 38644 -> 39340 bytes 11-build_abe-qemu/console.log.xz | Bin 31496 -> 31220 bytes 12-check_regression/console.log.xz | Bin 3052 -> 5488 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ 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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 45 +++++++++++++----------- 23 files changed, 67 insertions(+), 62 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (668ba4031a -> 1db64a02af)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 668ba4031a 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards 48972e4794 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards dc8c26ee60 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 1a8da83d40 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 8e5cabc6d0 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards a813ee454d 103: onsuccess: #589: 1: Success after binutils: 3 commits discards fb001163cc 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 70e0aaa658 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 1d95a0b1f7 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards cb26254986 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 89f1d325f9 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 09d7fc3674 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 8b9bb52389 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 929f839c27 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 9e37d22a2a 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards b498f589c8 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards e912af799b 92: onsuccess: #575: 1: Success after linux: 34 commits discards 55b05114cd 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 9b6cbe95f6 90: onsuccess: #572: 1: Success after binutils: 15 commits discards d0374efbc6 89: onsuccess: #570: 1: Success after linux: 11 commits discards 4c0d27f88e 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 2c56672076 87: onsuccess: #567: 1: Success after binutils: 8 commits discards b09efb9075 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 71b477fb8b 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards eba248d942 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 56c2be42c9 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards da52189e18 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards f7263bc448 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 489f47bc01 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 23a2e44bf0 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards d5b1c68dc0 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 0ee12b00b8 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 7c0db87b2a 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 6a9277b000 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 4f9075ccbf 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 4476589738 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards d2bc750403 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 7959fab7d9 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 6811b2353b 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards b9f5146236 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 4aa6da2055 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards e5b09a01b1 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards f37f0006c0 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 57762032cd 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 5d93d24849 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards c592ae3551 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 6fe6103c1a 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards f2da2285a4 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 9bd0b32d6d 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards 1459ee8e2f 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards eb962c875f 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 9e94cad1cf 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards b350f5abe6 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards b96dee6e3a 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 422e84d29a 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards ac7367f427 53: onsuccess: #531: 1: Success after binutils: 12 commits discards ceaec79148 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 480b2a41f2 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 13cc3ea22e 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards b5e8a7f26f 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards 2f294dbc58 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards b121a93594 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards 79d8eac418 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 5da6d10f34 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards be011e853a 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 76dc2b55db 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 0d0f247b1c 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] discards 2066cba80d 41: onsuccess: #514: 1: Success after linux: 64 commits discards 8e0b9ba28d 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] discards 71ba9f66bc 39: onsuccess: #511: 1: Success after binutils: 8 commits discards fa4de52c0a 38: onsuccess: #508: 1: Success after binutils: 3 commits discards 48bce7cd1d 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards e5fd55e5eb 36: onsuccess: #505: 1: Success after glibc: 3 commits discards cc65699a93 35: onsuccess: #503: 1: Success after binutils: 11 commits discards ae53fc446d 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 9e23ef111b 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] discards 751d16c613 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 1f7a28ac47 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards a0a79c33c5 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards df8a006f6c 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 33c9a812fa 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] discards 0a30f713d8 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 52de82f9db 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] discards 8be5b1effa 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 5b490c5a82 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards b5ed8468c6 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 50eb77d410 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards f81e4f9caa 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 45058311d9 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5a58cd66cc 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7bf6175d66 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c166289066 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b5fa12a764 16: onsuccess: 1: Successful build after binutils: 4 commits discards 5439856d79 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9296b48aa9 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fbeb692901 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9e3940b400 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 713c59108f 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9dd5d35ea3 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 69ed808efa 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 36b95f2a69 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 40fb1bf161 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 8c101959b5 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 882d06af1b 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 26976d2de2 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b30ad4917b 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9c10596442 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bfb3591caa 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f84c288d9b 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1cef97e362 16: onsuccess: 1: Successful build after binutils: 4 commits new e6611c13a6 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 748ee7127f 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3aaf26bc43 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2ab426bbbb 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2e02857576 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9768167bcd 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 793c3b9f00 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 080c782ca8 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 57aa099be6 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new fe5fdfa37b 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] new 16a4b71669 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 225975314d 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] new 56833249d0 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new d9c536e863 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 38a647b797 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 301cab0452 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 807204a254 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] new 7cba5ea981 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new a7cdf91d38 35: onsuccess: #503: 1: Success after binutils: 11 commits new 7b0937bf56 36: onsuccess: #505: 1: Success after glibc: 3 commits new cbaf8e8df9 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 69e603fe57 38: onsuccess: #508: 1: Success after binutils: 3 commits new bbf2398618 39: onsuccess: #511: 1: Success after binutils: 8 commits new b7ca127724 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] new 01c16e7eea 41: onsuccess: #514: 1: Success after linux: 64 commits new f896b373fc 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new f47dd08111 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 8ed26f9507 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 98a5c97c67 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new 16472ff5fc 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 79c607dbb6 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new 4db44fe2cc 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new e8760df85d 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 17ada6ed53 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new 0b5978d88c 51: onsuccess: #525: 1: Success after binutils: 8 commits new 8846d48533 52: onsuccess: #528: 1: Success after binutils: 8 commits new b4f589b3a9 53: onsuccess: #531: 1: Success after binutils: 12 commits new 228c054662 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new fbe9814725 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 97cc6990e7 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new bed488e230 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new f4cfb86f7d 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new f0bd63a404 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 54dc7260d9 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new e86747475d 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 58a77e215b 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 243437c8f8 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new bd67b66e82 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 9d50b8cb04 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new e51b519ebd 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new cf7d2a634b 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new d25cdb621a 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new 381ac54d34 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 04a96fde0d 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new e61af1e346 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 19b439838d 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 3675f85b4c 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new c64a2bc467 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 9a15afda29 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new cf405d861d 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new e069523b1d 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 3a72da97cf 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new be54025432 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 64aa0eff37 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new b764b18091 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 30feb48159 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new e54c5965c8 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new a54836e705 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new e1adc67761 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 3fdff7de0e 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 06e4151a31 87: onsuccess: #567: 1: Success after binutils: 8 commits new 1ff95332fd 88: onsuccess: #569: 1: Success after glibc: 10 commits new 4c9610c6f2 89: onsuccess: #570: 1: Success after linux: 11 commits new 3ba3513f0e 90: onsuccess: #572: 1: Success after binutils: 15 commits new f090e05c55 91: onsuccess: #574: 1: Success after glibc: 3 commits new 3ccfbd1509 92: onsuccess: #575: 1: Success after linux: 34 commits new a684c298e2 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new f3802c3136 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 4cb80171ac 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 7851e66b47 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 4f420a60bc 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 938c0d94ab 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 3357bee18b 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 4f142a7956 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 1aca64c9eb 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 3ce1638fb5 102: onsuccess: #586: 1: Success after binutils: 5 commits new 2a2a53494f 103: onsuccess: #589: 1: Success after binutils: 3 commits new 22247ffede 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new ce979a325d 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 7bff75c2c3 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new dc5e78cb99 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 5b7b5cc73c 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 1db64a02af 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] 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 (668ba4031a) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] 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 1680 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 53412 -> 53764 bytes 04-build_abe-gcc/console.log.xz | Bin 236148 -> 237608 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8584 -> 8648 bytes 07-build_abe-glibc/console.log.xz | Bin 235844 -> 235828 bytes 08-build_abe-gdb/console.log.xz | Bin 51736 -> 52356 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3884 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2276 -> 2580 bytes 11-check_regression/console.log.xz | Bin 15036 -> 10332 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 111 +- 11-check_regression/mail-body.txt | 190 +- 11-check_regression/results.compare | 162 +- 11-check_regression/results.compare2 | 1196 +----- 11-check_regression/results.regressions | 122 +- 12-update_baseline/console.log | 40 +- 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 | 192 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 122 +- sumfiles/gdb.log.xz | Bin 1790664 -> 1785968 bytes sumfiles/gdb.sum | 6808 +++++++++++++++++++------------ 30 files changed, 4789 insertions(+), 4202 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (4149bee4f5 -> 8ce28f0640)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 4149bee4f5 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards a31c088f47 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 6370705fde 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 222c279c3e 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 92221075aa 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards a66e16564a 95: onsuccess: #835: 1: Success after binutils: 3 commits discards bb90aeacd7 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 1790244615 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards ba6099675c 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 62e9ad9409 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards b8148f0a03 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 24e9fe8e24 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 00da8c3c24 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 130140b428 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards e6e52f2df8 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 5b8336f76c 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards a78a1069a1 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards af9bf7ebcb 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards f23f16396a 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 66e8fd358b 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 7a4a71b09b 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 533d422d73 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 2ac71a4542 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 223523930d 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards b8a4ab8506 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 037b63d05d 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards ff0e6fc0b1 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 1d961039c9 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards e2b258c7df 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 462d87a64c 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 1043dae4d1 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 204d0a69c6 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards d809c77d58 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards aadbf1d223 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 2d434a70d4 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 2ed65ecf36 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 7ac4c51a2d 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards b5fde2f0e7 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 24524304a5 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards d502b1fa68 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 24d3d8aae4 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards f2128a43c0 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 0369be36b5 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards cb4470485d 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 71fd7b5f50 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards f13323a5ec 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 2b3567035a 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards a5d94ff1d9 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 9be30e6001 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards b0f4193b0c 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards 31c40b7046 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards e754513030 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 822f5eee05 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 5ad1cfffd0 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 7bfaa489b3 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards 6bb27fc56f 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards 685078f817 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards f4d0a1e040 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards 413cb87a94 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards 9cb41fc912 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards 4fbf3d6860 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] discards 366376ea89 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] discards ce9655cd6e 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] discards 99133fa3c2 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] discards 4c255e0cf0 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 0bead72cef 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] discards f2792e60cb 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] discards b9df46d311 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] discards 77421ca188 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] discards bfa9eed3eb 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] discards d61ec9cf74 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] discards fd382af591 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] discards b155f18e0c 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] discards 5069c4451e 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] discards 754b6c16c2 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] discards 90710198bb 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] discards 5662c7dad7 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards 29a5cb4bde 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards c98f2cfccc 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 9f286ddddc 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards daf024ecef 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 75b7919290 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 17e7255b4d 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4505e37003 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 43610ba6fb 16: onsuccess: 1: Successful build after binutils: 4 commits discards 5a34c02681 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards be74ba6bb4 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 68161bd881 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a3352d9b60 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 94bb04547a 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5a54156407 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cf3d386d59 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 8b0ee7e426 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards e3d1d69940 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards b6f40e02db 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards eb01eb74c5 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 0641f5a7d0 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards c4dd935043 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 601308a433 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 3ef7050a49 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 54eda6b1e6 0: update: binutils-gcc-linux-glibc-gdb: 1 new 41c2f91a8d 0: update: binutils-gcc-linux-glibc-gdb: 1 new d78e1bed9d 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 608c7e847c 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 3142422efd 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 889f18e9db 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 6d672e94dc 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new d85836ab26 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 3ccb600a39 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 673b2faef3 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 6d84fb49c7 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 4fc0a63e0a 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9cb67b0d95 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4127a192a9 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 030a16dbb1 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 878ce17d6f 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new eee3fea60f 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2359d070ba 16: onsuccess: 1: Successful build after binutils: 4 commits new e0be1feea6 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7b0b3acbc9 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c3060f859c 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a5ea9e210d 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 14bfa859c0 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7dc514a786 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 9483851f4c 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new d49b8510f8 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 8cadc7f1e3 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] new 0a125ef551 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] new d39a2d6ef1 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] new e3d730b8d0 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] new 8b77bc3524 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] new 044fa59317 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] new 53fe58bd18 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] new 95a25307de 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] new 867f25ec40 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] new 8425f3a8c6 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] new 0eff7c3a05 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] new f599bef16c 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 5ac0d45e02 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] new 969f846586 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] new 6bc132e805 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] new ce033bd7d7 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new 7c8c35de0f 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new 5068cc7b22 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new 905dd095eb 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new a4996dd12c 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new cca428cab2 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new a785bec747 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new 7fb46e3415 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new f31c58352c 48: onsuccess: #782: 1: Success after binutils: 8 commits new 2caf435516 49: onsuccess: #785: 1: Success after binutils: 12 commits new 8625fcb3fd 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new ea9da694e6 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new bf673f6e84 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new b1cd6181fc 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 4ce73ffded 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new d37c2b87f1 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 5490575364 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 084ad84c4c 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new 58eab802f1 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 6cf55ad934 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new a1f8fc278a 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new ac5509df10 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 3f060fe55f 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 3930699636 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 8bd0e87274 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 549034b7ab 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new bd84a31d87 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new a0cdb59ad9 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new b7b2fc5a78 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 581f2b1679 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 6ecf6c5d0a 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 55f2360d8b 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new cdc3c1e946 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new aeda5a64c2 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 0830c401be 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new cf737224e3 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 15c2e27d28 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new b3e7f332f5 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 5652f33e98 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new c02990348d 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new b84f861185 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 50ce8fbb9c 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new a3c4fec973 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 1ec495e146 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 309609b386 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new e1e36ffb36 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 1f251cebe4 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 336d500e24 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 395c3478ce 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new d91c57d56d 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 45947a5bad 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 8bb2901e7f 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 187330af3d 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 27b00e5c23 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new b1e832e416 94: onsuccess: #832: 1: Success after binutils: 5 commits new 8d3bb6db37 95: onsuccess: #835: 1: Success after binutils: 3 commits new f1015bce93 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 35a8804204 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 60d67f0988 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new b049814b7a 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new c85ec761f8 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 8ce28f0640 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] 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 (4149bee4f5) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] 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 1752 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 39376 -> 39764 bytes 04-build_abe-gcc/console.log.xz | Bin 215056 -> 215748 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8528 -> 8752 bytes 07-build_abe-glibc/console.log.xz | Bin 243744 -> 244432 bytes 08-build_abe-gdb/console.log.xz | Bin 39168 -> 39128 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3836 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2716 -> 3744 bytes 11-check_regression/console.log.xz | Bin 8804 -> 5980 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 10 - 11-check_regression/mail-body.txt | 34 +- 11-check_regression/results.compare | 29 +- 11-check_regression/results.compare2 | 560 +--- 11-check_regression/results.regressions | 30 - 12-update_baseline/console.log | 39 +- 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 | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 30 - sumfiles/g++.log.xz | Bin 3741716 -> 3749764 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 3294100 -> 3299144 bytes sumfiles/gcc.sum | 4893 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1079704 -> 1077360 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2276 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 230636 -> 231784 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 450112 -> 453816 bytes sumfiles/libstdc++.sum | 12 +- 42 files changed, 2678 insertions(+), 3230 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_profiled_lto updated (9d9be54768 -> 1edf694670)

by git＠git.linaro.org

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/release-arm-bootstrap_profiled_lto in repository toolchain/ci/base-artifacts. from 9d9be54768 28: onsuccess: #140: 2: Success after binutils/gcc: 17 commits new 1edf694670 29: onsuccess: #141: 2: Success after binutils/gcc: 8 commits The 1 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 1680 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2708 -> 2716 bytes 04-build_abe-binutils/console.log.xz | Bin 51924 -> 50980 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 943208 -> 948360 bytes 06-check_regression/console.log.xz | Bin 2880 -> 2892 bytes 07-update_baseline/console.log | 2 +- 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, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-stable-allmodconfig updated (51d83f17ba -> 44a7bccb26)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-stable-allmodconfig in repository toolchain/ci/base-artifacts. from 51d83f17ba 39: onsuccess: #511: 23023: Success after binutils/llvm/linu [...] new 44a7bccb26 40: onsuccess: #512: 23023: Success after binutils/llvm/qemu [...] The 1 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 1712 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 31604 -> 31468 bytes 04-build_kernel_llvm/console.log.xz | Bin 65184 -> 65856 bytes 05-build_abe-qemu/console.log.xz | Bin 30524 -> 30712 bytes 06-build_linux/console.log.xz | Bin 5200 -> 5224 bytes 08-check_regression/console.log.xz | Bin 4440 -> 4084 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 15 files changed, 21 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-allnoconfig updated (269c875ae2 -> 48e3db9f97)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-allnoconfig in repository toolchain/ci/base-artifacts. from 269c875ae2 22: onsuccess: #464: boot: Success after binutils/gcc/linux/ [...] new 48e3db9f97 23: onsuccess: #465: boot: Success after binutils/gcc/qemu: [...] The 1 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 1712 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 31776 -> 32096 bytes 04-build_abe-stage1/console.log.xz | Bin 73208 -> 73784 bytes 05-build_abe-qemu/console.log.xz | Bin 30608 -> 31244 bytes 06-build_linux/console.log.xz | Bin 3312 -> 3320 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4324 -> 3980 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 16 files changed, 21 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[linux] branch master updated (77c51ba552a1 -> 894909f95aa1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository linux. from 77c51ba552a1 Merge tag 'scsi-fixes' of git://git.kernel.org/pub/scm/lin [...] new eb761a1760bf powerpc: Fix writable sections being moved into the rodata region new 712fb83dc3f6 Merge tag 'powerpc-6.1-5' of git://git.kernel.org/pub/scm/ [...] new 23df39fc6a36 locking: Fix qspinlock/x86 inline asm error new 6a211a753d1c Merge tag 'locking_urgent_for_v6.1_rc6' of git://git.kerne [...] new bb88f9695460 perf: Improve missing SIGTRAP checking new bdfe34597139 perf/x86/amd/uncore: Fix memory leak for events array new baa014b9543c perf/x86/amd: Fix crash due to race between amd_pmu_enable [...] new ce0d998be927 perf/x86/intel/pt: Fix sampling using single range output new eb0ef8add5a3 Merge tag 'perf_urgent_for_v6.1_rc6' of git://git.kernel.o [...] new 448dca8c8875 rseq: Use pr_warn_once() when deprecated/unknown ABI flags [...] new 91dabf33ae5d sched: Fix race in task_call_func() new d4f754c3615c Merge tag 'sched_urgent_for_v6.1_rc6' of git://git.kernel. [...] new f0861f49bd94 x86/sgx: Add overflow check in sgx_validate_offset_length() new 36b038791e1e x86/fpu: Drop fpregs lock before inheriting FPU permissions new 894909f95aa1 Merge tag 'x86_urgent_for_v6.1_rc6' of git://git.kernel.or [...] The 15 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: arch/powerpc/kernel/vmlinux.lds.S | 2 +- arch/x86/events/amd/core.c | 5 ++- arch/x86/events/amd/uncore.c | 1 + arch/x86/events/intel/pt.c | 9 ++++++ arch/x86/include/asm/qspinlock_paravirt.h | 2 +- arch/x86/kernel/cpu/sgx/ioctl.c | 3 ++ arch/x86/kernel/fpu/core.c | 2 +- kernel/events/core.c | 25 +++++++++++---- kernel/rseq.c | 19 +++++++++-- kernel/sched/core.c | 52 +++++++++++++++++++++---------- 10 files changed, 89 insertions(+), 31 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 updated (7512139967 -> 424fedfbae)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. from 7512139967 14: onsuccess: #19: 1: Success after binutils/gcc/linux/gdb: [...] new 424fedfbae 15: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb: [...] The 1 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 1688 -> 1888 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 40088 -> 39788 bytes 04-build_abe-gcc/console.log.xz | Bin 214824 -> 216856 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8632 -> 8780 bytes 07-build_abe-glibc/console.log.xz | Bin 245676 -> 246264 bytes 08-build_abe-gdb/console.log.xz | Bin 39508 -> 39600 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3840 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2632 -> 2920 bytes 11-check_regression/console.log.xz | Bin 5948 -> 5916 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 20 ++++++-------------- 12-update_baseline/console.log | 2 +- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- sumfiles/gdb.log.xz | Bin 14496 -> 14480 bytes sumfiles/gdb.sum | 34 +++++++++++++++++----------------- 25 files changed, 50 insertions(+), 58 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits November 2022