Add larecs package

[samufi]

Add a recipe for the Larecs package

Logo could be a cone or twig of a larch tree (Larix decidua)

Checklist

• My recipe.yaml file specifies which version(s) of MAX is compatible with my project (see here for an example). If not, my package is compatible with both 24.5 and 24.6.
• License file is packaged (see here for an example).
• Set the build number to 0 (for new packages, or if the version changed).
• Bumped the build number (if the version is unchanged).

[carolinefrasca]

Hi @samufi, thanks for submitting this! Looks like it is failing on line 11. I think rev is supposed to be a commit hash (see screenshot from rattler build docs), but you should be able to use tag instead:

You could probably sub out that line for tag: "0.1.0"

 ╭─ Running build for recipe: larecs-0.1.0-h58ea7c0_0
 │
 │ ╭─ Fetching source code
 │ │ Fetching source from git repo: https://github.com/samufi/larecs.git
 │ │ Fetching repository from https://github.com/samufi/larecs.git at v0.1.0 into /Users/runner/work/modular-community/modular-community/output/src_cache/larecs.git
 │ │
 │ ╰─────────────────── (took 1 second)
 │
 ╰─────────────────── (took 1 second)
Error:   × Failed to run git command: failed to checkout FETCH_HEAD: error: pathspec
  │ 'v0.1.0' did not match any file(s) known to git

[carolinefrasca]

Line 11 needs to be updated (see comment on PR)

[samufi]

Hmm, the issue seems to be that I require a Mojo version that is available on nightly only. In the Forum, it was suggested that I can specify the max-nightly requirement somewhere in the recipe, but I did not find anything else besides the place where the max version is specified. I'd welcome assistance.

[carolinefrasca]

Hi @samufi, unfortunately adding this nightly breaks the Mosaic package – let me reach out to the owner and ask them to update their package, and then once that's done, I can add that nightly to the channel.

[samufi]

@carolinefrasca I have updated Larecs to the second release, which uses the stable Mojo branch. Could you restart the checks so that we can see if the package can be merged?

[carolinefrasca]

@samufi So sorry for the delay here – I totally missed this.

This is the current error (looks like it's coming from one of your tests):

 Installing test environment
 │ │ │ ✔ Successfully updated the test environment
 │ │ │ Testing commands:
 │ │ │ + mojo test -D ASSERT=all test
 │ │ │ Testing Time: 4.262s
 │ │ │ Total Discovered Tests: 90
 │ │ │ Passed : 89 (98.89%)
 │ │ │ Failed : 1 (1.11%)
 │ │ │ Skipped: 0 (0.00%)
 │ │ │ ******************** Failure: '$PREFIX/etc/conda/test-files/larecs/0/test/world_test.mojo::test_world_remove_entities()' ********************
 │ │ │ Unhandled exception caught during execution
 │ │ │ $PREFIX/etc/conda/test-files/larecs/0/test/world_test.mojo::test_world_remove_entities()
 │ │ │ Unhandled exception caught during execution: At $PREFIX/etc/conda/test-files/larecs/0/test/world_test.mojo:94:17: AssertionError: `left == right` comparison failed:
 │ │ │    left: 12
 │ │ │   right: 0
 │ │ │ ********************

[samufi]

@carolinefrasca I have updated Larecs and Mojo to the current stable release. Could you restart the testing procedure and see if it works now?

[carolinefrasca]

@samufi seems like this is still failing due to one of the tests:

 Installing test environment
 │ │ │ ✔ Successfully updated the test environment
 │ │ │ Testing commands:
 │ │ │ + mojo test -D ASSERT=all test
 │ │ │ Testing Time: 4.347s
 │ │ │ Total Discovered Tests: 77
 │ │ │ Passed : 76 (98.70%)
 │ │ │ Failed : 1 (1.30%)
 │ │ │ Skipped: 0 (0.00%)
 │ │ │ ******************** Failure: '$SRC_DIR/test/world_test.mojo::test_world_remove_entities()' ********************
 │ │ │ Unhandled exception caught during execution
 │ │ │ $SRC_DIR/test/world_test.mojo::test_world_remove_entities()
 │ │ │ Unhandled exception caught during execution: At $SRC_DIR/test/world_test.mojo:93:17: AssertionError: `left == right` comparison failed:
 │ │ │    left: 12
 │ │ │   right: 0
 │ │ │ ********************
 │ │ │ × error Script failed with status 1
 │ │ │ × error Work directory: '/home/runner/work/modular-community/modular-community/output/bld/rattler-build_larecs_1753388074/work/test/run/etc/conda/test-files/larecs/0'
 │ │ │ × error To debug the build, run it manually in the work directory (execute the `./conda_build.sh` or `conda_build.bat` script)
 │ │ │

[samufi]

@samufi seems like this is still failing due to one of the tests:

Yes, @carolinefrasca, I have still not found the issue. Currently, I am waiting for a testing bug on nightly to be fixed so that I can see whether I can use some of the new features. I will message / tag you when there has been progress.

[carolinefrasca]

Sounds good, thank you!

[hogepodge]

@samufi checking in on this, have you had the opportunity to resolve the underlying issues?

[samufi]

@samufi checking in on this, have you had the opportunity to resolve the underlying issues?

We have investigated this intensively, and @moseschmiedel has put an aweful lot of work into tracking down the issue down to the MLIR level. We are very certain this is a compiler bug (the MLIR code is wrong afawk), in particular one that occurs under mojo test only. @moseschmiedel has written a detailed forum post, and it would be great if someone from the team could have a look at it.

We decided not to be blocked by the issue and will disable the failing tests, as we could never reproduce the issue under normal mojo run. We will submit a PR with succeesing tests asap.

[hogepodge]

I flagged the post internally, and I'm hoping someone from the Mojo team will get back to you soon.