Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[linux] branch master updated (a63f2e7cb110 -> 3db61221f4e8)

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 a63f2e7cb110 Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/li [...] new db7ba07108a4 s390/dasd: fix Oops in dasd_alias_get_start_dev due to mis [...] new 4c66a326b5ab Revert "block: freeze the queue earlier in del_gendisk" new 0be27f7be2e5 Merge tag 'block-6.0-2022-09-22' of git://git.kernel.dk/linux new e775f93f2ab9 io_uring: ensure that cached task references are always pu [...] new 3db61221f4e8 Merge tag 'io_uring-6.0-2022-09-23' of git://git.kernel.dk/linux The 5 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: block/genhd.c | 3 ++- drivers/s390/block/dasd_alias.c | 9 +++++++-- io_uring/io_uring.c | 3 +++ 3 files changed, 12 insertions(+), 3 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-mainline-defconfig updated (816c088b71 -> cc53b82b00)

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-arm-mainline-defconfig in repository toolchain/ci/base-artifacts. from 816c088b71 10: onsuccess: #394: boot: Success after binutils/gcc/linux/ [...] new cc53b82b00 11: onsuccess: #395: boot: Success after binutils/gcc/linux/ [...] 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 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 29884 -> 29972 bytes 04-build_abe-stage1/console.log.xz | Bin 86360 -> 86556 bytes 05-build_abe-qemu/console.log.xz | Bin 31104 -> 30876 bytes 06-build_linux/console.log.xz | Bin 2984 -> 3036 bytes 07-boot_linux/console.log.xz | Bin 5824 -> 5832 bytes 08-check_regression/console.log.xz | Bin 3072 -> 4368 bytes 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 | 31 ++++++++++++++++--------------- 17 files changed, 24 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap updated (06264941e5 -> dc89936619)

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 in repository toolchain/ci/base-artifacts. discards 06264941e5 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards 610429ad4e 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards ff890f71d7 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards 7e39fc504e 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards 8b7f8220c0 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards 0cbe18e710 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards 4b24ae8925 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards 1fe97702d3 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards 2119fedc6d 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards 5065f92489 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards 92647811a8 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards c559869f00 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards 48eb5b730e 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards 6feb1c4aa1 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 21857fd03d 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards b2931d4b9e 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards 246f697c35 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards d46af86bd9 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards 6cf173f247 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards 2dd9e65c8d 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 6b7a78d805 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards 9e10e25638 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards cea37e30b8 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards 42e170a2a0 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards 6d347eb27c 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 914da4c1de 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards bd1034d8e1 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards ae56dceb73 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards 2c49e048be 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards 09f0609dfd 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards 94120b6d55 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 79ff610c91 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 5e846caaec 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards 25517ad1aa 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards d726a7d986 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards 2345057bbb 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards 70cd0ebe91 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards 824c7f2edc 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards 0fc53aa453 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards c5365900e8 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards 657298424d 87: onsuccess: 2: Success after gcc: 4 commits discards 1eb4623f5d 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards 16d9334427 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards d6498a2f19 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards fd923c70d7 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 3001c522d1 82: onsuccess: 1: Successful build after gcc: 3 commits discards fb9049a305 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 1d04ff6f97 80: force: 2: Successful build after gcc: 14 commits discards 7967f4b235 79: onsuccess: 2: Successful build after binutils: 5 commits discards b27e7bc49d 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards 5e8916491b 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 7ddb2fb383 76: onsuccess: 2: Successful build after gcc: 12 commits discards c653f93b21 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 956e2a727f 74: onsuccess: 2: Successful build after baseline build: no [...] discards d1fe805647 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards b73c86f4ff 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 4835d521bc 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 1dbdfc756b 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 5f4d05a24d 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards d7422f10cf 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 0362bb1b0d 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards f3a62ce8a0 66: onsuccess: 2: Successful build after gcc: 9 commits discards df74436cc5 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards f7db1f53fc 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards b7e22fe179 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards db8042da81 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 1069db899d 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards 3590c6c25f 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards fa0074356c 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 6a1c7e1e25 58: force: 2: Successful build after gcc: 6 commits discards afc5da493a 57: onsuccess: 2: Successful build after binutils: gdb: new [...] discards f47f131a5e 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 7b3a871ad6 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 2fc4efc37c 54: onsuccess: 2: Successful build after gcc: 5 commits discards 741d46e271 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 4dcf00b46e 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards e7a32427de 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 7e976a8ef0 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 830fe01576 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards cd79fa22b8 48: onsuccess: 2: Successful build after gcc: 4 commits discards a304a07ca3 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 046e78e9db 46: onsuccess: 2: Successful build after baseline build: no [...] discards 4535b65f0d 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards fa2e07ccca 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 2a0d07c3f9 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards a4c95db9a3 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] discards 395ef45f6b 41: onsuccess: 2: Successful build after gcc: libcpp: Implem [...] discards 4728590b3b 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 4d1696a2c2 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 354fe91933 38: onsuccess: 2: Successful build after gcc: 2 commits discards 2392b1f616 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards c2696fc512 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 7145100ab2 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 6bac5be482 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 558993fba8 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards f56cac85f5 32: onsuccess: 2: Successful build after gcc: 6 commits discards 255821763e 31: onsuccess: 2: Successful build after gcc: 6 commits discards 57fd06a9ae 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards fb2ea6c7ef 29: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards ae62dfa711 28: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 6df96be902 27: onsuccess: 2: Successful build after binutils/gcc: 14 commits new e90792f29d 27: onsuccess: 2: Successful build after binutils/gcc: 14 commits new a21929a6c5 28: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 33b1e8d0a3 29: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 6472b422ec 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits new af8c91355f 31: onsuccess: 2: Successful build after gcc: 6 commits new b4e475b4bf 32: onsuccess: 2: Successful build after gcc: 6 commits new 2ed8072158 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits new b616f34eaf 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits new ea751c7307 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits new d52ede2bd0 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 134c097b22 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits new bb705d28d0 38: onsuccess: 2: Successful build after gcc: 2 commits new 9f8590b8d0 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits new a4feee0707 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 6b34716c02 41: onsuccess: 2: Successful build after gcc: libcpp: Implem [...] new d5eb13f144 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] new 1b43179e6f 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new ae26af50b8 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 7815821d45 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new ea5a335ffa 46: onsuccess: 2: Successful build after baseline build: no [...] new 1e06f59b5c 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 4b1b3645f6 48: onsuccess: 2: Successful build after gcc: 4 commits new 2b21bb14d2 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 45849a2e7b 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new d913ab41ef 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new c7e00ea423 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 0550b7b55e 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 0bb97b0b7c 54: onsuccess: 2: Successful build after gcc: 5 commits new bf41d53ef9 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 4df27c9667 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 92b48471c9 57: onsuccess: 2: Successful build after binutils: gdb: new [...] new 070bec02df 58: force: 2: Successful build after gcc: 6 commits new 309a3da8ef 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 3065efacfd 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 6292b9ae85 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new e99450dd5a 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 0587ac530e 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new d1eb26892c 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ca8a82222f 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 026da24e0f 66: onsuccess: 2: Successful build after gcc: 9 commits new c72882d24c 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 03c84c255c 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 20fa871a9f 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 29be51608d 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new b8518858a6 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new e4234cc8cd 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 4c13e262ef 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 23fe9f4c8f 74: onsuccess: 2: Successful build after baseline build: no [...] new 7972744ee4 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 0e822ca95b 76: onsuccess: 2: Successful build after gcc: 12 commits new 95ea192f9f 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new b137e93d4d 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new 67d65b8953 79: onsuccess: 2: Successful build after binutils: 5 commits new 1176d31b92 80: force: 2: Successful build after gcc: 14 commits new 10e0aae813 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 8ba303fa39 82: onsuccess: 1: Successful build after gcc: 3 commits new 7c0f489a4a 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new 1a5b3e9be5 84: onsuccess: 2: Success after binutils/gcc: 15 commits new 20d76f5dc2 85: onsuccess: 2: Success after binutils/gcc: 25 commits new 79f87f6908 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 4fbaa303cc 87: onsuccess: 2: Success after gcc: 4 commits new 3f17ea6030 88: onsuccess: 2: Success after binutils/gcc: 25 commits new c5e8171dc0 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 3fe1e865ff 90: onsuccess: 2: Success after binutils/gcc: 16 commits new bd2a0ec699 91: onsuccess: 2: Success after binutils/gcc: 7 commits new 005bcebf0e 92: onsuccess: 2: Success after binutils/gcc: 9 commits new e1a9f4427a 93: onsuccess: 2: Success after binutils/gcc: 3 commits new 2a4700d333 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new 8b41737850 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new 774235d082 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 53629e87d8 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new 832fcb8275 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new 161035eede 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new 457f92d741 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 1c08d07e1a 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new 1d9903581e 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new 8f751b7c91 103: onsuccess: #1504: 2: Success after gcc: 2 commits new 1c980d866a 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new 55503e5c8a 105: onsuccess: #1506: 2: Success after gcc: 2 commits new 5e06b7c66c 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 9791b36537 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new 31b4d66927 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new f8b9e67a42 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new 26cf511be9 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new 6966e1d230 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new fb11d6ca87 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new 934e3f0486 113: onsuccess: #1514: 2: Success after gcc: 5 commits new 9fb5559f7b 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new 662db06d50 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new 9344c2d259 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new b6f0f2f7a4 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 7089a895c8 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new 8efb7eb508 119: onsuccess: #1520: 2: Success after binutils: 8 commits new 22f27e64f0 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new 3ea0317268 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new d82363f52e 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new 68e66e2a80 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new 8613cb4d81 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new f9f8899e57 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new c41a5dac48 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new 04fe951b8d 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new dc89936619 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits 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 (06264941e5) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] 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 1684 -> 1656 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 50768 -> 50416 bytes 05-build_abe-bootstrap/console.log.xz | Bin 469224 -> 463376 bytes 06-check_regression/console.log.xz | Bin 2640 -> 2588 bytes 07-update_baseline/console.log | 40 +++++++++++++++++----------------- 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, 35 insertions(+), 35 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto_lean updated (96b04d9b2d -> 0a639b0ee6)

