Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap updated (f2f5b5f2e -> 41ccb65b4)

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 in repository toolchain/ci/base-artifacts. from f2f5b5f2e 13: onsuccess: #120: 2: Success after binutils/gcc: 10 commits new 41ccb65b4 14: onsuccess: #121: 2: Success after binutils/gcc: 12 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 1660 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2712 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 50504 -> 50768 bytes 05-build_abe-bootstrap/console.log.xz | Bin 458260 -> 460824 bytes 06-check_regression/console.log.xz | Bin 2152 -> 2148 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 | 18 +++++++++--------- 12 files changed, 15 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_gcc_bootstrap/master-arm-bootstrap updated (21b9e7650 -> 877bc9da6)

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 21b9e7650 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards 09018cce4 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards adfc0b0cc 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards 345fbf4d6 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards bb5fe266d 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards e6359ce4b 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards c147d663b 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards f376a863a 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards 1d146103d 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards ac104fbac 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-271 [...] discards d739d3243 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 1b95552f6 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-271 [...] discards 4d529ac47 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards b614ce784 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards 276cd663c 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards ac089fa4b 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 294434d4e 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards c633776b3 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards 56e325cce 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards d6ff45aee 99: onsuccess: #1455: 2: Success after baseline build: no new [...] discards 5bd2b8c27 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-2393 [...] discards 67cb4c6ae 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 0ab670b70 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 3c0bf23a4 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-2389 [...] discards e8ba681ce 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP 5 [...] discards 7fc03699e 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards a5936ece3 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards 955668013 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards 53eac3ffd 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards 42e0eb00c 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards e46ccf042 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards 7b88c346f 87: onsuccess: 2: Success after gcc: 4 commits discards 8139bf559 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards 72b96e133 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 61dbc1d9e 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 1e0221091 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards aff9e3ae7 82: onsuccess: 1: Successful build after gcc: 3 commits discards 490b6bcb9 81: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] discards 1799b45bb 80: force: 2: Successful build after gcc: 14 commits discards d645a7436 79: onsuccess: 2: Successful build after binutils: 5 commits discards 8958da0e9 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards 74451bc82 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards a1d0e2bea 76: onsuccess: 2: Successful build after gcc: 12 commits discards d6d86054d 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards fe9818146 74: onsuccess: 2: Successful build after baseline build: no n [...] discards 0bf39a18e 73: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] discards e6a2f4652 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards cb36ce010 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards fb110fd6f 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 58e4d2f75 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 4d9408e5c 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 13ca0cc6b 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 32f3cfa0b 66: onsuccess: 2: Successful build after gcc: 9 commits discards 8e98146d5 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 155c67250 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 1debff8bd 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards f108813ff 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 71472a644 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards a15d8d327 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards ca523678d 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] discards ccb2f77a9 58: force: 2: Successful build after gcc: 6 commits discards d9767e59b 57: onsuccess: 2: Successful build after binutils: gdb: new ' [...] discards 5f0fb0933 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards e2c72298c 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 15ca5c2bc 54: onsuccess: 2: Successful build after gcc: 5 commits discards 1d75e7b11 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 4ecb9379a 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 2dbb70cfc 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 933223915 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards ad547ec44 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards a03dc6ef2 48: onsuccess: 2: Successful build after gcc: 4 commits discards 69a117ce7 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 8c853bce7 46: onsuccess: 2: Successful build after baseline build: no n [...] discards 4386afcf6 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards 01b2c1d99 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 13b80be64 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] discards af4c71910 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] discards fe620ea4d 41: onsuccess: 2: Successful build after gcc: libcpp: Impleme [...] discards 71ad6759c 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 4d0dfb119 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 9589a6f6f 38: onsuccess: 2: Successful build after gcc: 2 commits discards c0bbab43a 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards bb9c6e528 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 199ec5aba 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 454d55b72 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards e185584c9 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 856f02cdd 32: onsuccess: 2: Successful build after gcc: 6 commits discards 4c9d05c9c 31: onsuccess: 2: Successful build after gcc: 6 commits discards 8beec8054 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards ffef4fb03 29: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 43b9ad337 28: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 6d04ce758 27: onsuccess: 2: Successful build after binutils/gcc: 14 commits discards 43e9f64e3 26: onsuccess: binutils-gcc: 2 discards ede95d765 25: onsuccess: binutils-gcc: 2 discards 8fe368047 24: onsuccess: binutils-gcc: 2 discards aaedbb113 23: onsuccess: binutils-gcc: 2 discards 9c9011581 22: onsuccess: binutils-gcc: 2 discards 2801b46e7 21: onsuccess: binutils-gcc: 2 discards 5919834a4 20: onsuccess: binutils-gcc: 2 discards ff54eec5e 19: onsuccess: binutils-gcc: 2 discards cdf04916e 18: onsuccess: binutils-gcc: 2 new ac4d8d6a7 18: onsuccess: binutils-gcc: 2 new 67fef4277 19: onsuccess: binutils-gcc: 2 new 89400144f 20: onsuccess: binutils-gcc: 2 new 5b860c852 21: onsuccess: binutils-gcc: 2 new 884e99c95 22: onsuccess: binutils-gcc: 2 new be249cb35 23: onsuccess: binutils-gcc: 2 new 1f2cae16b 24: onsuccess: binutils-gcc: 2 new 2e4d3abb9 25: onsuccess: binutils-gcc: 2 new 304fbff42 26: onsuccess: binutils-gcc: 2 new d6db6899b 27: onsuccess: 2: Successful build after binutils/gcc: 14 commits new aafdefb9e 28: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 2100eb3cf 29: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 9213b87e6 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits new fc8d01865 31: onsuccess: 2: Successful build after gcc: 6 commits new abc67e4e2 32: onsuccess: 2: Successful build after gcc: 6 commits new c2a7c82c8 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 6db734863 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits new ab0e0a172 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits new a249371d3 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 532237c9c 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 859e6e90b 38: onsuccess: 2: Successful build after gcc: 2 commits new 3580c67ef 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits new cddca98f3 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new adff008e4 41: onsuccess: 2: Successful build after gcc: libcpp: Impleme [...] new 3506c7a6b 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] new 480b60885 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] new 1e6c05822 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new d27fe0bc7 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 00c248172 46: onsuccess: 2: Successful build after baseline build: no n [...] new 4271c0a32 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits new b52d0f380 48: onsuccess: 2: Successful build after gcc: 4 commits new 4b1a3626e 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 062063580 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new b13e3eaa9 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 803d08a15 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 07620f0fb 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new f4899aa5b 54: onsuccess: 2: Successful build after gcc: 5 commits new 3dc58d1d2 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 85b0cb8d2 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 5877272e3 57: onsuccess: 2: Successful build after binutils: gdb: new ' [...] new cd5a626a0 58: force: 2: Successful build after gcc: 6 commits new 233219efe 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] new b6a531f21 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 05886d344 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new 9c2e36f1b 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 5b90f5ff1 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 0adad9f1e 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 1a3767af4 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 316393f1d 66: onsuccess: 2: Successful build after gcc: 9 commits new 071f7250a 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new ea3a9f50c 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 37ab5dc05 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new e5ee1bbdd 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 0020f16b8 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 6dac159f8 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 40722b367 73: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] new 9fcf70509 74: onsuccess: 2: Successful build after baseline build: no n [...] new ea2d23e98 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 8541f47f0 76: onsuccess: 2: Successful build after gcc: 12 commits new 77dce1c4c 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new ef0b0a8c5 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new 287acb179 79: onsuccess: 2: Successful build after binutils: 5 commits new 52cb3a406 80: force: 2: Successful build after gcc: 14 commits new 1a5688160 81: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] new 07ddaa730 82: onsuccess: 1: Successful build after gcc: 3 commits new ef49f0721 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new cee2f5fbb 84: onsuccess: 2: Success after binutils/gcc: 15 commits new 2e58f88fb 85: onsuccess: 2: Success after binutils/gcc: 25 commits new 801b795bb 86: onsuccess: 2: Success after binutils/gcc: 10 commits new ab94d0798 87: onsuccess: 2: Success after gcc: 4 commits new dab547e8d 88: onsuccess: 2: Success after binutils/gcc: 25 commits new 70881bbcc 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 2709b5672 90: onsuccess: 2: Success after binutils/gcc: 16 commits new abb130052 91: onsuccess: 2: Success after binutils/gcc: 7 commits new 3003f2aae 92: onsuccess: 2: Success after binutils/gcc: 9 commits new 15f08f538 93: onsuccess: 2: Success after binutils/gcc: 3 commits new ffb765568 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP 5 [...] new a3488dce0 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-2389 [...] new 33d81d6a9 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 9a5ac2d49 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new 603512560 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-2393 [...] new a80eedacc 99: onsuccess: #1455: 2: Success after baseline build: no new [...] new bf03a5905 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new c0af94a70 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new 6e69b52ff 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new c9798cbe4 103: onsuccess: #1504: 2: Success after gcc: 2 commits new 63c31ac2e 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new c8caf364a 105: onsuccess: #1506: 2: Success after gcc: 2 commits new e23e2d620 106: onsuccess: #1507: 2: Success after gcc: 2 commits new f0465060a 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-271 [...] new 512cdc792 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new f391c4385 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-271 [...] new 3743815fe 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new 16cd347da 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new 253db6d3d 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new 8c9bd2f9c 113: onsuccess: #1514: 2: Success after gcc: 5 commits new 7eb397571 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new 14775e61d 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new f7726bc4f 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new 8286586aa 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new dca45aaf3 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new 877bc9da6 119: onsuccess: #1520: 2: Success after binutils: 8 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 (21b9e7650) \ 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 1672 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2704 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 50476 -> 50204 bytes 05-build_abe-bootstrap/console.log.xz | Bin 466292 -> 463980 bytes 06-check_regression/console.log.xz | Bin 2244 -> 1968 bytes 07-update_baseline/console.log | 34 +++++++++++++++++----------------- 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 | 12 ++++++------ 12 files changed, 28 insertions(+), 28 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_bmk_llvm_tk1/llvm-master-arm-spec2k6-O3 updated (249c12d7c -> bf60c0f79)

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_llvm_tk1/llvm-master-arm-spec2k6-O3 in repository toolchain/ci/base-artifacts. from 249c12d7c 19: onsuccess: #341: 1: [TCWG CI] No change after binutils/gc [...] new bf60c0f79 20: onsuccess: #342: 1: [TCWG CI] No change after binutils/gc [...] 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 1760 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30316 -> 30384 bytes 04-build_abe-stage1/console.log.xz | Bin 91684 -> 91020 bytes 06-build_abe-linux/console.log.xz | Bin 8624 -> 8668 bytes 07-build_abe-glibc/console.log.xz | Bin 235336 -> 233268 bytes 08-build_abe-stage2/console.log.xz | Bin 211976 -> 209456 bytes 09-build_llvm-true/console.log.xz | Bin 62660 -> 63112 bytes 10-benchmark/benchmark-build.log | 124 +- 10-benchmark/benchmark.log | 122 +- 10-benchmark/console.log.xz | Bin 3952 -> 3916 bytes 11-check_regression/console.log.xz | Bin 7988 -> 8612 bytes 11-check_regression/csv-results-0/md5sum.csv | 24707 +- 11-check_regression/csv-results-0/perf.csv | 1781 +- 11-check_regression/csv-results-0/results.csv | 245097 ++++++++--------- 11-check_regression/csv-results-0/size.csv | 239162 ++++++++--------- 11-check_regression/csv-results-0/vect.csv | 18968 +- 11-check_regression/csv-results-1/md5sum.csv | 24718 +- 11-check_regression/csv-results-1/perf.csv | 1765 +- 11-check_regression/csv-results-1/results.csv | 246427 +++++++++-------- 11-check_regression/csv-results-1/size.csv | 250432 +++++++++--------- 11-check_regression/csv-results-1/vect.csv | 18990 +- 11-check_regression/results-brief.csv | 30 +- 11-check_regression/results-compare.csv | 8 +- 11-check_regression/results-full.csv | 1815 +- 11-check_regression/results-internal.csv | 118 +- 11-check_regression/results.csv | 118 +- 11-check_regression/results.log | 860 +- dashboard/dashboard-generate.sh | 2 +- .../squad/400.perlbench/results-metadata.json | 18 +- dashboard/squad/401.bzip2/results-metadata.json | 18 +- dashboard/squad/403.gcc/results-metadata.json | 18 +- dashboard/squad/403.gcc/results-metrics.json | 4 +- dashboard/squad/429.mcf/results-metadata.json | 18 +- dashboard/squad/429.mcf/results-metrics.json | 2 +- dashboard/squad/433.milc/results-metadata.json | 18 +- dashboard/squad/433.milc/results-metrics.json | 4 +- dashboard/squad/444.namd/results-metadata.json | 18 +- dashboard/squad/445.gobmk/results-metadata.json | 18 +- dashboard/squad/445.gobmk/results-metrics.json | 4 +- dashboard/squad/447.dealII/results-metadata.json | 18 +- dashboard/squad/447.dealII/results-metrics.json | 2 +- dashboard/squad/450.soplex/results-metadata.json | 18 +- dashboard/squad/450.soplex/results-metrics.json | 2 +- dashboard/squad/453.povray/results-metadata.json | 18 +- dashboard/squad/456.hmmer/results-metadata.json | 18 +- dashboard/squad/458.sjeng/results-metadata.json | 18 +- dashboard/squad/458.sjeng/results-metrics.json | 2 +- .../squad/462.libquantum/results-metadata.json | 18 +- .../squad/462.libquantum/results-metrics.json | 2 +- dashboard/squad/464.h264ref/results-metadata.json | 18 +- dashboard/squad/464.h264ref/results-metrics.json | 4 +- dashboard/squad/470.lbm/results-metadata.json | 18 +- dashboard/squad/470.lbm/results-metrics.json | 2 +- dashboard/squad/471.omnetpp/results-metadata.json | 18 +- dashboard/squad/471.omnetpp/results-metrics.json | 2 +- dashboard/squad/473.astar/results-metadata.json | 18 +- dashboard/squad/473.astar/results-metrics.json | 2 +- dashboard/squad/482.sphinx3/results-metadata.json | 18 +- dashboard/squad/482.sphinx3/results-metrics.json | 2 +- .../squad/483.xalancbmk/results-metadata.json | 18 +- dashboard/squad/483.xalancbmk/results-metrics.json | 4 +- dashboard/squad/Mean/results-metadata.json | 18 +- dashboard/squad/Mean/results-metrics.json | 2 +- dashboard/squad/dashboard-push-squad.sh | 82 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 54 +- mail/mail-body.txt | 54 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 1358504 -> 1356352 bytes save-temps/403.gcc.tar.xz | Bin 3764360 -> 3770652 bytes save-temps/429.mcf.tar.xz | Bin 35352 -> 35028 bytes save-temps/433.milc.tar.xz | Bin 161560 -> 161056 bytes save-temps/445.gobmk.tar.xz | Bin 2128424 -> 2134344 bytes save-temps/447.dealII.tar.xz | Bin 3374444 -> 3389932 bytes save-temps/450.soplex.tar.xz | Bin 529976 -> 539740 bytes save-temps/458.sjeng.tar.xz | Bin 170056 -> 170672 bytes save-temps/462.libquantum.tar.xz | Bin 53576 -> 53392 bytes save-temps/464.h264ref.tar.xz | Bin 715964 -> 713720 bytes save-temps/470.lbm.tar.xz | Bin 25632 -> 25696 bytes save-temps/471.omnetpp.tar.xz | Bin 911384 -> 889464 bytes save-temps/473.astar.tar.xz | Bin 76168 -> 76188 bytes save-temps/482.sphinx3.tar.xz | Bin 239648 -> 239780 bytes save-temps/483.xalancbmk.tar.xz | Bin 7191688 -> 7246976 bytes 90 files changed, 516101 insertions(+), 559787 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-master-arm-stable-allnoconfig updated (7b9ab02cd -> d368cee05)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-allnoconfig in repository toolchain/ci/base-artifacts. from 7b9ab02cd 10: onsuccess: #368: all: Success after binutils/gcc/linux: 2 [...] new d368cee05 11: onsuccess: #369: 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 1680 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 30100 -> 31016 bytes 04-build_abe-stage1/console.log.xz | Bin 91160 -> 91076 bytes 05-build_abe-qemu/console.log.xz | Bin 30776 -> 31728 bytes 06-build_linux/console.log.xz | Bin 4124 -> 4148 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 2836 -> 3488 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 | 30 +++++++++++++++--------------- 17 files changed, 23 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/release-aarch64-bootstrap_profiled_lto_lean updated (98fdb9a28 -> 9f60366b5)

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-aarch64-bootstrap_profiled_lto_lean in repository toolchain/ci/base-artifacts. from 98fdb9a28 13: onsuccess: #121: 2: Success after binutils/gcc: 10 commits new 9f60366b5 14: onsuccess: #122: 2: Success after binutils/gcc: 12 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1680 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 38332 -> 37764 bytes .../console.log.xz | Bin 507048 -> 506832 bytes 06-check_regression/console.log.xz | Bin 2148 -> 2236 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 | 18 +++++++++--------- 12 files changed, 15 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 (8951cb121 -> 22cde9678)

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 8951cb121 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits discards 60c696e45 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] discards 0058ae816 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] discards 2bdc20b1d 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] discards 99961427b 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] discards 499cc9eb9 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 35943c8bd 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards e9677b8b0 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards e7d901c2b 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] discards 8169e9382 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] discards f07562444 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] discards c89b44bc4 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 204465d41 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards ea4ee4c26 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards 39b548c97 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards d297d07d6 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards 358ae9079 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards 47e7a1003 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards ada44696e 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 4ea385845 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards ced4d781b 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards 17dbba7a4 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards 030c25770 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards c23a74890 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards abeecc148 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 56e258142 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards a6080c82b 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 09069ef13 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 2eb5e1a2d 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 8b51e4710 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards b3f8a9c34 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 97d60c5ed 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards d2e83efa2 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 7932f56e8 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 173cafbcc 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards a32035bac 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards 6dc9581d3 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards edf4420d0 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 633a76f09 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards cae37149f 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards a8607140a 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e84c5ee53 74: onsuccess: 1: Successful build after linux: 44 commits discards 4eca1653c 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 257656f60 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e6d7dd6d8 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards f9e416aab 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards 05dce6631 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 33e9b715d 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 528dec24f 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a20e4cbb9 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 68b7657ce 65: onsuccess: 1: Successful build after gcc: 4 commits discards 0c0798792 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c69007242 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e50ed1f88 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards ed9271ca9 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards cd847ce8e 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 36f7d44f6 59: onsuccess: 1: Successful build after glibc: 2 commits discards 73014c8f0 58: onsuccess: 1: Successful build after binutils: 2 commits discards 52429cad7 57: onsuccess: 1: Successful build after gcc: 7 commits discards 3c236f934 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f5423acd8 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f85031977 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards c1abade93 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 9030bb9ec 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards f3a56eac3 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 6c0e1c571 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e3cc5ab46 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 14a677087 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 5b24dd166 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 37091e337 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 55eec78d7 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a1263b2ab 44: onsuccess: 1: Successful build after linux: 34 commits discards b85a38097 43: onsuccess: 1: Successful build after gcc: 2 commits discards e35e72af2 42: onsuccess: 1: Successful build after baseline build: no n [...] discards b63a42b38 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards dde7048ea 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 961b4e477 39: onsuccess: 1: Successful build after gcc: 2 commits discards 46e855509 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards cf21f7e83 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 1f280f8e1 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c139193a7 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 0e4a21757 34: onsuccess: 1: Successful build after gcc: 3 commits discards ad6ef1572 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2ff0c5658 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards a898b3866 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 41223042b 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards e3e6afbd2 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 53560cddd 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 37fd1ed70 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards ddd7d5328 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards dff22a881 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9cad60640 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1d538682a 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ea0a43e52 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c348cff7a 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards bcb4b33d9 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards dbcc7e1b0 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 885365f01 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6fa90aaea 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c1990a215 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c37f6dd73 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new fcf74f047 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new def194b0e 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 660e281be 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f9b709198 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 073458d85 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9b1d1b78c 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 995e3856c 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 98b2b03c8 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 182f64879 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2be92279a 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 009a97ee9 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4e7c335fa 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ccad3b1ea 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new f39b15d74 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new a7e3b6128 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 85b7f6490 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 271026865 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new b4c5948c1 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 1f4563fd9 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new bdab61e30 34: onsuccess: 1: Successful build after gcc: 3 commits new b1fd1a924 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 690328bf9 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 14c802a55 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 3765bd27e 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 072cc48ac 39: onsuccess: 1: Successful build after gcc: 2 commits new 965a6603e 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 4818e444e 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 6e3ddee65 42: onsuccess: 1: Successful build after baseline build: no n [...] new acd27d260 43: onsuccess: 1: Successful build after gcc: 2 commits new 11c8948b3 44: onsuccess: 1: Successful build after linux: 34 commits new 7876718be 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 30bce21d6 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 2e48ad7ae 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 91e3de6f2 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 34187088c 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 34a576b3e 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new fd1da8a8d 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new b735aee8d 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 33e6d7e76 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new 00b896f85 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 726556444 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e95826e3b 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 1c205420b 57: onsuccess: 1: Successful build after gcc: 7 commits new f86ce0ddc 58: onsuccess: 1: Successful build after binutils: 2 commits new d591bbb6e 59: onsuccess: 1: Successful build after glibc: 2 commits new f205147ab 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 05ab6deb3 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 06fb3435f 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new 274e0abfe 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f3be12136 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5d0b57414 65: onsuccess: 1: Successful build after gcc: 4 commits new a05ec0b8e 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new aaeea1b37 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f4cfbde4e 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d8239d019 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new f7116effe 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new 06b8f5407 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new f2624098b 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2b928f9b7 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new ef819d1c8 74: onsuccess: 1: Successful build after linux: 44 commits new aabf084d1 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 9614535c1 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new 71112db4d 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new fab0441a9 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 88287b657 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new a4310865a 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new 8bd35a078 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 8ba1a429c 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new de988b29b 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 1030c666a 84: onsuccess: 1: Success after gcc/glibc: 9 commits new f1c88847f 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new e9cd8881e 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 2479ded5d 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 295ecd9cd 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 27d07227f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new b3f4d22d0 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new fb9287ca3 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new d9d29ba05 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new 2c3fdd83a 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new d8158e1ae 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new a7afa17d1 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new e6bfa91c2 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new f79627bea 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new 794b8c36e 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new c7e9ea745 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new f5e1c222f 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new 8a7838888 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 286b3a818 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new 8bb5915de 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new fd359246c 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 209a6e825 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] new 2ce16402d 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] new 508eb97fd 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] new 96643cede 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 413a33b95 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new c3c1cc7e2 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 4fd7231b7 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] new afc43149d 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] new 031e4a645 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] new e4fce6650 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] new 4693dec8a 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits new 22cde9678 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] 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 (8951cb121) \ 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 1884 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 29952 -> 30492 bytes 04-build_abe-stage1/console.log.xz | Bin 90564 -> 91148 bytes 06-build_abe-linux/console.log.xz | Bin 8600 -> 8572 bytes 07-build_abe-glibc/console.log.xz | Bin 233832 -> 233956 bytes 08-build_abe-stage2/console.log.xz | Bin 222932 -> 224564 bytes 09-build_abe-gdb/console.log.xz | Bin 37220 -> 37412 bytes 10-build_abe-qemu/console.log.xz | Bin 30924 -> 31924 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3916 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2644 -> 2664 bytes 13-check_regression/console.log.xz | Bin 5632 -> 6124 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 11 +- 13-check_regression/mail-body.txt | 94 +- 13-check_regression/results.compare | 46 +- 13-check_regression/results.compare2 | 71 +- 13-check_regression/results.regressions | 46 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 96 +- mail/mail-subject.txt | 2 +- manifest.sh | 46 +- results | 46 +- sumfiles/g++.log.xz | Bin 2678388 -> 2659592 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2207716 -> 2236176 bytes sumfiles/gcc.sum | 2390 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 882024 -> 879836 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201344 -> 201056 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2672 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 421944 -> 423440 bytes sumfiles/libstdc++.sum | 6 +- 45 files changed, 1395 insertions(+), 1553 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 (6eb851adc -> 80a33b8cd)

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 6eb851adc 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards c15c887b7 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 543cc4432 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards afb860e8e 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards aac66b181 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards aefd3f3f6 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards 32a6aaf94 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards e4d5d03b4 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 71be4773f 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards aed7d7fd6 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-271 [...] discards 1923ce36e 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 468a26b71 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards c8f93a13c 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards 8e8dbe919 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards daf1c2425 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards b627f51cd 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards 5dffd20ab 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards e463080f0 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards eb7709e2d 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards 9ae8fdff2 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards bfaecfba8 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards e3e6dadb4 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards 7d332be8a 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards b7f518c53 94: onsuccess: #1476: 2: Success after baseline build: no new [...] discards 19e663ecf 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-2393 [...] discards 5641a4534 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 7652d2177 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 4791ab5e3 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 337972be3 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards caeabcc4b 88: onsuccess: 1: Success after gcc: 20 commits discards 1bb88dc24 87: force: 1: Failure after gcc: Fix up dump_printf_loc forma [...] discards 2b228550a 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 w [...] discards c60d885d0 85: onsuccess: 2: Success after binutils: 4 commits discards 2f8c8156b 84: onsuccess: 2: Success after gcc: 9 commits discards 7cc9c1c24 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards e9787a068 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards a477772c4 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards bc1c1f90c 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 55b5606e5 79: onsuccess: 1: Successful build after gcc: 3 commits discards 2165bd013 78: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] discards b1be05012 77: force: 2: Successful build after gcc: 32 commits discards 66e97f339 76: onsuccess: 2: Successful build after binutils: 10 commits discards d7fa13464 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 5993ff801 74: onsuccess: 2: Successful build after gcc: 13 commits discards d75e031f9 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 94780886b 72: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] discards 701f39029 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 009362703 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards dd5622227 69: onsuccess: 2: Successful build after baseline build: no n [...] discards 3d826b81f 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 2e5cbef3d 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 342d41835 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards a40c0ee48 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 409ad6c40 64: onsuccess: 2: Successful build after gcc: 7 commits discards 5914c7225 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 7a8d6ceff 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 7dc6162fa 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 72c233742 60: onsuccess: 1: Successful build after gcc: 15 commits discards a7b391e0c 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] discards 4748c8552 58: force: 2: Successful build after gcc: tree.cc: Fix optimi [...] discards cb215e78f 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 458f9c8cf 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards da6ab3b46 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards e2a264f94 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards a690ad0a8 53: onsuccess: 2: Successful build after gcc: 5 commits discards fb8422b60 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 2218fa902 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards a1b201a69 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 9d41a51e3 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 62f4a423c 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards a98655371 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards f79304ddd 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 2a43e44da 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards b60b7941c 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 136f6120f 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] discards 4d4360c8a 42: onsuccess: 2: Successful build after gcc: 2 commits discards 9cf86505f 41: onsuccess: 2: Successful build after baseline build: no n [...] discards 5474f1df6 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 6b240d9ad 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 19a0aa627 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 1d9e1860d 37: onsuccess: 2: Successful build after gcc: 2 commits discards 642de5627 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards d893e8690 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards c7f14c80e 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 4beb591e7 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards b896252b9 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 621c2a0c8 31: onsuccess: 2: Successful build after gcc: 8 commits discards 464affaef 30: onsuccess: 2: Successful build after gcc: 7 commits discards b6bdd4ee8 29: onsuccess: 2: Successful build after binutils: 5 commits discards 6ae6d31e9 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards bb1f64122 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards ccd7e675e 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits discards 482c1842a 25: onsuccess: binutils-gcc: 2 discards d002822eb 24: onsuccess: binutils-gcc: 2 discards dc45269db 23: onsuccess: binutils-gcc: 2 discards b496bf036 22: onsuccess: binutils-gcc: 2 discards eb8043e5e 21: onsuccess: binutils-gcc: 2 discards 40e13c3c3 20: onsuccess: binutils-gcc: 2 discards 280b67aae 19: onsuccess: binutils-gcc: 2 discards 93146c87d 18: onsuccess: binutils-gcc: 2 discards 528d4cf77 17: onsuccess: binutils-gcc: 2 new db0fe7579 17: onsuccess: binutils-gcc: 2 new eef99181c 18: onsuccess: binutils-gcc: 2 new ed51b3f4c 19: onsuccess: binutils-gcc: 2 new 4a2c81427 20: onsuccess: binutils-gcc: 2 new b7c355a43 21: onsuccess: binutils-gcc: 2 new 6d2490de4 22: onsuccess: binutils-gcc: 2 new 7064f70f6 23: onsuccess: binutils-gcc: 2 new 03e68a845 24: onsuccess: binutils-gcc: 2 new 39fd59b51 25: onsuccess: binutils-gcc: 2 new 0f71fe556 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits new f599d675e 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits new c16cd2432 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits new f300c3f24 29: onsuccess: 2: Successful build after binutils: 5 commits new c4660030a 30: onsuccess: 2: Successful build after gcc: 7 commits new a9e96e83a 31: onsuccess: 2: Successful build after gcc: 8 commits new e1db477e0 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits new bc87d76a1 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ca4c2193e 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 2d8360cc5 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 838260d43 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits new ddc800698 37: onsuccess: 2: Successful build after gcc: 2 commits new 035a6b173 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 0e3d1b39b 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 07398884a 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new e3bf20484 41: onsuccess: 2: Successful build after baseline build: no n [...] new 9141fddc2 42: onsuccess: 2: Successful build after gcc: 2 commits new 71cd1fb9f 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] new f0f3f5928 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 238cbafe4 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new fa1def125 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new b116f58ca 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 16bf73533 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new effec9b71 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 3dc32632c 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new b9d5ac468 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new c33beace0 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 3d000f821 53: onsuccess: 2: Successful build after gcc: 5 commits new 701b9be9d 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 6037c4d56 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 57626b58f 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 0db5880b5 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 0729c24c3 58: force: 2: Successful build after gcc: tree.cc: Fix optimi [...] new df973ecbc 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] new 2ff359ecc 60: onsuccess: 1: Successful build after gcc: 15 commits new 43af521f7 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new e30779a7c 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new b55125077 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 6c830b809 64: onsuccess: 2: Successful build after gcc: 7 commits new a68f5f3c7 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 2bb4f9d2d 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new fbf752d04 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new f4064e437 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 8d3027fb8 69: onsuccess: 2: Successful build after baseline build: no n [...] new 45f5fb3d7 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new a99e165e4 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 680080c72 72: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] new c1dd3b4d8 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 2b905cd7a 74: onsuccess: 2: Successful build after gcc: 13 commits new 282099c16 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 630cea34e 76: onsuccess: 2: Successful build after binutils: 10 commits new 89c1948f2 77: force: 2: Successful build after gcc: 32 commits new 8767d677d 78: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] new 51e21618d 79: onsuccess: 1: Successful build after gcc: 3 commits new fa56571c0 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 91ff79dd0 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 9a200369a 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 6f80d65c5 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 823df897d 84: onsuccess: 2: Success after gcc: 9 commits new a148d9e1b 85: onsuccess: 2: Success after binutils: 4 commits new 6602e9731 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 w [...] new 058aaec13 87: force: 1: Failure after gcc: Fix up dump_printf_loc forma [...] new d8d35c247 88: onsuccess: 1: Success after gcc: 20 commits new cbaa3a190 89: onsuccess: 2: Success after binutils/gcc: 39 commits new fa22b81c4 90: onsuccess: #1472: 2: Success after gcc: 2 commits new ed722a44e 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 6a703267b 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 6c2fd3caf 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-2393 [...] new 1a6a274df 94: onsuccess: #1476: 2: Success after baseline build: no new [...] new ce1116d12 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 72c8db209 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new a77eac55d 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 51baa2df6 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new a276e0bf4 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 5af7185b6 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new 51647cdec 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new d296459eb 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 78069d24b 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 2dbd1c227 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 6efa01a8d 105: onsuccess: #1526: 2: Success after gcc: 2 commits new a30014553 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 7345e0bff 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new e2eeeb80d 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-271 [...] new 6d5d5e934 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 87419157f 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 1b2712c3f 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new bedd3b491 112: onsuccess: #1533: 2: Success after gcc: 5 commits new f5e04d888 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new fa35bbb6c 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 3ec04453f 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new f283c0dd0 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 0aba52b97 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new 80a33b8cd 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 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 (6eb851adc) \ 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 1692 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 37700 -> 37996 bytes 05-build_abe-bootstrap/console.log.xz | Bin 268944 -> 267816 bytes 06-check_regression/console.log.xz | Bin 2184 -> 2188 bytes 07-update_baseline/console.log | 38 +++++++++++++++++----------------- 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 | 16 +++++++------- 13 files changed, 33 insertions(+), 33 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-aarch64-bootstrap_ubsan updated (a28cca390 -> 6c6eb8960)

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-aarch64-bootstrap_ubsan in repository toolchain/ci/base-artifacts. from a28cca390 13: onsuccess: #120: 2: Success after binutils/gcc: 10 commits new 6c6eb8960 14: onsuccess: #121: 2: Success after binutils/gcc: 12 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 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 37628 -> 38896 bytes 05-build_abe-bootstrap_ubsan/console.log.xz | Bin 319244 -> 321196 bytes 06-check_regression/console.log.xz | Bin 2148 -> 2140 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 | 18 +++++++++--------- 12 files changed, 15 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_bmk_llvm_fx/llvm-master-aarch64-cpu2017rate-O2 created (now 0cbeea6c9)

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_llvm_fx/llvm-master-aarch64-cpu2017rate-O2 in repository toolchain/ci/base-artifacts. at 0cbeea6c9 0: init: #2: 1: [TCWG CI] No change after baseline build: no [...] This branch includes the following new commits: new 0cbeea6c9 0: init: #2: 1: [TCWG CI] No change after baseline build: no [...] 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. -- 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-master-arm-norov-defconfig updated (9a8e2bde2 -> e9385446d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-norov-defconfig in repository toolchain/ci/base-artifacts. from 9a8e2bde2 10: onsuccess: #37: boot: Success after binutils/gcc: 84 commits new e9385446d 11: onsuccess: #38: boot: 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 -> 1896 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30388 -> 30100 bytes 04-build_abe-stage1/console.log.xz | Bin 90840 -> 91764 bytes 05-build_abe-qemu/console.log.xz | Bin 31440 -> 31644 bytes 06-build_linux/console.log.xz | Bin 5512 -> 5540 bytes 07-boot_linux/console.log.xz | Bin 5816 -> 5892 bytes 08-check_regression/console.log.xz | Bin 2456 -> 3408 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 | 30 +++++++++++++++--------------- 17 files changed, 23 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