You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
is the only thing that looks like a error, it is likely the warning that cloning an empty repo in the beginning.
this part is not clear, should it ignore this? its not even clear which testcase it is that failed (i think its "pre-push" from the repo name) and the failing assert is on line 102 of t-pre-push.sh
# CREDS received command: store (ignored)
# CREDS received command: store (ignored)
but the output is pretty unclear on what is expected? should it ignore or not?
To Reproduce
Steps to reproduce the behavior:
run repobuild on a custom minimal copy of alpine community to build gitea and its dependencies that live in the community repo.
i can supply a minimal example if needed but since its really a question about what the testsuite complains about it does not seem warranted to go through the downstream process of packaging, the packaging 'sources' are located here https://git.alpinelinux.org/aports/tree/community/git-lfs?h=3.19-stable and yes i know i'm building a part of 3.19-community on top of 3.18-main.
Expected behavior
test suite should tell why it failed, and do it clear enough.
System environment
proxmox 8.1 + alpine 3.18.6 container using alpine supplied main repo and builds its own minimal alpine-bootstrap with stuff from 3.19-community repo due to 3.18-community is EOL.
Output of git lfs env git: 'lfs' is not a git command. See 'git --help' (this is expected since its during packaging of the git-lfs the testing occurs)
Additional context
proxmox lxc-container lives on openzfs-2.2.2 pool. not that it should matter on the missing error information in the output of the testsuite..
The text was updated successfully, but these errors were encountered:
Sorry you're having trouble. The reason this is failing is the error in the stderr block just before end_test. That's going to be the case in pretty much all of our shell tests, and due to the way shell works, it's going to be nearly impossible to annotate everything with nice error messages. Git's testsuite works the same way, but is even worse about this.
So the assertion that's failing is [ "$(du -k push.log | cut -f 1)" == "0" ]. You'd want to figure out why your version of du -k is printing 1 instead of 0 here, which probably involves figuring out what exactly is in push.log. Usually the output is somewhere under t/remote.
Describe the bug
during the packaging process, the APKBUILD script runs the testsuite, and it fails on t-pre-push., not sure why
the question is what is it that failed? from the output that the testcase printed its not clear what actually failed?
is the only thing that looks like a error, it is likely the warning that cloning an empty repo in the beginning.
this part is not clear, should it ignore this? its not even clear which testcase it is that failed (i think its "pre-push" from the repo name) and the
failing assert is on line 102 of t-pre-push.sh
but the output is pretty unclear on what is expected? should it ignore or not?
To Reproduce
Steps to reproduce the behavior:
i can supply a minimal example if needed but since its really a question about what the testsuite complains about it does not seem warranted to go through the downstream process of packaging, the packaging 'sources' are located here https://git.alpinelinux.org/aports/tree/community/git-lfs?h=3.19-stable and yes i know i'm building a part of 3.19-community on top of 3.18-main.
Expected behavior
test suite should tell why it failed, and do it clear enough.
System environment
proxmox 8.1 + alpine 3.18.6 container using alpine supplied main repo and builds its own minimal alpine-bootstrap with stuff from 3.19-community repo due to 3.18-community is EOL.
Output of
git lfs env
git: 'lfs' is not a git command. See 'git --help'
(this is expected since its during packaging of the git-lfs the testing occurs)Additional context
proxmox lxc-container lives on openzfs-2.2.2 pool. not that it should matter on the missing error information in the output of the testsuite..
The text was updated successfully, but these errors were encountered: