regards.
[1] https://github.com/actions/setup-java#basic
On Wed, Jul 1, 2020 at 5:44 PM Gary Gregory wrote:
>
> In Travis-CI, you can say "java-ea", what is the equivalent in GitHub?
>
> Gary
>
> On Wed, Jul 1, 2020 at 9:33 AM Matt Sicker wrote:
>
> > I’ll take
In Travis-CI, you can say "java-ea", what is the equivalent in GitHub?
Gary
On Wed, Jul 1, 2020 at 9:33 AM Matt Sicker wrote:
> I’ll take a look this week sometime. I’m in support of everything said
> here, too. This should help the PR testing feature actually work again!
&
o objections, I really would like to get this merged. Once this
> lifts off, I am inclined to drop the Travis CI. Would anybody mind
> reviewing the PR, please? (Note that the change set updates the Maven
> Wrapper scripts too.)
>
> Cheers!
>
> [1] https://github.com/apache/l
Hello,
I have pulled this off in my local repo and created a PR[1]. If there
are no objections, I really would like to get this merged. Once this
lifts off, I am inclined to drop the Travis CI. Would anybody mind
reviewing the PR, please? (Note that the change set updates the Maven
Wrapper
Given everybody is willing to give it a go, I've created LOG4J2-2764[1].
[1] https://issues.apache.org/jira/browse/LOG4J2-2764
On Mon, Jan 20, 2020 at 9:40 PM Volkan Yazıcı wrote:
>
> Given GitHub has introduced its own CI, i.e., GitHub Actions, would
> you consider migrating fro
running CI
>> on master and 2.x).
>>
>> On Mon, 20 Jan 2020 at 14:39, Volkan Yazıcı
>> wrote:
>>>
>>> Given GitHub has introduced its own CI, i.e., GitHub Actions, would
>>> you consider migrating from Travis CI to that? In its current form,
>
nkins instance (which is already running CI
> on master and 2.x).
>
> On Mon, 20 Jan 2020 at 14:39, Volkan Yazıcı
> wrote:
> >
> > Given GitHub has introduced its own CI, i.e., GitHub Actions, would
> > you consider migrating from Travis CI to that? In its current form
GitHub has introduced its own CI, i.e., GitHub Actions, would
> you consider migrating from Travis CI to that? In its current form,
> setup-java[1] doesn't support multiple JDKs, but I think it can be
> worked around. If the rest of the people would agree, I will create a
> ticket f
Given GitHub has introduced its own CI, i.e., GitHub Actions, would
you consider migrating from Travis CI to that? In its current form,
setup-java[1] doesn't support multiple JDKs, but I think it can be
worked around. If the rest of the people would agree, I will create a
ticket for that and
instead test Java 11.
> >
> > Gary
> >
> > -- Forwarded message -
> > From:
> > Date: Fri, Dec 7, 2018 at 8:53 AM
> > Subject: [4/4] httpcomponents-core git commit: Added openjdk10 to
> Travis-CI
> > build matrix
> > To:
> &g
ec 7, 2018 at 8:53 AM
> Subject: [4/4] httpcomponents-core git commit: Added openjdk10 to Travis-CI
> build matrix
> To:
>
>
> Added openjdk10 to Travis-CI build matrix
>
>
> Project: http://git-wip-us.apache.org/repos/asf/httpcomponents-core/repo
> Commit:
> http
I think we can skip Java 9 and 10 and instead test Java 11.
Gary
-- Forwarded message -
From:
Date: Fri, Dec 7, 2018 at 8:53 AM
Subject: [4/4] httpcomponents-core git commit: Added openjdk10 to Travis-CI
build matrix
To:
Added openjdk10 to Travis-CI build matrix
Project
See
https://travis-ci.org/apache/logging-log4j2/builds/54266?utm_source=github_status&utm_medium=notification
Gary
s it differently from Jenkins? Isn't both Jenkins and Travis CI
just running the Maven build? Or does Travis CI tries to be "smart" and
actually do something stupid?
> Fix travis-ci build
> ---
>
> Key: LOG4J2-1901
> U
will not work.
But why is it differently from Jenkins? Isn't both Jenkins and Travis CI
just running the Maven build? Or does Travis CI tries to be "smart" and
actually do something stupid?
---
If your project is set up for it, you can reply to this email and have your
ssue:
https://github.com/apache/logging-log4j2/pull/79
Not finding the `Logger$` class sounds like the Scala code isn't being
compiled properly. That's the companion object class name.
> Fix travis-ci build
> ---
>
> Key: LOG4J2-
Github user jvz commented on the issue:
https://github.com/apache/logging-log4j2/pull/79
Not finding the `Logger$` class sounds like the Scala code isn't being
compiled properly. That's the companion object class name.
---
If your project is set up for it, you can reply to this email
Jenkins somehow.
On 26 May 2017 at 06:27, Mikael Ståldal wrote:
Link to Travis CI build:
https://travis-ci.org/apache/logging-log4j2/builds/236303848
?utm_source=github_status&utm_medium=notification
On 2017-05-26 13:20, Mikael Ståldal wrote:
Now the Travis CI build almost works, but fails
Travis is set up for testing pull requests and potentially other free
GitHub-integrated services like coveralls, though if we looked into it, I
bet we could do all those things strictly with Jenkins somehow.
On 26 May 2017 at 06:27, Mikael Ståldal wrote:
> Link to Travis CI build:
>
&
Link to Travis CI build:
https://travis-ci.org/apache/logging-log4j2/builds/236303848?utm_source=github_status&utm_medium=notification
On 2017-05-26 13:20, Mikael Ståldal wrote:
Now the Travis CI build almost works, but fails with:
-
The log length has exceeded the limit of 4 MB (
Github user mikaelstaldal closed the pull request at:
https://github.com/apache/logging-log4j2/pull/80
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the f
Now the Travis CI build almost works, but fails with:
-
The log length has exceeded the limit of 4 MB (this usually means that
the test suite is raising the same exception over and over).
The job has been terminated
-
After 49 minutes.
Why do we even use Travis CI when we have
GitHub user mikaelstaldal opened a pull request:
https://github.com/apache/logging-log4j2/pull/80
Testing Travis CI
This is only a test for Travis CI.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/logging-log4j2 travis
pull request at:
https://github.com/apache/logging-log4j2/pull/79
> Fix travis-ci build
> ---
>
> Key: LOG4J2-1901
> URL: https://issues.apache.org/jira/browse/LOG4J2-1901
> Project: Log4j 2
> Issue Type:
1901:
-
Commit 64170ccc1059377f039441808d2b54e71ea423a8 in logging-log4j2's branch
refs/heads/master from [~pascalschumacher]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=64170cc ]
LOG4J2-1901: Fix travis-ci build
remove apt-get, use trusty dist
skip SecureSocketAppenderSocketOp
Github user asfgit closed the pull request at:
https://github.com/apache/logging-log4j2/pull/79
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
d on the issue:
https://github.com/apache/logging-log4j2/pull/79
That's strange. However, the Scala modules will soon be remove from this
repository (as they live in the logging-log4j-scala repo). So maybe we should
not spend time on fixing that problem in this repo.
> Fix tra
Github user mikaelstaldal commented on the issue:
https://github.com/apache/logging-log4j2/pull/79
That's strange. However, the Scala modules will soon be remove from this
repository (as they live in the logging-log4j-scala repo). So maybe we should
not spend time on fixing that probl
nted on the issue:
https://github.com/apache/logging-log4j2/pull/79
Added assumes to skip these tests on travis-ci.
Now a test of og4j-api-scala_2.11 fails:
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
1.228 s <<<
Github user PascalSchumacher commented on the issue:
https://github.com/apache/logging-log4j2/pull/79
Added assumes to skip these tests on travis-ci.
Now a test of og4j-api-scala_2.11 fails:
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed
nted on the issue:
https://github.com/apache/logging-log4j2/pull/79
Yes. The problem is that these tests also fail on java 7 when run on travis.
> Fix travis-ci build
> ---
>
> Key: LOG4J2-1901
> URL: https://issues.apa
Github user PascalSchumacher commented on the issue:
https://github.com/apache/logging-log4j2/pull/79
Yes. The problem is that these tests also fail on java 7 when run on travis.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
d on the issue:
https://github.com/apache/logging-log4j2/pull/79
Now it fails with the socket option test that has been fixed. Have you
synced with upstream?
> Fix travis-ci build
> ---
>
> Key: LOG4J2-1901
> URL: https:
Github user mikaelstaldal commented on the issue:
https://github.com/apache/logging-log4j2/pull/79
Now it fails with the socket option test that has been fixed. Have you
synced with upstream?
---
If your project is set up for it, you can reply to this email and have your
reply appear
ed a pull request:
https://github.com/apache/logging-log4j2/pull/79
LOG4J2-1901: Fix travis-ci build
remove apt-get, use trusty dist
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/PascalSchumacher/logging-lo
GitHub user PascalSchumacher opened a pull request:
https://github.com/apache/logging-log4j2/pull/79
LOG4J2-1901: Fix travis-ci build
remove apt-get, use trusty dist
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
Now Travis CI fails since it cannot find
JDK 9.
> Fix travis-ci build
> ---
>
> Key: LOG4J2-1901
> URL: https://issues.apache.org/jira/browse/LOG4J2-1901
> Project: Log4j 2
> Issue Type: Bug
>
d on the issue:
https://github.com/apache/logging-log4j2/pull/77
This has been fixed in master branch already.
> Fix travis-ci build
> ---
>
> Key: LOG4J2-1901
> URL: https://issues.apache.org/jira/browse/LOG4J2-1901
&g
Github user mikaelstaldal commented on the issue:
https://github.com/apache/logging-log4j2/pull/77
This has been fixed in master branch already.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not hav
d on the issue:
https://github.com/apache/logging-log4j2/pull/77
Wouldn't this best be fixed with a JUnit assume?
> Fix travis-ci build
> ---
>
> Key: LOG4J2-1901
> URL: https://issues.apache.org/jira/browse/LOG4J2-19
Github user garydgregory commented on the issue:
https://github.com/apache/logging-log4j2/pull/77
Wouldn't this best be fixed with a JUnit assume?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not h
the pull request at:
https://github.com/apache/logging-log4j2/pull/77
> Fix travis-ci build
> ---
>
> Key: LOG4J2-1901
> URL: https://issues.apache.org/jira/browse/LOG4J2-1901
> Project: Log4j 2
>
Github user PascalSchumacher closed the pull request at:
https://github.com/apache/logging-log4j2/pull/77
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if th
[
https://issues.apache.org/jira/browse/LOG4J2-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pascal Schumacher updated LOG4J2-1901:
--
Description:
The travis-ci build has been failing for weeks e.g.
https://travis
[
https://issues.apache.org/jira/browse/LOG4J2-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pascal Schumacher updated LOG4J2-1901:
--
Description:
The travis-ci build has been failing for weeks e.g.
https://travis
ed a pull request:
https://github.com/apache/logging-log4j2/pull/77
LOG4J2-1901 - Fix travis-ci build
temporary comment out failing asserts to see if build passes
Just a test, not ready to merge!
You can merge this pull request into a Git repository by running:
$ git
GitHub user PascalSchumacher opened a pull request:
https://github.com/apache/logging-log4j2/pull/77
LOG4J2-1901 - Fix travis-ci build
temporary comment out failing asserts to see if build passes
Just a test, not ready to merge!
You can merge this pull request into a Git
pull request at:
https://github.com/apache/logging-log4j2/pull/76
> Fix travis-ci build
> ---
>
> Key: LOG4J2-1901
> URL: https://issues.apache.org/jira/browse/LOG4J2-1901
> Project: Log4j 2
> Issue Type:
gt; Fix travis-ci build
> ---
>
> Key: LOG4J2-1901
> URL: https://issues.apache.org/jira/browse/LOG4J2-1901
> Project: Log4j 2
> Issue Type: Bug
>Reporter: Pascal Schumacher
>
> The travis-c
Github user asfgit closed the pull request at:
https://github.com/apache/logging-log4j2/pull/76
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Pascal Schumacher created LOG4J2-1901:
-
Summary: Fix travis-ci build
Key: LOG4J2-1901
URL: https://issues.apache.org/jira/browse/LOG4J2-1901
Project: Log4j 2
Issue Type: Bug
51 matches
Mail list logo
