Skip to content

Conversation

@SantaMcCloud
Copy link
Contributor

FOR CONTRIBUTOR:

  • I have read the CONTRIBUTING.md document and this tool is appropriate for the tools-iuc repo.
  • License permits unrestricted use (educational + commercial)
  • This PR adds a new tool or tool collection
  • This PR updates an existing tool or tool collection
  • This PR does something else (explain below)

@SantaMcCloud
Copy link
Contributor Author

SantaMcCloud commented Feb 24, 2025

Failed test should not happen. Could be bugs? To make sure i did open an issue by the devs to check if this output should be correct or not: raw-lab/mercat2#14

@bgruening
Copy link
Member

Job in error state.. tool_id: mercat2, exit_code: 1, stderr: 2025-02-24 00:22:34,777 WARNING services.py:1832 -- WARNING: The object store is using /tmp/tmpwxtzbi9v/tmp instead of /dev/shm because /dev/shm has only 67108864 bytes available. This will harm performance! You may be able to free up space by deleting files in /dev/shm. If you are inside a Docker container, you can increase /dev/shm size by passing '--shm-size=5.05gb' to 'docker run' (or add it to the run_options list in a Ray cluster config). Make sure to set this to more than 30% of available RAM.

Will the tool work without /dev/shm? You can tweak the error detection by using the <sdtio> and simply ignore this warning.

@bgruening
Copy link
Member

It might help to link the Docker container in the issues you have created.

@SantaMcCloud
Copy link
Contributor Author

Job in error state.. tool_id: mercat2, exit_code: 1, stderr: 2025-02-24 00:22:34,777 WARNING services.py:1832 -- WARNING: The object store is using /tmp/tmpwxtzbi9v/tmp instead of /dev/shm because /dev/shm has only 67108864 bytes available. This will harm performance! You may be able to free up space by deleting files in /dev/shm. If you are inside a Docker container, you can increase /dev/shm size by passing '--shm-size=5.05gb' to 'docker run' (or add it to the run_options list in a Ray cluster config). Make sure to set this to more than 30% of available RAM.

Will the tool work without /dev/shm? You can tweak the error detection by using the <sdtio> and simply ignore this warning.

It should work since test 3 and 4 did run with the warning and didnt fail. Test 1 and 2 fail because of some bugs which are fix in the repo but not in the relase. I hope that they respond quick to fix this errors!

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