Nope

but when it is executed through github actions, I get this error

I'm not, just want to be very precise an consice about them when I do ask... but bear with me, its coming 🙂

I executed it now with full path, using $(pwd)

AgitatedDove14 clearml version on the Cleanup Service is 0.17.0

Now I remind you that using the same credentials exactly, the auto scaler task could launch instances before

I'll try

I think you are talking about separate problems - the "WARNING DIFF IS TOO LARGE" is only a UI issue, that you can't see hte diff in the UI - correct me if I'm wrong with this

Maria seems to be saying that the execution FAILS when she has uncomitted changes, which is not the expected behavior - am I right maria?

This worked ✔

moreover, in each pipeline I have 10 different settings of task A -> Task b (and then task C), each run 1-2 fails randomly

For example, this is one execution:

😅

I can easily see how this problem can reoccur

I ran the wizard liek a milion times

I guess so

but why would the captcha fail? O_O

even though I apply append

Cool thanks 🤩

thx martin

Another thing I noticed now it happens on my personal computer, when I execute the same pipeline from the exact same commit with exact same data on another host it works without these problems

this is the df -h output

I have them only in one place

Continuing on this discussion... What is the relationship between configuring files_server and all the rest we just talked about and the the default_output_uri ?

it is the location of the repo

can't really see how this configuration effects the agents

ShinyLobster84

👍

Why is that an issue?

and also in the extra_vm_bash_script variables, I ahve them under export TRAINS_API_ACCESS_KEY and export TRAINS_API_SECRET_KEY

Clicking on that link exaclty 🙂