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

Fixed null reference exception on compilation results moving #2795

Merged
merged 1 commit into from
Aug 30, 2024

Conversation

Thorium
Copy link
Member

@Thorium Thorium commented Aug 5, 2024

As the tooltip says, the array may contain null-references:

image

Now, if it does, the Seq.filter below without null-check dies and kills the whole run for "Null reference exception".
Check added to skip nulls.

Also when "file already exists", added trace message which file.

@xperiandri xperiandri changed the title Fixed null reference exception Fixed null reference exception on compilation results moving Aug 30, 2024
@xperiandri xperiandri merged commit 2d3420d into fsprojects:master Aug 30, 2024
3 checks passed
@xperiandri
Copy link
Collaborator

@Thorium
Copy link
Member Author

Thorium commented Aug 30, 2024

I don't think this failure is related to this commit, rather it's still some unstability of integration test.
In this case, I've only run this locally on Windows that does work well.

I expect this is something about the test that runs integrationtests/core-no-dependencies-hello-world/before folder build, not having any restriction settings (like global.json), so it tries to run it on .Net 8.0 and it fails for something?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants