Only include files modified by the PR in tarball#1119
Only include files modified by the PR in tarball#1119boegel merged 6 commits intoEESSI:2023.06-software.eessi.iofrom
Conversation
|
Instance
|
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:x86_64/amd/zen2 |
Updates by the bot instance
|
|
New job on instance
|
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:x86_64/amd/zen2 |
|
This also was not triggered in this case: New job on instance
|
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:x86_64/amd/zen2 |
|
This seems to work as expected, in the Slurm logs I see: New job on instance
|
|
NOTE This PR does not need to be deployed |
| } | ||
|
|
||
| file_changed_in_pr() { | ||
| local full_path="$1" |
There was a problem hiding this comment.
We should also check that full_path is not empty?
There was a problem hiding this comment.
Isn't that kind of done at line 16?
There was a problem hiding this comment.
test -f (without argument) exits with zero, so I'd say no
There was a problem hiding this comment.
Interestingly, test -f "" does fail with non-zero exit code, so it's fine as is I guess, don't want to nitpick here...
There was a problem hiding this comment.
You had me sweating but
ocaisa@~$ export full_path="$PWD/file"; [[ -f "$full_path" ]] || echo Fail
Fail
ocaisa@~$ touch file
ocaisa@~$ export full_path="$PWD/file"; [[ -f "$full_path" ]] || echo Fail
ocaisa@~$ export full_path=""; [[ -f "$full_path" ]] || echo Fail
Fail
ocaisa@~$ export full_path= ; [[ -f "$full_path" ]] || echo Fail
Fail
ocaisa@~$ unset full_path
ocaisa@~$ [[ -f "$full_path" ]] || echo Fail
Fail
so the check below is indeed enough
Co-authored-by: Kenneth Hoste <kenneth.hoste@ugent.be>
|
One more test run to rule out utter breakage (I'm aware no deploy is needed here): bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:x86_64/amd/zen2 |
|
New job on instance
|
boegel
left a comment
There was a problem hiding this comment.
looks fine, if there's any fallout we'll deal with it in a follow-up PR
5ca8e88
into
EESSI:2023.06-software.eessi.io
No description provided.