-
Notifications
You must be signed in to change notification settings - Fork 0
Test bot status command #2
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
base: main
Are you sure you want to change the base?
Conversation
|
bot:build instance:eessi-bot-casparvl repository:eessi.io-2023.06-software on:arch=zen2 for:arch=x86_64/amd/zen2 |
Unable to download or merge changes between the source branch and the destination branch. |
|
bot:build instance:eessi-bot-casparvl repository:eessi.io-2023.06-software on:arch=zen2 for:arch=x86_64/amd/zen2 |
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
bot:build instance:eessi-bot-casparvl repository:eessi.io-2023.06-software on:arch=zen2 for:arch=x86_64/amd/zen2 |
|
New job on instance
|
|
bot:status last_build |
3 similar comments
|
bot:status last_build |
|
bot:status last_build |
|
bot:status last_build |
|
This is the status of all the
|
|
That looks good, it correctly deduplicated the on:arch=zen4 for:arch=x86_64/amd/zen4 and on:arch=zen4,accel=nvidia/cc90 for:arch=x86_64/amd/zen4 builds, which are for the same architecture and should thus be deduplicated. |
|
This is the status of all the
|
|
Is it now pasting that output because of my earlier comment? :\ or was it just a delayed response to my original command (to which it didn't seem to respond)? |
|
Hmmm, one small issue, it seems to have printed the first build for each... Should I not have done the |
|
bot:status last_build |
1 similar comment
|
bot:status last_build |
|
This is the status of all the
|
|
Sorted status table seems ok: It seems to have put the highest time stamps first. E.g. looking at the zen2 builds, we see |
|
bot:status last_build |
|
This is the status of all the
|
|
Ok, I was stupid, I created a |
|
bot:status last_build |
|
This is the status of all the
|
|
This is the status of all the
|
|
Great, that looks more like it. To make it even nicer, let's sort again on the 'for' target, just so we get an alphabetically sorted table. |
|
bot:status last_build |
|
This is the status of all the
|
|
Now really with resorting... bot:status last_build |
|
This is the status of all the
|
|
Now with sorting applied to the right table... bot:status last_build |
|
This is the status of all the
|
|
Test commit EESSI/eessi-bot-software-layer@3fc6a6e bot:status last_build |
|
This is the status of all the
|
|
Test commit EESSI/eessi-bot-software-layer@7b284ba bot:status last_build |
|
This is the status of all the
|
|
Let's make sure we also didn't break the original command: bot:status |
|
This is the status of all the
|
No description provided.