arrow
arrow copied to clipboard
GH-40454: [CI][Debian] Update Debian to 12 from 11
Rationale for this change
Debian 11 will reach EOL on 2024-07.
What changes are included in this PR?
- Use Debian 12.
- Enable build options that can't be enabled with Debian 11.
ARROW_AZUREARROW_FLIGHT_SQLARROW_WITH_OPENTELEMETRY
Are these changes tested?
Yes.
Are there any user-facing changes?
No.
- GitHub Issue: #40454
@github-actions crossbow submit test-debian-*
:warning: GitHub issue #40454 has been automatically assigned in GitHub to PR creator.
Revision: 6bf98a6465111ffe99efe26404cd2bf513ded52e
Submitted crossbow builds: ursacomputing/crossbow @ actions-aa275254c8
@github-actions crossbow submit test-debian-*
Revision: 53c3ff331b35de169dab7d8d0126100359f130b6
Submitted crossbow builds: ursacomputing/crossbow @ actions-fe10b1609e
@github-actions crossbow submit test-debian-*
Revision: 373cdea52cdfdb33bcd771a4820672235b6d393f
Submitted crossbow builds: ursacomputing/crossbow @ actions-89f6cc77e9
@github-actions crossbow submit test-debian-*
Revision: 379e5b48611ae2739deb75f3623b8eccd8e4685e
Submitted crossbow builds: ursacomputing/crossbow @ actions-ad8f7b1efa
@github-actions crossbow submit test-debian-*
Revision: 281c4379877b41634d9a5fdf8af5a43d563dbb68
Submitted crossbow builds: ursacomputing/crossbow @ actions-36e926db2f
@github-actions crossbow submit -g python
Revision: 281c4379877b41634d9a5fdf8af5a43d563dbb68
Submitted crossbow builds: ursacomputing/crossbow @ actions-dd8ded6b08
We are doing other things on this PR apart from updating debian version, like enabling AZURE build, etc. I am ok with it but should we reference it on the title/description or do it on a different PR?
You're right. I've update the description. I keep the title for now because these changes are PR details. (Title should describes summary not details.)
@github-actions crossbow submit test-debian-12-python-3-i386
Revision: 3a5b56801dc1d1d87eb88cf1a0409f0cd1c9980a
Submitted crossbow builds: ursacomputing/crossbow @ actions-4107cf027b
| Task | Status |
|---|---|
| test-debian-12-python-3-i386 |
@github-actions crossbow submit test-debian-12-python-3-amd64 -g python
Revision: 3a5b56801dc1d1d87eb88cf1a0409f0cd1c9980a
Submitted crossbow builds: ursacomputing/crossbow @ actions-01f19214ef
@github-actions crossbow submit -g python
Revision: 429fcda9dc0cef01e659d5e9e4735ca1c603f334
Submitted crossbow builds: ursacomputing/crossbow @ actions-81621861bb
@github-actions crossbow submit test-debian-12*
Revision: 8039954dd4cdc0e3306548f3052866251ce387c2
Submitted crossbow builds: ursacomputing/crossbow @ actions-fd91db0a83
| Task | Status |
|---|---|
| test-debian-12-cpp-amd64 | |
| test-debian-12-cpp-i386 | |
| test-debian-12-go-1.19 | |
| test-debian-12-go-1.21 | |
| test-debian-12-python-3-amd64 | |
| test-debian-12-python-3-i386 |
Can we merge this?
After merging your PR, Conbench analyzed the 5 benchmarking runs that have been run so far on merge-commit 93816475f75d751067d4ff427fb9ae64e85acebe.
There were no benchmark performance regressions. 🎉
The full Conbench report has more details. It also includes information about 3 possible false positives for unstable benchmarks that are known to sometimes produce them.