Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -10,11 +10,17 @@
"ciTests": {
"linux": [
{
"env": ["source /opt/intel/oneapi/setvars.sh --force", "conda create -n aikit-modin-test -c intel -c conda-forge matplotlib runipy intel-aikit-modin", "source activate aikit-modin-test"],
"env": [],
Copy link
Contributor Author

@dchigarev dchigarev Feb 14, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For some reason, placing environment setup and the notebook execution in different cells (env and steps) caused the environment wasn't applied (this was indicated by the "Import error: couldn't find 'modin'" error at CI logs).

Combining environment setup steps and the actual notebook execution in a single cell resolved the problem.

"id": "Intel_Modin_GS_py",
"steps": [
"runipy IntelModin_GettingStarted.ipynb"
]
"set -e # Terminate the script on first error",
"source $(conda info --base)/etc/profile.d/conda.sh # Bypassing conda's disability to activate environments inside a bash script: https://github.com/conda/conda/issues/7980",
"conda create -y -n intel-aikit-modin intel-aikit-modin -c intel",
"conda activate intel-aikit-modin",
"pip install -r requirements.txt # Installing notebook's dependencies",
"pip install runipy # Installing 'runipy' for extended abilities to execute the notebook",
"runipy IntelModin_GettingStarted.ipynb"
]
}
]
}
Expand Down