I'm having a build problem with jenkins, it has been working several months without any
problems, but now it says:
tar: Error exit delayed from previous errors
Build step 'Execute shell' marked build as failure
Checking console output
Finished: FAILURE
I tried to put more verbose to this build, but still the same error occurs.
I have looked from the shell logs and found that same error in there,
also I matched old build logs to this one and I cannot find any
several errors that would do this.
There's plenty of disk space left, also i raised open files, but the problem stays the same.
Could newly added class files do this kind of problem?
--bp
Related
I am trying to build a hello world project to see if gtk4-rs is working correctly, which always fails at creating the binaries. The rest of the build seems to fine (tried to run cargo clean and cargo check a couple of times, those do not produce any errors). My Cargo.toml just uses the version specified in the crate:
[dependencies]
gtk4 = "0.4.8"
My error is exactly the same as the one in this question, but running the cargo build in an admin powershell also fails with the same error.
I am on Win 11 and I've followed the installation instructions linked to by GTK themselves, https://github.com/wingtk/gvsbuild.
The linking error seems to indicate that gobject-2.0.lib is missing:
LINK : fatal error LNK1181: cannot open input file 'gobject-2.0.lib'
(Full error message (with redacted user directory) on Pastebin)
That file is found at c:\gtk-build\gtk\x64\release\lib, which is the default location for an installation produced by gvsbuild, as far as I can tell (I haven't messed with the files at all).
Both c:\gtk-build\gtk\x64\release\lib and c:\gtk-build\gtk\x64\release\bin are part of the path, restarting the machine did not seem to fix anything in this regard either.
I have not found anything close to helpful on the internet, so any pointers to what could be wrong here would be great.
I am trying to run the Google Cardboard sample by following their guide: https://developers.google.com/cardboard/develop/c/quickstart
However, I run into the same error mentioned in this guide. Their solution was:
You should click the "assemble" option under ":sdk", not the one under ":hellocardboard-android".
As shown below:
The following is the image of my window. I don't have the :hellocardboard-android or :sdk folders, just Tasks.
So, is this the right assemble to be running? I am not sure how to see the other folders mentioned. If you have any clarifying questions let me know!
My full error:
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ':hellocardboard-android:externalNativeBuildDebug'.
Build command failed.
Error while executing process C:\Users\Jonah\AppData\Local\Android\Sdk\cmake\3.10.2.4988404\bin\ninja.exe with arguments {-C O:\Dordt University Campus\hellocardboard-android.cxx\cmake\debug\armeabi-v7a cardboard_jni}
ninja: Entering directory `O:\Dordt University Campus\hellocardboard-android.cxx\cmake\debug\armeabi-v7a'
ninja: error: '../../../../libraries/jni/armeabi-v7a/libcardboard_api.so', needed by '../../../../build/intermediates/cmake/debug/obj/armeabi-v7a/libcardboard_jni.so', missing and no known rule to make it
It appears the problem had to do with the path having spaces, moving the project caused the proper folders to appear in the Gradle window.
Somehow this week my cygwin installation broke down, giving the following error when I try to start it:
Error: Could not fork child process: Resource temporarily unavailable (-1).
DLL Rebasing may be required see 'rebaseall / rebase --help'.
So far so good, a google search easily points to many places explaining how to perform the rebasing.
However, when I then follow the instructions to rebase:
Open cmd.exe as administrator
cd in \cygwin\bin
run ash /usr/bin/rebaseall
However, then I get a similar error to what I was trying to solve by rebaseing:
0 [main] ash (14624) c:\cygwin\bin\ash.exe: *** fatal error - cygheap base mismatch
detected - 0xCB8408/0xD28408.
This problem is probably due to using incompatible versions of the cygwin DLL.
Search for cygwin1.dll using the Windows Start->Find/Search facility
and delete all but the most recent version. The most recent version *should*
reside in x:\cygwin\bin, where 'x' is the drive on which you have
installed the cygwin distribution. Rebooting is also suggested if you
are unable to find another cygwin DLL.
0 [main] ash 7140 fork: child -1 - forked process 14624 died unexpectedly, retry 0,
exit code 0xC0000142, errno 11/usr/bin/rebase-trigger: 33: /usr/bin/rebase-trigger:
Cannot fork
So, I searched for the cygwin1.dll build only one was found.
Does anyone have some clues what more I could try to fix this?
You need to delete the PortableGit folder
Go to the GitHub AppData folder: C:\Users\[username]\AppData\Local\GitHub
Delete the folder PortableGit*...
I am trying to Install Cygwin 64 bit on a Windows 2012R2 (64 bit).
Downloading and initial setup went through but when it reached man-db (/etc/postinstall/man-db) the setup hangs
and remains so forever. I waited more than 1.5 Hours but still no progress.
I checked log file in /var/log/setup.log which has following contents.
Updating index cache for path `/usr/share/man/man1'. Wait...
Processing manual pages under /usr/share/man...
/usr/bin/mandb: warning: /usr/share/man/man1/col.1.gz: whatis parse for col(1) failed
/usr/bin/mandb: warning: /usr/share/man/man1/imv.1 is a dangling symlink
/usr/bin/mandb: iconv_open ("UTF-8//IGNORE", "utf8"): Invalid argument
/usr/bin/mandb: warning: /usr/share/man/man1/mc.1.gz: whatis parse for mc(1) failed
I am not sure if I should cancel and start again. Will this setup come out of this stage with at least some error?
Did anyone install 64 bit Cygwin and got this error ?
Please help
Happens to me often. I was setting up 8 servers this week and it happened to 3 of them. Waited many hours and it is still would not finish. Sometimes the re-installation works, some it does not. So I have resorted to kill the mandb.exe process and that allows the installer to finish normally. So far I have found no side effects of doing so.
After waiting for more than 3 hours, I decided to cancel the setup. Then I tried a reinstall, following the steps exactly as in the first install. I did not add or remove any packages. The already selected packages in the first attempt were recognized as installed. This time, the setup stopped at the above step (man-db) briefly and then completed the installation. No errors. So, re-installation solved my problem.
Late to the party, but —
When mandb.exe hung, I killed its parent bash.exe via Task Manager and the installation completed.
I then killed mandb.exe in Task Manager, since it was still running.
I then opened a Cygwin shell and ran mandb -cds. -c recreates the index, -d prints messages (so you can actually tell it's doing something constructive!) and -s suppresses checking for orphaned formatted manual pages ("stray cats").
As I write this, mandb is still chugging along, three or four hours later, with plenty yet to go.
So I'll remember to file a bug report later :) , I did notice one oddity during the mandb run:
mandb: /usr/share/man/man3/jN.3 is self referencing
mandb: warning: /usr/share/man/man3/jnf.3.gz: bad symlink or ROFF `.so' request
I've been struggling with the same problem today until I realised that moving the main Cygwin setup window revealed a popup complaining about "can't open (null) for reading: no such file"
This happens multiple times in a (re)install
I am currently trying to run Coverity Prevent and I believe I have everything set up appropriately on my windows 7 build machine. I have run it with AnthillPro and when my code finishes and gets to Coverity it says that everything was built fine and the only error I get is:
Warning: Cygwin pathname conversion ignored; no applicable
'bash'/'mount', 'cygpath', or registry keys found.
I have even tried to install Cygwin to see if this could rectify the problem and I still end up with the same error.
I am currently using AnthillPro 3.7 and Coverity 5.5.3. The build log says that I have warnings but no errors and that it hasn't emitted anything. I have tried to run a script directly from the machine (not server) itself and I have the same error as I do using the Coverity Prevent in Anthill
This is the only information I get at the bottom of the build log.
Run from AnthillPro:
Build time (cov-build overall): 00:00:17.753597
[WARNING] No files were emitted. This may be due to a problem with your configuration
or because no files were actually compiled by your build command.
Please make sure you have configured the compilers actually used in the compilation.
For more details, please look at:
d:\Coverity\Intermediate\AllToolsProjects.sln_pc_vs2010\build-log.txt
Run from Script:
The cov-build FAILED.
This may be because less than 90 percent of units were successfully compiled
Check for errors here:
D:\\Coverity\Scripts\build_AllToolsProjects.sln_pc_vs2010.bat
D:\\Coverity\Intermediate\AllToolsProjects.sln_pc_vs2010\build-log.txt
D:\\Coverity\Configuration\pc_vs2010
It sounds like you haven't configured the compiler - that's when you tell your Coverity Analysis installation which compiler you are using. devenv is not a compiler, cl.exe is.
Run the following command:
coverity-analysis-dir/bin/cov-configure --msvc
This will say that you are using the cl.exe compiler and it's of type msvc no matter where it's installed.
Then rerun your Coverity build and see if it captures more of your compilations.