-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[Packaging][C#] Nuget build is failing on maintenance branch for 13.0.0 #36863
Comments
@westonpace @CurtHagenlocher could you help me with this one related to the 13.0.0 maintenance branch. Any idea on what is the issue? |
@raulcd Does this happen consistently? The call stack suggests a network issue which I imagine could be transient. |
I retried when opening the ticket and I just retried a third time now and it failed again: https://github.com/ursacomputing/crossbow/actions/runs/5654516424/job/15319395743 |
Oh, I see; the communications channel here is not part of a Flight test but with the test runner and is a result of the test process crashing. |
I have been able to reproduce locally from the
I can confirm that the issue is not reproducible on the main branch where the same docker-compose run is successful. |
I'm not setup to develop under Linux and have never been able to run the Python interop tests on my Macbook. If you temporarily comment out PythonEngine.Shutdown in line 63 of CDataInterfacePythonTests.cs, does it fix the problem? |
Wait, it succeeds on the main branch? |
It does succeed on main.
It also succeeds. |
The Shutdown is only required to prevent a hang on exit under .NET 4.7.2, for which tests are not yet running anyway in CI. But I can think of no reason that the behavior would be different in the main branch than in the release branch. As an unblocker, instead of commenting out entirely perhaps consider
|
Thanks this seems to solve the issue locally. I am also not sure why this is failing. I can't seem to find any change on the build scripts/docker etcetera with main and the commits that are in main and not on the maintenance branch: |
…InterfacePythonTests if .NET is > 5.0
…acePythonTests if .NET is > 5.0 (#36868) ### Rationale for this change Tests are failing on maintenance branch to generate Nuget packages. This has been tested on the maintenance branch and it solves the issue. ### What changes are included in this PR? Only Shutdown if `#if !NET5_0_OR_GREATER` ### Are these changes tested? Locally and via archery. ### Are there any user-facing changes? No * Closes: #36863 Authored-by: Raúl Cumplido <[email protected]> Signed-off-by: Raúl Cumplido <[email protected]>
…acePythonTests if .NET is > 5.0 (#36868) ### Rationale for this change Tests are failing on maintenance branch to generate Nuget packages. This has been tested on the maintenance branch and it solves the issue. ### What changes are included in this PR? Only Shutdown if `#if !NET5_0_OR_GREATER` ### Are these changes tested? Locally and via archery. ### Are there any user-facing changes? No * Closes: #36863 Authored-by: Raúl Cumplido <[email protected]> Signed-off-by: Raúl Cumplido <[email protected]>
FWIW, I can reproduce this locally. The error message itself seems to be a red herring. The problem, I think, is that pythonnet is somehow crashing the process (e.g. segfault). The error message above is just saying "the test process crashed". It isn't actually giving us any hint to the location or reasoning of the crash. Oddly, commenting out the shutdown does not stop the crash on my system. Though unsetting PYTHONNET_PYDLL (and skipping these tests) does prevent the crash. |
It has fixed the issue on the maintenance branch: |
Let's continue and I will keep debugging in parallel. |
@raulcd @CurtHagenlocher The root cause, I think, is that we need to cherry pick #36688 (b477501) You mentioned that you cherry picked this one already and the issue still reproduced. However, this fixes it for me locally and it matches the stack trace I got from further debugging which was:
Can you try cherry picking this one commit and see if that fixes it? |
Sorry, I did cherry-pick all except that one, because with that one locally on top of
|
Yikes. That seems unrelated. Maybe you need to clean your verification environment? I'm sorry, I don't really know how sourcelink works. I believe it is checking the published nuget packages to ensure that they have source archives uploaded alongside the binary archives. |
…ythonEngine on CDataInterfacePythonTests if .NET is > 5.0
I've reverted d9b9003 from the maintenance branch and I have cherry-picked b477501 |
Oh, thank you, yes. I hadn't realized that change wasn't in the release branch and it's definitely a must-have. |
…ngine on CDataInterfacePythonTests if .NET is > 5.0 (#36872) ### Rationale for this change Maintenance branch fix is not necessary. ### What changes are included in this PR? Remove unnecessary patch ### Are these changes tested? Yes, on CI ### Are there any user-facing changes? No * Closes: #36863 Authored-by: Raúl Cumplido <[email protected]> Signed-off-by: Raúl Cumplido <[email protected]>
…InterfacePythonTests if .NET is > 5.0 (apache#36868) ### Rationale for this change Tests are failing on maintenance branch to generate Nuget packages. This has been tested on the maintenance branch and it solves the issue. ### What changes are included in this PR? Only Shutdown if `#if !NET5_0_OR_GREATER` ### Are these changes tested? Locally and via archery. ### Are there any user-facing changes? No * Closes: apache#36863 Authored-by: Raúl Cumplido <[email protected]> Signed-off-by: Raúl Cumplido <[email protected]>
…ythonEngine on CDataInterfacePythonTests if .NET is > 5.0 (apache#36872) ### Rationale for this change Maintenance branch fix is not necessary. ### What changes are included in this PR? Remove unnecessary patch ### Are these changes tested? Yes, on CI ### Are there any user-facing changes? No * Closes: apache#36863 Authored-by: Raúl Cumplido <[email protected]> Signed-off-by: Raúl Cumplido <[email protected]>
…InterfacePythonTests if .NET is > 5.0 (apache#36868) ### Rationale for this change Tests are failing on maintenance branch to generate Nuget packages. This has been tested on the maintenance branch and it solves the issue. ### What changes are included in this PR? Only Shutdown if `#if !NET5_0_OR_GREATER` ### Are these changes tested? Locally and via archery. ### Are there any user-facing changes? No * Closes: apache#36863 Authored-by: Raúl Cumplido <[email protected]> Signed-off-by: Raúl Cumplido <[email protected]>
…ythonEngine on CDataInterfacePythonTests if .NET is > 5.0 (apache#36872) ### Rationale for this change Maintenance branch fix is not necessary. ### What changes are included in this PR? Remove unnecessary patch ### Are these changes tested? Yes, on CI ### Are there any user-facing changes? No * Closes: apache#36863 Authored-by: Raúl Cumplido <[email protected]> Signed-off-by: Raúl Cumplido <[email protected]>
Describe the bug, including details regarding any error messages, version, and platform.
The nuget job is failing on our maintenance branch but does not seem to be failing on main:
https://github.com/ursacomputing/crossbow/actions/runs/5654516424/job/15319395743
I had a minor conflict when cherry-picking but it does not seem related. This was the conflict:
I ended up deleting:
because #34620 is not part of the release.
Here the full log of the failure:
Component(s)
C#, Continuous Integration, Packaging
The text was updated successfully, but these errors were encountered: