Jenkinsfile: avoid errors from find#39685
Conversation
|
OK, I'm not sure why but the old Jenkinsfile is used. How do I test changes to Jenkinsfile? @andrewhsu maybe you know? |
|
@kolyshkin I think Jenkins is configured to accept jenkinsfile changes only from certain people/users @psftw could you check? |
|
@kolyshkin the For now, the old jenkins.dockerproject.org PR check job janky is still run which does not use |
There was a problem hiding this comment.
your find assumes a certain working directory, which looks incorrect (it's one level deeper) and btw will most certainly fail on my PR (#39682), so you should probably make this more robust. Does ** work for arbitrarily nested ?
|
My find was not doing what it should to begin with. Please see updated commit. |
|
forgot |
|
it works (almost... I had not anticipated |
|
Note that there are tests with subtests that have deeper directory nesting |
it does not matter for |
|
Ah, okay; that looks good (thought I'd double-check) |
This commit is not changing anything wrt how deep |
|
Not sure what went wrong on RS1 https://jenkins.dockerproject.org/job/Docker-PRs-WoW-RS1/26308/console Triggering again |
|
@kolyshkin still WIP? |
|
needs a rebase now; probably should be copied to all stages? |
There are many errors like this one: > 01:39:28.750 find: ‘bundles/test-integration/dbc77018d39a5/root/overlay2/f49953a883daceee60a481dd8e1e37b0f806d309258197d6ba0f6871236d3d47/work/work’: Permission denied (probably caused by bad permissions) These directories are not to be looked at when we search for logs, so let's exclude them. It's not super easy to do in find, here is some kind of an explanation for find arguments ``` PATTERN ACTION OR PATTERN ACTION -path X -prune -o -type f [AND] (-name A -o name B) -print ``` (here -o means OR, while AND is implicit) While at it, - let the find know we're only looking for files, not directories - remove a subshell and || true - remove `-name integration.test` (there are no such files) Signed-off-by: Kir Kolyshkin <[email protected]>
|
rebased; should be good to go but let's wait for ci |
|
|
exp CI restarted |
|
CI error in docker-py, not sure why but def unrelated. |
|
OK this one is ready, artifacts looks same as before i.e. seems to be no regression |
|
opened a PR for the failing docker-py test (my bad); #39714 |
|
Output looks good: no more errors/warnings: Bundles look good; Before this patch: After this patch applied: |
|
I'm merging this one 👍 |
There are many errors like this one:
(probably caused by bad permissions)
These directories are not to be looked at when we search for logs, so
let's exclude them. While at it, let the find know we're only looking
for files.