rfan1
rfan1
> @rfan1 can you provide a failing case? http://openqa.suse.de/tests/9171525#step/system_prepare/5 But, I don't have any job can explain without "sync" cmd, the job failed one. however, I think it makes sense...
> > @rfan1 can you provide a failing case? Let me try to set the disk size to 40GB and trigger a failed job then, hold on the merge process
> > > @rfan1 can you provide a failing case? > > Let me try to set the disk size to 40GB and trigger a faild job then, hold on...
> It's not really a regex, more of a string match. It may fail in the future but it will fail loudly and we can attempt a regex then. If...
> @rfan1 Do we want to continue working on this? @foursixnine I would hold on this PR: 1. the issue was not seen any more after increasing the disk size...
Mark it as WIP due to the discussion in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18270
> Should also this line be changed? -> > > https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/bebe56bb31c8baa9f4ee7e71c9adb105ac7d399b/Makefile#L118 > ? done
Thanks all for the kindly feedback. I will hold on this PR due to some risks
> You can just follow the suggestion in [#16497 (comment)](https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16497#issuecomment-1449668278) to have the "changed" target called in GitHub actions for pull requests, the complete one otherwise. I suggest to look...
@foursixnine Seems it is hard to define the different job for ci check for both push and pull_request, so I create a new file