travis is slowly catching up. It is basically building the PRs now which
were submitted yesterday -> ~20h queue time.
meanwhile I began to incrementally migrate jobs to github actions:
https://github.com/apache/netbeans/pull/4105
-mbien
On 12.05.22 09:07, antonio wrote:
Quoting from [1]
https://github.com/apache/netbeans#full-history
On 13.05.22 01:28, Łukasz Bownik wrote:
Where is the mercurial repo?
On Thu, May 12, 2022, 4:26 PM Michael Bien wrote:
but maybe that is exactly the reason why this was added, to
automatically skip timing related tests under high load
Where is the mercurial repo?
On Thu, May 12, 2022, 4:26 PM Michael Bien wrote:
> but maybe that is exactly the reason why this was added, to automatically
> skip timing related tests under high load situations as attempt to make
> tests appear more reliable.
>
> who knows. I wish there would be
but maybe that is exactly the reason why this was added, to
automatically skip timing related tests under high load situations as
attempt to make tests appear more reliable.
who knows. I wish there would be a comment so that less archeology is
required. there might be a commit in the
now -> no
On 13.05.22 01:12, Michael Bien wrote:
i don't think the assumption in that method is correct btw:
https://github.com/apache/netbeans/blob/f117b5568a12b59e085be02076bc2df1be489258/platform/openide.util/test/unit/src/org/openide/util/TaskTest.java#L171
sleep does not make any
i don't think the assumption in that method is correct btw:
https://github.com/apache/netbeans/blob/f117b5568a12b59e085be02076bc2df1be489258/platform/openide.util/test/unit/src/org/openide/util/TaskTest.java#L171
sleep does not make any guarantees that it wakes up right after the
timeout. It
I will create a separate test calling only this method.
On Thu, May 12, 2022, 3:21 PM Michael Bien wrote:
> Hi Lukasz,
>
> I don't know why its there but if i can make a guess:
> early multi core CPUs had often timing desyncs between cores (likely
> between sockets too). This was somewhat of a
Hi Lukasz,
I don't know why its there but if i can make a guess:
early multi core CPUs had often timing desyncs between cores (likely
between sockets too). This was somewhat of a problem for realtime
applications like game engines since the time could appear to run backwards.
once travis is
Hi.
I stated to clean and extend test cases for org.openide.util.Task class.
In the test case I found the canWait1s() method
https://github.com/apache/netbeans/blob/f117b5568a12b59e085be02076bc2df1be489258/platform/openide.util/test/unit/src/org/openide/util/TaskTest.java#L171
which is used in
Can't tell, really. I think I deleted a dependency in a Maven project,
and then it happened.
Will try to take a look at it in the evening.
El jue, 12 may 2022 a las 14:32, Eric Barboni () escribió:
>
> Hi
> What was your actions that lead to this ? I have windows 11 and I don't see
> this
Hi
What was your actions that lead to this ? I have windows 11 and I don't see
this issue.
Some issue on the jenkins build seems to be related to Stamps since a long time
(709 builds).
https://ci-builds.apache.org/job/Netbeans/job/netbeans-windows/lastCompletedBuild/testReport/
But it has to
Hi all,
I'm seeing this [1] in NB14-RC3 on a Windows 10 box. It seems we're
stubborn trying to delete "all-layers.dat".
Is this a known issue? Blocker?
Thanks
Antonio
INFO [org.netbeans.Stamps]: after GC
INFO [org.netbeans.Stamps]: Slept 426 ms
WARNING [org.netbeans.Stamps]: Error saving
Quoting from [1]
"GitHub contacted Heroku and Travis-CI to request that they initiate
their own security investigations, revoke all OAuth user tokens
associated with the affected applications, and begin work to notify
their own users."
So even though the attack was last month, maybe
Hi Brad,
ex-Sun here as well, so emotional attachment too :-).
I think we should keep SPARC support for at least one (or more) Apache
NetBeans releases. SPARC users deserve it. And who knows, we may have at
least one user ;-).
Last March Oracle announced Solaris 11 CBE [1], free for use for
14 matches
Mail list logo
