Community
Participate
Working Groups
Nick said: There should be a way to redirect standard out and standard err to the same file. Usually, I use 2>&1 | tee somefile.txt but in this case we might need to also add the -consolelog when launching the tests so that the log data is in the console log AND the build log, if that's what you need.
No idea where to add "2>&1 | tee somefile.txt" ;-( Nick, can you do it please? I don't think I need stdout in the build.log because it can grow very large. If I detect an error I can build with -noclean and look into emft.eclipse.org filesystem.
/org.eclipse.emf.net4j.releng/builder/tests/configs/local/relengbuildgtk.sh and /org.eclipse.emf.cdo.releng/builder/tests/configs/local/relengbuildgtk.sh already logging everything to console file; I added the 2>&1 thing so as to trap stderr too.
What does that mean? Where can I look at the console log?
http://emft.eclipse.org/modeling/emft/net4j/downloads/drops/0.8.0/N200709241248/testresults/consolelogs/linux.gtk_consolelog.txt does not contain stderr or stdout ;-(
The best I can suggests is to hack org.eclipse.test/library.xml, or use the few variables you have access to to pass in more vmargs via your /org.eclipse.emf.net4j/tests/org.eclipse.net4j.tests/test.xml: <ant target="core-test" antfile="${library-file}" dir="${eclipse-home}"> <!-- <property name="vmargs" value=""/> <property name="extraVMargs" value=""/> <property name="test-output" value=""/> --> ... If passing in more args won't help, then we'll have to devise a 'replace the standard library.xml with something else' approach, which I've had to do in the past for EMF. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=171756 for how to hack your build to replace library.xml with your own changes.
I really don't want to hack things that I don't know. Is it really so hard to receive stdout messages in the buildlog or somewhere else? Then I prefer to build my own linux machine just to see what happens during linux tests.
(In reply to comment #6) > I really don't want to hack things that I don't know. > Is it really so hard to receive stdout messages in the buildlog or somewhere > else? > Then I prefer to build my own linux machine just to see what happens during > linux tests. Well, you could adopt your own version of org.eclipse.test and check it out from another location in CVS. As long as the mapfile is accurate, it won't be a hack, it'll be your own EPL'd version. ;-) As to building your own build server / running the build locally... by all means. You can either follow the config steps in http://wiki.eclipse.org/EMF_Build_Server_Setup, or just build inside Eclipse (not headless), then use the various Export options to create zips and test results. From there you should be able to use a promoteToEclipse.sh-like script to upload the folder w/ the zips and test results to dev.eclipse.org. See /cvsroot/modeling/releng-common/ for server config stuff and build/promote scripts (in tools/scripts/).
No, I didn't mean to produce builds with an on server. It could only help me to track down linux related problems (filesystem, ...) in the case that we don't manage to get the stdout into some file with out build.
later
Reversioned due to graduation
LATER/REMIND bugs are being automatically reopened as P5 because the LATER and REMIND resolutions are deprecated.
Closing. Please reopen if you feel this should be addressed.
