-
Notifications
You must be signed in to change notification settings - Fork 4
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
Fixes an issue with some jobs being parentless #2241
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2241 +/- ##
==========================================
+ Coverage 53.90% 54.16% +0.25%
==========================================
Files 72 72
Lines 17242 17232 -10
Branches 3352 3350 -2
==========================================
+ Hits 9294 9333 +39
+ Misses 7103 7050 -53
- Partials 845 849 +4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Fyi @agarci3 Hello @albertvilabsc , @stamenminkov I wanted to deploy this branch as a module in the Hubs, and I am having this issue ( I think this happened before )
Any clue or something I can do? Thanks! FYI @kinow , After manual testing, I wanted to upload this version before I do the automatic tests, as it can take a while ( I have some similar tests that run (on my laptop, not my actual PC, which is a shame ) locally, and the idea was to prepare them to run under the CI/CD starting with the new ones and gradually adding the rest of them) |
Hi @dbeltrankyl , Working on it. Thanks, Albert |
Hi @dbeltrankyl , Solved! Can you try again, please? Thanks, Albert |
I have other issues, but they are related to my configuration. I'll solve it myself So now it works! thanks |
Perfect! Albert |
@agarci3 I think the eb recipe should work now; just waiting for the hubs to be up again. |
There is an issue with the keyword "NONE". This keyword disables a dependency for a specific member, chunk, split, or date. The fix applied here also affects that keyword, as I didn't contemplate that possibility. However, @rocsalvadorbsc reported to me that it doesn't work properly on v4.1.12, which I confirmed, and I also tested the same workflow in 4.1.11 where it is working. I'm using this branch to address the issue in the best way possible. FYI @rocsalvadorbsc |
@dbeltrankyl this is for me? Albert |
No, no. You can unsubscribe from this if you wish ( so you don't get spam). Thanks Albert! |
A perfect jeje. Thanks, Albert |
2ed6cab
to
383c0fd
Compare
It's still not working correctly ( it broke other cases with the fix) , but I have been working on adding an automatic regression test for this. It's possible that I need to modify something else in the test, but it's fairly automatic. I've added a readme for instructions on how to add new cases @kinow I'll add the auto-monarch ones, and the Destine ones to the test |
Dependencies:
FYI @kinow |
Added @rocsalvadorbsc automatic-profiler ![]() ![]() Added monarch ( @agarci3 case) ![]() Added e-monarch ![]() All three are correct. If not, tell .me Destine workflows are already confirmed to be correct For other PR'S I'll open an issue, asking for CES workflows to add all of them |
This fix is being tested by @franra9. When he finishes and everything is alright we can merge it |
Missing coverage is related to lint. Also, this regression test is not yet running automatically on CI/CD ( I will create an issue for it ) |
Normalized the new regression test
This PR does two things:
Removes "changed" related code, as the dependencies are remade each time the autosubmit needs the job_list.
And, if there is a parent_less job after all the dependencies addition, autosubmit will add all possible parents as an edge and remove it in an old-fashioned way ( check redundant dependencies ).
The calculation of the "distance" between sections has some flaws, but they are hard to fix. This workaround will cause the graph dependencies addition to be a bit slow in these cases, but it will at least generate the correct graph.
I'll make some tests that check the graph generated