Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-mainline-allyesconfig updated (7483472bb8 -> a0dc485bb0)

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-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from 7483472bb8 18: force: #506: all: Success after llvm: 28 commits new a0dc485bb0 19: force: #507: 36: Failure after llvmorg-16-init-5673-ge07 [...] 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 -> 1628 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30384 -> 30352 bytes 04-build_kernel_llvm/console.log.xz | Bin 64832 -> 63996 bytes 05-build_abe-qemu/console.log.xz | Bin 31564 -> 31520 bytes 06-build_linux/console.log.xz | Bin 3080 -> 3584 bytes 07-boot_linux/console.log.xz | Bin 576 -> 0 bytes 08-check_regression/console.log.xz | Bin 2960 -> 3744 bytes 08-check_regression/jira-body.txt | 2 +- 08-check_regression/mail-body.txt | 15 +- 08-check_regression/mail-subject.txt | 2 +- 08-check_regression/results.regressions | 7 + 08-check_regression/trigger-bisect | 2 + 08-check_regression/trigger-notify | 0 dashboard/dashboard-generate.sh | 2 +- git/llvm_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 442 ++++++++++++++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 15 +- mail/mail-subject.txt | 2 +- manifest.sh | 12 +- results | 11 +- 26 files changed, 500 insertions(+), 25 deletions(-) delete mode 100644 07-boot_linux/console.log.xz create mode 100644 08-check_regression/results.regressions create mode 100644 08-check_regression/trigger-bisect create mode 100644 08-check_regression/trigger-notify create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/interesting-commits] branch master updated (cb09c53 -> 6371769)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from cb09c53 Add entry a1c9f779f75283427316b5c670c1e01ff8ce9ced from https [...] new 6371769 Add entry e07ead85a368173a56e96a21d6841aa497ad80f8 from https [...] 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: .../tcwg_kernel/llvm-master-aarch64-mainline-allyesconfig}/build_url | 2 +- .../last_good | 0 .../summary.txt | 0 .../e07ead85a368173a56e96a21d6841aa497ad80f8/tcwg_kernel/status.txt | 3 +++ 4 files changed, 4 insertions(+), 1 deletion(-) copy {linux/sha1/3dd33a09f5dc12ccb0902923c4c784eb0f8c7554/tcwg_kernel/llvm-master- [...] copy llvm/sha1/e07ead85a368173a56e96a21d6841aa497ad80f8/tcwg_kernel/{llvm-master-a [...] copy llvm/sha1/e07ead85a368173a56e96a21d6841aa497ad80f8/tcwg_kernel/{llvm-master-a [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-next-defconfig updated (3c6715fe13 -> a831bb1195)

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-release-aarch64-next-defconfig in repository toolchain/ci/base-artifacts. from 3c6715fe13 10: onsuccess: #536: boot: Success after binutils/gcc/qemu: [...] new a831bb1195 11: force: #538: boot: Success after linux: 435 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 1664 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30364 -> 30216 bytes 04-build_abe-stage1/console.log.xz | Bin 69048 -> 68988 bytes 05-build_abe-qemu/console.log.xz | Bin 31348 -> 31468 bytes 06-build_linux/console.log.xz | Bin 3156 -> 3440 bytes 07-boot_linux/console.log.xz | Bin 6124 -> 6272 bytes 08-check_regression/console.log.xz | Bin 3760 -> 3008 bytes 08-check_regression/mail-body.txt | 2 +- 09-update_baseline/console.log | 10 +++++----- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 26 ++++++++++++-------------- results | 2 +- 17 files changed, 25 insertions(+), 27 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (f3437bbff7 -> e514d07682)

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-arm in repository toolchain/ci/base-artifacts. discards f3437bbff7 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] discards a8d5a8c3f3 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] discards 9531665ac0 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] discards 91106e13fe 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards d144b94807 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 06b44bb7da 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards 1f6b4e58d9 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards 3c049bd5a7 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards 09592d60cd 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards 5473377bd8 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards 844f8f92a6 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards 24524e40e3 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards a82657e550 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards 5caf9fe4d5 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards 03a75e89ef 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards 4eb9b99c40 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards 89ee0ddd6c 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 7db46ac5a5 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards a2dc6146ac 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 1cbdbf240f 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards 31028abd64 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 494dc06eda 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 4333413703 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards 6ebcfeeb33 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 21d461739c 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards f990eb2cf2 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards bf87e2eed3 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards d499027470 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards c7b639b842 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards ddfc0c2d98 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards e389529448 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 5e276eba4b 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards ab3a8cbf2f 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards baf8183c06 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 40dcf9c84c 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 5bc3453677 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 98d87ea7e9 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 69d4ee46f7 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 9563610cfa 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 049a876880 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards e31128d762 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards f7a82e51e6 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 18c929eb2f 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards 08df0b1e68 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards dce176b710 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 2041c3099c 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards ec62d53b0a 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards c2df094a7c 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 638ab8f651 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 8614bb1d0d 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 8932ff0cdc 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 9957e07d65 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 5518397756 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards e552a97011 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards b8dcdd3369 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards bcd4758acc 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards 9d5528f444 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 4cc6a2f65d 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards bc549c8efc 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 8edf02cdc8 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 3414988978 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards dbd01bfe3c 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 97bbb116fa 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards c35723eff8 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 97bab3b931 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards f2bb3bc33e 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards dec27674f8 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 1626e7dda5 85: onsuccess: 7: Success after gcc: 9 commits discards 7d3d98ecab 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 36295794cf 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 0ab8bb3c05 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards ab739e0484 81: onsuccess: 7: Successful build after gcc: 2 commits discards e15f14f53b 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 5281d6b44e 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 27f8eeca3f 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7c45ecc8fb 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 9782c52a66 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9ad0dfa44f 75: onsuccess: 7: Successful build after linux: 44 commits discards 7e9a9604a9 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 02b7329753 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 311815273c 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 411730b886 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards b7ac6a2be8 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards f6237e9dfd 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 9a164f6069 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5185ba1200 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 7ef9e9a81b 66: onsuccess: 7: Successful build after gcc: 3 commits discards 4bbfdf95bc 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ff2ac65922 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0e0b377751 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 72c1010d69 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 4502d4ecfe 61: onsuccess: 4: Successful build after gcc: 15 commits discards 5f81c4560e 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 4a8e656b86 59: force: 7: Successful build after gcc: 2 commits discards 7ee66451e4 58: onsuccess: 7: Successful build after glibc: 2 commits discards 624274d0f6 57: onsuccess: 7: Successful build after gcc: 7 commits discards 7857a50269 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards fa6d5cf4ae 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 11e8e05164 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards fb1ec742db 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 5752b93a2b 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new a938cb114d 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 321f930f20 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 8058d1e8b1 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 37319fb8d5 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d12a77da9d 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5114a66362 57: onsuccess: 7: Successful build after gcc: 7 commits new ed6c27d200 58: onsuccess: 7: Successful build after glibc: 2 commits new e15f665d1c 59: force: 7: Successful build after gcc: 2 commits new 5bf2693bcf 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 198e09d311 61: onsuccess: 4: Successful build after gcc: 15 commits new 2f7a271c11 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 627d77c4ac 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 725014b541 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b19b0aa063 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4f64d88022 66: onsuccess: 7: Successful build after gcc: 3 commits new b32a16ac42 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 03c74ed2c0 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d6bbfafa0b 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 741f672110 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new e9f3581f6d 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 3111aacf0b 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 4116ef8d4c 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2fc788ddfe 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 2cc0088fed 75: onsuccess: 7: Successful build after linux: 44 commits new 49d223f6fc 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 90c7ebef9e 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new f571f97776 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 01660047b9 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new b65c76e55a 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new f6c6a151a5 81: onsuccess: 7: Successful build after gcc: 2 commits new b22be48b82 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new fb18f8332e 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 2680a09c67 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new e79afc6b7b 85: onsuccess: 7: Success after gcc: 9 commits new 3c027b9cb7 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new ec3c77c950 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new af9a07e901 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 8aa1e239c1 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 7f8c122c66 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new b67f7d213a 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 63aa5b74ed 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new b80f6c8fd9 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new 969273a753 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 5f920633df 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 51b833ec55 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 9529e3f7dc 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 7ce1a6b5f5 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new d13ad8edd9 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 54c5381310 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new b6eeb0c0db 101: onsuccess: #1609: 7: Success after binutils: 78 commits new a8ef7d27a3 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 9b89ecf76a 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new c391e16528 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 897c3e12b9 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 78df0cf1b5 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 82a2c2ff3b 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 5b495eaeca 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new deaedeb5d7 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 80f6a40674 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new ae383b6383 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 9a9c014c39 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 909ea7f256 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 90049d123d 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 337f344f69 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 0efdf4cb46 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 08c7a0aae0 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 323c3ee87b 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 9bb4877ca0 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 2c2599aa98 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 63656b1866 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new dc0c2e42e2 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 113691f8a0 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new ea81fc5db1 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 6aaee169dd 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new daea0ec246 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new 3ef077ab60 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new ff19260914 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 433004a0f7 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 64594196e9 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 0868ee2e90 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 918d8c17f2 132: onsuccess: #1645: 7: Success after linux: 23 commits new a81d900f65 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new f3d3938413 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new 99da78d9ab 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new dade1915db 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 85d71ca1de 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new ee5ee2b355 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new a8ed850e08 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 1ce24dfdba 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new 95004054df 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 8815e8c20e 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 5b770f7de5 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new 18f6c7c0b2 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new 258a03de2b 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new 830441d135 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new 313315b69b 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new e18d9c2074 148: onsuccess: #1663: 7: Success after glibc: 2 commits new 5919cae3a7 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new 3f828e3c21 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] new 065b36b7bf 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] new 068ba79527 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] new e514d07682 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] 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 (f3437bbff7) \ 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 1664 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 30228 -> 30424 bytes 05-build_abe-stage1/console.log.xz | Bin 91164 -> 91508 bytes 07-build_abe-linux/console.log.xz | Bin 8472 -> 8492 bytes 08-build_abe-glibc/console.log.xz | Bin 234220 -> 235636 bytes 09-build_abe-stage2/console.log.xz | Bin 224088 -> 225880 bytes 10-build_abe-gdb/console.log.xz | Bin 37440 -> 37120 bytes 11-build_abe-qemu/console.log.xz | Bin 31584 -> 31804 bytes 12-check_regression/console.log.xz | Bin 3820 -> 3996 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 ++++++++++---------- 19 files changed, 57 insertions(+), 57 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/jenkins-scripts] branch master updated (808f49ee -> 01e9c013)

