[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-releng-dev] workspace logs on jenkins?
|
Still no success, I gave up,
over to https://bugs.eclipse.org/bugs/show_bug.cgi?id=560654
On 24.02.20 07:16, Sravan K Lakkimsetti wrote:
Hi,
I configured to archive all .log files. Next build should have .log files
archived. If necessary we can archive workspace for debug purposes. But this has
to last resort and to be done only for a few builds(till the problem is debugged)
Thanks
Sravan
-----Original Message-----
From: Stephan Herrmann <stephan.herrmann@xxxxxxxxx>
Sent: 24 February 2020 03:15
To: platform-releng-dev@xxxxxxxxxxx
Subject: [EXTERNAL] Re: [platform-releng-dev] workspace logs on jenkins?
Two failed builds without a trace were:
https://ci.eclipse.org/jdt/job/eclipse.jdt.core-run.javac-1.8/151
https://ci.eclipse.org/jdt/job/eclipse.jdt.core-run.javac-1.8/152
As you can see in the config history, the latter build already tried to archive
the logs:
<hudson.tasks.ArtifactArchiver>
<allowEmptyArchive>false</allowEmptyArchive>
<artifacts>*/target/work/data/.metadata/.log</artifacts>
<caseSensitive>true</caseSensitive>
<defaultExcludes>true</defaultExcludes>
<fingerprint>false</fingerprint>
<onlyIfSuccessful>false</onlyIfSuccessful>
</hudson.tasks.ArtifactArchiver>
Anything wrong with that declaration? Is .log filtered by <defaultExcludes>?
For reference, the error message pointed to
/home/jenkins/agent/workspace/eclipse.jdt.core-run.javac-1.8/org.eclipse.jdt.core.tests.compiler/target/work/data/.metadata/.log
The build also mentioned:
13:59:57 Archiving artifacts
> The .log file are already configured and accessible from jenkins build > page
when available.
This seems true for the regular gerrit build, but not for this special build.
In the gerrit build I also see "**/hs_err_pid*.log", which I'll add to the
special builds, too, just in case the attempt to write the workspace log caused
a vm crash.
Since this hunt for a simple log file seems a science in itself, is it possible
to (exceptionally) preserve the entire workspace for trouble shooting? Makes me
feel like I want my shell access to the test machine :(
best,
Stephan
On 23.02.20 22:23, Mickael Istria wrote:
>
>
> On Sat, Feb 22, 2020 at 3:53 PM Stephan Herrmann
> <stephan.herrmann@xxxxxxxxx <mailto:stephan.herrmann@xxxxxxxxx>> wrote:
>
> I assume that workspaces disappear at the end of the job when also the executor
> terminates, right?
>
>
> Right.
>
> But surely there must be a remedy to keep the workspace when you must
> analyze it
> for failures, right?
>
>
> The CI Job configuration defines some "archiveArtifacts" that are
> stored and persisted after the build completes. The .log file are
> already configured and accessible from jenkins build page when
> available. However, it looks like the configuration may be missing this
specific file.
> Can you please share a link to the related build?
>
> Obviously, deploying the log file at the end of the build didn't work, because
> the build was aborted before trying to deploy anything.
>
>
> The main build can fail but the artifacts should still be archived. I
> don't think this is the main cause of the missing log.
>
>
>
> _______________________________________________
> platform-releng-dev mailing list
> platform-releng-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/platform-releng-dev
>
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev
