Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update GitHub Actions #742

Merged
merged 2 commits into from
Nov 2, 2022
Merged

Update GitHub Actions #742

merged 2 commits into from
Nov 2, 2022

Conversation

DimitriPapadopoulos
Copy link
Contributor

@DimitriPapadopoulos DimitriPapadopoulos commented Sep 20, 2022

Unfortunately tipi-build-linux fails with:

● [err] Dynamic exception type: std::runtime_error
std::exception::what: can not create git repository [-3] - config value 'safe.directory' was not found

● [err] Something went wrong, for help on your issue, we would enjoy getting your report at https://tipi.build/#contact
Error: Process completed with exit code 1.

@DimitriPapadopoulos DimitriPapadopoulos marked this pull request as ready for review September 20, 2022 07:39
@t-mat
Copy link
Contributor

t-mat commented Sep 20, 2022

Hi @DimitriPapadopoulos , thanks for the PR. I also don't understand what happens with tipi.

● [err] Something went wrong, for help on your issue, we would enjoy getting your report at https://tipi.build/#contact
Error: Process completed with exit code 1.

@pysco68 , since I think we're not cutomer of the tipi.build service, we can't contact/report this issue directly.
Could you help us to resolve this issue?

@DimitriPapadopoulos
Copy link
Contributor Author

DimitriPapadopoulos commented Sep 20, 2022

The strange thing is that reverting my change for tipi-build-linux fails too. I don't know what tipi is, and the error message does not really help:

config value 'safe.directory' was not found

@DimitriPapadopoulos
Copy link
Contributor Author

https://git-scm.com/docs/git-config#Documentation/git-config.txt-safedirectory

safe.directory

These config entries specify Git-tracked directories that are considered safe even if they are owned by someone other than the current user. By default, Git will refuse to even parse a Git config of a repository owned by someone else, let alone run its hooks, and this config setting allows users to specify exceptions, e.g. for intentionally shared repositories [...]

@DimitriPapadopoulos
Copy link
Contributor Author

While this is only a warning, I think it's the same problem:

▼ Run mkdir -p ~/.tipi
 mkdir -p ~/.tipi
 shell: sh -e {0}
 env:
   HOME: /root
WARNING: Error loading config file: /root/.docker/config.json: open /root/.docker/config.json: permission denied

@DimitriPapadopoulos
Copy link
Contributor Author

I'll try to revert again from v3 to v2, I must have done something wrong when reverting last time:

▼ Run actions/checkout@v3
  with:
    repository: Cyan4973/xxHash
    token: ***
    ssh-strict: true
    persist-credentials: true
    clean: true
    fetch-depth: 1
    lfs: false
    submodules: false
    set-safe-directory: true
  env:
    HOME: /root
/usr/bin/docker exec  84ed8eaf7dd9f6139174d1635c373866149763118b56d824b2efebbf58d81c60 sh -c "cat /etc/*release | grep ^ID"
WARNING: Error loading config file: /root/.docker/config.json: open /root/.docker/config.json: permission denied
Syncing repository: Cyan4973/xxHash
▼ Getting Git version info
  Working directory is '/__w/xxHash/xxHash'
  /usr/bin/git version
  git version 2.25.1

@DimitriPapadopoulos
Copy link
Contributor Author

We get the same errorr with v2:

▼ Run actions/checkout@v2
  with:
    repository: Cyan4973/xxHash
    token: ***
    ssh-strict: true
    persist-credentials: true
    clean: true
    fetch-depth: 1
    lfs: false
    submodules: false
    set-safe-directory: true
  env:
    HOME: /root
/usr/bin/docker exec  e272b64d51a78baf0f1958fe1d1bbfd3c13999a74103a39be35407b1d6bd4944 sh -c "cat /etc/*release | grep ^ID"
WARNING: Error loading config file: /root/.docker/config.json: open /root/.docker/config.json: permission denied
Syncing repository: Cyan4973/xxHash
▼ Getting Git version info
  Working directory is '/__w/xxHash/xxHash'
  /usr/bin/git version
  git version 2.25.1
● [err] Dynamic exception type: std::runtime_error
std::exception::what: can not create git repository [-3] - config value 'safe.directory' was not found

● [err] Something went wrong, for help on your issue, we would enjoy getting your report at https://tipi.build/#contact

It looks like a tipi new bug, unrelated to this merge request.

@Cyan4973
Copy link
Owner

The proposed PR looks good to me.
The CI test issue seems to be on the tipi side.

@Cyan4973 Cyan4973 merged commit 267ba94 into Cyan4973:dev Nov 2, 2022
@DimitriPapadopoulos DimitriPapadopoulos deleted the actions branch November 3, 2022 08:49
@Cyan4973
Copy link
Owner

It looks like Github Action tests are no longer active right after this PR.

Investigation ongoing ...

@DimitriPapadopoulos
Copy link
Contributor Author

DimitriPapadopoulos commented Nov 10, 2022

But tests were working on my branch before merging, weren't they?

@DimitriPapadopoulos
Copy link
Contributor Author

DimitriPapadopoulos commented Nov 10, 2022

I see them not working after 63356da, but it's tipi not working, again:
xxHash

I don't see how this PR could be involved.

@DimitriPapadopoulos
Copy link
Contributor Author

/usr/local/share/.tipi/w/cli-89765bc/xsum_bench.c:33:10: error: '../xxhash.h' file not found, did you mean 'xxhash.h'?
#include "../xxhash.h"
         ^~~~~~~~~~~~~
         "xxhash.h"
[ 42%] Building C object CMakeFiles/cli-89765bc.dir/usr/local/share/.tipi/w/cli-89765bc/xsum_sanity_check.c.o
1 error generated.

@t-mat
Copy link
Contributor

t-mat commented Nov 10, 2022

@DimitriPapadopoulos sorry for bothering!
#758 and further PRs will resolve CI and tipi.build issues.

@Cyan4973
Copy link
Owner

Yeah, sorry for the noise @DimitriPapadopoulos ,
it's just a time coincidence,
the problem actually comes from another part of CI (tipi).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants