Mike Kupfer <mike.kupfer at sun.com> writes:
>>>>>> "Rich" == Richard Lowe <richlowe at richlowe.net> writes:
>
> Rich> I moved the check for the Makefile to after the bringover, but
> Rich> obviously, couldn't test TeamWare.
>
> Indeed. ;-)
>
> Rich> However, I can't see how it would break like that, right now. Can
> Rich> I get more details before I go back myself out, again?
>
> The nightly.log is below. This is from a workspace that was synched up
> with onnv-scm through 15c5ff7afb90, with no local changes to
> nightly.sh. I assume the error is happening at line 2227:
>
> 2218 echo "number of concurrent jobs = $DMAKE_MAX_JOBS" |
> 2219 tee -a $build_environ_file >> $LOGFILE
> 2220
> 2221 #
> 2222 # Report the compiler versions.
> 2223 #
> 2224
> 2225 if [[ ! -f $SRC/Makefile ]]; then
> 2226 build_ok=n
> 2227 echo "\nUnable to find \"Makefile\" in $SRC." | \
> 2228 tee -a $build_environ_file >> $LOGFILE
> 2229 exit 1
> 2230 fi
Yes
>>> Is it supposed to work for Mercurial workspaces?
>
> Rich> Yes, and in my testing, it did.
>
> Okay. Just wanted to make sure. I populated my Mercurial workspace by
> hand, so I didn't try testing the initial bringover for Mercurial.
>
> FWIW, I'm willing to limp along for a bit doing the initial bringover by
> hand. So don't feel like you have to do a backout on my account.
>
[snip]
> ==== Build version ====
>
> 264-test-sparc
...
> ==== No bringover to /home/kupfer/ws/264-test-sparc ====
>
^^^^^^^^^^^^
Well, that would be why it's failing... it's not really using nightly
to do the initial bringover when you tell it not to. :)
Given I'm assuming that's not the actual issue, is your problem that
the version information is now only present if bringover succeeds, or...?
-- Rich
