-
Notifications
You must be signed in to change notification settings - Fork 123
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
Mac os integration #3539
Mac os integration #3539
Conversation
Suggest that you base the Mac build on the actions in the build-conda workflow, so that you get all the necessary python dependencies. There may be other problems as well! |
2553080
to
c5f714d
Compare
Tests that fail and some reasons I'm getting locally (or if it fails remotely that's mentioned too): --- Testing makeflow/test/TR_makeflow_001_dirs_01.sh ... success 2s ## Fails Remotely --- Testing work_queue/test/TR_work_queue_python.sh ... failure 17s ## Nonetype error happening “cctools/work_queue/test/wq_test.py", line 96 --- Testing taskvine/test/TR_vine_allocations.sh ... failure 31s ## vine_manager[53797] notice: rejecting worker (127.0.0.1:50479) as it uses protocol 4. The manager is using protocol 3. --- Testing taskvine/test/TR_vine_python.sh ... failure 22s tasks “completes” (exits cleanly) but still remains in the background vine_manager[53999] notice: rejecting worker (127.0.0.1:50489) as it uses protocol 4. The manager is using protocol 3. --- Testing taskvine/test/TR_vine_python_futures.sh ... failure 6s ## Exception: Could not create manager on port 9123 --- Testing taskvine/test/TR_vine_python_no_serialization.sh ... failure 11s ## vine_manager[54629] notice: rejecting worker (127.0.0.1:50615) as it uses protocol 4. The manager is using protocol 3. --- Testing taskvine/test/TR_vine_python_serverless.sh ... failure 23s ## vine_manager[54745] notice: rejecting worker (127.0.0.1:50617) as it uses protocol 4. The manager is using protocol 3. --- Testing taskvine/test/TR_vine_python_tag.sh ... failure 22s ## Master is ready on port 1031 --- Testing taskvine/test/TR_vine_python_task.sh ... failure 11s ## listening on port 9126 --- Testing taskvine/test/TR_vine_python_temp_files.sh ... failure 12s ## listening on port 9127 |
Checks haven't passed, I'm manually testing in the pipeline. |
Notes:
Cases still failing (mainly in taskvine): --- Testing taskvine/test/TR_vine_allocations.sh ... failure 31s ## vine_manager[53797] notice: rejecting worker (127.0.0.1:50479) as it uses protocol 4. The manager is using protocol 3. --- Testing taskvine/test/TR_vine_python.sh ... failure 22s tasks “completes” (exits cleanly) but still remains in the background vine_manager[53999] notice: rejecting worker (127.0.0.1:50489) as it uses protocol 4. The manager is using protocol 3. --- Testing taskvine/test/TR_vine_python_futures.sh ... failure 6s ## Exception: Could not create manager on port 9123 --- Testing taskvine/test/TR_vine_python_no_serialization.sh ... failure 11s ## vine_manager[54629] notice: rejecting worker (127.0.0.1:50615) as it uses protocol 4. The manager is using protocol 3. --- Testing taskvine/test/TR_vine_python_serverless.sh ... failure 23s ## vine_manager[54745] notice: rejecting worker (127.0.0.1:50617) as it uses protocol 4. The manager is using protocol 3. --- Testing taskvine/test/TR_vine_python_tag.sh ... failure 22s ## Master is ready on port 1031 --- Testing taskvine/test/TR_vine_python_task.sh ... failure 11s ## listening on port 9126 --- Testing taskvine/test/TR_vine_python_temp_files.sh ... failure 12s ## listening on port 9127 |
Most of these failures are due to some setup problem where a
|
Superseded by #3594 |
Proposed changes
Please describe your changes (e.g., what problems they attempt to solve, what results are expected, etc.) Additional motivation and context are welcome.
Please also mention relevant issues and pull requests as appropriate.
Post-change actions
Put an 'x' in the boxes that describe post-change actions that you have done.
The more 'x' ticked, the faster your changes are accepted by maintainers.
make test
Run local tests prior to pushing.make format
Format source code to comply with lint policies. Note that some lint errors can only be resolved manually (e.g., Python)make lint
Run lint on source code prior to pushing.Additional comments
This section is dedicated to changes that are ambitious or complex and require substantial discussions. Feel free to start the ball rolling.