| commit | 53d11f8d2026701aa74a690cb7375546830d4c70 | |
| author | Kyle J. McKay <mackyle@gmail.com> | |
| Sun, 16 Aug 2020 04:54:57 +0000 (15 21:54 -0700) | ||
| committer | Kyle J. McKay <mackyle@gmail.com> | |
| Sun, 16 Aug 2020 04:54:57 +0000 (15 21:54 -0700) | ||
| tree | 2b6291bd917635132b8958170e87c47b05982097 | treesnapshot (tar.gz zip) |
| parent | fa57e21738b6f4df246a4a61fbdea934dc8256fc | commitdiff |
taskd/clone.sh: do not rely on SIGXFSZ error
The actual git process that ends up dying as a result of a SIGXFSZ
when it attempts to create a file that's too large will almost
certainly not be the initial git process that's running the fetch.
As a result, the actual error exit code will end up being something
much less helpful.
Attempt to detect this situation by looking for any files that
have the same size as the file size limit and trigger the exceeds
file size limit that way as well.
Signed-off-by: Kyle J. McKay <mackyle@gmail.com>
The actual git process that ends up dying as a result of a SIGXFSZ
when it attempts to create a file that's too large will almost
certainly not be the initial git process that's running the fetch.
As a result, the actual error exit code will end up being something
much less helpful.
Attempt to detect this situation by looking for any files that
have the same size as the file size limit and trigger the exceeds
file size limit that way as well.
Signed-off-by: Kyle J. McKay <mackyle@gmail.com>
| taskd/clone.sh | diffblobblamehistory |