Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GH-35099: [CI][Packaging] Upgrade vcpkg to 2023.04.15 Release #35430

Merged
merged 3 commits into from May 6, 2023

Conversation

sjperkins
Copy link
Contributor

@sjperkins sjperkins commented May 4, 2023

Rationale for this change

What changes are included in this PR?

This pins vcpkg to the official 2023.04.15 release (commit microsoft/vcpkg@501db0f)

Are these changes tested?

I've successfully test that the following local wheel builds succeed:

$ ARCH=amd64 PYTHON=3.10 archery docker run python-wheel-manylinux-2014
$ ARCH=amd64 PYTHON=3.10 archery docker run python-wheel-manylinux-2-28

Are there any user-facing changes?

I don't believe so

@github-actions
Copy link

github-actions bot commented May 4, 2023

@github-actions
Copy link

github-actions bot commented May 4, 2023

⚠️ GitHub issue #35099 has been automatically assigned in GitHub to PR creator.

@github-actions github-actions bot added the awaiting review Awaiting review label May 4, 2023
ci/vcpkg/ports.patch Show resolved Hide resolved
.env Show resolved Hide resolved
@kou
Copy link
Member

kou commented May 4, 2023

@github-actions crossbow submit wheel-manylinux-* java-jars

@github-actions github-actions bot added awaiting changes Awaiting changes and removed awaiting committer review Awaiting committer review labels May 4, 2023
@github-actions
Copy link

github-actions bot commented May 4, 2023

Revision: 996cd86

Submitted crossbow builds: ursacomputing/crossbow @ actions-821498ff0c

Task Status
java-jars Github Actions
wheel-manylinux-2-28-cp310-amd64 Github Actions
wheel-manylinux-2-28-cp310-arm64 Github Actions
wheel-manylinux-2-28-cp311-amd64 Github Actions
wheel-manylinux-2-28-cp311-arm64 Github Actions
wheel-manylinux-2-28-cp37-amd64 Github Actions
wheel-manylinux-2-28-cp37-arm64 Github Actions
wheel-manylinux-2-28-cp38-amd64 Github Actions
wheel-manylinux-2-28-cp38-arm64 Github Actions
wheel-manylinux-2-28-cp39-amd64 Github Actions
wheel-manylinux-2-28-cp39-arm64 Github Actions
wheel-manylinux-2014-cp310-amd64 Github Actions
wheel-manylinux-2014-cp310-arm64 Github Actions
wheel-manylinux-2014-cp311-amd64 Github Actions
wheel-manylinux-2014-cp311-arm64 Github Actions
wheel-manylinux-2014-cp37-amd64 Github Actions
wheel-manylinux-2014-cp37-arm64 Github Actions
wheel-manylinux-2014-cp38-amd64 Github Actions
wheel-manylinux-2014-cp38-arm64 Github Actions
wheel-manylinux-2014-cp39-amd64 Github Actions
wheel-manylinux-2014-cp39-arm64 Github Actions

@sjperkins
Copy link
Contributor Author

All green, except for the java-jars which looks to be related to a maven timeout?

@kou
Copy link
Member

kou commented May 5, 2023

I've re-ran it.

@sjperkins
Copy link
Contributor Author

Failed again. On both occasions it seems related to transfer of the maven shade plugin?

Error:  Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:3.1.1:shade (default) on project arrow-vector: 
Execution default of goal org.apache.maven.plugins:maven-shade-plugin:3.1.1:shade failed:
Plugin org.apache.maven.plugins:maven-shade-plugin:3.1.1 or one of its dependencies could not be resolved:
Failed to collect dependencies at org.apache.maven.plugins:maven-shade-plugin:jar:3.1.1 -> org.ow2.asm:asm:jar:6.0:
Failed to read artifact descriptor for org.ow2.asm:asm:jar:6.0:
The following artifacts could not be resolved: org.ow2.asm:asm:pom:6.0 (absent):
Could not transfer artifact org.ow2.asm:asm:pom:6.0 from/to apache (https://repo.maven.apache.org/maven2/):
Connection reset -> [Help 1]

@kou
Copy link
Member

kou commented May 5, 2023

Ah, the java-jars nightly builds on main were failed since 2023-05-05:

https://lists.apache.org/list.html?builds@arrow.apache.org

2023-05-04: https://github.com/ursacomputing/crossbow/actions/runs/4880720274/jobs/8715652875
2023-05-05: https://github.com/ursacomputing/crossbow/actions/runs/4891509316/jobs/8732835157

So I think that the failure isn't related to this PR.

Could you open an issue for the failure? Then we can merge this.

Copy link
Member

@assignUser assignUser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 Thanks!

@sjperkins
Copy link
Contributor Author

Could you open an issue for the failure? Then we can merge this.

#35463 opened.

Copy link
Member

@kou kou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

Thanks!

@kou kou merged commit 2c97151 into apache:main May 6, 2023
18 of 19 checks passed
@github-actions github-actions bot added awaiting merge Awaiting merge and removed awaiting changes Awaiting changes labels May 6, 2023
@ursabot
Copy link

ursabot commented May 7, 2023

Benchmark runs are scheduled for baseline = f0e1453 and contender = 2c97151. 2c97151 is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Finished ⬇️0.0% ⬆️0.0%] ec2-t3-xlarge-us-east-2
[Failed ⬇️2.22% ⬆️0.0%] test-mac-arm
[Finished ⬇️0.26% ⬆️0.0%] ursa-i9-9960x
[Failed ⬇️0.0% ⬆️0.0%] ursa-thinkcentre-m75q
Buildkite builds:
[Finished] 2c971511 ec2-t3-xlarge-us-east-2
[Failed] 2c971511 test-mac-arm
[Finished] 2c971511 ursa-i9-9960x
[Failed] 2c971511 ursa-thinkcentre-m75q
[Finished] f0e14539 ec2-t3-xlarge-us-east-2
[Failed] f0e14539 test-mac-arm
[Finished] f0e14539 ursa-i9-9960x
[Failed] f0e14539 ursa-thinkcentre-m75q
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java