by Prathamesh Kulkarni

This is an automated email from the git hooks/post-receive script. "Prathamesh Kulkarni pushed a change to branch master in repository toolchain/jenkins-scripts. from 808f49ee tcwg_bmk-build.sh: Run VECT benchmark jobs in parallel. new 01e9c013 tcwg_bmk-build.sh: Collect symbols that are skipped by md5sum [...] 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: tcwg_bmk-build.sh | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (57707f38f2e -> 3bb2d70d380)

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 gcc. from 57707f38f2e libstdc++: Add missing <bits/stl_algobase.h> include to <bitset> new 3bb2d70d380 testsuite: Colon is reserved on Windows 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: gcc/testsuite/g++.dg/modules/ben-1.map | 2 +- gcc/testsuite/g++.dg/modules/ben-1_a.C | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (c23b5006d3f -> 57707f38f2e)

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 gcc. from c23b5006d3f rs6000: Rework ELFv2 support for -fpatchable-function-entry [...] new 57707f38f2e libstdc++: Add missing <bits/stl_algobase.h> include to <bitset> 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: libstdc++-v3/include/std/bitset | 2 ++ 1 file changed, 2 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-mainline-allyesconfig updated (cf0064eeb9 -> 7483472bb8)

by git＠git.linaro.org

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (e25a460018 -> 225a878581)

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 e25a460018 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards 240af40538 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards b5ddb3e933 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards 642860ca1f 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards 6c3614d7e6 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 8798d448d2 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards 4fb2d650c2 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards 346207108d 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 6dbab2cce1 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards f03dab070c 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards 8d3cc00126 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards f19e797d01 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards b908e233d3 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards a8912336ac 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards f9d02ddb3c 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 47480af588 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards 6cc3c2f8ed 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards f1d1bc2284 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 567bc5c455 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards c206a1bf53 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards 1098d81c65 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 708d516859 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 6b8c2a77ca 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 810717c4d1 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards f9472b63bd 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 647b3ae7e9 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards 68142ef5cf 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 8df0b73259 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards 70b6d44ba0 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards 272e505276 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 993f3c0316 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards e07bc6988d 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 822e90b7bd 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 8983bdd2f3 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards 4b46e54312 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards cf9ec65eec 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards 2c00735de4 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards 99f2f7f4ae 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards c86adc916a 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 515ebbf741 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards bbdb3a75be 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards bd616c26b8 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards a1dbc215b6 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 1f773edb43 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards b298856745 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards d3e51325d5 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 093cabef1b 102: force: #1551: 1: Failure after gcc: 306 commits discards 9f6bdf6e1f 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 9fba5acd9c 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 44411e6185 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 4395d95906 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards b8c16ee67a 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 5c313b4159 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards d3d57b7b37 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 15678e2844 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 57af793785 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 87a5798da3 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 197c10eb91 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards ce298ecd31 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 790609fba8 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 117ab4f979 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 6745b00710 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 928e9456ed 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 59016b8d46 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards e9121e8be3 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 9cc589bc9f 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 111e5d318e 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 6446d10bf8 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e6f269077f 80: onsuccess: 7: Successful build after linux: 44 commits discards b0aadfdfad 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards efe26c381e 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards fed1953754 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards cedebc9f62 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 10f727dc01 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 0a189b385e 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 9a2db4759a 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 95106cf21a 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 56c386044b 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 938fd94d61 70: onsuccess: 7: Successful build after gcc: 4 commits discards 269743932e 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 905ee59c68 68: onsuccess: 7: Successful build after linux: 6 commits discards 88d375b67b 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards a05a712a90 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards cde8a0972b 65: onsuccess: 7: Successful build after binutils: 3 commits discards 2da43c676a 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards e75469dea0 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards de7ebb9ad6 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 581dd8a0e3 61: onsuccess: 4: Successful build after gcc: 5 commits discards c1c6348cfe 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 5a29d982ef 59: force: 7: Successful build after gcc: 3 commits discards 0753c76cd2 58: onsuccess: 7: Successful build after glibc: 2 commits discards 0f6ca84419 57: onsuccess: 7: Successful build after gcc: 7 commits discards f84c654e14 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a00ec6dcc2 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5ebe1a8ec5 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards 377f2d8ac5 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 44e208e380 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] discards 51cfa37733 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 698977530c 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 8b1f59ba1c 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 38baa22d32 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new eb6f7e42db 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 1d7d382c48 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 10d6f26a90 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 53efb95d2b 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new c1de2774f7 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new a6f9a331a3 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 0a12db3fb2 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 9fec548da7 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new cf1be0130e 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b4de426809 57: onsuccess: 7: Successful build after gcc: 7 commits new e9066dd907 58: onsuccess: 7: Successful build after glibc: 2 commits new f1a8c82151 59: force: 7: Successful build after gcc: 3 commits new 534d944432 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 4ba9d5fa44 61: onsuccess: 4: Successful build after gcc: 5 commits new ef360ae470 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 1e65a73396 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new b9d4e7b7bb 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 504dd2b02f 65: onsuccess: 7: Successful build after binutils: 3 commits new 957c3233d0 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 7d7a2593e8 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new 94c868f14e 68: onsuccess: 7: Successful build after linux: 6 commits new 3e0de6c593 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2c949ccb50 70: onsuccess: 7: Successful build after gcc: 4 commits new 130566037a 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 7df2a78c9c 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ce5607d6f2 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 66e4a4fc93 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 0d6b57e3c6 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 446b072115 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new d3c4c75fd6 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c630148cfd 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new f98d714770 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 333a7abb9e 80: onsuccess: 7: Successful build after linux: 44 commits new 85529a4cb9 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new cbf062ed08 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 6d71b70cb1 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new fb3525eb9c 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 0549c42662 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 2f40010745 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 743d4acabc 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 315c272596 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 9773caa7c4 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 9ec145d09a 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new b5c6a51de3 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new a2ea1236d6 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new f85b9c8514 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 6f4c68e528 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 40a05b5073 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 6fc3facb8f 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 04ccff08d6 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 37b2f60dd2 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 00383f5333 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 7592b08b02 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 687894bf0c 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 7d3eaa41f2 102: force: #1551: 1: Failure after gcc: 306 commits new 7e380ef60f 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 17b2eba8a8 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 1598495f23 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 904d9b419d 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new f5d97171dc 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new 36dc374d65 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new fb8d1773cc 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new e3c9b76afb 110: onsuccess: #1559: 7: Success after gcc: 4 commits new daeb17442a 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new 25c0cc0ffd 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 283f323f6e 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new 41c0301827 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 50a9f5c0fb 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 7a17ac0536 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new ce51c31dda 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 74ae5a7b03 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new 5c63a13f0f 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new c7b46f8f80 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new d771789414 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new e9460e4a38 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new e2d4963647 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new df54482cea 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 07d6503ae5 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 6a80ba9151 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 1c326f2c4a 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new b5367e6a15 128: onsuccess: #1579: 7: Success after linux: 12 commits new 96290f83a4 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new e6c76975b6 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new d4a6355848 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new e2ca10a67c 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 723bbfa91c 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new 8b80b585d3 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new a23300e194 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new 7f22da529e 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new 154f79a91b 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 8f91d32148 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new 9d86e74533 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new c53af1cff9 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new a787ecc3b6 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new 89d0b07652 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new 33db9b8662 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new 2694b60104 144: onsuccess: #1595: 7: Success after glibc: 2 commits new f57f6e4ba3 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new 619266d837 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new f721d4589c 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new 80da1edbf8 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new 225a878581 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] 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 (e25a460018) \ 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 1712 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 30408 -> 30200 bytes 05-build_abe-stage1/console.log.xz | Bin 72460 -> 72740 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 8456 -> 8460 bytes 08-build_abe-glibc/console.log.xz | Bin 239464 -> 239864 bytes 09-build_abe-stage2/console.log.xz | Bin 202436 -> 203060 bytes 10-build_abe-gdb/console.log.xz | Bin 37796 -> 37396 bytes 11-build_abe-qemu/console.log.xz | Bin 31956 -> 32160 bytes 12-check_regression/console.log.xz | Bin 3836 -> 3976 bytes 13-update_baseline/console.log | 70 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++--------- 20 files changed, 60 insertions(+), 60 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_lto updated (3ae5ad3d64 -> 265368c35d)

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/master-arm-bootstrap_lto in repository toolchain/ci/base-artifacts. from 3ae5ad3d64 50: onsuccess: #459: 1: Success after gcc: 26 commits new 265368c35d 51: onsuccess: #460: 2: Success after binutils/gcc: 126 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 1672 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 50636 -> 51772 bytes 05-build_abe-bootstrap_lto/console.log.xz | Bin 110916 -> 472776 bytes 06-check_regression/console.log.xz | Bin 2672 -> 3180 bytes 06-check_regression/mail-body.txt | 11 +---------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 13 ++----------- mail/mail-subject.txt | 2 +- manifest.sh | 21 +++++++++++---------- results | 2 +- 14 files changed, 20 insertions(+), 37 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

← Newer
1
2
3
4
5
6
7
8
9
...
469
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022