[JIRA] (JENKINS-38520) Every message in slave log appears twice with the -slaveLog option
Title: Message Title Matěj Korvas commented on JENKINS-38520 Re: Every message in slave log appears twice with the -slaveLog option Thanks for getting back to this. I am happy to believe that it was solved by Oleg's changes as commented above. If I happen to observe the erroneous behaviour again with a recent Jenkins version, I will update this ticket as suggested. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41176) InterruptedException during fingerprinting
Title: Message Title Matěj Korvas commented on JENKINS-41176 Re: InterruptedException during fingerprinting We have also observed this InterruptedErrorException on that line. Trying to figure out what could have caused it, I came across this Cloudbees Support page, which seems relevant and contains some advice. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40840) Jenkins never stops looking for next February 31st
Title: Message Title Matěj Korvas created an issue Jenkins / JENKINS-40840 Jenkins never stops looking for next February 31st Issue Type: Bug Assignee: Unassigned Components: next-executions-plugin Created: 2017/Jan/05 3:17 PM Environment: Jenkins 2.7.4, next-executions 1.0.11 Priority: Minor Reporter: Matěj Korvas After I configured a job to be triggered every 31st of February (an approximation of "never" when I already assumed a time trigger in my Job DSL), trying to view the folder that contains it would send Jenkins to an apparently endless loop, never returning the expected web page. Views not containing this job continued to work fine, however I still saw a close to 100% CPU usage on the server. I just saw there is a new version of the plugin available, sorry for not having tested it... on the other hand, I searched for a similar ticket several times and didn't find one. Add Comment
[JIRA] (JENKINS-38671) Email-ext plugin sending duplicate email notifications
Title: Message Title Matěj Korvas updated an issue Jenkins / JENKINS-38671 Email-ext plugin sending duplicate email notifications Change By: Matěj Korvas Comment: We have observed this behaviour too, running Jenkins 1.651.1, email-ext version 2.40.5.We have an email-ext post-build step as a substep of a Conditional Action (this didn't trigger in the case where we saw duplicate emails, they came from the post-build step described next), and as a separate post-build step. The "Trigger for matrix projects" option is set to "Trigger for each configuration" and the duplicate email is indeed sent for a failed matrix child build, as expected, just that it comes twice for the same configuration, build number, with the same timestamp. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38671) Email-ext plugin sending duplicate email notifications
Title: Message Title Matěj Korvas commented on JENKINS-38671 Re: Email-ext plugin sending duplicate email notifications We have observed this behaviour too, running Jenkins 1.651.1, email-ext version 2.40.5. We have an email-ext post-build step as a substep of a Conditional Action (this didn't trigger in the case where we saw duplicate emails, they came from the post-build step described next), and as a separate post-build step. The "Trigger for matrix projects" option is set to "Trigger for each configuration" and the duplicate email is indeed sent for a failed matrix child build, as expected, just that it comes twice for the same configuration, build number, with the same timestamp. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38520) Every message in slave log appears twice
Title: Message Title Matěj Korvas commented on JENKINS-38520 Re: Every message in slave log appears twice I have removed the note about potentially related issue of slaves failing to start. It turned out to be solvable by using the -text argument to slave.jar, while messages continue to be printed twice in slave logs. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38520) Every message in slave log appears twice
Title: Message Title
Matěj Korvas updated an issue
Jenkins / JENKINS-38520
Every message in slave log appears twice
Change By:
Matěj Korvas
Running a local slave, launched using a command, with the {{\-slaveLog}} option causes a log file to be written (as expected) with every message printed twice there, like this:{noformat}channel startedchannel startedchannel stoppedchannel stopped{noformat}(which is not expected).The launch script looks as follows ({{/home/matej/wc/jenkins}} is path to the Jenkins clone):{noformat}#!/bin/bash --norcexport TMP=$(mktemp -d --tmpdir jenkins-X)SLAVEJAR_URL=http://localhost:8080/jenkins/jnlpJars/slave.jarwget -q "${SLAVEJAR_URL:?}" -P "${TMP:?}" 2>&1_log_dir=/home/matej/wc/jenkins/work/logsmkdir -p "$_log_dir"_log=$(mktemp -u "$_log_dir/$(date -u +%Y%m%d-%H%M%S)-XXX")export JAVA_HOME=/usr/lib/jvm/java-7-oracle"$JAVA_HOME"/bin/java -jar "$TMP"/slave.jar \ -slaveLog "$_log"{noformat}I wondered whether it is just the messages that gets duplicated (perhaps caused by the {{TeeOutputStream}} created by the {{Launcher}} effectively outputting twice to the identical output stream) or if it is the threads calling {{Launcher.run()}} (I cannot imagine how that could happen). In our production Jenkins environment, we start slaves using a similar command and we see them fail to start more often than succeed, which could point to some concurrency issues.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38520) Every message in slave log appears twice
Title: Message Title Matěj Korvas updated an issue Jenkins / JENKINS-38520 Every message in slave log appears twice Change By: Matěj Korvas Environment: * Virtualbox 64-bit Ubuntu* Java 7, Oracle:java version "1.7.0_80" // Java(TM) SE Runtime Environment (build 1.7.0_80-b15) // Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)* Jenkins installed and run as described in [Building Jenkins| https://wiki.jenkins-ci.org/display/JENKINS/Building+Jenkins ] , except I checked out the LTS version tag 2.7.4 (remoting v2.60) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38520) Every message in slave log appears twice
Title: Message Title
Matěj Korvas updated an issue
Jenkins / JENKINS-38520
Every message in slave log appears twice
Change By:
Matěj Korvas
Environment:
* Virtualbox 64-bit Ubuntu* Java 7, Oracle: {noformat} java version "1.7.0_80" // Java(TM) SE Runtime Environment (build 1.7.0_80-b15) // Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode) {noformat} * Jenkins installed and run as described in [Building Jenkins|https://wiki.jenkins-ci.org/display/JENKINS/Building+Jenkins], except I checked out the LTS version tag 2.7.4 (remoting v2.60)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38520) Every message in slave log appears twice
Title: Message Title
Matěj Korvas created an issue
Jenkins / JENKINS-38520
Every message in slave log appears twice
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2016/Sep/26 9:17 PM
Environment:
* Virtualbox 64-bit Ubuntu * Java 7, Oracle: {noformat} java version "1.7.0_80" Java(TM) SE Runtime Environment (build 1.7.0_80-b15) Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode) {noformat} * Jenkins installed and run as described in [Building Jenkins|https://wiki.jenkins-ci.org/display/JENKINS/Building+Jenkins], except I checked out the LTS version tag 2.7.4 (remoting v2.60)
Labels:
slaves
Priority:
Minor
Reporter:
Matěj Korvas
Running a local slave, launched using a command, with the -slaveLog option causes a log file to be written (as expected) with every message printed twice there, like this:
channel startedchannel started
channel stoppedchannel stopped
(which is not expected). The launch script looks as follows (/home/matej/wc/jenkins is path to the Jenkins clone):
#!/bin/bash --norc
export TMP=$(mktemp -d --tmpdir jenkins-X)
SLAVEJAR_URL=h
[JIRA] [matrix-project-plugin] (JENKINS-27463) Operator {{in}} stopped working in Groovy expression in combination filter
Title: Message Title
Matěj Korvas commented on JENKINS-27463
Re: Operator {{in}} stopped working in Groovy _expression_ in combination filter
I just learned about this ticket and it appears as a duplicate of
JENKINS-28154
to me. Can it be marked as resolved then?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
