the notification off and work
on fix.
Li-Wen
--
Li-Wen Hsu lw...@freebsd.org
http://lwhsu.org
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr
files under sys/conf ?
I tried to switch to this and it seems work, but I am not sure if this
is your original intention. I'll change the modules building job to
checkout the whole src tree if this is not an accepted solution.
Thanks,
Li-Wen
--
Li-Wen Hsu lw...@freebsd.org
http://lwhsu.org
modules can be built on 10. Do we suppose to support this?
By the way, jenkins just (stupidly) mails every committer who changes
code in a failed build. It cannot tell which commit is the root cause.
Li-Wen
--
Li-Wen Hsu lw...@freebsd.org
http://lwhsu.org
On Sat, Jun 28, 2014 at 13:36:19 -0700, Rui Paulo wrote:
On Jun 28, 2014, at 13:31, Li-Wen Hsu lw...@freebsd.org wrote:
On Sat, Jun 28, 2014 at 20:55:19 +0200, Hans Petter Selasky wrote:
Hi,
Jenkins is by error reporting my changes as cause of fault!
/builds/FreeBSD_HEAD-modules
Makefile
I wiped out the workspace, it will do a fresh checkout on next build.
Let's see if this helps.
Li-Wen
--
Li-Wen Hsu lw...@freebsd.org
http://lwhsu.org
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
://people.freebsd.org/~lwhsu/tmp/test.img.xz
Here are config and test script:
https://github.com/freebsd/freebsd-ci/blob/master/scripts/test/config/config.json
https://github.com/freebsd/freebsd-ci/blob/master/scripts/test/run-tests.py
Hope these help.
Li-Wen
--
Li-Wen Hsu lw...@freebsd.org
http://lwhsu.org
. Sorry for the noise.
Li-Wen
--
Li-Wen Hsu lw...@freebsd.org
http://lwhsu.org
pgptDGxdpMtud.pgp
Description: PGP signature
, it does not find
devel/amd64-xtoolchain-gcc either. While 11-CURRENT works. Is this a
package building issue? Is there anyone get different result?
Thanks,
Li-Wen
--
Li-Wen Hsu
http://lwhsu.org
___
freebsd-current@freebsd.org mailing list
http
On Mon, Jul 27, 2015 at 1:40 PM, Li-Wen Hsu lw...@freebsd.org wrote:
On Mon, Jul 27, 2015 at 10:55 AM, jenkins-ad...@freebsd.org wrote:
FreeBSD_HEAD_amd64_gcc4.9 - Build #247 - Failure:
Build information:
https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/247/
Full change log
On Mon, Jul 27, 2015 at 08:23:47 +0200, Baptiste Daroussin wrote:
On Mon, Jul 27, 2015 at 02:07:31PM +0800, Li-Wen Hsu wrote:
On Mon, Jul 27, 2015 at 1:40 PM, Li-Wen Hsu lw...@freebsd.org wrote:
On Mon, Jul 27, 2015 at 10:55 AM, jenkins-ad...@freebsd.org wrote:
FreeBSD_HEAD_amd64_gcc4.9
On Mon, Jul 27, 2015 at 08:31:18 +0200, Baptiste Daroussin wrote:
On Mon, Jul 27, 2015 at 02:28:16PM +0800, Li-Wen Hsu wrote:
On Mon, Jul 27, 2015 at 08:23:47 +0200, Baptiste Daroussin wrote:
On Mon, Jul 27, 2015 at 02:07:31PM +0800, Li-Wen Hsu wrote:
On Mon, Jul 27, 2015 at 1:40 PM, Li
we need to support build -CURRENT on latest -RELEASE, right?
Any comments?
Thanks,
Li-Wen
--
Li-Wen Hsu lw...@freebsd.org
http://lwhsu.org
pgpmXMIv1u06q.pgp
Description: PGP signature
Resend this using another subject for not being overwhelmed by lots of build
fail mails :(
On Sun, Jul 12, 2015 at 01:22:48 +0800, Li-Wen Hsu wrote:
On Sat, Jul 11, 2015 at 17:11:24 +, jenkins-ad...@freebsd.org wrote:
FreeBSD_HEAD - Build #2953 - Still Failing:
Build information
v/kyua/issues/136
https://github.com/jmmv/kyua/pull/148
Escape these characters is a way, or we might make our test cases always
produce printable characters in outputs, however that might be
impossible (who knows when test fails would happen?). Or, don't know if
there is a method to embedded these bytes into a valid XML.
Li-Wen
--
Li-Wen Hsu <lw...@freebsd.org>
http://lwhsu.org
pgpqIWs0vVLM0.pgp
Description: PGP signature
s are up-to-date.
> > Build step 'Execute shell' marked build as failure
>
> pkg install -y is returning an error now here where it didn't before.
Yeah, Baptiste is working on a fix and I think it will be completed
soon.
I'll disable this step in the build process temporarily until pk
: Add vital field
> FreeBSD repository is up-to-date.
> All repositories are up-to-date.
> Build step 'Execute shell' marked build as failure
>
> I'd consider this a bug in pkg? Is it suppose to return a failure code in
> this case?
I've checked this a little more, I found the r
On Mon, Apr 04, 2016 at 00:50:14 +0200, Baptiste Daroussin wrote:
> On Mon, Apr 04, 2016 at 04:41:47AM +0800, Li-Wen Hsu wrote:
> > I've checked this a little more, I found the return code of
> > "installing a installed package" has been changed.
> >
> > For
On Mon, Apr 04, 2016 at 12:53:16 +0200, Baptiste Daroussin wrote:
> On Mon, Apr 04, 2016 at 06:39:00PM +0800, Li-Wen Hsu wrote:
> > On Mon, Apr 04, 2016 at 00:50:14 +0200, Baptiste Daroussin wrote:
> > > On Mon, Apr 04, 2016 at 04:41:47AM +0800, Li-Wen Hsu wrote:
> > > &
On Mon, Apr 04, 2016 at 14:32:35 +0200, Baptiste Daroussin wrote:
> On Mon, Apr 04, 2016 at 08:25:39PM +0800, Li-Wen Hsu wrote:
> > On Mon, Apr 04, 2016 at 12:53:16 +0200, Baptiste Daroussin wrote:
> > > On Mon, Apr 04, 2016 at 06:39:00PM +0800, Li-Wen Hsu wrote:
> > > &
pt:
https://github.com/freebsd/freebsd-ci/blob/master/scripts/build/cross-build.sh
with TARGET_ARCH=TARGET_ARCH
And MAKE_CONF_FILE as:
NO_WERROR=yes
WERROR=
WITH_FAST_DEPEND=yes
Li-Wen
--
Li-Wen Hsu <lw...@freebsd.org>
https://lwhsu.org
signature.asc
Description: PGP signature
st recent version of packages are already installed
The build script install/update the latest devel/amd64-xtoolchain-gcc
package. I think the problem is we did not upgrade the dependencies. I
cannot think of a elegant way to upgrade all amd64-xtoolchain-gcc's
dependencies, so I added a line to build script to upgrade everything
before build.
Let see if this works.
Best,
Li-Wen
--
Li-Wen Hsu <lw...@freebsd.org>
https://lwhsu.org
signature.asc
Description: PGP signature
On Sat, Dec 17, 2016 at 18:29:09 +0100, Dimitry Andric wrote:
> On 15 Dec 2016, at 18:56, Li-Wen Hsu <lw...@freebsd.org> wrote:
> >
> > On Thu, Dec 15, 2016 at 12:42:00 +0100, Dimitry Andric wrote:
> >> On 15 Dec 2016, at 12:03, jenkins-ad...@freebsd.org wrote:
>
ll_subdir_bin/df ---
> > > ===> bin/df (all)
> > > --- all_subdir_libexec ---
> > > /usr/local/bin/x86_64-freebsd-ld: atf-check.o: relocation R_X86_64_32
> > > against symbol `_ZTIN3atf12system_errorE' can not be used when making a
> > > shared object; recompile with -fPIC
> > > /usr/local/bin/x86_64-freebsd-ld: final link failed: Nonrepresentable
> > > section on output
> > > collect2: error: ld returned 1 exit status
> > > *** [atf-check.full] Error code 1
> >
> > Baptiste, is this the problem again with -lstdc++ being linked in
> > accidentally again?
>
> Should not be, is the object directory always cleaned before building? by
> cleaned I mean rm -rf
Seems not, I just added rm -fr ${MAKEOBJDIRPREFIX} to build script.
Best,
Li-Wen
--
Li-Wen Hsu <lw...@freebsd.org>
https://lwhsu.org
signature.asc
Description: PGP signature
t; >>>
> >>> make[5]: stopped in /usr/src/kerberos5/lib/libkafs5
> >>> --- libkafs5.a ---
> >>> *** [libkafs5.a] Error code 70
> >>>
> >>> and:
> >>>
> >>>
> >>> --- lib__L ---
> >>> ranlib -D libc
t; *** [libclang_rt.asan_cxx-i386.a] Error code 70
> >>
> >>
> >> (Notice the variability in what .a the ranlib's fail for.)
> >>
> >>
> >>
> >>
> >>
> >
> >
> >
gt; brk_test.o:(atfu_brk_basic_body)
> >
> > . . . (and many more) . . .
>
> Do a clean build or remove the libc directory from /usr/obj, then do
> your build.
Each build on ci.freebsd.org is a clean build from scratch.
Li-Wen
> --
Li-Wen Hsu
https://lwhsu.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
.freebsd.org is running r331373 now.
--
Li-Wen Hsu
https://lwhsu.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On Tue, Jun 19, 2018 at 9:24 PM Mark Millard wrote:
>
> On 2018-Jun-19, at 8:02 AM, Li-Wen Hsu wrote:
>
> > On Mon, Jun 18, 2018 at 8:36 PM Ed Maste wrote:
> >> Li-Wen reported that the build is done in a 11.1-rel jail though, so
> >> the libarchive (
le here:
https://artifact.ci.freebsd.org/snapshot/head/r336751/amd64/amd64/
You can use disk-test.img.xz which is a VM with setup testing
environment. The build script will start automatically but you can
ctrl-c to interrupt anytime and run tests by hand:
cd /usr/tests/usr.s
377/
Thanks for your help!
Li-Wen
--
Li-Wen Hsu
https://lwhsu.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> Stopped at inp_gcmoptions+0xe3:movqll+0x33f(%rax),%r9
I think this is because we are trying to enable more tests:
https://github.com/freebsd/freebsd-ci/pull/25
I'm looking into that. If I cannot resolve this quickly I will revert
it temporarily.
Li-Wen
--
Li-Wen Hsu
https://lwhsu.org
__
e as TARGET_ARCH here because it takes a shorter time
in one iteration. There should be nothing related to the
architectures.
I am not very sure about what is the next step, maybe modifying ranlib
and log more what it gets "fatal: Failed to open 'libxxx.a'" Any good
idea about debugging
:59 PM, Matthew Macy wrote:
>>
>> That looks like it is tied to changes I made 3 months ago. I won't be at my
>> desk until the end of the week, but if it's consistent I can take a look.
>>
>> -M
>>
>> On Sun, Aug 5, 2018 at 17:57 Li-Wen H
1 of
'__atomic_fetch_sub'
if (atomic_fetch_sub(>cnt, 1) > 1)
^~
*** [acm.o] Error code 1
make[6]: stopped in /usr/home/lwhsu/freebsd-src/lib/ofed/librdmacm
BTW, stable/11 should be fine to cross-build riscv64, this job uses
11.2-RELEASE an
On Sun, Jul 22, 2018 at 18:45:05 +0300, Konstantin Belousov wrote:
> On Sun, Jul 22, 2018 at 01:01:16AM +0000, Li-Wen Hsu wrote:
> > On Sun, Jul 22, 2018 at 02:18:32 +0300, Konstantin Belousov wrote:
> > > On Sat, Jul 21, 2018 at 02:16:17AM +, jenkins-ad...@freebsd.org wrot
On Sun, Jul 22, 2018 at 10:27 PM Konstantin Belousov
wrote:
>
> On Sun, Jul 22, 2018 at 06:16:02PM +0100, Li-Wen Hsu wrote:
> > On Sun, Jul 22, 2018 at 18:45:05 +0300, Konstantin Belousov wrote:
> > > On Sun, Jul 22, 2018 at 01:01:16AM +, Li-Wen Hsu wrote:
> >
rhaps use __riscv since this
> apparently is what Ruslan wants to use.
I committed the original patch as r336620.
--
Li-Wen Hsu
https://lwhsu.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To
ame=head-amd64-default=p474051_s336054
Li-Wen
--
Li-Wen Hsu
https://lwhsu.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
ll others in the process. Everything that I found
> from arthur.nyi.freebsd.org was yellow-status.
>
This is because of the ABI incompatible between different versions of
-CURRENT, on pkg build cluster and the arthur.nyi. It has been fixed.
Thanks,
Li-Wen
--
Li-Wen Hsu
https://lwhsu.org
> ^~~~
> > 1 error generated.
> > *** [ia32_genassym.o] Error code 1
> >
> > Later builds ( -r335880 , -r335881 , -r335882 ) get the same.
> >
> > FreeBSD-head-i386-LINT also fails for such reasons.
> >
>
> r335884 should fix this.
It seem
Ok, this one looks interesting.
On Thu, Nov 8, 2018 at 10:39 PM wrote:
>
> FreeBSD-head-armv7-build - Build #2129 (r340262) - Failure
>
> Build information: https://ci.freebsd.org/job/FreeBSD-head-armv7-build/2129/
> Full change log:
>
://ci.freebsd.org/job/FreeBSD-head-scan_build/lastCompletedBuild/clangScanBuildBugs/
--
Li-Wen Hsu
https://lwhsu.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "fr
On Thu, Dec 13, 2018 at 3:25 AM Mark Millard via freebsd-toolchain
wrote:
> Looks like this might have been from a race condition or some such.
> Rerunning the meta-mode build again had no such problem and completed.
It is also happening in clean build, I've filed a PR about this:
(bcc -current and -stable for more audience)
FreeBSD CI Weekly Report 2019-03-24
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-03-18 to 2019-03-24.
During this period, we have:
* 2286 builds (98.3% passed, 1.7%
(bcc -current and -stable for more audience)
FreeBSD CI Weekly Report 2019-03-31
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-03-25 to 2019-03-31.
During this period, we have:
* 2095 builds (98.7% passed, 1.3%
(bcc -current and -stable for more audience)
FreeBSD CI Weekly Report 2019-03-03
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-02-25 to 2019-03-03.
During this period, we have:
* 2299 builds (98% passed, 2% failed)
(bcc -current and -stable for more audience)
FreeBSD CI Weekly Report 2019-02-24
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-02-18 to 2019-02-24.
During this period, we have:
* 2214 builds (98.7% passed, 1.3%
(bcc -current and -stable for more audience)
FreeBSD CI Weekly Report 2019-02-17
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-02-11 to 2019-02-17.
During this period, we have:
* 2348 builds (93.4% passed, 6.6%
(bcc -current and -stable for more audience)
FreeBSD CI Weekly Report 2019-03-17
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-03-11 to 2019-03-17.
During this period, we have:
* 1918 builds (93.2% passed, 2.3%
(bcc -current and -stable for more audience)
FreeBSD CI Weekly Report 2019-03-10
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-02-03 to 2019-03-10.
During this period, we have:
* 1890 builds (95.6% passed, 4.4%
(bcc -current and -stable for more audience)
FreeBSD CI Weekly Report 2019-02-10
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-02-04 to 2019-02-10.
During this period, we have:
* 2564 builds (97.4% passed, 2.6%
(bcc -current and -stable for more audience)
FreeBSD CI Weekly Report 2019-02-03
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-01-28 to 2019-02-03.
During this period, we have:
* 2220 builds (93.7% passed, 6.2%
(bcc -current and -stable for more audience)
FreeBSD CI Weekly Report 2019-01-27
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-01-21 to 2019-01-27.
During this period, we have:
* 2429 builds (91.2% pass, 7.3%
(bcc -current and -stable for more audience)
FreeBSD CI Weekly Report 2019-04-14
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-04-08 to 2019-04-14.
During this period, we have:
* 1702 builds (95.7% passed, 4.3%
(Please send the followup discussions to freebsd-testing@ list.)
FreeBSD CI Weekly Report 2019-05-26
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-05-20 to 2019-05-26.
During this period, we have:
* 2273 builds (97%
(Please send the followup discussions to freebsd-testing@ list.)
FreeBSD CI Weekly Report 2019-06-02
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-05-27 to 2019-06-02.
During this period, we have:
* 1752 builds
(Please send the followup discussions to freebsd-testing@ list.)
FreeBSD CI Weekly Report 2019-06-09
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-06-03 to 2019-06-09.
During this period, we have:
* 2444 builds
(Please send the followup discussions to freebsd-testing@ list.)
FreeBSD CI Weekly Report 2019-06-16
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-06-10 to 2019-06-16.
During this period, we have:
* 1927 builds
(bcc -current and -stable for more audience)
FreeBSD CI Weekly Report 2019-05-05
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-04-29 to 2019-05-05.
During this period, we have:
* 2372 builds (99.9% passed, 0.1%
(bcc -current and -stable for more audience)
FreeBSD CI Weekly Report 2019-05-19
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-05-13 to 2019-05-19.
During this period, we have:
* 1845 builds (97% passed, 3% failed)
(bcc -current and -stable for more audience)
FreeBSD CI Weekly Report 2019-05-12
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-05-06 to 2019-05-12.
During this period, we have:
* 2151 builds (98.2% passed, 1.8%
(bcc -current and -stable for more audience)
FreeBSD CI Weekly Report 2019-04-28
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-04-22 to 2019-04-28.
During this period, we have:
* 2358 builds (96.9% passed, 3.1%
(Please send the followup discussions to freebsd-testing@ list.)
FreeBSD CI Weekly Report 2019-06-23
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-06-17 to 2019-06-23.
During this period, we have:
* 1835 builds
(Please send the followup discussions to freebsd-testing@ list.)
FreeBSD CI Weekly Report 2019-07-07
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-07-01 to 2019-07-07.
During this period, we have:
* 1871 builds
(Please send the followup discussions to freebsd-testing@ list.)
FreeBSD CI Weekly Report 2019-06-30
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-06-24 to 2019-06-30.
During this period, we have:
* 1764 builds
(bcc -current and -stable for more audience)
FreeBSD CI Weekly Report 2019-04-21
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-04-15 to 2019-04-21.
During this period, we have:
* 2346 builds (95.5% passed, 4.5%
(bcc -current and -stable for more audience)
FreeBSD CI Weekly Report 2019-04-07
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-04-01 to 2019-04-07.
During this period, we have:
* 1841 builds (96% passed, 4% failed)
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-07-28
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-07-22 to 2019-07-28.
During this period, we have:
* 1689
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-08-11
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-08-05 to 2019-08-11.
During this period, we have:
* 2066
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-08-18
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-08-12 to 2019-08-18.
During this period, we have:
* 2205
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-08-25
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-08-19 to 2019-08-25.
During this period, we have:
* 2262
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-09-01
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-08-26 to 2019-09-01.
During this period, we have:
* 1625
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-09-08
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-09-02 to 2019-09-08.
During this period, we have:
* 2122
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-09-15
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-09-09 to 2019-09-15.
During this period, we have:
* 2095
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-08-04
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-07-29 to 2019-08-04.
During this period, we have:
* 1662
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-07-14
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-07-08 to 2019-07-14.
During this period, we have:
* 1628
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-07-21
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-07-15 to 2019-07-21.
During this period, we have:
* 1659
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-10-27
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-10-21 to 2019-10-27.
During this period, we have:
* 2267
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-11-03
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-10-29 to 2019-11-03.
During this period, we have:
* 1820
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-11-10
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-11-04 to 2019-11-10.
During this period, we have:
* 2331
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-12-08
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-12-02 to 2019-12-08.
During this period, we have:
* 2463
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-12-15
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-12-09 to 2019-12-15.
During this period, we have:
* 2566
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-10-13
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-10-07 to 2019-10-13.
During this period, we have:
* 2217
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-10-20
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-10-14 to 2019-10-20.
During this period, we have:
* 2475
On Thu, Nov 21, 2019 at 1:39 AM bob prohaska wrote:
>
> From time to time it would be handy to revert freebsd-current to
> an older, well-behaved revision.
>
> Is there a mechanism for identifying revision numbers that
> will at least compile and boot, by date?
>
> In my case buildworld seems to
On Thu, Nov 21, 2019 at 12:39 AM Michael Butler
wrote:
>
> The no-relax flag can't be used on all architectures ..
>
> Building /usr/obj/usr/src/amd64.amd64/usr.sbin/jail/jail
> --- jail ---
> ld: error: unknown argument '--no-relax'
> cc: error: linker command failed with exit code 1 (use -v to
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-12-01
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-11-25 to 2019-12-01.
During this period, we have:
* 2134
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-11-24
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-11-18 to 2019-11-24.
During this period, we have:
* 2617
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-11-17
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-11-11 to 2019-11-17.
During this period, we have:
* 2174
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-09-22
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-09-16 to 2019-09-22.
During this period, we have:
* 2048
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-09-29
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-09-23 to 2019-09-29.
During this period, we have:
* 2159
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-10-06
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-09-30 to 2019-10-06.
During this period, we have:
* 2129
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2020-02-23
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2020-02-17 to 2020-02-23.
During this period, we have:
* 1969
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2020-02-02
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2020-01-27 to 2020-02-02.
During this period, we have:
* 2188
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2020-01-26
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2020-01-20 to 2020-01-26.
During this period, we have:
* 2153
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2020-02-16
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2020-02-10 to 2020-02-16.
During this period, we have:
* 2180
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2020-02-09
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2020-02-03 to 2020-02-09.
During this period, we have:
* 2010
On Mon, Jan 13, 2020 at 1:10 PM wrote:
>
> FreeBSD-head-amd64-test - Build #13912 (r356671) - Failure
>
> Build information: https://ci.freebsd.org/job/FreeBSD-head-amd64-test/13912/
> Full change log:
> https://ci.freebsd.org/job/FreeBSD-head-amd64-test/13912/changes
> Full build log:
>
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2020-01-05
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2020-12-30 to 2020-01-05.
During this period, we have:
* 2029
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2020-01-12
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2020-01-06 to 2020-01-12.
During this period, we have:
* 2218
1 - 100 of 150 matches
Mail list logo
