Jorge Ejarque
Jorge Ejarque
I am having the same issue when updating to the latest release 3.27.0-GA. It was not happening in previous version i was using 3.21
This bug seems to be in the Extrae part. We are trying to migrate to de master branch. I will contact you to check if the issue still fails with...
Supporting the use of task parameters in the proposed fields ais that parameter values can be dependencies to other tasks so they are not know at this time or will...
As commented in #10, when you use a task parameter these values are solved at the worker. Environment variables are resolved at master, so they will appear in this logs.
When did you downloaded the image? Was it today or last week?
Looking at the full log. It seems the installation is done twice! First one is working second one is failing.
Do you have a portable environment where I can test this installation with the OS which is failing (such as a docker image)?
I have seen an official arch-linux docker image. I was looking a Manjaro one. I will try to install there to see if the problem is happening there.
The NF(NODE FAIL) is managed in the same way as F (FAILED). They are considered an QueueStatus.ERROR that has been started and not active. For all submitted and started tasks...
I see what is happening. The final error message includes the dump of the queue status, but the failing job doesn't appear because the Slurm squeue command is not printing...