Conversation
|
bot: show_config |
|
Instance
|
|
bot: build instance: eessi-bot-casparvl arch: zen4 accel:nvidia/cc90 |
|
bot: build instance:eessi-bot-surf repo:eessi.io-2023.06-software arch:zen4 accel:nvidia/cc90 |
|
bot: build instance:eessi-bot-casparvl repo:eessi.io-2023.06-software arch:zen4 accel:nvidia/cc90 |
|
New job on instance
|
|
bot: build instance:eessi-bot-casparvl repo:eessi.io-2023.06-software arch:zen4 accel:nvidia/cc90 |
|
New job on instance
|
|
bot: build instance:eessi-bot-casparvl repo:eessi.io-2023.06-software arch:zen4 accel:nvidia/cc90 |
|
New job on instance
|
|
bot: build instance:eessi-bot-casparvl repo:eessi.io-2023.06-software arch:zen4 accel:nvidia/cc90 |
|
New job on instance
|
|
bot: build instance:eessi-bot-casparvl repo:eessi.io-2023.06-software arch:zen4 accel:nvidia/cc90 |
|
New job on instance
|
|
bot: build instance:eessi-bot-casparvl repo:eessi.io-2023.06-software arch:zen4 accel:nvidia/cc90 |
|
New job on instance
|
|
Trying to build with new args bot:build instance:eessi-bot-casparvl repo:eessi.io-2023.06-software on:arch=zen4,accel=nvidia/cc90 |
|
And again bot:build instance:eessi-bot-casparvl repo:eessi.io-2023.06-software on:arch=zen4,accel=nvidia/cc90 |
|
New job on instance
|
|
New job on instance
|
|
We failed to also pass the bot:build instance:eessi-bot-casparvl repo:eessi.io-2023.06-software on:arch=zen4,accel=nvidia/cc90 |
|
Parsing of the argument passed to the filters failed. Retrying with more verbose output to fix the issue bot:build instance:eessi-bot-casparvl repo:eessi.io-2023.06-software on:arch=zen4,accel=nvidia/cc90 |
3 similar comments
|
Parsing of the argument passed to the filters failed. Retrying with more verbose output to fix the issue bot:build instance:eessi-bot-casparvl repo:eessi.io-2023.06-software on:arch=zen4,accel=nvidia/cc90 |
|
Parsing of the argument passed to the filters failed. Retrying with more verbose output to fix the issue bot:build instance:eessi-bot-casparvl repo:eessi.io-2023.06-software on:arch=zen4,accel=nvidia/cc90 |
|
Parsing of the argument passed to the filters failed. Retrying with more verbose output to fix the issue bot:build instance:eessi-bot-casparvl repo:eessi.io-2023.06-software on:arch=zen4,accel=nvidia/cc90 |
|
bot:build instance:eessi-bot-casparvl repo:eessi.io-2023.06-software on:arch=zen4 for:arch=x86_64/amd/zen4 |
|
New job on instance
|
As expected, good. It only matches the CPU based zen4 partition. |
|
bot:build instance:eessi-bot-casparvl repo:eessi.io-2023.06-software for:arch=x86_64/amd/zen4 |
|
New job on instance
|
|
Launching with only the 'for' syntax implies a native build. This seems to work: as expected. |
|
bot:build instance:eessi-bot-casparvl repo:eessi.io-2023.06-software for:arch=x86_64/amd/zen4,accel=nvidia/cc90 |
Unable to clone the target repository. |
|
Hm, this is not how I envisioned it: This is the CPU only partition. How does this match? I thought the filter - explicitely stating that it requires an accelerator - would make sure it would only be matched if the context provides one, but that's not the case.... Relevant current code is: I'm not sure what's going on. The default is |
|
Ah, the problem is this: the default is false. And for the Should I make it Or is that too 'hard'? I.e. this would enforce that all action filter components are present in the context. It seems reasonable: if someone specifies a repository, you'd want But there may be a good reason for not having done this initially? |
|
Well, let's be strict... bot:build instance:eessi-bot-casparvl repo:eessi.io-2023.06-software for:arch=x86_64/amd/zen4,accel=nvidia/cc90 |
|
New job on instance
|
|
Excellent, this no longer matches: Now, the only match I get is: As intended. Note how the job.cfg is also correct in defining a native build |
|
bot:status |
|
This is the status of all the
|
|
bot:status |
9 similar comments
|
bot:status |
|
bot:status |
|
bot:status |
|
bot:status |
|
bot:status |
|
bot:status |
|
bot:status |
|
bot:status |
|
bot:status |
|
I don't get it, it seems to match the very first response by the bot, but that shouldn't be the case since that was a totally different format: How could that match? |
|
bot:status |
|
Aaah... It matches, because it considers everything from this part:
To be the instance name, and then it succesfully matches Ok, I should just try this in a fresh PR... I'll close it, make a new one. |
No description provided.