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.

Sign up for GitHub

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

Jump to bottom

testpr: Move recipe in a different directory to avoid that output, .pixi and .git folders are saved in the package itself #2

Open
wants to merge 8 commits into
base: testpr-rattler-build
Choose a base branch
from
Open

testpr: Move recipe in a different directory to avoid that output, .pixi and .git folders are saved in the package itself #2

wants to merge 8 commits into from

Conversation

traversaro
Copy link

@traversaro traversaro commented Sep 17, 2024 •
edited
Loading

Attempt to workaround RoboStack#8 (comment) .

CI for the change running in RoboStack#11 .

@traversaro traversaro mentioned this pull request Sep 17, 2024
Closed
@traversaro
Copy link
Author

Unfortunatly it still adds the .pixi directory in the package.

@traversaro
Copy link
Author

traversaro commented Sep 17, 2024 •
edited
Loading

Unfortunatly it still adds the .pixi directory in the package.

After moving the generated recipe.yaml in a independent directory, everything seems to be working fine actually that is not the case.

@traversaro traversaro changed the title testpr: Do not put output artifacts in the recipe folder testpr: Move recipe in a different directory to avoid that output, .pixi and .git folders are saved in the package itself Sep 17, 2024
@traversaro
Copy link
Author

Unfortunatly it still adds the .pixi directory in the package.

After moving the generated recipe.yaml in a independent directory, everything seems to be working fine actually that is not the case.

After moving a bunch of other files, now it works, but it would probably make more sense for vinca to generate the recipe directory in its own folder. Now the build fails with:

× error Error building package: Failed to resolve dependencies: Cannot solve the request because of: No candidates were found for ros-jazzy-ros-environment *.
Error:   × Failed to resolve dependencies: Cannot solve the request because of: No
  │ candidates were found for ros-jazzy-ros-environment *.
  │ 
  ╰─▶ Cannot solve the request because of: No candidates were found for ros-
      jazzy-ros-environment *.

but I guess this is another problem.

@traversaro traversaro mentioned this pull request Sep 17, 2024
Closed
oursland added a commit that referenced this pull request Sep 20, 2024
@oursland
WIP: rclpy interaction crashes.
8466bcd 
Current processes:

rebuild:
  reset ; rm -rf output/bld && pixi run generate-recipes && time pixi run -v rattler-build build --recipe recipes/ros-jazzy-rosidl-generator-py --recipe recipes/ros-jazzy-rclpy --recipe recipes/ros-jazzy-rcl-interfaces -m conda_build_config.yaml -c robostack-jazzy -c conda-forge --keep-build

test:
  mamba create -n ros-jazzy -c conda-forge -c file:///Users/jso/code/ros-jazzy/output python=3.11\* ros-jazzy-rclpy
  mamba run --live-stream -n ros-jazzy lldb python -- -c 'import rclpy; rclpy.init(); node = rclpy.create_node("test"); rclpy.spin(node)'

  Then run with the 'r' command:

