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.

Sign up for GitHub

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

Jump to bottom

Add Trilinos Developer Instructions for GitHub Issues and waffle.io #138

Closed
jwillenbring opened this issue Feb 11, 2016 · 2 comments
Closed

Add Trilinos Developer Instructions for GitHub Issues and waffle.io #138

jwillenbring opened this issue Feb 11, 2016 · 2 comments
Assignees
@jwillenbring
Labels
Framework tasks Framework tasks (used internally by Framework team)

Comments

@jwillenbring
Copy link
Member

@maherou has asked me to write up some instructions for using GitHub Issues and waffle.io. I am going to do this on a Trilinos GitHub wiki page. I am going to use the IDEAS Jira instructions as a guide.
@jwillenbring jwillenbring self-assigned this Feb 11, 2016
@jwillenbring jwillenbring added Framework tasks Framework tasks (used internally by Framework team) stage: in progress Work on the issue has started labels Feb 11, 2016
@jwillenbring
Copy link
Member Author

@maherou

I completed a rough draft of this page.

https://github.com/trilinos/Trilinos/wiki/Managing-Trilinos-Project-Issues

It was not clear to me how much detail about deliverable tracking and customer-specific issue tracking was appropriate for this page. I have some thoughts to share with you on that issue if you want to pursue it. Please provide feedback on what I have (and don't have) in this page.

@maherou
Copy link
Member

maherou commented Feb 14, 2016

I modified the bottom of the page slightly, just enumerating the steps so that a developer can scan quickly to see what has to be done.

@maherou maherou closed this as completed Feb 14, 2016
@maherou maherou removed the stage: in progress Work on the issue has started label Feb 14, 2016
@trilinos-autotester trilinos-autotester mentioned this issue Nov 3, 2021
Closed
@trilinos-autotester trilinos-autotester mentioned this issue Dec 9, 2021
Merged
jhux2 added a commit that referenced this issue Jul 12, 2023
@jhux2
Tpetra: checkpoint
5de9d39 
All tests pass
Tons of debugging output

Hack in Tpetra_CrsMatrix_def.hpp:
    destMat->numImportPacketsPerLID_.modify_host()

because numImportPacketsPerLID_ is a Kokkos::DualView and hasn't been
properly marked as modified on host

Some tests are *extremely* slow, I suspect from the debugging output

 99/279 Test #198: TpetraCore_MatrixMatrix_UnitTests_MPI_4 .....................................................   Passed  135.66 sec
105/279 Test #139: TpetraCore_ImportExport2_UnitTests_ISend_MPI_4 ..............................................   Passed  191.11 sec
275/279 Test #138: TpetraCore_ImportExport2_UnitTests_Send_MPI_4 ...............................................   Passed  112.59 sec
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jwillenbring jwillenbring

Labels
Framework tasks Framework tasks (used internally by Framework team)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@maherou @jwillenbring