-
Notifications
You must be signed in to change notification settings - Fork 29
Remove gcdiff and adjust testsuite #230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: gc4
Are you sure you want to change the base?
Conversation
That approach is good, but let's try to get rid of those sed invocations (or make them simpler/less used, for example with SOURCE_DATA_EPOCH) in 3.x first, then merge the change over (I think most of the effected lines will use gcdiff in 4.x). Oh, and another note: you don't need to use the underscore-sed hack, it may be much easier to use Interesting to see that this PR does uncover some tests that have a different result and was not recognized before because of the use of gcdiff. |
04cd061
to
67e3d7f
Compare
I'd do that when time permits.
Ah, I though those underscores were just a visual reminder that the trailing spaces are intentional.
I was as surprised as you are. |
... waits for rebase ... |
Rebased. Still a bit of work to do. One test in
What should be changed in NOTES ? |
NOTES is a document we'll handle berfore handling the TODO - you can just delete any elements related to gcdiff in this file as part of this PR (less to glance over). And yes: SOURCE_DATE_EPOCH must be handled in everything that is generated by the compiler by using the central general time routines that are used otherwise within cobc for timestamps; it may should use the same time than the generated .c file, but that's up to the fixing person (= you :-). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
both commits are nearly fine, please adjust (and feel free to do that in the upstream commit directly, if you want to)
Merged in SVN @ 5526 and 5527. |
Test failures on 32bit - so we either need a sed script or a conditional test here:
|
Ah, I knew I had forgotten something. Maybe this calls for a 32-bit Ubuntu CI (we only test 32-bit on MSYS2 and MSVC). |
Hm, shouldn't the 32bit MSYS test have failed as well? We may still ignore the failure (but should try to skip/ignore, then error the CI also on Win32)... Concerning the ubuntu one, this is the different part that we run on appveyor (starting from the already created dev tarball) for the 32bit build on Ubuntu (also testing older GCC) sudo apt install -y lib32gcc-7-dev libgmp-dev:i386 libdb-dev:i386 libncurses5-dev:i386 libxml2-dev:i386 libicu-dev:i386 libodbc1:i386 odbcinst1debian2:i386 unixodbc-dev:i386
export PKGCONFIG_PATH=/usr/lib32/pkgconfig:/usr/local/lib32/pkgconfig:/usr/local/lib/pkgconfig:/usr/lib/pkgconfig
./configure CC="gcc-7 -m32" --with-odbc |
The thing is, test 846 fails anyways on MSYS2 & MSVC because of a segfault (even on 64-bit). 847 is now okay on 32-bit.
I'm gonna try to tweak the Ubuntu CI using this info (first on GC3, then on GC4). |
sure (for GC3 obviously without the odbc/oci part and for configure using |
Fix merged in SVN @ 5535. |
This PR removes gcdiff and adjusts the testsuite to accomodate for the changes.