Closed cdietrich closed 5 years ago
have no idea which update site the feature was pulled from before
No repository found at http://download.eclipse.org/modeling/tmf/xtext/updates/nightly/head. => @kthoms is our nightly update site broken?
i wonder how this can happen. do we delete stuff and then decide not to redeploy cause we think it is already deployed?
publish.build.stage.2:
[echo] Used launcher: /opt/public/common/buckminster-4.3/plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
[java] Picked up JAVA_TOOL_OPTIONS: -Xmx2G -Djava.io.tmpdir=/tmp/genie.xtext
[java] Buildfile: /jobs/genie.xtext/common-deploy/workspace/build-result/promoter.ant
[java]
[java] -check.property.file.location:
[java]
[java] -load.properties.as.is:
[java]
[java] -load.properties.with.prefix:
[java]
[java] -load.properties:
[java]
[java] publish.build.from.framework:
[java]
[java] publish:
[java]
[java] echo-status:
[java] [echo] Build N201905291758 already promoted, nothing to do...
[java] BUILD SUCCESSFUL
[java]
[java] BUILD SUCCESSFUL
[java] Total time: 0 seconds
or is this done by https://ci.eclipse.org/xtext/job/xtext-snapshots ? https://ci.eclipse.org/xtext/job/xtext-snapshots/1074/console
Could not read error output of command '/opt/public/common/java/oracle/jdk1.8.0_192_x64/jre/bin/pack200'.
java.io.IOException: Stream Closed
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:326)
at org.gradle.process.internal.streams.ExecOutputHandleRunner.forwardContent(ExecOutputHandleRunner.java:66)
at org.gradle.process.internal.streams.ExecOutputHandleRunner.run(ExecOutputHandleRunner.java:52)
at org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable.run(CurrentBuildOperationPreservingRunnable.java:42)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
at java.lang.Thread.run(Thread.java:748)
Pack build-result/p2.repository/plugins/org.eclipse.xtext.ui.t
but build was green anyway
still have no idea who delete the dir and how to recreate it
zips are bad too https://www.eclipse.org/modeling/tmf/downloads/
Sebastian reverted the change to publishing so the nightly is deployed again
@kthoms @Hejado how shall we proceed. are you working on a fix for xtext/publishing
Didn't we already find/fix the issue for this on monday, @kthoms ?
Not sure, if I'm missing something...
We have a fix and it is available on the branch. We should merge that when we have the time to repair it for the case that something breaks. I think we should do this on tuesday. I don't have time today/tomorrow.
@kthoms still does not work. try to revert your changes again
the xtext-snapshots has also bogus messages in the log
Pack build-result/p2.repository/plugins/org.eclipse.xtext.ui.codetemplates.ui_2.19.0.v20190618-0537.jar
Could not read error output of: command '/opt/public/common/java/oracle/jdk1.8.0_192_x64/jre/bin/pack200'.
java.io.IOException: Stream Closed
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:326)
at org.gradle.process.internal.streams.ExecOutputHandleRunner.run(ExecOutputHandleRunner.java:55)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:46)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
deploy did not work cause it thinks its already deployed this crap needs to be more stable
[java] echo-status:
[java] [echo] Build N201906180629 already promoted, nothing to do...
[java] BUILD SUCCESSFUL
@kthoms
[ERROR] Failed to resolve target definition /home/travis/build/itemis/xtext-reference-projects/greetings-tycho/2.19.0/org.xtext.example.mydsl.target/org.xtext.example.mydsl.target.target: Failed to load p2 metadata repository from location https://download.eclipse.org/modeling/tmf/xtext/updates/nightly/: Unable to read repository at https://download.eclipse.org/modeling/tmf/xtext/updates/nightly. Artifact not found: https://download.eclipse.org/modeling/tmf/xtext/updates/nightly/head/content.xml.xz. -> [Help 1]
=> the update site is deleted again
https://ci.eclipse.org/xtext/job/xtext-snapshots/1119/console is red
Will check today
Download folder contains "workspace.zip"
The zip file should be N
still an issue
log contains
Additional action for task ':zipXtextP2Repository': was implemented by the Java lambda 'io.typefox.publishing.EclipsePublishing$$Lambda$159/568787640'. Using Java lambdas is not supported, use an (anonymous) inner class instead.
this might be the issue.
we call doFirst and doLast at several places. the generated code looks like
final Action<Task> _function_13 = (Task task2) -> {
.....
We changed recently the Xtext/Xtend version in publishing/buildSrc/build.gradle
. Has this something to do with that?
Note: The issue might be resolved with the new deployment job on ci-staging.
yes. i converted the lamdas to classes. lets see what happens
yes but the code is broken
task viech(type: Zip) {
//archiveFileName = "my-distribution.zip"
destinationDirectory = file("$buildDir/dist")
from "lele"
archiveFileName = provider {
"demo.zip"
}
}
is needed with newer gradle
also the gradle api still seems 4.8 am not sure why
First successful deployment with new job sign-and-deploy:
director -l -r http://download.eclipse.org/modeling/tmf/xtext/updates/composite/latest/
201906242045.Default=1.0.0.8h3-cKYB3-_kE7Ag7QAY3AgMU
201906242045.mwe2lang=1.0.0.67U3cLSXLr7E7Ag7UEME7MQ
a.jre.javase=10.0.0
a.jre.javase=10.0.0
a.jre.javase=11.0.0
a.jre.javase=11.0.0
com.google.guava=27.1.0.v20190517-1946
com.google.guava=27.1.0.v20190517-1946
com.google.guava.source=27.1.0.v20190517-1946
com.google.guava.source=27.1.0.v20190517-1946
...
org.eclipse.xtext=2.19.0.v20190628-0955
org.eclipse.xtext.activities=2.19.0.v20190703-0145
org.eclipse.xtext.activities.source=2.19.0.v20190703-0145
org.eclipse.xtext.builder=2.19.0.v20190703-0145
org.eclipse.xtext.builder.source=2.19.0.v20190703-0145
...
=> you use the workspace zip name and rename back? i have pushed a fixed version for the broken api
No, I ignore the zip that the publishing plugin creates and zip it with a shell command.
=> the plugin still creates a zip with wrong name
should the nightly deploy job be deactivated too?
nightly-deploy
it triggers the common-deploy
and simrel-tests
job nightly with the result from xtext-snapshots
.
The new job combines that all together. It runs nightly for the master
branch, builds the repository for upload and deploys it to the nightly site. It is also already prepared to do the same for milestone/release builds.
I have disabled nightly-deploy
now.
https://download.eclipse.org/modeling/tmf/xtext/updates/nightly/ contains the latest build result from the sign-and-deploy job. This job is triggered nightly for branch master.
I consider this fixed now.
??????????