[Bug] DotNetAstGen binary gets killed instantly on MacOS #4019
Assignees
Labels
bug
Something isn't working
Comments
|
cc: @pandurangpatil |
|
I've encountered this too, and I've found that the default terminal is usually simulating Intel (Rosetta mode). I've tried to look at cross-architecture builds for |
|
Ok I looked into this and seems related to dotnet/runtime#79267 Also, running |
DavidBakerEffendi
added a commit
that referenced
this issue
Jan 10, 2024
Two main groups of properties are commonly duplicated among test fixtures: * Dataflow processing with custom semantic definitions * Post processing passes This PR uses a combination of traits and new additions to `TestCpg` to improve the re-usability and consistency of these among frontend fixtures. I leave it up to the authors of the frontends to refactor these changes in each test suite.themselves. Misc: Added a fix for #4019
DavidBakerEffendi
added a commit
that referenced
this issue
Jan 11, 2024
Two main groups of properties are commonly duplicated among test fixtures: * Dataflow processing with custom semantic definitions * Post processing passes This PR uses a combination of traits and new additions to `TestCpg` to improve the re-usability and consistency of these among frontend fixtures. I leave it up to the authors of the frontends to refactor these changes in each test suite.themselves. The result is that all test fixtures include the options for ```scala .withOssDataflow(Boolean) .withExtraFlows(List[FlowSemantic]) .withPostProcessingPasses(Boolean) ``` Misc: Added a fix for #4019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The
DotNetAstGenbinaries stored injoern-cli/frontends/csharpsrc2cpg/bin/astgenfolder are segregated by operating systems. Thedotnetastgen-macos-armis terminated instantly on a ARM Mac, throwing an error code of 137. The tests fail with a RuntimeException defined in code. Strangely, thedotnetastgen-macosworks perfectly fine on the same machine, but it is not picked up by default when running the tests.To Reproduce
Steps to reproduce the behavior:
Expected behavior
The Ast for the tests should be generated and tests should execute.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: