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

Mismatch between running FM in circle illustration and fm table view in GUI #9422

Open
2 of 11 tasks
jonathan-eq opened this issue Dec 3, 2024 · 2 comments · May be fixed by #9432
Open
2 of 11 tasks

Mismatch between running FM in circle illustration and fm table view in GUI #9422

jonathan-eq opened this issue Dec 3, 2024 · 2 comments · May be fixed by #9432
Assignees
Labels

Comments

@jonathan-eq
Copy link
Contributor

jonathan-eq commented Dec 3, 2024

What happened? (You can include a screenshot if it helps explain)

It is unclear if the number in the progress widget (in center of circle) is representing the number of FMs completed, or if it is the number of which FM is currently running. This should be the same number, but there can be a situation where an event is lost/dropped, then this number number will be off.
In the attached image, realization 4 is shown as 101/108 FMs are completed, yet the detailed table view shows that FM 72 is still running while 73,74,75,76... has successfully finished.
Image
This happened with max_submit=2, so there might be something buggy with how we do status counting when resubmitting realizations.

What did you expect to happen?

FMs after a running FM should not be marked as finished if the proceeding one has not finished. In case an event is dropped, we should be able to conclude that it has succeeded if the FMs after it are running/finished.

steps to reproduce

TBD

Environment where bug has been observed

  • python 3.8
  • python 3.10
  • python 3.11
  • python 3.12
  • macosx
  • rhel7
  • rhel8
  • local queue
  • lsf queue
  • slurm queue
  • openPBS queue
@jonathan-eq jonathan-eq added the bug label Dec 3, 2024
@jonathan-eq jonathan-eq self-assigned this Dec 3, 2024
@jonathan-eq jonathan-eq moved this to In Progress in SCOUT Dec 3, 2024
@jonathan-eq jonathan-eq linked a pull request Dec 4, 2024 that will close this issue
9 tasks
@jonathan-eq jonathan-eq moved this from In Progress to Ready for Review in SCOUT Dec 4, 2024
@xjules
Copy link
Contributor

xjules commented Dec 11, 2024

Let's figure out why the event got lost.

@JHolba
Copy link
Contributor

JHolba commented Dec 16, 2024

Putting this back into todo as discussed with owls. No feedback from user. We will pick it up again if this error is encountered by others.

@JHolba JHolba moved this from Ready for Review to Todo in SCOUT Dec 16, 2024
@jonathan-eq jonathan-eq moved this from Todo to Backlog in SCOUT Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Backlog
Development

Successfully merging a pull request may close this issue.

4 participants