The second line will run a simple python script that exhibits the crash.  The log looks like this:

  (lldb) target create "python"
  Current executable set to '/Users/jso/code/FreeCAD/FreeCAD/.conda/ros-jazzy/bin/python' (arm64).
  (lldb) settings set -- target.run-args  "-c" "import rclpy; rclpy.init(); node = rclpy.create_node(\"test\"); rclpy.spin(node)"
  (lldb) r
  Process 78922 launched: '/Users/jso/code/FreeCAD/FreeCAD/.conda/ros-jazzy/bin/python' (arm64)
  Process 78922 stopped
  * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x60)
      frame #0: 0x00000001027d6314 libpython3.11.dylib`set_attribute_error_context + 60
  libpython3.11.dylib`set_attribute_error_context:
  ->  0x1027d6314 <+60>: ldr    x0, [x8, #0x60]
      0x1027d6318 <+64>: bl     0x1028a0b0c    ; PyErr_GivenExceptionMatches
      0x1027d631c <+68>: cbz    w0, 0x1027d6384 ; <+172>
      0x1027d6320 <+72>: ldr    x8, [x21, #0x358]
  Target 0: (python) stopped.
  (lldb) bt
  * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x60)
    * frame #0: 0x00000001027d6314 libpython3.11.dylib`set_attribute_error_context + 60
      frame #1: 0x00000001027d68f0 libpython3.11.dylib`PyObject_GetAttr + 192
      frame #2: 0x00000001027d67e0 libpython3.11.dylib`PyObject_GetAttrString + 108
      frame #3: 0x0000000101a87b04 libbuiltin_interfaces__rosidl_generator_py.dylib`builtin_interfaces__msg__time__convert_from_py + 60
      frame #4: 0x000000010219c0a8 librcl_interfaces__rosidl_generator_py.dylib`rcl_interfaces__msg__parameter_event__convert_from_py + 356
      frame RoboStack#5: 0x0000000100e48250 _rclpy_pybind11.cpython-311-darwin.so`___lldb_unnamed_symbol2190 + 360
      frame RoboStack#6: 0x0000000100e2b844 _rclpy_pybind11.cpython-311-darwin.so`___lldb_unnamed_symbol1795 + 76
      frame RoboStack#7: 0x0000000100e2c1a0 _rclpy_pybind11.cpython-311-darwin.so`___lldb_unnamed_symbol1802 + 208
      frame RoboStack#8: 0x0000000100dc17c0 _rclpy_pybind11.cpython-311-darwin.so`___lldb_unnamed_symbol708 + 4556
      frame RoboStack#9: 0x00000001000b7f4c python`cfunction_call + 124
      frame RoboStack#10: 0x00000001000606f0 python`_PyObject_MakeTpCall + 332
      frame RoboStack#11: 0x0000000100162e3c python`_PyEval_EvalFrameDefault + 46484
      frame RoboStack#12: 0x00000001001674c8 python`_PyEval_Vector + 184
      frame RoboStack#13: 0x00000001000608b8 python`_PyObject_FastCallDictTstate + 156
      frame RoboStack#14: 0x00000001000617f0 python`_PyObject_Call_Prepend + 176
      frame RoboStack#15: 0x00000001000dc888 python`slot_tp_init + 196
      frame RoboStack#16: 0x00000001000d4de4 python`type_call + 464
      frame RoboStack#17: 0x00000001000606f0 python`_PyObject_MakeTpCall + 332
      frame RoboStack#18: 0x0000000100162e3c python`_PyEval_EvalFrameDefault + 46484
      frame RoboStack#19: 0x00000001001674c8 python`_PyEval_Vector + 184
      frame RoboStack#20: 0x00000001000608b8 python`_PyObject_FastCallDictTstate + 156
      frame RoboStack#21: 0x00000001000617f0 python`_PyObject_Call_Prepend + 176
      frame RoboStack#22: 0x00000001000dc888 python`slot_tp_init + 196
      frame RoboStack#23: 0x00000001000d4de4 python`type_call + 464
      frame RoboStack#24: 0x00000001000606f0 python`_PyObject_MakeTpCall + 332
      frame RoboStack#25: 0x0000000100162e3c python`_PyEval_EvalFrameDefault + 46484
      frame RoboStack#26: 0x00000001001568f4 python`PyEval_EvalCode + 220
      frame RoboStack#27: 0x00000001001bc970 python`run_mod + 144
      frame RoboStack#28: 0x00000001001c04a4 python`PyRun_SimpleStringFlags + 272
      frame RoboStack#29: 0x00000001001e1b3c python`Py_RunMain + 1396
      frame RoboStack#30: 0x00000001001e3050 python`pymain_main + 1252
      frame RoboStack#31: 0x0000000100003398 python`main + 56
      frame RoboStack#32: 0x00000001921f0274 dyld`start + 2840
@oursland oursland force-pushed the testpr-rattler-build branch 2 times, most recently from 0313766 to e62746c Compare September 21, 2024 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@traversaro @oursland @wolfv