This is an automated email from the ASF dual-hosted git repository.
tibordigana pushed a change to branch SUREFIRE-1689
in repository https://gitbox.apache.org/repos/asf/maven-surefire.git.
discard cc7aba1 all mvn builds are successful but Jenkins fails
discard fa648e1 removed my logger System.out.println()
discard c9ae0a5 fixed test
discard bcf1019 exit 1 investigated
discard 988d226 fixed checkstyle
discard bd194dc investigating maven-booter on Linux
discard 70c8e1b [SUREFIRE-1689] The fast PpidChecker is switched to the slow
30 seconds PING after the subprocess (/bin/ps -o etime= -p ...) failed with
exit 1
new 1908951 [SUREFIRE-1689] The fast PpidChecker is switched to the slow
30 seconds PING after the subprocess (/bin/ps -o etime= -p ...) failed with
exit 1
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (cc7aba1)
\
N -- N -- N refs/heads/SUREFIRE-1689 (1908951)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
Jenkinsfile | 36 ++++++++++++++++++++++++++++++++----
1 file changed, 32 insertions(+), 4 deletions(-)
