-
Notifications
You must be signed in to change notification settings - Fork 427
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
[BE] github actions migration #2422
Conversation
@aclegg3 EGL initialization on the Actions runner now works correctly. You may still have issues with the CUDA build - let me know if that happens. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added some high-level comments.
- name: setup | ||
run: |- | ||
pip install -U pip | ||
pip install -U --prefer-binary \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should pin all dependencies here, especially complex ones like numpy
.
This could be done from a requirements_ci.txt
file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed
# Disable clone protection for git lfs | ||
export GIT_CLONE_PROTECTION_ACTIVE=false | ||
|
||
sudo apt install git-lfs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would move LFS installation to a separate actions.yml
workflow, along with all other basic setup steps.
python src_python/habitat_sim/utils/datasets_download.py --uids ci_test_assets ycb rearrange_dataset_v2 --replace --data-path data/ --no-prune | ||
ls -la data/scene_datasets/habitat-test-scenes/ | ||
- name: Debugging with tmate | ||
uses: mxschmitt/[email protected] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is really handy!
…ry removing some "fluff" from testing to see if necessary
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Good job figuring this out!
sudo mkdir /opt/cmake312 | ||
sudo sh ./cmake-3.12.4-Linux-x86_64.sh --prefix=/opt/cmake312 --skip-license | ||
sudo ln -s /opt/cmake312/bin/cmake /usr/local/bin/cmake | ||
sudo ln -s /opt/cmake312/bin/ctest /usr/local/bin/ctest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would simplify this with sudo apt install -y cmake
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can try this and see if it works. 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nah, cmake isn't available on apt. I think that's the reason for this installation method initially.
Anyway, feel free to fiddle with it as a follow-up.
tags: [ "v*" ] | ||
schedule: | ||
- cron: "0 5 * * *" | ||
#this is 9PM PST |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
assert not config.has_value("test") | ||
# TODO: this line segfaults on some platforms, investigate | ||
# config.remove("test") | ||
# assert not config.has_value("test") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is pretty strange. Do you have an idea of what could be going on here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have this issue on my local platform (Fedora 40) also. I spoke to John about it. His guess is that the more recent compilers may be treating some C++ code differently in the Configuration string manipulation system. E.g. I have gcc 14 here. He's looking into it, but for now we'll disable this one line. It really only hits when trying to remove a string key from a Configuration which I don't think we ever do anywhere downstream.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Putting this here for posterity) Yeah, specifically removing a string key to a string field in a raw configuration only.
Motivation and Context
Working branch to test migration to github actions. Do not merge.
How Has This Been Tested
CI
Types of changes
Checklist