Comments (13)
I guess you are talking about this warning here, right?
https://github.com/rwth-i6/sisyphus/blob/master/sisyphus/job.py#L518
Looking at the code I guess you keep getting the same warnings for the same directories over and over again. At least I don't see any check to stop that. That would be an undesired behavior and needs to be fixed anyway, Sisyphus should stop trying to clean it up after the first try.
Or is your problem that you keep getting warnings for different directories? The only way I see right now is to disable the warning there in the code until I find a nicer solution.
from sisyphus.
You get each warning only once per start up! So if you restart Sisyphus it's expected to see the warnings again. Before that fix the same warning kept showing up over and over again every time Sisyphus tried to cleanup the directory.
I think you could just add a check if the directory which should be cleaned actually belongs the user running Sisyphus inside
_sis_cleanable. I guess that would remove these warnings for you and would probably be a good idea anyway.
from sisyphus.
Looking at the code I guess you keep getting the same warnings for the same directories over and over again.
Yes exactly. For now I turned off autocleaning because it was spamming the console every few minutes.
from sisyphus.
This branch here should fix your issue: https://github.com/rwth-i6/sisyphus/tree/cleanup_once
Could you give it a try and let me know if it works for you?
from sisyphus.
Hey, first of all sorry for the later reply.
So I switched to the branch (and also pulled the master which was quite behind in my sis version) and there is some other issue right now (visual I think):
It loads the config, then the usual appears
Print verbose overview (v), update aliases and outputs (u), start manager (y), or exit (n)? [2021-09-24 09:29:20,640] INFO: clean up: [SOME PATH]
but as you can see there instantly also comes the first cleanup massage in the same line. I can just type y or the other commands but its already few lines behind because cleaning instantly starts. Besides that from what I can tell it is also not working, it still tries to clean up Jobs multiple times (In the output I found at least one job which is tried twice)
from sisyphus.
Good point, maybe the starting the cleaner should be delayed until the manger is started.
I'll take a look at this and why this didn't solve the double cleaning problem next week.
from sisyphus.
Sorry for the late reply. I added a bugfix to the cleanup_once branch and delayed the startup of the cleaner till the manager loop is started. Please try it again.
from sisyphus.
No worries, I was on vacation and only came back today so the timing was fitting :)
From what I see (like 10 minute test run) it seems to be working. Thanks again for your help!
from sisyphus.
Not sure why this is still open, but this is working now.
from sisyphus.
Not sure why this is still open, but this is working now.
@Atticus1806 Is this actually under master? I am still getting these warnings
from sisyphus.
These changes are under master. They don't suppress all warning, but make sure that Sisyphus only tries to clean a directory once instead trying it each time the cleaner is run. So you should only get each warning once, instead of getting repeatedly all the time.
from sisyphus.
from sisyphus.
Isn't this also fixed now via PR #154 (fixing issue #105)?
from sisyphus.
Related Issues (20)
- More then one matching SLURM task HOT 9
- `Task.run`, wait for inputs HOT 7
- `FileExistsError` in `Job._sis_setup_directory` HOT 4
- More then one matching SLURM task HOT 6
- Crash after user interrupt HOT 4
- Sisyphus fails to hash numpy bools HOT 1
- Sisyphus sometimes hangs for a while (several minutes) at startup HOT 11
- Suggestion: Database for cache, `_sis_all_path_available` etc
- AssertionError: Only runnable jobs can list needed tasks HOT 1
- Local job hangs, not available input HOT 2
- Job marked in error state is actually running HOT 2
- More then one matching SLURM task (again)
- Auto-restart hanging job if faulty node detected HOT 11
- Possibility to set specific env vars for job HOT 13
- Auto-restart jobs on user-specified error conditions
- `Unsupported operand type(s) for *` when running `tk.remove_job_and_descendants(mode="move")` HOT 7
- `sis_hash_helper` on `enum.Enum`s is Python version dependent HOT 2
- Too many open file descriptors HOT 5
- Use `dill` for pickling HOT 2
- `IndexError` in `DelayedFormat` when providing kwargs HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sisyphus.