Friday, March 1, 2024
HomeGolangFailing assessments in 1.21.6 bootstrap - Getting Assist

Failing assessments in 1.21.6 bootstrap – Getting Assist

I need assistance with bootstrapping 1.21.6. A number of assessments fail and I see there are necessities about gdb, swig and so on, nonetheless, they’re arduous to guess.

3 errors deadly error: hint: ReadTrace acquired invalid frequency in
os/sign -src/runtime/panic.go
syscall – exec_linux_test.go:354: Cmd failed with err fork/exec /tmp/go-build1662809362/b1680/syscall.check: no such file or listing, it’s repeated aslo with TestUnshareUidGidMapping
runtime/hint -runtime/panic.go

I suppose these errors are generated by 2 assessments particularly
TestUnshareUidGidMapping TestAnalyzeAnnotations however they write the hint in parallel and it’s a mess.

7 fails in git assessments in vcstest_test.go

It may be an outdated git?

And another:
go instrument dist check -run=^archive/tar$
Failed: exit standing 1

Please inform what I ought to set up or tips on how to repair them.

1 Like

1. Handle Lacking Dependencies:

  • Set up gdb and swig: These are important for elements of the Go construct course of. Use your system’s package deal supervisor to put in them:
    • Ubuntu/Debian: sudo apt set up gdb swig
    • Fedora/CentOS: sudo dnf set up gdb swig
    • macOS: brew set up gdb swig

2. Resolve “Cmd failed with err fork/exec…” Errors:

  • Test file permissions: Guarantee non permanent construct recordsdata are created with right permissions:
    • Briefly disable any safety software program which may intervene with file creation.
    • Confirm that the person operating the construct has write permissions in /tmp .

3. Repair “hint: ReadTrace acquired invalid frequency” Errors:

  • Assessment hint configuration: Test if any trace-related instruments or settings battle with the Go construct course of.
  • Improve Go model: Take into account updating to a more moderen model (1.21.7 or later) if accessible, because it might need bug fixes associated to hint performance.

4. Handle Failed Git Checks:

  • Improve Git: Guarantee you could have the most recent model of Git put in.
  • Confirm atmosphere variables: Test if any Git-related atmosphere variables are set incorrectly.
  • Assessment check scripts: If doable, study the failing Git check scripts to pinpoint particular points.

5. Troubleshoot “archive/tar” Take a look at Failure:

  • Examine logs: Search any error messages or clues within the construct logs associated to archive/tar assessments.
  • Assessment check code: If doable, study the check code for potential points or dependencies.
  • Take into account cross-compiling: If constructing for a distinct structure, guarantee you could have the required cross-compilation instruments and dependencies.



Please enter your comment!
Please enter your name here

Most Popular

Recent Comments