Re: can you PLEASE _read_ the QAT mails? (was: Re: Question about a failure report)
On Thu, Jul 09, 2009 at 10:25:50PM +0200, Ulrich Spörlein wrote: > I am always confused about what portsmon is doing vs. pointyhat. portsmon tracks all the errorlog data from pointyhat, with the caveat that only the last 2 runs (somewhat erroneously termed "full" and "latest") of each buildenv are tracked. e.g., if package foo failed more than 2 runs ago and has not be re-run since, portsmon will not show a build error for it. It will, however, show you the last package that was uploaded. portsmon's idea of metadata for a port is based on a single buildenv -- this is a limitation of the database schema ATM. The default buildenv that is used is i386-7 right now*, but I should be switching it to i386-8 pretty soon. This means there is no way to ask it "show me packages that fail on amd64-6" or "show me ports that are marked BROKEN on sparc64, for instance. Therefore, all of the periodic emails describe the state of a port only on i386-7. Finally, since portsmon is looking at errorlogs that have already been produced, it to some degree is reporting the state of past ports tree(s). However, its metadata is updated every hour. mcl * careful observers will note that the environment in which the metadata are evaluated may not _exactly_ match pointyhat's setup, but it's as close as I can get it. The last time I checked, this affected only a handful of ports; in particular, a few false positives for IGNORE based on conflicts. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: can you PLEASE _read_ the QAT mails? (was: Re: Question about a failure report)
On Thu, 9 Jul 2009 22:25:50 +0200 Ulrich Spörlein wrote: > On Mon, 06.07.2009 at 00:51:48 +0300, Ion-Mihai Tetcu wrote: > > On Sun, 05 Jul 2009 13:49:49 -0500 > > Paul Schmehl wrote: > > > > > > For short, your port's configure script fails to search for > > > > mysql headers in the right place; QATty has LOCALBASE and > > > > PREFIX set to /usr/PPP. If you can't sorted out in a few days > > > > drop me an email and I'll take a look. > > > > > > No offense taken. The thing that confused me is that I always > > > build my ports in /tmp/portname when testing, but barnyard still > > > managed to find mysql headers when building. > > > > Yes, that's PREFIX (ie. you install in /tmp/portname) but LOCALBASE > > I bet it's /usr/local. > > > > > So I didn't understand why it was failing in QAT. I followed all > > > the links in the email and read the materials, but I still didn't > > > understand why the build failed in QAT. > > > > It failed on QATty, not on QAT. > > > > QAT has -DNOPORT* while > > QATty has PREFIX and LOCALBASE = /usr/PPP > > Hi Ion-Mihai, > > this is the first time, I hear there are different QAT setups > (although it makes sense, doesn't it?). Well, QATty is almost at the end (it builds x11/ now) of its first run (LOCALBASE/PREFIX) conformance :-) The run was announced on committers ML and on ports ML. > So I was wondering where this is documented. I am always confused > about what portsmon is doing vs. pointyhat. PortsmMon aggregates the date from PointyHat and a few others sources, it's usually easier to use that PointyHat directly. > Then we have tinderbox for src and other ones for ports. Now there > are multiple QAT setups! And we're gonna have more! :-) QAT basically does on-commit testing (I regard -DNOPORT* as something accessory at the moment since the biggest part of the problems were fixed). QATty does non-standard config testing; PREFIX and LOCALBASE for now, other things in the future. The plan is to unite reports for on-commit testing, for standard config and multiple non-standard configs and have one QATMail for all the tests. This depends on available hardware and my available time. > Searching for 'qat' on wiki.freebsd.org revealed no hits, although I > think that would be a good place to document all "official" > port/package "linters" Blame it on me rather hating wikies. Each QATMail contains a link to a doc describing the testing process. > So I would kindly ask you, if you could put some information and links > regarding QAT on the wiki. Other people will probably fill in the > details for pointyhat, portsmon, etc. I'll do it eventually. And yes, you are right, we need to document a lot of things. -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: can you PLEASE _read_ the QAT mails? (was: Re: Question about a failure report)
On Mon, 06.07.2009 at 00:51:48 +0300, Ion-Mihai Tetcu wrote: > On Sun, 05 Jul 2009 13:49:49 -0500 > Paul Schmehl wrote: > > > > For short, your port's configure script fails to search for mysql > > > headers in the right place; QATty has LOCALBASE and PREFIX set > > > to /usr/PPP. If you can't sorted out in a few days drop me an email > > > and I'll take a look. > > > > No offense taken. The thing that confused me is that I always build > > my ports in /tmp/portname when testing, but barnyard still managed to > > find mysql headers when building. > > Yes, that's PREFIX (ie. you install in /tmp/portname) but LOCALBASE I > bet it's /usr/local. > > > So I didn't understand why it was failing in QAT. I followed all the > > links in the email and read the materials, but I still didn't > > understand why the build failed in QAT. > > It failed on QATty, not on QAT. > > QAT has -DNOPORT* while > QATty has PREFIX and LOCALBASE = /usr/PPP Hi Ion-Mihai, this is the first time, I hear there are different QAT setups (although it makes sense, doesn't it?). So I was wondering where this is documented. I am always confused about what portsmon is doing vs. pointyhat. Then we have tinderbox for src and other ones for ports. Now there are multiple QAT setups! Searching for 'qat' on wiki.freebsd.org revealed no hits, although I think that would be a good place to document all "official" port/package "linters" So I would kindly ask you, if you could put some information and links regarding QAT on the wiki. Other people will probably fill in the details for pointyhat, portsmon, etc. That would be great, thanks! Cheers, Ulrich Spörlein -- http://www.dubistterrorist.de/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: can you PLEASE _read_ the QAT mails? (was: Re: Question about a failure report)
On Sun, 05 Jul 2009 13:49:49 -0500 Paul Schmehl wrote: > > For short, your port's configure script fails to search for mysql > > headers in the right place; QATty has LOCALBASE and PREFIX set > > to /usr/PPP. If you can't sorted out in a few days drop me an email > > and I'll take a look. > > No offense taken. The thing that confused me is that I always build > my ports in /tmp/portname when testing, but barnyard still managed to > find mysql headers when building. Yes, that's PREFIX (ie. you install in /tmp/portname) but LOCALBASE I bet it's /usr/local. > So I didn't understand why it was failing in QAT. I followed all the > links in the email and read the materials, but I still didn't > understand why the build failed in QAT. It failed on QATty, not on QAT. QAT has -DNOPORT* while QATty has PREFIX and LOCALBASE = /usr/PPP > I didn't want to make a change to the port unless the problem really > was with the port. That's why I asked the question. It is :) Sahil's patch looks good, I'm going to test it tomorrow. -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: can you PLEASE _read_ the QAT mails? (was: Re: Question about a failure report)
--On July 5, 2009 11:15:32 AM +0300 Ion-Mihai Tetcu wrote: Paul, I'm not picking on you, it's just that it's the 4th mail I get in the last days showing the same thing. Sigh, at lest this one was a question, not trying to convince me QATty setup is wrong because we don't support non-default configs. For short, your port's configure script fails to search for mysql headers in the right place; QATty has LOCALBASE and PREFIX set to /usr/PPP. If you can't sorted out in a few days drop me an email and I'll take a look. No offense taken. The thing that confused me is that I always build my ports in /tmp/portname when testing, but barnyard still managed to find mysql headers when building. So I didn't understand why it was failing in QAT. I followed all the links in the email and read the materials, but I still didn't understand why the build failed in QAT. I didn't want to make a change to the port unless the problem really was with the port. That's why I asked the question. Paul Schmehl, If it isn't already obvious, my opinions are my own and not those of my employer. ** WARNING: Check the headers before replying ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
