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.

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

2037 - Remove workers from vt #2058

Merged
merged 12 commits into from
Jan 17, 2023
Merged

2037 - Remove workers from vt #2058

merged 12 commits into from
Jan 17, 2023

Conversation

thearusable
Copy link
Contributor

Closes #2037

@thearusable thearusable self-assigned this Jan 2, 2023
src/vt/pool/pool.cc Outdated Show resolved Hide resolved
@lifflander
Copy link
Collaborator

There should also be some removals from documentation.

@thearusable thearusable force-pushed the 2037-remove-workers branch 2 times, most recently from d4c6454 to 95d3d8a Compare January 5, 2023 14:27
@thearusable
Copy link
Contributor Author

@lifflander Should I also remove the fcontext?

Copy link
Member

@PhilMiller PhilMiller left a comment

Choose a reason for hiding this comment

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

Definitely don't remove fcontext. We're using that for real application work, and actively developing and improving it

@thearusable thearusable force-pushed the 2037-remove-workers branch 3 times, most recently from 2ac952b to 641ddf9 Compare January 6, 2023 14:00
@thearusable thearusable marked this pull request as ready for review January 6, 2023 15:36
@thearusable thearusable force-pushed the 2037-remove-workers branch 3 times, most recently from a4280c1 to 77bcb99 Compare January 9, 2023 14:42
@codecov
Copy link

codecov bot commented Jan 9, 2023

Codecov Report

Merging #2058 (708a084) into develop (9089be5) will increase coverage by 0.31%.
The diff coverage is 81.94%.

❗ Current head 708a084 differs from pull request most recent head 26333a5. Consider uploading reports for the commit 26333a5 to get more accurate results

Impacted file tree graph

@@             Coverage Diff             @@
##           develop    #2058      +/-   ##
===========================================
+ Coverage    84.47%   84.78%   +0.31%     
===========================================
  Files          730      723       -7     
  Lines        25842    25647     -195     
===========================================
- Hits         21829    21746      -83     
+ Misses        4013     3901     -112     
Impacted Files Coverage Δ
src/vt/collective/collective_ops.cc 92.04% <0.00%> (+1.03%) ⬆️
src/vt/context/context.cc 100.00% <ø> (ø)
src/vt/context/context.h 100.00% <ø> (+8.33%) ⬆️
src/vt/context/context_attorney.cc 100.00% <ø> (+66.66%) ⬆️
src/vt/pool/header/pool_header.cc 100.00% <ø> (ø)
src/vt/pool/pool.cc 92.40% <ø> (+4.90%) ⬆️
src/vt/runtime/runtime.h 100.00% <ø> (ø)
src/vt/scheduler/scheduler.cc 68.71% <ø> (ø)
src/vt/standalone/vt_main.h 100.00% <ø> (ø)
src/vt/utils/atomic/null_atomic.h 80.00% <ø> (ø)
... and 37 more

@cz4rs
Copy link
Contributor

cz4rs commented Jan 9, 2023

The following tests FAILED:
	395 - vt:TestPreconfig.test_vt_assert_no_mpi (SEGFAULT)

I think this might be an independent failure caused by a newer intel/oneapi image available. I'll try to reproduce this on develop and create a separate issue if needed.

cmake/threading_config.cmake Outdated Show resolved Hide resolved
docs/md/context.md Outdated Show resolved Hide resolved
docs/md/vt.md Outdated Show resolved Hide resolved
src/vt/configs/debug/debug_masterconfig.h Outdated Show resolved Hide resolved
src/vt/runtime/runtime.cc Outdated Show resolved Hide resolved
src/vt/runtime/runtime_get.cc Outdated Show resolved Hide resolved
src/vt/utils/container/process_ready_buffer.h Outdated Show resolved Hide resolved
@thearusable thearusable force-pushed the 2037-remove-workers branch 2 times, most recently from f99fcd1 to 708a084 Compare January 12, 2023 10:43
Copy link
Collaborator

@lifflander lifflander left a comment

Choose a reason for hiding this comment

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

Looks good to me!

@lifflander
Copy link
Collaborator

The failing pipelines seem to have nothing to do with this PR.

@PhilMiller
Copy link
Member

The commit signatures will need to be fixed

@lifflander
Copy link
Collaborator

The commit signatures will need to be fixed

There's no problem with them. The github action is being very unstable.

Copy link
Member

@PhilMiller PhilMiller left a comment

Choose a reason for hiding this comment

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

Other than maybe some left-over bits that can also be deleted, this looks good to me.

@cz4rs
Copy link
Contributor

cz4rs commented Jan 13, 2023

The following tests FAILED:
	395 - vt:TestPreconfig.test_vt_assert_no_mpi (SEGFAULT)

I think this might be an independent failure caused by a newer intel/oneapi image available. I'll try to reproduce this on develop and create a separate issue if needed.

This runs fine on my machine with IntelLLVM 2023.0.0

-- The C compiler identification is IntelLLVM 2023.0.0
-- The CXX compiler identification is IntelLLVM 2023.0.0
vt  build  ctest -R TestPreconfig.test_vt_assert_no_mpi
Test project /home/cz4rs/code/vt/build
    Start 995: vt:TestPreconfig.test_vt_assert_no_mpi
1/1 Test #995: vt:TestPreconfig.test_vt_assert_no_mpi ...   Passed    0.00 sec

100% tests passed, 0 tests failed out of 1

I'll try running it inside container 🤷

@@ -20,11 +10,11 @@ if(vt_fcontext_enabled)
STATUS
"Using fcontext for worker threading"
)
config_for_fcontext()
set(vt_fcontext_enabled "1")
Copy link
Member

Choose a reason for hiding this comment

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

This can go away too, can't it? if (X) set(X)?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ah yes! removed.

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.

Remove workers/worker groups from VT.
4 participants