Commit graph

8 commits

Author SHA1 Message Date
Kris Kennaway
0b457b9cf0 * Implement basename and dirname using shell builtins 2008-07-26 14:02:55 +00:00
Kris Kennaway
1ace35e972 Don't use a lockfile, the script will be called with lockf -t0 instead
to avoid problems with stale lockfiles after reboots.
2005-12-11 04:35:04 +00:00
Kris Kennaway
f233e968d9 If the symlink under latest/ exists, then use that to find the most recent
error log for the port, instead of assuming it exists in the current
build.
2004-10-25 04:31:14 +00:00
Kris Kennaway
faec39b50e Back out the attempt to list the error type in the failure summary;
because this file is a chronological history of port builds that have
failed, the files listed may not be present in the current set of
error logs, and we currently have no easy way to find the most recent
failure log to use instead.
2004-07-14 10:41:03 +00:00
Joe Marcus Clarke
5b279805c7 * Refactor processlogs so that new error types can be added easily to a new
processonelog script, that contains all the per-errorlog logic [1]
* Add new error checks, one for detecting CPU problems, and the other for
  checking for broken libgnugetopt support [2]
* Add a new "munmap" error type to check for broken bindists
* Add imake and pthread detection to processonelog [3]
* Add errortype column to the bento "New Build Failures" report [4]

PR:		50258 56859 [1]
		54406 [2]
		57067 [3]
		59272 [4]
Submitted by:	linimon [1] [2] [3] [4]
2004-01-19 22:30:53 +00:00
Kris Kennaway
a36c5cd9ad Condense the table a bit 2003-10-13 06:33:04 +00:00
Kris Kennaway
f1200b6ecc * Generate newfailure file (sorted list by original failure date) from failure
* Enhance HTML output to include both original and latest failure date, and
  number of times the build has failed.
2003-10-13 02:54:56 +00:00
Kris Kennaway
934f3cece0 First cut at a script to process the logfile maintained by 'buildsuccess'
and 'buildfailure' and produce a HTML output listing ports with the date
they became broken.  The output can surely be made more useful (e.g. it
always links to the ${branch}-latest logs, which may not exist when the
build-in-progress has not yet attempted the build of that port).
2003-01-24 05:03:08 +00:00