by git＠git.linaro.org

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_tx1/gnu-master-aarch64-spec2k6-O3_LTO updated (93e7a17ec6 -> 87dc4818f9)

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_bmk_gnu_tx1/gnu-master-aarch64-spec2k6-O3_LTO in repository toolchain/ci/base-artifacts. from 93e7a17ec6 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: [...] new 87dc4818f9 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 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 1772 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 31880 -> 31356 bytes 04-build_abe-stage1/console.log.xz | Bin 75576 -> 72236 bytes 06-build_abe-linux/console.log.xz | Bin 8700 -> 7948 bytes 07-build_abe-glibc/console.log.xz | Bin 242536 -> 241260 bytes 08-build_abe-stage2/console.log.xz | Bin 187636 -> 178200 bytes 09-benchmark/benchmark-build.log | 108 +- 09-benchmark/benchmark.log | 106 +- 09-benchmark/console.log.xz | Bin 3840 -> 3780 bytes 10-check_regression/console.log.xz | Bin 6316 -> 6200 bytes 10-check_regression/csv-results-0/perf.csv | 172 +- 10-check_regression/csv-results-0/results.csv | 59633 +-- 10-check_regression/csv-results-0/size.csv | 489255 +++++++++--------- 10-check_regression/csv-results-0/vect.csv | 40 +- 10-check_regression/csv-results-1/perf.csv | 169 +- 10-check_regression/csv-results-1/results.csv | 47773 +- 10-check_regression/csv-results-1/size.csv | 479562 +++++++++-------- 10-check_regression/csv-results-1/vect.csv | 40 +- 10-check_regression/results-brief.csv | 60 +- 10-check_regression/results-full.csv | 183 +- 10-check_regression/results-internal.csv | 82 +- 10-check_regression/results.csv | 82 +- 10-check_regression/results.log | 1538 +- 11-update_baseline/console.log | 8 +- dashboard/dashboard-generate.sh | 2 +- .../squad/400.perlbench/results-metadata.json | 10 +- dashboard/squad/400.perlbench/results-metrics.json | 4 +- dashboard/squad/401.bzip2/results-metadata.json | 10 +- dashboard/squad/401.bzip2/results-metrics.json | 2 +- dashboard/squad/403.gcc/results-metadata.json | 10 +- dashboard/squad/403.gcc/results-metrics.json | 4 +- dashboard/squad/410.bwaves/results-metadata.json | 10 +- dashboard/squad/410.bwaves/results-metrics.json | 2 +- dashboard/squad/416.gamess/results-metadata.json | 10 +- dashboard/squad/416.gamess/results-metrics.json | 4 +- dashboard/squad/429.mcf/results-metadata.json | 10 +- dashboard/squad/429.mcf/results-metrics.json | 2 +- dashboard/squad/433.milc/results-metadata.json | 10 +- dashboard/squad/433.milc/results-metrics.json | 2 +- dashboard/squad/434.zeusmp/results-metadata.json | 10 +- dashboard/squad/434.zeusmp/results-metrics.json | 2 +- dashboard/squad/435.gromacs/results-metadata.json | 10 +- dashboard/squad/435.gromacs/results-metrics.json | 4 +- .../squad/436.cactusADM/results-metadata.json | 10 +- dashboard/squad/436.cactusADM/results-metrics.json | 2 +- dashboard/squad/437.leslie3d/results-metadata.json | 10 +- dashboard/squad/437.leslie3d/results-metrics.json | 2 +- dashboard/squad/444.namd/results-metadata.json | 10 +- dashboard/squad/444.namd/results-metrics.json | 2 +- dashboard/squad/445.gobmk/results-metadata.json | 10 +- dashboard/squad/445.gobmk/results-metrics.json | 4 +- dashboard/squad/447.dealII/results-metadata.json | 10 +- dashboard/squad/447.dealII/results-metrics.json | 2 +- dashboard/squad/450.soplex/results-metadata.json | 10 +- dashboard/squad/450.soplex/results-metrics.json | 2 +- dashboard/squad/453.povray/results-metadata.json | 10 +- dashboard/squad/453.povray/results-metrics.json | 4 +- dashboard/squad/454.calculix/results-metadata.json | 10 +- dashboard/squad/454.calculix/results-metrics.json | 2 +- dashboard/squad/456.hmmer/results-metadata.json | 10 +- dashboard/squad/456.hmmer/results-metrics.json | 2 +- dashboard/squad/458.sjeng/results-metadata.json | 10 +- dashboard/squad/458.sjeng/results-metrics.json | 2 +- dashboard/squad/459.GemsFDTD/results-metadata.json | 10 +- dashboard/squad/459.GemsFDTD/results-metrics.json | 4 +- .../squad/462.libquantum/results-metadata.json | 10 +- .../squad/462.libquantum/results-metrics.json | 2 +- dashboard/squad/464.h264ref/results-metadata.json | 10 +- dashboard/squad/464.h264ref/results-metrics.json | 2 +- dashboard/squad/465.tonto/results-metadata.json | 10 +- dashboard/squad/465.tonto/results-metrics.json | 4 +- dashboard/squad/470.lbm/results-metadata.json | 10 +- dashboard/squad/470.lbm/results-metrics.json | 2 +- dashboard/squad/471.omnetpp/results-metadata.json | 10 +- dashboard/squad/471.omnetpp/results-metrics.json | 2 +- dashboard/squad/473.astar/results-metadata.json | 10 +- dashboard/squad/473.astar/results-metrics.json | 2 +- dashboard/squad/481.wrf/results-metadata.json | 10 +- dashboard/squad/481.wrf/results-metrics.json | 2 +- dashboard/squad/482.sphinx3/results-metadata.json | 10 +- dashboard/squad/482.sphinx3/results-metrics.json | 2 +- .../squad/483.xalancbmk/results-metadata.json | 10 +- dashboard/squad/483.xalancbmk/results-metrics.json | 4 +- dashboard/squad/Mean/results-metadata.json | 10 +- dashboard/squad/Mean/results-metrics.json | 4 +- dashboard/squad/dashboard-push-squad.sh | 122 +- git/gcc_rev | 2 +- mail/jira-body.txt | 14 +- mail/mail-body.txt | 14 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 6971412 -> 6974256 bytes save-temps/401.bzip2.tar.xz | Bin 421928 -> 422228 bytes save-temps/403.gcc.tar.xz | Bin 19603368 -> 19609288 bytes save-temps/410.bwaves.tar.xz | Bin 79328 -> 79356 bytes save-temps/416.gamess.tar.xz | Bin 29046980 -> 29044220 bytes save-temps/429.mcf.tar.xz | Bin 135836 -> 135612 bytes save-temps/433.milc.tar.xz | Bin 845912 -> 842856 bytes save-temps/434.zeusmp.tar.xz | Bin 1170952 -> 1170180 bytes save-temps/435.gromacs.tar.xz | Bin 5469572 -> 5467824 bytes save-temps/436.cactusADM.tar.xz | Bin 4239320 -> 4243748 bytes save-temps/437.leslie3d.tar.xz | Bin 292700 -> 292348 bytes save-temps/444.namd.tar.xz | Bin 1268312 -> 1270764 bytes save-temps/445.gobmk.tar.xz | Bin 8587352 -> 8593148 bytes save-temps/447.dealII.tar.xz | Bin 28519356 -> 28264000 bytes save-temps/450.soplex.tar.xz | Bin 4379948 -> 4401172 bytes save-temps/453.povray.tar.xz | Bin 6985796 -> 6987100 bytes save-temps/454.calculix.tar.xz | Bin 8816920 -> 8803736 bytes save-temps/456.hmmer.tar.xz | Bin 1926380 -> 1929028 bytes save-temps/458.sjeng.tar.xz | Bin 669276 -> 669884 bytes save-temps/459.GemsFDTD.tar.xz | Bin 1275188 -> 1274500 bytes save-temps/462.libquantum.tar.xz | Bin 251848 -> 250712 bytes save-temps/464.h264ref.tar.xz | Bin 3007592 -> 3015852 bytes save-temps/465.tonto.tar.xz | Bin 16296556 -> 16282080 bytes save-temps/470.lbm.tar.xz | Bin 81652 -> 82076 bytes save-temps/471.omnetpp.tar.xz | Bin 5846068 -> 5820344 bytes save-temps/473.astar.tar.xz | Bin 359200 -> 358444 bytes save-temps/481.wrf.tar.xz | Bin 15726816 -> 15780496 bytes save-temps/482.sphinx3.tar.xz | Bin 1328132 -> 1328508 bytes save-temps/483.xalancbmk.tar.xz | Bin 51965092 -> 51993836 bytes 122 files changed, 538691 insertions(+), 540678 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_profiled_lto_lean updated (d5a106ed65 -> 0121659dc2)

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_lean in repository toolchain/ci/base-artifacts. from d5a106ed65 13: onsuccess: #120: 2: Success after binutils/gcc: 10 commits new 0121659dc2 14: onsuccess: #121: 2: Success after binutils/gcc: 13 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 1676 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 50584 -> 51264 bytes .../console.log.xz | Bin 934936 -> 931692 bytes 06-check_regression/console.log.xz | Bin 2128 -> 2944 bytes 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 | 19 ++++++++++--------- 12 files changed, 16 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (2f260e26c9 -> ce917f99c7)

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_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards 2f260e26c9 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 6ac2284ced 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 97f8f61906 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 5605e65c8b 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 0a0aa5ee42 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 75f39fff4d 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards fb01ee06b2 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 1b1685a57b 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 7005d8bef4 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards fca47379da 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 787c0b6ac5 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 6b6de671e6 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 3c38daccee 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 7c52dee1ce 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards fa5322b392 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 03b25f1662 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 226aadc428 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 0ce2c4929f 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards f3a5d25518 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 2a25fd9ac1 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 8de2316cab 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 6e96051c6e 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards b693ec556a 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards dd433b4420 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards c8bf6a03cf 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 3caa2c447c 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 8c4d20c104 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 80d01fc73a 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards fb7c9c1a53 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards b350273bfb 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 9e04678d01 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 0a681be15d 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 7bd2195f55 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards c912562c2c 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards d7a79745a4 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2515396058 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1c8216536e 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 215edec3a4 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 41331744a4 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 006281681f 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 2b7ff71481 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards e6717fd332 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards f879448cae 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 7bc67ea73c 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards c28d77d885 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards cd5ad136c0 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 262023bd29 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 929e5d2388 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e36b4ff520 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 4898ced993 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a542241359 74: onsuccess: 1: Successful build after linux: 44 commits discards 33acda8e4f 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 30b3196b1f 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c7ea99df3f 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards f82c035e67 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 634d523c1b 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards dd15e0c069 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dc5173138e 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cc16f96b33 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c6932390a8 65: onsuccess: 1: Successful build after gcc: 4 commits discards 01e2800c2a 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2c0f53d65d 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5b99bef05f 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 2a6bf43910 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards ee1e6db7d6 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards e719a90bf5 59: onsuccess: 1: Successful build after glibc: 2 commits discards 7c15787702 58: onsuccess: 1: Successful build after binutils: 2 commits discards 17eec55130 57: onsuccess: 1: Successful build after gcc: 7 commits discards 3f946d6c5c 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b99573bfd6 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fea5c7955c 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards f23f5c1c55 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards c3f3e6c088 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards dd7a2bf2e8 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ecb16f14b4 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4c4f0ac824 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 671ff536d9 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards a3af03175b 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 06a3a6a2a2 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 785a12f705 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7ad547a5be 44: onsuccess: 1: Successful build after linux: 34 commits discards 399f5b106d 43: onsuccess: 1: Successful build after gcc: 2 commits discards a8d9133b83 42: onsuccess: 1: Successful build after baseline build: no [...] discards 2636640f33 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a6b5c4e725 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards efb64e088f 39: onsuccess: 1: Successful build after gcc: 2 commits discards 02182fecf2 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 33c873156a 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ee58f11edb 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b118770ed7 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 57b66db3d0 34: onsuccess: 1: Successful build after gcc: 3 commits discards 0005672bd2 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b346af96ee 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards df4861eeff 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2f873fa467 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards 07984f40f9 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 32276625e0 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 5ef3014886 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2b9f8f8c88 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a1b3e72047 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 400806b5f7 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 55d59f0d55 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e91b49737f 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 22be63e70e 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8cb8d8298a 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ede28b4f5e 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 5b48981281 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7c0569514d 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 79dca063d3 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new edae2643fd 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new a8e09635f5 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9c727079b3 34: onsuccess: 1: Successful build after gcc: 3 commits new 334a3b5f32 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 9a392f5eec 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 916008c119 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 032ee63563 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a3e0ac3c95 39: onsuccess: 1: Successful build after gcc: 2 commits new cd97febc87 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 26c93be87d 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1da6c7868a 42: onsuccess: 1: Successful build after baseline build: no [...] new cdd85c91f2 43: onsuccess: 1: Successful build after gcc: 2 commits new cbfdffc5bc 44: onsuccess: 1: Successful build after linux: 34 commits new 968132f4bc 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cb881ee799 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 0c2355bed1 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 74a3664be2 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 90394a2b59 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2006b09be5 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 18a66cb425 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 402817973c 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 463d78dc49 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 909e7be8e9 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 191260d3b3 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 15b635b6ed 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 98ac556aec 57: onsuccess: 1: Successful build after gcc: 7 commits new 9b915a5061 58: onsuccess: 1: Successful build after binutils: 2 commits new 153fb8aafe 59: onsuccess: 1: Successful build after glibc: 2 commits new 1980ae4567 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 8d835cc2ba 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new adddf69665 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new a1bc261548 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b61d9ba596 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c436e6e6ea 65: onsuccess: 1: Successful build after gcc: 4 commits new a94b2ff495 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c0c3c26877 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7399ae6c3f 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d9be1a4a66 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new f5d4bf5b6e 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 58ae66ba9a 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new e96a9423d2 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ea0366c129 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 5885f4cf71 74: onsuccess: 1: Successful build after linux: 44 commits new b005e0f7a3 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 44fdd7a3ca 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new a84df03623 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3de5ae1820 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3e022fe118 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new a3d1dcb5fa 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 67869b56ce 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new e431a2bcd2 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 0b41be28e3 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 5e3745d3b0 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 09b612c442 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 70bef01e15 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new da57bb5568 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 780ac4ee17 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 0d345dd617 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new e31aae9e78 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 54bbae9930 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 15eb1b8125 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new b938de70f9 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 43406dae6a 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new b41730ef41 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new bd33b3ba80 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new b8f6e369e7 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 6a17c3852e 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 3f960fae19 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new b59d40514b 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 620c491846 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 207e33be9e 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new d026685872 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new dc17df05c7 104: onsuccess: #1697: 1: Success after gcc: 4 commits new d60d0f5bf6 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 0efc94703a 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 3bbadcbdbe 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 8df0d21862 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 11b1a9d6ad 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 41242bc7f5 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 0ae614946f 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new ca884d3e4b 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new bcf3c4996d 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 60f714402f 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 9fdcb5fb32 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 97e2874bea 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new b3d9cbe7c7 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 343959b0d8 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 21477532e7 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new d3b2b1738c 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 7a1f306ac1 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new a42b65ce05 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 817f4fbe27 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 44733f0d14 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new ce917f99c7 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits 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 (2f260e26c9) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1744 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30032 -> 30276 bytes 04-build_abe-stage1/console.log.xz | Bin 90540 -> 91064 bytes 06-build_abe-linux/console.log.xz | Bin 8808 -> 8836 bytes 07-build_abe-glibc/console.log.xz | Bin 233776 -> 233672 bytes 08-build_abe-stage2/console.log.xz | Bin 223020 -> 223792 bytes 09-build_abe-gdb/console.log.xz | Bin 37228 -> 37608 bytes 10-build_abe-qemu/console.log.xz | Bin 31256 -> 31000 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2440 -> 3124 bytes 13-check_regression/console.log.xz | Bin 5348 -> 5656 bytes 13-check_regression/results.compare | 14 - 13-check_regression/results.compare2 | 54 +- 14-update_baseline/console.log | 66 +- 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 | 32 +- sumfiles/g++.log.xz | Bin 2651708 -> 2666820 bytes sumfiles/g++.sum | 52 +- sumfiles/gcc.log.xz | Bin 2207648 -> 2199392 bytes sumfiles/gcc.sum | 2401 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 879888 -> 881392 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201268 -> 201200 bytes sumfiles/libgomp.sum | 8 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 426708 -> 428188 bytes sumfiles/libstdc++.sum | 8 +- 37 files changed, 1345 insertions(+), 1312 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap updated (76540e1b69 -> 8fc803ea3a)

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-aarch64-bootstrap in repository toolchain/ci/base-artifacts. discards 76540e1b69 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards 16f50db6fc 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards 298d40a9a7 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards 236ca15d15 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 01bf6b40a7 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards 201a306e90 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards 3766c68cfa 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards 500f95dbd0 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 670eb4aeea 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 5cd78fe3af 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 1cfd45ab23 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards 9938ab1634 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 23b2d0b028 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards a13fb6d4e9 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards 05408733f8 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards b3d82ff0aa 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 7ed15e39a7 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards fac94f4332 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards 74f65273bf 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 4a17a1fe77 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 4bc7c7f4cf 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards b6a4d13c3a 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards d882c94f1f 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards c023a17005 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards c5104705fc 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards 2ca3f4197a 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards ff4cf8f26a 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards 87acbddd18 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards f82cf5db3d 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 1da91e1fce 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards 3ffa32a4da 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards a72e7a2755 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards bbb38a36d5 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards ea3fd4f2bc 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards bf295f4b22 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards ff7b796ca4 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 64a6b781ed 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 799a4b42ae 88: onsuccess: 1: Success after gcc: 20 commits discards 442f95e73a 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards 6bb456a4e6 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards 55b219c5a7 85: onsuccess: 2: Success after binutils: 4 commits discards 85f9bf1fab 84: onsuccess: 2: Success after gcc: 9 commits discards 8967b82abf 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 2ef88b1226 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards a32a8ddd06 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 7a58becd56 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards b87cfbdb52 79: onsuccess: 1: Successful build after gcc: 3 commits discards 0081d60a18 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards b9024e52f4 77: force: 2: Successful build after gcc: 32 commits discards edc514aa13 76: onsuccess: 2: Successful build after binutils: 10 commits discards c06cad2ac7 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 07ad20e4ae 74: onsuccess: 2: Successful build after gcc: 13 commits discards 0a49296355 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 5ebf5caaa1 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 12ba011abd 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 4c6a4d98af 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards b846e2a288 69: onsuccess: 2: Successful build after baseline build: no [...] discards 1fb1ed7a45 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards fb390a9ac0 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards af37595c3b 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards b0a2016e72 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards ccc1959290 64: onsuccess: 2: Successful build after gcc: 7 commits discards 1d06802350 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards c7c88d0d3e 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards abcb4eb382 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 721909222a 60: onsuccess: 1: Successful build after gcc: 15 commits discards dd7d119dd3 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 69a344bdcf 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards 87c588c0e0 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 62688ec6b8 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 90f3d37fc1 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards d1da4434ef 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards f0e2714d08 53: onsuccess: 2: Successful build after gcc: 5 commits discards 37d3b8d886 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 378f309bce 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 9fb1275b62 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 4cd43a5225 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 43068431b6 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards b51ae64d03 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 2010ac3b10 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards ddc091e7a2 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards 4e38aa9c88 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards b2e6973ce2 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards fa5f5c8d9b 42: onsuccess: 2: Successful build after gcc: 2 commits discards 7999368fd0 41: onsuccess: 2: Successful build after baseline build: no [...] discards 6f09ee7693 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards a9b000fc49 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards c6cdc3fb66 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 4356068f98 37: onsuccess: 2: Successful build after gcc: 2 commits discards 326c1ffb9b 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 64bfa906fb 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards e5d4a78679 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 76c7c7b49f 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards c0f1b33b68 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 32317af3d7 31: onsuccess: 2: Successful build after gcc: 8 commits discards 2bd80f5331 30: onsuccess: 2: Successful build after gcc: 7 commits discards 3cb25474a3 29: onsuccess: 2: Successful build after binutils: 5 commits discards b5400579ee 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 0a8d277687 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 38dae28294 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits discards c6cee18ea0 25: onsuccess: binutils-gcc: 2 new e1718860ec 25: onsuccess: binutils-gcc: 2 new 6c8e6e5bf5 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits new 6a05294c1b 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 79b13cee09 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 1c76c09dd8 29: onsuccess: 2: Successful build after binutils: 5 commits new 09afc00493 30: onsuccess: 2: Successful build after gcc: 7 commits new 5ad1a0221d 31: onsuccess: 2: Successful build after gcc: 8 commits new 6c3a5e3aed 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits new f8ef74a754 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 2a83756d81 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits new fb321cf78f 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 5d597a2c95 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 7115490022 37: onsuccess: 2: Successful build after gcc: 2 commits new 33273b0f5a 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 8099a86f54 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 659b9ad1e7 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 522b119dc5 41: onsuccess: 2: Successful build after baseline build: no [...] new 57ea789387 42: onsuccess: 2: Successful build after gcc: 2 commits new ea285d0f25 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new e82cedd209 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new cc1252bdd9 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 8e50bfcd05 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 7d00695b78 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 1921a7339e 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 53ad862cc2 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new acf2a2cca2 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 796eb05893 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 573393e4e8 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 5cdfc81875 53: onsuccess: 2: Successful build after gcc: 5 commits new 86c15536eb 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 3780015863 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 496550ef0c 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 2aed6a0f5c 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new ab681f2513 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new d459d116bd 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new bd416857c8 60: onsuccess: 1: Successful build after gcc: 15 commits new a27f7f2f03 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 2fe47b9a27 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new fe1838cdc2 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 711871ab2a 64: onsuccess: 2: Successful build after gcc: 7 commits new ab02f03fab 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new cb8680dd15 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new f319a73ca6 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new caf16ec007 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new bf5f915ae7 69: onsuccess: 2: Successful build after baseline build: no [...] new 5e70eba435 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 1662970478 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new b84bf02ec8 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 40486a0b6c 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 4355f440ec 74: onsuccess: 2: Successful build after gcc: 13 commits new 29bcceb3de 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 4b2bceb857 76: onsuccess: 2: Successful build after binutils: 10 commits new 2004aa409e 77: force: 2: Successful build after gcc: 32 commits new f539748e8f 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new cb5dd443ba 79: onsuccess: 1: Successful build after gcc: 3 commits new f42c141aca 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 4af283ce0f 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 497c205711 82: onsuccess: 2: Success after binutils/gcc: 26 commits new db05e26cdf 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 2f86dfa2bc 84: onsuccess: 2: Success after gcc: 9 commits new 077875a473 85: onsuccess: 2: Success after binutils: 4 commits new 4657729f73 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new 9ca727a2d1 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new 4d28ce934a 88: onsuccess: 1: Success after gcc: 20 commits new 54fb74a77b 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 8fc310d1e3 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 1d3d8bd3e3 91: onsuccess: #1473: 2: Success after gcc: 2 commits new e6ff4e691f 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new f4d3589ae5 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new 2ca825ff05 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new 6bc77f33d7 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new d2491ea7b5 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 7a0486db7f 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 9164f80518 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 6fbd617cfb 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 005bb12f87 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new 81e842251a 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new 031ed2838a 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 6c5321d3de 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 9d85a7862a 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new ed560fadac 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 2ec7179b2b 106: onsuccess: #1527: 2: Success after gcc: 2 commits new df049c8b8d 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new 052c8f2539 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 2e7e5ded9d 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 09a120c5ae 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 4e33b23a70 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 962cf5105e 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 8c172a48fd 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new ff62d37638 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new e5227d2e7c 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 46aee3d2a5 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 83083c56c7 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new e07c72c31c 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 5f95fc8998 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new 98f6eab8ef 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new d41d430891 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new ef8934a84c 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 1b1e8412f9 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 707a543918 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new 4c6ffc35ef 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new 8fc803ea3a 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] 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 (76540e1b69) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] 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 1672 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 37812 -> 37884 bytes 05-build_abe-bootstrap/console.log.xz | Bin 272892 -> 268992 bytes 06-check_regression/console.log.xz | Bin 2648 -> 2552 bytes 07-update_baseline/console.log | 64 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 ++++---- 12 files changed, 44 insertions(+), 44 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto_lean updated (5fc720e1c7 -> b0acb2ad2d)

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_profiled_lto_lean in repository toolchain/ci/base-artifacts. from 5fc720e1c7 42: onsuccess: #417: 2: Success after binutils/gcc: 40 commits new b0acb2ad2d 43: onsuccess: #420: 2: Success after binutils/gcc: 134 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 1708 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2700 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 50464 -> 50252 bytes .../console.log.xz | Bin 941752 -> 946072 bytes 06-check_regression/console.log.xz | Bin 2324 -> 3124 bytes 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 | 19 ++++++++++--------- 12 files changed, 16 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-norov-allmodconfig updated (39286a78a0 -> 50d4fb14b6)

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-arm-norov-allmodconfig in repository toolchain/ci/base-artifacts. from 39286a78a0 10: onsuccess: #42: all: Success after binutils/gcc/linux/qe [...] new 50d4fb14b6 11: onsuccess: #43: all: 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 1700 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30184 -> 29900 bytes 04-build_abe-stage1/console.log.xz | Bin 86488 -> 86664 bytes 05-build_abe-qemu/console.log.xz | Bin 31116 -> 30936 bytes 06-build_linux/console.log.xz | Bin 3444 -> 3412 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 2976 -> 4168 bytes 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 | 31 ++++++++++++++++--------------- 17 files changed, 24 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022