@ursabot
Copy link

ursabot commented May 7, 2023

['Python', 'R'] benchmarks have high level of regressions.
test-mac-arm

@sjperkins sjperkins deleted the upgrade-vcpkg branch May 7, 2023 07:01
@kou
Copy link
Member

kou commented May 7, 2023

@github-actions crossbow submit wheel-windows-*

@kou
Copy link
Member

kou commented May 7, 2023

I want to check whether https://github.com/ursacomputing/crossbow/actions/runs/4906241298/jobs/8760550661#step:7:1397 is caused by this or not:

CMake Error at scripts/cmake/z_vcpkg_apply_patches.cmake:34 (message):
  Applying patch failed: error: corrupt patch at line 18

Call Stack (most recent call first):
  scripts/cmake/vcpkg_extract_source_archive.cmake:153 (z_vcpkg_apply_patches)
  scripts/cmake/vcpkg_extract_source_archive_ex.cmake:8 (vcpkg_extract_source_archive)
  scripts/cmake/vcpkg_from_github.cmake:113 (vcpkg_extract_source_archive_ex)
  ports/snappy/portfile.cmake:4 (vcpkg_from_github)
  scripts/ports.cmake:147 (include)


error: building snappy:amd64-windows-static-md-release failed with: BUILD_FAILED
Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
Then check for known issues at:
    https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+snappy
You can submit a new issue at:
    https://github.com/microsoft/vcpkg/issues/new?title=[snappy]+Build+error&body=Copy+issue+body+from+C%3A%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md

@github-actions
Copy link

github-actions bot commented May 7, 2023

Revision: 996cd86

Submitted crossbow builds: ursacomputing/crossbow @ actions-84a73cd34d

Task Status
wheel-windows-cp310-amd64 Github Actions
wheel-windows-cp311-amd64 Github Actions
wheel-windows-cp37-amd64 Github Actions
wheel-windows-cp38-amd64 Github Actions
wheel-windows-cp39-amd64 Github Actions

@sjperkins
Copy link
Contributor Author

wheel-windows-cp37-amd64

Looks like it may have. I've opened #35503

liujiacheng777 pushed a commit to LoongArch-Python/arrow that referenced this pull request May 11, 2023
…pache#35430)

### Rationale for this change

- apache#34818 pinned vcpkg to a non-release master branch commit.
- This was to include unreleased changes, specifically microsoft/vcpkg#29674.

### What changes are included in this PR?

This pins vcpkg to the official 2023.04.15 release (commit microsoft/vcpkg@501db0f)

### Are these changes tested?

I've successfully test that the following local wheel builds succeed:

```bash
$ ARCH=amd64 PYTHON=3.10 archery docker run python-wheel-manylinux-2014
$ ARCH=amd64 PYTHON=3.10 archery docker run python-wheel-manylinux-2-28
```

### Are there any user-facing changes?

I don't believe so

* Closes: apache#35099

Authored-by: Simon Perkins <simon.perkins@gmail.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
ArgusLi pushed a commit to Bit-Quill/arrow that referenced this pull request May 15, 2023
…pache#35430)

### Rationale for this change

- apache#34818 pinned vcpkg to a non-release master branch commit.
- This was to include unreleased changes, specifically microsoft/vcpkg#29674.

### What changes are included in this PR?

This pins vcpkg to the official 2023.04.15 release (commit microsoft/vcpkg@501db0f)

### Are these changes tested?

I've successfully test that the following local wheel builds succeed:

```bash
$ ARCH=amd64 PYTHON=3.10 archery docker run python-wheel-manylinux-2014
$ ARCH=amd64 PYTHON=3.10 archery docker run python-wheel-manylinux-2-28
```

### Are there any user-facing changes?

I don't believe so

* Closes: apache#35099

Authored-by: Simon Perkins <simon.perkins@gmail.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
rtpsw pushed a commit to rtpsw/arrow that referenced this pull request May 16, 2023
…pache#35430)

### Rationale for this change

- apache#34818 pinned vcpkg to a non-release master branch commit.
- This was to include unreleased changes, specifically microsoft/vcpkg#29674.

### What changes are included in this PR?

This pins vcpkg to the official 2023.04.15 release (commit microsoft/vcpkg@501db0f)

### Are these changes tested?

I've successfully test that the following local wheel builds succeed:

```bash
$ ARCH=amd64 PYTHON=3.10 archery docker run python-wheel-manylinux-2014
$ ARCH=amd64 PYTHON=3.10 archery docker run python-wheel-manylinux-2-28
```

### Are there any user-facing changes?

I don't believe so

* Closes: apache#35099

Authored-by: Simon Perkins <simon.perkins@gmail.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting merge Awaiting merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[CI][Packaging] Pin vcpkg to release that includes OpenSSL linux-headers fix
4 participants